News for hackers. Stuff that matters.
Re:PolyMC compromised by rogue developer having unabomber ma... by nalllar on Monday October 17, 2022 @08:25PM (#33241445)
There is a big difference between "did not adopt a different CoC" and "removed all the other maintainers from the project and unilaterally deleted a CoC which had been around for a long time".

As far as I can tell, your message is itself misinformation.

Re:PolyMC compromised by rogue developer having unabomber ma... by wisnoskij on Monday October 17, 2022 @09:13PM (#33241812)
If you look at the github history, it looks like people were literally griefing and deleting all of polymc. So it looks like he did not remove developers until after they threw a temper tantrum and started trying to destroy the project. What is a owner supposed to do when people you gave authority to start accepting PRs that delete all the content or replace the readme.md with trolly memes and harassment?

OR maybe some were removed before. All I know is clearly this targeted harassment campaign are not being forthright and truthful, otherwise the github history would not show what it shows.

Re:PolyMC compromised by rogue developer having unabomber ma... by None4U on Monday October 17, 2022 @09:45PM (#33242019)
Can you link to which commit you're talking about? Have you verified it's not from a fork or a PR?
Re:PolyMC compromised by rogue developer having unabomber ma... by wisnoskij on Monday October 17, 2022 @10:02PM (#33242114)
Hmm, maybe I just dont understand github. I have only ever done one PR. I see people approved (https://github.com/PolyMC/PolyMC/pull/1243) and took that to mean PolyMC devs approved it, but maybe the forker approved his own fork and that has nothing to do with polymc devs?
Re:PolyMC compromised by rogue developer having unabomber ma... by Nullabillity on Monday October 17, 2022 @09:50PM (#33242055)
This is just... not true? The README.md history[0] shows that it was last updated in august.

[0]: https://github.com/PolyMC/PolyMC/commits/develop/README.md

Re:PolyMC compromised by rogue developer having unabomber ma... by wisnoskij on Monday October 17, 2022 @10:06PM (#33242136)
It is possible I dont understand how GH works. I apologies if I was wrong. I was talking about (https://github.com/PolyMC/PolyMC/pull/1243), which got 2 approvals. But it is possible I dont understand what approvals are, but to looks to me that people with authority on polymc to make changes approved of troll/destructive changes. But I am not an GH expert, maybe you dont need authority approve a PR that deleted the entire project and completly changes the readme?
Re:PolyMC compromised by rogue developer having unabomber ma... by Macha on Tuesday October 18, 2022 @07:17AM (#33245623)
Anyone on GitHub can give a grey checkmark approval. It's basically just a thumbs up. The green checkmark approvals are the ones given by people who at time of approving had project approval permission and only these green checkmark approvals have any mechanical effect.

Additionally, everyone who has ever contributed to the project gets a "Contributor" tag on their profile (current recognised contributors with permissions get a "Member" tag). You can see the trolling PR authors and approvers lack those.

So no, the trolls, including those giving the grey checkmark approvals, are not the former maintainers.

Re:PolyMC compromised by rogue developer having unabomber ma... by IAmLiterallyAB on Monday October 17, 2022 @09:53PM (#33242067)
I see nothing like that in the Git commit history? What are you talking about?

Edit: it looks like some randos opened some PRs in the past couple hours. But that was after he already went rogue and kicked everyone?

Re:PolyMC compromised by rogue developer having unabomber ma... by wisnoskij on Monday October 17, 2022 @10:08PM (#33242156)
I apologies if I just do not understand how the GH PR system works. I see approved/reviewed troll PRs. Maybe randoms can review/approve PRs? I assumed they had to be devs to approve PRs.