Getting involved in ubuntu (was Re: metapackages)

Dennis Kaarsemaker dennis at kaarsemaker.net
Tue Sep 27 01:50:56 CDT 2005


On di, 2005-09-27 at 11:54 +1000, Taryn East wrote:
> * Dennis Kaarsemaker <dennis at kaarsemaker.net> spake thus:
> > Same for getting involved with ubuntu, which is where ubuntu-devel comes
> > in. A not-so-experienced programmer or even a seasoned one getting
> > started on ubuntu-specifics needs to be given an easy route.
> 
> being one of said programmers I figured I should take this opportunity
> to leap into this conversation and say: what sort of stuff do you need
> to get involved in ubuntu development?
>
> Apart, of course, from joining this list...

Programming knowledge is useful if you want to develop software. If you
want to help out by fixing a few bugs or helping with packaging,
documentation like the debian new maintainer guide is a must-read.

> mostly the wiki seems to describe stuff that goes beyond "just getting
> started" - such as becoming a memberi/official maintainer.
> 
> The "how to contribute" page points you vaguely at MOTU, which then
> points to MaintainerCandidates which mentions something about Launchpad
> (without explaining what launchpad is, but it seems to take you to the
> dedicated ubuntu-dev team which seems more than I'm able to do right now).

Every contribution is welcome :) Launchpad is launchpad.net, a (imho really 
cool) collaboration framework.

> It also seems to be a bit circular as it states that:
> "In order to become a maintainer, you must first be a member of the
> Ubuntu project."
> but to become a member... you have to have contributed to projects
> right?  which means you need to become a maintainer...

The trick here is: You can help out the MOTU by fixing bugs, without
being a member. They'll do the uploads for you. Once you've shown
quality packaging/fixing/programming for a sustained time you can become
a member.

> Also, it seems to be a bit more on the extreme side than I am ready to
> put myself forward for atm - I'm not ready to own a whole package... I
> don't have specific interests yet, just interested in contributing a
> little - when I have time to do so, and to start with on some fairly
> basic stuff. Maybe a few easy bugs, working up to something more
> serious... then eventually submitting the bigger stuff and maintaining
> packages.

Ubuntu does not have 'package owners'. Everybody can relatively freely
work on everything. Bug fixers are very welcome at the MOTU, there's so
much work to do there that every little contribution counts.

> I guess for me the issue lies in the fact that I've never really
> contributed much to OSS at all - and this is my starting point.
> 
> Do you guys support this approach? If so - may I ask for a clear idea of
> how? :)

Of course we support starting OSS developers :) Think a bit about how
much time you want to spend and what you like to do most (coding,
bufixing, documentation, artwork, support) and just get involved :)
-- 
Dennis K.
  - Linux for human beings: http://www.ubuntulinux.org
  - Linux voor normale mensen: http://www.ubuntulinux.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.ubuntu.com/archives/ubuntu-devel/attachments/20050927/5b8b96d9/attachment-0001.pgp


More information about the ubuntu-devel mailing list