misyltoad / misyltoad/frog-protocols
Move frog-protocols to its own organization/group
Nobody has claimed this yet.
- Dominant language
- Meson
- Stars
- 435
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
At this point, it's unclear whether frog-protocols is just @misyltoad or if there are more folks engaged, involved, or invited to participate. Some of this is because it's brand-new, but also some of this is that projects under a personal namespace on GitHub are awkward for collaborative development.
I would like to suggest that frog-protocols moves to a GitHub organization (or GitLab group) so that it's easier to set up collaborative maintenance and make it more transparent who is part of the project and administering things.
It would also probably make people feel more at ease to engage when it appears to be set up more like a multi-stakeholder project.
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or code entry points are mentioned. Start by reviewing the current GitHub project ownership and the requirements for a GitHub organization or GitLab group. Done means frog-protocols has moved to a collaborative namespace with transparent membership and administration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100