[jira] [Updated] (COMDEV-68) [Gsoc] Lenya : Add a CMIS endpoint to Apache Lenya
[ https://issues.apache.org/jira/browse/COMDEV-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent ANDRE updated COMDEV-68: Labels: gsoc gsoc2013 mentor mentoring (was: gsoc gsoc2012 gsoc2013 mentor mentoring) Summary: [Gsoc] Lenya : Add a CMIS endpoint to Apache Lenya (was: [Gsoc2012] Lenya : Add a CMIS endpoint to Apache Lenya) [Gsoc] Lenya : Add a CMIS endpoint to Apache Lenya -- Key: COMDEV-68 URL: https://issues.apache.org/jira/browse/COMDEV-68 Project: Community Development Issue Type: New Feature Components: Comdev, Mentoring Reporter: Florent ANDRE Labels: gsoc, gsoc2013, mentor, mentoring Lenya : http://lenya.apache.org/ is an Open Source Java/XML Content Management System and comes with revision control, multi-site management, scheduling, search, WYSIWYG editors, and workflow. Content Management Interoperability Services (CMIS) is an open standard that defines an abstraction layer for controlling diverse document management systems and repositories using web protocols. ( http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services and http://chemistry.apache.org/project/cmis.html). The idea here is to implement a CMIS enpoint to the Lenya CMS with the help of Apache Chemistry (http://chemistry.apache.org/java/opencmis.html). CMIS don't define any authentication method or rule. Student will have to take care of this an propose a solution to provide authentication. This work will be helped with the atom module (http://svn.apache.org/repos/asf/lenya/contributions/2_0_X/modules/atom/) and the LenyaDocWriting module (http://svn.apache.org/repos/asf/lenya/contributions/2_0_X/modules/lenyaDocWriting/) that both define a service to interact with the Lenya repository. During this CMIS integration, proposals for repository API and implementation refactoring will be encouraged. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1459746 - /comdev/site/trunk/content/gsoc.mdtext
Author: bdelacretaz Date: Fri Mar 22 12:44:33 2013 New Revision: 1459746 URL: http://svn.apache.org/r1459746 Log: fix old 2012 links Modified: comdev/site/trunk/content/gsoc.mdtext Modified: comdev/site/trunk/content/gsoc.mdtext URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/gsoc.mdtext?rev=1459746r1=1459745r2=1459746view=diff == --- comdev/site/trunk/content/gsoc.mdtext (original) +++ comdev/site/trunk/content/gsoc.mdtext Fri Mar 22 12:44:33 2013 @@ -15,9 +15,9 @@ programme. to make sure you really want to apply to GSoC. * Watch Philip Johnson's [GSoC video presentation](http://www.youtube.com/watch?v=vBRRR0BQyz0) for students. -* Examine the list of [available ASF GSoC projects](http://s.apache.org/gsoc2012ideas) +* Examine the list of [available ASF GSoC 2013 projects](http://s.apache.org/gsoc2013ideas) ** Note that you can search the issue tracker for GSoC projects by -filtering using the gsoc2012 label, this allows you to narrow down the list +filtering using the gsoc2013 label, this allows you to narrow down the list to the projects you are interested in. a name=GSoC-ApplyingforGSoC/a
svn commit: r855560 - in /websites/staging/community/trunk/content: ./ gsoc.html
Author: buildbot Date: Fri Mar 22 12:44:37 2013 New Revision: 855560 Log: Staging update by buildbot for community Modified: websites/staging/community/trunk/content/ (props changed) websites/staging/community/trunk/content/gsoc.html Propchange: websites/staging/community/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Fri Mar 22 12:44:37 2013 @@ -1 +1 @@ -1411491 +1459746 Modified: websites/staging/community/trunk/content/gsoc.html == --- websites/staging/community/trunk/content/gsoc.html (original) +++ websites/staging/community/trunk/content/gsoc.html Fri Mar 22 12:44:37 2013 @@ -115,9 +115,9 @@ programme./p to make sure you really want to apply to GSoC./li liWatch Philip Johnson's a href=http://www.youtube.com/watch?v=vBRRR0BQyz0;GSoC video presentation/a for students./li -liExamine the list of a href=http://s.apache.org/gsoc2012ideas;available ASF GSoC projects/a +liExamine the list of a href=http://s.apache.org/gsoc2013ideas;available ASF GSoC 2013 projects/a ** Note that you can search the issue tracker for GSoC projects by -filtering using the gsoc2012 label, this allows you to narrow down the list +filtering using the gsoc2013 label, this allows you to narrow down the list to the projects you are interested in./li /ul pa name=GSoC-ApplyingforGSoC/a/p
svn commit: r855561 - /websites/production/community/content/
Author: bdelacretaz Date: Fri Mar 22 12:45:15 2013 New Revision: 855561 Log: fix old 2012 links Added: websites/production/community/content/ - copied from r855560, websites/staging/community/trunk/content/
[jira] [Created] (COMDEV-77) [GSoC] Apache OpenOffice Extension Plugin for Eclipse
Juergen Schmidt created COMDEV-77: - Summary: [GSoC] Apache OpenOffice Extension Plugin for Eclipse Key: COMDEV-77 URL: https://issues.apache.org/jira/browse/COMDEV-77 Project: Community Development Issue Type: New Feature Reporter: Juergen Schmidt Apache OpenOffice is the leading open source desktop office suite. Our most recent release has had over 40 million downloads. OpenOffice has a powerful API and extension framework that allows to extend the office with new features or provide connectors into external applications and simplify the interoperability between the application and office. Many service provider interfaces (SPI) are available and allow specific integration into existing areas. For example you can provide extensions that behaves as normal build in function in the spreadsheet application. Or you can provide an grammar checking extensions etc. A key element here to simplify the development of such extensions is to have a good tooling. There is already a plugin available for NetBeans [1] that provides some basic project types and wizards to simplify the setup of a new project and the ongoing maintenance and development (including deployment and debugging in the office) of such extension projects. The idea is to have a similar plugin for Eclipse in place to reach even more extension developers and give them a powerful tooling to speed up their work and to help growing the eco-system around OpenOffice. The focus is here on Java extensions but on demand the support for C++ or Python extension is also possible. Project scope and ideas: 1. thinking about a good project structure for an Eclipse extension project 2. evaluating how to package an extension package (oxt), deploy it from Eclipse into the office and how to remote debug the extension in the office 3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in, Add-on, ...) and help to setup a basic project The OpenOffice SDK provided a code skeleton generator that can be used to generate necessary code skeletons. Skills needed: -- Java programming (Core Java), good working knowledge, but don't need to be a guru or anything -- open minded to learn something new, the office API and some basic concepts regarding the underlying component technology -- open to have fun with one of the biggest open source projects -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COMDEV-77) [GSoC] Apache OpenOffice Extension Plugin for Eclipse
[ https://issues.apache.org/jira/browse/COMDEV-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juergen Schmidt updated COMDEV-77: -- Description: Apache OpenOffice is the leading open source desktop office suite. Our most recent release has had over 40 million downloads. OpenOffice has a powerful API and extension framework that allows to extend the office with new features or provide connectors into external applications and simplify the interoperability between the application and office. Many service provider interfaces (SPI) are available and allow specific integration into existing areas. For example you can provide extensions that behaves as normal build in function in the spreadsheet application. Or you can provide an grammar checking extensions etc. A key element here to simplify the development of such extensions is to have a good tooling. There is already a plugin available for NetBeans [1] that provides some basic project types and wizards to simplify the setup of a new project and the ongoing maintenance and development (including deployment and debugging in the office) of such extension projects. The idea is to have a similar plugin for Eclipse in place to reach even more extension developers and give them a powerful tooling to speed up their work and to help growing the eco-system around OpenOffice. The focus is here on Java extensions but on demand the support for C++ or Python extension is also possible. Project scope and ideas: 1. thinking about a good project structure for an Eclipse extension project 2. evaluating how to package an extension package (oxt), deploy it from Eclipse into the office and how to remote debug the extension in the office 3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in, Add-on, ...) and help to setup a basic project The OpenOffice SDK provided a code skeleton generator that can be used to generate necessary code skeletons. Skills needed: -- Java programming (Core Java), good working knowledge, but don't need to be a guru or anything -- open minded to learn something new, the office API and some basic concepts regarding the underlying component technology -- open to have fun with one of the biggest open source projects [1] http://wiki.openoffice.org/wiki/OpenOffice_NetBeans_Integration was: Apache OpenOffice is the leading open source desktop office suite. Our most recent release has had over 40 million downloads. OpenOffice has a powerful API and extension framework that allows to extend the office with new features or provide connectors into external applications and simplify the interoperability between the application and office. Many service provider interfaces (SPI) are available and allow specific integration into existing areas. For example you can provide extensions that behaves as normal build in function in the spreadsheet application. Or you can provide an grammar checking extensions etc. A key element here to simplify the development of such extensions is to have a good tooling. There is already a plugin available for NetBeans [1] that provides some basic project types and wizards to simplify the setup of a new project and the ongoing maintenance and development (including deployment and debugging in the office) of such extension projects. The idea is to have a similar plugin for Eclipse in place to reach even more extension developers and give them a powerful tooling to speed up their work and to help growing the eco-system around OpenOffice. The focus is here on Java extensions but on demand the support for C++ or Python extension is also possible. Project scope and ideas: 1. thinking about a good project structure for an Eclipse extension project 2. evaluating how to package an extension package (oxt), deploy it from Eclipse into the office and how to remote debug the extension in the office 3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in, Add-on, ...) and help to setup a basic project The OpenOffice SDK provided a code skeleton generator that can be used to generate necessary code skeletons. Skills needed: -- Java programming (Core Java), good working knowledge, but don't need to be a guru or anything -- open minded to learn something new, the office API and some basic concepts regarding the underlying component technology -- open to have fun with one of the biggest open source projects [GSoC] Apache OpenOffice Extension Plugin for Eclipse - Key: COMDEV-77 URL: https://issues.apache.org/jira/browse/COMDEV-77 Project: Community Development Issue Type: New Feature Reporter: Juergen Schmidt Labels: gsoc, gsoc2013, mentor Apache OpenOffice is the leading open source desktop office suite. Our most recent
[jira] [Created] (COMDEV-78) [GSoC] CMIS Universal Contet Provider (UCP) for Apache OpenOffice
Juergen Schmidt created COMDEV-78: - Summary: [GSoC] CMIS Universal Contet Provider (UCP) for Apache OpenOffice Key: COMDEV-78 URL: https://issues.apache.org/jira/browse/COMDEV-78 Project: Community Development Issue Type: New Feature Reporter: Juergen Schmidt Apache OpenOffice is the leading open source desktop office suite. Our most recent release has had over 40 million downloads. OpenOffice used internally a universal content broker [1] to provide access on file contents. It's a very generic concept and it can be extended by providing additional content providers (UCP) [2]. Such a UCP can be provided as an optional extension or bundled directly with the office. It doesn't matter for the scope of this project and the main idea is to implement a new UCP for accessing files in a content management system supporting the OASIS standard CMIS [3]. The scope of this project is: 1. Implement a new CMIS UCP using the Apache Chemistry library [4] 2. Implement a new sidebar panel to provide an easy navigation of CMIS supporting CMS and the support of some basic CMS typical functions like check-in, check-put of documents, open and editing of files, versioning etc. Skills needed: -- Java programming (Core Java), good working knowledge, but don't need to be a guru or anything -- open minded to learn something new, the office API and some basic concepts regarding the underlying component technology -- open to have fun with one of the biggest open source projects [1] http://wiki.openoffice.org/wiki/Documentation/DevGuide/UCB/Universal_Content_Broker [2] http://wiki.openoffice.org/wiki/Documentation/DevGuide/UCB/Content_Providers [3] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis [4] http://chemistry.apache.org/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
