Conversation
Notices
-
@mangeurdenuage this seems like quite immature stuff (and no, I'm not being transphobic). If I were GNU I'd just fork libreboot from before the shitstorm, rename it to "gnuboot" or whatever and find a new maintainer. Even if there is a genuine discrimination case underneath all of this why drag the entire community into it? Surely if it's a personal disagreement then the relevant people should figure things out between themselves.
- Claes Wallin (韋嘉誠) repeated this.
-
@bob @mangeurdenuage That's assuming anyone cares enough about libreboot to want to take over maintainership and probably get in a lot of trouble with Ms Rowe.
-
It's also about the technical capacities I think.
Not everyone goes on hardware level dev.
-
@verius @bob @mangeurdenuage When you give a project to GNU, part of the agreement is it is *theirs* now. Seems like Rowe doesn't understand that, but then given she's acted less mature than the four year old kid one of my house mates has that's not terribly surprising.
-
This ^
Leah should have read to what happened to nano.
-
@mangeurdenuage Does libreboot contain actual development though? I thought it was just about removing proprietary bits from coreboot and adding GNUisms like Makefiles and texinfo.
-
@verius @mangeurdenuage From what I read, apparently there's changes to build system and stuff, I'm guessing things that ease librifying.
-
@maiyannah @bob @mangeurdenuage @verius It's different from project to project. GNU has FSF-owned (c) projects and non-FSF-owned projects.
-
@mangeurdenuage @maiyannah Thanks for mentioning nano, I hadn't heard about that kerfuffle. Lots of discussion at http://qttr.at/1hnc (HN).
-
@mangeurdenuage @maiyannah (For anyone else who didn't know: Apparently they left GNU, or not, depending on whom you ask, then came back.)
-
@clacke I'd heard about the leaving part.
-
@lnxw48 The #gnunano folk thought they had to assign copyright, got better informed. https://pumprock.net/clacke/note/YE0z5ZZiR5-2SwruGtOGOg