At the moment, the lines are blurry. However, every project team has
one or more Zenders on the team, sometimes with one Zender coordinating
a particular component, and another Zender coordinating a different
component within the same project team. For a small number of
components, multiple Zenders work on them.
Some components, and several contributors are not yet listed on the team
wiki pages in the table below. Contributors are encouraged to add their
missing components and names to components they are supporting.
However, there are Zenders listed on each project team page:
http://framework.zend.com/wiki/x/GgE
Cheers,
Gavin
André Hoffmann wrote:
The other day you mentioned that each team is going to be led by a
'Zender'. When are we going to hear more about that?
On 9/23/06, *Gavin Vess* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
I'm excited to report we now have formation of project teams
around both team wiki pages and team-specific mail lists!
Please join us by subscribing to the mail lists that interest you,
using the email account you wish to send messages from.
Project Team Wiki Pages
============================
- team members (add yourself if your name is missing)
- team's ZF components
- who is working on which components, including coordinators
- major milestones
- tasks needed to accomplish milestones
- what help is needed (very important)
Project Teams
=============================
Auth: http://framework.zend.com/wiki/x/qBM
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Core: http://framework.zend.com/wiki/x/QxM [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
DB: http://framework.zend.com/wiki/x/0xM [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Doc: http://framework.zend.com/wiki/x/_ws [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
I18N/Locale:
http://framework.zend.com/wiki/x/Lx [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
MFS:
http://framework.zend.com/wiki/x/mRI [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
MVC: http://framework.zend.com/wiki/x/mRI [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Server:
http://framework.zend.com/wiki/x/Fx [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Web Services: http://framework.zend.com/wiki/x/zhM
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
How to Subscribe
=============================
You may subscribe to each list individually, according to your
preference,
or you may subscribe to all the new lists using
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Do *not* subscribe to both fw-all and one of these lists, or you will
get *duplicate* messages.
To subscribe, send a mail to [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
- e.g. [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Please remember to subscribe the email address you use to post
messages. We have to manually review and approve all messages
received from email addresses not subscribed to a mail list.
Project Team Responsibilities
=============================
Each project team is responsible for producing status updates /
newsletters:
- Zend project team members will help and work with community
members on
each team
- copy emailed to fw-general and team-specific mail list
- publish update every two weeks to wiki
- all team members can help update the team's wiki page
- all team members can help author a wiki page containing the
status update
We need *each* team to study the other team's wiki pages and borrow
ideas to improve their wiki team page. The pages don't need to be
identical, and some things will work better for different
teams. Don't
be afraid to improve something I edited. Be creative =)
Also, coordinators and everyone else should help identify tasks and
things to list under "help wanted" sections. We are an open
community,
and each project team should be receptive and open to finding areas
for community members to help.
Cheers,
Gavin
Community Development Server Project?
==============================
Goal: Make all ZF mail lists searchable via the web using ZF and
Zend_Search_Lucene.
Why not use JIRA? The search feature of JIRA lacked
precision. Also,
JIRA's trackback feature was disabled due to spam problems, so the
value of auto-indexing emails into JIRA diminished further.
Andi Gutmans wrote:
> The idea behind separating the various related components into
> separate mailing lists and having bigger teams is that it'll enable
> better inter-component design and architecture, plus it is our
> experience that having these discussions in bigger groups (which
> previously were held most directly with Zend) will foster an
> environment where ideas+proposals are more mature and less work
needs
> to be done afterwards (it will significantly shorten any peer
review
> process).
--
best regards,
André Hoffmann
Germany
