This blogpost is highly inaccurate and a heavy misportrayal of the events that occured. The title is completely wrong already. They did not get banned from GrapheneOS. GrapheneOS is a free and open source operating system, you can’t be banned from using it and the developers would also not wish to do so. They were instead banned from the OS issue tracker on GitHub because of spam and inapprioriate behavior. They were also blocked by multiple GrapheneOS developers on GitHub, not solely Daniel Micay, for continuing to mention them and sending notifications their way, even via other repositories than the official GrapheneOS issue tracker. Also, they are not a contributor at all. They have never contributed to GrapheneOS, not a single line of code. Unless they would call issue tracker spam a contribution, but that’s a very big stretch.
Now, as to what actually happened. They wanted GrapheneOS to implement a certain feature, but GrapheneOS did not deem it desirable. Instead of accepting this, they kept spamming the issue tracker. The issue got deleted because it caused too much spam from other accounts as well who kept saying they also wanted the feature instead of following the rules of the issue tracker that you should upvote a post if you agree. After getting banned, they forked the issue tracker and started pinging a bunch of GrapheneOS developers. This behavior is insanely inapprioriate in the FOSS world. GrapheneOS is free, yet they act insanely entitled, as if the GrapheneOS developers owe them anything. GrapheneOS project memebers also clearly explained to them on multiple occasions why the feature they proposed is undiserable.
If you disagree, the solution in open source is to fork GrapheneOS and make your own changes to the source code instead of endlessly complaining to the developers of the original project, who can’t be forced to follow your opinion. GrapheneOS had every right to ban them because they kept making a scene out of something minor like a non-accepted feature request. Many feature requests get rejected, yet they make this whole drama about it and continue to do so.
On top of all that, they link misinformation and harassment about the GrapheneOS project in their blog post. The videos they link from content creators contain bullying and fabrications about the project and the founder. They are also entirely unrelated to how they dealt with the issue on the issue tracker.
Maybe, but the usual way to deal with issues that attract lots of unwelcome comments is to close it and lock the comments, so that people know what happened. If the issue just disappears, people will end up wondering what happened.
Readit News
Now, as to what actually happened. They wanted GrapheneOS to implement a certain feature, but GrapheneOS did not deem it desirable. Instead of accepting this, they kept spamming the issue tracker. The issue got deleted because it caused too much spam from other accounts as well who kept saying they also wanted the feature instead of following the rules of the issue tracker that you should upvote a post if you agree. After getting banned, they forked the issue tracker and started pinging a bunch of GrapheneOS developers. This behavior is insanely inapprioriate in the FOSS world. GrapheneOS is free, yet they act insanely entitled, as if the GrapheneOS developers owe them anything. GrapheneOS project memebers also clearly explained to them on multiple occasions why the feature they proposed is undiserable.
If you disagree, the solution in open source is to fork GrapheneOS and make your own changes to the source code instead of endlessly complaining to the developers of the original project, who can’t be forced to follow your opinion. GrapheneOS had every right to ban them because they kept making a scene out of something minor like a non-accepted feature request. Many feature requests get rejected, yet they make this whole drama about it and continue to do so.
On top of all that, they link misinformation and harassment about the GrapheneOS project in their blog post. The videos they link from content creators contain bullying and fabrications about the project and the founder. They are also entirely unrelated to how they dealt with the issue on the issue tracker.