On Sunday, March 2, 2014 5:27:39 PM UTC-6, cptstubing wrote: > > > When I was considering the situation, I too had a vision like what Andre > mentioned -- dozens of forked projects and no clear direction for the average > user or even the empowered one who simply doesn't have the time to evaluate > all of the choices. Further, I can envision a scenario where someone does > take the helm of the project by nature of his/her leadership skills, yet > lacks Bram's vision and steers us all into the rocks. > > As for the assertion that governance by committee does not work, I challenge > you to consider the longevity and the vastness-of-reach in each and every one > of our lives that has come out of organizations like ANSI, ISO, and IEEE. > Consider, also, POSIX: It's a mix of certain things that were not > standardized, but were essentially de facto standards of a certain epoch, and > other guidelines that were decided upon by committee. Even vim itself is > mostly compliant with the POSIX vi standard, and effort was clearly made to > document the places where it breaks that standard (vi_diff.txt). >
A committee certainly could govern development, voting if needed when consensus cannot be reached. There are some good ideas in this online book about managing an open-source project: http://www.producingoss.com In particular: http://www.producingoss.com/en/social-infrastructure.html -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
