/srv/irclogs.ubuntu.com/2019/02/25/#ubuntu-meeting.txt

=== cpaelzer__ is now known as cpaelzer
=== cpaelzer__ is now known as cpaelzer
slashdo/18:57
tsimonq2Hello!19:02
slashddo we have something to discuss ?19:05
cyphermoxI don't know19:06
cyphermoxfwiw my action is done19:06
tsimonq2We do19:06
tsimonq2Granting ~lubuntu-dev upload permissions.19:07
cyphermoxtsimonq2: I'm not sure why ~lubuntu-countil is in the team, sounds like it shouldn't be19:08
tsimonq2cyphermox: It's a temporary measure.19:08
cyphermoxI don't see why it needs to be in at all19:08
cyphermoxit's definitely not going to work with having ~lubuntu-dev upload permissions19:09
tsimonq2gilir is the owner of the LP group and ~lubuntu-council is in the team at the moment for bus factor.19:10
cyphermoxI still don't understand19:10
cyphermoxgilir owning the team isn't necessarily a blocker. If he can't be reached, there's a way to request the ownership to be changed19:10
cyphermoxOTOH, I don't think it's necessarily a given that a council member is also a developer19:11
cyphermox(certainly doesn't seem to be the case for other flavours)19:11
tsimonq2It was not planned to keep it this way if upload permissions were granted19:11
tsimonq2It's a temporary stopgap measure before ownership is transferred19:12
cyphermoxwell, I guess the point is, I would personally prefer that the teams are all properly set before we do any permissions changes (well, before the TB does)19:12
cyphermoxno objection to lubuntu-dev being a delegated team though, that makes total sense19:12
tsimonq2Well, I would like to vote on it :)19:13
tsimonq2I understand19:13
cyphermoxwell, do we need to is also my question, because if we're all in agreement there is no real use in voting :)19:13
tsimonq2I don't want to act unilaterally before giving DMB members time to voice any concerns19:14
cyphermoxsure sure.19:14
cyphermoxso, anyone objects?19:14
cyphermoxtsimonq2: also, since ~l-council is admin, can't it change the ownership already?19:15
cyphermoxor are you waiting for a council meeting before you do that?19:16
tsimonq2Nope, only owners can transfer ownership19:16
cyphermoxtsimonq2: or launchpad admins, if you make your case19:16
tsimonq2Right19:16
tsimonq2I forget if I have to file an RT or if I can just ping on #launchpad19:16
jbichavoting sounds reasonable. It's been several years since we've had a new delegated team with ability to ability their own members.19:17
cyphermoxit's usually a good idea to file the RT so it's tracked19:17
tsimonq2Right, audit logs and such19:17
tsimonq2jbicha: I don't think it would hurt19:18
cyphermoxjbicha: we've already reached the point where the time effect is moot, but typically if there's consensus, voting is extra19:18
tsimonq2ok19:18
cyphermoxthe logs aren't any different, they're just text19:18
cyphermoxwell, if someone wants to start it..19:18
tsimonq2[ACTION] tsimonq2 to file RT transferring ownership of ~lubuntu-dev, deactivate ~lubuntu-council, ask TB to do ACL change19:19
tsimonq2:P19:19
jbichaI don't think we started a meeting…19:20
cyphermox#startmeeting Developer Membership Board19:23
meetingologyMeeting started Mon Feb 25 19:23:28 2019 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:23
meetingologyAvailable commands: action commands idea info link nick19:23
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | Developer Membership Board Meeting | Current topic:
cyphermox#topic ~lubuntu-dev delegated team19:23
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | Developer Membership Board Meeting | Current topic: ~lubuntu-dev delegated team
cyphermoxtsimonq2: you want to summarize for the logs?19:23
cyphermoxthen I'll start the vote19:24
cyphermoxslashd: around?19:24
tsimonq2Sure.19:24
cyphermoxrbasak isn't19:24
slashdcyphermox, yep19:24
jbichaoh, we're voting after all?19:24
cyphermoxwell since you all seem to need it :P19:24
jbichaI wasn't going to call us for us to have a vote on whether to have a vote đŸ˜‰19:25
tsimonq2https://lists.ubuntu.com/archives/devel-permissions/2019-February/001319.html - tl;dr Lubuntu is asking for ~lubuntu-dev to be granted upload permissions to the `lubuntu` packageset.19:25
tsimonq2:D19:25
cyphermoxtsimonq2: sounds like a great summary :)19:25
cyphermox#vote ~lubuntu-dev to be granted delegated control over lubuntu packageset (new delegated team)19:25
meetingologyPlease vote on: ~lubuntu-dev to be granted delegated control over lubuntu packageset (new delegated team)19:25
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)19:25
tsimonq2+119:26
meetingology+1 received from tsimonq219:26
cyphermox+119:26
meetingology+1 received from cyphermox19:26
jbicha+119:26
meetingology+1 received from jbicha19:26
slashd+119:26
meetingology+1 received from slashd19:26
cyphermoxno sil2100 either19:27
cyphermoxand no micahg.19:27
cyphermox#endvote19:27
meetingologyVoting ended on: ~lubuntu-dev to be granted delegated control over lubuntu packageset (new delegated team)19:27
meetingologyVotes for:4 Votes against:0 Abstentions:019:27
meetingologyMotion carried19:27
cyphermoxthat was quorate anyway19:28
cyphermoxnow; one issue is that I'm not sure if we're supposed to decide if we can delegate directly, or if it needs to be approved or something19:28
cyphermoxbut I suppose, tsimonq2, if you're going to be the person bringing it up to the TB, it can be part of the discussion if there's any needed19:29
cyphermoxI'll definitely be at the next TB meeting anyway19:29
tsimonq2The original proposal I outlined was to create a new team, ~lubuntu-dev-owner, which has the DMB and ~lubuntu-council, and allow that team to approve/deny members.19:29
cyphermoxyup19:30
tsimonq2cyphermox: Is that something we decide or the TB does?19:30
cyphermoxlike kubuntu, basically19:30
tsimonq2Right.19:30
cyphermoxwell, TB ultimately is responsible for granting access rights to developers, they delegate that to us19:30
cyphermoxbut it sounds exactly like what Kubuntu does, and seems like it's perfectly fine for lubuntu to do that as well19:31
cyphermoxso you probably just need to finish sorting out the ownership of the teams and you'll be all set19:31
tsimonq2Cool.19:31
tsimonq2Do we have a wiki page somewhere for formally requesting that the TB edit ACLs?19:32
tsimonq2(Or just generally some documentation I can follow.)19:32
tsimonq2"The name 'lubuntu-dev-owner' has been blocked by the Launchpad administrators. Contact Launchpad Support if you want to use this name." - heh, ok, so it'll have to be with one big ticket.19:33
tsimonq2(To answer my own question: https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Actions_after_a_successful_applications )19:33
cyphermoxoh, looky19:33
cyphermoxthat actually also covers delegation19:34
cyphermoxwe should be looking at a policy for how the applications will be managed19:34
tsimonq2[ACTION] tsimonq2 to file RT transferring ownership of ~lubuntu-dev, deactivate ~lubuntu-council, ask TB to do ACL change19:36
meetingologyACTION: tsimonq2 to file RT transferring ownership of ~lubuntu-dev, deactivate ~lubuntu-council, ask TB to do ACL change19:36
cyphermoxtsimonq2: we should really go over such a "policy" on the applications for lubuntu, but we can do that at a later meeting I guess?19:37
cyphermoxthat way you could write down something in the wiki like the one for the DesktopTeam; what you expect to see for an applicant, etc.19:37
tsimonq2https://phab.lubuntu.me/w/lubuntu-dev/19:38
tsimonq2I wrote that when I sent the email to devel-permissions.19:38
tsimonq2It's a more complete page which I'd like to generalize for Ubuntu Developers that shows everything I would expect a Lubuntu Developer to know, plus the application process.19:39
cyphermoxnice19:40
tsimonq2So where I'm still curious is whether that's a process that the TB or the DMB approves.19:40
cyphermoxthe knowledgebase page says it's us19:42
tsimonq2Alright, so the vote earlier was to grant the team the packageset permissions, I guess we need a separate vote for the process?19:42
cyphermoxslashd: jbicha: any issues with the aforementioned document?19:42
cyphermoxor do you want to vote on it?19:43
jbichaI don't think we need a second vote19:43
tsimonq2For the record: ~lubuntu-dev changed to self-renewal, 720 day expiry period, ~ubuntu-core-dev was already a member, added ~lubuntu-dev to ~ubuntu-dev.19:44
cyphermoxack19:45
tsimonq2Oh, and ~lubuntu-council deactivated prior to doing all of that.19:45
tsimonq2Something else I noticed when adding ~lubuntu-dev to ~ubuntu-dev; ~ubuntu-sru-developers is the only team with an expiry date. Should that be changed to "expire never"?19:47
cyphermoxtsimonq2: you mean in ~ubuntu-dev?19:47
tsimonq2Yes.19:47
cyphermoxpossibly19:47
cyphermox#topic AOB?19:48
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | Developer Membership Board Meeting | Current topic: AOB?
cyphermoxoh19:48
cyphermoxok, I already did end the voting19:48
tsimonq2https://launchpad.net/~ubuntu-dev/+member/ubuntu-sru-developers vs https://launchpad.net/~ubuntu-dev/+member/kubuntu-dev19:48
cyphermoxanything else?19:48
cyphermoxtsimonq2: I agree.19:48
tsimonq2I'll make that change then.19:49
tsimonq2Nothing else from me.19:49
cyphermoxslashd: jbicha19:49
slashdcyphermox, nothing else on my side19:49
jbichanothing from me :)19:50
cyphermoxok19:50
cyphermox#endmeeting19:50
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice
meetingologyMeeting ended Mon Feb 25 19:50:20 2019 UTC.19:50
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-02-25-19.23.moin.txt19:50
cyphermoxthanks everyone!19:50
tsimonq2Thanks!19:50
jbichabye19:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!