I believe that for many of us who use GitHub for a long time, it has become more than just a “place to organize code”. For me, GitHub issues, pull requests, milestones and wikis are essential to the day to day work.
By managing (organization, private-) work on GitHub itself, I am facing a problem:
Non-developer users - for example, product manager, QA testers, etc - do not have access to GitHub. So, I find myself managing “double booking” and linking my GitHub tickets with whatever other ticketing system is available to the non developer users. Sometimes I find myself printing the Markdowns or Commit List from GitHub to a PDF so I can send it internally… this feels dirty and wrong.
The reasons I am not giving these users access to GitHub are these:
Such non developer user would cost the same as a regular user, and since we have a lot more non developers than developers, this is outside of our budget. These are just occasional users, and I cannot justify the full user price for them.
I would prefer to be able to set these users so that they cannot see code - to avoid confusion, and even to prevent access from business persepctive. I wish these users to only see Issues, PRs, Milestones - everything that is more “business” or “product” oriented, rather than code oriented.
In essence, I would like to make two separate suggestions
Provide a new “seat” type, lets call it “viewer” at a reduced cost.
Provide another downgraded role (lower than “viewer”), lets call it “participant”, who can not view code, but can enjoy the “surrounding” GitHub experience.
I know this was discussed in one form or another in several venues.
One such post with a similar problem can be found here.
Still thought it was worth writing it down as it is.