Labels
Labels
46 labels
- author has to improve the recipe according to comments from review
- author has to write the abstract and submit it to the editor
- author has to write the full recipe
- closed because of extremely low priority; this will most likely not be worked on
- closed because the corresponding task was successfully and completely achieved
- closed because the corresponding task was somehow achieved (workaround);should be revisited
- closed because this issue just duplicated another issue; link to the duplicate in the comments!
- closed because of low priority, but might/could/should be worked on in the future
- Pull requests that update a dependency file
- editor has to assess the outcome of the review; what are the next steps?
- editor has to follow-up on discussion sparked by the community
- editor has to run over the recipe for technical checks, and merge it into main branch
- editor has to follow-up on the recipe writing
- editor has to give feedback to the abstract submitter; is there need to improve?
- editor has to invite and enable an review of the recipe
- editor has to find an author for this recipe
- editor has to cope with an unsolicited submission; create trackers etc
- editor has to invite and get hold on an abstract for a recipe, describing the scope of the recipe
- issue tracks author's tasks, i.e. issues of type "author's task"
- an issue which reports a bug, i.e. that something isn't working as expected
- issue tracks editorial tasks, i.e. labels of type "editor's task"
- a meta-issue which tracks multiple other issues by providing a checklist
- issue contains general proposals on how to proceed forwards
- issue suggests a new feature which needs to be implemented in the backend of the cookbook
- issue suggests improvement of cookbook process documentation; NOT to individual recipes
- issue suggests improvement of the general cookbook content, and is not focusable on one recipe
- issue suggests to create one new recipe