Hi Fedora Infra Team,
I would like to request the creation of a new organization and associated teams in Fedora Forge.
Desired Organization Name (Short Name): deliverables
Full Name of Organization: Deliverables
Description of Organization's Purpose: This organization is responsible for keeping the inputs for Fedora image build tooling (such as https://pagure.io/fedora-kiwi-descriptions, https://pagure.io/fedora-kickstarts) and in the future the YAML input to image-builder.
image-builder
Website URL (Optional): N/A
Avatar/Logo (Optional): N/A
Fedora Accounts Group for Organization Owners: N/A
Team 1:
Target Organization Name: deliverables
Team Name: admins
Description of Team's Purpose: Core team responsible for repository management.
Desired Permission Level in Forgejo: Org Admin
Fedora Accounts to Team: ngompa, supakeen
Include all repositories?: Yes (This team should have write access to all current and future repositories in 'deliverables'.)
Please let me know if any further information is required.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: forgejo_migration, low-gain, low-trouble
I'm a bit confused about this.
aren't those going to be repos under releng org?
Why is this a seperate org?
CC: @jnsamyak @humaton
@kevin I don't know, it made sense to me but having it under releng also makes sense! @ngompa and me chatted about this on Matrix and we came up with this. Discoverability might be a bit better under a separate org and I don't think releng needs to (by default) tinker with definitions for deliverables very often? :)
Ultimately neither of us are part of releng and there's basically nobody from releng actively working on these repositories. So unless you want to add us to release engineering (with all the privileges that entails), I think a separate org makes sense.
nobody from releng actively working on these repositories
Uh... I surely do. You usually merge things before I can because you are in an eariler timezone, but I definitely work on them. Other releng folks definitely do also as needed.
I think it makes little sense to move these outside releng since they are used to make official deliverables.
I have no objection to adding you to the releng org. If that allows you to help out other places too, all the better... but of course you can just focus on these or whatever.
I guess I'd wait to hear from @jnsamyak for sure. I am also pretty sure releng folks are already working on migrating these... they just haven't gotten to them yet.
I'm fine with either option (adding to releng, or separate org), I like separate org more because separation of concern but maybe it makes the concern-box too small. Let's see what @jnsamyak and others think as well :)
Well, we can't migrate fedora-kiwi-descriptions because the new forge lacks CI support right now. So it's going to be a while.
fedora-kiwi-descriptions
I think a seperate org will confuse a lot of people who expect these things that are used to make official deliverables under releng... ;)
But yeah...
Also livesys-scripts needs somewhere to go...
livesys-scripts
IMHO, it sounds like you just need a deliverables team in the releng org. And we can give access to just these repos to that team.
The general members org in releng will still have access to it, as it has commit access to all repos.
I mean, to be honest, if that's how it goes, I would probably expect things like the pungi-fedora repository to also be governed by that team too.
I don't see why we need to silo these things out. This all seems like release engineering to me. I mean what does release engineering do if they don't manage whats released?
@kevin by "team" i mean team in the forge sense, which is just a acl group really.
so we would use that to give people access to the deliverables repos without having access to all the other releng stuff (if that is how fine grained they want to go)
Sure, I get that, but I don't know that we need to have that fine grained an access...
I'd rather finally get releng access than deal with this strange partitioned access thing. Partitioned access has been an annoying problem for years.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/infra/tickets/issues/12968
Please continue any further discussion there.
Metadata Update from @ryanlerch: - Issue close_status updated to: Migrated to Fedora Forge - Issue status updated to: Closed (was: Open)