BugSquashingDay

Differences between revisions 2 and 4 (spanning 2 versions)
⇤ ← Revision 2 as of 2017-04-24 23:13:07 →
Size: 3282
Editor: nacc
Comment:
← Revision 4 as of 2017-04-25 05:42:12 → ⇥
Size: 3898
Editor: paelzer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(ServerTeam/Header)>>
<<BR>>
<<BR>>
Line 3: Line 6:
Have you ever been interested in wanting to help make Ubuntu Server better
but been stymied by not being sure where to start?		 Have you ever been interested in wanting to help make Ubuntu Server better but been stymied by not being sure where to start?
Line 6: Line 8:
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.		 We will hold a twice-a-month IRC (FreeNode/#ubuntu-server) event that hopefully will help encourage contributions to Ubuntu for server-related bugs and demystify the [[https://wiki.ubuntu.com/UbuntuDevelopment|Ubuntu package development]] and [[https://wiki.ubuntu.com/StableReleaseUpdates|Ubuntu Stable Release update]] process.
Line 12: Line 10:
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):		 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):
Line 16: Line 12:
[[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+ | bitesize]] (implying small changes are needed)  * [[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+ | bitesize]] (implying small changes are needed)
Line 18: Line 14:
[[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+ | server-next]] (implying these are the next set of bugs to look at for
the Server Team)		  * [[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+ | server-next]] (implying these are the next set of bugs to look at for the Server Team)
Line 21: Line 16:
When I ran these queries, they had 24 and 20 bugs respectively, which
is pretty manageable.		 When I ran these queries, they had 24 and 20 bugs respectively, which is pretty manageable.
Line 26: Line 20:
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 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
Line 32: Line 24:
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		 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
Line 39: Line 27:
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!		 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!

This isn't school, but anyone that wants to prepare or just start on your own to then come to the event with questions out of your work we encourage to read through some good starting documentation at:
 * [[http://packaging.ubuntu.com/|Ubuntu Packaging Guide]]
 * [[https://wiki.ubuntu.com/SponsorshipProcess|Ubuntu Sponsorship Process]]
 * [[https://wiki.ubuntu.com/ProposedMigration|Ubuntu Proposed Migration]]
 * [[https://wiki.ubuntu.com/StableReleaseUpdates|Ubuntu Stable Release Updates]]
 * [[https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow|Git Based Workflow]]



Along the same lines as Robie's recent post to ubuntu-devel for a sponsorship queue squashing party, nacc proposed a monthly Server Bug Squashing Day. (This has been since updated to bi-monthly).

Have you ever been interested in wanting to help make Ubuntu Server better but been stymied by not being sure where to start?

We will hold a twice-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 and Ubuntu Stable Release update process.

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)

  • server-next (implying these are the next set of bugs to look at for the Server Team)

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!

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!

This isn't school, but anyone that wants to prepare or just start on your own to then come to the event with questions out of your work we encourage to read through some good starting documentation at:

ServerTeam/BugSquashingDay (last edited 2017-04-25 05:42:12 by paelzer)