A lightening talk that I gave at Mountain West Ruby Conf about how I feel that the OSS contribution system should work.

1. BDD for the OSS
Contribution Process
Mike Gehard, Software Engineer mgehard@pivotallabs.com @mikegehard

3. Feature:

4. Feature:
As a prospective open source contributor

5. Feature:
As a prospective open source contributor
I would like to be able to easily contribute to a project

6. Feature:
As a prospective open source contributor
I would like to be able to easily contribute to a project
In order to give back to the community

8. Scenario: Easily set up a development environment

9. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on

10. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo

11. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo
And I cd into the project

12. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo
And I cd into the project
And I run “bundle install”

13. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo
And I cd into the project
And I run “bundle install”
And I run “rake”

14. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo
And I cd into the project
And I run “bundle install”
And I run “rake”
Then I should see all of the tests pass

15. Scenario: Easily set up a development environment
Given there is an OSS project that I want to work on
When I clone the git repo
And I cd into the project
And I run “bundle install”
And I run “rake”
Then I should see all of the tests pass
And I can start working

17. Scenario: Contribute code

18. Scenario: Contribute code
Given I have green tests

19. Scenario: Contribute code
Given I have green tests
When I write tests for the functionality I want to add

20. Scenario: Contribute code
Given I have green tests
When I write tests for the functionality I want to add
And I watch them fail

21. Scenario: Contribute code
Given I have green tests
When I write tests for the functionality I want to add
And I watch them fail
And I write code to make them pass

22. Scenario: Contribute code
Given I have green tests
When I write tests for the functionality I want to add
And I watch them fail
And I write code to make them pass
Then I can easily push code to a fork of the repo

24. Scenario: Have my commit integrated in the project

25. Scenario: Have my commit integrated in the project
Given I have have submitted a well tested patch

26. Scenario: Have my commit integrated in the project
Given I have have submitted a well tested patch
When I wait about a week

27. Scenario: Have my commit integrated in the project
Given I have have submitted a well tested patch
When I wait about a week
Then I should be able to see my commit in the repo

28. Scenario: Have my commit integrated in the project
Given I have have submitted a well tested patch
When I wait about a week
Then I should be able to see my commit in the repo
And I should have commit rights in the main repo

29. Make it easy to set up dev environment
Write well tested code
Quickly integrate changes
Keep you contributors happy

30. Be the change you wish to see in the world.
- M Gandhi