Skip site navigation (1) Skip section navigation (2)

Re: Patch to roadmap

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Patch to roadmap
Date: 2007-02-27 17:28:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-www
Joshua D. Drake wrote:
>>>> You've completely misunderstood my point.  If we do it that way then the
>>>> TODO list exists only upon sufferance of the wiki, which is not the true
>>>> power structure around here, even if you would wish it otherwise.
>>> I do not wish anything but for the information to be central and easy to
>>> find. Let's stay on task shall we. I find it much more productive. I
>>> submitted a patch. You don't like the patch. Fine. Let's come up with a
>>> better one.
>> FWIW, I'm with Tom on this - it's fine to present a link to the wiki (it
>> really should be there, it's something we've missed), but the wiki is
>> *not* a replacement for the TODO list. At least not yet. (it might be at
>> some time in the future, but that's a completely different discussion)
> Well I am not against Tom on this. There seems to be this attachment to
> the idea that I removed a link to the TODO list. I already said I would
> put it back. The link *is* redundant, but that's fine.

:-) Sorry, probably didn't read the thread careful enough.

>> The same goes for the link on the frontpage (per your other patch), I
>> think it's better if it goes into the developer section, or possibly
>> directly to the TODO list, and not to the Wiki.
> I disagree strongly with this one. The point of the change to the front
> page is to get everyone as much information as they need with one entry
> point.
> It isn't about replacing the TODO list, it in fact has nothing to do
> with the TODO list.
> If I go to the TODO list, how do I know who is working on a feature?
> If I go to the TODO list, how do I know the status of a feature?
> I don't. The WIKI gives us that and gives us the TODO list to boot.

What you are suggesting is getting rid of the TODO list and replacing it
with the Wiki. If we want to do that, then it's a different question
(I'm not going to go into the reasons for or against doing it here, just
that it's a different consideration)

Until then, AFAIK the TODO list is the official word, and that's the
only thing we should be linking to from our frontpage. We should not be
linking to something that's labeled as Unofficial from the entry page of
our website.

>>> I could, also remove roadmap which in general seems to be a redundant
>>> category and thus allow for less links in general, as the roadmap is
>>> basically a regurgitation of the /developer page anyway.
>> A general change there might not be a bad idea. Though I like having the
>> Roadmap on it's own page - perhaps we should get rid of all those links
>> on the first page instead?
> The problem with roadmap on its own page is that it exists to give a
> warm and fuzzy about possibly having a roadmap which we don't. At all.
> It is a bogus link, even with the original page and it only contains
> redundant information.

That's a good point, but people requested a roadmap and that's the best
we could come up with - IIRC. But I'm definitely open for other changes
there, but it has to be made to the whole section and not just
micro-fixes, I think.

>> What might make more sense is to have a paragraph about "the postgresql
>> development model", in how we deal with patches and such in our project.
>> (I'm volounteering your time to write this, of course :-P)
> I would agree with this, including information on a roadmap etc..

Great, especially considering that it was your time that was volunteered
to do it :-)


In response to


pgsql-www by date

Next:From: Josh BerkusDate: 2007-02-27 17:55:46
Subject: Re: update to main page for feature freeze
Previous:From: Joshua D. DrakeDate: 2007-02-27 17:26:51
Subject: Re: update to main page for feature freeze

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group