ApacheCon was included in April, so I didn't think we should double-dip...

-Dan

On Wed, May 14, 2008 at 1:16 AM, Cassie <[EMAIL PROTECTED]> wrote:

> + community presence: ApacheCon
> lgtm
>
>
> On Wed, May 14, 2008 at 8:55 AM, Dan Peterson <[EMAIL PROTECTED]>
> wrote:
> > Hey folks,
> >
> > It's that time again -- our third board report is due Wednesday (May 14!)
> --
> > sorry for the short notice on this note, things have been busy. I need to
> > submit this to http://wiki.apache.org/incubator/May2008 in less than 24
> > hours.
> >
> > I'd propose the following:
> > Shindig is a reference implementation of the OpenSocial and gadgets
> stack.
> >
> > Incubating since: 2007-12-06
> >
> > High-level status summary: Shindig community growing and working on
> > OpenSocial v0.8 implementation.
> >
> >   - Community presence/growth: JavaOne, OpenSocial Summit, Google I/O
> >   - Retired 10 inactive committers (from Google)
> >   - Technical progress:
> >      - Initial work towards implementing OpenSocial v0.8
> >      - Lots of progress getting new RESTful server implemented
> >      - Implemented full OAuth support
> >
> > Comments? Additions?
> >
> > For ease of reference, I've included our last two board reports below.
> >
> > Thanks,
> > -Dan
> >
> > ---------- Forwarded message ----------
> > From: Dan Peterson <[EMAIL PROTECTED]>
> > Date: Tue, Apr 8, 2008 at 8:30 AM
> > Subject: Proposed Apache Incubator board report for April 2008
> > To: [email protected]
> >
> > Hi everyone,
> >
> > As far as I'm aware, the incubator board report is due this Wednesday.
> This
> > is now our second report.
> >
> > Here's what I'd propose:
> >
> > Shindig is a reference implementation of the OpenSocial and gadgets
> stack.
> >
> > Incubating since: 2007-12-06
> >
> > High-level status summary: Shindig making rapid progress since inception
> in
> > December 2007.
> >
> >   - Introduced a new committer, primarily focused on PHP server
> >   - Participating in Summer of Code to help build the community
> >   - Giving Fast Feather talk and hosting Shindig BoF at ApacheCon EU
> >   - Technical progress:
> >      - Initial infrastructure for OAuth and signing keys, and completed
> >      crpyto compliance
> >      - Discussions around RESTful implementation design
> >      - Refactoring to introduce a proper sample container, especially for
> >      OpenSocial data
> >
> > Comments?
> >
> > For reference, I've included the March report below.
> >
> > Cheers,
> > -Dan
> >
> > ---------- Forwarded message ----------
> > From: Dan Peterson <[EMAIL PROTECTED]>
> > Date: Tue, Mar 11, 2008 at 12:16 AM
> > Subject: Proposed Apache Incubator board report for March 2008
> > To: [email protected]
> >
> >
> > Hey folks,
> >
> > The incubator board report is due this Wednesday. This will be our first
> > report.
> >
> > Here is what I'd propose we send in (for reference, below you'll find a
> more
> > detailed report from a few weeks ago), but I'd love feedback, edits,
> > additions:
> >
> > Shindig is a reference implementation of the OpenSocial and gadgets
> stack.
> >
> > Incubating since: 2007-12-06
> > (Note this report covers since inception, as we've not yet submitted any
> > other reports, and will submit for the next 3 months to compensate)
> >
> > High-level status summary: Shindig making rapid progress since inception
> in
> > December 2007.
> >
> >   - Accepted a couple rounds of "bootstrapping" Java and JS code
> >   contributions from Google (with appropriate IP licensing)
> >   - Large patch written by a community member for PHP port committed
> >   - Healthy community growing, though committers still Google-heavy
> >   - JIRA queue moving in full force
> >   - Initial website created: http://incubator.apache.org/shindig/
> >
> > <http://wiki.apache.org/incubator/February2008>Comments?
> >
> > Cheers,
> > -Dan
> >
> > P.S. For reference, here is the wiki page for February 2008:
> > http://wiki.apache.org/incubator/February2008
> >
> > ---------- Forwarded message ----------
> > From: Dan Peterson <[EMAIL PROTECTED]>
> > Date: Fri, Feb 29, 2008 at 3:35 AM
> > Subject: State of the Shindig - February 2008
> > To: [email protected]
> >
> >
> > Hi all,
> >
> > The note regarding the Apache Board Reports got me thinking that it would
> be
> > an ideal time to touch on the status of Shindig. Since this is
> essentially
> > the first thread of this form since inception, I'll include some
> > pre-Febraury details as well, for historical sake. Please note that this
> is
> > generally longer than the February status reports I saw, but I felt it
> would
> > be better to over communicate given that we're a bit late to the game
> with
> > these reports. Please do correct anything I may have stated inaccurately.
> >
> > High-level summary: Shindig's Java implementation making rapid progress
> > since inception in December 2007.
> >
> >   - All committers have Apache accounts and access to the repository
> >   - Accepted a couple rounds of "bootstrapping" Java and JS code
> >   contributions from Google (with appropriate IP licensing)
> >   - Generally-functional out of the box experience
> >   - Good progress on (optional) Caja integration for improved security
> >   - Preliminary website created: http://incubator.apache.org/shindig/
> >   - Healthy community growing, though committers still Google-heavy
> >   - JIRA queue moving in full force
> >   - Majority of progress on the Java server port
> >   - Emerging PHP port, which many people are excited about
> >
> >
> > Now, to jump into some more particular areas...
> >
> > OpenSocial and Gadgets specification compliance (referring to the Java
> > implementation):
> >
> > For Gadgets, the compliance with the XML spec is very far along, though
> > Shindig doesn't yet support icons or preloads, and doesn't correctly
> handle
> > all message bundle substitutions. In terms of the core gadgets JavaScript
> > API, it is also quite far along, though gadgets.util.getFeature is
> broken.
> > For the "highly-recommended features," all, with the exception of
> skins.js,
> > are implemented in Shindig.
> >
> > For OpenSocial compliance, Shindig is not as far along. The initial
> sample
> > container was a very basic non-standard implementation for quick testing
> > purposes. However, the sample container is now in the middle of being
> > modified to use OpenSocial properly. This means that it is being
> refactored
> > to speak via very recently created interfaces, to get data stored in a
> > flatfile as a mock implementation that can easily be swapped out in
> > favor ofmore sophisticated versions, depending upon deployment needs.
> > In addition,
> > there is discussion about some initial infrastructure work for the
> Gateway
> > server component, though the OpenSocial RESTful API is under discussion
> over
> > on the spec discussion forum.
> >
> > Usage status:
> >
> > To facilitate early access for developers, orkut and hi5 are running
> > Shindig-based
> > sandbox instances (of the Java server port), and plan to use Shindig for
> > upcoming production user-facing launches as well. Ning is similarly
> running
> > an early instance based on the PHP port. Due to the activity on
> shindig-dev,
> > it is very likely there are others in similar positions, so please feel
> free
> > to chime in.
> >
> > What is coming in the near-term (the next several weeks)?
> >
> >   - Improved support for OpenSocial 0.7, via a well-defined interface and
> a
> >   flatfile-backed method for supporting people, activities, and
> persistence
> >   (as mentioned above)
> >   - Rounding out compliance with the Gadgets spec
> >   - Initial, but *large* "update" patch to the PHP server port
> >   - Initial infrastructure work for supporting the OpenSocial RESTful API
> >   - Performance improvements to the GadgetServer
> >
> > What else is going on? Please speak up if you're working on things that
> > weren't touched on, or if I didn't accurately describe the state
> > ofsomething that was touched on.
> >
> > Cheers,
> > -Dan
> >
> > P.S. If you're looking to get involved, I'd suggest browsing through
> JIRA,
> > and finding an issue that you'd like to take -- please speak up on
> shindig-dev
> > when you do so, to avoid duplicate effort. Details documented here:
> > http://incubator.apache.org/shindig/#tab-support &
> > http://incubator.apache.org/shindig/#tab-contribute -- Other questions?
> Just
> > Ask!
> >
>

Reply via email to