Hi Tristan! Actually, going after bugs in modules is the best way to get started. You should check out:
http://docs.ansible.com/ansible/developing_modules.html Which will give you some ideas about how module code is written, how to test it, and so forth. --g On Wed, Jun 8, 2016 at 10:41 PM, Tristan Marks <[email protected]> wrote: > Hello, > > My name is Tristan Marks. I'm a Python developer of modest skill who gets > called upon to do system administration work quite often (I guess that makes > me DevOps more or less) and I'm looking to get involved in an open source > project. A friend of mine expounds on the glory of Ansible so I took a look. > I was quite impressed with it, and I feel I have the capability to lend a > hand. I've been in the background for a while, playing with a few Ansible > examples, and reading the code for the yum module to get an idea of how it's > all done. I want to jump in and help look at an issue if I can. I have > forked the repository and cloned it, and I was looking at a small issue > someone reported earlier: https://github.com/ansible/ansible/issues/16197 -- > it looks simple (you probably already know what's wrong) but it seems like a > good way to get introduced to the workflow to follow when contributing. > > According to the community page, I should fork the repository and submit a > pull request. However, I am not sure if and how the Submodules pointing to > ansible-modules-core and ansible-modules-extras affect the clone, and how I > would go about fixing this bug which I would have to guess is in the > unarchive module itself. Perhaps I shouldn't go after this one since it's in > ansible-modules-core, but in any case, I had the question about submodules > and just wanted to show that I've been thinking about it. > > I've been hanging out in the #ansible IRC channel a bit, too, under the name > tfmarks, so feel free to say "hi" if you see me there. > > Thanks for reading. Hope I can help. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Greg DeKoenigsberg Ansible Community Guy -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
