[chirp_devel] Modernizing

[Jim Unroe]

> On the git and/or github conversation, I really want to hear from people like Jim and maybe Rick. Jim has contributed a ton to chirp, and if he was less likely to work on stuff if it was in git, then that's a non-starter for me. Rick has (I think, not sure) been struggling with the SCM process in general, so I'd like to hear if he's more comfortable with git, or if he'd be okay pivoting to something else with a slightly different workflow. If these guys are okay with switching and learning something else (or with trying to continue using mercurial from a mirrored tree, which I could maintain), then we could think about moving to git.

I got my Baofeng UV-5R back in April of 2012. I started using CHIRP
when the initial support for the UV-5R was added in May or June of
2012. the same year. I for get how or why, but soon after I started
using CHIRP, I mapped out all of the unsupported settings of the UV-5R
factory software and offered a copy to Dan. Dan replied with some
snippets for Python and 2 or 3 links reference material for developers
on the CHIRP website and asked if I thought I could do it myself.

I am not a computer programmer. I did some BASIC programming back in
the days of the COMMODORE PET, but I have never had any formal
training in computer programming. I didn't know anything about Python
or Mercurial. Even still, I decided to give it a go. With some help
and a lot of patience from Dan, I submitted my first patch on December
22, 2012. Five years later, I am just starting to get comfortable with
Mercurial. I am still a hack with Python.

I am not opposed to change. But if git/github thing requires me to
take another 5 years to get comfortable, it might be time for me to
retire. But like before, I'd probably give it a go.

Jim KC9HI