Mission Statements

From TYPO3Wiki

Jump to: navigation, search

<< Back to Teams page   (edit)

We need a scalable collaboration around building TYPO3! We have already divided us into teams and working groups - a natural move. But we need something to "kit" these together. Something to avoid misunderstandings. Something that will set expectations right. Something that makes it transparent who takes which sort of decisions and what the aims of the teams are. Something to control the chaos. So each team or project can and should write a "Mission Statement" (the former name was "Team Contract").

[edit]

Definition: Mission Statement

A Mission Statement (glossary-definition) defines a minimum of information about a team:

  • Location in TYPO3 universe: Which Committee, Team, Project does the team work under?
  • Description: What is the mission of the team?
  • Responsibility: Specifics about what the team is responsible to deliver!
  • Authority: Specifics about what decision power the team has been delegated!
  • Leader: Who is in charge of the team
  • Membership: How can you become a member of the team?

Contents

[edit]

The story behind and principle

The underlying principle of our teams should be to make them autonomous. This creates the least bureaucracy and the most joy of working in the team. To make a team autonomous but still productive as a piece of the TYPO3 puzzle we must work very hard to define two important things: Responsibility and Authority. Basically, we must fill in this sentence: "The X team is responsible for A, B & C and can work authoritatively on these goals as long as rule Y & Z are followed".

This is what the contract defines along with a little more information. All work of the team will subsequently be evaluated based on these responsibilities and authorizations.

[edit]

Getting started with the Mission Statements

To get these started, lets coorperate on defining these responsibilities and authorizations! When we have a first draft to try and implement we "fixate" this into contracts by which we will carry out our work. We can then refine the model as we go.

Below I have provided templates for all teams under the R&D committee. Please fill in the team under your command --Kasper 13:55, 9 June 2006 (CEST)

[edit]

Research & Development Committee Mission Statements:

The boxed elements are the teams under R&D: Image:RNDcommittee_teams.png


[edit]

5.0 Core Team

Leader: Not yet defined

Parent node: Research & Development Committee

Mission: To develop TYPO3 v5.0 to be an excellent, state-of-the-art next generation CMS enabling people to communicate with modern technology for years to come. Development will be a joint effort with the TYPO3 community and according to the present roadmap.

Tasks:

  • Process Strategy
    • Responsibility: Device an overall plan for execution of the mission. The plan should contain a suggested time frame and major steps on the way. Should be suitable for presentation to the community.
    • Authority: Full, within the limits of the roapmap and mission statement for the team.
    • Deadline: 1st. August 2006

More tasks will be defined after the "Process Strategy"

Delegated roles (optional): N/A

Membership requirement: N/A

Webpage URL: N/A

Mailing lists: Yet undecided, maybe new list? Maybe dev-list? Depends on results from the process strategy task.

Wiki: http://wiki.typo3.org/index.php/TYPO3_5.0-Development

[edit]

Core Team

Leader: Michael Stucki

Parent node: Research & Development Committee

Mission: To manage and execute detail level, short term development and bug fixing of the TYPO3 4.x Core plus release management.

Tasks:

  • Bugtracker:
    • Responsibility: Monitor and actively process entries in the bugtracker for bugs and feature requests to the TYPO3 Core
    • Authority: Complete management of the bug tracker as long as it remains an open service to the community for filing of bugs and feature requests for both TYPO3 core and extensions.
  • Release management:
    • Responsibility: Perform the release process of TYPO3 (see procedure)
    • Authority: Manage the release process of TYPO3 according to procedure as soon as the R&D committee says “go”.
  • CVS:
    • Responsibility: TYPO3core CVS module
    • Authority: Manage all rules and access to TYPO3core CVS as long as it respects the tradition that TYPO3 in CVS is not broken code but generally executable, even usable on production sites for experts.

Delegated roles (optional):

  • CVS service administration - Andreas Otto
  • CVS hosting - Sourceforge.net staff
  • Team website maintenance - Michael Stucki
  • Bugtracker administration - Sebastian Kurfürst, Michael Stucki
  • Bugtracker hosting - Michael Hirdes (Elios)
  • Team mailing list administration - Michael Stucki
  • Team mailing list hosting - Jan-Hendrik Heuing (Digital-District)

Membership requirement:

  • Members for the core team are handpicked from the community, based on skills and commitment
  • Members are expected to actively
    • solve/implement issues from the bug tracker
    • help approve patches according to procedure
  • Members can be excluded again by teamleader based on these criteria

Webpage URL: http://typo3.org/teams/core-development

Mailing lists:

  • Core Team list (typo3-team-core)
    • Purpose: The Core Team mailing list is the place where our team members publish their patches and improvements before they enter CVS. It is a very interesting resource if you want to stay up to date about the latest changes in TYPO3 development.
    • Significance: Decisions for patches and commits are made among core team members. Peers can follow daily work in the core team.
    • Access: read-only for public, write access for members.

Wiki:

[edit]

Security

Leader: Lars Houmark

Parent node: Research & Development Committee

Mission: To improve security in the core and help extension authors to secure their extensions.

Tasks:

  • Security Reviews
    • Responsibility: The Goal is to have all public available TYPO3 extensions reviewed by at least four eyes. Therefor a subproject "Security Reviews" was founded and the team currently searches for developers to volunteer.
  • Incident Response
    • Responsibility: React to reports of potential security issues. the security team analyses it and if the problem is reproduceable contacts the responsibile author of the extension and / or the core team.
    • Authority: Take care of the process of fixing security problems and inform the community via newsfeed, email and security bulletin on typo3.org. If an author is not reachable or not willing to fix a problem, the extension can be removed from TER.

Delegated roles :

  • Team website maintenance - Michael Stucki , Michael Hirdes
  • Team mailing list administration - Michael Stucki
  • Team mailing list hosting - Jan-Hendrik Heuing (Digital-District)

Membership requirement:

  • Members of the security list are picked from their reputation, skills and knowledge.
  • to become a member, people should
    • have profund knowledge of PHP / extension development
    • be familiar with common security problems regarding php / apache / mysql

Webpage URL: http://typo3.org/teams/security/

Form to report Security Issues http://typo3.org/teams/security/contact-us/

[edit]

Content Rendering

Leader: Ben van 't Ende

Parent node: Research & Development Committee

Mission: The Content Rendering Group provides or suggests means to get a semantical XHTML compliant output for the TYPO3 core and it's most important extensions (like tt_news, chc_forum). This would comprise writing XHTML templates, stylesheets, modifying TYPO3 core functions and suggesting new or improved functionality to enhance the presence of a TYPO3 website on the internet (like proper 404 handling).

Tasks:

  • [Task 1 title]
    • [Responsibility]
    • [Authority of execution]
  • [Task 1 title]
    • [Responsibility]
    • [Authority of execution]

Delegated roles (optional):

  • Programmer, bug fixer, bug tracker moderator, css_styled_content developer - Ernesto Baschny (Core Developer)
  • Programmer, bug fixer - Rupert Germann (Core Developer)
  • Programmer, bug fixer - Sebastian Kurfuerst (Core Developer)
  • Programmer, bug fixer - Ingo Renner
  • Programmer, bug fixer - Martin Kutscher (Core Developer)
  • Programmer - Joey Hasenau

Membership requirement: It is most logical to join CRG when you have actually already done something before for TYPO3

Webpage URL:

Mailing list/Newsgroup:

Wiki:

[edit]

Documentation

Leader: Daniel Brüßler and Virgil Huston

Parent node: Research & Development Committee

Mission: organization and ongoing maintenance of TYPO3 documentation, support for people or teams writing good documentation, support for documentation of current running TYPO3-projects, care for the wiki. version 1.1 - last update --Daniel Brüßler 18:07, 13 October 2006 (CEST)

Tasks:

  • Organization and ongoing maintenance of TYPO3 documentation
  • Care for single documents
    • Responsibility: documents what do not belong to other teams or projects (e.g. Glossary, Compatible Licenses)
    • Authority: Care for correct and up-to-date documents
  • Support for helpfull documentation (core, extensions, projects)
    • Responsibility: 1) Help other teams in the wiki to create new documents or projects really easy so that they can soon be published on typo3.org 2) Make bridges between wiki/ typo3.org and care for them
    • Authority: 1) Analyse what kind of help other teams need, communicate with them and built the needed tools. 2) Analyse what bridges are needed and create them in communication with the typo3.org-team

Delegated roles: Sebastian Kurfürst is the admin for the wiki-engine mediawiki, Elios is our hoster, the mediawiki-dev-team is caring for the wiki-features and the spam-filter. (Thanks all!)

Membership requirement: The will to care for people who need help, enough knowledge about TYPO3, time to do something and to talk about it, good english

Webpage URL: http://wiki.typo3.org/index.php/DocTeam

Mailing lists:

Wiki: http://wiki.typo3.org/index.php/DocTeam

[edit]

Extension Coordination

Leader: Elmar Hinz

Board: Jan-Hendrik Heuing

Parent node: Research & Development Committee

Missions: 1.) Winning and integration of new resources (ideas, code, people) into the TYPO3 community by making use of the possibilty to extend the core by components called extensions. 2.) Guiding extension development from 4.x to 5.x as smoothly as possible. 3.) Spreading TYPO3 by coordinating thrilling applications.

Targets:

  • Coordination of extensions with each other
  • Coordination of extensions and core
  • Integration of new ideas and concepts presented as extensions
  • Collection of new components (sources) as extensions
  • Integration of developers into the community
  • Incubating developers and ideas to establish independent project groups
  • Finding instruments to assure quality and usabiltiy of extensions
  • Advertising TYPO3 by providing valuable extensions
  • Integrating extensions that complement one anther to new products

Tasks:

  • Basical extension libraries
    • Developmenent of common libraries for extensions development
    • [Authority of execution]
  • Standards and best practice
    • Defining standards for the development of extensions for better integration and common look and feel
  • Preconfigured packages
    • Preconfigured packages for different areas of application
    • [Authority of execution]


Delegated roles: see Extension_coordination_team

Membership requirement: To become a member is simply done by taking up activities. Some people register on the wiki page, others come via NG, others are actively are approached by the project leaders. We define severel levels of activity.

  • Interested Party: People who are connected to a special project in some or other way. Maybe they have build an extension of that category, maybe they are interested users. There is some chance that they become active members. In the majority of cases they consult the active project members.
  • Candidtates: Registered people on the wiki page looking for an active role.
  • Members: People that have taken up an active role within ECT or one of the projects.

Webpage URL: not yet

Lists and Repositories:

Wiki: http://wiki.typo3.org/index.php/Extension_coordination_team

[edit]

Usability (HCI)

Leader: Kasper Skårhøj

Parent node: Research & Development Committee

Mission: In the short term, to define what "ease-of-use" (according to roadmap) for TYPO3 4.5 means in concrete suggestions through currently accepted usability methodologies. In the long term, to support and inspire all developers of core and extensions to implement userfriendly solutions.

Tasks:

  • 4.5 "ease-of-use"
    • Responsibility:
      • to define for the 4.x Core Team what "ease-of-use" (according to roadmap) for TYPO3 4.5 means in concrete suggestions through currently accepted usability methodologies.
      • to perform usability testing on the implemented solutions before final launch
    • Authority: Full, as long as roadmap is expected.
  • Usability support for 5.0
    • Responsibility:
      • to summarize the knowledge obtained about usability in version 4.5
      • to feed this knowledge and working solutions into the development of 5.0
    • Authority: Full authority to decide on usable solutions in 5.0
  • Embed usability awareness in developer culture
    • Responsibility:
      • to device a practical concept for how developers not primarily concerned with usability can implement solutions not too far off the mark.
    • Authority: to have this concept embedded into the official coding guidelines for core and extensions.

Delegated roles (optional): N/A

Membership requirement: At this point, the team is the HCI mailing list. Later (after the initial brainstorming), we will construct an actual team with long-term contributers taking ownership of the goals of the team. Requirements for membership will be some convincing perspective or expertice on the subject or some other relevant team role. Above all, a clear commitment to take assignments in the teams work is required.

Webpage URL: N/A

Mailing lists:

  • TYPO3-team-hci - TYPO3 human computer interaction team
    • Purpose: To gather brainstorm input for the usability team. To recruit people into the teams work. To allow the whole community a say on the subject.
    • Significance: The list inspires the HCI-team. There is no guarantee that suggestions will be accepted or even commented. However, its the first place to try and but them.
    • Access: Public.

Wiki: http://wiki.typo3.org/index.php/Human-Computer-Interaction

[edit]

Templates

[edit]

[Mission Statement Template]

Parent node: Research & Development Committee -- see Committees

Mission: [Insert description here]

Tasks:

  • [Task 1 title]
    • [Responsibility]
    • [Authority of execution]
  • [Task 1 title]
    • [Responsibility]
    • [Authority of execution]

Leader: [Name of team leader]

Delegated roles (optional):

  • [Role in team] - [Name of person]
  • [Role in team] - [Name of person]

Membership requirement: [Write how to become member if possible]

Webpage URL: [URL of TYPO3.org page or other website where team organizes itself]

Mailing lists:

  • [Mailing list name, purpose, significance, access criteria]
  • [Mailing list name, purpose, signifincance, access criteria]

Wiki: [Url to entry Wikipage, if any]

Retrieved from "http://wiki.typo3.org/index.php/Mission_Statements"
Personal tools
content
help 'N' beginners