Flesh out and document target UX
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 196
- Forks
- 55
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 14
Description
I think it's a useful exercise to early on flesh out what the UX will look like. Let's discuss that here and then add something in the README?
Some bootstrapping questions:
- how does one perform a manual upgrade?
- how do automated systems perform upgrades?
- how does this tie into
rpm-ostree statuson rpm-ostree-based systems?
We don't need to answer everything completely, but discussing these will make it easier to think about how bootupd fits in.
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 the existing README, then use this issue's questions to frame the target UX: manual upgrades, automated upgrades, and integration with rpm-ostree status. Discuss the expected workflows and document the agreed behavior in the README; done means the UX has been clarified rather than every question answered completely.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100