Labels
Labels
28 labels
- Pull requests that update a dependency file
- Someone with a little familiarity can pick up
- Extensive knowledge (implications, ramifications) required
- Having worked on the specific codebase is important
- Prior experience is likely helpful
- Can be confidently tackled by newcomers
- Estimated to take multiple days, but less than a week
- Estimated to take one or several hours
- Pull requests that update GitHub Actions code
- Pull requests that update Javascript code
- A bug in existing code (including security flaws)
- Topical discussion; usually not changes to codebase
- A net-new feature or an improvement to an existing feature
- Something that you'd like to see in the docs. This can be written content, web design, or imagery.
- A question or request for support
- Has been looked at, but not deeply. Needs further research. May need community/maintainer input.
- The Docs Team needs to formulate a viable plan of action for this issue.
- Needs initial labeling and prioritization
- Critical: Tackled by core team ASAP
- High: Likely tackled by core team if no one steps up
- Medium: Good to have, but can wait until someone steps up
- Low: Not priority right now
- Front-end web development issues.
- Issues tied directly to smart-contract development.
- Docs content for the Interplanetary Consensus (IPC) project.
- Issues that aren't explicitly content related, but will improve readers experience.
- Issues tied directly to supporting storage providers.
- Unable to be worked further until needs are met