Project-MONAI / Project-MONAI/MONAI
Creation of Github Teams
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.7k
- Forks
- 1.6k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 20
Description
My idea was to create new teams within the Project MONAI Github organisation. We have a few here https://github.com/orgs/Project-MONAI/teams but I think we should add more for specific areas of interest, topics, application areas, etc. so that there's a known group of people who might be able to contribute to issues or discussion.
For example, I'd suggest a UNet or Networks team composed of people who have contributed to networks in some way or are otherwise known as experts on these topics. If a question relating to networks comes up then this team can be referred to @-referencing so that the issue is more visible to someone in that team who can help out. It would be expected that people would be members of multiple teams, but also that they wouldn't be obligated to answer every summons. I see this as an easy way of knowing who to ask for help on certain topics when they arise.
Some team ideas:
- Networks
- Loss Functions
- Dataset and DataLoader
- Workflows (Ignite)
- Segmentation
- Classification
- Diffusion
- Generative
- Label
- Other working group topics
This is a proposal for discussion on this so please do comment. We should also be inviting more contributors for these teams as well as core contributors.
@Nic-Ma @KumoLiu @aylward
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
Start by reviewing the existing teams in the Project-MONAI GitHub organization and the discussion in this issue. The proposal lists possible teams such as Networks, Loss Functions, Dataset and DataLoader, and Segmentation, but does not define an agreed scope or implementation plan. Done would require maintainer agreement on team structure, membership, and the teams to create.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100