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
Create a GitHub issue template for edit suggestions from users coming directly to the Cliopatria resource via GitHub rather than via Seshat.
Should include ShapeID(s) and free text description. But could cover the entire set of Cliopatria fields - e.g. if people are suggesting to an entire Polity.
This could potentially be a better mechanism than relying on the Seshat comment system - or it could be in parallel. If the former, we should update the Seshat docs page to link to opening an issue in GitHub instead. If the latter, the Seshat task and the GitHub issue should be linked.
Advantages include:
Edit suggestions could include screenshots or drawings, something isn't possible on the Seshat website
Disadvantages:
Seshat Expert would need a GitHub account if issues can't also be raised via the Seshat website
Create a GitHub issue template for edit suggestions from users coming directly to the Cliopatria resource via GitHub rather than via Seshat.
Should include ShapeID(s) and free text description. But could cover the entire set of Cliopatria fields - e.g. if people are suggesting to an entire Polity.
This could potentially be a better mechanism than relying on the Seshat comment system - or it could be in parallel. If the former, we should update the Seshat docs page to link to opening an issue in GitHub instead. If the latter, the Seshat task and the GitHub issue should be linked.
Advantages include:
Disadvantages:
Linked to:
The text was updated successfully, but these errors were encountered: