Definition of the process used to collect all issues

[adriatic]

Rule 1

Issues should be entered using a predefined format which classified issues as either being in the "Missing API" category or "Template processing" category. We should use the labels Templates processing and Missing API to indicate the category issue belongs to.

For completeness sake, we also expect "bug" and "other category:

Image 1

Note issues are labelled as definition or organizational (metadata issues) do not have to comply with the above defined format. The "kanban view" of this issue (In progress column illustrates this exception):

Image 2 - "metadata" issue

Example of the "template processing" category:

Image 3 - template issue

See the article Aurelia versus KendoUI Template Processing for more information on this category.

Example of the "missing api" category:

Image 4 - missing API issue

See the article Aurelia binding and KendoUI SDK missing API for more information on this category.

---

Rule 2

Each KendoUI SDK issue should be fully contained in a single GitHub issue item.

---

Rule 3

Each issue (including metadata issues) should be discussed in the form of additional comments to the GitHub issue that contains the KendoUI SDK issue.

---

Rule 4

While this project is still active issues that reached the status resolved should be labelled using this label:

(we do not want to close any of the resolved issues as they will be used as input to the next project: Implementation)