Jun 09 2005
For a while it seems that some members of the Mojavi community that have wanted Mojavi development to be a little more open. I can’t say I blame them really, if an open source project is promising big things is it really to much to ask for a little feedback as to how things are progressing…. if they’re not, say so.
I know that Sean Kerr is protective of his project, I’m just as protective of mine, but when a project gets this big I guess the game changes a little and you need to start thinking more about what the users are shouting a less about absolute perfection before saying anything to the community. I know it is possible to get the latest updates to Mojavi from Subversion, but who wants to keep checking for updates with subversion and then trying to figure exactly whats changed and how it affects your current system.
On the other hand I’m not going to be placing all bets with Agavi (the new community branch of Mojavi). I may have taken this the wrong way but they seem to have come into the Mojavi Forum with guns blazing, boasting about their new branch of Mojavi and how wonderful its going to be but to me it seems like its going to be a “Programming by Committee” effort of which I’ve had some experience and don’t wish to experience again.
For historic purposes (in case it gets pulled from the Mojavi Forum) here is what they wrote:
First and foremost, we would like to openly thank Sean Kerr and the entire Mojavi development team for their contributions to the PHP community. The 3.0.0-DEV branch of Mojavi is impressive to say the least. At the same time, some of us find ourselves wanting something more. To that end, a small team has joined together in an effort to fill in the gaps and perhaps even take development off into a slightly different direction than what was originally intended.
Our goals and focus at this point are quite simple:
- Community based development. Existing developers vote on accepting patches and developers. It is our hope that our work will encourage others to get involved and join our efforts to make Agavi the best it can be.
- Open development. It’s pretty disheartening as a developer to not be informed about what potential plans or changes are going on in the development of a fundamental library which you are committed to using. Development and discussion thereof will be completely in the open, no ‘behind the scenes’/’in the dark’ black magic sillyness.
- Promote Test Driven Development. We are firm believers in Test First coding practices and are comitted to providing as close to 100% unit test coverage for the framework and encourage a test first coding practice by developers using the framework.
Though many more exist, we believe these to be the major points which seperates Agavi from Mojavi. We encourage you to take a more in-depth look at our project and goals, and additionally welcome any feedback (positive or negative).
The Agavi Foundation