> Why is the TODO list keep in the source code repository, anyway? One
> alternative would be to move it to a wiki. That would allow other people
> to contribute to maintaining the list, with less procedural overhead.
> The GCC folks do this, for example: example: http://gcc.gnu.org/wiki/
I agree with this. It would add visibility to what the direction of
PostgreSQL as well as put a friendly face on what the heck is
happening.
I get a lot of calls that are basically, "What's coming in 8.2" Unless I
follow the lists it is not an easy bit of information to get. A wiki that had
a page that said, "What's planned for 8.2!" or would be great!
It would also be useful to see who has signed on as the lead or to work on
a particular subproject in case other developers would like to either lead
or help a lead on the project.
I would request a vote interface but I think we would get to many
mysqlisms ;)
> I don't see that we're "covered": sure, it's documented that people
> ought to ask on -hackers first, but this exact situation has happened
> several times in the past. Avoiding that would be a good thing,
> documentation or no.
Agreed.
Joshua D. Drake
>
> -Neil
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564
Custom programming, 24x7 support, managed services, and hosting
Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG
Reliable replication, Mammoth Replicator - http://www.commandprompt.com/
