[SiriusCon 2018] Closing session - Live Community Survey
1 like105 views
The document details the closing session of a live community survey concerning the Sirius project, highlighting its history, participation, and contributions since its inception. Key community feedback includes preferences for release frequency, compatibility between web/rcp flavors, and focus areas for future development. Upcoming events include an extended community survey and a designer workshop planned for Q1 2019 in Paris.
[SiriusCon 2018] Closing session - Live Community Survey
- 1. Closing Session Live Community Survey Pierre-Charles David Sirius Project Lead 5th December, 2018 @_pcdavid | pierre-charles.david@obeo.fr Stéphane Bégaudeau Web and Modeling Consultant 5th December, 2018 @sbegaudeau | stephane.begaudeau@obeo.fr
- 3. A global community 200+ registrations 33 countries 5 continents
- 6. Live Community Survey In which year was Sirius open-sourced and became an official Eclipse project? 1. 2009 2. 2013 3. 2015
- 7. Live Community Survey ● Eclipse project created in June 2013 ○ project started in 2007 ● Since then: 50 versions released ○ 11 major/minor, 39 maintenance ● 31 contributors, 5000+ commits ● 1.5M SLOCs (incl. comments) ● 6,300 automated tests run daily
- 8. We are currently making two major releases every year, and plan to add a third one. How many yearly releases do you feel is the best for you? 1. One: I don’t have time to integrate more versions 2. Two was fine: do not change anything 3. Three (or more): release early, release often! Release rhythm Live Community Survey
- 9. Web/RCP Compatibility Live Community Survey How much do you value compatibility/interoperability between the RCP and web flavors? 1. It’s essential to keep the two flavors as compatible as possible, even if it means the web version is more complex and takes more time 2. It’s not critical: move to the web full speed ahead and don’t slow down or limit the potential of the web version for the sake of compatibility concerns
- 10. For the web flavor, which use case should we focus on first? 1. A complete, ready-to-use modeling environment that can be used directly by end-users 2. A set of reusable components & services/APIs that I can embed into larger web applications (e.g. Eclipse Che or your own web apps) Modeling Environment vs Reusable Components Live Community Survey
- 11. Should we focus first on the end-user experience or the developer experience? 1. Developer first: favor features to create and integrate web modelers (from odesign authoring to webhooks and DevOps) 2. End-User first: favor sophisticated features for power users (e.g. search, batch editing, complex layouting) Developer first vs End-User first Live Community Survey
- 12. Next major feature after diagrams Live Community Survey After diagrams, which existing feature do you want us to bring to the web? 1. Tables & Trees 2. Properties Views 3. Text editors (LSP) 4. Code generation (Acceleo) 5. Document generation (M2Doc)
- 13. To infinity and beyond! Live Community Survey Moving to a client/server architecture with modern web browsers opens lots of opportunities for new features. Which of these feel the most exciting to you? 1. New kinds of representations (3D, maps, etc.) 2. Mobile devices support 3. Collaboration (multi-cursors, chat, etc.) 4. Integrations (Slack, Trello, Office365, etc.) 5. Sirius-as-a-Service (cloud hosting)
- 14. Farewell ● Thanks again for your participation and feedback! ● What’s next: ○ participate to the full community survey (soon) ○ 1st Obeo Designer Consumer Workshop, Q1 2019, Paris twitter.com/eclipsesirius linkedin.com/company/obeo blog.obeo.fr sirius-dev@eclipse.org contact@obeo.fr