You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the Open Documentation Academy we need an easy way for contributors to browse participating free software organizations and available documentation issues to work on.
For listing the issues the idea came up to create a GitHub action to be used by the participating organizations to get documentation issues posted on their GitHub repos automatically copied into the GitHub of the Academy (this repo). This was presented as issue #11 here.
There I have found some problems:
A participating organization needs to manage their issues (at least the documentation-related ones) on GitHub to get them easily listed at the Academy. Otherwise they have to re-post them on our repo manually.
To be able to create or modify issue reports on our GitHub by an automatic process, each participating organization needs sepecial permission by Canonical's IS Team, the owner of our repo.
The copies of the organization's issues need to be kept up-to-date.
For listing the organizations I have made a suggestion in issue #70, and there I also suggest that together with each organization's listing, the related documentation issues should be listed, too.
As we then list issues from a GitHub, why should we not directly list from the organization's GitHub, and then perhaps from GitLab, and other bug trackers, too? The registration record of each organization could contain a list of projects/bug trackers with which they want to participate and a list of tags with which they want to mark issues to be presented in the Academy.
For the Open Documentation Academy we need an easy way for contributors to browse participating free software organizations and available documentation issues to work on.
For listing the issues the idea came up to create a GitHub action to be used by the participating organizations to get documentation issues posted on their GitHub repos automatically copied into the GitHub of the Academy (this repo). This was presented as issue #11 here.
There I have found some problems:
For listing the organizations I have made a suggestion in issue #70, and there I also suggest that together with each organization's listing, the related documentation issues should be listed, too.
As we then list issues from a GitHub, why should we not directly list from the organization's GitHub, and then perhaps from GitLab, and other bug trackers, too? The registration record of each organization could contain a list of projects/bug trackers with which they want to participate and a list of tags with which they want to mark issues to be presented in the Academy.
@degville WDYT?
The text was updated successfully, but these errors were encountered: