Menu
▾
▴
Re: [wxperl-users] wxPerl Community project...
|
From: Eric W. <scr...@gm...> - 2007-02-12 18:52:14
|
# from Huub Peters # on Monday 12 February 2007 07:57 am: Hi Huub, You make some good points, and I'll address some of them below. However, I think you missed a few: * sourceforge is not working anymore * this mailing list gets spammed way more than any other that I'm on * their online mail archive is poorly done * cvs? What's cvs? I think moving all of this to the perl.org infrastructure and switching to svn would be a huge improvement. >Here are some of my ideas: >* We need a user friendly, nice looking wiki. Firstly, most of what's wrong with the pvoice wiki is that it is terminally slow (this is partly latency, at least from the west coast of the US -- the ping time from here is 175ms.) With kwiki and many others, editing a page involves at least 2 page loads, and it doesn't take too many 3-second delays to lose interest in doing a lot of editing. But why a Wiki? For wxPerl? IMNSHO, Web2.0 is dead (and was dead before it started[1].) I think wxPerl is the foundation of Web3.0, which I'll summarize as "The network is the network and the computer is the computer." Also, While "anybody wanders in and edits it" is interesting for wikipedia, I'm not sure it applies so much to wxPerl. If you have something worth writing, you are a programmer, so the complexity threshold is higher and the tool need not be as simplistic as a wiki. How about svn and pod? http://combust.develooper.com/ >* Maybe a forum for some nice discussions (alltough it might clash > with the mailing list) Please, no web forums. A mailing list is much more convenient and appropriate. One without spam would be nice. Ref: [1] http://rescomp.stanford.edu/~cheshire/rants/Latency.html --Eric -- Introducing change is like pulling off a bandage: the pain is a memory almost as soon as you feel it. --Paul Graham --------------------------------------------------- http://scratchcomputing.com --------------------------------------------------- |
