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 VekslerDirector, FOLIO Development - EBSCO Information Servicesmveksler@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://www.simplelists.com/confirm.php?u=Uhvs4dEChs1inyA5TUDqoiU9gKMSF09K