Hi Ralf, there's no need to rush. I for myself just spent three days in the mountains skiing .... so let's talk once we are all back.
Cheers Werner [email protected] wrote: > Hi Werner, > > I'll have to review proposals in deatil which I will do once I'm back from > holiday on Thuesday evening. WIll share my opinion thereafter. > > Regards > Ralf > > > Hi everybody, > > it looks like we are having quite some GSoC 2009 applications this year. > We still got two weeks to have students refine their proposals and work > with us (committers, would be mentors) to show us that they can really > make a contribution. As such, I am very positive that we will be > allocated a few slots with GSoC 2009 and will be able to mentor some > really good projects. > > Having said that, given the sheer number of applications (~10), I think > we should allow us to focus as well. Given that we won't be getting all > slots at The Codehaus, I guess we need to define priorities amongst > ourselves and sketch out what matters most to us. This could relate to > many things, including technologies, problem areas and/or JSR > specifications. > > As such, let me try to state my preferences: on the JDO side of things, > given the amount of work that has already gone into (partial) JPA > annotation support, any contribution to implememt selected JPA features > is worth it. I am not saying that e.g. SQL query refactoring or > inheritance is a bad contribution, but for me JPA matters more. > > On the XML side of things, given that there's two proposals only (for > one idea, that is), things are easy. And yes, support for STaX parsers > in addition to SAX matters to me as well. > > Not sure how I would prioritize between JPA and XML ... but maybe the > following statement makes my thinking a bit clearer. Castor JDO has to > move a lot to be noticed again in the public. And (partial) JPA > compliance is about the only way this could (sic!) be achieved. There's > only one other thing that makes it attractive to some users currently: > is getting easier and easier to persist to a database using Castor (JDO) > when starting from XML schemas (given the new JDO extensions for the XML > code generator). > > Castor XML is a very alive framework, widely used .. and as far as I can > tell, there seems to be an increasing number of people looking into > Castor (again and/or instead of JAXB). As such, a proposal that makes > that offering even more attractive is a good one .. ;-). > > Enough said .... opinions welcome. > > Cheers > Werner > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
