Consider creating a .github repository?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation
Research direction
Start with GitHub's default community health file documentation and the linked Node.js organization profile example. Review the proposed .github/profile/README.md, CODE_OF_CONDUCT.md, SECURITY.md, and CONTRIBUTING.md files, then confirm which organization-wide defaults Bytecode Alliance wants and what the profile should contain. Done means the agreed .github repository structure and profile are established for the organization.
Written by the indexing model from the issue text.
Description
Hello! 👋
Not really sure where to recommend this or whether there's a formal procedure or what. I just wanted to pose the idea that @bytecodealliance should have a .github meta repo https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
Why this would be a good idea:
- Outline what Bytecode Alliance is right on the https://github.com/bytecodealliance GitHub profile/org page
- Be able to set an organization-wide CODE_OF_CONDUCT.md file
- Be able to set an organization-wide SECURITY.md file
- etc. for other org-wide default files like CONTRIBUTING.md or whatever
Mainly though I would very much like to see a .github/profile/README.md similar to Node.js' profile readme:
- Dominant language
- No language data
- Stars
- 73
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
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.
More from bytecodealliance/rfcs
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bytecodealliance/rfcs#23 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
bytecodealliance/rfcs#7 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/rfcs#6 · 1 comment · 1 reaction ·
All issues in bytecodealliance/rfcs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#167 ·
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·