Page History

...

• pick the issue at hand
• burst of discussion on the list
• secretary captures the salient points
• offers up the document for review
• go back to discussion/capture/review until complete
• a final document then accompanies the resolution and the issue is closed

NOTES:

• a filter can be created to send all unresolved issues to the dev list
• JIRA is used as a tracker not a place for discussion
• TODO do we want a separate project for design/best practices discussions
• possibility of setting up a custom workflow
• demonstrate design/practices as opposed to scheduled work

One person might start a discussion but it can be picked up by anyone who has the energy/motivation/time/whatever to finish it. I think what happened with the dev process works just fine. The issue was in JIRA with me assigned, but you had time to post some initial thoughts and I tried to follow up with a document. The issue needs a champion but anyone should be able to carry it to completion because all the information should be clearly visible.

once its in JIRA, it doesn't need a
champion. I was just making sure it didn't get buried, but
responsibility for momentum can be carried by anyone able to at any
given time.

Where new development starts

...