Missing policy to upstream Linux patches
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux
- Domain
- operating-systems
Research direction
Start by reviewing the issue’s rationale and the referenced OpenBMC Development Process. Compare that process with the sonic-linux-kernel workflow and define a policy covering upstreaming, forward-porting, and cases where product requirements prevent synchronization; done means the policy is documented and adapted for this project.
Written by the indexing model from the issue text.
Description
Currently, there does not seem to be a policy to upstream the Linux patches, adding maintenance burden.
- Forward porting these patches takes a lot of effort, which – once upstream – the Linux community would take care of.
- Work with other network operating systems, like Open Network Linux, which also has no upstreaming policy, is duplicated.
- The original patch authors are often gone after a while.
OpenBMC has a Development Process, I recommend to adapt.
Upstream is key
In order to leverage the benefits of using the Linux kernel, OpenBMC maintains a policy that all kernel code will be merged upstream.
However, there are often cases where product requirements mean that synchronising with an upstream schedule is not always possible. This process aims to allow both goals (upstream inclusion and a useful OpenBMC build) to occur in parallel.
- Dominant language
- Shell
- Stars
- 72
- Forks
- 237
- Avg merge
- 7d 19h
- Merged PRs (30d)
- 8
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 sonic-net/sonic-linux-kernel
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
sonic-net/sonic-linux-kernel#531 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
sonic-net/sonic-linux-kernel#367 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
sonic-net/sonic-linux-kernel#348 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sonic-net/sonic-linux-kernel#347 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sonic-net/sonic-linux-kernel#346 ·
All issues in sonic-net/sonic-linux-kernel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100