Steps to improve the Server Team community

Registered by Mathias Gug on 2009-04-30

What can we do to improve the Server Team profile within the Ubuntu community and in the OSS at large? How can we get more contributor started?

Different roles for community members, need to define the tasks to cover for each role. Need to come up with metrics in order to measure progress and reward them. Need to come up with a way to publish small tasks for each roles to help get started. Need to come up with a way to collect these small tasks from other team members.

Help in documentating each tasks: how to get started, what to do, how to do it, where to find new work to be done, how to report successful completion, skills required, example of one task, tools required, who to contact, how to get help.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

=================
Discussion from UDS karmic

= Improving the Server Community =

Different roles for community members, need to define the tasks to cover for each role. Need to come up with metrics in order to measure progress, reward them. Help in documentating each tasks: how to get started, what to do, how to do it, where to find new work to be done, how to report successful completion, skills required, example of one task, tools required, who to contact, how to get help.

Bug reporter: open/file new bugs.
 * Track new bugs opened.
 * How often they follow up.
  * Bugs reported that are not *incomplete*.
 * Categorize reporters by which package the bug is reported on.

Bug triager: triage bugs, make comments, link upstream bugs.
 * Amount of bugs triaged.
 * Goal is to move bugs from new to triaged.
  * Try to reproduce bugs yourself
  * Ask about how to reproduce.
  * Document 'test case' for recreating the bug.
 * Link to upstream bugs.
 * Top bug triagers for each package.
 * TODO list.
 * Focus on a package for a week.
  * Engage entire bug community as well.
  * Enables specific things for new members.
  * Blog the package of the week.
  * Send a mail to the list about the package.
 * Identify new comers, and prioritize them.
  * Help commit patches, etc.
 * TODO list

Packager: pkg uploads, bug in progress/closing, provide patch, sponsor patch/pkg, review patch, find upstream/other distro patches, send patches to upstream.
 * patching oriented
 * weekly reports on blog - top uploader, top sponsor, top bug resolver?

Documentator: bzr commits, patches, ml activity, wiki editing, wiki page creation.

Support: ml, irc, forums.

Translator: pkg/software translation.

Tester: conduct test plans and report their result (iso testing).

Developer: participate in design decision/feature definition, implement features.

Evangelist, megaphone operator: talk about new features implemented, specific events, specific achievments by other members, report of ubuntu status in upstream communities, rely what needs to be done, call for testing. Send minutes.

Community manager: run meeting, gather reports, member achievement and activities to reward them.

 * Blogging
  * Working fine.

 * Server Forum
  * Not very engaging.
     * Ask about how to reproduce.
 * Samba bug day.
  * Good outcome.
  * Bug triaging
  * More people looking at Samba bugs.

 * IRC Channel
  * Some rudeness creeping in.
  * More experienced community members should keep an eye on it.

 * Good to have team members blog what they are working on.

 * List of easy things to do for new developers.

=================

(?)

Work Items