Summary
==========
I'm keenly interested in helping find teammates and build teams around
these Zend Framework projects. Our website infrastructure provides much
of the technology support needed, and the new project teams will help
provide both the social infrastructure and documentation needed to
support the team's activities and growth.
The next release of the ZF will provide a superb opportunity for all of
us to reach out to the PHP community, as a result of all your hard work,
including supporting materials found in the wiki, the new project team
wikis, and the manual. Instant message technologies have many benefits,
but the wiki "spaces" provide the place for all of us to help summarize
key information and make participation in the ZF projects easy and fun
for all.
By identifying milestones and key tasks on project teams' wiki pages,
volunteers will find places and ways to help, and the ZF project teams
will find new members :)
The Details ...
=============
Some initial "preparation" work has been in our focus recently, including:
* getting ready for 0.2,
* standardizing and identifying best practices to keep our diverse teams
consistent,
* improving documentation (makes it easier to recruit and easier for new
recruits),
* improving our wiki (lots of good content, but confusing organization),
* and paving the way for project teams through project team wiki "spaces".
With the release of 0.2 and updated documentation, I am confident we
will achieve an important new milestone in the development of ZF. With
improved components, documentation, and supporting materials on the
website, we can achieve much greater efficiency in helping new community
members past the friendly ZF learning curve on the path to becoming
valuable contributors. Also, as we improve documentation, improve our
wiki spaces, establish project teams, and continually add and improve ZF
functionality, the world's interest in ZF rises along with our
opportunities to highlight specific needs for each project team. As
each project team take shape and forms, specific goals, milestones, and
tasks become clearly identified, allowing for the possibility of
highlighting these opportunities to the PHP community -e.g. features in
Zend DevZone, personal blogs, etc. We already have a good start for the
Documentation Team, Server Management Team, and Locale Team wiki spaces,
prior to the roadmap announcement.
In conclusion, all these factors make it easier for new recruits to find
and achieve productive ways to contribute to the ZF. I see 0.2 as a
major milestone and accomplishment which will present an ideal time for
reaching out to the PHP community in search of additional ZF project
team members to help with the tasks described in each project team's
wiki "space". We'll be launching the remaining ZF project teams' wiki
spaces over the next couple days, and look forward to a rapid pace of
feedback, improvements, and participation in the true spirit of
wiki-authored documents and the ZF community. Although component
proposal authors are expected to coordinate the effort for their
component, many know there are numerous areas where additional teammates
could help. Your valuable help in this effort will result in successful
wiki-based project team materials and task descriptions to attract new
PHP community members to the ZF project teams, and coordinate who works
on each task.
Cheers,
Gavin
Andi Gutmans wrote:
Yep, I'll see if we can put this up someplace. If not on the homepage then
on the Wiki.
Sorry to hear you don't have more contributors around i18n. Maybe getting up
project pages would help. We'll try and make that a priority in the coming
days. Obviously this is a longer process and it'll take a bit of time to
find the right way of doing it and getting more contributors.
-----Original Message-----
From: Thomas Weidner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006 5:45 AM
To: Andi Gutmans; 'Zend Framework General'
Subject: Re: [fw-general] Roadmap Update
Hy,
Better late than never :)
Hope dies at last ;-)
Now the Summer is over and everyone is back at work, we
feel it's the
right time to finish planning the 1.0 release.
It would be great to have the detailed roadmap on the homepage.
Also a not so detailed roadmap (Roadmap Overview) would be great.
Just to become a feeling on which timespans we're speaking
for the different upcoming release versions.
These teams would focus on their area, set milestones for getting
closure on the various pieces and recruit contributors to
their team.
To be clear the component leads would still lead their
component but
we'd have more focused groups helping each other out.
Requireness:
We need headhunters to get contributors ;-) As example: Since
I proposed the locale proposals there were only 2 people who
wanted to help.
I'm already coding several months and until now i've had no
time to search for new helping hands.
How ever, it's a great idea to group several related
components together to increase efforts.
Happy Frameworking!
The Zend Team
Happy releasing ;-)
The Locale Team ;-)
