Roman supported the private repo and was aware of the temporary (last 3 days only) CF logs to address CDN abuse. However, several hours ago, he (or someone else using his account?) unexpectedly made the repository public without discussing it with the project's maintainers. As a result, his account rights were temporarily restricted to clarify the situation.
There is still no response from Roman regarding his motivation for ignoring the usual governing board rules. Previously, all similar important project decisions were always discussed with maintainers/active contributors before being executed.
I hope that we resolve this strange situation successfully soon.
Yeah I mean, of course technically that's not how it's supposed to be done, but if they initially added the code and the licence (the latter by mistake), then I can see how the internal narrative is "here's my code (that Roman has contributed to) and I accidentally added the licence to it - oops, let me remove that before we accidentally make it public".
Of course at that point they should have realised that they weren't the only author of the code any more and that Roman understandably would have the wrong idea. But I see how it's an easy mistake to make, and it would probably also have easily been resolved had Roman reached out about it, rather than just instantly making it public and implying nefarious behaviour ("quietly made a change...discovered by me").
Was that decision put to a vote like "all important project decisions" are? I assume it can't have been unless Roman is blatantly lying about only noticing it a few days later.
Roman supported the private repo and was aware of the temporary (last 3 days only) CF logs to address CDN abuse. However, several hours ago, he (or someone else using his account?) unexpectedly made the repository public without discussing it with the project's maintainers. As a result, his account rights were temporarily restricted to clarify the situation.
There is still no response from Roman regarding his motivation for ignoring the usual governing board rules. Previously, all similar important project decisions were always discussed with maintainers/active contributors before being executed.
I hope that we resolve this strange situation successfully soon.