MNX Issue Review Process

Hi Group Members,

Daniel and Michael and I met last week to discuss how we'll move forward on
handling GitHub issues with the MNX repository.

Here's a rough outline of the process we are proposing, and we envision
getting started with it in the next few weeks:

- Every couple of weeks, all three co-chairs will examine issues filed
since the last review.
- Reviewed issues will be assigned to one of these issue milestones:
"Uncommitted" (release priority undecided), "V1" (must be addressed in
initial release of CG spec) and "V Next" (can be deferred to a subsequent
release).
- The chair will append questions to issues where clarification is needed.
- After receiving clarification, the chair may close issues that are not in
the scope of the CG charter, are poorly defined, or are otherwise not
actionable.
- Members wishing to be notified of issue activity will need to watch the
Github repository.

Members' comments on this proposed process are welcome.

.            .       .    .  . ...Joe

Joe Berkovitz
Founder
Noteflight LLC

49R Day Street
Somerville MA 02144
USA

"Bring music to life"
www.noteflight.com