On 3/9/06, Fabian M. Schindler, Yoper Ltd. <[EMAIL PROTECTED]> wrote:
Ok, so in the new Team Layout, i have added to hold Fabian's point of having Sub-Sections - Contact Sheets. The link is
http://www.yoper.com/wiki/index.php?title=Team_Members:_Yoper_Board_Members#Contacts
Please pour in your comments whether can we follow this layout.This "Contacts" column will have contact details of everybody in the Team. The status would tell what position is he in the Team.
The only sub-section which i have left out is "Responsibilities".Do we really need it here since the Team Description and Summary would tell what the team does.
Here are my thoughts based on the team meeting.
-------------
Requirements for a team-coordination program
1. It must be possible to set up a central database for the team. In this database, there should be individual accounts for each member where contact data will be stored, like a valid email-address (minimal requirement). Furthermore, the contact sheet should point out the sub-section, where the team member is active (e.g. KDE-team).
e.g.: Dept.: Yoper graphics
Name: Fabian M. Schindler
Status: Dept. Leader
email: [EMAIL PROTECTED]
Responsibilities: Coordination of design-work for Yoper releases, ...
Ok, so in the new Team Layout, i have added to hold Fabian's point of having Sub-Sections - Contact Sheets. The link is
http://www.yoper.com/wiki/index.php?title=Team_Members:_Yoper_Board_Members#Contacts
Please pour in your comments whether can we follow this layout.This "Contacts" column will have contact details of everybody in the Team. The status would tell what position is he in the Team.
The only sub-section which i have left out is "Responsibilities".Do we really need it here since the Team Description and Summary would tell what the team does.
2. A central database /sheet for each section should be available on a Wiki basis. With a Wiki, tasks can be added later to the team profile or changed, if needed. Responsibilities of the teams should be pointed out clearly. If possible, a mail-address for every subsection of Yoper should be available (e.g. [EMAIL PROTECTED]), thus contacting the "relevant" team members is easier for developers and the amount of time spent by the whole Yoper-team on reading mails that are of secondary to none importance to individuals can be reduced. Result: Better work-flow and organization.
3. Each team should have a Wiki or similar page, where they can discuss and upload things and where monthly reports will be stored. The reports do not need to be large, but they should point out, where the development currently is and if there are problems that might delay the release of Yoper. If delays are expected, team leaders should note down how much time they guess Yoper might be behind schedule.
4. One central calendar should be available. In this calendar, team meetings should be announced, as well as release dates and other important events.
5. One section for new developers (FAQs/HOWTOs) should be made available on one separate section of the new board.
6. One page should show a typical schedule for a Yoper release. This structure should allow all members to follow the development process and reduce "chaos". E.g.
Step 1: Team meeting – evaluate Yoper and decide which apps and features are needed.
Step 2: Assign Teams and check availability of team members
Step 3: Team meeting – discuss team structure and expected time for new release
Step 4: Kernel-team: Decide on compilers, set up relevant programs and a clean buildserver
Step 5: Kernel-team: Build first kernel for bugtesting
etc.
I don't know if mantis can do all that. If not, I suggest using egroupware. Add your thoughts and ideas.
Cheers,Fabian
_______________________________________________
yoper-dev mailing list
[email protected]
https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
--
Regards,
Chaks,
Yoper Ltd.
http://www.yoper.com
http://www.yoper.com/forum
--
The main aim of communication is clarity and simplicity. Simplicity means focussed effort.
_______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
