+0 to apply to become an Apache incubator project. Even with reading I've done, I still don't feel I know enough.
Server issues would decrease dramatically, and we could concentrate on Habari, not infrastructure. We would still need to maintain separate space for -extras and a publicly editable wiki, if I understand things correctly. I'm not totally clear of what the status of a plugin/theme repository would be. Perhaps it could be part of the blog, which the wiki says we could still maintain (http://wiki.habariproject.org/en/ ASF_Incubation). Since the plugins/themes wouldn't be an official part of Habari, it seems they wouldn't be a problem, especially since we would be linking to them from the repository, not hosting them, but again, that is unclear. The public relations aspect of being under the Apache umbrella don't mean a lot to me. I know what the Apache web server is. If I hear the word 'Apache', generally the server is what I first think of. Some of the names of other Apache projects I vaguely recognize, but that's it. Maybe I'm sheltered or illiterate, but to me, that says something about the power of the name amongst the general populace. The legal framework we would gain is a huge plus, both for the protection it could give in the as yet farfetched event of a lawsuit, and as a way to reasonably deal with finances as the project grows. The downside is, any framework will bring restrictions. Most notably here is the need for CLAs from all contributers. I have no problem with that for myself, but what of users who file a bug report and a patch to fix it? As I understand it, they would also have to agree to a CLA. In the worst case scenario, someone who has contributed many patches to Habari may not do so. Would we have to remove any of their code that already exists in Habari? Another positive effect of becoming an Apache incubator project is the opportunity for 'professional development' (for want of a better phrase) it brings. We would learn, and experience how mature software projects are run. Many current members of the PMC are all too familiar with working on such software projects already. Many of us are not. In the long run, Habari the software, and those of us who work on it, would benefit. But the 'community' of which the Habari software is supposed to be a part would change. I'm not sure that change would be for the better. Rick --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users -~----------~----~----~----~------~----~------~--~---
