On 11 Jan 2017, at 22:34, Michael H Lambert wrote:
On 11 Jan 2017, at 10:05, Nick Hilliard <n...@foobar.org> wrote:
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 secur...@quagga.net 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.
Forks can also happen when developers decide they want to "monetize"
the code. Yes, it's still open source, but if you want updates in
timely fashion you'll need to subscribe to a maintenance plan. I
agree that the community needs to be kept in the loop.
The problem was really getting the name picked. It was way more
painful than expected. And a lot of the work was done while it was
still called Quagga - and that would have caused a really bad confusion
(and most likely upset Paul for the right reasons).
The rename in the code just got done last weekend (finally).
There are absolutely no plans to monetize the code. There might be
always
commercial spins (i.e. any vendor who provides Quagga or the fork on
their
box) and they may try this, but I’m not sure how legal this is under a
GPL
license.
And Quagga and all it’s forks are locked to GPLv2 or later as it’s
probably
impossible to ever contact all contributors and get them to agree to a
license
change.
Some of the organizational structure behind is still in the discussion
phase at this time. We are trying to find a model where there is no
single
entity able to take over or lock others out of it.
But some of the key differences is trying a different model where
patches
submitted or pull requests get automatically integrated into a
development
branch. Based on what was discussed last year for Quagga.
Anyway, no need to discuss this here in details. Donald posted the list
for the fork. Feel free to join and ask questions there. Just don’t
expect
it all be ready yet.
- Martin
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
