public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: merging advocacy and "overview"
Date: 02 Dec 2004 12:10:12 -0500
Message-ID: <1102007412.2558.63.camel@camel> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Thu, 2004-12-02 at 11:57, Joshua D. Drake wrote:
>
> >>> members{a}
> >>
> >>
> >> Doesn't this duplicate the developer site portion?
> >>
> >>> corporate{a}
> >>
> >>
> >> We'll need to come up with some rules on who can appear here. My
> >> thoughts:
> >> 1) Anyone who sponsors a full-time or 1/2 time developer;
> >> 2) Anyone who has sponsored a significant feature in the last 3
> >> versions.
> >
> >
> > Not sure if I agree with a 'time limit' on this one ... there should
> > be some sort of 'history' section ... if we are remembering a
> > contribution, it should be remembered, not 'fade out over time' ...
>
>
> I think Marc has an interesting point. The other issue is what about
> companies who may not sponsor a ton of code but troll the mailing lists?
> Or provide major services like hosting? Or secondary code like the .Net
> provider?
>
This is why we never came up with a guideline...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
view thread (41+ 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], [email protected], [email protected]
Subject: Re: merging advocacy and "overview"
In-Reply-To: <1102007412.2558.63.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