[PLAN] Hustle: 0.2.0

[Davey Shafik]

Hey folks,

After a very productive IRC meeting last night, we have finalized our plans for Hustle (0.2.0) and proposed plans for Bump (0.3.0).

This information can be found here: https://github.com/frapi/frapi/wiki/Roadmap

Additionally, we have decided on a development process to help people contribute to the project, and to keep the project manageable.

You can find details about the development process here: https://github.com/frapi/frapi/wiki/Contributing-to-FRAPI — I plan to flesh this out much better at a later date.

Unless there are objections, I will continue to drive the development and act as release-manager.

Further, we have decided that for 0.2, we will ensure that the documentation at frapi.github.com is accurate (e.g. remove/fix any incorrect information) but that we will not necessarily try for complete.

I will soon start on creating a roadmap/plan for the documentation that will run separately, but concurrently alongside the development of FRAPI itself. Our goals are to educate on best practices, and their implementation within FRAPI.

Finally, we will be releasing a 0.1.1 maintenance release on July 1st; all issues for this release are assigned to the 0.1.1 milestone: https://github.com/frapi/frapi/issues?milestone=2&state=open

The milestone for 0.2.0 still needs some (most) tickets created: https://github.com/frapi/frapi/issues?milestone=3&state=open

With all the outcome said, I'd like to just document some of the decision making:

- We decided not to change the configuration away from XML files. The major argument in their favor is human edit-ability, and ease of automated upgrading without breaking anything (XML tools are easy, robust and plentiful)

- We are going with PEAR for our initial attempt at packaging/installing/upgrading. We are not yet committed to PEAR, and are willing to abandon it if it proves insufficient for the task. Other options to explore are Phing and Pyrus.

- Documentation is an on-going goal, and with the emphasis on education, not "How to use our software", it doesn't make sense to tie it to releases (though every attempt should be make to ensure it does cover new functionality before it's release). Managing the documentation will be handled through milestones and issues in the frapi.github.com repository.

If I have missed anything here, please feel free to ask questions or if you were part of the meeting add anything I missed.

- Davey