Re: Shindig 1.0 release timeline.

[Chris Chabot]

Hey Joseph,

Welcome to the list & project, great to have you here and I'm sure  
your assistance will be invaluable!

In general the shindig-dev list is the best place to coordinate, I  
think all main developers (both on the php and java sides) read pretty  
much every email on the list, and if not they know who to poke to make  
them pay attention; You'll find out quickly we're a pretty friendly  
and willing-to-help bunch here on the list :)

The person working on the javascript adjustments for the PC alignment  
is Cassie Doll, it would be good to coordinate the field name changes  
with her where required, but I actually think most of the field  
changes don't affect most of the gadget calls (who mostly use the id,  
thumbnail & profile url and name fields), so as long as both versions  
of Shindig end up having the same field names & structure in the end,  
it shouldn't be to much of a hassle.

For the OAuth side, it would be good to take a quick look at the  
proposed Java issue in our bug tracking system for the Java side of  
things, it includes some code and design discussion that would make a  
good place to start out: https://issues.apache.org/jira/browse/SHINDIG-290 
 , Dirk Balfanz is the one who contributed the patch for the Java  
version, and also Brian Eaton is frequently involved with OAuth (&  
general security stuff) for the java version, so also a great guy to  
check with when required.

As far as the strategy goes, that sounds pretty much perfect, the end  
goal is of course that both sides end up functioning the same (from an  
end user / gadget dev / javascript library perspective), so as long as  
that goal can be met it's all good. Implementation details can vary  
between different languages, so don't feel like you have to follow the  
implementation structure, as long as the end result is 'compatible',  
which is (read: should be) easy since we both implement the same spec :)

        -- Chris

On Aug 29, 2008, at 1:00 AM, Joseph Smarr wrote:

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.