GettingInvolved

What can I do to help ?

There are different areas where you can help the Ubuntu Server Team.

If you don't really know how to get started, you can join the Ubuntu Server Team mentoring program.

Help on the mailing list and the IRC channel

You can lend a hand with people's questions and problems on the mailing list and the IRC channel.

To get started:

  1. subscribe to ubuntu-server mailing list.

  2. join the channel #ubuntu-server on the Freenode IRC.
  3. answer questions from users

Triage bugs and become a Triager

The goal is to move bug that are in a NEW status to a CONFIRMED or INVALID status.

To get started:

  1. Choose a bug from the New,Unconfirmed bug list and subscribe to it.

  2. Work with the user to identify the issue using the INCOMPLETE status.
  3. Once the bug is reproducible and the process to reproduce it is clearly documented in the bug thread set the status to CONFIRMED. If it turns out that there isn't any bug set the status to INVALID.
  4. You can unsubscribe from the bug as your role as a bug triager is finished.
  5. Read more bug triaging ressources:

You should also subscribe to the ubuntu-server-bugs mailing list where all the bugs are sent. You can also view the list of bugs related to the ServerTeam and help triaging them.

Have a look at the Triager roadmap for specific tasks you can help on.

Improve packages and become a Packager

You can have a look at the list of packages looked after by the Ubuntu Server Team to see if some needs packaging work.

This is a excellent way to gain experience to become a MOTU.

Have a look at the Packager roadmap for specific tasks you can help on.

Add apport hooks into key Ubuntu Server packages

These are the Ubuntu Server packages selected to have apport hooks installed with. Please sign up to create the apport hook.

To create an apport hook, start reading here.

  • Please attach a debdiff to the launchpad bug.
  • Please use the Notes column to add comments to the package.

Package

Assignee

LP Bug

Status

Notes

Samba

ChuckShort

Complete

OpenSSH

ChuckShort

Complete

PHP5

ChuckShort

Complete

DHCP3

ChuckShort

Complete

ntp

ChuckShort

Complete

Apache

bind

RoAkSoAx

533601

Waiting Sponsorship

openldap

eucalyptus

ChuckShort

Complete

lp:~zulcss/ubuntu/lucid/eucayptus/eucalyptus-apport

euca2tools

vmbuilder

ChuckShort

Complete

rsyslog

clamav

dovecot

net-snmp

RoAkSoAx

533603

Waiting Sponsorship

nut

openvpn

spamassasin

vsftpd

RoAkSoAx

531978

Complete

Participate in testing plans and become a Tester

If you have server-type hardware, you can make sure that Ubuntu is supported and works well on it. You can also test software and features worked on by the Ubuntu Server Team.

Have a look at the Tester roadmap for specific tasks you can help on.

Maintain documentation and become a Documentor

You can head to the community documentation to check that server related pages are up to date or help to get the Ubuntu Server Team wiki pages into shape. You can also help with the Ubuntu Server Guide, the official Server documentation.

Have a look at the Documentor roadmap for specific tasks you can help on.

Verify Stable Release Update Fixes

Whenever we fix a bug in past stable releases, we need somebody who is not the developer making the fix to verify that the package fixes and doesn't cause any obvious regressions. It is vital that we have people test these updates before they are sent to all users.

The full process for doing so is here:

QATeam/PerformingSRUVerification

Here is the list of server bugs needing verification.

How to become an member of the Ubuntu Server Team

Policy

Membership lasts for one year, and is renewable. If not renewed the member will join the former member list.

Users that have applied for membership and have not met the criteria within a 2 month period will have their application declined.

Requirements

The following criteria have to be met by all team members:

  • Subscription to the ubuntu-server mailing list.

Process to apply for membership

Becoming a member of the Ubuntu Server Team is really easy:

Mentoring

Are you interested in joining the ServerTeam and contribute to Ubuntu ? Don't know where to get started ? The mentors of the ServerTeam are here to help you make your first contribution to Ubuntu.

This program is lightweight and short in time. You'll get a mentor from the ServerTeam and together:

  1. discuss your areas of interest.
  2. define a simple task to accomplish.
  3. get your contribution integrated in Ubuntu !

Interested ? Send an email to <ubuntu-server AT SPAMFREE lists DOT ubuntu DOT com> introducing yourself and we'll take it from there.

Mentor guidelines

The mentor provides guidance during the whole process by:

  • presenting existing procedures.
  • pointing to existing communication channels (#ubuntu-server, ubuntu-server mailing list, other IRC channels and mailing lists).
  • linking to key members of the ServerTeam and Ubuntu in general.

  • sponsoring one upload if the contribution is packaging related.
  • giving feedback to the applicant in a timely manner.

Once the task has been accepted in Ubuntu, the contributor should have been in contact with the rest of the ServerTeam and should know where to ask questions.

Process to approve a new member

  • Check that the member is subscribed to ubuntu-server mailing list.
    • If the applicant is subscribed, approve the member in launchpad. The approval should be sent with the following comment:
      Welcome to the Ubuntu Server Team - https://wiki.ubuntu.com/ServerTeam!
      
      We're looking forward to working with you. There are many ways you can help us: the GettingInvolved wiki page lists areas where you can contribute (https://wiki.ubuntu.com/ServerTeam/GettingInvolved).
      
      You can also have a look at our Roadmap to see what we're working on now and pick a specific task to contribute to (https://wiki.ubuntu.com/ServerTeam/Roadmap).
      
      If you're interested in bug triaging, you should subscribe to the ubuntu-server-bugs@lists.ubuntu.com mailing list - https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs.
      
      Thanks and welcome aboard !
      
      The Ubuntu Server Team.
    • If the applicant is not subscribed and email address is available from LP, send a invitation using the preferred email address in Launchpad to subscribe to the ubuntu-server mailing list with the following message:
      Hello,
      
      Thank you for your interest in the Ubuntu Server Team on Launchpad. Membership requires a subscription to the ubuntu-server mailing list. Please confirm your subscription and we will happily approve you.
      
      Thank you.
      
      The Ubuntu Server Team.
    • If the applicant is not subscribed and email address is not available from LP, contact the user via LP to subscribe to the ubuntu-server mailing list with the following message:
      ubuntu-server membership application
      Hello,
      
      Thank you for your interest in the Ubuntu Server Team on Launchpad. Membership requires a subscription to the ubuntu-server mailing list. 
      
      You can subscribe to the mailing list here: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
      
      Thank you.
      
      The Ubuntu Server Team.
    • If the application is declined, put the following message as a comment:
      Hello,
      
      Thank you for your interest in the Ubuntu Server Team on Launchpad. We're sorry to decline your application as you haven't met the criteria to become a member.
      
      The Membership policy is outlined here: https://wiki.ubuntu.com/ServerTeam/Membership. 
      
      You can reapply for membership whenever you want by following the process described here: https://wiki.ubuntu.com/ServerTeam/GettingInvolved#becomemember.
      
      Thank you,
      
      The Ubuntu Server Team.

Ubuntu Server Task Forces

What are Ubuntu Server task forces ?

Ubuntu Server task forces are subgroups of the Ubuntu Server community, formed by specialists of a specific area. Becoming an Ubuntu Server developer is often seen as a daunting task, due to the breadth of packages and knowledge areas that it covers. However, lots of people are specialists of a specific server area, and such specialists should be able to gather to drive the integration and maintenance of that specific area, since they know better than anyone else. We already have a few of those groups around: formalizing and publicizing a governance model around those groups should encourage the creation of more of them.

Official Task Force List

(no team has applied to be considered a task force yet)

Task Force Processes

Creation of Task Forces

The task force should be founded as a Launchpad group. It should consist of more than one person. Its team description should include a mission statement, the list of packages covered, and a link to at least one blueprint/spec with plans for the current (or next) development cycle. A single person should be the administrator of the group, and that person will be considered the primary point of contact. When the group is ready to apply to be a formal task force, it should add its application as a topic for the next Ubuntu Server IRC team meeting. Application will be reviewed during that meeting, and if accepted by the Ubuntu Server team engineering manager, the task force will be listed on this page.

Task Force Rights

The Task force can shape the future state of the packages that are part of it. Its members define the design and implementation details of the blueprints/specs around those packages. The specs are reviewed by the Server engineering manager and accepted or denied for the current development cycle, like for any other spec.

Upload rights are not directly linked to task force participation: they are reviewed and granted by the Developer Membership Board. However, being part of a task force that cares about a particular package set is obviously recommended to get said upload rights to it Smile :)

Task force members will be encouraged to participate to Ubuntu Developer Summits, and the sponsorship process should try to favor them whenever possible.

Task Force Duties

The Task force primary point of contact should participate to the weekly Ubuntu Server Team IRC meeting, and report progress on their spec(s) if requested. He is responsible for making sure the status of the Task force specs is regularly updated, so that it's easy for anyone to follow what they are up to. It should raise any significant policy decision in an ubuntu-server and/or ubuntu-devel mailing-list thread to give the rest of the community of chance of commenting.

The Task force must come up with at least one blueprint for each development cycle, detailing the plan(s) for the group during that cycle. That plan does not have to be ambitious every time, it just needs to exist so that the rest of the Ubuntu Community knows what the Task force is up to for that cycle. If the Task force repeatedly fails to deliver on its duties, the Ubuntu Server engineering manager may discuss and decide its dissolution during a weekly IRC meeting.


CategoryServerTeam

ServerTeam/GettingInvolved (last edited 2012-08-11 15:09:44 by petermatulis)