Labels
Labels
26 labels
- Tagging of activity areas for scoping committer releases
- Project-internal tasks that most parties can happily ignore
- Describing times, dates and events (and their relationships)
- Pull requests that update a dependency file
- Fixed in main branch / posted to webschemas.org site / proposed for inclusion in next release
- Work on our supporting materials rather than on schema definitions
- Queued for moving to suggestions-questions-brainstorming repo
- Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
- Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
- An old (and thus closed) but interesting issue for future reference iff the topic comes up again
- Pull requests that update Python code
- Editor needs to turn issues/PRs into final code and release notes.
- Anything that has been in Pending for > 6 months.
- This is ready to send around (and check release notes are suitable)
- Editorial work provisionally complete; ready for final review/checks.
- Pull requests that update Ruby code
- General top level tag for issues on the vocabulary
- Infrastructural issues around schema.org site. Most can ignore this!
- Relationships, liaison, mappings between our work and standards elsewhere
- Proposals that are inactive, abandoned, obsolete or handled another way.
- We are likely to, or would like to, or probably should try, ... to do something in this area.
- Collaboration amongst schema-maintaining projects
- A mistake or malfunction whose remedy should be straightforward technical work
- Addresses wording fixes, ambiguities, confusion, bad examples etc
- Hard problems, including modeling / vocabulary and infrastructural aspects (eg fiction, probability)
- Issues related to Schema Markup Validator