pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-docs@postgreSQL.org
Subject: Re: Uniform policy for author credits in contrib module documentation?
Date: Wed, 05 Dec 2007 21:12:52 -0800
Message-ID: <475784D4.2070305@joeconway.com> (raw)
In-Reply-To: <3393.1196917132@sss.pgh.pa.us>
References: <3393.1196917132@sss.pgh.pa.us>

Tom Lane wrote:
> As of CVS HEAD, some of the contrib module documentation pages have
> extensive credit screeds, eg
> http://developer.postgresql.org/pgdocs/postgres/cube.html
> and some just have the author's name, with or without an <email> link,
> and some don't have anything at all.
> 
> This bothers me; it seems like we should have a more uniform approach.

[snip]

> I don't have a strong opinion one way or the other, except that I think
> we should have a uniform policy for all the contrib modules.
> 
> Comments?

As far as I'm concerned, you can remove any credits for me from the 
contrib modules I've worked on (or I can do it if you'd prefer).

In any case +1 for a uniform policy, and +1 for removing credits from 
documentation.

Joe



view thread (13+ messages)  latest in thread

Message-ID: <475784D4.2070305@joeconway.com>
Permalink:  ../475784D4.2070305@joeconway.com/
Also on:    postgresql.org/message-id/475784D4.2070305@joeconway.com

 · 

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: pgsql-docs@postgresql.org
  Cc: mail@joeconway.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: Uniform policy for author credits in contrib module documentation?
  In-Reply-To: <475784D4.2070305@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox