riscv-software-src / riscv-software-src/opensbi
why so adamant about mailing list though?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 712
- PR merge metrics
- No merged PRs in 30d
Description
every pull request you are closing because of "mailing list" argument is a lost opportunity and slap on the face of potential contributor.
i get it, it's "old dogs, new tricks" sort of a thing when it comes to pull request vs. mailing list flow (ycombinator is full of reasons to support both), but opensbi is relatively a new project. it doesn't have legacy like linux kernel, so why not keep things modern? LLVM project moved from mailing list to github pull requests, so can this project. makes no sense to use 80's tech for new repos..
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 files, tests, or entry points are named. Start by reviewing the project's contribution workflow and examples of pull requests closed for mailing-list reasons, then identify the maintainers' decision on whether GitHub pull requests should be supported. Done means the workflow decision is documented and any required repository guidance is updated.
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
- 25/100