> Nebulous semi-employee with unspecified responsibilities related to a founder?
This is the point that stands out for me. That the wife is not an employee of Github but claims to be able to access private company chat records, and also is able to "work" from within the office and interact with the staff.
Even with allowances that company property remains company property and private chat rooms are in fact non-private to the company... there is no scenario in which a non-employee should have access to those chat rooms.
The wife, and the husband (founder), have displayed an incredible lack of professionalism here. There may even be a question about whether those acts are illegal if they are substantiated.
And for companies that use Github to host private repositories, the question should be asked very loud and clear... "Who can access private company data, why, and for what reason?".
If a non-employee can access information that is presumed (even by their own employees) to be private, then our (external companies) assumptions about what is private and secure at Github are weakened and demand very clear statements backed up with clear processes to reassure.
This is the point that stands out for me. That the wife is not an employee of Github but claims to be able to access private company chat records, and also is able to "work" from within the office and interact with the staff.
Even with allowances that company property remains company property and private chat rooms are in fact non-private to the company... there is no scenario in which a non-employee should have access to those chat rooms.
The wife, and the husband (founder), have displayed an incredible lack of professionalism here. There may even be a question about whether those acts are illegal if they are substantiated.
And for companies that use Github to host private repositories, the question should be asked very loud and clear... "Who can access private company data, why, and for what reason?".
If a non-employee can access information that is presumed (even by their own employees) to be private, then our (external companies) assumptions about what is private and secure at Github are weakened and demand very clear statements backed up with clear processes to reassure.