Future development of Ofborg
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Since there is the question what we should do this in future, it would be good to figure out,
who would like to work on this and how much time you think you could spend on this.
Contribution could fall into one of the two categories or both:
- Infrastructure maintenance
- Development
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 with the issue discussion and the Ofborg repository description; no specific file, test, or entry point is identified. A useful outcome would require agreeing on future infrastructure maintenance or development priorities and identifying who will work on them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100