Get teams.fp.o to allow access to projects at a default level for anyone with a FAS #7826

Closed
opened 2019-05-23 10:16:26 +00:00 by bex · 22 comments

This will require consultation with our teams.fp.o hoster.

This will require consultation with our teams.fp.o hoster.

Can you explain a bit more about your request and the thinking behind it?

I'm concerned that this would create confusion between individual boards/projects vs Fedora approved(for lack of better term) ones.

Can you explain a bit more about your request and the thinking behind it? I'm concerned that this would create confusion between individual boards/projects vs Fedora approved(for lack of better term) ones.
Author

I do not view teams.fedoraproject.org as a place to host individual non-Fedora related boards. The teams really need a way to get people on-boarded that doesn't require constant manual maintenance. The default in almost all areas of our project is open commenting. We need this here too, in my opinion.

I do not view teams.fedoraproject.org as a place to host individual non-Fedora related boards. The teams really need a way to get people on-boarded that doesn't require constant manual maintenance. The default in almost all areas of our project is open commenting. We need this here too, in my opinion.

Right now, the Taiga OIDC plugin doesn't even request group membership information.
While that bit is easy to solve, it would then also need hooking up to the taiga internals for some kind of mapping.

Right now, the Taiga OIDC plugin doesn't even request group membership information. While that bit is easy to solve, it would then also need hooking up to the taiga internals for some kind of mapping.
Author

I think an MVP here is, "I have a valid FAS account, I get comment access to any card in Taiga" if I need to be assigned a card or have more responsibility I need to get upgraded membership.

Phase II, if determined to be needed can be based on FAS groups.

I think an MVP here is, "I have a valid FAS account, I get comment access to any card in Taiga" if I need to be assigned a card or have more responsibility I need to get upgraded membership. Phase II, if determined to be needed can be based on FAS groups.

Metadata Update from @kevin:

  • Issue assigned to jperrin
  • Issue priority set to: Waiting on Assignee (was: Needs Review)
**Metadata Update from @kevin**: - Issue assigned to jperrin - Issue priority set to: Waiting on Assignee (was: Needs Review)

I think an MVP here is, "I have a valid FAS account, I get comment access to any card in Taiga" if I need to be assigned a card or have more responsibility I need to get upgraded membership.
Phase II, if determined to be needed can be based on FAS groups.

Co-sign.

@bex There may be a workaround: From what I can tell, board admins can add permission to the "external user" role and it doesn't make it as scary as the UI indicates. For example, I gave the "external user" role permission to create issues on a project and from an unauthenticated browser session, I could not create the issue.

> I think an MVP here is, "I have a valid FAS account, I get comment access to any card in Taiga" if I need to be assigned a card or have more responsibility I need to get upgraded membership. > Phase II, if determined to be needed can be based on FAS groups. Co-sign. @bex There may be a workaround: From what I can tell, board admins can add permission to the "external user" role and it doesn't make it as scary as the UI indicates. For example, I gave the "external user" role permission to create issues on a project and from an unauthenticated browser session, I could not create the issue.
Author

I have enabled permissions in the Flock and Mentored Projects board per @bcotton 's workaround. We should get some better verification, ideally, but at a minimum document this.

I have enabled permissions in the Flock and Mentored Projects board per @bcotton 's workaround. We should get some better verification, ideally, but at a minimum document this.

Metadata Update from @mizdebsk:

  • Issue tagged with: taiga
**Metadata Update from @mizdebsk**: - Issue tagged with: taiga
This was also requested in https://pagure.io/fedora-infrastructure/issue/8344

Metadata Update from @mohanboddu:

  • Assignee reset
**Metadata Update from @mohanboddu**: - Assignee reset

@mattdm @riecatnor do you know who is our current contact for taiga?

This ticket is 2 years old and I'd love to either find a way to address it or just close it.

Thanks!

@mattdm @riecatnor do you know who is our current contact for taiga? This ticket is 2 years old and I'd love to either find a way to address it or just close it. Thanks!

@pingou I have that information... catch me out of ticket and I can get it to you. :)

@pingou I have that information... catch me out of ticket and I can get it to you. :)

@kevin do you know if we've contacted them about this request?

@kevin do you know if we've contacted them about this request?

Metadata Update from @smooge:

  • Issue tagged with: low-gain, low-trouble
**Metadata Update from @smooge**: - Issue tagged with: low-gain, low-trouble

Metadata Update from @smooge:

  • Issue tagged with: ops
**Metadata Update from @smooge**: - Issue tagged with: ops

@pingou I don't seem to have a record of us asking them about this. ;)

Would you like to ask them? support at taiga dot io

Or I can do so if you prefer.

@pingou I don't seem to have a record of us asking them about this. ;) Would you like to ask them? support at taiga dot io Or I can do so if you prefer.

@pingou I don't seem to have a record of us asking them about this. ;)

Would you like to ask them? support at taiga dot io

Or I can do so if you prefer.

You're on PTO so I'll reach out to them and cc admin@fp for record keeping.

Thanks for the info!

> @pingou I don't seem to have a record of us asking them about this. ;) > > Would you like to ask them? support at taiga dot io > > Or I can do so if you prefer. You're on PTO so I'll reach out to them and cc admin@fp for record keeping. Thanks for the info!

Metadata Update from @pingou:

  • Issue assigned to pingou
**Metadata Update from @pingou**: - Issue assigned to pingou

Turns out the original request for allowing anyone to create top-level project had already been fullfilled.

This together with the fix @bcotton indicated (allowing external users to create tickets) I think solves this ticket.

I'm therefore closing this ticket, tet us know if you need anything else.

Turns out the original request for allowing anyone to create top-level project had already been fullfilled. This together with the fix @bcotton indicated (allowing external users to create tickets) I think solves this ticket. I'm therefore closing this ticket, tet us know if you need anything else.

Metadata Update from @pingou:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @pingou**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)

Issue status updated to: Open (was: Closed)

Issue status updated to: Open (was: Closed)

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Sign in to join this conversation.
No milestone
No project
No assignees
11 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#7826
No description provided.