Re: Policy on cross-posting to multiple lists

Greetings,

* Tatsuo Ishii (ishii(at)sraoss(dot)co(dot)jp) wrote:
> >> I'm quite on board with the need to reduce useless cross-posting,
> >> but this is not the solution.
> >
> > Agreed. Similarly, posts from pgadmin-support sometimes end up
> > intentionally being cross posted to pgadmin-hackers.
>
> Another use case is, pgsql-docs and pgsql-hackers. For non trivial
> documentation changes I would like to register a doc patch to CF, but
> CF app does not pick up any messages other than posted in
> pgsql-hackers. So to discuss with pgsql-doc subscribers, while dealing
> with CF app, I would like cross postings for pgsql-hackers and
> pgsql-docs.

So, cross-posting between -hackers and -docs should be working now,
thanks to the change I made yesterday.

After stealing some time from Magnus to chat quickly about this (he
seems to be mostly unavailable at present), what we're trying to figure
out is what the group, overall, wants, and in particular if the change
to allow cross-posting with -hackers solves the valid use-cases while
preventing the invalid use-cases (like cross-posting between -general,
-performance, and -sql).

Of course, it isn't perfect, but then it's unlikely that anything will
be. Changes which require us to write additional code into pglister
will, of course, take longer, but we can work towards it if there's
agreement about what such a change would look like. In the interim, we
could see how things go with the current configuration, or we could add
other lists to the 'exclude', beyond just -hackers and the private
lists, or we could add them all (effectively going back to where things
were before the changes were made).

Thoughts? Specific votes in one of those directions would help me, at
least, figure out what should be done today.

Thanks!

Stephen