kubuntu-devel Digest, Vol 145, Issue 6

[Paul Loughman]

I have no problem with restricting who can make commits. It’s a no brainer. Why would anyone who isn’t either a packager (with demonstrated experience) or a developer (with peer reviewed acceptance) be allowed to commit?

Paul Loughman
snowhg at icloud.com




> On Jan 13, 2017, at 6:00 AM, kubuntu-devel-request at lists.ubuntu.com wrote:
> 
> Send kubuntu-devel mailing list submissions to
> 	kubuntu-devel at lists.ubuntu.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
> or, via email, send a message with subject or body 'help' to
> 	kubuntu-devel-request at lists.ubuntu.com
> 
> You can reach the person managing the list at
> 	kubuntu-devel-owner at lists.ubuntu.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kubuntu-devel digest..."
> Today's Topics:
> 
>   1. Re: Change in policy for Kubuntu Members (Valorie Zimmerman)
> 
> From: Valorie Zimmerman <valorie.zimmerman at gmail.com>
> Subject: Re: Change in policy for Kubuntu Members
> Date: January 12, 2017 at 5:06:33 PM CST
> To: Kubuntu Developer Discussion <kubuntu-devel at lists.ubuntu.com>
> Reply-To: Kubuntu Developer Discussion <kubuntu-devel at lists.ubuntu.com>
> 
> 
> True that. On the other hand, we have a lot of powerful tools these
> days, and a mistake can cause a lot of time and trouble to clean up.
> In KDE, the permissions have always been wide-open for anybody with a
> devel status too. And yet all but the smallest of commits are now
> subject to review.
> 
> I think that we are pretty liberal at handing out ninja status still.
> 
> Valorie
> 
> On Thu, Jan 12, 2017 at 1:00 AM, Harald Sitter <sitter at kde.org> wrote:
>> Members having access to all venues of contribution was not a result
>> of legacy, it was a conscious decision made at the time we introduced
>> source code version control. We found that we trust all members to act
>> in the best interest of the project and work towards the same goal.
>> 
>> It is truly a sad day that members of Kubuntu cannot be trusted
>> anymore. I always looked with fondness at the fact that membership
>> actually meant something more than been-around-long-enough.
>> 
>> :(
>> 
>> On Thu, Jan 12, 2017 at 12:16 AM, Valorie Zimmerman
>> <valorie.zimmerman at gmail.com> wrote:
>>> In the early days of Kubuntu, all the Kubuntu Members were packagers
>>> and developers. Since the community has grown, we now have some
>>> Kubuntu Members who are not packagers, developers or coders. Yet one
>>> of the privileges of Kubuntu Membership has long been the right to
>>> commit changes to our packaging and packages.
>>> 
>>> The Kubuntu Council, after extensive discussion which you can read in
>>> the archives of our list on our Launchpad page [1], has updated our
>>> Kubuntu Policies [2] and Launchpad.
>>> 
>>> Since packagers and developers are already members of the teams which
>>> have the permissions to commit, change or upload as needed, this
>>> should have no effect on Kubuntu Members, but it will improve the
>>> security of our code and packages on LP.
>>> 
>>> Valorie, for the Kubuntu Council
>>> 
>>> 1. https://launchpad.net/~kubuntu-council
>>> 2. https://community.kde.org/Kubuntu/Policies
>>> 
>>> --
>>> http://about.me/valoriez
>>> 
>>> --
>>> kubuntu-devel mailing list
>>> kubuntu-devel at lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>> 
>> --
>> kubuntu-devel mailing list
>> kubuntu-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
> 
> 
> 
> -- 
> http://about.me/valoriez
> 
> 
> 
> 
> -- 
> kubuntu-devel mailing list
> kubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kubuntu-devel/attachments/20170113/11cfa7ca/attachment.html>