river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Ramsdale <jeff.ramsd...@gmail.com>
Subject Re: Web hosting of Jini.org was:Re: Jini.org and mailing list
Date Fri, 03 Jul 2009 03:01:53 GMT
I have one other suggestion to offer before we make a move. The current
jini.org site is a MediaWiki site. Sourceforge now provides MediaWiki to
projects hosted there (
http://sourceforge.net/apps/trac/sourceforge/wiki/Hosted%20Apps). Would it
make sense to move to Sourceforge (including old starter kit downloads) and
point jini.org there? One advantage is that the sf folks manage the app,
which would hopefully reduce some of the spam problems we've had. Since this
wouldn't be a standard open source project with code releases (since these
are handled by Apache River) I'm not certain if it makes sense nor if it
would be acceptable to sf, but I thought it was worth asking...

On Thu, Jul 2, 2009 at 4:22 PM, Peter Firmstone <jini@zeus.net.au> wrote:

> We've had enough volunteers willing to pay for web hosting of jini.org,
> all we need now, is info from Jim Hurley on how to make a contribution.
> Jim?
> Cheers,
> Peter.
> Elijah Menifee wrote:
>> I have run a 'wget -o obtainjiniorg.log -w 5 -m -k www.jini.org' so I
>> have a
>> mostly working local copy of the information(in non-wiki mode), however I
>> am
>> unsure if there are any utilities or methods for converting/hosting this
>> archive on the Apache infrastructure.
>> The jini.org uses MediaWiki where as the River site is set up with
>> MoinMoin,
>> the mark-up source format for these appears is different along with
>> available macros and I had no luck just pasting the the jini.org src to
>> river. So I am currently manually formatting by pasting the text and
>> adding
>> MoinMoin specific markup indicators.
>> The upside is I am making progress (slow but steady) in getting the Jini
>> Spec documents on the river site (plan on doing FAQ/HowTo/Tutorial
>> information after I get all the specs in place)
>> The downsides are as follows:
>>  1. Not very familiar with Wiki's in general so there may be MoinMoin
>> markup
>> features I am not using, or categorized pages appropriately...
>>  2. Not sure how to get images to the Apache site, so currently I am in
>> lining the images with links to the jini.org site, which means if the
>> hosting for jini.org goes down the images will be broken ( the robots.txt
>> on
>> jini.org excluded the /images/ however some of the spec images appear to
>> be
>> availeble out of the /files/... hiearchy so I do have a local copy of some
>> of the images)
>>  3. formatting is different, and there is a chance for typos, so someone
>> more familiar with jini may want to take a cursory glance after I have
>> done
>> the initial grunt work of the port.
>>  4. Not sure how MoinMoin handles page protection, so the specs are
>> currently open for anyone to edit/spam/destroy.  The original spec pages
>> on
>> the jini.org are protected...
>> If anyone has any better ideas for getting the most important information
>> on
>> to the River wiki, I am open to suggestions, however until then I will
>> continue to manually port the info as time allows.
>> Until the porting work is done (...still open to suggestions on a better
>> method than manual document editing...), and we get the images local, we
>> need the hosting of jini.org to remain.
>> On Thu, Jul 2, 2009 at 5:35 AM, Niclas Hedhman <niclas@hedhman.org>
>> wrote:
>>> On Thu, Jul 2, 2009 at 6:04 PM, Peter Firmstone<jini@zeus.net.au> wrote:
>>>> There still web hosting of the jini.org site to pay for.
>>> Because?
>>> If you move the content to Apache infrastructure, and get Sun/Oracle
>>> to point the DNS accordingly, then there should only be the domain
>>> registrar fee...
>>> Cheers
>>> --
>>> Niclas Hedhman, Software Developer
>>> http://www.qi4j.org - New Energy for Java
>>> I  live here; http://tinyurl.com/2qq9er
>>> I  work here; http://tinyurl.com/2ymelc
>>> I relax here; http://tinyurl.com/2cgsug

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message