Re: UbuntuStudio flavor status in jeopardy, action needed [Was, Re: [Ubuntu Studio] Cry For Help]

2019-03-15 Thread Mathieu Trudel-Lapierre
On Thu, Mar 7, 2019 at 1:02 PM Steve Langasek  wrote:
>
[...]
> > The packageset reports [1] already include all the information, too.
>
> > [1] http://people.canonical.com/~ubuntu-archive/packagesets/disco/
>
> To fully audit this requires answering a different question: is there at
> least one member of the development team for the flavor who is active and
> has upload rights to all the packages in the packageset?
>
> This might mean the members of the flavor team with upload rights are MOTU
> or core-dev rather than having PPU on the packageset.  And we can't rely on
> membership in the flavor development team being an indicator of current
> activity.
>

If we can report on the current members in the development team vs.
what their upload rights are (core-dev, MOTU, or the relevant team for
packageset upload) we'll already have some initial data to work with.

Then, we also do have some amounts of data to try to guess if a
particular developer is "active"... It's possible, it just becomes
computationally expensive (at least if you check -changes mailing list
against developers in the right development teams, etc.), for not a
ton more "certainty" on whether someone is active.

> Is this something you'd want to modify the DMB scripts to try to tackle, at
> least the parts that can be automated? (Probably not the bit where we have
> to confirm that uploaders are currently active and interested in continuing
> to be responsible for the flavor)

Sorry for the late response. I suggested it because I'm happy to write
a new script / modify the existing to get this data. I'll see to get
this working soon, so we have some data to work with before the disco
release.


Mathieu Trudel-Lapierre 
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B58DA1 818A D123 0992 275B 23C2  CF89 C67B B4D6 65B5 8DA1

-- 
technical-board mailing list
technical-board@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/technical-board


Re: Ubuntu Studio (and others) Flavor Status

2019-03-15 Thread Ross Gammon
Hi Steve,

On 13/03/2019 23:12, Steve Langasek wrote:
> There are over 400 source packages that are seeded on the Ubuntu Studio DVD
> but not on any other flavor images.[1]  Can you appreciate that it's
> important to ensure that these packages are well-maintained in Ubuntu if
> they are going to be part of an officially-recognized flavor?

Wow, I think anyone with a full time job would take years to get around
to touching every one of those packages in their spare time!

Personally, I agree that if a package is seeded in a flavour, it should
be in the package set (unless it is in main), and it should be possible
to "help" fix any of the flavour's packages.

As a Debian Developer or MOTU, you have the possibility of working on
many packages. For Debian there are very clear rules for working on a
package that you are not a maintainer of. In Ubuntu, there is no concept
of a maintainer. You are allowed to work on any package. However, there
is an accepted convention that you e.g. contact the previous uploader if
you are planning to attempt a merge (to avoid duplication of work, and
to find out if there are any known traps). It is also accepted that you
should follow up after an upload/sync to make sure it migrates from
-proposed, and if there is a transition involved - to follow through
with all the reverse dependencies.

Maybe there is a need to make sure those with upload rights to a package
set have the same awareness of their responsibilities as a MOTU? This
should include contacting other teams with the same package in their
package set. Maybe Simon's DMB action (tsimonq2 to better document what
we expect applicants to know) will help with this?

Anyway, many thanks for yours, and everyones help and time with this.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature
-- 
technical-board mailing list
technical-board@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/technical-board