We do use both versions internally and the PHP one is still valuable for fast prototyping & integration with existing CMS. We had to do some work to get it working with the AS data model but I believe if there is enough bandwidth to continue this track it could be valuable in order to widespread the use of OS APIs into existing PHP-based CMS.
walter -----Messaggio originale----- Da: Agustin Casiva [mailto:casivaagus...@gmail.com] Inviato: mercoledì 7 marzo 2012 18.49 A: dev@shindig.apache.org Oggetto: Re: [DISCUSS] Support and active development for PHP version of Apache Shindig From my point of View, as a PHP developer, Shinding for PHP is a great alternative, but some clients ask for features existent in the Java version and have the hope use those features in the PHP Version (by example Caja). This is a real problem for the PHP shinding vendors. In the other hand, the gap between Shindig for PHP and Shindig for Java is huge. I think, if the PHP version will continue alive, the dev team for PHP must grow. I can see that only Bastian is working with the PHP version in the last time (maybe I'm wrong); could be great if some others PHP developers joins as active developers. If no one is thinking in maintain the PHP version maybe the best option is abandon the work of PHP and leave the current work in PHP to be continued outside of the Shindig Project with other team (as a Fork). My two cents. On Thu, Mar 1, 2012 at 8:33 PM, Ryan J Baxter <rjbax...@us.ibm.com> wrote: > Henry, from an IBM point of view we are focused on the Java version, we do > not use the PHP version....and I don't see that changing any time soon. > > -Ryan > > > > > From: Henry Saputra <henry.sapu...@gmail.com> > To: dev@shindig.apache.org, us...@shindig.apache.org, > Date: 03/01/2012 02:38 PM > Subject: [DISCUSS] Support and active development for PHP version > of Apache Shindig > > > > Hi Shindig community, > > Currently the Apache Shindig project supports both Java and PHP code > for the server side execution. > However, recent development in PHP have been very limited and in > effort to catch up and getting closer to the OpenSocial specifications > the PHP part have lot of catching up to do. > > On the other hand the Java development efforts have been very active > and closer to OpenSocial specs. > > So, I would like to bring out this discussion to get some feedback > about what is the future of the PHP side of Shindig. Most active > contributors in Java side dont have enough bandwidth to make the > duplicate updates in both PHP and Java parts of the server side code. > > I would like to send a VOTE thread later but would like to get inputs > about how to energize or deal with the PHP part of Apache Shindig. > > As community I think we want Shindig to be the reference > implementation of OpenSocial to help new adopters to embrace and > support the specs, and to do this I think we need to refocus and > regroup the effort to bring back the healthy and active contributions > from community. > So far the PHP side has been lacking development of the new features > and bug fixes that the Java counterpart has enjoyed. This cause a lot > of confusions about how big the difference between the Java and PHP > implementations which ideally should be equal. > > This is also a shout out to many active committers and PMC of Shindig > that still want and have bandwidth to keep contributing to Shindig > development. > > Chime in and let your voice be heard! > > - Henry > > > -- Ing. Casiva Agustin Mail/Msn/GTalk/Jabber: casivaagus...@gmail.com Skype: casivaagustin CEL : 054-03722-15270639 Site: http://www.casivaagustin.com.ar Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
