One of the stated goals of the OPNFV project is to "work with upstream projects to coordinate continuous integration and testing while filling development gaps". To do this successfully, it is important to have a framework for approaching projects you have not worked with before. Each project has its own culture, norms and participants, and effecting change in a project means more than turning up with a laundry list of feature requests.
This session will provide you with that framework. The target audience is engineers interested in improving projects like Openstack, OpenDaylight and OpenvSwitch in the context of the OPNFV project. The subject matter will not be technical, but will assume a solid background in software development methodologies. The syllabus will cover some or all of:
- Framing: How to think about interactions when you are a stranger in a strange land
- Navigating the Unknown: Identifying infrastructure, community processes and key contributors in projects.
- Shortening the feedback loop: How to maximize your chances of getting code and ideas accepted upstream
- Lots of examples and case studies identifying best and worst practices
By the end of the session, attendees will have a clearer understanding of what is involved in developing features across multiple projects, in a way in which that code will be accepted upstream and integrated into a stable release.
