public inbox for [email protected]
help / color / mirror / Atom feedTechnical Mailing list creation policy
4+ messages / 3 participants
[nested] [flat]
* Technical Mailing list creation policy
@ 2008-03-04 17:15 Joshua D. Drake <[email protected]>
2008-03-04 20:00 ` Re: Technical Mailing list creation policy Selena Deckelmann <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Joshua D. Drake @ 2008-03-04 17:15 UTC (permalink / raw)
To: pgsql-www
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I think we need to put in place a technical policy that says that the
mailing list creation is the last step of the process. E.g;
1. Patch archives
2. Patch community/lists
3. create mailing list
If any one of those is missing, none get done.
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHzYOVATb/zqfZUUQRAgQQAJ9JMdBq6hSZxZk+dX++Vyu57zIo6ACdGoVF
MPhIpPLfeIV64Nu4L3AlQRM=
=/kjJ
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Technical Mailing list creation policy
2008-03-04 17:15 Technical Mailing list creation policy Joshua D. Drake <[email protected]>
@ 2008-03-04 20:00 ` Selena Deckelmann <[email protected]>
2008-03-04 20:02 ` Re: Technical Mailing list creation policy Joshua D. Drake <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Selena Deckelmann @ 2008-03-04 20:00 UTC (permalink / raw)
To: Joshua D. Drake <[email protected]>; +Cc: pgsql-www
On Tue, Mar 4, 2008 at 9:15 AM, Joshua D. Drake <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I think we need to put in place a technical policy that says that the
> mailing list creation is the last step of the process. E.g;
>
> 1. Patch archives
> 2. Patch community/lists
> 3. create mailing list
Also patch:
4. http://www.postgresql.org/community/lists/subscribe
-selena
--
Selena Deckelmann
PDXPUG - Portland PostgreSQL Users Group
http://pugs.postgresql.org/pdx
http://www.chesnok.com/daily
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Technical Mailing list creation policy
2008-03-04 17:15 Technical Mailing list creation policy Joshua D. Drake <[email protected]>
2008-03-04 20:00 ` Re: Technical Mailing list creation policy Selena Deckelmann <[email protected]>
@ 2008-03-04 20:02 ` Joshua D. Drake <[email protected]>
2008-03-04 20:33 ` Re: Technical Mailing list creation policy Magnus Hagander <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Joshua D. Drake @ 2008-03-04 20:02 UTC (permalink / raw)
To: Selena Deckelmann <[email protected]>; +Cc: pgsql-www
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 4 Mar 2008 12:00:03 -0800
"Selena Deckelmann" <[email protected]> wrote:
> > I think we need to put in place a technical policy that says that
> > the mailing list creation is the last step of the process. E.g;
> >
> > 1. Patch archives
> > 2. Patch community/lists
> > 3. create mailing list
>
> Also patch:
>
> 4. http://www.postgresql.org/community/lists/subscribe
+1
I would note that yes this should all be databased and I can look at it
(as yet another item on the list) but until that time, we need to
enforce something.
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHzarUATb/zqfZUUQRAknCAJ95WurN0HD/eCybR4+EhSK9EW6AAwCfVqDm
h7WvI5O5nHusA5eyviIUfUQ=
=7mAY
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Technical Mailing list creation policy
2008-03-04 17:15 Technical Mailing list creation policy Joshua D. Drake <[email protected]>
2008-03-04 20:00 ` Re: Technical Mailing list creation policy Selena Deckelmann <[email protected]>
2008-03-04 20:02 ` Re: Technical Mailing list creation policy Joshua D. Drake <[email protected]>
@ 2008-03-04 20:33 ` Magnus Hagander <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Magnus Hagander @ 2008-03-04 20:33 UTC (permalink / raw)
To: Joshua D. Drake <[email protected]>; +Cc: Selena Deckelmann <[email protected]>; pgsql-www
Joshua D. Drake wrote:
> On Tue, 4 Mar 2008 12:00:03 -0800
> "Selena Deckelmann" <[email protected]> wrote:
>
>>> I think we need to put in place a technical policy that says that
>>> the mailing list creation is the last step of the process. E.g;
>>>
>>> 1. Patch archives
>>> 2. Patch community/lists
>>> 3. create mailing list
>> Also patch:
>
>> 4. http://www.postgresql.org/community/lists/subscribe
>
>
> +1
>
> I would note that yes this should all be databased and I can look at it
> (as yet another item on the list) but until that time, we need to
> enforce something.
I'm working on code for this and has most of it done :-) Now to find
that time to test it so it doesn't kill everything :-)
That will take care of all the stuff that's on www.postgresql.org and
also search.postgresql.org (which is missing from the bullet list
above). Eventually, it will also take care of archives (in step 2, but I
haven't looked at code for that yet)
//Magnus
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2008-03-04 20:33 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-03-04 17:15 Technical Mailing list creation policy Joshua D. Drake <[email protected]>
2008-03-04 20:00 ` Selena Deckelmann <[email protected]>
2008-03-04 20:02 ` Joshua D. Drake <[email protected]>
2008-03-04 20:33 ` Magnus Hagander <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox