> Maybe they thought that it was clear that they had the authority to move member projects to GitHub Enterprise. Seeing the various owner reactions this was ob

> Maybe they thought that it was clear that they had the authority to move member projects to GitHub Enterprise. Seeing the various owner reactions this was obviously not clear for them > Maybe they thought that moving to GitHub Enterprise is solely a helpful move since it gives extra features to the the projects for free (by that I mean that maybe they considered it to be the equivalent of simply setting a flag on the project that gives it access to those features). Maybe there was miscommunication internally due to not having well-define protocols and someone thought it was safe to move the project. If no one in the .net foundation was able to raise an alarm about those transfers because of a "simple" lack of awareness of the importance of project ownership, then I don't see how they can rebuild the lost trust. They have demonstrated an absolute lack of understanding of their OSS community. As you said maybe it is a process issue but simply saying "sorry we shouldn't have done that" is not transparent enough. Clearly at some point they were ok with those transfers since they were carried. And now they understand that it was a bad thing. What happened? Did the twitter/blog post backlash suddenly opened their eyes on the perspective of the project owners? If that is the case then what are the other things they need to realise in order to avoid making other mistakes such as this one?