Hi All
The initiative to setup a unified commit message was to help reduce the
workload Michael has to do each month to compile the blog.
We are a community and we want to work together and help each other. All the
time we try very hard to reach consensus but sometimes that isn't possible, so
someone has to be willing to compromise, or we take a vote and that is the way
progress is made.
I can see no compromise happening here at all, instead I see a lot of effort
defending a single position and people getting frustrated on both sides. A
community functions by raising proposals and building consensus. That means it
is about convincing others, not everyone, but the majority that the proposal
has merit, and Michael has successfully done that in this case.
I think that if Jacques is not willing to compromise then I suspect that a
formal vote will settle it. Ideally we shouldn't have to go to those extremes
over a single word.
Thanks
Sharan
On 2016-09-22 19:28 (+0200), Jacopo Cappellato
<jacopo.cappell...@hotwaxsystems.com> wrote:
> On Thu, Sep 22, 2016 at 5:21 PM, Rupert Howell <ruperthow...@provolve.com>
> wrote:
>
> > Hi yes, reading with interest, I agree with Jacques.
> > Commit messages should be Present Tense Imperative, Imperative Style.
> >
>
> well, now I am a bit confused because Jacques is using Present Tense in
> Third Person ("fixes") and not the Imperative Style ("fix")... but now I am
> walking on the thin ice since English is not my mother tongue! From what I
> understand the "present tense imperative" is the suggested style for Git
> repositories... and this reminds me that we should start talking about
> migrating from Svn to Git :-)
>
> Jacopo
>
> PS: Welcome back Rupert!
>
