freedomofpress / freedomofpress/kernel-builder
Consider moving workstation's paxctld into this repo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It's in the client repo right now, while the server one is in this repo. Having it in the client repo means it'll be easier to update as we ship new applications instead of requiring new kernel releases (see also #49). But it also means it's not managed with the kernel, and might need changes based on kernel updates??
Mostly filing this to have a spot for discussion, I'd be fine with us deciding to keep things the way they are.
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
Start by reading issue #49 and comparing how paxctld is currently managed in the client repository versus the server repository. The issue does not name files or tests; done would be a documented decision about where paxctld belongs and whether kernel updates require changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100