Quote:
Originally Posted by DiapDealer
The guide IS in its own independent repository. And yes... that's how version tracking works. Every commit--regardless if it's big or small--needs to be pushed to github if it is to be made available for others to use and/or contribute to.
Whether you think it is good idea or not is irrelevant. That's how just how it is it is. Major props to those who have made an effort to contribute to the guide, but it just doesn't really matter how we ultimately make it available. Easy or hard, people (except the handful I previously praised) won't contribute. They'd much rather complain about it being out of date (or hard to contribute to) than actually knuckling down and helping bring it up to date. *shrug*
But it HAS to be in a git repository. Otherwise we'd have to read the whole guide each and every time someone made a small change just to make sure they didn't inadvertently break something somewhere else. The github repo allows us to see exactly the change that's being proposed (at the code-level) at a glance before signing off on it.
The alternative is to have multiple people making multiple changes to multiple copies of the same epub that we then have to figure out how to integrate without losing anything (and without wasting hours of time that could be better spent actually working on Sigil). No thanks.
|
In this case, you can make the decompressed ePub file in git repo. Easier to change, smaller to git clone.