[chirp_devel] Documentation and taking up tasks

[Ben Weiss]

Ok, so as everybody may have seen by now, I put in for a new model but left
it as "Bug" by mistake. I was able to assign it to myself, but I couldn't
go back and edit it. Nor could I modify the existing DTX requests.

Haven't had a chance yet to look into PEP8, but I'll do so soon.

Thanks,
Ben KC9UUM


On Sat, Dec 21, 2013 at 9:45 PM, Tom Hayward <esarfl at gmail.com> wrote:

> 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
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131227/84128f1f/attachment-0001.html