incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <>
Subject RE: AW: Moving content from GoogleCode to Apache
Date Wed, 15 Apr 2009 20:03:25 GMT
In my opinion, it is better to do it in the wiki. There is no time lag and the number of people
can contribute is probably higher based on the necessity of learning forrest (which isn't
difficult but still - it is not browser based). 
If you look at the SVN site, there is the forrest code (
You would just need to create a redirect to the esme wiki page
Maybe we should have a vote about using the wiki instead of forrest site.


From: Anne Kathrine Petteroe []
Sent: Wed 15.04.2009 21:55
Subject: Re: AW: Moving content from GoogleCode to Apache

Do you want to get rid of the forrest site, or just update the 
information there?
I can take care of updating it, if you tell me how it is done..


On 15. april. 2009, at 09.11, Hirsch, Richard wrote:

> Now we just have to integrate the forrest site with the Apache wiki. 
> There is currently a partial data overlap.
> D.
> ________________________________
> Von: Anne Kathrine Petteroe []
> Gesendet: So 12.04.2009 17:17
> An:
> Betreff: Re: Moving content from GoogleCode to Apache
> I have moved most of the content to the Apache wiki.
> The only content still on Google Code is everything related to the AIR
> client and the old WAR/library files.
> /Anne
> On 4. april. 2009, at 11.54, Hirsch, Richard wrote:
>> Right now, there is still a lot of content at our old Google Code
>> site ( and
>> that I think should be moved to the Apache site. There is just too
>> little traffic at the Google site and a content consolidation is
>> critical if we are to expand our community.
>> What is the best way to do this? In particular, what are the IP
>> implications /issues? The Google site has a Apache License 2.0 for
>> the code but I have no idea about the licensing for other content
>> that is located there.   Should/Can we move the content to Apache or
>> leave it at the Google site and just reference it from our pages at
>> Apache.
>> D.

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