public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Alexey Borzov <[email protected]>
Cc: [email protected]
Subject: Re: Update on 'portal' changes
Date: 09 Mar 2004 10:04:33 -0500
Message-ID: <1078844674.2753.348.camel@camel> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<1078783781.22416.251.camel@camel>
<[email protected]>
<1078788127.22416.327.camel@camel>
<[email protected]>
On Tue, 2004-03-09 at 09:32, Alexey Borzov wrote:
> Hi!
>
> Robert Treat wrote:
> >>I would say +1. He might not be very diplomatic, but if he can save
> >>you/the web team some valuable time, why not ?
> >
> >
> > I guess we're still trying to decide if he can save us valuable time :-)
>
> Ahem. I'd learn that my work is not needed *now* rather than later, when
> I've spent more time on it...
>
No, the work is needed now, and quite frankly I have more faith that
you'll get it done than I do that we will, at least anytime soon. It's
just that we keep going round and round on the whole "working together"
thing... a similar issue came up on interfaces, with libtcl. A new guy
had a bunch of patches he wanted to submit but the project maintainers
had been idle for awhile, so he wanted to take over the project. The
admins stated they wanted to stay on, so he forked the project... all
bad imho. ISTM that when your new to a project, you should assume that
you don't know as much as folks that are currently running things. If
you want to take over things, the way to do it is by putting in enough
effort to show your serious, killing people with kindness, and by
submitting enough patches that the developers decide it's too much
hassle to stand in your way. At least that's how I have tried to
approach things...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
view thread (24+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Update on 'portal' changes
In-Reply-To: <1078844674.2753.348.camel@camel>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox