On this topic, the "testing" guideline could include some instruction to disable testing if wanted. In fact this breaking of compatibility during the last two weeks has followed a smooth evolution: first the test became broken, then we (our group) survived by deleting the test/ directory, and then this week the first Java 6 specific has been introduced, forcing us to migrate. Not a headache, except that Java6 is not a SUSE 10.2 standard package yet, only "in testing".
I'd be happy following java 6. > > work on Shindig as an observer and have/will submit patches to the project > > (at least until you guys get fed up with me). I have worked on a number > > of > > open source projects (Moz and a few of my own) and currently represent > > Piczo > > (www.piczo.com), a social networking company (what else?). We intend to > > use > > Shindig for our OpenSocial implementation and we are close to hosting an > > internal implementation of Shindig for experimental purposes. We are It seems that this accident has forced some of us to surface. So hat tip to the community :-) On my side, our group is finishing a development for a BOINC based platform are planning to keep the shinding java for the gadgets, but opensocial request will need some rerouting, most probably to python. Launching date is 24 April. Simultaneusly we will deploy some gadgets, mostly videocomm. Cheers, Alejandro
