Check that organisation users are set to public
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 98
- Forks
- 298
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 38
Description
By default, when people join the nf-core organisation, their membership is set to be private. This is bad because:
- We publicise everyone's membership on the website anyway, so it's not really private
- It means that the team size is very under-represented when viewed by non-members
This is annoying and slightly fiddly to change - only the user themselves is allowed to change it and it requires a bit of clicking.
Although we can't change it for people, we can check the organisation to see who is set to public and spam them until they update their profile.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating how the website handles nf-core organisation data and whether it already accesses GitHub membership information. Done means the organisation can be checked for private memberships and the affected users are prompted to make them public.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100