Goal: To successfully review every bug filed against Ubuntu Server related packages
A review involves analyzing a bug to determine if the bug is valid and if sufficient information was provided. If the bug is both valid and provided with sufficient information, the bug is marked as triaged and will be worked to closure by a member of the server team. Otherwise, the bug will be responded to and marked as 'Incomplete' for more details, 'Invalid' for not a real bug, or 'Won't Fix'.
Daily Bug Triaging
Bug triage is completed for all bugs last updated on a particular day. An assigned member of the server team will look at all bugs that were updated on the previous day. For example, the member with responsibility on Friday will review all the bugs updated on Thursday. For the weekend, the member with responsibility on Monday will review all the bugs updated on Friday, Saturday, and Sunday.
This process is expected to take less than 30 minutes per day. This is not meant to be a full root cause analysis (RCA) investigative time, instead only determining if further attention is warranted and sufficient information has been provided.
Current members of Ubuntu Server bug triage:
Assignment of daily bug triage is completed as an agenda item of the server team's IRC meeting.
Helpful Guides and Definitions:
Developer & Packaging Resources
We are focusing on server related packages in main and universe. Developers can use the Triaged Ubuntu Server bugs list to prioritize their work.
For packaging information, head to the MOTUs, the Master Of The Universe.
There is the PackagingGuide.
UbuntuDevelopers explains how to become an official packager.
ubuntu-motu mailing list and #ubuntu-motu on irc.freenode.org are good places to ask for help.
For Ubuntu release specific resources, the Ubuntu Team wiki is the central location where Ubuntu developers exchange ideas and track their progress.
UbuntuDevelopment gives an overview of the development processes.
The ubuntu-devel mailing list and #ubuntu-devel on irc.freenode.net are the places where ubuntu developers can be found.
The server team utilizes IRC to offer support for server-related questions. The team sits on freenode in the #ubuntu-server channel.
The ubottu IRC bot makes it easy to share an extensive set of factoids to others in an IRC channel. E.g. typing !ask | noobie will cause ubottu to tell noobie that folks should just go ahead and ask their questions. Ubottu can also conveniently show the channel information on bugs and packages. See ubottu for more details.
The Membership policy is described in Membership.
The ServerTeam has a section in the monthly report. We try to get status reports on a weekly basis on the day preceding the IRC meeting. The ReportingPage is used to gather the outcome of the tasks done by the ServerTeam members during the week.
The monthly report is a subpage under ServerTeam/ReportingPage. It's a summary from the Meeting minutes and the "a Month in the archive" post.
We hold IRC meeting regularly to report about current tasks and define new ones. The Meeting page presents the Agenda for the next meeting.
MootBot can be used to record the meeting.
irclogs are available on http://irclogs.ubuntu.com/.
Publishing the Minutes
Once the meeting is over, minutes are prepared to summarized the outcome of the meeting.
Move the agenda from ServerTeam/Meeting to agenda section.
Copy in the IRC logs from the "Minutes" link at the end of the meeting. This can be found on http://ubottu.com/meetingology/logs/ubuntu-meeting/
- Updated the minutes section with a summary of each section. You can template to work from using the IRC minutes you found the IRC logs from. Then fill in each section with your summary.
Update ServerTeam/Header to announce the next meeting date.
Update the Agenda for the next meeting at ServerTeam/Meeting
- In particular, remove completed ACTIONS, add new ones
- Update the list of Chair/Scribes
- move yourself to the back
- send an email to the person who will chair next week