SEO

Hallo to all,

Just wondering after reading so many mails from Hackers List.(its 2.15 AM now!!)
Is there anybody working on something to create a DB from
a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
b) The sourcecode of PostgreSQL
c) The relevant Mailings from the developers lists

Not sure if someone was dealing with similar thoughts.PostgreSQL is such a great
tool
to get you organized so that I wonder why the 3 most important things of this
project are not organized like a PostgreSQL DB

Thanks for any feedback

Gottfried

www.wirtschaftswunder.co.uk

www.5152.eu


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

deductive@Kutoma.com wrote:
> Hallo to all,
>
> Just wondering after reading so many mails from Hackers List.(its 2.15 AM now!!)
> Is there anybody working on something to create a DB from

What?

Joshua D. Drake

> a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
> b) The sourcecode of PostgreSQL
> c) The relevant Mailings from the developers lists
>
> Not sure if someone was dealing with similar thoughts.PostgreSQL is such a great
> tool
> to get you organized so that I wonder why the 3 most important things of this
> project are not organized like a PostgreSQL DB
>
> Thanks for any feedback
>
> Gottfried
>
> www.wirtschaftswunder.co.uk
>
> www.5152.eu
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>


--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Gottfried,

> Just wondering after reading so many mails from Hackers List.(its 2.15 AM
> now!!) Is there anybody working on something to create a DB from
> a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
> b) The sourcecode of PostgreSQL
> c) The relevant Mailings from the developers lists

Of those, only the TODO makes sense as a DB. You're welcome to go for it.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On 2/26/07, Josh Berkus <josh@agliodbs.com> wrote:
>
> > Just wondering after reading so many mails from Hackers List.(its 2.15AM
> > now!!) Is there anybody working on something to create a DB from
> > a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
> > b) The sourcecode of PostgreSQL
> > c) The relevant Mailings from the developers lists
>
> Of those, only the TODO makes sense as a DB. You're welcome to go for it.


The TODO list is a bit outdated, and it would make sense to make it into a
web page and assign names to the tasks and which releases the TODO task will
make it in. Perhaps it would even be useful for folks to post their WIP
patches, status updates, etc to such a page?

Any comments? I am willing to chip in. I could only imagine the current
workload for maintaining this is a bit overwhelming.

On Tue, 2007-02-27 at 08:41 -0500, Chad Wagner wrote:

> The TODO list is a bit outdated,

Really?

> and it would make sense to make it into a web page and assign names to
> the tasks and which releases the TODO task will make it in. Perhaps
> it would even be useful for folks to post their WIP patches, status
> updates, etc to such a page?

Please read the archives.
--
Devrim GÃœNDÃœZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBF5DhHpme12CBXnxERAlnFAKCO6XCS9Fc11t94Pvhxr1 grK0RWtQCeOyzV
aJj5rhaCnFwJ3uhyPNHQR/k=
=3qaJ
-----END PGP SIGNATURE-----

Chad Wagner wrote:
> On 2/26/07, *Josh Berkus* <josh@agliodbs.com
> <mailto:josh@agliodbs.com>> wrote:
>
> > Just wondering after reading so many mails from Hackers
> List.(its 2.15 AM
> > now!!) Is there anybody working on something to create a DB from
> > a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
> > b) The sourcecode of PostgreSQL
> > c) The relevant Mailings from the developers lists
>
> Of those, only the TODO makes sense as a DB. You're welcome to go
> for it.
>
>
> The TODO list is a bit outdated, and it would make sense to make it
> into a web page and assign names to the tasks and which releases the
> TODO task will make it in. Perhaps it would even be useful for folks
> to post their WIP patches, status updates, etc to such a page?
>
> Any comments? I am willing to chip in. I could only imagine the
> current workload for maintaining this is a bit overwhelming.

Before we rehash recent debates, please, everybody, review them. Going
over and over and over the same ground laboriously is really getting
tiresome, and unfortunately it's also getting more frequent. It's *déjà
vu *all over again.

And, for the record, I do not see the slightest point in putting the
TODO list on its own into a database. None, zilch, nada. As database
professionals we should be adept at recognising when the use of a
database is appropriate and when it isn't. If we put it into a tracking
system (presumably database backed) that would be another matter, but
that has gone nowhere as usual.

There is some point in putting it in a wiki where we can gather relevant
documents, links to discussions etc. That's why the developers' wiki was
established, AIUI.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On 2/27/07, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> Before we rehash recent debates, please, everybody, review them. Going
> over and over and over the same ground laboriously is really getting
> tiresome, and unfortunately it's also getting more frequent. It's *déjà
> vu *all over again.


History does tend to repeat itself, doesn't it? I just assumed it was never
discussed based on Josh's response.


database is appropriate and when it isn't. If we put it into a tracking
> system (presumably database backed) that would be another matter, but
> that has gone nowhere as usual.


A tracking system is what I was referring to, if it didn't have a front-end
then it would be quite pointless to have it in a database. Honestly, I
think Trac even does this, but I am far from familiar with that tool -- I
have just seen other projects with "roadmap" items which categorized TODO
tasks into future releases.


There is some point in putting it in a wiki where we can gather relevant
> documents, links to discussions etc. That's why the developers' wiki was
> established, AIUI.
>

To be honest, it may be adequate to maintain this solely through the Wiki.
The only thing I see lacking is specifically who is handling tasks, and what
release it is planned for. Perhaps, I am just looking in the wrong place?

Chad Wagner wrote:
>
> There is some point in putting it in a wiki where we can gather
> relevant
> documents, links to discussions etc. That's why the developers'
> wiki was
> established, AIUI.
>
>
> To be honest, it may be adequate to maintain this solely through the
> Wiki. The only thing I see lacking is specifically who is handling
> tasks, and what release it is planned for. Perhaps, I am just looking
> in the wrong place?
>

There's a good reason this information is missing: it doesn't exist.
Please, like I said, have a look at recent discussions.

Maybe we need some extra FAQs, like:

.. Why do you still use CVS instead of <insert favorite SCM system here>?
.. Why don't you use bug tracking software?
.. Where do I find out when <insert desired feature here> will be in a
release?

cheers

andrew


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Andrew Dunstan wrote:
> Chad Wagner wrote:
>>
>> There is some point in putting it in a wiki where we can gather
>> relevant
>> documents, links to discussions etc. That's why the developers'
>> wiki was
>> established, AIUI.
>>
>>
>> To be honest, it may be adequate to maintain this solely through the
>> Wiki. The only thing I see lacking is specifically who is handling
>> tasks, and what release it is planned for. Perhaps, I am just looking
>> in the wrong place?
>>
>
> There's a good reason this information is missing: it doesn't exist.
> Please, like I said, have a look at recent discussions.
>
> Maybe we need some extra FAQs, like:
>
> . Why do you still use CVS instead of <insert favorite SCM system here>?
> . Why don't you use bug tracking software?
> . Where do I find out when <insert desired feature here> will be in a
> release?

yeah .. would be a good idea .. with some links to key posts in the
archive .. would be much less work than replying all the time .. and
would also make it easier for new comers to not burn their fingers at
rehashing things needlessly ..

regards,
Lukas

On Feb 27, 2007, at 23:40 , Andrew Dunstan wrote:

> Maybe we need some extra FAQs, like:
>
> . Why do you still use CVS instead of <insert favorite SCM system
> here>?

I just saw a patch from Robert Treat on just this topic. Doesn't look
like its been applied yet.

Michael Glaesemann
grzm seespotcode net



---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate