[dev] why fork Quagga?

[JR Rivers]

Combining the former articles with Lou and Vincent's comments is pretty
telling.  Due to circumstance, there was a VERY large backlog of
outstanding patches against Quagga at various companies/institutions.  The
group was interested in both getting through that backlog as well as
creating a fast paced, community oriented project, and the output and
nature of the project are a reflection of the developer's efforts.



On Tue, Apr 3, 2018 at 2:07 AM, Vincent JARDIN <vincent.jardin at 6wind.com>
wrote:

> Le 02/04/2018 à 19:35, Carla Schroder a écrit :
>
>> If there is anything else you think is cool and needs to be shared,
>> throw that in too.
>>
>
> I think you should analyze the pace of patches from the git's repos, for
> the features and for the bug fixes integration.
>
> Frankly, no-one likes forking (code and community!), but sometime it helps
> to reorganize some projects with some different visions. Look in the past
> to the *BSD for instance... Then, it can be good to have some forks: each
> fork can be a sandbox with some different models of organizations. Down the
> roads, any "goods" (protocols, design improvement, tools, etc.) from any
> "forks" get usually cross merged.
>
> best regards,
>   Vincent
>
>
> _______________________________________________
> dev mailing list
> dev at lists.frrouting.org
> https://lists.frrouting.org/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20180403/a1b3fb02/attachment.html>