SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Use OpenUse and benchmark open
source software by default. When starting a new initiative, always evaluate open source options before going to reinvent the wheel. (e.g., if redis doesn’t work for you, you better have solid evidence)
Define Secret Sauce Don’t open
source anything that represents a core business value. Define your secret sauce sothere’s a shared understanding that can guide decisions. Embed this secret sauce within your culture and company via training.
Assume Open Assume that what
you are developing will beopened in the future. Pretend the whole world will be watching. Use reasonable third partydependencies to prevent pain down the road. (we mostly use Apache’s Third Party Guidelines as a starting point)
Default to GitHub The GitHub
community is the largest open sourcecommunity, with over three million users. You would be stupid to ignore that fact. Embrace social coding tools to lower the barrier to contribution and participation.
Foundations are Good* We just
prefer not to default to them. We view them as a place for stable projects that growinto maturity, not to incubate new projects. Ourgoal is to gain traction first as fast as possible. If not, fail fast and carry on.
Be PermissiveFor outbound open source
software, we default toOSI permissive licenses (the ALv2 in the majority ofcases). We do this so we can maximize adoption and participation, which we favor instead of control.
Notes from Antirez (1) “First
of all, open source for me is not a way to contribute to the free software movement, but to contribute to humanity. This means a lot of things, for instance I dont care aboutwhat people do with my code, nor if theyll release back their modiﬁcations. I simply want people to use my code in one way or the other. Especially I want people to have fun, learn new stuff, andmake money with my code. For me other people makingmoney out of something I wrote is not something that I lost, it is something that I gained.” See http://antirez.com/news/48
Notes from Antirez (2)1) Im
having a bigger effect in the world if somebodycan pay the bills using my code.2) If there are N subjects making money with my code,maybe they will be happy to share some of this moneywith me, or will be more willing to hire me.3) I can be myself one of the subjects making moneywith my code, and with other open source softwarecode.For all this reasons my license of choice is the BSDlicensed, that is the perfect incarnation of do whatever youwant as a license.” See http://antirez.com/news/48
Acquire and Open* Include open
sourcing software in M&Adiscussions, especially if you’re mainly acquiringtalent or shelving the product. There’s no need for software to go to waste.
Acquire and Open: Clutch.IO See
http://engineering.twitter.com/2012/10/open-sourcing-clutchio.html See http://www.prweb.com/releases/2012/10/prweb10067693.htm
Measure Everything If you can’t
measure what you’re doing, you haveno idea what you’re doing. We measure everythinginside of Twitter (affectionately called birdbrain) and make it accessible to everyone.
Pay it Forward Support open
source organizations and projects important to your business, it’s theright and smart thing to do. This can be financiallyor simply staffing projects that are strategic to you.
Open Source Craft* Use Open
Assume Open Deﬁne Secret Sauce Measure Everything Default to GitHub Default to Permissive Acquire and Open Pay it ForwardNote: This fits in a tweet
Not all process is bad!
“process is an embedded reaction to priority stupidity” True. Remember the history of surgery? Ignaz Semmelweiz (hand washing) Surgery checklist: Glad your surgeon washes hands?Even with surgery process, metal objects still are left in people :) See http://many.corante.com/archives/2003/09/17/process_is_an_embedded_reaction_to_prior_stupidity.php See http://en.wikipedia.org/wiki/Ignaz_Semmelweis
Automate Quality Checklist Tooling to
check for baseline “quality” before we open √ README √ LICENSE √ CONTRIBUTING.MD √ .travis.yml √ Avoid KEYS / sensitive bits √ Avoid GPL License Family Attempts to build and posts results in JIRA. Enforces and teaches good practices.
Automate Sourcing for Hiring Let’s
scale hiring a bit! Run monthly queries on contributors to our open source projects and projects of interest. Hand it off the Recruiting and the ATS.It’s hard enough to find good talent, why not hire from open source projects of interest.
Automate Reporting / Metrics Send
out weekly reports based on: Open Sourced Projects (what opened) Top Committers (commits+issues closed) Releases (assumed via git-tag) Contentious Issues (issues with most comments) Top Watched Project (most stars) Top Forked Project (most forks) Track trends. Motivates contribution.