But the what we need to get over is - how can we ever replace Github Issues. I mean, it is 'integrated' into github and will be a natural place for people to report issues. Like MS bundling IE or Google calendar adding Google Meet links into calendar invites automatically.
But, GitHub has really only sown up the issues part for developers, for everyone else it's a mess - so if your differentiator is building something that's useful to everyone _else_ on the project, you could be on to a winner. On our projects, the everyone else typically outnumber the developers by about 3 to 1, sometimes even more. These are designers, project managers, client-side stakeholders etc. All of these people need to interact with an issue system, all of them need to be able to track progress, all of them need visibility on how a project is going.
Jira will tell you that that's what they do, but of course it isn't, Jira is a crime against humanity.
Github does seem to have a marketplace that we could get into. Maybe something we can explore.
Sync is simple to sort out.
We were thinking of two kinds of projects 1. Private - for the internal dev teams to work on 2. Public - for external folks like end users to work with internal teams
Now I see another one which is CLIENTS only - for a restricted set of external users.
Thought: Make a free marketplace extension that allows a one-click "configure this user's subscriptions to different event types to make it into an issues-only user from that user's POV".
Both useful and if done right would hopefully be much more of a way to get people to engage with your product/brand than it would be "enabling a competitor" (I think ... or at least: I'm not trying to convince you to do something against your own interests for my own gain here, but that does not at all mean I'm not completely wrong ;)