[Perl-org-patches] Priorities / content updates

[Ask Bjørn Hansen]

Matt S Trout wrote:

> I'd like to have a look at the information architecture a bit but  
> there's lots
> of obvious "let's bring things up to date a bit" data updates we can  
> do first.

Definitely.   Robert and I have been looking after some of these  
things for about a decade (!) and our  most common frustration is  
people starting new projects and then never maintaining them; leaving  
us to either shut them down or trying to maintain them (or entice  
someone else to).

Indeed www.perl.org ended up in the current state because we stripped  
down the previously unmaintained site to just have pointers to other  
(at least occasionally or at the time) updated things.

(This is also why we marginally prefer hosting things over delegating  
DNS elsewhere; history shows that more often than not when we point  
DNS elsewhere we just end up having to remove the DNS entry after  
someone tells us a perl.org site/wiki is full of p0rn spam -- hosting  
it we avoid that and at least get the choice of finding someone to  
help update the content).

Anyway -- enough ranting.  I'm really happy and excited about you guys  
stepping up to help get things in proper shape!

Doing content updates is really just patches to .html and .pod files -  
very easy.  You don't even really need combust running for that.

>> I'd never heard of moose.perl.org or catalyst.perl.org, oh, just  
>> found poe.perl.org, I wonder if there's a list of these projects  
>> somewhere?

> I dunno, but if there isn't, we should make one.

Having a list of the various *.perl.org sites would indeed be good.


   - ask