You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Anil Ramnanan (JIRA)" <ji...@apache.org> on 2005/08/17 16:33:12 UTC

[jira] Created: (FOR-636) Daisy Repository Browser

Daisy Repository Browser 
-------------------------

         Key: FOR-636
         URL: http://issues.apache.org/jira/browse/FOR-636
     Project: Forrest
        Type: New Feature
  Components: Tool: Eclipse config  
    Versions: 0.8-dev    
    Reporter: Anil Ramnanan


This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Updated: (FOR-636) Daisy Repository Browser

Posted by Ross Gardler <rg...@apache.org>.
Anil Ramnanan (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/FOR-636?page=all ]
> 
> Anil Ramnanan updated FOR-636:
> ------------------------------
> 
>     Attachment: org.apache.forrest.repository.200805.zip
> 
> This splits the repository browser into two plugins. One plugin contains code specific to the Daisy repository and the other contains an interface that 
> will be configurable so that different repositories could be used.
> 
> This replaces the previous ile org.apache.forrest.repository.daisy.180805.zip which is no longer needed.

I'm on Internet Cafe connections for around the next week. My updates
will be slow. It was a last minute trip so no chance to warn you I'm afraid.

I'll do the best I can to review your code so that others can commit,
however, other committers should be aware that generally I am only
checking legal stuff on Anils contributions now. So if you have the
time, please take a look at this patch.

Ross


Re: [jira] Updated: (FOR-636) Daisy Repository Browser

Posted by Ross Gardler <rg...@apache.org>.
Anil Ramnanan (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/FOR-636?page=all ]
> 
> Anil Ramnanan updated FOR-636:
> ------------------------------
> 
>     Attachment: org.apache.forrest.repository.200805.zip
> 
> This splits the repository browser into two plugins. One plugin contains code specific to the Daisy repository and the other contains an interface that 
> will be configurable so that different repositories could be used.
> 
> This replaces the previous ile org.apache.forrest.repository.daisy.180805.zip which is no longer needed.

I'm on Internet Cafe connections for around the next week. My updates
will be slow. It was a last minute trip so no chance to warn you I'm afraid.

I'll do the best I can to review your code so that others can commit,
however, other committers should be aware that generaly I am only
checking legal stuff on Anils contributions now. So if you have the
time, please take a look at this patch (and others).

Ross


[jira] Updated: (FOR-636) Daisy Repository Browser

Posted by "Anil Ramnanan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]

Anil Ramnanan updated FOR-636:
------------------------------

    Attachment: org.apache.forrest.repository.200805.zip

This splits the repository browser into two plugins. One plugin contains code specific to the Daisy repository and the other contains an interface that 
will be configurable so that different repositories could be used.

This replaces the previous ile org.apache.forrest.repository.daisy.180805.zip which is no longer needed.

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (FOR-636) Daisy Repository Browser

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/FOR-636?page=comments#action_12319683 ] 

David Crossley commented on FOR-636:
------------------------------------

Applied org.apache.forrest.repository.200805.zip

Made some minor changes:
* Added missing license header for one file.
* Fix the copyright date on each file to be 2005.

Also, did not commit the pre-compiled classes in the "bin" directory.
Is that correct?

 

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>     Assignee: David Crossley
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (FOR-636) Daisy Repository Browser

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]
     
David Crossley closed FOR-636:
------------------------------

    Fix Version: 0.8-dev
     Resolution: Fixed

There is duplication of jars in the various plugins/*/lib/ directories and even different versions of some jars. This problem will be addressed by FOR-560

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>      Fix For: 0.8-dev
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: Properly licensed icons

Posted by Ross Gardler <rg...@apache.org>.
Anil Ramnanan wrote:
> Ross Gardler (JIRA) wrote:
> 
>> Also note that the "sample.gif" included in this zip is not released 
>> under a compatible license, it is created by Eclipse wizards and is 
>> therefore under the EPL (I've been caught out by this one myself).
>>  
>>
> I was wondering what kind of license is appropriate for icons. Would I 
> be able to use icons that were released under a creative commons license ?

As others have said it depends on which of the CC licenses is used.

A good source of clipart and icons that we *can* use is 
http://www.openclipart.org/ This stuff is released under the CC "No 
Rights Reserved" license. Which is essentially public domain.

Note that we cannot relicense these images so we must include a license 
file for them.

Ross

Re: Properly licensed icons

Posted by David Crossley <cr...@apache.org>.
Anil Ramnanan wrote:
> David Crossley wrote:
> 
> >It depends. The main thing is that we cannot add anything
> >that has retrictions beyond the terms of the Apache License.
> >
> >Please direct us to an example of something that you want
> >to include and to their license conditions.
> >
> Here is an example of icons that are made available under the Creative 
> Commons license.
> http://www.graphicpush.com/index.php?s=icons
> 
> Here is the license that it is released under:
> http://creativecommons.org/licenses/by-sa/2.5/
> 
> Basically the license states
> You are free:
>    * to copy, distribute, display, and perform the work
>    * to make derivative works
>    * to make commercial use of the work
> 
> Under the following conditions:
> by    Attribution. You must attribute the work in the manner specified 
> by the author or licensor.

Most such licenses would ask for simple attribution
and we add it to our trunk/NOTICE.txt file. If these
people ask for something beyond that then we need
to assess that requirement.

>       Share Alike. If you alter, transform, or build upon this work, 
> you may distribute the resulting work only under a license identical to 
> this one.

See Ferdinand's comments.

>    * For any reuse or distribution, you must make clear to others the 
> license terms of this work.

That is okay. We would add their license beside
those files and retain their copyright headers.

>    * Any of these conditions can be waived if you get permission from 
> the copyright holder.

We wouldn't.

-David 

Re: Properly licensed icons

Posted by David Crossley <cr...@apache.org>.
Anil Ramnanan wrote:
> 
> Would I be ok with a BSD license ?

Basically, yes. We still need to investigate
each case.

> The only Icon collection I have found with such a licence is here.
> http://sourceforge.net/projects/icon-collection

Nope, there is a gotcha. I downloaded and looked at
the README. It says that it cannot be used without
his explicit consent. So, boom! ... cannot include it.

Clauses like this mean that all of our users must
obtain consent.

-David

Re: Properly licensed icons

Posted by Anil Ramnanan <li...@peppersauce.org>.
David Crossley wrote:

>Ferdinand Soethe wrote:
>  
>
>>With creative commons licences it is extremely important to take a
>>close look at the license options as there are a variety of different
>>flavours that are explained very well at their website
>>http://creativecommons.org/.
>>
>>Anil Ramnanan wrote:
>>    
>>
>>>Share Alike. If you alter, transform, or build upon this work, 
>>>you may distribute the resulting work only under a license identical to
>>>this one.http://creativecommons.org/
>>>      
>>>
>>If the share alike option is selected then this license is probably
>>not compatible with the Apache License.
>>    
>>
Would I be ok with a BSD license ?
The only Icon collection I have found with such a licence is here.
http://sourceforge.net/projects/icon-collection

Regards,
Anil.

Re: Properly licensed icons

Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> 
> With creative commons licences it is extremely important to take a
> close look at the license options as there are a variety of different
> flavours that are explained very well at their website
> http://creativecommons.org/.
> 
> Anil Ramnanan wrote:
> > Share Alike. If you alter, transform, or build upon this work, 
> > you may distribute the resulting work only under a license identical to
> > this one.http://creativecommons.org/
> 
> If the share alike option is selected then this license is probably
> not compatible with the Apache License.

That was the part that worried me too.
It inhibits our downstream re-distributors.
Also what does "build upon" mean?

In this case it might be okay. It is a set
of icons that shouldn't be changed.

If people want this, then some of our committers
need to ensure that it is okay by taking it to
the legal-discuss mailing list:
http://www.apache.org/foundation/mailinglists.html

The last time that this came up on our dev
list we were not sure about what to do.

Someone proposed to avoid the whole situation
by making a collection of Apache Licensed icons
to distribute with Forrest. Not yet happened.

Another solution would be to have a plugin
which is a Cocoon sitemap that generates a simple
graphic with text, colours, and size, based on
the request parameters. Should be easy.

Another solution would be to create a set of
static graphic icons, by extending our
trunk/tools/logos/ and we could check the
generated result into forrest core svn and/or
our plugins.

-David

Re: Properly licensed icons

Posted by Ferdinand Soethe <fe...@apache.org>.
David Crossley wrote:

> Careful, that is old and only addresses the previous
> version of the Apache License.

Darn, and I was so happy to have found something that I could
understand ;-) Thanks for pointing that out.

--
Ferdinand Soethe


Re: Properly licensed icons

Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> 
> There's a pretty good comparison of important open source licences at
> http://www.unt.edu/benchmarks/archives/2003/august03/copyright.htm.

Careful, that is old and only addresses the previous
version of the Apache License.

-David

Re: Properly licensed icons

Posted by Ferdinand Soethe <fe...@apache.org>.





Ferdinand Soethe wrote:

> If the share alike option is selected then this license is probably
> not compatible with the Apache License.

There's a pretty good comparison of important open source licences at
http://www.unt.edu/benchmarks/archives/2003/august03/copyright.htm.

--
Ferdinand Soethe


Re: Properly licensed icons

Posted by Ferdinand Soethe <fe...@apache.org>.
Anil Ramnanan wrote:

With creative commons licences it is extremely important to take a
close look at the license options as there are a variety of different
flavours that are explained very well at their website
http://creativecommons.org/.


> Share Alike. If you alter, transform, or build upon this work, 
> you may distribute the resulting work only under a license identical to
> this one.http://creativecommons.org/

If the share alike option is selected then this license is probably
not compatible with the Apache License.

--
Ferdinand Soethe


Re: Properly licensed icons

Posted by Anil Ramnanan <li...@peppersauce.org>.
David Crossley wrote:

>It depends. The main thing is that we cannot add anything
>that has retrictions beyond the terms of the Apache License.
>
>Please direct us to an example of something that you want
>to include and to their license conditions.
>
>-David
>
>  
>
Here is an example of icons that are made available under the Creative 
Commons license.
http://www.graphicpush.com/index.php?s=icons

Here is the license that it is released under:
http://creativecommons.org/licenses/by-sa/2.5/

Basically the license states
You are free:
    * to copy, distribute, display, and perform the work
    * to make derivative works
    * to make commercial use of the work

Under the following conditions:
by    Attribution. You must attribute the work in the manner specified 
by the author or licensor.
       Share Alike. If you alter, transform, or build upon this work, 
you may distribute the resulting work only under a license identical to 
this one.

    * For any reuse or distribution, you must make clear to others the 
license terms of this work.
    * Any of these conditions can be waived if you get permission from 
the copyright holder.


Anil.


Re: Properly licensed icons

Posted by David Crossley <cr...@apache.org>.
Anil Ramnanan wrote:
> Ross Gardler (JIRA) wrote:
> 
> >Also note that the "sample.gif" included in this zip is not released under 
> >a compatible license, it is created by Eclipse wizards and is therefore 
> >under the EPL (I've been caught out by this one myself).
>
> I was wondering what kind of license is appropriate for icons. Would I 
> be able to use icons that were released under a creative commons license ?

It depends. The main thing is that we cannot add anything
that has retrictions beyond the terms of the Apache License.

Please direct us to an example of something that you want
to include and to their license conditions.

-David

Properly licensed icons (was: [jira] Commented: (FOR-636) Daisy Repository Browser)

Posted by Anil Ramnanan <li...@peppersauce.org>.
Ross Gardler (JIRA) wrote:

>Also note that the "sample.gif" included in this zip is not released under a compatible license, it is created by Eclipse wizards and is therefore under the EPL (I've been caught out by this one myself).
>  
>
I was wondering what kind of license is appropriate for icons. Would I 
be able to use icons that were released under a creative commons license ?

Anil

[jira] Commented: (FOR-636) Daisy Repository Browser

Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/FOR-636?page=comments#action_12319063 ] 

Ross Gardler commented on FOR-636:
----------------------------------

Sorry I can't apply this patch, there are a number of issues, mostly legal:

Please ensure all license files are included with your patch and that they are corerctly named (see the lib of core for examples, in particular notice that every file must have a license and that the fielname must be the same as the jar filename (including version number). This may seem like overkill but it does make life much easier when we have to check license compliance before a release.

Also note that the "sample.gif" included in this zip is not released under a compatible license, it is created by Eclipse wizards and is therefore under the EPL (I've been caught out by this one myself).

License headers in the java files show the wrong dates (there is degbate as to what the correct range is but since you are writing these in 2005, we can be pretty sure that 1999-2004 is not correct ;-)

Please stick to the naming convention for our plugins and source code.

In this case the plugin will be - org.apache.forrest.repository.daisy

No Javadocs (other than generic comments created by the Wizard)

The java classes should be - org.apache.forrest.repository.daisy.*

It looks like it'll work though :-))

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>  Attachments: daisyPlugin.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-636) Daisy Repository Browser

Posted by "Anil Ramnanan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]

Anil Ramnanan updated FOR-636:
------------------------------

    Attachment: daisyPlugin.zip

Daisy Repository Browser

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>  Attachments: daisyPlugin.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-636) Daisy Repository Browser

Posted by "Anil Ramnanan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]

Anil Ramnanan updated FOR-636:
------------------------------

    Attachment: org.apache.forrest.repository.daisy.180805.zip

Daisy Repository Browser with the changes suggested in the last comment.

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (FOR-636) Daisy Repository Browser

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]

David Crossley reassigned FOR-636:
----------------------------------

    Assign To:     (was: David Crossley)

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (FOR-636) Daisy Repository Browser

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-636?page=all ]

David Crossley reassigned FOR-636:
----------------------------------

    Assign To: David Crossley

> Daisy Repository Browser
> ------------------------
>
>          Key: FOR-636
>          URL: http://issues.apache.org/jira/browse/FOR-636
>      Project: Forrest
>         Type: New Feature
>   Components: Tool: Eclipse config
>     Versions: 0.8-dev
>     Reporter: Anil Ramnanan
>     Assignee: David Crossley
>  Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip
>
> This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira