On Tue, 2011-02-22 at 13:32 -0300, Alvaro Herrera wrote:
> >
> > Before we add more, I think we need to define a policy for hosting
> > mailing lists of 3rd party projects.
>
> So what policy do you propose?
In my previous email, I wrote:
"IMHO, postgresql.org can provide mailing list service to such projects,
unless they have their own domain already, or they are not hosted at
pgfoundry."
which is:
> I would suggest the following:
>
> 1 Use common sense to determine whether a project belongs into the
> postgresql.org list infrastructure. Strong majority is needed to
> accept a project.
>
> 2 Projects already on pgfoundry do not apply.
>
> 3 Lists for anything other than PostgreSQL core need to be categorized
> under "project lists" (not "user lists"). If some project has too
> many
> lists, a new category may be needed.
Pretty much what I have in my mind.
> Thus, under rule (3) above, I think we should move pgsql-jdbc and
> pgsql-odbc from "user lists" to "project lists". (Not a big deal --
> they just change group under which they are listed, in the
> archives.pg.org pages).
+1.
Cheers,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
