[Bigdata-developers] overview of active development.

[Bryan T. <br...@sy...>]

Hello,

Now that there is an increasing number of people working on the code base, I think that we need to improve our coordination somewhat so I (and others) can keep track of what is going on with the project.

I am open to suggestions here, but it seems that the most scalable approach is to move to a model where people open and accept an issue before they touch the code and then keep the status updated on the accepted issues.  

We are also building up a list of more minor issues on trac which lack top-level categorization.  Would someone like to step up to help maintain and impose order on the trac issues?  The current organizational scheme uses "milestones" to capture high level areas of activity for the project, such as High Availability, Query Optimization, Performance Optimizations, etc.  There is also an orthoginal set of components (Journal, Federation, RDF database, etc).  Both of these could be refined somewhat to include additional distinctions.

Thanks,
Bryan