KnowledgeBase
Differences between revisions 61 and 178 (spanning 117 versions)
|
Size: 7854
Comment:
|
← Revision 178 as of 2019-12-10 22:29:10 ⇥
Size: 16
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(ServerTeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(1)>>|| Here are some ressources to help you get things done. If you have any questions, don't hesitate to [[ServerTeam/Contact|contact]] other ServerTeam members. = Bug Triager resources = Triaging bugs in Launchpad is coordinated with the BugSquad team: * BugSquad/KnowledgeBase has valuable information on how to work with bugs in Launchpad. * [[Bugs/Responses]] has a list of standard responses for different categories of bugs. * Ask for help on the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad|ubuntu-bugsquad mailing list]] and #ubuntu-bugs on irc.freenode.org. * The launchpad [[http://launchpad.net/people/ubuntu-server|ubuntu-server]] team is the bug contact for many server-related packages, so if you become a member of the team you'll get email traffic related to those bugs. Avoid assigning or subscribing {{{ubuntu-server}}} for packages {{{ubuntu-server}}} is already a bug contact for. * [[https://bugs.launchpad.net/~ubuntu-server|bugs assigned to the Ubuntu Server Team]]. * [[https://bugs.launchpad.net/~ubuntu-server/+packagebugs|summary report of bugs by package]]. All the bugs related to the ubuntu-server team LP are sent to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs|ubuntu-server-bugs mailing list]]. * Use the mentoring feature of Launchpad to mark bugs that should be easy to fix. We don't have a specific bug workflow. = Packager resources = For packaging information, head to the [[MOTU|MOTUs, the Master Of The Universe]]. * There is the [[PackagingGuide]]. * [[PackagingGuide/Lists/DocumentationResources]] and [[MOTU/School]] have information related to packaging. * [[UbuntuDevelopers]] explains how to become an official packager. * [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu|ubuntu-motu mailing list]] and #ubuntu-motu on irc.freenode.org are good places to ask for help. We're focusing on server related packages in main and universe. = Server support resources = The server team offers support for server-related questions in #ubuntu-server. * The [[https://wiki.ubuntu.com/UbuntuBots|ubotu]] irc bot makes it easy to share an extensive set of [[http://ubotu.ubuntu-nl.org/factoids.cgi|factoids]] to others in an irc channel. E.g. typing {{{!ask | noobie}}} will cause ubotu to tell noobie that folks should just go ahead and ask their questions. Ubotu can also conveniently show the channel information on bugs and packages. See [[https://wiki.ubuntu.com/UbuntuBots|ubotu]] for more details. = Tester resources = We coordinate our testing plans in the [[Testing/Server|Server testing section]] of the [[Testing|Testing project]]. New test plans should be defined as new pages below [[Testing/Server]]. Example: Testing/Server/My''''''Test''''''Plan. === ISO testing === Ubuntu Server iso testing follows the process described in [[Testing/ISO]]. We focus on testing the ubuntu-server isos. The [[https://iso.qa.stgraber.org/|Iso testing tracker]] is used to track test results. You can register with the iso testing tracker and subscribe to the ubuntu server testcases so that you'll be notified whenever a new ubuntu-server iso needs to be tested. = Documentor resources = This area is involved with updating and creating new content for the [[http://doc.ubuntu.com/ubuntu/serverguide/C/index.html|Ubuntu Server Guide]] and the [[https://help.ubuntu.com/community/|community help website]]. We're working with the DocumentationTeam and focus on server related topics. <<Anchor(serverguide)>> == Ubuntu Server Guide == The current development version of the Ubuntu Server Guide is located in [[https://code.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-intrepid|a bazaar branch]] (lp:ubuntu-doc) hosted on Launchpad. There is also [[http://doc.ubuntu.com/ubuntu/serverguide/C/index.html|an html version]] available online. Here are the steps to modify the Ubuntu Server Guide and ask the DocumentationTeam to review your changes: * Create a directory where you'll put your local working version of the Ubuntu Server Guide: {{{ $ bzr init-repo --trees --format=dirstate-with-subtree ubuntu-bzr $ cd ubuntu-doc/}}} * Get the ubuntu-doc files that have the latest version of the Ubuntu Server Guide: {{{ $ bzr branch lp:ubuntu-doc $ cd ubuntu-doc/}}} NB: that command can take some time as the whole history of the branch has to be downloaded from Launchpad. * Update the Ubuntu Server Guide files using your favorite editor. They can be found in the {{{serverguide/C/}}} directory. * Once your changes are complete, commit them: {{{ $ bzr ci }}} And send them to the ubuntu-doc mailing lists with the bzr send command: {{{ $ bzr send --mail-to=ubuntu-doc@lists.ubuntu.com }}} == Community wiki == * The [[https://help.ubuntu.com/community/WikiGuide|WikiGuide]] has guidelines for contributing to the help website. * If help is needed, the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-doc|ubuntu-doc mailing list]] and #ubuntu-doc on irc.freenode.net are good places to ask around. The Ubuntu Team wiki, at [[https://wiki.ubuntu.com/]], is focused on documentation for Ubuntu community contributors rather than for end users = Developer resources = The [[https://wiki.ubuntu.com/|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 [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel|ubuntu-devel mailing list]] and #ubuntu-devel on irc.freenode.net are the places where ubuntu developers can be found. = Team policy = === Membership === The Membership policy is described in [[ServerTeam/Membership|Membership]]. === Reporting === The ServerTeam has a section in the [[TeamReport| monthly report]]. We try to get status reports on a weekly basis on the day preceding the IRC meeting. The [[ServerTeam/ReportingPage| ReportingPage]] is used to gather the outcome of the tasks done by the ServerTeam members during the week. The montly report is a subpage under [[ServerTeam/ReportingPage]]. It's a summary from the Meeting minutes and the "a Month in the archive" post. The subpage is automatically included in the [[TeamReport| monthly team report]] with the following macro: {{{ === Server Team === <<Include(ServerTeam/ReportingPage/2008-06, ,from="## ReportStart", to="## ReportEnd")>> }}} Don't forget to change the month in the include macro link when starting a new montly report. === IRC meeting === We hold IRC meeting regularly to report about current tasks and define new ones. The [[ServerTeam/Meeting| Meeting]] page presents the Agenda for the next meeting. [[ScribesTeam/MootBot|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. 1. Create a new entry in [[MeetingLogs/Server]]/YYYYMMDD with the [[ServerTeamMeetingLogTemplate]]. a. Move the agenda from [[ServerTeam/Meeting]] to agenda section. a. Copy the irc logs to the Irc log section. a. Write the minutes. 1. Update [[ServerTeam/Header]] to announce the next meeting date. 1. Send the minutes on the ubuntu-server and ubuntu-devel mailing lists. Publish the minutes on the [[http://ubuntuserver.wordpress.com|ubuntuserver blog]]. [[http://bazaar.launchpad.net/~mathiaz/+junk/ubuntuserver-minutes/files|A script]] has been written to automate this step. ---- CategoryServerTeam |
See ServerTeam |
See ServerTeam
ServerTeam/KnowledgeBase (last edited 2019-12-10 22:29:10 by powersj)