[22:20] <dronov> Hello everyone! My name is Mike, I am new here :) I have a big desire to be a part of great worldwide community and contribute or maintain something, but new big achievements are easier to make with small steps. That's why I decided to start from maintaining some packages in Ubuntu (Debian). I work with Emdedded Linux everyday and use this simple tool to upload firmware to SPI chips. https://github.com/setarcos/ch341prog/ I have some contributions there
[22:20] <dronov> (not to big but enough to participate in Arctic Vault program, haha). Some of my friends (and ex-colleagues) feel themselves unhappy without an opportunity to install it from Ubuntu's repositories.
[22:20] <dronov> I contacted the author of ch341prog but have not yet received an answer from him to the question what does he think about me to maintain the package in Ubuntu/Debian. While I wait, I study guides, wikis, and other useful resources. I have already packed programs in deb packages, so I don't think it will take a lot of time to create a package.
[22:20] <dronov> As I see, more time will take to find a sponsor for help, review and upload the package. And here I have the main question. The fact is that original ch341prog has only one beta version made in the git repository created three years ago. A lot of things in code has changed since this time. I'm still waiting for a response from the author of ch341prog. But what should I do if I don't get it? The Packaging guide talks about using meaningful versions of a
[22:20] <dronov> package. Can the Ubuntu package's version differ from the upstream's code version of the git repository? Or maybe it will be more correct to create a fork if I will not receive any feedback from author? Of course I will wait some time, because it is right to ask author his opinion and create a new version of everything is okay. But the last commit in master was created about a year ago and I feel myself a little afraid.
[23:23] <Unit193> dronov: Howdy and welcome!  First off, yeah Debian is pretty much the way to go since then it would benefit both Ubuntu and Debian.  The fact it's only had one tag a few years ago is a bit concerning, but technically wouldn't stop you from packaging it.  With regards to that, you could just take a newer git snapshot (the version would look something like 0.4.1+git20160905.c185bc4-1)  If you do decide
[23:23] <Unit193> to push it for Debian and have any questions about it, there's a channel on the OFTC network, #debian-mentors that was created just for that purpose.