User:JimDeLaHunt/ArchivePage/CSGD IssuesList 200802
ClassicalStyleGuideDiscussion Issues List
This page tracks just the status of proposals to change the ClassicalStyleGuide, and AdvancedRelationships as they apply to ClassicalMusic, and related changes to the MusicBrainzWiki. It doesn't summarise the proposals themselves.
The purpose of this page is to give contributors who are proposing changes, and the StyleCouncil who have to approve them, some visibility into what proposals exist, where they are in the process, and how active they are.
Open (and Stuck) Issues
See Table Key below for an explanation of what goes into each column.
|ID||Short name||State||Champion||Proposal||RFC (link, date)||RFV (link, date)||Decision||Implemented||Last changed by, on|
|2007-03-a||Performer as Artist||Open||AaronCooper||CSGD "performer as artist" 2007-03||JimDeLaHunt 2008-02-06|
Here are is what goes in each column of the Issues List.
- a string of the form YYYY-MM-x which uniquely identifies this issue through its lifetime. e.g. "2007-03-a". YYYY is the 4-digit year, MM is the two-digit month, and x is a lowercase letter or letters from the sequence 'a', 'b', 'c', ...'z', 'aa', 'ab', ...'az', 'ba', etc. Each ID is unique among all Issues List IDs. The editor who adds the entry to the list uses the year and month when the issue is added, and the next letter from the sequence. Once assigned, the ID should not change.
- Short name
- a brief, simple phrase with which contributors can refer to the proposal. e.g. "Performer as Artist". It is good for it to be unique among open, not-stuck proposals, but need not be unique across entire list, since the ID is unique. Once assigned, this phrase should not change, but may if its content changes a lot or if it helps disambiguate between issues.
- One of the following three strings: Open, Stuck, or Closed. Open means that the issue has started the process, is not Closed or Stuck. Closed means that the issue has been affirmatively removed from the process; it has been completed or StyleCouncil has decided to abandon it. Stuck means that an issue is not Closed, but there has been no discussion or action on it for a period of 30 days or more. An issue can be Stuck at any phase of the StyleCouncil workflow before completion. Update this entry from time to time to reflect the current reality.
- the WikiName of the contributor who is a main proponent currently active proponent of the change. e.g. JimDeLaHunt. The Champion can change from time to time, as one person loses interest and another takes it up. Any contributor who is generating attention for a proposal can be the Champion. The Champion may not be the person who needs to take the next action, but usually is.
A brief phrase linking to the location where the text of the proposal is, and the proposal date. e.g.
[:ClassicalStyleGuideDiscussion#head-9978b1d7d5d9f53b6340180e2bc1fd3b1cb9c040:CSGD "performer as artist"] 2007-03. This may be a WikiName page name, and the proposal text will be on that page (perhaps under a Discussion heading, or a subhead). In that case, use the MoinMoinWikiSyntax
[:WikiName#anchor:brief text]so that the link is concise in the table, but links directly to the heading where the proposal is. This link may also be a URL to a mailing list or forum posting making the proposal, probably starting a thread of discussion. In that case, use the link syntax
[http://www.nabble.com/<url>.html brief text]. Or use whatever linking syntax seems to work. If discussion happens at a different place than the proposal, link to that too. The date is a string of digits in the form YYYY-MM when the proposal was first sent. If discussion unfolds in the same general page or thread or forum for a few months, there's no need to update the link or date. The purpose is to give people a place to start finding the discussion. Detailed lists of links to discussions belong on a wiki page or section devoted to the proposal. If a proposal gets restated several times a few months apart, it's enough to keep just the most recent few proposal links.
- RFC (link, date)
- A brief phrase linking to the location where the formal RequestForComment (RFC) is, and the RFC date. The link has the same syntax as for Proposal above. The date should include the day, i.e. YYYY-MM-DD. This field stays blank until there is a formal RFC.
- RFV (link, date)
- A brief phrase linking to the location where the formal RequestForVeto (RFV) is, and the RFV date. Same syntax as for RFC above. This field stays blank until there is a formal RFV.
- A brief summary of the decision, the date that decision was declared, and a link to the URL of the archive for the mailing list message announcing that decision. According to the StyleCouncil process, the change is announced to the UsersMailingList and recorded in RecentStyleChanges. Same syntax as for RFC above. This field stays blank until there is a formal decision.
- A brief summary of the implementation made, the date that implementation was completed, and a link to the URL of the archive for the mailing list message announcing that completion. According to the StyleCouncil process, the change is announced to the UsersMailingList and recorded in RecentStyleChanges. There can be considerable time lag between when the decision is made and the implementation occurs. Same syntax as for RFC above. This field stays blank until the implementation is complete.
- Last changed by, on
- The WikiName of the contributor most recently editing this row of the table, and the date of that change in YYYY-MM-DD form. This is just a simple record of how recent the table contents are.
This section contains entries from the Open Issues table above, once those issues have reached the Closed state. It serves as a historical record. Add newly-closed records to the top of the table, so that it's sorted roughly in reverse chronological order by date closed.
No entries in this table yet
How to use this table to track issues
Discuss the use of this table, and tracking of issues, here. Do not discuss the pros and cons of individual proposals here; do that in ClassicalStyleGuideDiscussion.
JimDeLaHunt created this list on his own initiative, because in January 2008 a number of proposals to revise the ClassicalStyleGuide gained momentum, and he saw a need to be able to track them. —JimDeLaHunt 2008-02-06