Re-upstreaming and maintainership of the KGPE-D16 - Cost: 30 000E and counting
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
There was a proposition to do required work under refused grant application. If there is interest from third party to fund conjointly needed work, board could be maintained and reupstreamed, under u-bmc, coreboot and under Heads.
Edit:
- Proposition from 3mdeb [here](https://github.com/3mdeb/kgpe-osf/pull/1)
- History [here](https://github.com/osresearch/heads/issues/719#issuecomment-627605335)
- ~Possible funding path [here](https://github.com/osresearch/heads/issues/719#issuecomment-627607853)~
- EDIT: Funded by Immunefi https://github.com/osresearch/heads/issues/719#issuecomment-893024079
- Work plan: https://github.com/osresearch/heads/issues/719#issuecomment-921877456
- Trail of 4.11 reported problems: https://github.com/osresearch/heads/issues/719#issuecomment-995879031
Last updates, newsletter, code source drop : https://github.com/osresearch/heads/issues/719#issuecomment-966729133
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 reading the linked 3mdeb proposition, the project history, and the work plan in the issue comments. Review the reported 4.11 problems and the source drop before determining the required work. Done means the KGPE-D16 board is maintained and re-upstreamed under u-bmc, coreboot, and Heads.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100