Slashdot posts a story about how moving from the Red Hat build systems to the Fedora build systems means that through some sort of magic, OLPC is now subject to export restrictions. Here is a hint, OLPC is a US based non-profit and as far as I know, though I am not a lawyer, OLPC is subject to US law in any case. What that says about export restrictions I don’t know – ask a laywer not Slashdot. Add the fact that it is no secret that Red Hat is the creator of the Sugar interface and that the OS is a derivative of Fedora and all you’ve got is FUD. <sarcasm>Oh no Slashdot users don’t spread FUD they only combat it</sarcasm>. The “article” gets it wrong on so many accounts and I am easily reachable via IRC or e-mail (they link to a mailing list post with my e-mail in it) that you think someone might have fact checked. So to set the record straight here is a mini FAQ:
Why did OLPC move to Fedora?
OLPC didn’t move to Fedora. Sugar, the software layer, was already being built on top of the Fedora OS within Red Hat’s build systems. With the merge of Fedora Core and Fedora Extras we felt it prudent to move the Sugar packages to the Fedora infrastructure. This lessens the burden of maintainership as we were branching a lot of packages just so we could build against them. It also gave us access to a legion of Fedora packagers, developers and translators, which has so far payed off very well in terms of quality of the packages.
What does this mean to people in the community?
It means people in the community have more ways to participate. The Red Hat build servers are accessible only to Red Hat engineers, Fedora’s are open. Go here if you want to contribute to the base OS.
What else is gained?
By not reinventing the wheel we free ourselves from having to think about infrastructure such as signing packages or hosting builds which leaves us to think about the forward moving innovative bits.
For more information you can read my post announcing the move.[read this post in: ar de es fr it ja ko pt ru zh-CN ]