plperlng - testimport: try 7

'k, commit messages from pgfoundry projects are now sent to -committers,
as previously discussed ... all existing projects have been updated for
this ...

the format of the subject above is "project - module"

On Wed, 9 Jun 2004, User Andrewd wrote:

Log Message:
-----------
try 7

Modified Files:
--------------
testimport:
testcommit (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plperlng/testimport/testcommit.diff?r1=1.6&r2=1.7)

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

On Wed, 9 Jun 2004, Marc G. Fournier wrote:

'k, commit messages from pgfoundry projects are now sent to -committers,
as previously discussed ... all existing projects have been updated for
this ...

the format of the subject above is "project - module"

Do we really want all foundry projects commit messages coming here?
Eventually this will be a large number of messages about projects that
I not only don't care about, but don't even know what they are.

Why not have the a commit list for each project so people can choose what
they hear about? Failing that perhaps only certain "important" projects
get their messages posted here, but I imagine that it will be impossible
to select the "important" projects, just like now no favorites are played
between admin tools or competing interfaces or anything outside of the
core. Why are end users left groveling through gborg/pgfoundry for
important tools while developers are flooded with these projects' commit
messages in the "core area"?

Kris Jurka

On Wed, 9 Jun 2004, Kris Jurka wrote:

On Wed, 9 Jun 2004, Marc G. Fournier wrote:

'k, commit messages from pgfoundry projects are now sent to -committers,
as previously discussed ... all existing projects have been updated for
this ...

the format of the subject above is "project - module"

Do we really want all foundry projects commit messages coming here?
Eventually this will be a large number of messages about projects that
I not only don't care about, but don't even know what they are.

Then we'll re-evaluate this at that time ... we already had a good
discussions on the list about doing this to make the projects on
pgfoundry seem less "seperate" from the core, and make them more
visible ...

personally, I don't want to subscribe to 101 mailing lists just so that I
can see activity ... if you only want to see pgsql-server messages, setup
a filter that drops the rest into /dev/null ... that is why there are
per-project subject headings, so that you can easily setup a filter to get
rid of (or just keep) what you want to see ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

Marc G. Fournier wrote:

Then we'll re-evaluate this at that time ... we already had a good
discussions on the list about doing this to make the projects on
pgfoundry seem less "seperate" from the core, and make them more
visible ...

Oh dear god, please turn it off.

Marc G. Fournier wrote:

personally, I don't want to subscribe to 101 mailing lists just so
that I can see activity ...

I seem to recall that you are always the first one to suggest a new
mailing list when more than two people are talking about a topic. :-)

The header to allow filtering doesn't really help. What if I do want to
see commit messages from some projects but not from all? Eventually
we'll be drowned by commit messages from dozens or hundreds of projects
(we already nearly are, and it's been only a few weeks). Those who
actually read the commit messages to closely monitor the projects that
they care about will soon give up and overall quality will be less.

On Sun, 13 Jun 2004, Peter Eisentraut wrote:

Marc G. Fournier wrote:

personally, I don't want to subscribe to 101 mailing lists just so
that I can see activity ...

I seem to recall that you are always the first one to suggest a new
mailing list when more than two people are talking about a topic. :-)

The header to allow filtering doesn't really help. What if I do want to
see commit messages from some projects but not from all?

Filter on the subject ... reject if X-Site: PgFoundry AND ! Subject: IN (
plperlpng ) ... its really not that difficult ...

Eventually we'll be drowned by commit messages from dozens or hundreds
of projects (we already nearly are, and it's been only a few weeks).

Wow, how do you handle committers in the first place? there have been ~6
messages from pgfoundry, minus the ones that I got Andrew to make to test
that I had the format right ...

Those who actually read the commit messages to closely monitor the
projects that they care about will soon give up and overall quality will
be less.

If ppl aren't already using filtering on their email, they I can't imagine
them not already having given up on all the spam into their mailboxes ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664