Simple but worthwhile to fix bugs?

[Daniel Holbach]

Hello everybody,

we recently had a quick conversation in #ubuntu-devel about how to get
new people involved in Ubuntu development. Ideally we'd offer something
like this:

 - Contributor finds good instructions.
 - Also a few simple things to work on, giving them a nice experience
   fixing things and they feel they accomplished something.
 - Their fixes get accepted quickly.
 - They progress to new and more exciting things.

So far the theory.

What we set up is

	https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative

and we have a few merge proposals in the sponsoring queue already.

While we tried to make it clear that Ubuntu-only fixes should go into
sponsoring and Debian package fixes should go to Debian, some ended up
in the queue, which sparked the discussion.

In an attempt to make things even clearer, I wrote an article for the
packaging guide, which I'd love to get feedback on:

 https://code.launchpad.net/~dholbach/ubuntu-packaging-guide/1045396/+merge/122552

Another question is: what kind of fixes do we want new contributors to
work on? How simple is too simple? Are we afraid of typo fixes piling up
in the queue?

My personal take on this is that we should be able to review them pretty
quickly and that "some additional work" is an effort we should
definitely put into this, to give new contributors a nice experience.

Feedback and suggestions very much appreciated.

Have a great day,
 Daniel

-- 
Get involved in Ubuntu development! developer.ubuntu.com/packaging
And follow @ubuntudev on identi.ca/twitter.com/facebook.com/gplus.to