Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Thales Inner Source 2017 keynote on JHipster

935 views

Published on

Slides used for the keynote of Thales Inner Source 2017 conference, about JHipster and Open Source

Published in: Technology
  • Be the first to comment

Thales Inner Source 2017 keynote on JHipster

  1. 1. TISS Keynote @juliendubois
  2. 2. Julien Dubois JHipster creator & lead developer Follow me & react to the talk @juliendubois @java_hipster
  3. 3. A few words on Ippon Technologies… Funded in 2003 + 300 consultants Specialized in Java, Cloud & Big Data Focus on innovation and technical expertise Offices in France, USA, Australia
  4. 4. - Creates a full-stack application in record time - Generates a Spring Boot back-end - Generates an Angular front-end - Configures tooling - Provides best-practices and high-quality code - Shortens time-to-market and increases productivity - Brings developer happiness - 100% Open Source - no tricks! What JHipster does
  5. 5. Companies love JHipster - 200+ companies officially listed on http://www.jhipster.tech/ companies-using-jhipster/ - All industries, all countries - Many companies contribute back to the project
  6. 6. Some statistics on JHipster - 19 developers in the « core » team - 380 contributors, including official contributions from Google, Red Hat and Salesforce - 8,600+ GitHub stars - 700,000+ downloads - conferences all around the world
  7. 7. Why Open Source matters - Brings together a large number of developers - Different companies - Different goals - Different skills - Higher quality - Focus on peer review - No hidden code
  8. 8. Legal aspects - Open Source is all about licensing - Being “free” is a consequence of the license - JHipster uses the Apache 2 license - Foundations are great for hosting successful projects
  9. 9. How to run a successful Open Source project?
  10. 10. Drive project awareness - Be popular in the Internet - Social networks:
 GitHub, Twitter - News sites:
 Hacker News, Reddit - Do IRL events - Conferences - Meetups
  11. 11. At the beginning, do guerrilla marketing (yes, that’s +1,500 retweets!)
  12. 12. Focus on the project, not on marketing - Marketing is worthless is you don’t have a great product - The most important keys to success: - Great community - Great code - Lots of releases -> How can you create this great community?
  13. 13. Events and conferences - Meetups and conferences are very important - Not everybody is on Twitter! - We also help people organize their own events - Slides - Marketing
  14. 14. Provide great documentation - Documentation is very important - Help beginners and 
 advanced users - Documentation must be versioned - Let people contribute: the JHipster documentation 
 is also an Open Source 
 project on GitHub - Provide user guides - Video tutorials work great - Our official tutorial has over 90K views!
  15. 15. Make it easy to contribute - “Contributing” guide - Issue and Pull Request templates - JHipster even has a specific sub-generator to help create an issue! - Easy-to-understand code - That’s why we use JavaScript and EJS: not the best languages, but the most common and the easiest to understand
  16. 16. Create a welcoming community
  17. 17. Code of Conduct - Most OSS projects now follow a Code of Conduct - Very important for a lot of people - Our goal is to attract as many talented people as possible - We don’t tolerate brilliant jerks
  18. 18. JHipster Code of Conduct
  19. 19. Managing growth - JHipster’s community has grown so big that it can’t be handled by a single person - This is why we created the “core team”
  20. 20. Organization of JHipster - Meritocracy - People are voted into the core team - Core team members have write access to the code, to the dev mailing list, etc. - Democracy - All core team members are equals
  21. 21. JHipster policies
  22. 22. Quality at scale - Follow the GitHub workflow - Pull Requests, code reviews - Code quality guidelines - Eslint - Sonar - Have a great Continuous Integration system - Release early, release often
  23. 23. Support channels - The main trouble is support - GitHub tickets for bugs - Great for bugs, as it 
 integrates with the commits, 
 code review and CI systems - Stack Overflow for questions - Great for questions and 
 answers, as it has a voting 
 and reputation system - Gitter.im for chat - People helping each other directly - Open discussions on the project
  24. 24. Finding sponsors - People contributing for free are not always enough - Many companies contribute to OSS projects - When they find a business interest on their side - Example: Salesforce provides Heroku support for JHipster - Companies also provide lots of free “gifts” - In exchange of some advertisement/ support, it’s easy to have free credits - Example: Google gives $5,000 of free Google Cloud credits to JHipster
  25. 25. The business of Open Source - Team - 6 core comiters - 2 trainees/year - Investments - 100 KE/year - Marketing support - ROI - Sales - Recruitment - R&D - Consulting engagements - Trainings
  26. 26. More information on JHipster Website: http://www.jhipster.tech/ Code: https://github.com/jhipster/generator-jhipster Twitter: @java_hipster

×