<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style> </head> <body> <meta content="text/html; charset=UTF-8"> <style type="text/css" style="">  </style> <div dir="ltr"> <div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif"> Nish, I am for a bug squash day. I would like to be on rotation as well of triaging bugs. How can I do so? Tammy </div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr">From: ubuntu-server-bounces@lists.ubuntu.com <ubuntu-server-bounces@lists.ubuntu.com> on behalf of Nish Aravamudan <nish.aravamudan@canonical.com> Sent: Friday, March 10, 2017 2:09:32 PM To: ubuntu-server Subject: Ubuntu Server Bug Squashing Day (monthly) <div> </div> </div> </div> <div class="PlainText">Along the same lines as Robie's recent post to ubuntu-devel for a sponsorship queue squashing party: <a href="https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039714.html">https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039714.html</a> ... I am proposing a monthly Server Bug Squashing Day. Have you ever been interested in wanting to help make Ubuntu Server better but been stymied by not being sure where to start? I am proposing a once-a-month IRC (FreeNode/#ubuntu-server) event that hopefully will help encourage contributions to Ubuntu for server-related bugs and demystify the Ubuntu package development process. Our tentative first Ubuntu Server Bug Squashing Day will be March 22, 2017. I will send a reminder the preceding Monday in confirmation. Ideally, if you are interested in contributing, you would take a look at the following two queries on bugs to which ~ubuntu-server is subscribed (some overlap, probably): bitesize (implying small changes are needed): <a href="https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server&field.tag=bitesize+">https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server&field.tag=bitesize+</a> server-next (implying these are the next set of bugs to look at for the Server Team): <a href="https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server&field.tag=server-next+">https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server&field.tag=server-next+</a> When I ran these queries, they had 24 and 20 bugs respectively, which is pretty manageable. The overall ubuntu-server backlog, though, is up to 405!: <a href="https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server">https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-server</a> And since there is now a daily rotation of Server Team members doing triage, that number is only going to go up. It does not feel possible for just Server Team members to get us even to a steady-state And that's where Server Bug Squashing Day comes in! I do not expect it to be very rigidly structured, and we will learn what works as we go, but bring a bug you'd like to help resolve (again, ideally from the list above, as it will mean someone from the Server Team has already looked at it) and we'll talk about how to generate the debdiff, how to build a package, how to test it and any other development-related issues that might come up. Once you've been mentored in fixing one or two bugs, I think it is certainly possible you will be able to go and look at packages you are interested in and do some real good! And of course, the Server Team will be a resource on Bug Squashing Day and otherwise to help! -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-server">https://lists.ubuntu.com/mailman/listinfo/ubuntu-server</a> More info: <a href="https://wiki.ubuntu.com/ServerTeam">https://wiki.ubuntu.com/ServerTeam</a> </div> </body> </html>