commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Sanders" <ssand...@nextance.com>
Subject RE: To fork or not to fork (was: AltRMI Tasks if anyone want to take them)
Date Wed, 23 Jan 2002 19:51:45 GMT
Just go full steam ahead with 4).  You contributed your packaged code to
the logging discussion, which helped me very much.  The only thing that
stopped me from actually using it was a [PATCH] against the current
impl.  I apologize if you think you were ignored.  I heard you loud and
clear.

Cheers,
Scott (Trying to erase the bad blood between Avalon and commons)

> -----Original Message-----
> From: Paulo Gaspar [mailto:paulo.gaspar@krankikom.de] 
> Sent: Wednesday, January 23, 2002 5:24 AM
> To: Jakarta Commons Developers List
> Subject: RE: To fork or not to fork (was: AltRMI Tasks if 
> anyone want to take them)
> 
> 
> Sam, I first tried 4) and 1) with the Common Logging Interface.
> 
> Since that was frustrating I am now going trough 2).
> =;o)
> 
> The waste of 3) is in this case harder to accept. Even Jon 
> agrees with that (when it is not me saying it, at least).
> 
> 
> What I would like from 2) is that there is more people 
> agreeing that it is better to fork code in the conditions I 
> described instead of just re-implementing it from scratch. It 
> seems that the later is becoming current practice.
> 
> I would not spend so much energy on this if I did not care 
> about Apache.
> 
> 
> Thanks anyway: adult advice is much nicer to hear (read) than 
> the alternative.
> 
> 
> Have fun,
> Paulo Gaspar
> 
> > -----Original Message-----
> > From: Sam Ruby [mailto:rubys@us.ibm.com]
> > Sent: Wednesday, January 23, 2002 1:41 PM
> >
> > Paulo Gaspar wrote:
> > >
> > > Thanks Sam, but my mood about this is too bad to relax.
> >
> > You read my intentions correctly.  But there is a deeper 
> message. if 
> > you care to look.  The problems that you are pointing out are not 
> > unique to Jon, Peter, yourself, commons, Jakarta, or even Apache.
> >
> > Generally, if you see something you believe is wrong, plain 
> wrong, as 
> > obvious as the nose on your face, to the point where it amazes you 
> > that others don't see the problem, there are several things you can 
> > do:
> >
> >    1) you can patiently try to work with others to get them 
> to address the
> >    problem  Quite frankly, this doesn't always work.
> >
> >    2) you can yell or pout.  Believe it or not, this actually works
> >    sometimes too.  But not always.
> >
> >    3) you can accept the current state as it is.  Sometime 
> this isn't
> >    possible.
> >
> >    4) or, you can engage.
> >
> > As always, the choice is yours.
> >
> > - Sam Ruby
> >
> >
> > --
> > To unsubscribe, e-mail: 
> > <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: 
> > <mailto:commons-dev-help@jakarta.apache.org>
> >
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message