4 ms·
I find the "rant" and the linked post by Nikos Mavrogiannopoulos sadly missing any direct details over what the actual issues are. From reading it, one could ge
by belorn 14y ago
I find the "rant" and the linked post by Nikos Mavrogiannopoulos sadly missing any direct details over what the actual issues are. From reading it, one could get the idea that all the problem stems from GNU coding standard being archaic and not updated for modern programming.
Okey, I am skipping all the rant about FSF not funding software projects to pay developers, or that the GNU brand is not "hot", but both feels a bit silly. The hotness of a brand is transient, and in reality, only a handful number of brands inspires users and developers. I can't see how GNU would be more or less hot than say Gnome, KDE, or apache which each has a large number of projects under them. As for funding, since when did any of those organizations actually fund the projects? They role is provide help in setting up funding systems, help with tax declarations and provide further legal help.
Thankfully, the last link in the end (http://lwn.net/SubscriberLink/529522/854aed3fb6398b79/ http://lwn.net/SubscriberLink/529522/854aed3fb6398b79/) looks to bring some light of what the actually issues really are: copyright assignments being US only, who the "owner" of a community project is, Nikos' feeling that he aren't getting any tangible benefits from being under the name GNU, and last a request for more transparency in the GNU projects decision process.
As for those reasons, there are two I agree with and two I don't. Firstly, Copyright assignments being US only is bad and shows an inflexibility a non-profit foundation should not have. Their role is to help projects, and thus should be as flexible as possible and thus provide equal possibility to assign copyright to US or EU. Second, as for who the owner of a community project is, the answer should stare the developers in the face. It should always be the community (developers and users) that "own" the project and decides its fate. If Nikos' announcement had included a decision by the community (preferable in a transparent manner), it would had been hard for GNU to object. Third, Nikos' feeling that he aren't getting any tangible benefits from GNU are his to have, but legal assistance is something many projects value. If a project has no need for legal assistance, no need for help in creating donation systems, and don't feel a threat about lawsuits against individual developers, then a foundation such as GNU, Apache or other similar organization are not going to give much tangible benefits. Fourth, in regard to more transparency in the GNU projects decision process, I can only agree with Nikos. The corner pillar in a community is transparency, and GNU should be fully aware of this. If there are discontent growing because of an lack of transparency, it should be addressed and fixed with high priority.
- CJefferson 14y agoJust on your comment of legal support. One of his major complaints is that actually he is not getting the legal support he wants, and he thinks that he could do better by himself.
- belorn 14y agoIs there a place where this complaint is posted? I know about the one time in regard to Werner Koch, and in which a legal problem arrived, and was subsequently fixed, but where FSF did not inform Koch about the fixing. To my understanding, that was a mistake in communication from FSF and was later resolved.
- clinth 14y agoThe clearest example is from the LWN article you referenced. > "Once a developer assigns copyright, they are at the mercy of the assignee to enforce the copyright. In this particular case, one can speculate that the failure to pursue the violation was likely a shortage of human resources. As Richard noted, "We have staff for GPL enforcement, […] but there are so many violations that they can't take action on all."" As the LWN article notes, statements like this are a huge distance between FSF in practice, and FSF's own reasoning behind assigning copyrights to it (http://www.gnu.org/licenses/why-assign.html http://www.gnu.org/licenses/why-assign.html). When a project has assigned copyright to FSF, the project workers have no recourse when the copyright holder opts not to fulfill its part of the bargain.
- belorn 14y agoThat is a general complain which has a general answer. If you let someone do your legal work, it might not be done with the same priority as if you did it yourself. But, general handwaving aside, has there been a case with GNU sed or gnutls in which the legal work was done in a less than satisfactional way?