Specify optional additional resources (homepage, blog, <your idea here>)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Currently we only support specifying a repo which is not ideal to lure in people who're vaguely interested in learning more a team/WG but not necessarily want to wade through the amount and level of details a repo typically provides.
Some teams/WG have dedicated homepages to feature their work and others also frequently blog about it so it would be nice to being able to provide links to that work, too.
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
No files or tests are named. Start by locating the existing support for specifying a repository and trace where that information is stored and displayed; done means teams can provide optional homepage, blog, or other resource links alongside a repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100