ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Smits <pierre.sm...@gmail.com>
Subject Re: Commit template, more flexibility [was Re: Put "Reverts" in the commit template?]
Date Sat, 24 Sep 2016 12:48:30 GMT
Yes, you have to give to get. In this case give up the viewpoint and get
the compromise. Unfortunately, that goes for *everybody*, not just the one,
as a compromise is something everybody can live with. If only viewpoints
are brought forward, the only thing we can say is: 'we agree to disagree'.
Which is also a satisfactory outcome for that moment.

On a related subject: Jacques has asked Michael to share the procedure to
be put in a wiki page, so that the burden doesn't rely on 1 contributor.
There seem to be no response to that question.

Best regards,



Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Sat, Sep 24, 2016 at 2:38 PM, Sharan Foga <sharan.foga@gmail.com> wrote:

> 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.cappellato@
> hotwaxsystems.com> wrote:
> > On Thu, Sep 22, 2016 at 5:21 PM, Rupert Howell <
> ruperthowell@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!
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message