Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Dec 2013 09:08:30 +0100
From:      Philippe =?iso-8859-1?Q?Aud=E9oud?= <jadawin@FreeBSD.org>
To:        Adam Weinberger <adamw@FreeBSD.org>
Cc:        svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, marino@freebsd.org, ports-committers@freebsd.org, Rene Ladan <rene@FreeBSD.org>, Mark Linimon <linimon@lonesome.com>, John Marino <dragonflybsd@marino.st>
Subject:   Re: svn commit: r335281 - in head: . audio audio/gnump3d
Message-ID:  <20131203080830.GA77731@tuxaco.net>
In-Reply-To: <20131203015955.GA55963@apnoea.adamw.org>
References:  <20131202104324.GB71618@tuxaco.net> <529C689B.9050902@marino.st> <20131202131244.GC71618@tuxaco.net> <529C8C1F.7050802@marino.st> <20131202134921.GD71618@tuxaco.net> <529C91F2.6020004@marino.st> <20131202145224.GH71618@tuxaco.net> <529CA16C.2060000@marino.st> <20131202184749.GC30485@lonesome.com> <20131203015955.GA55963@apnoea.adamw.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 02 Dec 2013, Adam Weinberger wrote:

> >> (2013/12/02 @ 1347 EST): Mark Linimon said, in 1.5K: <<
> > My reasoning is that contributing to FreeBSD is sometimes
> > hard and thankless, and if someone just hears too much negative feedbac=
k,
> > they may just find something else better to do.
> >> end of "Re: svn commit: r335281 - in head: . audio audio/gnump3d" from=
 Mark Linimon <<
>=20
> The style police (I'm looking at you, Alexey) should be allowed to fix
> commits for "correctness," and committers should be allowed to fix
> obvious mistakes for each other.
>=20
> 1) You have the confidence that if you accidentally commit something
> with an obvious error, someone is likely to help you out and fix it for
> you.
>=20
> 2) You don't have to sit there and stew when a commit accidentally
> breaks that port you love. Because let's face it, nobody wants to file a
> PR for ${PORT_OPTIONS:MODCS}.
>=20
> 3) If everybody is empowered to fix obvious mistakes and style nits, you
> gain a consistent experience for the end-user, who we all theoretically
> work for. You know, rather than just having Alexey send you an email
> about the importance of not muting install commands, which everybody
> seems to ignore anyway.
>=20
> 4) People need to un-knot their panties. Seriously. We're talking about
> "but *I* wanted to delete that port!" Someone did your work for you.
> Think about all the things you could do with the 30 seconds they just
> saved you.
>=20
> But when faced with the choice between "let's all fix bugs and promote a
> consistent ports user experience" and "MINE!", we all know which one
> people will pick.

Adam,

I don't care about "mine" port... I'm just saying that
nothing is clear around maintainer and that if maintainer is set, it
have to be respected. I agree that we need to be more reactive to fix a mis=
take
but rules don't have to be too permissive regards to maintainer respect.

Clearly, nothing to see with "People need to un-knot their panties".
Serioulsy.

Now, that everybody gave his opinion about panties, playground and other
off topic remarks, can we have a *debate* on how we can write or update
current rules about maintainer and each committer relation, please ?
Obviously it's a problem encountered by many committer and it have to be
fixed. Or are we only good to troll ?

I suggest to work with marino@ and rene@ to help portmgr@ and bapt@ ask it =
too.
So, if you want to be constructive (more than talking about panties, I mean=
),
 feel free to send me an email and i will put you in the "workshop".

Regards,

--=20
Philippe Aud=E9oud



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131203080830.GA77731>