[00:37:08] 10GitLab: Gerritlab - https://phabricator.wikimedia.org/T300819 (10TheDJ) [00:50:54] 10GitLab, 10Release-Engineering-Team: Gerritlab - https://phabricator.wikimedia.org/T300819 (10brennen) [07:43:57] 10GitLab, 10Release-Engineering-Team: Gerritlab - https://phabricator.wikimedia.org/T300819 (10Aklapper) [16:40:04] brennen: thanks for creating the sre group, I alwso wanted to ask if there is any advice/convension on how to sub organise this group. i.e. $team/{debs,software,tools,operations}/$project vs $team/$project vs .... [16:42:26] jbond: my feeling is that project groups should model broad functional areas rather than team structure [16:42:49] we really haven't established conventions or strong guidelines, though. [16:43:30] thcipriani might have some thoughts. [16:47:44] it's early days, but I can say where gerrit went wrong with naming. there are two dimmensions: teams and code. Gerrit for sre folks was pretty much just "ldap" -- I'm not sure how that worked internally, but maybe that's fine? What I think aged less well is "operations/*" the top-level namespace I don't think served much of a functional purpose other than grouping permissions (which is no [16:47:46] longer necessary in gitlab) and it didn't age well: "operations" is ~"hr" now and what was "operations" is now "sre" so I'm +1 for projects not fitting under "$team/project" vs "f$unction/project" [16:48:29] I also think that "$function" == "$team" often and that's fine. We'll undoubtedly make new mistakes here :) [16:49:53] (this is a long way of saying exactly what brennen said :)) [17:00:13] ack thanks and yes i think in this case sre ~= team|function. however im now wondering if what i was orignally thinking of should go under sre and think of sre more of a project what i was originally thnking of make senses... [17:00:44] what i was originally loking at is storing some patches to a debian package. in gerrit theses would gi in to operations/debs/foobar [17:01:41] so i was thinking of creating a sre/debs/foobar but perhaps something like {packaging,debs,debian}/foobar (i.e. a new dedicate root repo) may make more senses [17:03:19] or releng/debs ? [17:03:53] * jbond mutteres There are only two hard things in Computer Science.... [17:32:38] jbond: figuring out a successful naming scheme should account for a pay raise [17:56:57] most of the options above strike me as pretty reasonable [17:57:12] i guess maybe we should decide how granular we want to get with top-level groups [17:57:52] not having to manage access _too_ much is probably a good thing to think about [17:58:40] so maybe {broad area of concern}/debs/foobar? {broad area of concern}/packaging/foobar? [18:26:30] ack thanks brennen [22:51:49] 10GitLab (Project Migration), 10Release-Engineering-Team (Doing), 10User-brennen: Create new GitLab project group: Generated Data Platform - https://phabricator.wikimedia.org/T296381 (10brennen) > Could you help me understand how repos and people namespaces differ from each other operationally? Groups in `/... [23:05:39] 10GitLab (Project Migration), 10Release-Engineering-Team (Doing), 10User-brennen: Create new GitLab project group: Generated Data Platform - https://phabricator.wikimedia.org/T296381 (10brennen) 05In progress→03Resolved I went ahead and transferred the project, which seems to work for admins: https://git... [23:15:45] 10GitLab (Auth & Access), 10Release-Engineering-Team, 10User-brennen: Investigate what's required to allow a user to fork or transfer a project to a group - https://phabricator.wikimedia.org/T300935 (10brennen) [23:16:01] 10GitLab (Auth & Access), 10Release-Engineering-Team, 10User-brennen: Investigate what's required to allow a user to fork or transfer a project to a group - https://phabricator.wikimedia.org/T300935 (10brennen) p:05Triage→03Medium [23:43:51] 10GitLab, 10Release-Engineering-Team, 10Upstream, 10User-brennen: GitLab group permissions are not inherited by sub-groups for groups of users invited to the parent repo - https://phabricator.wikimedia.org/T300939 (10brennen) [23:44:34] 10GitLab (Project Migration), 10Release-Engineering-Team (Done by Wed 24 Nov 🧟), 10User-brennen, 10cloud-services-team (Kanban): Create top level 'cloud' group on Gitlab - https://phabricator.wikimedia.org/T293741 (10brennen) 05In progress→03Resolved > I'll need to dig into this a bit more. Filed T300...