5 ms·
I’m not sure what to think of this. The only thing that struck me was that dnf “deeply regrets” their actions but also makes maintainers opt out instead of opt
by duncan-donuts 5y ago
I’m not sure what to think of this. The only thing that struck me was that dnf “deeply regrets” their actions but also makes maintainers opt out instead of opt in. Maybe that makes the most sense at this point to cause no disruption to the maintainers that don’t mind. It just kind of felt like a whole lot of nothing I’d you deeply regret it but didn’t undo your action. Idk maybe I’m in the minority.
- lowercased 5y agoTaking another automated step with the account before getting permission would just be the same thing all over again, no? i get your point, but they're acknowledging that making unrequested changes was bad. doing it again would contradict that, I'd think.
- nathanaldensr 5y agoYeah, maintainers are already by this point well aware of what's going on and are basically looking for a reason to claim ownership of their projects again. I don't think this is an unreasonable fix for a one-time mistake (even though it was severe). If I were a maintainer I'd be removing that dnfadmin bot ASAP anyway.
- lostmsu 5y agoIf my understanding is correct they can initiate a move out on their side, and owners would have to approve it in GitHub. That would be better than forcing everyone to email them.