You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2010/12/03 17:05:12 UTC

[jira] Commented: (SLING-1438) GSoC 2010: create a mini-CMS to demonstrate Sling

    [ https://issues.apache.org/jira/browse/SLING-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966563#action_12966563 ] 

Bertrand Delacretaz commented on SLING-1438:
--------------------------------------------

I finally found time to look at this to see if we can commit it alongside the Sling samples.

The following licenses, mentioned in 3rdparty.txt, are not ok for redistribution with Apache projects [1], so we cannot commit the code as is:

WP-Cumulus SWF : GPL v3 license - http://wordpress.org/extend/plugins/wp-cumulus/
iText :  AGPL v3 license - http://itextpdf.com/terms-of-use/index.php

Does it make sense to create a version of the mini-CMS that doesn't use these tools? 

[1] http://www.apache.org/legal/resolved.html

> GSoC 2010: create a mini-CMS to demonstrate Sling
> -------------------------------------------------
>
>                 Key: SLING-1438
>                 URL: https://issues.apache.org/jira/browse/SLING-1438
>             Project: Sling
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Bertrand Delacretaz
>            Assignee: Federico Paparoni
>         Attachments: david.rar, david16092010.zip
>
>
> This is a suggested project for Google Summer of Code 2010.
> The goal is to create a mini-CMS with Sling, that demonstrates Sling best practices.
> The emphasis is on the quality and readability of the demo code, and we expect to have to go through several iterations to refine it and the corresponding JCR content model so that they demonstrate Sling best practices. We will not necessarily create a full-fledged CMS, the goal is for the result to be educational and help Sling newcomers understand how to create web applications with it.
> Suggested technologies: jQuery for the front-end, ESP and/or JSP for server-side scripting, and Java code in OSGi bundles for back-end functionality.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.