Did we want to review it more time as a group tomorrow before opening it up – will only need 5min.

 

thx

 

 

From: <tech-council@ole-lists.openlibraryfoundation.org> on behalf of Jakub Skoczen <jakub@indexdata.com>
Reply-To: "tech-council@ole-lists.openlibraryfoundation.org" <tech-council@ole-lists.openlibraryfoundation.org>
Date: Tuesday, July 17, 2018 at 11:06 AM
To: "tech-council@ole-lists.openlibraryfoundation.org" <tech-council@ole-lists.openlibraryfoundation.org>
Cc: Tod Olson <tod@uchicago.edu>
Subject: Re: updated Def of Done

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

I have added comments to the doc today. Mark may want to have a chance to address them before we post it.

 

On Tue, 17 Jul 2018 at 16.45, Tod Olson <tod@uchicago.edu> wrote:

Yes, I think the document is already in pretty good shape and that this is a good time to post it.

 

-Tod

 



On Jul 17, 2018, at 9:42 AM, Mike Gorrell <mdg@indexdata.com> wrote:

 

Folks,

 

Would people be OK posting this to the #developer channel and asking for feedback?

 

-mdg

 



On Jul 16, 2018, at 5:27 PM, Mark Veksler <mveksler@ebsco.com> wrote:

 

Good afternoon everyone,

 

I converted the spreadsheet version of the DoD document to Google doc.  Here it is for your reading pleasure (or if you need something to quickly fall asleep):

I changed the link on the Tech Council’s confluence page too.

 

In this version I (think I) addressed a couple of comments raised in the sheets version.  Please remember to submit your comments by eod tomorrow.

 

As I was finishing work on the doc, I thought of the next steps (all are listed in the document now)

 

  • Document and publish NFRs
  • Establish and document security vulnerability quality gate in SonarQube.  When do we run it?  Should it happen nightly when the code deploys to an integration environment?  
  • Document and publish UX guidelines: http://ux.folio.org/docs/design-guidelines/
  • Define severity levels of the issues found by QA (critical, high, etc)
  • Define supported FOLIO browser/devices
  • Agree whether testing a feature across all supported browsers would need to be included in the nightly regression testing Jenkins job

 

 

Thanks,

-m

 

-- 

Mark Veksler

Director, FOLIO Development - EBSCO Information Services

mveksler@ebsco.com | +1-978-356-6500 x2349 (O) | +1-617-470-5453 (m)

 

To unsubscribe from this list please go to http://archives.simplelists.com

 

To unsubscribe from this list please go to http://archives.simplelists.com

 

To unsubscribe from this list please go to http://archives.simplelists.com

--

--

Regards,

Jakub Skoczen

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=Vy4UmbCQg2YUuehuMGk9b9LQwA9fx5Pb