Central GA4GH Ticketing

[MKonopko]

Per M Haendel:

a place to put requests such as these. It would be terrific if there was a more coordinated suite of GitHub repos and a central ticketing/work tracking system across them for GA4GH. Please let us know if you want help or advice in setting up such a thing, we are happy to contribute.

[jb-adams]

@MKonopko @mellybelly one way to track incoming requests would be through the GA4GH Organization-level Project boards on Github (link). We currently have boards for specific projects, but could potentially add a board for TASC and/or general GA4GH work.

[mellybelly]

I love the board :-)

[rishidev]

Defer until technical team is in place 2021 if this is feasible.

[uniqueg]

I just wanted to bump this and say that I 100% agree that GA4GH should offer a centralized entry point for raising issues/tickets. In my opinion, it would be crucially important especially for newcomers and one-off or casual contributors , but also for regular contributors (as it is, I only found out today that in fact there is a TASC repo and project board).

I could imagine a publicly available open (i.e., no auth) service with a form that people can fill in issues. It could provide checklists for work streams and individual specs/standards that submitters could optionally make use of. This info could then be used to automatically create issues, via the GitHub API, in the appropriate repos for further manual triaging by WS and API/standard champions. Issues that do not have any info to allow us to identify a suitable repository would end up in some dummy repo and would need to be manually triaged and transferred to an appropriate place.

Ideally, the service could also make use of the GitHub API to list all available issues for people to search through before filing an issue (or, ideally, suggest related issues) to avoid duplicates. But that may be a second step. Although perhaps the whole service could be a Google Summer of Code project.

[uniqueg]

Or JIRA: https://www.atlassian.com/licensing/purchase-licensing#pricing-discounts

[mellybelly]

I couldn't agree more about the importance of a one-stop shop for anyone to submit a ticket (and have it delivered to the correct team) as well as the inventory of standards and their associated repos/ticketing systems (i.e. #7). Overall, we continue to have very many different places to work, making coordination across them challenging.