1. Open Source Community
Chris Donley

2. A word about shoes and socks…

3. All I Really Need to Know I Learned in Kindergarten
Share everything.
Play fair.
Don't hit people.
Put thngs back where you found them.
CLEAN UP YOUR OWN MESS.
Don't take things that aren't yours.
Say you're SORRY when you HURT somebody.
Wash your hands before you eat.
Flush.
Warm cookies and cold milk are good for you.
Live a balanced life - learn some and drink some and draw some and paint some and sing and dance and play and work everyday some.
Take a nap every afternoon.
When you go out into the world, watch out for traffic, hold hands, and stick together.
Be aware of wonder. Remember the little seed in the Stryrofoam cup: The roots go down and the plant goes up and nobody really knows how or why, but we are all like that.
And then remember the Dick-and-Jane books and the first word you learned - the biggest word of all - LOOK.”

4. …Extending to Open Source…
The sandbox that’s best is the one with the most kids in it
Especially when everyone brings their toys

5. Open Source Requires Trust
Build Trust to Build Success
13 Specific Behaviors
Talk Straight
Be honest, tell the truth, let people know where you stand
Demonstrate Respect
Create Transparency
Err on the side of disclosure
Right Wrongs
If you make a mistake, correct it. Don’t cover things up.
Show Loyalty
Share credit. Acknowledge other people’s contributions.
Don’t criticize other people behind their back

6. More Trust Behaviors Deliver Results
Get Better (continuous improvement)
Ask for feedback, learn from mistakes
Confront Reality
Address tough issues directly and early
Clarify Expectations
Practice Accountability
Hold others (and yourself) accountable. Take responsibility for results.
Listen first
Try to understand others’ points of view before you speak
Keep Commitments
Extend Trust

7. Open Source Culture Healthy communities foster “GuanXi”
Developers are more like artists than factory workers
Provide opportunities to build “MianZi”
Use common communication tools such as wiki, IRC, Slack even when people work next to each other
Provides transparency
Facilitates onboarding

8. Project Approvals
Open source is a ‘gift’ economy. People write code because it’s valuable to them. Do we want to share it?
In open source, best practices are to default to approving new projects unless they are harmful to the organization
If projects are not accepted, submitters may go somewhere else
They don’t typically abandon the project
Suggested acceptance criteria
Does the proposed project add value (or is it at least neutral to the community and adds value to the contributor)?
Does it overlap with existing projects? 
Is it generally aligned with the architecture / scope of the release?
Will it negatively impact other projects’ schedule?
Does the team have a reasonable project plan given their resources?

9. Cadence/Synchronization
OPEN-O is date-driven (not scope or quality)
Small changes in arrival time can multiply delays if synchronization is poor
Cadence can help minimize waiting
More frequent opportunities reduce impact of a ‘miss’

10. Batch Size Speed vs. Efficiency Fast Efficient
Open Source goal: Minimum viable product

11. Rapid Feedback Cable Labs
Imagine a lottery where tickets cost $3 for 3 digits. Odds are 1:1000 of obtaining a payout. Now imagine that you could purchase digits individually for $1. You purchase the first digit, and only 10% of the time (when the first digit is correct) do you buy the second. Likewise, only 1% of the time do you buy the third (when the first and second are correct). This reduces the expected cost of the ticket to $1.11 ($1+ $1*10% + $1*1% = $ ), 37% of the cost of buying all three digits at once.

12. Law of Diminishing Returns
Cable Labs
Law of Diminishing Returns
Product- market fit and well- defined interfaces
Commercial target
Valu e
Open Source target t0 t1 t2
More value is delivered between 0 and t0 than t0 and t1 or t1 and t2. CableLabs should focus on early-stage work up to t0, and let vendors optimize beyond that point.
Time

13. For more details on Open-O: membership@open-o.org谢谢
For more details on Open-O: