Re: [trinity-devel] how to prevent a hugs/freebsd fiasco in trinity

Hello "Physical contact and simulated physical contact (e.g., textual descriptions like "*hug*" or "*backrub*") without consent". Agree with you that the FreeBSD's New Code of Conduct overreaches out of place. Desagree with you that this "clarifies" that horizontal organizations are bad and that software projects work better with a vertical structures with a benevolent dictator. But where FreeBSD fails, similar organizated projects as Debian or Gentoo work fine. There are long-standing free software projects with vertical organizations but also ones with horizontal organizations. What is failing in Trinity is the number of developers and collaborators, and this will not be changed by a organization modification, additionally I think that a vertical organization with censoring dictators tends to discourage potential collaborators. The praiseworthy Slávek/Timothy/others' dedication can be recognized without creating censoring or hierarchical figures. Likewise, the continuity after the disappearance of some person (exchange of passwords,...) can be guaranteed without the need to create vertical organizations. If a horizontal organization guaranteed the future of the Trinity project, it would be the first person to sign it even if it touches me the lowest post in the hierarchy, but that is not the case. Affectionate hugs to everyone! :) ________________________________ De: "wofgdkncxojef(a)gmail.com" <wofgdkncxojef(a)gmail.com> Para: trinity-devel(a)lists.pearsoncomputing.net Enviado: Sábado 10 de marzo de 2018 23:35 Asunto: [trinity-devel] how to prevent a hugs/freebsd fiasco in trinity Hi every one. I'm sure you all know about the storm about the new code of conduct in freebsd. (you need to ask consent in advance before sending virtual hugs.... etc) This is happening, because their governing structure is a committee. They are making an experiment in politics, with rules and votes and consensus etc.... You can easily avoid this, by just having an enlighten dictator. A bit like Torvalds with linux. In the Linux project, there is no committee and votes and politics. Linus has the final word. An open source project is not like in real life, if you think the benevolent dictator is a dick, you just tell him and fork. So, trinity should remain a dictatorship. Even if the project got big. I'm assuming the dictator is petersons. And when he leaves, he must appoint a successor. If that ever turned to shit, people would have to decide to fork then. (Roman emperor Caligula once, ordered his men to collect seashells) A common mistake with projects/businesses, is that the founders don't think through about what happens after they are gone. hugs :P --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting