This is Open Source too: Contributing Documentation
So what does Open Source software mean in real life? I promise no fancy philosophies and day-long lectures by Richard Stallman about open source and free software.
Contributing documentation — yes that’s an open source thing too.Not everything is about code, and you don’t need to provide a patch to fix the Linux kernel for your contribution to matter. Any contribution is welcome!
Obviously to interact with the console there is going to be some library that someone else wrote for me to use, which can parse all the arguments and display a nice command usage output. Something like this:
That library is gold!It does everything I need, it has tests and code coverage, maintained well, released often. Awesome. But then… I wanted to add some description to my command arguments yet couldn’t find anything in the documentation about it. Only after inspecting the source code a little bit further I’ve found references to a description property that can be configured.
So hey, I found the solution to my problem, that’s great, I’m all done with this library.But what if someone else will have the same problem in the future? They might be a little lazier and rule out this library just because it doesn’t seem to support a description configuration, which isn’t true, it’s just missing out from the documentation.
This is where open source shines! Here is how you contribute to open source in 3 easy steps:
- Fork the original Github repository, in our case it is https://github.com/75lb/command-line-args
- Now that you have your own copy of the repository, make changes to the md documentation on your own repo, commit and push them.
- Create a Pull-Request, which is just Github terminology for merging and incorporating your changes with the original repository.
Your contribution will be appreciated, and addressed by the project maintainer:
And you also got yourself a new brother in the open source family :)