MicrosoftI think that the ACTUAL problem here, is that the GitHub issues for any document set were replete with problems about the underlying technology. So, for example, folks might raise an issue with the SharePoint API not working in the GitHub for the SharePoint API documentation. That's a wrong usage.
*HOWEVER* ... ... The reason for that is because there was no SIMILAR method to actually raise those.
Raising such issues publically ensures that there is an open discourse about problems that other people can see, and it is *vital* (especially for the professionals) that it is open and available to the community. It lets us know that something is in hand and being managed.
Sure, we (professionals) also know that we can raise issues via the admin panels, however those do not help *everyone* when there is a wider issue.
The correct path should not be: Private request > MS Handles > Notice goes out that barely anyone sees
The correct path should be: GitHub request > MS Assesses > MS Decides if issue is broad or restricted to user > If the latter a private ticket is raised and they are contacted privately if not it carries on in the GH (and whatever internal ticketing MS use)
