|
|
|
|
|
by buro9
1768 days ago
|
|
Tell me about the sync... how complete is it?
And the pricing... how do you accommodate OSS projects? Our scenario is that our work comes in from multiple places, i.e; OSS community (one repo), SaaS offering (another repo) and Enterprise offering (another repo). What we're trying to achieve is a single pane of glass for a team to see all of their work, but the work to remain in the respective repos. So whatever tool we use must treat Github Issues as the system of record, and any tool must reflect what it does in Github. And further, it would be great to make that single pane of glass dynamic... i.e; I'm a Prometheus engineer and I want to create a team/project that aggregates all work on Alertmanager across all of the big projects that use it (even the ones that exist in other orgs). ACK that our use-case may be at the extremes of what others do, so it's cool if this is not yet possible. Additionally with the OSS repos per-user licensing of potentially all contributors is a tough ask, we would have no control over our pricing and most contributors would be idle... they're not employees, but we'd want to ensure the community could use/see the same tools that we would use, how could we enable community involvement in the tools without exposing ourselves to a loss of control over the operating costs of it? |
|