Get teams.fp.o to allow access to projects at a default level for anyone with a FAS #7826
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
11 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#7826
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.
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:
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 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:
This was also requested in https://pagure.io/fedora-infrastructure/issue/8344
Metadata Update from @mohanboddu:
@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. :)
@kevin do you know if we've contacted them about this request?
Metadata Update from @smooge:
Metadata Update from @smooge:
@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:
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 status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed