Hi Chris, as we discussed offline, I'm happy to dive in on the OAuth and RESTful updates to php-shindig. This is my first time working on shindig code, so it may take me a bit of time to get the lay of the land, but as one of the main instigators of the changes we now have to make, I think I'm knowledgable and motivated enough about getting these changes made that I should be able to make a difference here. :)
Thanks! js PS: How should I coordinate these changes with the corresponding Java changes? My naive assumption would be: 1) focus first on just updating php-shindig; 2) find the right Java people and show them what changes I made, and 3) help out on the Java side to the extent that's helpful. But I'm happy to pursue a different strategy if anyone has any feedback! On Tue, Aug 26, 2008 at 8:16 AM, Chris Chabot <[EMAIL PROTECTED]> wrote: > Hey Kevin, > > I'll need a bit more time before I can give you a solid schedule > indication, I'm a bit tight for development time right now with only one > week available for development in september, and there's a few largish items > still on the todo list for PHP Shindig (I'll go file issues @ jira right > after this mail btw), namely OAuth support for the RESTful interface, > PortableContacts alignment work, json-rpc support.. and 18 points that still > fail in the reference test gadget and some a bit of code cleanups and > refactoring to really make it release ready.. In other word's I'll never be > able to fit that in a week I'm afraid ;/ > > I'm trying to see who's got time to help out where, but if anyone is able > to contribute to that todo list, that would be incredibly helpful for > speeding up the getting release ready on the PHP side of things! See the > Jira issues i'll file in the next 30 minutes. > > I'll have a better insight on what will be possible to achieve by the end > of the week once everyone gets back to me I hope. > > Worst case we could de-couple the release schedules, but if we can get the > 2 versions ready at approximately the same time (say, give or take a few > weeks) that would have my strong preference of course. > > -- Chris > > > > On Aug 26, 2008, at 12:20 PM, Kevin Brown wrote: > > Hi everyone, >> >> We've been saying for a while that 0.8 completion was a prerequisite for >> our >> first release. As we approach this milestone, it's time to really get >> serious about it. >> >> To make this happen, we're going to need to do the following: >> >> 1. Lock down all public interfaces and signatures. This is critical if we >> want to be able to offer any compatibility guarantees. >> >> 2. Get rid of rough edges. Now is the time to resolve any outstanding >> integration issues. >> >> 3. Lock down a target release date. September 30th gets my vote, but I'm >> willing to hear arguments otherwise. >> >> We can lock down the release into distinct components, as long as >> compatibility guarantees are met, but we should strive to release >> everything >> at around the same time so as to avoid developer confusion. >> >> There are 5 major components that need to be released: >> >> - javascript (all together, due to interdependencies) >> - Java/PHP social data component >> - Java/PHP gadget rendering component >> >> I'm not that concerned about the java web app artifact, but that wouldn't >> hurt either. >> > >
