On Tuesday, October 2, 2012, Bertrand Delacretaz wrote: > On Tue, Oct 2, 2012 at 3:10 AM, Blaine Bradbury > <bla...@blainebradbury.com <javascript:;>> wrote: > > ...I think it would be EXTREMELY useful to have a device which could > show the > > current (as close to the present knowledge as is really manageable) > > trajectory that the Apache Flex project is taking... > > From my experience with other Apache projects, the best way to achieve > that is by using the issue tracker in a way that reflects people's > actual actions. > > A contributor creates issues at > https://issues.apache.org/jira/browse/FLEX for things that they intend > to work on, marks them as "wishlist" if not working on them > immediately, updates their status as they go on working on them. Using > hierarchical issues ("blocked by") allows you to group them in logical > blocks and see which issues need to be fixed to reach a given goal. > Each issue can also serve as a mini-documentation of the feature in > question, by including a description of the use case and test > scenarios. > > Combined with a high-level overview of the general direction that > active contributors want the project to take, this is IMO the best way > of exposing the "project trajectory", in real time. > > -Bertrand >
Hadn't thought about that. JIRA makes the most sense to me. -omar
