Building Innovation with Open Source Approaches
•
1 gostou•556 visualizações
My talk at TransferSummit 2010.
![How to build innovation using Open Source approaches Paul Fremantle [email_address] @pzfreo / Twitter CTO and Co-Founder, WSO2](https://image.slidesharecdn.com/transfersummit-fremantle-100624092756-phpapp02/85/Building-Innovation-with-Open-Source-Approaches-1-320.jpg)
![Me ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Building Innovation with Open Source Approaches
Semelhante a Building Innovation with Open Source Approaches (20)
Mais de Paul Fremantle
Mais de Paul Fremantle (19)
Último
Último (20)
Building Innovation with Open Source Approaches
- 1. How to build innovation using Open Source approaches Paul Fremantle [email_address] @pzfreo / Twitter CTO and Co-Founder, WSO2
- 4. How do you encourage innovation?
- 13. Why the Apache License?
- 14. Usability U.S. Mission Photo: Eric Bridiers
- 15. Open Source Processes Photo http:// garth.vox.com /
- 16. Open Development
- 22. eBay
- 24. WSO2 Carbon
- 26. Cloud Native
- 27. WSO2 Stratos: Platform as a Service
- 30. Thank you
Notas do Editor
- We let our users drive the development Shorter planning cycles than normal Balance vision with demand We do not have a separate support team Developers provide support We do have a separate QA team But developers test their systems thoroughly Hugely automated test and build We do not have a separate training/consultancy team Our customer architects contribute to the code Our developers do training and on-site consultancy We let our users drive the development Shorter planning cycles than normal Balance vision with demand We do not have a separate support team Developers provide support We do have a separate QA team But developers test their systems thoroughly Hugely automated test and build We do not have a separate training/consultancy team Our customer architects contribute to the code Our developers do training and on-site consultancy
- We do everything on mailing lists Almost all our mailing lists are open Architecture Dev lists We get mails from concerned people who think there is a problem with our infrastructure Open Bug Tracker Open build processes What is closed? Customer support system Support mailing list Sales and marketing