<p dir="ltr">On Dec 16, 2013 12:32 PM, "Ben Weiss" <<a href="mailto:kc9uum@gmail.com">kc9uum@gmail.com</a>> wrote:<br>
> Is there some sort of procedure for accepting a bug? I'd be happy to assign them to myself, and create one for the RTX as well.</p>
<p dir="ltr">Sorry this went so long without a response. </p>
<p dir="ltr">When you create an issue on the website, you should be able to assign it to yourself. If not, Dan may first need to mark your account as a developer. Try it and let us know if you need a change. </p>
<p dir="ltr">> One thing that is in my line of work, though, is documentation. Would some more documentation be welcomed? The API calls, their parameters and returns and such?</p>
<p dir="ltr">Python is mostly self-documenting, but Chirp is pretty weak in docstrings. If you want to add some of those (stating only non-obvious details), that would be welcome. </p>
<p dir="ltr">Another thing you might do is run pylint and fix style issues. We'd like to be in line with PEP8. </p>
<p dir="ltr">Tom KD7LXL <br>
</p>