On Tue, Apr 20, 2004 at 08:13:59AM -0400, Matt Cashner wrote:
> Steve Peters wrote:
> 
> >That sounds like a great idea to me.   Can we designate a piece of the 
> >Wiki for this purpose?
> 
> go to town. its world writable for a reason :) just let the list know 
> where it is and if you want you can let me know when you're happy with a 
> section so i can merge it in.

I also agree.

To help get things rolling, I designate the entire "Documentation"
section of the wiki as the place for the documentation project.  It's
so bad now that tearing it down and rebuilding it again can only help.
See: http://poe.perl.org/?POE_Documentation

Some recommendations:

The pointers to external online documentation are useful and should
probably stay at the top of the page until an adequate replacement is
made.

The rest of the page is clutter and notes.  That can probably be moved
to a subpage.

Despite its disorganization, the wiki contains a lot of useful
information.  Unless otherwise specified, I'm assuming wiki content is
licensed under the same terms as POE (Perl 5's license), so feel free
to cannibalize the site for ideas and content.

http://poe.perl.org/?List_pages_on_this_site shows a few different
ways to look at the wiki as a whole, or in aggregate, or something.

All the wiki is yours except the POE Cookbook.  Attempt no landings
there.  I mean, it's the best thing going right now; a lot of people
know its location by heart.  Assimilate a copy of its content, if you
must, but leave the originals where they are.

Get a wiki account before making major changes.  It'll help identify
who you are.  The wiki requires a cookie to identify you.  Remember
your user NUMBER and password---usemod wiki's authentication is lame
that way.  http://poe.perl.org/?action=editprefs

Describe your changes.  The description shows up in the automated
recent changes page.

There's a search field on every page.

Every page is editable.  There's a wee link in the page footer.

Preview before you save.  It saves my butt almost every time.

-- Rocco

Reply via email to