On Wed, Dec 05, 2007 at 05:40:59AM -0800, J.C. Roberts wrote:
> On Wednesday 05 December 2007, Simon Bertrang wrote:
> > On Tue, Dec 04, 2007 at 05:41:55PM -0800, J.C. Roberts wrote:
> > > update: devel/p5-Test-NoWarnings-0.084
> > >
> > > maintainer: Simon Bertrang <[EMAIL PROTECTED]>
> > >
> > > tested: i386
> >
> > As you already showed, you don't seem to care about the actual
> > changes for the ports.  Also you're mostly doing duplicate work.
> >
> > And your way of pushing the diffs is NOT NICE!
> >
> > Talk to the maintainers FIRST, before sending it to ports@ because
> > you give people who should know better a chance to look at it.
> > Besides, asking the right people for comments, tests and/or oks is
> > often harder than the update itself.
> >
> > I'd welcome if you start to FOLLOW THE PROCESS.
> >
> > Simon
> 
> 
> You are advocating talk rather than code.
> 

I'm just trying to tell what i think is a (more) productive behaviour.

> Your accusation of not caring about the actual changes to the ports is 
> completely unfounded. I've been very carefully walking the dependency 
> trees, updating all dependencies before updating the parent.
> 

See, one can only make assumptions if you don't mention that explicitely
with your updates.

> Your accusation of "mostly doing duplicate work" is also completely 
> unfounded. If it's not in -current and has not been posted to this list 
> for testing, then it most likely hasn't been done.
> 

Unfounded?

$ ls p5-*.diff | wc -l
     142

Guess why i'm still on it to get them in...  because it's actual work to
do things right, even for those more or less simple updates.

> The "right people" for comments, tests and oks are already subscribed to 
> this list. If something is out of date in -current and has not been 
> mentioned on the lists, I fix it, make the changes public on the list, 
> and cc the maintainer. Talking to a maintainer first is rude, pushy and 
> manipulative because it is tantamount to asking the maintainer to do an 
> update and to take their responsibility more seriously --it's a guilt 
> trip. I do not expect *you* to spend your free time doing the work that 
> *I* want done. I just do the work myself, and share the results.
> 

Talking to the maintainer first is everything else than rude; i'd even
say that's the way to go.  Plus, i'm doing it exactly this way for more
than a few days now and only had contact with one maintainer who told me
he's doing updates on it's own.

> Please try to realize this is not a competition, and there is no reason 
> for a maintainer to be offended when someone else manages to get the 
> work done before you do. I'm not doing the work for you and I'm not 
> doing it to make you look bad. Instead, I'm doing the work because I 
> want it done. If you find it useful, then great, but if not, then don't 
> let it trouble you so much.
> 

I don't see competition nor i feel like you make me look bad.  I'm just
a bit annoyed but the verbosity on ports@ (and always tried to avoid
that myself when possible).

> Simon, please stop looking for a fight, I'm not your enemy.
> 

In fact i'm looking for the opposite.

Regards,
Simon

Reply via email to