Debian Health Check

Registered by Jorge O. Castro on 2011-10-04

The usual. :)

Blueprint information

Status:
Not started
Approver:
Jono Bacon
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Jorge O. Castro
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Review previous work-items from UDS-O
 - DDs having access to LP via their debian-keyring GPG keys for filing bugs. Bug was LP:#252368
 - LP build failures due to regexes on build logs. We should probably have a way to do this locally, maybe forward -Werror build flags for this?

Button to submit bugs to Debian?
Probably get pushback from Debian...
submittodebian is already not getting enough bug editorial.
Laney to pull lp bug descriptions in submittodebian

Forwarded bugs need to be linked back to LP. This requires waiting for a debbugs number. Can this be automated? Possibly via a address @launchpad that could receive bug filed email and do the link. This way, the mail filing the bug in Debian just needs to X-Debbugs-Cc: the launchpad address and include the launchpad bug number (in the address?) to let launchpad make the bug watch
Problem: authentication of the e-mail. DKIM on debbugs (and deployed on bugs.debian.org in particular)?

nhandler had a list of people who are active in both projects. Can we have a live version of this?
Activity can be defined simply as doing uploads.

ARB:
There are concerns about ARB, and how it changes distribution development.
This was accompianied with discussions on reducing the Ubuntu arcihve size. We can judge from removal complaints that people use and care about all the corners of the Ubuntu archive.
The concerns are that this could lose the opportunity of getting a packge into Debian. ARB charter states that these apps should be pushed towards Debian when possible.
One question about the packages that are forwarded to Debian, is how do we link these with people who can do the uploads in Debian and do sponsorship for this in the future.
One option is go to mentors, but it's demotivating to be passed around a lot. One also wouldn't want to affect the mentoring balance on -mentors.
We need to build a mentoring community, doesn't need to be Debian or Ubuntu specific. REVU may also be merged into debian-metors.
The pkgme messy packages probably aren't candidates for getting into Debian.
Package name conflicts: Because new packages only come into extras / software centre after release, the conflict with future releases is restricted to upgrades.

glib-gtk Unity patches may be forward-able to Debian. Not scrollbars (probably)

There are a couple of people in Debian interested in getting Unity in. Some of the parts require patches all over the place.
This should be better documented (e.g. an ITP blocked by other bugs).

There are places where Ubuntu needs to be a better upstream, if it really has an interest in having the software in other distributions. Packages which are in Debian, but very out of date.
Debian can have different requirements (e.g. non-linux ports), making this work harder.

(?)

Work Items

Work items:
[bryce] : DD LP access: TODO
[laney] : pull lp bug descriptions in submittodebian: TODO
[stefanor] : list of people who are active in both projects: DONE
[zack] : Talk to asheesh about the missing features from REVU: TODO