[chirp_devel] Documentation and taking up tasks

[Tom Hayward]

On Dec 16, 2013 12:32 PM, "Ben Weiss" <kc9uum at gmail.com> wrote:
> 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.

Sorry this went so long without a response.

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.

> 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?

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.

Another thing you might do is run pylint and fix style issues. We'd like to
be in line with PEP8.

Tom KD7LXL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131221/5e2c129c/attachment-0001.html