|
It has occurred to me before, the idea of hosting k2pdfopt on GitHub, but I was loath to suggest it for precisely that reason -- that if you weren't using it already, it's probably because you aren't familiar with VCS.
Really, uploading release snapshots for each commit doesn't do a lot... the main reason people use VCS is to track the evolution of software line by line and change by change, not simply version by version. Seeing not just how stuff changed, but why it changed (commit messages). Experimenting with changes and rolling them back, mixing and matching (the branching model). Stepping through the commits to see where "x" went wrong (git bisect).
Running a `diff` on consecutive releases is not significantly different from committing each release tarball.
If the dev isn't familiar enough to do any of that, there is little point, I guess.
(And I don't blame you for not having the time to spare.)
It doesn't even lower the barrier to entry for contributing. (Easy and familiar to open a pull request on GitHub, but who knows the best way to contribute to a tarball?)
That requires the repo be maintained by the dev.
|