kubuntu-council team mailing list archive

[Valorie Zimmerman <valorie-zimmerman@xxxxxxxxxxx>]

On Mon, Nov 14, 2016 at 2:57 AM, Clive Johnston <clivejo@xxxxxxxxx> wrote:
> Sounds reasonable.  As Rik Mills is now a Kubuntu Member and has a good grasp
> of how it works, are you all OK if I add him?

+1 from me to adding Rik to the KCI admins

> I will give him a brief overview (basically as much as I know) into how it
> works and its operation.
>
> Clive
>
> On Monday, 14 November 2016 10:15:45 GMT you wrote:
>> Actually, historically the decision who had access to river was pretty
>> much up to Harald back when the Server was only accessible by Blue
>> Systems people. After he passed maintainership on to us, we never
>> actually decided what the rules for getting access are. Scarlett got it
>> as she was helping to keep it running, and I got it to fix a couple
>> things, we just happened to already be devs. IMO the kubuntu CI admins
>> should be able to follow a bit of a self-governance and decide on their
>> own who gets access.
>>
>> I would personallly impose a kubuntu membership requirement for all
>> people with access, as having access to river gives access to the CI PGP
>> and SSH keys, which someone could use to make git commits under the name
>> of the CI (I don't think all keys have a password for practical reasons).
>>
>> Exceptions can, as usual, be made with approval of the KC.
>>
>>
>> Philip
>>
>> Am 13.11.2016 um 13:18 schrieb Aaron Honeycutt:
>> > Historically it has only been Kubuntu Developers and as such Simon can
>> > not be given it. Walter (wxl) has come up with a plan to ask the other
>> > KDs if they don't mind uploading a few packages at a time after they
>> > have been tested well and repeatedly.
>> >
>> >
>> > On Sun, Nov 13, 2016, 6:00 AM Clive Johnston <clivejo@xxxxxxxxx
>> >
>> > <mailto:clivejo@xxxxxxxxx>> wrote:
>> >     Hi folks,
>> >
>> >     As far as I know, the KCI master (river) is only accessible by
>> >     people with
>> >     kubuntu-devel membership.  However, that basically means that only
>> >     Phillip and
>> >     myself currently have access.  With me stepping down and Phillip
>> >     not as active
>> >     as he once was, this could be problematic for the remaining team.
>> >
>> >     This became very apparent with the announcement of a zero day exploit
>> >     affecting Jenkins.  Luckily I was in the KDE Neon channel when
>> >     Scarlett
>> >     announced it and after contacting her, I was able to patch the
>> >     system using
>> >     her instructions.
>> >
>> >     Anyway, back to my question.  Simon Quigley has requested that he
>> >     have access
>> >     to the machine. I have told him that I don't have the authority to
>> >     do that.
>> >     But it does open the question.
>> >
>> >     Can the KC please advice on what to do?
>> >
>> >     Thanks,
>> >     Clive