Issue priorities

Hi All,

Since we start to have a good list of issues [1], I'd ask the editor, with the help of the group, to take a first stab at assigning priorities to the issues. GH makes the priority setting easy using labels. To keep this simple, we could use:

P1 = High
P2 = Med
P3 = Low

I suggest the primary responsibility is on the editor to ensure the issue priorities reflect the group's consensus.

To give more context, other labels (bug, duplicate, enhancement etc.) could be used in addition to P{1,2,3}.

[Later on, we can create milestones that map to the standards track stages (First Public Working Draft, Last Call, Candidate Rec etc., see [2]) and associate the issues with the milestones.]

I think this would help not only the group's current participants, but also new people who are still joining the group, to have a shared understanding of the priorities.

I've documented this proposal in the Work Mode wiki at [3].

All - comments and suggestions welcome.

Thanks,

-Anssi

[1] https://github.com/w3c/presentation-api/issues
[2] http://www.w3.org/2014/Process-20140801/#recs-and-notes
[3] https://www.w3.org/wiki/Second_Screen/Work_Mode

Received on Friday, 21 November 2014 12:45:22 UTC