juanbono · April 10, 2018 00:11
diff --git a/steps.txt b/steps.txt
 1. have a brilliant idea for something you want to use
 2. Stop! Don't start building it. 
 3. Find a project that does something similar. (This likely exists)
 4. Read it's documentation. 
  * If it has none, learn the project and create some. 
  * If it does, try to build something with it and document what wasn't clear. 
 5. If it feels broke. Write some failing tests, 
  * If possible, fix them, then open a pr
  * If not, open a pr with failing tests and get the maintainer to teach you how to fix them 
 6. Document your process for contributing in a file called CONTIBUTING.md
  * If this file exists, improve it
 7. Reach out to the project owner and ask how to become a maintainer
 8. Start reviewing prs
 9. Congrats. You have just created value and not a second or third project
   that is under documented, under tested, and under maintained!
	1. have a brilliant idea for something you want to use
	2. Stop! Don't start building it.
	3. Find a project that does something similar. (This likely exists)
	4. Read it's documentation.
	* If it has none, learn the project and create some.
	* If it does, try to build something with it and document what wasn't clear.
	5. If it feels broke. Write some failing tests,
	* If possible, fix them, then open a pr
	* If not, open a pr with failing tests and get the maintainer to teach you how to fix them
	6. Document your process for contributing in a file called CONTIBUTING.md
	* If this file exists, improve it
	7. Reach out to the project owner and ask how to become a maintainer
	8. Start reviewing prs
	9. Congrats. You have just created value and not a second or third project
	that is under documented, under tested, and under maintained!