Re: [pgsql-advocacy] We need an Advocacy wiki - Mailing list pgsql-www

From Joshua D. Drake
Subject Re: [pgsql-advocacy] We need an Advocacy wiki
Date
Msg-id 46B4AFC0.2030403@commandprompt.com
Whole thread Raw
In response to Re: [pgsql-advocacy] We need an Advocacy wiki  (Dave Page <dpage@postgresql.org>)
Responses Re: [pgsql-advocacy] We need an Advocacy wiki  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Page wrote:
> Robert Treat wrote:
>> On Saturday 04 August 2007 09:56, Greg Sabino Mullane wrote:
> I don't see any need to have any public facing pages on a Wiki - are we
> too lazy to write things up for the website when we want to present them
> to the world? It's not like it's difficult to do.

Yes, in fact it is. It is a complete pain in the butt in comparison to
editing a wiki. If I want a page added to the .Org I have to:

A. Understand CVS
B. Understand HTML
C. Understand patch

Worse, if I want to test my changes:

A. Understand apache
B. Understand mod_rewrite
C. Install and configure PHP
D. Figure out how everything is laid out in the htdocs structure for pgweb

Now, *I* understand all these things (except mod_rewrite). I *can*
contribute to the website and have.

*I* and nobody else in this community should have to go through that
much effort to add a page.

As a comparison for CMDs website:

(if the page exists)

A. Login
B. Edit page
C. Review changes
D. Save changes

(if the page doesn't exist)

A. Login
B. Insert new row into pages and site_items table
C. Edit page
D. Review changes
E. Save changes

The only time anyone has to do any type of coding is if we want a new
feature such as my blog.

Compare to a wiki:

A. Login
B. Make change
C. Review change
D. Save change


Now that I have written all of this. I am not suggesting that we change
our web infrastructure. I am however suggesting that we stop insulting
people and looking very arrogant about our, "It isn't like it is that
hard", because it is indeed hard and much harder than it should be.

Sincerely,

Joshua D. Drake





>
> For collaboration work however, the Wiki is important I think - but I
> agree with Greg, we shouldn't need a second one. Can't we have an area
> on the current one with looser permissions?
>
> /D
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>


- --

      === 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/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGtK/AATb/zqfZUUQRAhllAJ9h+B5K2AWAmnHzCcmnh9j9QwgvjwCfcYqb
xBYMwCTHAhnrFgca8e06MKI=
=Oata
-----END PGP SIGNATURE-----

pgsql-www by date:

Previous
From: Decibel!
Date:
Subject: Re: [pgsql-advocacy] We need an Advocacy wiki
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [pgsql-advocacy] We need an Advocacy wiki