Re: adaptTo(Berlin) 2012
Hi all, For those interested in attending this event, I'd like to share the registration page [1] and the current CFP [2]. Logistics in summary: when: September 26-28 where: Berlin, SUPERMARKT [3] how much: 50 euros [1] - http://adaptto.mixxt.de [2] - http://adaptto.mixxt.de/networks/wiki/index.CallforPapers2012 [3] - http://www.supermarkt-berlin.net/en/venue Regards, -- Paolo On Tue, May 22, 2012 at 10:46 PM, Michael Dürig mdue...@apache.org wrote: Dear Apache Jackrabbit developers and users, after last year's edition (http://adaptto.mixxt.de/) which got very good feedback from attendees, Provision and Adobe would like to organize and invite you to an event focused on our technologies, in Berlin, Germany, on September 26th-28th, called .adaptTo(Berlin) 2012. A brief description of the event follows below; please note that this is kept in a draft fashion to let the communities (Sling, Jackrabbit) shape its final content and organization. So please let us know if you are interested, what suggestions and what questions you would like to post, and, most of all: what you want to present or you would like to see presented at .adaptTo(Berlin) This is a brief description which we also put up on the web site: .adaptTo(Berlin) is a technical meetup focused on the technical stack of Apache Sling including Apache Jackrabbit and Apache Felix and is adressed to all developers using this stack or parts of it. Specific content will be focused on Adobe CQ5, the commercial WCM system whose infrastructure is based on the Sling stack and the commercial JCR Implementation Adobe CRX. This event is sponsored by Adobe Systems and pro!vision GmbH which also acts as host. The goal of this meetup is the consolidation of the experience and knowledge of the existing Apache Sling, Apache Jackrabbit and Apache Felix community and to introduce the complete Sling stack to newcomers. To achive this goal we'll try to bring developers and users (which means developers who work on top of this framework) together, talking about the framework and presenting solutions or best practices. Attendees that have not much experience with one or more parts of this stack will get the chance to get a kickstart introduction to Apache Jackrabbit, Apache Felix and Apache Sling on the first day. Day 1 of this meetup will therefore give unexperienced attendees the possiblity to learn the basic principles of this technological stack, while experienced users can set up free meetups in the style of a barcamp. Day 2 3 will include session on the open source Apache projects, Apache Sling, Apache Felix and Apache Jackrabbit, as well as some breakout sessions focused on Adobe CQ5 and CRX. The idea is to have a good mix of presentations, hands-on sessions, free discussions and maybe even workshops or a hackaton. Note: This is only a draft how we think this event could work, but since this is a community driven event, further planning and discussion of the contents of the meeting will be continued in the public mailinglists. where/when: Berlin, September 26-28 2012 Target audience: Developers working with Sling, Jackrabbit, CQ and other related projects. Michael -- Paolo Mottadelli http://twitter.com/paolomoz
Content Technology Track at ApacheCon North America 2010?
Hi, I'm not sure that cross posting this message is the right way for this; please eventually pick me up on any better way. planners@ are requesting a first draft proposal from PMC's for presenting their projects at ApacheCon North America, Atlanta 1st-5th November. Unfortunately this is required in a very short time frame (21st March) Both in the POI and Chemistry communities, there has been an idea of joining a more generic track at ApacheCon, such as a Content Related projects one, the same we did last year. In the Chemistry case, there would also be other options such as New technologies or Web Services. Since last year Jackrabbit and Sling were the initial promoters of such an initiative, I was wondering whether there has been any discussion around this again. (I didn't see anything related to this on public ML's) Cheers, -- Paolo Mottadelli http://twitter.com/paolomoz
Re: Content Technology track at the ApacheCon US 2009
Hi all, I'm helping in sorting out things within the POI project. How should we merge proposals from all the ConTechTrack and build an organic overall proposal? What should we take as the Track mailing list (if in any way needed...)? Thanks, -- Paolo Mottadelli: http://www.paolomottadelli.com
Re: [RESULT] [VOTE] Approve Chemistry for Incubation
On Sun, Apr 26, 2009 at 11:44 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: The vote passes as follows: +1 Alexander Klimetschek +1 Dominique Pfister +1 Felix Meschberger +1 Jukka Zitting +1 Julian Reschke +1 Marcel Reutegger +1 Stefan Guggisberg +1 Thomas Müller +1 Tobias Bocanegra Thanks for voting! I'll now ask the Incubator to accept Chemistry with Jackrabbit as the sponsoring PMC. Thanks guys for your interest in Chemistry! -- Paolo Mottadelli Sourcesense - making sense of Open Source: http://www.sourcesense.com M: +39 335 6502416 Skype/Twitter: paolomoz Blog: http://www.paolomottadelli.com
Re: Next steps for Chemistry
On Mon, Apr 27, 2009 at 12:00 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: To keep everyone on track of what's happening with Chemistry, here's a list of things that are going to happen: Thanks Jukka for this update. It would be a good day next Thursday to have Chemistry as a new project, also considering the concomitance with the CMIS Plug Fest! -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Content Technology track at the ApacheCon US 2009
Hi, On Thu, Apr 23, 2009 at 11:37 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: It would be cool to have a track related to content repositories and content management I like your idea. This is based on the same idea of the 'Interoperability' one, that I mentioned some days ago. Jackrabbit and Sling would form a nice core for such a track, but we could also include sessions on things like Chemistry and other related projects. POI is often used in CM contexts and products; do you think that such a project could fall within such a track? Cheers, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Content Technology track at the ApacheCon US 2009
On Thu, Apr 23, 2009 at 1:28 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: I'm sure we can easily fill a half-day track with Jacrkabbit, Sling, Chemistry, and by inviting related projects like POI, Tika, etc. to contribute. +1 I'm forwarding this message to the POI community, which is strongly willing to join some other project. I've also submitted a proposal about 'POI' (besides one about 'CMIS' and another about 'Apache in Open Source ECM') Hope this is going to help. Cheers, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi Jukka, On Tue, Apr 21, 2009 at 2:54 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: In general I'd restrict the set of initial committers to people who've already been contributing to the initial codebases or the related discussions. Thanks for this clarification. I agree with your valuable suggestion. Engagement rules were not totally clear to me before this. I was suggesting Salvatore to join us as he is currently contributing to some related projects, such as the Spring JCR integration. I've removed Salvatore from the Initial Committers list; I'm sure he will join the list in a while with his contributions. Thanks, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Naming Chemistry
On Tue, Apr 21, 2009 at 7:00 PM, Florent Guillaume f...@nuxeo.com wrote: I contend that Chemistry is good enough. +1 btw Florent, , your original suggestion (Camaieu) was even better! ;-) -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
PMC Invitation to Participate in ApacheCon 2009/US
Hi all, I'm forwarding this message, sure that everybody is already up-to-date with it. This is mostly about the CMIS/Chemistry effort. As part of the POI PMC I'm proposing to build a thematic track about Interoperability. The main reasons for this proposal are the following: _ We have a bunch of small yet charming projects that should join under one single umbrella in a context such as the ApacheCon _ Interoperability fits totally well in an Apache context, see concepts like: + The Apache Way + The Apache Infrastructure + The sustainable way we drive standards with RI, TCK and others + The presence of specific projects driving efforts in this direction _ A first bunch of projects directly involved in this would be: POI, CMIS/Chemistry, Stonehenge, QPid I see that Jackrabbit could not be directly interested in such a venture, having it already a good critical mass of interest around; anyway, the CMIS/Chemistry effort could find itself in a good context Do you see any interest in such a proposal or does it pull out some more interesting ideas? Cheers, -- Paolo -- Forwarded message -- From: ApacheCon 2009 US Planners Team planners-2009...@apachecon.com Date: Wed, Apr 15, 2009 at 3:28 AM Subject: PMC Invitation to Participate in ApacheCon 2009/US To: All Apache PMCs p...@apache.org Project Management Committees, For this 10th Year of the Apache Software Foundation, the Conference Planning Committee and Stone Circle Productions are infusing ApacheCon US 2009 with the same Community Spirit that guides our Open Source Communities themselves. With the goal of creating the most successful ApacheCon to-date, we are seeking the support of each ASF Community to help drive their content for the 3-day conference. As the PMC, we invite you to come forward with content based on the needs of your user community. First: Decide as a project, how much time you would like to fill with commercially viable content. Do you need a half-day or a full-day to achieve a professional, quality program? Don't restrict yourselves to presentations by the PMC members or past speakers. You are likely familiar with other committers, the members of your user community, published authors and others who would offer effective sessions. Consider involving the community in this process through either the dev or users list, as appropriate for your project. Identifying the exact contents and schedule of your program will come in a 2nd phase. Note: If you believe your track is better presented in tandem with other project(s), and you would like to work together as a small group of related projects to create a unified track, please discuss this with the other project(s) and offer one proposal you all agree upon to the Planners. Second: Identify your consumers. Please explain to the Planners, in your submission, who your attendees would be. Are they web content authors or developers, or backend infrastructure adopters, integrators or administrators? Are they technical or novice individuals, management or general users? Third: Communicate your interest to planners-2009...@apachecon.com no later than April 21st! The Planners will get back to you by April 28th to share the general program schedule, and where your project best fits. You will be provided a mentor who will forward to you the CFP's which made the first cut of talk selections. Your community will then have two weeks to create a schedule on a Wiki page. Again, be creative, and keep in mind there are several opportunities for content beyond the programmed track: MeetUps, BOFs, symposiums, un-conference style activities, etc. In four weeks, the Planners will complete a review of the programming, offer final feedback, cut programming that doesn't fit into the formal tracks of the program, and finally attempt to fit all of the programming into space available. Your mentor is there to help you avoid this cut and guide you in creating a professional and marketable track! Should a PMC choose not to participate in this process, but there are still compelling presentations about that particular project, the Planners may choose to run that track. Speaker acceptance/rejections will be sent out in five weeks, once all decisions are made. All projects, participating in this program or not, will have opportunities to get more involved with the conference. These will be announced over the coming months. We look forward to your PMC's response! Yours, The ApacheCon 2009 US Planning Team - To unsubscribe, e-mail: private-unsubscr...@poi.apache.org For additional commands, e-mail: private-h...@poi.apache.org -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Incubating Chemistry (Was: IP clearance for the Chemistry contribution)
Hi, On Thu, Apr 16, 2009 at 3:38 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: However, it seems that with quite a bit of interest around this and with the codebase and potential committers having just a little overlap with Jackrabbit core, it might be better to take the effort to the Apache Incubator where the codebase and related community can evolve more freely without being bound too tightly to Jackrabbit. This is very nice news. I'm sure this is going to give more visibility to the Chemistry project and, hopefully one day, make it graduate as a Jackrabbit subproject. -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Chemistry (PMC Invitation to Participate in ApacheCon 2009/US)
Hi Florent, On Thu, Apr 16, 2009 at 9:40 PM, Florent Guillaume f...@nuxeo.com wrote: FWIW I have submitted a talk proposal about Chemistry for ApacheCon US 2009 a few months ago. I have no idea if it's going to be accepted by the program committee, but if yes then that would be already a visible presence at ApacheCon. As per my understanding of the Planners' invitation, having already submitted your proposal about Chemistry is the ideal starting point. Now PMCs should come up with valuable proposals and give guidance to Planners about conference contents. After PMCs submitting their 'big picture' programs, talks will be elected among the ones already submitted. That is to say: Planners are going to drive a double phase selection; phase 2_ coming on top of 1_: 1_ PMCs programs selection 2_ Talks selection If the previous considerations stand, we should firstly come up with an interesting program (including 1 or more projects); this will increase chances of success for submitted talks surfing around such a program. Is my understanding about this correct? Cheers, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: CMIS / Camaieu
Even if -Camaieu- IMHO is very 'sexy', I also understand that it could be difficult to fix for non-French speakers. +1 for -Chemistry-, I like it as well. Cheers, On Thu, Feb 26, 2009 at 4:35 PM, Alexander Klimetschek aklim...@day.com wrote: On Thu, Feb 26, 2009 at 4:12 PM, Torgeir Veimo torg...@pobox.com wrote: What about CheMIStry? After all, it's about mixing various types of systems here. +1 Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Working on CMIS
Thank you Florent for your interest in this topic. I'm sure that all the people currently working on the cmis sandbox are really keen to have new heads on the project. IMHO, having a system (like Nuxeo) using (and contributing to) the cmis component is an excellent catch in order to get more quality in our work. Hope to hear from you soon. On Sat, Feb 7, 2009 at 1:56 AM, Florent Guillaume f...@nuxeo.com wrote: Hi all, I'm from Nuxeo, and we plan on working a lot on CMIS in the coming months. We're very interested in the young but promising ideas embodied in the current jcr-cmis sandbox, because we plan on offering CMIS bindings on top of our current repository (Nuxeo 5.2). We'll be using and contributing to the API+client parts of the jcr-cmis project very soon, and I wanted to announce this to you first. Nuxeo has been using Jackrabbit as one of its underlying content storage for quite some time, and we're quite familiar with it. However for the time being our area of focus will not be the CMIS-to-JCR (server) part, but the building of a complete Java API and model for CMIS, and the bindings of AtomPub and SOAP to it. Internally we'll be writing a binding from the Java API to our Nuxeo Core API. I'm not yet an Apache committer so our contributions will take the form of patches for the time being. I'll be floating ideas soon about code and stuff :) Thanks, Florent -- Florent Guillaume, Head of RD, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: [cmis] api and general structure, client implementation
Hi all, On Mon, Jan 12, 2009 at 9:36 AM, David Nuescheler da...@day.com wrote: since i think it should also be a goal of this implementation to make our code as re-uable as possible, it is great that it does not have any specific proprietary jackrabbit dependencies but really just jcr dependencies. on top of that i think it would also be great to expose the entire cmis model as a separate api. Yes, this is what we were thinking about, as well; thinking of naming it 'model'. So let's go with the 'api' one; I totally agree. i would like to take that a step further and also propose that we have a cmis client. i think this is something that is really important and help everybody developing something around cmis a great deal. so. i would propose that we have an svn subproject structure that is something like this. I think that the client subproject could be structured as a sort of TCK for our server implementation; in that case it should be structured to support generic functionalities and could be, one day, a useful tool for other implementations. WDYT? -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
[jira] Created: (JCRCMIS-4) Validate copyright/license coverage
Validate copyright/license coverage --- Key: JCRCMIS-4 URL: https://issues.apache.org/jira/browse/JCRCMIS-4 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Paolo Mottadelli The copyright and license on CMIS Specification have to be managed. At the moment we are adding a copyright-notice.txt file at the root of the CMIS sandbox, reporting the same notice provided in the CMIS Specification document -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRCMIS-1) Move parent/version/dependencies to latest Jackrabbit development version
[ https://issues.apache.org/jira/browse/JCRCMIS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12658826#action_12658826 ] Paolo Mottadelli commented on JCRCMIS-1: Patch applied. Thanks Move parent/version/dependencies to latest Jackrabbit development version - Key: JCRCMIS-1 URL: https://issues.apache.org/jira/browse/JCRCMIS-1 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro Attachments: JCRCMIS-1.diff POM files still refer to Jackrabbit 1.5-SNAPSHOT as parent, using 1.5-SNAPSHOT as version and 1.4 in certain dependencies. It's suggestable to have 1.6-SNAPSHOT as project version, as parent version of Jackrabbit and in Jackrabbit dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRCMIS-6) [WS] Have proper License included in the WSDL generated java file
[ https://issues.apache.org/jira/browse/JCRCMIS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12658859#action_12658859 ] Paolo Mottadelli commented on JCRCMIS-6: If we automatically generate classes from wsdl (using the wsdl2java tool), we also have to add the license comment automatically, or we will have to do it manually every time we need to regenerate the classes from a new version of wsdl. [WS] Have proper License included in the WSDL generated java file - Key: JCRCMIS-6 URL: https://issues.apache.org/jira/browse/JCRCMIS-6 Project: Jackrabbit CMIS Sandbox Issue Type: Task Reporter: Gabriele Columbro Priority: Minor Java classes/interfaces generated by CXF wsdl2java are now without license. Either add it manually (boring ;) ) or have wsdl2java generate files with proper license. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: jcr-cmis WS volounteers/approach
Hi all, find my comments below. By the time, I created this pom.xml, 1.5 was not officially released yet, and I copied a pom.xml from some other sandbox project. We could very well depend on the latest development version or on the released version, whatever seems more appropriate, or even drop the parent reference as well. In the spirit of implementing a JCR compliant CMIS, if we don't have any technical reason of having Jackrabbit as a parent project, I'd opt for dropping the parent reference untill we'll need it. __Core technologies (Axis or CXF) Which WS framework would you suggest? At the moment I have a better feeling for CXF with respect to Axis(2), maybe for the lower footprint it seems to have, but I never had hands on expertise with both frameworks. Any suggestion/direction here of course more than welcome. Axis is the only framework I heard of right now, but I was hoping that there is some better approach ;) ATM I'm playing with CXF and it is making me confident enough; the main reasons for which I've chosen it for these test are: _ they say CXF has better support for JAX-WS _ it has a simpler approach to make things start __'jcr-cmis' component in Jira As I mentioned before, does it make sense to have a specific component for this bit of the sandbox or just use the 'sandbox' component? I'd prefer having a specific component. +1 for a specific component for me, as well __Dynamically generate services interfaces and commit wsdl files? As a starting point, we were thinking of generating the Java interfaces from committed WSDL files with cxf as described here [3]. Also committing the WSDL, we could automatically regenerate the interfaces upon specs changes using the maven plugin [4]. Do you have any objections/suggestions for this approach? Sounds good to me. I started creating a couple of interfaces from the spec, but if we can have them generated through WSDL and use them in the atompub part as well, even better :) I've generated interfaces starting from the WSDL using the CXF wsdl2java command. For this first phase, it would be reasonable to consider these as a commodity we could add; I'd focus more on validating the better technology for us. Cheers, -- Paolo Kind regards Dominique Eager to hear your comments/suggestions (if you could make it trough this long email :). Ciao, Gab [1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=10591component=12310830resolution=-1sorter/field=prioritysorter/order=DESC : [2] http://people.apache.org/repo/m2-snapshot-repository [3] http://cwiki.apache.org/CXF20DOC/wsdl-to-java.html [4] http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html -- Gabriele Columbro Alfresco ECM Product Strategy Consultant +31 627 565 103 Sourcesense - Making sense of open Source (http://www.sourcesense.com) -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: jcr-cmis WS volounteers/approach
Hi Jukka, On Tue, Dec 9, 2008 at 3:00 PM, Jukka Zitting [EMAIL PROTECTED] wrote: How about if I created a new Jira project like JCRCMIS for this? Having sandbox issues in the JCR project has always been a bit distracting for release management purposes, and with a specialized Jira project for the CMIS effort you could also have more fine-grained component labels like ws or atompub. From our perspective it sounds better for the same reason :-) +1 for me -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Opening up the sandbox (Was: jcr-cmis sandbox)
Hi, As an informal rule I'd still expect external committers who choose to commit to our sandbox to be subscribed on dev@ and to follow at least the relevant parts of [EMAIL PROTECTED] OK, Jukka. I've been following dev@ for several months ;-) and I've just subscribed on [EMAIL PROTECTED] Cheers, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: jcr-cmis sandbox
Hi all, 2 words about me. working for Sourcesense, committer of Apache POI implementing the Open XML format support, very close to the CM world, in particular to JCR; I have been also working on Alfresco for a couple of years. I am very excited by this thread, since I am one of those hoping that CMIS could be, at least, a battering-ram towards better interoperability among CM vendors. The specification is in a very early stage and a lot of things need to be addressed [2], but it has peeked the interest of a number of people at Apache already. Yes, this is because there is already a missing brick for CMIS in order to be successful, that is a Reference Implementation where to build the Specs. Sounds good. We can get started fast in the sandbox and decide later whether the effort should be promoted to Jackrabbit trunk, turned into a subproject, or branched off somewhere else. If there are existing Apache committers from other projects who'd be interested in working on this, then we could simplify things by opening write access in the Jackrabbit sandbox to all Apache committers. So, here is one! I like the proposal to create a sandbox where we can put stuff that could turn out very good stuff or just junk... Yes: sandbox + committers r/w on it would be the simplest approach. Cheers, -- Paolo Mottadelli: http://www.paolomottadelli.com Sourcesense - making sense of Open Source: http://www.sourcesense.com
