Back to Blog Entries
Updated plans for ONOS Build event in November
August 16, 2016
Thank you to everyone for providing feedback on our strawman plan for the ONOS Developer Event. We’ve taken those suggestions and have updated our plans and we want to share that back out for another round of discussions.
Feedback on strawman plans
There were a few things we heard from people about our draft plans:
- We hadn’t been sure what to call this event and Viswa suggested calling it “ONOS Build”. This name captures well the interactive/collaborative nature of our event and it really struck a chord with a wide group of people.
- We had called out having 50% of the time for hacking (with the other 50% split between social activities and presentations). We heard clearly from many people that it would be much more valuable to have time to interact with other community members to showcase what people are working on, learn about other people’s use cases and projects and have conversations around challenges, opportunities and other issues. So we’re now thinking of having this time focused more broadly on interactivity and hacking may be one of those interactive activities
- We got supportive feedback about the rest of the plans, so we think we’re on the right track. So for next steps, we want to dive into more specifics around the schedule so we can start getting thoughts and comments about the agenda.
First pass at schedule
Please check out the first pass at a detailed schedule below and provide comments and suggestions. Do you agree or disagree with anything? Is there anything you would change, rearrange, remove or add?
View the ONOS Build 2016 schedule & directory.
We’re getting close to the point where we need to start finalizing some details, such as location and dates, so we’ll move forward with that and share out updates. Going forward we’ll focus our discussions mostly on sorting out other details, such as the exact agenda for the event. If you have ideas, comments or suggestions on the draft agenda above, please comment in the thread on the community-team mailing list.