Skip to content
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.

Conformance Questionnaire Development Process #43

Open
shanecoughlan opened this issue Jun 26, 2020 · 1 comment
Open

Conformance Questionnaire Development Process #43

shanecoughlan opened this issue Jun 26, 2020 · 1 comment
Assignees

Comments

@shanecoughlan
Copy link
Contributor

The conformance questionnaire for OpenChain Specification 2.0 was developed and deployed largely by a small team, particularly @goneall , and moving forward to OpenChain Specification 2.1 (ISO version of 2.0) it would be useful to ensure the workload is more widely distributed. Adding @MarkGisi to this thread.

Proposal:
(1) We move editing of the questionnaire into the Spec review calls (bi-weekly, second and fourth Monday each month, 9am and 5pm Pacific respectively).
(2) We seek to have the questionnaire ready by September 15th 2020 to allow time to get it live before the expected September 22nd 2020 ISO completion date.

Comments?

@goneall
Copy link
Collaborator

goneall commented Jul 15, 2020

it would be useful to ensure the workload is more widely distributed

+1 :)

(1) We move editing of the questionnaire into the Spec review calls (bi-weekly, second and fourth Monday each month, 9am and 5pm Pacific respectively).

Agree - this seems to be a good forum for editing, discussion and review

(2) We seek to have the questionnaire ready by September 15th 2020 to allow time to get it live before the expected September 22nd 2020 ISO completion date.

This would depend on the agenda and bandwidth of the Spec review calls @shanecoughlan and @MarkGisi I'll leave this up to you

We could use pull requests against the questionnaire JSON files as the mechanisms for doing the actual edits. I can go over the mechanics of this on one of the upcoming spec calls.

I can think of 2 approaches using the Spec review call:

  1. Review and update the questionnaire online during the review call itself
  2. Go over the mechanics of updating the questionnaire on one of the calls and ask for volunteers to review and update specific sections as pull requests. You could then review the PR's either on the call or prior to the call and close/merge once aproved.

@MarkGisi I'll leave this up to you if you agree to include it in the Spec review call.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants