UPDATE: Friday, April 18 is the deadline for submissions.
At this year’s OpenStack Summit we’re going to be offering space to Open Source projects that are important to the OpenStack community. We’re calling it Open Source @ OpenStack, and it’s an opportunity for these projects to hold small design summits with their community members. We’re impressed by the number of projects that have grown in the OpenStack ecosystem, and want to continue the practice we started with StackForge of fostering these projects.
We have space and time available for half day sessions on Tuesday and Wednesday, both morning and afternoon. The purpose of the space is to get developers in the same room so they can plan their development for the Juno release cycle. Rather than being a time to market a particular company or technology, it should be an opportunity communication and goal setting. To achieve these goals, we would like participating projects to use the following guidelines:
- The project needs to be directly related to OpenStack in some way.
- The project must be open source, with source code available and actively developed.
- The work needs to be non-commercial and vendor neutral, although a vendor that sponsors a project can organize the meeting.
- Sessions must be open to anyone who wants to attend. This should be not just an opportunity for core developers to meet, but to also give a venue for people interested in your project to get more information.
- Meeting notes from the design session should be made publicly available.
- The group organizers and participants must adhere to the OpenStack Summit Code of Conduct.
If you have a project that you think qualifies for this space, we invite you to submit a proposal for Open Source @ OpenStack. Update: Friday, April 18 is the deadline for submissions.
- The name of your project.
- A description of the project and how it relates to OpenStack.
- The names and contact information for the organizers commiting to hosting the session.
- Relevant links to project sites such as repositories, bug trackers, and documentation.
- An estimate of the number of developers you expect to attend your design meeting.
- A plan for how you intend to use the time and space.
We want to thank everyone for the time and effort they put into supporting OpenStack.