Derek Chen-Becker <[email protected]> writes: > 1. For the WORGG change, that needs to be a separate patch because that's a > different repo. Should there be anything at all in CONTRIBUTE.org, or just > leave it in the original state?
The hooks refer to CONTRIBUTE.org, so let's put a section in there, linking to WORG website, just as the existing sections in CONTRIBUTE.org do. > 2. Previously you said to add the git hooks target to `all', but I wonder > if this should be opt-in or opt-out. Instead of adding some sort of > configuration (e.g. environment variable, file settings, etc), maybe I can > just leave the git hooks target out of `all' . Thoughts? I guess the question is who is the target auditory for these hooks. Should it be occasional contributors? Should it be regular contributors? If the former, we should include the hooks as a part of make all. If the latter, maybe not. P.S. I tested the hooks a bit, and it looks like they have false-positives when inserting long Urls - complain about "too long word" and "too long line". -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
