Re: [cgiapp] The future of the CGI::App web presence

[Michael Graham <suppressed>]

Last week a bunch of us had a long chat on IRC, and we mad some progress
on deciding what to do about the Wiki and other web resources.  This is
a summary of that discussion for those who weren't present or who aren't
on IRC yet.

Jesse Erlbaum has generously donated a new server for the cgi-app
community to use.  He'll also be taking care of the system
administration for us.  So that's a good start.

We debated back and forth between using Trac
(http://www.edgewall.com/trac/) or a homegrown equivalent.

Trac is an integrated Source Code Management (SCM) system, Bug tracking
system and Wiki, with a single web interface.  The idea is that
we would like to create a mini development portal not only for
CGI::Application, but also for the C::A plugins and some related
projects.

So a system like Trac seems ideal.  However Trac is written in python.
Also, it has a less than fully-featured Wiki, and unknown darcs support.

So we decided to go the homegrown route and make a Trac-replacement out
of SVN, SVK, darcs, and RT (http://www.bestpractical.com/rt/).  Plus a
wiki of our choice.

Other arguments in favour of a homegrown system were that a lot of us
already use RT (via rt.cpan.org), and also there's a SCM preference
split in cgiapp community between SVN+SVK and darcs, so we'd like to
offer good support for both if we can.  Plus RT is written in Perl.

As we go along, we'll try to add the custom glue between the source
control and the ticket system (and the wiki) to make a more integrated
portal.

On the wiki side, we're going to try Kwiki for now.  The arguments are
that it's written in Perl, that it has a good development community, and
that some of us have experience admining it and developing for it.  So
hopefully we can pool our intelligence and figure out how to make custom
Kwiki plugins which link to the Ticket sytem and to the SCM content.

At the same time there is work going on by Shawn Sorichetti (hide) to
make a CGI::Application based wiki, but that is a few months off.
However, he says that when it's done it will display Kwiki-syntax fine,
so we should be able to move the content over fairly easily.  That was
another argument in favour of Kwiki.

There are lots of other (more tentative) plans in the works - we're
hoping to use Rubric (http://search.cpan.org/dist/Rubric/lib/Rubric.pm)
for blogging, and also to host a CGI::Application "meta-blog" which will
aggregate other CGI::Application based blogs from around the net.  Also,
Jesse wants to RSS-enable absolutely everything.

The old wiki will stay where it is for now, until we're happy with the
new site.  In the meantime, if you want to get involved, write the list with your 
plans or start a discussion on the #cgiapp IRC channel at perl.irc.org.


Michael

--
Michael Graham <suppressed>


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed