-
Notifications
You must be signed in to change notification settings - Fork 211
Add description of how we vet requests to join obo-discuss #2726
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
base: master
Are you sure you want to change the base?
Conversation
as described by James in #2112. I changed the 'I' to 'we', but it would be better if we replaced 'we' with the name of the role of the person who does the steps described (who apparently is currently James).
Yes, this is exactly the current process, and this PR is fine to merge as it is. As I was reviewing, I had more thoughts... When someone includes a reason that they want to join, I approve them right away, but 80% do not. So I just added this text to the description of the Google Group:
I haven't heard any complaints about the existing process, but it's annoying for several reasons. Let me just write them down for the record:
Instead of checking new members before they join, we could allow anyone to join and then moderate. That sounds like even more of a pain, and higher risk. So I think we're left with the status quo. I guess my small suggestions are:
What do you think @nlharris ? |
@jamesaoverton I'll volunteer to be another person doing that job—I don't currently have many responsibilities within OBO Ops, so I'm happy to step up for this. |
Sounds good to me! Thanks for your work on this, and thank you, @sebastianduesing for volunteering to help! |
Is there a way to add this text to the 'reason' field of the application form? |
btw, re
It would be good if we had a way to refer to 'this job' in the documentation. I don't think it would be ideal to put individual names in the SOP. Can we call it "obo-discuss moderator"? |
I guess we decided to go ahead and merge this and maybe make future improvements (e.g. my suggestion above to name 'this job')? |
Yes. I did not see a way to add any other message to users about the 'reason' field. |
as described by James in #2112. I changed the 'I' to 'we', but it would be better if we replaced 'we' with the name of the role of the person who does the steps described (who apparently is currently James).
fixes #2112