4 ms·
This is a problem at every org scale as well. We have this issue with a 1000+ developer org where we still can't give our PMs and other non-developers read-onl
by fishpen0 5y ago
This is a problem at every org scale as well. We have this issue with a 1000+ developer org where we still can't give our PMs and other non-developers read-only access to the gitlab issues because it would be another 200 headcount worth of full-price licenses. It's basically the sole reason we can't utilize most of their jira/confluence alternative product line and still keep issue tracking and docs mostly outside of gitlab.
- z3t4 5y agoIf you are just using the .git hosting part, it would be really easy to setup an open-ssh server yourself... Could you explain why you are not hosting your own ssh server already ?
- lolinder 5y agoThey didn't say they're only using the git hosting, they're just not using the issue trackers because that would require adding non-devs. For all you know they could be using GitLab for CI, merge requests, package management, and deployments, none of which require adding new people to the team.
- fishpen0 5y agoExactly this, we use it for all of those things. None of which provide value to PMs, designers, and other non-engineer roles within teams that still need to collaborate on issue tracking and documentation.