← Back to team overview

launchpad-dev team mailing list archive

Re: RFC: either remove 'Ubuntu CoC signing required' for PPA use, or enforce it consistently

 

On 12 February 2012 00:09, Robert Collins <robertc@xxxxxxxxxxxxxxxxx> wrote:
> At the moment, we require the Ubuntu CoC to be signed to create and
> use a PPA as an individual. As a member of a team, there is no such
> requirement.
>
> (Note that private PPAs w/commercial entitlements are arguably
> different, so I'm not talking about them at all here).
>
> I believe jml has in the past said that the CoC requirement wasn't all
> that useful - it occurs to me that we can make LP PPA's easier to get
> going with if we drop it entirely; if we are not willing to do that,
> then I think we really have to fix the use-via-team hole, or we'll be
> tangling ourselves up in knots to justify keeping this
> partial-enforced rule.
>
> Any strong objections or concerns any which way?

As PPAs are effectively an Ubuntu feature provided by Launchpad, I
think we consult the CC.

My memory of the reason for requiring signing the CoC was to aim to
have software in PPAs that was created in the same spirit of the
Ubuntu project generally. We should talk, particularly with the Ubuntu
community, about whether requiring a CoC sign is an effective way of
doing that or if we need some other agreement. I guess I'm involving
the Community Council by CCing Laura.

I'll put my cards on the table and say that my preference is for
closing the team-member hole and having a separate PPA agreement.
Obviously that depends on an agreement system that can track more than
just the one CoC.

-- 
Matthew Revell
Launchpad Product Manager
Canonical

https://launchpad.net/~matthew.revell


Follow ups

References