Yep, I know about GitHub Issues and the similar features in GitLab and Forgejo. What I have in mind would build atop those, not replace them (analogous to how the higher project management features in those and Jira build atop an issue/task-tracking system).
What I have in mind has a different and narrower emphasis than Linear.app, and hopefully would do the main thing it does much better. (Yet another reason I don't want to do enterprise sales initially -- I'd lose all the org chart stakeholders feature checklist deathmatches. I have to sell it word-of-mouth, to founders/PMs/TLs who appreciate the focus, and who have small-purchase company credit cards.)
For user data, what you suggest would work, if I modify the initial functionality slightly. I don't want customer data flowing through my servers, but I could serve up JS app/pages from my servers, with the browser making the data requests to GitHub/etc. directly. (Future functionality might need code running separate from any browser.) And should be easy to package up for customers who want that server part on-prem. The greatly reduced friction -- to some PM suddenly deciding to try it as they're wrangling the project at 4:30pm, and be up and running in a minute -- seems well worth contorting the functionality a little. Thanks!
Yep, I know about GitHub Issues and the similar features in GitLab and Forgejo. What I have in mind would build atop those, not replace them (analogous to how the higher project management features in those and Jira build atop an issue/task-tracking system).
What I have in mind has a different and narrower emphasis than Linear.app, and hopefully would do the main thing it does much better. (Yet another reason I don't want to do enterprise sales initially -- I'd lose all the org chart stakeholders feature checklist deathmatches. I have to sell it word-of-mouth, to founders/PMs/TLs who appreciate the focus, and who have small-purchase company credit cards.)
For user data, what you suggest would work, if I modify the initial functionality slightly. I don't want customer data flowing through my servers, but I could serve up JS app/pages from my servers, with the browser making the data requests to GitHub/etc. directly. (Future functionality might need code running separate from any browser.) And should be easy to package up for customers who want that server part on-prem. The greatly reduced friction -- to some PM suddenly deciding to try it as they're wrangling the project at 4:30pm, and be up and running in a minute -- seems well worth contorting the functionality a little. Thanks!