Kubuntu Policies (for council consideration)

Harald Sitter apachelogger at ubuntu.com
Wed Mar 5 17:57:45 UTC 2014

On Wed, Mar 5, 2014 at 6:06 PM, Jonathan Riddell <jr at jriddell.org> wrote:
> I still strongly disagree, I think we should have a stepping stone to
> being able to upload to the Ubuntu archive and we should give people
> access where they have shown they are competant and know their own
> limits.  In the case of Scarlett (sorry to use you as an example)
> she's rapidly learning the important points of library packaging so I
> hope to not have to review her changes soon and just let her upload to
> the PPA.  Currently she has to wait around until I find time to review
> which blocks her and takes time from me.  How would you handle her
> situation under your proposal?

Let's repurpose kubuntu-ninjas the way it is practically used.

~kubuntu-ninjas becomes member of ~kubuntu-packagers and ~kubuntu-ppa.
~kubuntu-dev becomes admin of ~kubuntu-ninjas.

Process for joining ninjas is a mail to the list asking to become
ninja, as soon as 2 devs vouge for the candidate they may ascend to
ninjahood gaining access to all our PPAs and the packaging branches.

It doesn't really resolve my reservations about taking away the
mandatory review process, but as long as ~kubuntu-dev and
~kubuntu-council feel this is an acceptable approach to pragmatic
packaging, I am happy.

This would however mean that someone who is not member, not dev, and
cannot be accepted by dev (e.g. someone who is being brought in for
testing), cannot join the private PPA. So, if that is something we
want to do, an alternate approach would be to introduce a new group
~kubuntu-acolytes which is member of -ninjas, -packagers, -ppa.


More information about the kubuntu-devel mailing list