[quagga-users 14791] Re: FRR or Quagga

Richard Palmer <[email protected]> Mon, 28 Aug 2017 22:57:53 +0100
Newsgroups gmane.network.quagga.user
Message-ID <[email protected]>
With the bgp bug (and other issues) I’m certainly happy to help / work on fixing this as needed. As well as other work 

I do have a c background but not yet a knowledge of quagga itself. If someone is willing to help me get started I’m certainly happy to support the project moving forward. 

I’ve used quagga for some time and I have s fair bit of loyalty to it if the issues I mentioned on the list earlier can be resolved. 

Richard Palmer | Director | Merula Limited
Company Registered in England and Wales No. 3243995
5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS
Phone 01480 222940 | Support 0845 330 0666
Support Email [email protected]

> On 28 Aug 2017, at 21:40, Paul Jakma <[email protected]> wrote:
> 
>> On Mon, 28 Aug 2017, Alexis Rosen wrote:
>> 
>> We're pretty heavily invested in Quagga, and unfortunately, it has had some serious issues over the last few releases that have not been addressed. Most obviously, the BGP issue that has been reported time and time again in this list, that appeared after 0.99.24.1, stands to this day in 1.2.1. I would not at this time be willing to risk a new deployment on the current release.
> 
> It's likely an FRRers bug, annoyingly. Also, whichever commit it is, probably easily reversable / not important.
> 
> If you can trigger it reliably, please step through the commits and identify the breaking one. The bug report already lists one suspect commit ID.
> 
>> I'm also very concerned that there is no future in Quagga because all the developer momentum
> 
> Well, those who are concerned should then try avoid that future, by working on Quagga, if they can. The only conditions are:
> 
> - The project must serve a wide range of interests, and be resistant to
>  capture (e.g. by well resourced interests, who can pay off other
>  participants).
> 
>  To my thinking, that means the top-level/last-resort governance must
>  be by consensus, weighted towards some longer-standing interests (the
>  latter is something that is normal in almost every social system I can
>  think of that has any degree of order). Even if day-day matters are
>  handled by other means, such as technical commitees. Benevolent
>  dictator works for some other projects, but it's hard to reliably
>  replicate.
> 
>  If people have better ideas, they are free to /persuade/ others
>  involved of the merit of them.
> 
> - The project must be conservative about legal risks, and do its best to
>  serve the interests of _ALL_ copyright holders.
> 
> - People should deal with each other fairly and straight-forwardly.
> 
>  §2.7.5 of the ZeroMQ 4C has some very good language on this:
> 
>    https://rfc.zeromq.org/spec:42/C4/
> 
> Anyone who wants to work on Quagga on those terms will be welcomed and given whatever access they need.
> 
> regards,
> -- 
> Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
> Fortune:
> If it smells it's chemistry, if it crawls it's biology, if it doesn't work
> it's physics.
> _______________________________________________
> Quagga-users mailing list
> Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-users