What now?

[Dave Everitt]

@Philippe:
Agreed - if Camping is going to get any mindshare it does need a  
portal one-stop site.
BTW rubyoncamping - ROC (as in 'solid as a...' :-? )

So... .com/org/net(all?) domain options (bearing in mind SEO- 
friendliness and availability) - [ ] = add a score out of 10:
rubycamping.com [ ]
campingframework.com [ ]
rubyoncamping.com [ ]
whywentcamping.com [ ]

Domains cost around £12 p.a., which I'm sure we can find between us.  
Hosting (I imagine with all the sysadmins and webmasters on this  
list ;-) is effectively free.

@Julik:
> A new site shared over githubz would be nice
You'll have heard that _why's inheritance already has a preservation  
plan (see 'Decentralization of _why's Projects' at http:// 
whymirror.github.com) - there's a lot of [planning|thinking|reporting  
on what's happening] there, and Magnus is already part-time  
'scoutmaster' for Camping at http://github.com/camping/camping ... or  
did you mean something other?

- Dave

> I like the idea of updating the  rubyforge site,  but  having a  
> main  site  to  publicize  Camping would  be a nice addition and  
> would  have the benefit of being easier for people to find or  
> remember (especially if they are new to Ruby). I really like:
> rubycamping.com
> campingframework.com
> Here is an additional suggestion: rubyoncamping.com (like ROR).
> The new site could act as a portal for everything Camping, such as  
> news, rotating features on sites using Camping, code snippets, etc.
>
> Philippe
>
> Dave Everitt wrote:
>>
>> Agreed, but ideally it would be great to have it updated as the  
>> dead links (redhanded.hobix.com, code.whytheluckystiff.net etc.)  
>> give the impression that Camping is neglected (also with the  
>> CHANGELOG frozen at 1.5 in 2006), and that's a bit sad for such a  
>> nice little framework! Perhaps the community could list and  
>> collate the necessary changes/updates on each page, then updating  
>> could be shared (I'd be more than willing to do updates)?
>>
>> An external website would be an extra to collect links and provide  
>> an overview, with - say - where get Camping, recent examples from  
>> the community, how-to guides (or links and previews), etc. all in  
>> one SEO-optimised place. Also, Camping does have some advantages  
>> over - say - Sinatra (one being that Sintra needs a reload with  
>> each code update) - these aren't immediately apparent unless  
>> pointed out. A few of the best Ruby Micro-frameworks deserve a  
>> fair hearing, and Camping isn't getting all the web presence it  
>> deserves - that's what motivates me!
>>
>> - Dave Everitt