Skip to end of metadata
Go to start of metadata


Open Source Routing (OSR) is an ISC project to assist in improving the quality and broaden the operational applicability of the quagga routing software.

 OSR’s goal is providing the appropriate resources and processes enabling the community to develop a commercial quality, operationally trusted version of Quagga. This version will become a strong stable baseline to enable networking innovation across multiple market segments.

 OSR is not only working with the community of developers and contributors, but also contributing our own resources (testers and developers) in improving Quagga

 All the things we do will be open for community input and the results shared with the community unless there is a specific extenuating circumstance.

 We see quagga as a key element for the evolution of networking infrastructure and want to move it to a commercial quality enabling operational alternatives to existing vendor products, and enabling innovation in academic universities and service providers.

 Our work will be focused on finding and fixing bugs, adding features that fill gaps and helping with merging code back into the common pool for quagga.

How does OSR fit into the community?


OSR sees itself as contributing to the community and not taking it over. We are committed to maintaining the open design and architecture that exists with quagga today. OSR is working with the community to provide the following capabilities:

 a) Community contributed testing - a well defined and reusable test bed to ensure, compliance, interoperability, resiliency, functional viability, and ensure scale and performance on Quagga releases, patches, and bug fixes

 b) Community re-integration - provide guidance and process around release management, such as integration of private, public, and large patches which have been orphaned - not integrated.

 c) provide development resources to fix bugs, and potentially develop and integrate features (based on major customer and community needs).

 When new features are either contributed through OSR or developed by OSR, we will bring the design and the code to the community to discuss and review. In the case of new work, this will be done before development. In the case of finished work, the discussion will need to cover the appropriateness for inclusion in the quagga mainline and things that need to be changed to have it included.

  • No labels