Currently, only labels/tags are used to organise issues, which makes it difficult to have a general overview of which issues are related to which tasks and/or DCAT-AP version.
I suggest using the "project" feature of GitHub to group issues related to a new DCAT-AP release as, besides providing another grouping mechanism, allow people to see which issues have been completed, which are to do, and which are in progress - about GitHub projects, see:
Moreover, looking at the issues related to the new major release of DCAT-AP, I suggest adding another tag/label to flag those issues related to alignment with DCAT2 (e.g., "dcat2-alignment"), for future reference, and also to distinguish them from the other ones.
We apply more labeling in our issues to make this clearer for the community. Maybe a more structured approach for SEMIC as a whole could be valuable. We will take this as part of our governance improvements.
Currently, only labels/tags are used to organise issues, which makes it difficult to have a general overview of which issues are related to which tasks and/or DCAT-AP version.
I suggest using the "project" feature of GitHub to group issues related to a new DCAT-AP release as, besides providing another grouping mechanism, allow people to see which issues have been completed, which are to do, and which are in progress - about GitHub projects, see:
https://help.github.com/en/articles/about-project-boards
Moreover, looking at the issues related to the new major release of DCAT-AP, I suggest adding another tag/label to flag those issues related to alignment with DCAT2 (e.g., "dcat2-alignment"), for future reference, and also to distinguish them from the other ones.