iilab / contentascode

Content as Code
http://iilab.github.io/contentascode
GNU General Public License v3.0
34 stars 7 forks source link

Issue tracker integration #40

Open jmatsushita opened 8 years ago

jmatsushita commented 8 years ago

This is an issue meant to keep track of various sub issues that relate to integration with issue trackers as a user interaction and feedback mechanism (#28)

Semantics

The first step is to depend on an external service for notifications (despite the need to register/login). Good candidates are the Github/Gitlab issue trackers (Gitlab self-hosted allowing to avoid third party authentication dependencies).

In that case there should be mappings of content items to issues (#24) and notifications can be managed through the issue subscription mechanism. Here are possible approaches:

Approach A

Example for one master repo

Repo: https://github.com/iilab/contentascode Issues: https://github.com/iilab/contentascode/issues

One issue could be mapped to one page.

Implementation:

One master repo, issues are orthogonal to the content (a more classical setup between code and issue tracking or documentation and issues)

Repo: https://github.com/iilab/openmentoring-mobile Issues: https://github.com/iilab/openmentoring-mobile/issues

Approach C

Multiple subrepos, corresponding to "areas of interest"

Repo: https://code.iilab.org/openintegrity/openintegrity.org Subrepos: