Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12893 - {archweb} Add ability to have non-account devs on the developers page

Attached to Project: Arch Linux
Opened by Aaron Griffin (phrakture) - Thursday, 22 January 2009, 18:42 GMT
Last edited by Dan McGee (toofishes) - Friday, 18 February 2011, 14:56 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I noticed the UserProfile stuff was recently split out. I was wondering if there was some way to add users who don't have/need dashboard accounts to the developers page.

I want to add these people:
Loui and Callan as AUR Developers
Gerhard and Dieter as Release Engineers
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 18 February 2011, 14:56 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Permissions should be good enough already; if not we can add some more groups with fine-grained permissions.
Comment by Dusty Phillips (Dusty) - Friday, 30 January 2009, 23:22 GMT
Do they require access to anything under the django site? If all you want is for them to show up on the developers page, but not be able to access the dashboard or dev pages, you can add them like normal users, but set a random unusable password.

If you need for them to be able to log in to some stuff but not other stuff, I'll have to add some permission checking to the dashboard. Not hard, but I'll need to know what they can or can't view.
Comment by Aaron Griffin (phrakture) - Friday, 30 January 2009, 23:35 GMT
Well, I was thinking about giving them the ability to post news and the like, but the recognition is the most important part.

In the long run though, adding a "can adopt packages" permission group is probably a good idea. Actually, more refined - adding permissions for each repo might be a good idea. Or at least something like: can adopt core packages, can adopt community packages, and then a catch-all. Sometime in the future we will be moving the TUs to the official tools, which means dashboard access...
Comment by Dusty Phillips (Dusty) - Tuesday, 14 April 2009, 02:21 GMT
Ah, I dropped this. You can add these guys and not give them the 'base permissions' group. Then if you want them to post news or similar, they just need to have the specific news posting permissions added directly to the user profile.
Comment by Paul Mattal (paul) - Thursday, 24 September 2009, 11:24 GMT
Sounds like we should keep this around, but maybe change the name to "finer grained permissions groups for developers site"? I suspect we'll want this eventually.
Comment by Aaron Griffin (phrakture) - Thursday, 24 September 2009, 18:54 GMT
Yeah, we have a little bit of this already in that we have repo-based permissions for packagers. I can just select nothing and they can't adopt anything
Comment by Dan McGee (toofishes) - Monday, 30 August 2010, 20:42 GMT
Wow, old bug getting assigned to me. Does anything need to be done here? If they don't have any repos selected in the admin user site, then they can't adopt packages. Where they show up on the TU/Developer list depends on the groups they are in and whether they are marked active.

Loading...