Announcing the Redwood project
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Announcing the Redwood project

on

  • 628 views

A lightning talk from OSCON 2011 calling for help with the Redwood Project.

A lightning talk from OSCON 2011 calling for help with the Redwood Project.

Statistics

Views

Total Views
628
Views on SlideShare
628
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Announcing the Redwood project Presentation Transcript

  • 1. Announcing theRedwood Open project
  • 2. Toward solving the code of conduct problem.
  • 3. Anti-social behavior is detrimental to communities.
  • 4. It drives existing members away.
  • 5. It scares newmembers away.
  • 6. (Projects require a constant flow ofnewcomers to live,thrive and survive.)
  • 7. It gives your project a bad reputation.
  • 8. “Yeah, that’s just how those guys are.”
  • 9. For project leaders, dealing with the behavior sucks.
  • 10. It takes time away from real work.
  • 11. Who wants to write acode of conduct for a conference?
  • 12. Who wants to writepolicies for a mailing list or IRC channel?
  • 13. Who has time to?
  • 14. But these aresolved problems.
  • 15. Ex: OSBridge havepublished their code of conduct for use.
  • 16. Even then,tracking down suitable documents is time-consuming.
  • 17. What to do?
  • 18. I’m starting a project called Redwood.
  • 19. Redwood wants to help leaders create strong, lasting projects.
  • 20. (You know?Redwood trees? Strong?Last a long time?)
  • 21. Redwood’s firstdeliverable will be a code of conduct.
  • 22. It will be a named entity that projectsadopt like a license.
  • 23. Mailing lists could say “We adhere toRedwood Mailing List Policies v1.0”
  • 24. Project websites could have a badge saying “We are a Redwood Project”.
  • 25. The Redwood badge would let newcomersknow the project takes community seriously.
  • 26. A kind of “GoodHousekeeping Seal OfKeeping Things Civil.”
  • 27. Note that this is notjust for Perl projects.
  • 28. (Last week, Rasmus had to tell the PHP dev list not to call each other assholes.)
  • 29. We can help all open source projects.
  • 30. Redwood has other goals as well.
  • 31. We will be a repositoryof information to help projects with other Solved Problems.
  • 32. But the policies/codething is Numero Uno.
  • 33. I’m looking for help on the project.
  • 34. I’ve been roundingpeople up all week.
  • 35. I know the objections to this idea.
  • 36. “But you can’tchange people!”
  • 37. No kidding.
  • 38. I want to make it easier for leaders to manage their projects.
  • 39. “Dude, people willalways be like that. Live with it.”
  • 40. I get that. But I think we canstill improve things.
  • 41. Some of you think I’m just whining.
  • 42. That’s OK, too.
  • 43. But for the rest of you,
  • 44. who want to help improve the opensource community
  • 45. and make it easier forprojects to do the same
  • 46. please come talk to me.
  • 47. Andy Lesterandy@petdance.com(I’m pretty findable)
  • 48. Let’s improve our little slice of the world. Thank you.