forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r413066 - /forrest/events/forrest-friday/20060609-log.txt
Date Fri, 09 Jun 2006 15:20:05 GMT
Author: crossley
Date: Fri Jun  9 08:20:04 2006
New Revision: 413066



Modified: forrest/events/forrest-friday/20060609-log.txt
--- forrest/events/forrest-friday/20060609-log.txt (original)
+++ forrest/events/forrest-friday/20060609-log.txt Fri Jun  9 08:20:04 2006
@@ -386,3 +386,25 @@
 [00:59] cheche:  blog system
 [00:59] _Gav_: cms
 [01:00] xley: k
+[01:00] cheche: I can give you an account in mine if you want to have a look:
+[01:00] cheche:
+[01:01] xley: no thanks. Anyway, continue describing your issue.
+[01:03] cheche: well, there are 600 +  themes for a competition... and I choose one for my
+[01:03] cheche:
+[01:03] cheche: then I wanted to use forrest to create stationtect base on that theme.
+[01:03] cheche: then I wanted to use forrest to create statict contect base on that theme.
+[01:04] cheche: and I created the exo skin
+[01:04] cheche: so am I allow to publish that under the asf license?
+[01:07] xley: Depends what you did to "create the exo skin".
+[01:08] cheche: to create the exo skin you have to 
+[01:08] cheche: create the same elements with same identifiers ( div class="wrapper") so
when in the css file #wrapper is used the match and give the look and feel
+[01:09] cheche: the idea of the exo skin is to be as close as wordpress so any theme can
be used with forrest
+[01:11] xley: so the xslt is your creation and the css are from wordpress?
+[01:11] cheche: yes
+[01:11] cheche: and the images
+[01:12] cheche: well, possible the images and the css had been modify by the designer (tony
+[01:12] cheche: but there is not any information about licenses in the header.
+[01:13] cheche: so I do not know if it is ok for me to released like that... or just posibly
create a new css with direfent colours and diferent images so we are 100% ok
+[01:18] xley: i am no license expert. You could perhaps package it like we do at Forrest.
The whole thing is under Apache License. The bits that are someone else's work we declare
by adding their license.txt and if they make any conditions (such as request attribution)
then we put an entry in NOTICE.txt
+[01:19] cheche: they do not have a license.txt, but I am in contact with the developer...
+[01:19] xley: And we don't add any supporting products that are any more restrictive than
the Apache License. However for your personal release you don't need to stick to that.

View raw message