An updated process for contributing code is on the community overview page of our staging project site. (this is still a work in progress so excuse any errors)
http://shindig.staging.apache.org/community_overview.html On Friday, July 13, 2012, Stanton Sievers wrote: > Hi René, > > If you'd like to contribute code back to Shindig, the first step is to > open a JIRA [1]. The second step is to create an account on the Review > Board instance [2] and post a review with your patch. Within your review > you can add the "shindig" group to send a notification of your review our > to this list. > > If you're just looking for some feedback on ideas that are easier to > express via a source code patch, you can skip right to the Review Board > site and create the JIRA at a later time. > > Thanks, > -Stanton > > [1] https://issues.apache.org/jira/browse/SHINDIG > [2] https://reviews.apache.org/ > > > > From: René Peinl <rene.pe...@hof-university.de <javascript:;>> > To: <dev@shindig.apache.org <javascript:;>>, > Cc: "Florian Holzschuher" <fholzschuh...@hof-university.de<javascript:;> > > > Date: 07/13/2012 01:46 > Subject: AW: Shindig neo4j backend > > > > Hi, > thanks for all the good suggestions. > One last question for the moment: how exactly do we contribute our code? > Should we open a Jira issue and attach the sources? > Maybe there are new suggestions, once you've seen our code. > Regards > René > > -----Ursprüngliche Nachricht----- > Von: Henry Saputra [mailto:henry.sapu...@gmail.com] > Gesendet: Freitag, 13. Juli 2012 07:17 > An: dev@shindig.apache.org > Betreff: Re: Shindig neo4j backend > > Hi, > > Thanks for the interest at Apache Shindig and Rave projects. > > Let me try to help answering some concerns and questions you have and > maybe other people in the community could chime in. > > Looks like Apache Rave provides model database abstraction that allow plug > and play to relational database. > > The Shindig's JPA implementation is just for sample/demo purpose. The only > implementation of the OpenSocial model is only POJO classes. > Backing the data storage with Neo4J sounds like awesome idea and I believe > should be more fitting for the social links for the OpenSocial data. > > As for activitystrea.ms implementation in Shindig, its fully implemented > based on the JSON 1.0 for JavaScript and Java components. > Shindig also support PHP for the server side but the implementation is far > behind the Java counterpart. > > For portal solution proposal, I would recommend using Rave as the front > end and management module and rebind the data model with Neo4J. > Contributing back to either Rave and Shindig is welcomed and encouraged =) > > Hope this helps. > > Looking forward for contributions and awesome project with you guys. > > - Henry > > On Thu, Jul 12, 2012 at 8:25 AM, René Peinl <rene.pe...@hof-university.de> > wrote: > > Dear Shindig developers, > > > > I’m working together with my colleague Florian on a systems > > integration research project that brings together a DMS, a groupware > > system, an ERP system in an Intranet scenario and adds social media > > capabilities under the hood of a central lightweight portal (see > > requirements overview at the end of the email). > > > > > > > > For the portal, we are planning to use Shindig as the central > > component and maybe Rave as a basis for the presentation layer. Since > > social media data is inherently graph-oriented, we are planning to use > > neo4j as the storage engine for Shindig (and maybe Rave as well). > > Florian has already implemented a draft of this neo4j storage layer > > which works well for some sample data that we have generated (if > > anyone is interested we can provide the sample data and the generator > > for it), but due to simplicity reasons and to avoid additional > > conversion operations in between the storage layer is currently not > > using JPA, but directly writing the objects to the database (replacing > e.g. both PersonImpl and PersonDB). > > > > > > > > Lately, we have discovered Rave and found out that despite its close > > integration with Shindig it uses its own database abstraction and > > partly competing implementations for classes that are already present in > Shindig. > > For example there is rave.portal.model.Person which uses JPA to store > > a (incomplete compared to OpenSocial 2.0 specs) person object in the > > database and there is shindig.social.opensocial.jpa.PersonDB which > > does the same, but seems like a complete implementation of the fields > > defined in OpenSocial 2.0. > > > > > > > > My goal is to better understand the decisions behind the current > > implementation of both Shindig and Rave (I’ve posted a similar > > question on the Rave mailing list) in order to find a solution for our > > project that lets the Apache community benefit as much as possible > > from our efforts, without burdening our project too much with > non-project-specific requirements. > > > > > > > > The options we have (from my perspective) are as follows > > > > 1) Kind of forking the Shindig project and using our own neo4j > backend > > and not using Rave > > > > 2) Going one step further and integrating Rave with our own neo4j > > Shindig backend and eliminate the duplicate classes > > > > 3) Trying to use SpringData JPA a
