Hi Will, I saw your email yesterday, and am back today, Philipp beat me to it!
Indeed, there's undercover work in progress for this... when I have some extra time. I hope to reveal more at the conference ;) In the meantime: * no need to change your package structure; it is and will still be *your* project. * when I get a little more time, I'll finish up the underground work, and will let you know. We're planning on opening up: Jira, Subversion, Hudson, and hopefully we'll also put in place some mechanism to "publish" your module(s) on the store or elsewhere. Cheers, -g On Jul 16, 2010, at 11:09, Will Scheidegger wrote: > > Thanks for the feedback, Philipp. And thanks for considering accepting this > module into the "Magnolia habitat". What would the necessary steps be? From > my part, I'll move the code to the info.magnolia namespace. And then? SVN? > JIRA? > > Regards, > -will > > On 16.07.2010, at 09:42, Philipp Bärfuss wrote: > >> >> Hi Will, >> >> We really want to lower the barrier to host magnolia related modules in our >> infrastructure and the first steps were already taken. A ready made >> Jackrabbit OCM integration is definitely something which fits very well. As >> far I see it could indeed become a base for several other modules. >> >> So yes, lets take the necessary steps to bring this module and the shop into >> the Magnolia habitat. >> >> Cheers >> >> Philipp >> >> On 15.07.2010, at 18:17, Will Scheidegger wrote: >> >>> >>> Dear Magnolia developers >>> >>> As you might have already seen on the user list we have made publicly >>> available a "magnolia-module-ocm" which integrates Jackrabbit OCM into >>> Magnolia. This module should be very useful to all who need to persist >>> POJOs into the JCR repository and back. For instance the (hopefully) >>> upcoming shop module will most likely make heavy use of it and get rid of a >>> home grown object content library instead. >>> >>> At this time the module is only available as jar download from our server. >>> Also the package names are in the ch.fastforward.magnolia namespace. >>> However we would like to open source it fully and propose to turn it into >>> an "official" magnolia module with >>> - info.magnolia package names >>> - code on svm.magnolia-cms.com >>> >>> What do you think: Useful or useless? Turn into an official magnolia module >>> or leave it as it is? >>> >>> See >>> http://www.fastforward.ch/web/ff/dokumentation/entwickler/magnolia-module-ocm.html >>> for more info. >>> >>> Regards, >>> -will >>> >>> ---------------------------------------------------------------- >>> For list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> To unsubscribe, E-mail to: <[email protected]> >>> ---------------------------------------------------------------- >> >> Cheers >> - Philipp >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
