Nick, sorry, forgot to answer the last part or your email about reason etc on fork:
First of all, we haven’t announced it yet. We want to get it to “rc1” quality first before making it public. And we had to get a name (which was a painful slow process and we are still making sure this name isn’t violating any trademarks etc). Name is probably the more important as the github location will change again if we have to rename again. In general, the idea on the fork was to try a different model of developing similar to what was discussed last year (and blocked by Paul’s veto) for the Quagga community. We hope to get a much faster turnaround of new features and fixes into the code. There are several companies interested in Quagga, but see it as abandoned because of the slow speed. We try to change this by automating more, have more maintainers and simple processes on getting code into the project. But everyone is welcome to join. - Martin On 11 Jan 2017, at 22:05, Nick Hilliard wrote: > Martin Winter wrote: >> I don’t like to have this discussion in privacy - this isn’t about >> me. Maybe I did something stupid or you (or community?) decided on >> new rules for who should be on it. I think it would be beneficial to >> everyone to have make it public on who is on the list and probably >> why they are on the list (so it makes somehow the selection more >> transparent. > > Martin, > > Quagga was forked recently: github.com/freerangerouting/frr > > The commit logs in FRR show a good deal of activity since the split, and > the freerangerouting.com domain seems to have been registered by Netdef. > > Usually forks happen after a breakdown of confidence and/or trust in the > original project. Without prejudice to whatever changes may have been > made to the [email protected] email address, it looks like there has > been a serious breakdown of communications. > > It would be helpful if there were some public discussion about what's > happened, and why. There are a lot of people who depend on the quagga > code base, and trust in community projects depends on transparency. > > Nick _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
