Tags:
governance1Add my vote for this tag task_team1Add my vote for this tag create new tag
, view all tags

Task Team Examples

Here are some outlines of task team goals an powers to help you when writing your own.

TWiki Content team

Goals

  • ensure that TWiki has an attractive "web presence" designed to draw in users and potential contributors.
  • Redesign the main pages of TWiki.org.
  • Ensure t.o content is regularly audited to meet expectations of independence, fairness, equality, truth, justice and the Armorican way.

Powers modify any page on TWiki.org. Priority service from T.O admin team to help make it happen. Use comms channels (such as existing t.o and mailing lists) to advertise the activity and draw in contributors).

Recognition contributors and commercial sponsors will be identified as the "TWiki Web Presence Team" in a prominently-linked page on the finished site. Launch communications, issued through the Press Relations task team, will include links as appropriate.

Timeframe chartered until end 2008

TWiki 5.0 planning

Goals

  • write a TWiki 5.0 roadmap that (1) reflects the twiki mission (2) reflects the requirements of the open-source community (3) is achievable and timeframed. The roadmap does not have to be detailed, and may not be adhered to 100%, but should as far as possible reflect community requirements for TWiki.

Powers use community mailing lists to gather inputs

Timeframe chartered until end October 2008

TWiki 4.2.3 patch release

Goals

  • integrate and test TWiki 4.2.3 patch release
  • Ensure unit and interactive tests are completed.
  • Complete release checklist.
  • Communicate release availability (press release).

Powers final say over releasability. Reject checkins if necessary. Generate press release on behalf of twiki.org

Timeframe chartered until end December 2008 or 4.2.3 release, whichever is earlier

Contributor sharing environment cleanup

Goals

  • improve the environment for better initial experience for new contributors
  • provide taxonomy and search tools in Codev to create a better experience for new and returning contributors.

Powers delete topics from Codev. Mark topics as obsolete. Refactor anything. Move subsets of content to new areas (e.g. webs) or sites (eg d.t.o)

Timeframe chartered until end November 2008

D.T.O admin team

Goals

  • provide admin support for develop.twiki.org
  • ensure service availability for Bugs web and subversion repository.
  • Ensure all standard admin expectations (backup, security etc) are fulfilled.
  • Audit registered users and ensure that spammers are dealt with quickly and effectively.

Powers root access to d.t.o. Login (non-root) to t.o (to support mirrored data). Recognition as the "d.t.o admin team" prominent on d.t.o and t.o. Solicit funding on behalf of TWiki to support mirror sites (subject to published constraints on recognising sponsors). Remove spam and legally infringing content.

Timeframe chartered until 31st January 2009

T.O. admin team

Goals

  • provide admin support for develop.twiki.org
  • ensure service availability for twiki.org. Ensure all standard admin expectations (backup, security etc) are fulfilled.
  • Audit registered users and ensure that spammers are dealt with quickly and effectively.

Powers root access to t.o. Recognition as the "t.o admin team" prominent on t.o. Solicit sponsorship on behalf of TWiki to support mirror sites (subject to published constraints on recognising sponsors). Remove spam and legally infringing content. Ban vandals.

Timeframe chartered until 31st January 2009

Press relations

Goals

  • Communicate with the press on behalf of the open-source community
  • ensure broad, balanced and unbiased communication of significant events in the TWiki project.
  • Raise the profile of TWiki among technology commentators, including bloggers and the tech press.
  • Maintain commercial independence.

Powers all press communications will be channelled through this team, which must sign off on content.

Timeframe active up to and including TWiki 5.0 release

Test monitoring team

  • Proposer and team leader: QuisCustodiet
  • Team members: IpsosCustodes
Goals
  • provide regular feedback on test status of the twiki trunk and active release branch
  • ensure daily runs of unit testcases and automatic result reporting to developer mailing lists.
  • Ensure tests on at least Debian/Linux.
  • Run tests as many platforms as practical.
Powers
  • mail lists, and individual community members, in the event of failures.
  • Obtain sponsorship on behalf of TWiki for the maintenance and support of test platforms.

Timeframe chartered until 31st March 2009

TWiki user conference

  • Proposer and team leader: BillyGates
  • Team members: JonnyShirley, StevieBallmer
Goals
  • The conference team will organise a TWiki user conference
  • The conference will be somewhere in Europe
  • The team will use commercial sponsorship to raise funds to support this work
Powers
  • The team will be able to use the TWiki name to raise sponsorship funds
  • The TWiki users mailing list may be used by the team for announcements, including requests for funds
  • The team will have unlimited rights to modify twiki.org content to support the conference
  • Commercial sponsors will be granted the right to use the TWiki name and logo in promotional materials, as long as it's linked to the conference
  • The team will have final say over all advertising materials.
  • This charter expires 31 September 2009

Multiple teams working on the same task

An important aspect of the system is that in a highly active community, there is scope for two or more task teams to work to address the same problem. All you have to do is specify their rights and responsibilities appropriately. Here's a charter for one of two task teams working on a store module:
  • The DB Store task team 1 will design and code a database store
  • The work may or may not be selected for inclusion in future TWiki releases. Task team 2 is also working on an alternative implementation.
  • The work will be based on a branch of TWiki 5.X.X
  • The team will have it's own web on twiki.org (and bug database on d.t.o) for management and discussion of its work
  • If the work may require modification of the TWiki core. If so, all unit tests will be maintained and all documents updated.
  • 100% compatibility with old TWiki data and templates will be maintained.
  • This charter expires on the 20th December 2009
  • The team will deliver benchmark results and user experience stories for evaluation by the BoD, who will take the final decision
  • Sponsor X has committed a prize of $2M for the best implementation. It is up to the successful team how this is shared.
  • If their solution is selected, the team commits to merge its work with the trunk
  • Team members will have the final say on any advertising or marketing materials generated referring to their work
Task team 2 would work to an almost identical charter.
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2008-09-10 - CrawfordCurrie
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.