ServerTeam

Differences between revisions 11 and 60 (spanning 49 versions)
⇤ ← Revision 11 as of 2006-04-14 00:36:14 →
Size: 1749
Editor: 140
Comment: rewrite, remove UDU spec
← Revision 60 as of 2022-02-10 14:05:02 → ⇥
Size: 6900
Editor: paelzer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Ubuntu Server Team == = Ubuntu Server Team =
Line 3: Line 3:
The [http://launchpad.net/people/ubuntu-server Ubuntu Server team], under the able stewardship of Fabio "I'm going to make him an offer he can't refuse" Massimo di Nitto, is working to make Ubuntu Server the best Linux server platform on the market. <<Include(ServerTeam/Header)>>
Line 5: Line 5:
This means working on simplifying the system administrator's life, while focusing on advanced features, rock-solid stability, and high performance. We want Ubuntu Server to be an attractive platform for the entire range of servers -- from makeshift, converted desktop machines, to carrier-grade server hardware. While our install CD already comes with an option to install a LAMP server, thus satisfying the most common use case, we're working on incorporating clustering and virtualization technologies for the higher end, and are developing software for simplified management of many Ubuntu servers. ~+The [[http://launchpad.net/people/ubuntu-server|Ubuntu Server team]] works to enable and promote the use of Ubuntu Server, the number one cloud OS.+~
Line 7: Line 7:
We specifically focus on three key areas:
Line 8: Line 9:
== Joining the team ==  1. Providing a robust and stable infrastructure for scale-out computing deployments.
 2. Supporting the latest scale-out computing workloads and architectures.
 3. Providing the right tools for orchestrating services within a scale-out computing environment.
Line 10: Line 13:
Thanks for your interest. We look for a history of sustained contribution to Ubuntu Server in potential new team members -- luckily, it's easy to get involved. == Communication ==
Line 12: Line 15:
Join the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-server mailing list] or hop onto IRC (#ubuntu-server on FreeNode) and lend a hand with people's questions and problems. Grab the latest [http://cdimage.ubuntu.com/ubuntu-server/daily/ ubuntu-server daily release] and test it, posting your results and feedback to the list. Submit some patches for outstanding bugs we have, or help shape the future of Ubuntu Server by writing up some detailed specifications for desired functionality here on the wiki, and registering them with Launchpad. If you want to contact the ServerTeam use the following resources:
Line 14: Line 17:
Your efforts won't go unnoticed, and we're looking forward to having you on board soon! === Mailing List ===
Line 16: Line 19:
Join our mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-server.

You can read an archive of messages at https://lists.ubuntu.com/archives/ubuntu-server/.

=== IRC ===

The server team utilizes IRC to offer support for server-related questions. The team sits on freenode in the #ubuntu-server channel.

The [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] IRC bot makes it easy to share an extensive set of [[http://ubottu.com/factoids.cgi|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 [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] for more details.

== Getting Involved ==

There are different areas where you can help the Ubuntu Server Team. Here are a few ideas:

=== Help on Mailing List & IRC ===

You can lend a hand with people's questions and problems on the above mailing list and the IRC channel. Ask and answer questions, provide suggestions, and provide input in our periodic calls for input.

=== Test, Test, Test ===

If you have server-type hardware or can spin up VMs and containers, 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.

=== Improve Documentation ===

You can head to the [[https://help.ubuntu.com/community/|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 [[https://ubuntu.com/server/docs|help with the Ubuntu Server Guide]], the official Server documentation.

=== Verify SRUs ===

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 [[http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs|list of server bugs needing verification]].

=== Triage Bugs ===

The goal of triage is to move bugs that are in a NEW status to a CONFIRMED or INVALID status.

To get started:
 1. Choose a bug from [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|the New,Unconfirmed bug list]] and subscribe to it.
 1. Work with the user to identify the issue using the INCOMPLETE status.
 1. 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.
 1. You can unsubscribe from the bug as your role as a bug triager is finished.
 1. Read more bug triaging resources:
    * [[BugSquad/KnowledgeBase]]
You should also subscribe to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs|ubuntu-server-bugs mailing list]] where all the bugs are sent. You can also view the [[https://bugs.launchpad.net/~ubuntu-server/|list of bugs related to the ServerTeam]] and help triaging them.

=== Improve Packages ===

You can have a look at the [[https://bugs.launchpad.net/~ubuntu-server/+packagebugs|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]].

== Ubuntu Server Bug Triage ==

'''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'. In certain (rare) cases bugs might stay in new/confirmed which reflects we need to look into it again more deeply to triage in a better way.

This is a list of the various queues of interest to the server team. They are a good place to go if you are looking for a good "what to do next" bug.

{{{#!wiki comment
contact davidpbritton if you want these bit.ly vanity links modified
}}}
 * [[http://bit.ly/ubuntu-server-next|Top 20 Bugs ("server-next")]]
 * [[http://bit.ly/ubuntu-server-bitesize|Bite-sized Bugs]]
 * [[http://bit.ly/ubuntu-server-recent|Recently modified Bugs]]
 * [[https://bugs.launchpad.net/~ubuntu-server/+subscribedbugs|Full Backlog]]

For Details about the process have a look at The [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/BugTriage.md|Ubuntu Maintainers handbook]].

=== Additional Resources ===

Helpful Guides and Definitions:

 * [[Bugs/Importance|Definitions for bug importance levels]]
 * [[Bugs/Status|Definitions for bug status settings]]
 * [[DebuggingServer|Server specific triage responses]]
 * [[Bugs/Responses|Additional predefined response templates]]

== Ubuntu Server Packaging ==

We are transitioning to a [[UbuntuDevelopment/Merging/GitWorkflow|git-based workflow]] for handling package changes. This also allows us to use Launchpad Merge Proposals and request Reviews before publishing a new package version.

For details about this please have a look at [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/MergeProposal.md|Merge Proposals]] and [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md|Package Merges]] in the Ubuntu maintainers handbook.
Line 18: Line 108:
[[CategoryServerTeam]]<<BR>>

Ubuntu Server Team

The Ubuntu Server team works to enable and promote the use of Ubuntu Server, the number one cloud OS.

We specifically focus on three key areas:

  1. Providing a robust and stable infrastructure for scale-out computing deployments.
  2. Supporting the latest scale-out computing workloads and architectures.
  3. Providing the right tools for orchestrating services within a scale-out computing environment.

Communication

If you want to contact the ServerTeam use the following resources:

Mailing List

Join our mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-server.

You can read an archive of messages at https://lists.ubuntu.com/archives/ubuntu-server/.

IRC

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.

Getting Involved

There are different areas where you can help the Ubuntu Server Team. Here are a few ideas:

Help on Mailing List & IRC

You can lend a hand with people's questions and problems on the above mailing list and the IRC channel. Ask and answer questions, provide suggestions, and provide input in our periodic calls for input.

Test, Test, Test

If you have server-type hardware or can spin up VMs and containers, 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.

Improve Documentation

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.

Verify SRUs

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.

Triage Bugs

The goal of triage is to move bugs 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 resources:

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.

Improve Packages

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.

Ubuntu Server Bug Triage

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'. In certain (rare) cases bugs might stay in new/confirmed which reflects we need to look into it again more deeply to triage in a better way.

This is a list of the various queues of interest to the server team. They are a good place to go if you are looking for a good "what to do next" bug.

For Details about the process have a look at The Ubuntu Maintainers handbook.

Additional Resources

Helpful Guides and Definitions:

Ubuntu Server Packaging

We are transitioning to a git-based workflow for handling package changes. This also allows us to use Launchpad Merge Proposals and request Reviews before publishing a new package version.

For details about this please have a look at Merge Proposals and Package Merges in the Ubuntu maintainers handbook.

CategoryServerTeam
CategoryUbuntuTeams

ServerTeam (last edited 2022-02-10 14:05:02 by paelzer)