public inbox for [email protected]
help / color / mirror / Atom feedFrom: Josh Berkus <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: [email protected]
Cc: Dave Page <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: Magnus Hagander <[email protected]>
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
Date: Thu, 12 Jun 2008 10:22:17 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <1213290175.11470.94.camel@jd-laptop>
References: <[email protected]>
<[email protected]>
<1213290175.11470.94.camel@jd-laptop>
Guys,
> Special attention should be limited specifically to community. That is
> how you are going to drive a larger community, by reinforcing the
> community itself. Not by becoming advertising space.
Can we *please* get back on topic here? Absolutely none of this is relevant
to a pgfoundry feed.
First, I wasn't proposing merging pgfoundry news with *events* (which only has
3 slots) but with *news* (which has 6). Right now, 3 of those slots are
taken up by commercial products; don't you think it's fair that pgFoundry
projects should bump them? If we have a problem with core release
announcements scrolling off too fast, isn't that a *code* problem for the WWW
team to solve?
The pgfoundry team can easily regulate the volume of pgfoundry traffic that
gets passed on.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
view thread (19+ 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], [email protected], [email protected]
Subject: Re: Proposal: pulling newsbytes from www.pgfoundry.org
In-Reply-To: <[email protected]>
* 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