[chirp_devel] Documentation and taking up tasks
Hi all,
Back around the middle of the year, I started work on adding support for the Ritron RTX-450 radios. Due to a (forced) job change, though, it has been some time since I've continued - coding and devices is not near my current line of work. I do intend to see it through, though, and am starting to finally get some time freed up. I was poking around the site today, and noticed a bug filed for the DTX-150 and DTX-450. These are basically the radio (as opposed to audio, there are 2 boards that connect together) portion of the RTX line. I actually used documentation from the DTX series in my work on the RTX. 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. 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?
Ben KC9UUM
On Dec 16, 2013 12:32 PM, "Ben Weiss" kc9uum@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
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@gmail.com wrote:
On Dec 16, 2013 12:32 PM, "Ben Weiss" kc9uum@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
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.
See if you can make that change now.
--Dan
I now can make the changes. Thanks, Dan! Now to get to work!
On Sat, Dec 28, 2013 at 8:42 AM, Dan Smith dsmith@danplanet.com wrote:
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.
See if you can make that change now.
--Dan
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (3)
-
Ben Weiss -
Dan Smith -
Tom Hayward