Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

bye for a while / odd announcement 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Please take a good look at ikiwiki before designing a new wiki. It has some very good ideas.
  • Spending time to modernise ST pays off immediately and will also be overall more beneficial in the long term compared with designing and coding a software from scratch.
    • not necessarily. there is a open source version, but its also lot of effort to understand a large system. and if you work your on your own when we want to tweak the wiki syntax and the overall rendering. maybe its worth a try. i look at http://github.com/socialtext [github.com]. but there is also the problem i cant find any admin.
      • One does not need to understand every detail of the whole system in order to change smaller parts.

        The homepage of the open source version is http://www.socialtext.net/open/ [socialtext.net].

        What do you need an admin for?

        • currently i cant reach an admin of perlfoundation.org :( it would have the advantage to use all the existing highter modules. there is even one for perl 6 that padre uses. but on other hand the changes i need would change the wiki markup syntax. i dont believe socialtext would allow that. so we maybe need a parser for wikimedia markup and extend it. i think it would touch a lot of subsystems such as the diff module, revamp search engine, add links to the history. i dont think you need that much code to imp

  • Hi! I agree Socialtext 2.0 really is subpar. :-)

    However, I'm coincidentally working for Socialtext, and am one of the main hackers of its Wiki Syntax!

    I wonder if we can set up a Free-50 hosted account for the @cpan.org domain, and import the existing Perl 6 Wiki content: See http://www.socialtext.com/products/free50.php [socialtext.com] for details.

    The gist is that all writers (not readers) need to be a CPAN author, which may have the nice dual side-effect of encouraging CPAN authorship and reducing spam.

    The Social

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.