> What do you have in mind to solve this?
Well, what I had in mind, actually, was precisely not a passive "people are
welcome to fork the repo and patch bugs themselves and submit them for
approval". That might bring us a few isolated contributions here and there,
but that's not really what the framework needs at this point, in my opinion.
The framework seems to becoming a framework supported by one person, Mark
Story, and I don't believe it is healthy for any framework to be on the
shoulders of only one person, no matter how great a developer he is.
I was hoping that whoever is "in charge" of cakephp these days might
consider doing all or some of the following:
1. Identify within the cake core 10 or more reasonably defined areas.
2. Put up a wiki with a section for each one of these areas. Describe in
general what the area does, how it currently works, what deficiencies there
are, what things need to be done to get to the next level.
3. Actively solicit a team leader for each area, as well as additional
developers who want to assist that team leader in building the area up,
implementing some of the proposed ideas, and proposing additional ideas.
3. Set up a developer forum, where each area can be discussed for ideas for
improvement. Make the forum visible to the community, so others, can view
and feel part of the ongoing development thought. If they have development
related ideas for the core, or the issues being discussed, they have a place
to add them.
4. Add a blog to cakephp.org with a "weekly news on cakephp development".
There you would describe the updates made this week, summarize some of the
issues being discussed, mention new sites recently built with cake, mention
other blogs or sources which are discussing cake (see the Symfony2 blog
"week of symfony - great idea).
5. Make a list of side projects which need to be developed for the cake
community, separate from the core, and actively solicit developers to make
it happen.
eg.
A) a cake plugins site, modelled after Joomla extensions, for all
plugins, descriptions, votes, community reviews, links to github or wherever
they are stored, editor's picks, etc.
B) the cake documentation project would have been a great thing to
outsource to someone this way.
6. Have a "Cake bug fix blitz-day" once a month, where all developers are
encouraged to take one bug and fix it.
The above are only a small sample of things one can (should) do. I'm sure
people can come up with many more ideas to help.
Please don't attack me for saying this stuff. I am on your side. I want to
see a healthy cake. A framework cannot continue to be based on the free time
of a single person. I believe quite strongly that if a "developer culture"
for the core is not cultivated, it will not be the best thing for cake's
future.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/cake-php
