This document is intended to clarify the precise workflow and project management structure we’ll be using for rolling projects for the Brigade.
Precursor: If a brigade member or resident has a general topic in his/her head that might make a useful project but doesn’t quite know whether it fits or whether it’s more observational, you may want to create a free-form topic in the Community Input section of this forum or post to Slack to help plant a seed.
Steps in the Open Savannah agile project development process:
IDEATION: All projects begin by creating an open-ended project idea statement in the Proposed Project section of this forum as well as on Slack, if desired. See the topic ‘Proposing a new civic tech project - Guideline/Format’ for detailed instructions.
VALIDATION: Brigade members weigh in on the project statement in the forum or on Slack, generally over the course of about a week or so. If the project is feasible, a call for an initial Project Lead/Maintainer will be made. Usually, the original poster of the project statement will take on this role.
DISCOVERY: After the project has been validated and a project lead assigned, it may be moved from the ‘Proposed’ to the ‘Active’ project parent category under a new subcategory for the project name. In addition, the following should be set up by the Project Lead:
- Creation of GitHub repository with README.md intro documentation file.
- On opensavannah.org, log in with GitHub, select
Manage Brigade, then select
Sync Projects With GitHub, You should now see your newly created GH repo in the
Inactive Project list on the page
/projects. Activate it, add a thumbnail, save changes.
- As you assemble contributors and add tags, you’ll notice that changes sync between GH and opensavannah.org.
- Allow users unfamiliar with GitHub who would like to contribute to the repository to use Prose.io, which is essentially a WYSWIWYG editor for GitHub.
5 PROJECT/TASK MANAGEMENT
We use waffle.io
WORK IN PROGRESS