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

Announcing the Redwood project

568

Published on

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

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
568
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \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

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

      Clipping is a handy way to collect important slides you want to go back to later.

    ×