Ubuntu Server papercuts project overview

Thierry Carrez thierry.carrez at ubuntu.com
Tue Jan 19 10:56:15 GMT 2010


Robert Freeman-Day wrote:
> Unless I am missing some feature of launchpad, I think the project
> option may be better.  There is a simple URL to remember as well as the
> ability to join the project team.  When/If one joins, it will show up on
> a user's home page for gurther easy access.  I just now had some trouble
> attempting to find the tags on a reported bug, for they are not
> obviously places in the reports.
> 
> I do not see anywhere (like I said, I may be missing out on a feature)
> the ability to "subscribe" to tags.

Thanks very much for your feedback, and based on it (and others) we
decided during the meeting to follow the project route.

Project is at: https://launchpad.net/server-papercuts
Bug supervisor team is: https://launchpad.net/~server-papercutters

> My two cents, not as a developer, but one who wishes to assist in bug
> triage/resolution.

Please feel free to apply to the server-papercutters team !

Next meeting (Wednesday at 1400 UTC) we'll discuss the nomination
criteria. What makes an acceptable Server papercut ? What bugs should
this effort concentrate on fixing ?

My initial take on this was that we should concentrate on easy-to-fix
server experience issues. I have identified the following categories:

* Out-of-the-box readiness (bad default configs, package requiring
manual steps to go from installed to running)
* Teamplay (packages not working well together, while making sense to be
used together)
* Smooth operation (anything requiring tedious or repetitive manual work)
* Missing documentation (missing man pages, missing inline comments in
default configs)
* Upgrade issues (init scripts failures blowing up maintainer scripts)
* Cruft (broken symlinks, residue of purge)
* Consistency (upstartification ?)

Anything missing from the list ?

I would define "easy to fix" by (1) having an obvious fix and (2)
requiring less than 2 hours of work.

A few examples of what would *not* make server papercuts:
* Making the right software to install easier to find on servers: good
idea, but project is too large
* Upgrade X to version Y: we should improve existing packages rather
than adding new features
* Make file sharing work in all cases: too vague, no obvious fix

Time permitting, we'll also discuss the timing and contents of the
project publicity plan. Please join us at the meeting if you're
interested, or reply to this thread if you unfortunately can't join us
this time !

-- 
Thierry Carrez
Ubuntu server team



More information about the ubuntu-server mailing list