Skip to content

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

nlharris
Copy link
Contributor

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

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).
@nlharris nlharris requested a review from jamesaoverton May 30, 2025 01:14
@jamesaoverton
Copy link
Member

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:

Everyone is welcome to join, but to avoid spam we check new member requests. When signing up for this list, please tell us why you want to join, so we can tell that you're not a bot.

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:

  • people don't like waiting for approval
  • I'm never sure if people get my confirmation requests
  • I don't like checking the pending list, sometimes I forget for a few days, I don't check on weekends or vacation
  • I think I'm the only one who does this job
  • as admins we don't have a way to coordinate who we've sent follow-up emails, so it's hard to share the job

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:

  1. set up a private Google Sheet to track new member requests and add it to the SOP
  2. get more people to do this job, which would hopefully minimize how long it takes to approve a new member

What do you think @nlharris ?

@sebastianduesing
Copy link
Contributor

@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.

@nlharris
Copy link
Contributor Author

I guess my small suggestions are:

  • set up a private Google Sheet to track new member requests and add it to the SOP
  • get more people to do this job, which would hopefully minimize how long it takes to approve a new member

Sounds good to me! Thanks for your work on this, and thank you, @sebastianduesing for volunteering to help!

@nlharris
Copy link
Contributor Author

nlharris commented May 30, 2025

When signing up for this list, please tell us why you want to join, so we can tell that you're not a bot.

Is there a way to add this text to the 'reason' field of the application form?

@nlharris
Copy link
Contributor Author

btw, re

get more people to do this job,

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"?

@nlharris
Copy link
Contributor Author

I guess we decided to go ahead and merge this and maybe make future improvements (e.g. my suggestion above to name 'this job')?

@jamesaoverton
Copy link
Member

Yes.

I did not see a way to add any other message to users about the 'reason' field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add OBO Discuss mailing list management to SOP
3 participants