-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document how to add reviewers without also requiring superuser privs #19
Comments
I also posted this as a question to the symposion mailing list. |
Just checking -> this is so that Serge and I can point reviewers at specific abstracts? |
@katyhuff, I am not sure, it is something @mrterry mentioned during the last tech meeting and I jotted this issue down hastily. It might be. Anyway, here's an answer from the symposion mailing list. Is it helpful? I can try it later today or this week.
|
I see. I guess it's probably helpful. I'm not sure what a section is or a proposal section. If those correspond to the abstract submissions to the main tracks or minisymposia, then, that definitely would be the thing. As it is, though, there is not an apparent place to submit a talk abstract ( see issue #22 )... so my ability to assign those abstracts among the reviewers is currently a bit moot. That is - Issue #22 is more urgent than my ability to assign reviewers. |
(also, thanks @codersquid !!! ) |
I'll work on this. |
I ran the django command that Jacob mentioned, which added some new permissions.
For an example, I added two Teams, Super reviewers and Talk reviewers, and added a couple of Memberships for a couple of my accounts to check that I had differential permissions based on the teams. That worked. I should figure out how to automate permissions creation for when we set up production. |
documentation tracked in #66 |
making this issue so we remember to document the process once we know how to do it.
The text was updated successfully, but these errors were encountered: