Would it be worthwhile to publish the pilot-link 0.13.0 source code?

[unforgettableid]

Background information

Arch Linux maintains packages for pilot-link and for jpilot.

In a comment, an Arch user said they couldn't find the source code for pilot-link 0.13.0. (A compiled version is easily available.)

My question for you

I looked at changelog.gz, which is inside the pilot-link 0.13.0 .deb file. The only change for 0.13.0 is: "Changing python2 dependency to python3".

Dear @juddmon: How much work went into this change? If it was a lot of work, might it be worthwhile to post a patch and/or the source code to GitHub?

Conclusion

Thank you for reading this!

[dmalia1]

Its at https://github.com/desrod/pilot-link

[juddmon]

It wasn't a lot of work. I downloaded the Debian package and just basically tipped the python2 code dependencies out of it. The reason I didn't try to upload it anywhere is because the Debian source code didn't match the code at pilot-link and this was a quick hack to get Ubuntu/Debian users a working jpilot when a pilot-link package was not available. I'll contribute what I have to someone if they are willing to sort out the code. We just need to figure out to do this.

[CoSoCo]

Please also note: https://lists.jpilot.org/empathy/thread/QPHDE42D3QA5ZB6XH7QIWGCWY2ED52YG

For more convenienceI need an up-to-date libpisock-dev package to work on a plugin, see: https://sourceforge.net/p/picsnvideos/discussion/822268/thread/a319aac6/

[CoSoCo]

Its at https://github.com/desrod/pilot-link

The latest tag there points to 0.12.3. Version 0.13.0 is based on 0.12.5, so there seems to be a gap between these versions, where nobody knows the source code of.