What benefits does a collaborator receive?
Strategic value - be more closely involved than open source email lists allow with those who are leading the SDN and NFV revolution. Gain better understanding possible of where SDN and NFV initiatives are heading, and where the leading service providers and their vendors are going.
Business value - open up new business opportunities for your company by being involved in the transition to SDN and NFV - align your company with the leaders in this space - get involved in new business initiatives
Marketing value - have your logo placed with those of the leaders of the SDN and NFV revolution - be visible at industry events by having your logo displayed with the partner and collaborator logos of the CORD project. Be visible to new business partners in presentations and demonstrations. Be recognized as an innovator.
Technical value - learn from the experts in SDN and NFV. Work closely with the architects and visionaries of this revolution. Understand the possibilities for transforming your organization early as a result of advanced knowledge.
A full listing of benefits is available on the ONF's Membership Info page.
What is required of a collaborator? The main requirement is to bring value to the CORD Project and community. How can you do that?
By dedicating resources to help with CORD – in development, testing, documentation, or any number of other areas.
By integrating CORD with your products. Integrate CORD into your products and help CORD become the platform of choice for service delivery.
By deploying CORD in your networks. Use CORD to build an SDN and/or NFV infrastructure.
Contribute and maintain source code on behalf of the CORD project.
What is the process to become a collaborator? It is simple:
Send a proposal to david at opennetworking dot org
Fill in the template found here. In short, you will be asked to provide:
A short description of your proposal for collaboration. What value do you want to bring to the community? Is it source code? Is it a testbed? Is it a deployment?
Describe what resources you will commit to the collaboration. Is it two full time developers? Four part time test and deployment people? A technical documentation writer? A source code repository? Test cases?
Provide a proposed timeline for bringing this value into the community. What can you commit to the next release? The one after?
The technical steering team will review the proposal within 3 weeks and provide an initial determination. That determination will indicate the level of interest and alignment, and will probably include a number of questions. It may also include a request for a meeting to further discuss the proposal. The steering team will provide an estimate of when a determination can be made if it is not made in the discussion.
Once approved, it is expected that the collaborator will begin executing to the proposal. When the first commitments have been accepted (source code committed and delivered in a release, for example), the collaboration can be announced (perhaps with a joint press release) and the marketing collaborations can begin. The logo will be put onto the CORD web site and the logo will be added to standard presentation templates.
- By becoming a collaborator, you are opting-in to receive occasional emails from ONF about relevant project news and topics. You may choose to opt-out of these communications.