You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Dan Peterson <dp...@google.com> on 2008/05/14 08:55:45 UTC
Proposed Apache Incubator board report for May 2008
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 <dp...@google.com>
Date: Tue, Apr 8, 2008 at 8:30 AM
Subject: Proposed Apache Incubator board report for April 2008
To: shindig-dev@incubator.apache.org
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 <dp...@google.com>
Date: Tue, Mar 11, 2008 at 12:16 AM
Subject: Proposed Apache Incubator board report for March 2008
To: shindig-dev@incubator.apache.org
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 <dp...@google.com>
Date: Fri, Feb 29, 2008 at 3:35 AM
Subject: State of the Shindig - February 2008
To: shindig-dev@incubator.apache.org
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!
Re: Proposed Apache Incubator board report for May 2008
Posted by Dan Peterson <dp...@google.com>.
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 <do...@apache.org> wrote:
> + community presence: ApacheCon
> lgtm
>
>
> On Wed, May 14, 2008 at 8:55 AM, Dan Peterson <dp...@google.com>
> 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 <dp...@google.com>
> > Date: Tue, Apr 8, 2008 at 8:30 AM
> > Subject: Proposed Apache Incubator board report for April 2008
> > To: shindig-dev@incubator.apache.org
> >
> > 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 <dp...@google.com>
> > Date: Tue, Mar 11, 2008 at 12:16 AM
> > Subject: Proposed Apache Incubator board report for March 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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 <dp...@google.com>
> > Date: Fri, Feb 29, 2008 at 3:35 AM
> > Subject: State of the Shindig - February 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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!
> >
>
Re: Proposed Apache Incubator board report for May 2008
Posted by Upayavira <uv...@odoko.co.uk>.
Incubating projects have been asked to add a section "what are the top
three things to resolve to move towards graduation". (this was asked
ages ago). Do you think you could add something of that kind?
Regards, Upayavira
On Wed, 2008-05-14 at 10:16 +0200, Cassie wrote:
> + community presence: ApacheCon
> lgtm
>
>
> On Wed, May 14, 2008 at 8:55 AM, Dan Peterson <dp...@google.com> 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 <dp...@google.com>
> > Date: Tue, Apr 8, 2008 at 8:30 AM
> > Subject: Proposed Apache Incubator board report for April 2008
> > To: shindig-dev@incubator.apache.org
> >
> > 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 <dp...@google.com>
> > Date: Tue, Mar 11, 2008 at 12:16 AM
> > Subject: Proposed Apache Incubator board report for March 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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 <dp...@google.com>
> > Date: Fri, Feb 29, 2008 at 3:35 AM
> > Subject: State of the Shindig - February 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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!
> >
Re: Proposed Apache Incubator board report for May 2008
Posted by Cassie <do...@apache.org>.
+ community presence: ApacheCon
lgtm
On Wed, May 14, 2008 at 8:55 AM, Dan Peterson <dp...@google.com> 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 <dp...@google.com>
> Date: Tue, Apr 8, 2008 at 8:30 AM
> Subject: Proposed Apache Incubator board report for April 2008
> To: shindig-dev@incubator.apache.org
>
> 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 <dp...@google.com>
> Date: Tue, Mar 11, 2008 at 12:16 AM
> Subject: Proposed Apache Incubator board report for March 2008
> To: shindig-dev@incubator.apache.org
>
>
> 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 <dp...@google.com>
> Date: Fri, Feb 29, 2008 at 3:35 AM
> Subject: State of the Shindig - February 2008
> To: shindig-dev@incubator.apache.org
>
>
> 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!
>
Re: Apache Incubator board report for May 2008
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Chris Chabot <ch...@xs4all.nl> writes:
>I've added our incubator board report too: http://wiki.apache.org/incubator/May2008
>ps Formally updating our incubator status page is still "in progress",
>since i don't have the slightest clue where that file would reside or
Well, I am not one of the mentors, but you can update your status by
changing your project status file at
https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/shindig.xml
This file gets transformed into
http://incubator.apache.org/projects/shindig.html, which is quite
outdated, so updates are probably needed.
>what the protocol for it is. I don't suppose one of our mentors could
>provide assistance with how and what to edit in it?
Tell me what you want to have in there, and I can commit it.
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
"...it's good to be a lunatic..." -- 10th doctor
Apache Incubator board report for May 2008
Posted by Chris Chabot <ch...@xs4all.nl>.
I've added our incubator board report too: http://wiki.apache.org/incubator/May2008
ps Formally updating our incubator status page is still "in progress",
since i don't have the slightest clue where that file would reside or
what the protocol for it is. I don't suppose one of our mentors could
provide assistance with how and what to edit in it?
-- Chris
Re: Proposed Apache Incubator board report for May 2008
Posted by Vincent Siveton <vs...@apache.org>.
2008/5/15, Vincent Siveton <vs...@apache.org>:
> Hi
>
> I guess it would be "complete the status file [1]" (and should be the
> first one IMHO)
BTW I guess that we also need to use and integrate existing ML, ie
shindig-commits@ and shindig-issues@
Cheers,
Vincent
> Cheers,
>
> Vincent
>
> [1] http://incubator.apache.org/projects/shindig.html
>
>
> 2008/5/15, Dan Peterson <dp...@google.com>:
>
> > Good suggestions everyone -- I actually see only 2 issues to resolve prior
> > to graduation.
> >
> > Is there a third that isn't coming to mind right now?
> >
> > Planning to submit the below in 2 hours:
> >
> >
> > 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
> >
> > - Aiming to get Infrastructure to provision a Zone (but progress is
> > slow): https://issues.apache.org/jira/browse/INFRA-1585
> >
> > - Retired 10 inactive committers (from Google)
> >
> > - Shindig docs are coming together:
> > http://chrisschalk.com/shindig_docs/shindig_sql_tutorial/shindig_data_tutorials.html
> >
> > - Technical progress:
> > - Initial work towards implementing OpenSocial v0.8
> > - Lots of progress getting new RESTful server implemented
> > - Implemented full OAuth support
> >
> > - Top 3 things to resolve prior to graduation:
> > - Improve diversity of committers (progress, but on-going)
> > - Run through at least one release (seems like 0.8-compliance is a
> > good time)
> > - <there seem to be only 2>
> >
> > Thanks,
> > -Dan
> >
> >
> > On Wed, May 14, 2008 at 3:45 AM, Vincent Siveton <vs...@apache.org>
> > wrote:
> >
> >
> > > Hi Dan,
> > >
> > > Since Shindig build was capricious this month, I think that board
> > > needs to be aware about INFRA-1585: we definitely need a CI and a zone
> > > will help us to test snapshots.
> > >
> > > Cheers,
> > >
> > > Vincent
> > >
> > > 2008/5/14, Dan Peterson <dp...@google.com>:
> > > > 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 <dp...@google.com>
> > > > Date: Tue, Apr 8, 2008 at 8:30 AM
> > > > Subject: Proposed Apache Incubator board report for April 2008
> > > > To: shindig-dev@incubator.apache.org
> > > >
> > > > 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 <dp...@google.com>
> > > > Date: Tue, Mar 11, 2008 at 12:16 AM
> > > > Subject: Proposed Apache Incubator board report for March 2008
> > > > To: shindig-dev@incubator.apache.org
> > > >
> > > >
> > > > 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 <dp...@google.com>
> > > > Date: Fri, Feb 29, 2008 at 3:35 AM
> > > > Subject: State of the Shindig - February 2008
> > > > To: shindig-dev@incubator.apache.org
> > > >
> > > >
> > > > 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!
> > > >
> > >
> >
>
Re: Proposed Apache Incubator board report for May 2008
Posted by Vincent Siveton <vs...@apache.org>.
Hi
I guess it would be "complete the status file [1]" (and should be the
first one IMHO)
Cheers,
Vincent
[1] http://incubator.apache.org/projects/shindig.html
2008/5/15, Dan Peterson <dp...@google.com>:
> Good suggestions everyone -- I actually see only 2 issues to resolve prior
> to graduation.
>
> Is there a third that isn't coming to mind right now?
>
> Planning to submit the below in 2 hours:
>
>
> 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
>
> - Aiming to get Infrastructure to provision a Zone (but progress is
> slow): https://issues.apache.org/jira/browse/INFRA-1585
>
> - Retired 10 inactive committers (from Google)
>
> - Shindig docs are coming together:
> http://chrisschalk.com/shindig_docs/shindig_sql_tutorial/shindig_data_tutorials.html
>
> - Technical progress:
> - Initial work towards implementing OpenSocial v0.8
> - Lots of progress getting new RESTful server implemented
> - Implemented full OAuth support
>
> - Top 3 things to resolve prior to graduation:
> - Improve diversity of committers (progress, but on-going)
> - Run through at least one release (seems like 0.8-compliance is a
> good time)
> - <there seem to be only 2>
>
> Thanks,
> -Dan
>
>
> On Wed, May 14, 2008 at 3:45 AM, Vincent Siveton <vs...@apache.org>
> wrote:
>
>
> > Hi Dan,
> >
> > Since Shindig build was capricious this month, I think that board
> > needs to be aware about INFRA-1585: we definitely need a CI and a zone
> > will help us to test snapshots.
> >
> > Cheers,
> >
> > Vincent
> >
> > 2008/5/14, Dan Peterson <dp...@google.com>:
> > > 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 <dp...@google.com>
> > > Date: Tue, Apr 8, 2008 at 8:30 AM
> > > Subject: Proposed Apache Incubator board report for April 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > > 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 <dp...@google.com>
> > > Date: Tue, Mar 11, 2008 at 12:16 AM
> > > Subject: Proposed Apache Incubator board report for March 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > >
> > > 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 <dp...@google.com>
> > > Date: Fri, Feb 29, 2008 at 3:35 AM
> > > Subject: State of the Shindig - February 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > >
> > > 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!
> > >
> >
>
Re: Proposed Apache Incubator board report for May 2008
Posted by Ropu <ro...@gmail.com>.
:D
Good point Cassie.
We are finishing all OAuth (0.7) impl today, i'll create a patch for that
and add it to a JIRA issue.
Ropu
On Mon, May 19, 2008 at 5:29 AM, Cassie <do...@apache.org> wrote:
> Ropu - You should really be creating jira issues with patches for
> these commits attached. If you don't post public patches then we will
> never see which code you are actually committing... which means we
> would never be able to vouch for you as a committer.
>
> It is great to know that you are contributing though. Thanks for the help!
>
> - Cassie
>
>
> On Fri, May 16, 2008 at 7:16 PM, Ropu <ro...@gmail.com> wrote:
> > Hi
> >
> > Im the Teach Lead managing all OpenSocial stuff in Globant, and as Chris
> > stated, we are, and will continue to collaborate with Shindig, PHP and
> Java.
> > Right now we canalize all of our commits though Chris, but we are ready
> to
> > become committers in the near future.
> >
> > We do have several big clients that are implementing Shindig PHP as well
> as
> > the JAVA version. (And i'll hope we'll start contributing JAVA soon too)
> >
> > So from Globant's side, Shindig has all our support.
> >
> > Regards
> >
> > Bruno Rovagnati (Ropu)
> >
> > www.globant.com
> >
> > On Fri, May 16, 2008 at 1:33 PM, Chris Chabot <ch...@xs4all.nl> wrote:
> >
> >> While having the PHP shindig server by it's self is already a good
> factor
> >> in this, in the PHP shindig implementation it's self I'm seeing more and
> >> more interest from other people and parties too, so even in this front
> the
> >> diversification is going well.
> >>
> >> There's explicit stated interest from about 4 large SNS's to use php
> >> shindig for their becoming an open social platform, most of which have
> >> expressed interest in contributing to shindig (some already are *waves
> to
> >> people from globant.com*).
> >>
> >> Plus there's currently 3 social network software writers who plan to
> >> release new versions of their products with shindig integrated this
> summer,
> >> some of which also expressed the desire to contribute.
> >>
> >> So there is already some actuated contributions happening and quite a
> few
> >> potentials in the future, so I'm hoping some of these will be become
> >> committers too :)
> >>
> >> All in all, i think we are gathering enough stakeholders on various
> fronts
> >> that the goal of guaranteeing the projects health in the future, even if
> one
> >> large party would pull out, is going well; So i share your opinion that
> the
> >> next ApacheCon could be a realistic goal
> >>
> >> -- Chris
> >>
> >>
> >> On May 16, 2008, at 3:53 PM, Santiago Gala wrote:
> >>
> >> I think that, with the alternate php server diversifying the code base
> >>> way beyond the original donation, the number of refactorings already
> >>> going on and the fact that there is people already in the committer
> pool
> >>> coming from different stakeholders, not to mention next committers to
> be
> >>> "invited", the project looks relatively mature for a quick graduation.
> >>> Next ApacheCON looks like a realistic horizon, IMO. What do you think?
> >>>
> >>
> >>
> >
> >
> > --
> > .-. --- .--. ..-
> > R o p u
> >
>
--
.-. --- .--. ..-
R o p u
Re: Proposed Apache Incubator board report for May 2008
Posted by Cassie <do...@apache.org>.
Ropu - You should really be creating jira issues with patches for
these commits attached. If you don't post public patches then we will
never see which code you are actually committing... which means we
would never be able to vouch for you as a committer.
It is great to know that you are contributing though. Thanks for the help!
- Cassie
On Fri, May 16, 2008 at 7:16 PM, Ropu <ro...@gmail.com> wrote:
> Hi
>
> Im the Teach Lead managing all OpenSocial stuff in Globant, and as Chris
> stated, we are, and will continue to collaborate with Shindig, PHP and Java.
> Right now we canalize all of our commits though Chris, but we are ready to
> become committers in the near future.
>
> We do have several big clients that are implementing Shindig PHP as well as
> the JAVA version. (And i'll hope we'll start contributing JAVA soon too)
>
> So from Globant's side, Shindig has all our support.
>
> Regards
>
> Bruno Rovagnati (Ropu)
>
> www.globant.com
>
> On Fri, May 16, 2008 at 1:33 PM, Chris Chabot <ch...@xs4all.nl> wrote:
>
>> While having the PHP shindig server by it's self is already a good factor
>> in this, in the PHP shindig implementation it's self I'm seeing more and
>> more interest from other people and parties too, so even in this front the
>> diversification is going well.
>>
>> There's explicit stated interest from about 4 large SNS's to use php
>> shindig for their becoming an open social platform, most of which have
>> expressed interest in contributing to shindig (some already are *waves to
>> people from globant.com*).
>>
>> Plus there's currently 3 social network software writers who plan to
>> release new versions of their products with shindig integrated this summer,
>> some of which also expressed the desire to contribute.
>>
>> So there is already some actuated contributions happening and quite a few
>> potentials in the future, so I'm hoping some of these will be become
>> committers too :)
>>
>> All in all, i think we are gathering enough stakeholders on various fronts
>> that the goal of guaranteeing the projects health in the future, even if one
>> large party would pull out, is going well; So i share your opinion that the
>> next ApacheCon could be a realistic goal
>>
>> -- Chris
>>
>>
>> On May 16, 2008, at 3:53 PM, Santiago Gala wrote:
>>
>> I think that, with the alternate php server diversifying the code base
>>> way beyond the original donation, the number of refactorings already
>>> going on and the fact that there is people already in the committer pool
>>> coming from different stakeholders, not to mention next committers to be
>>> "invited", the project looks relatively mature for a quick graduation.
>>> Next ApacheCON looks like a realistic horizon, IMO. What do you think?
>>>
>>
>>
>
>
> --
> .-. --- .--. ..-
> R o p u
>
Re: Proposed Apache Incubator board report for May 2008
Posted by Ropu <ro...@gmail.com>.
Hi
Im the Teach Lead managing all OpenSocial stuff in Globant, and as Chris
stated, we are, and will continue to collaborate with Shindig, PHP and Java.
Right now we canalize all of our commits though Chris, but we are ready to
become committers in the near future.
We do have several big clients that are implementing Shindig PHP as well as
the JAVA version. (And i'll hope we'll start contributing JAVA soon too)
So from Globant's side, Shindig has all our support.
Regards
Bruno Rovagnati (Ropu)
www.globant.com
On Fri, May 16, 2008 at 1:33 PM, Chris Chabot <ch...@xs4all.nl> wrote:
> While having the PHP shindig server by it's self is already a good factor
> in this, in the PHP shindig implementation it's self I'm seeing more and
> more interest from other people and parties too, so even in this front the
> diversification is going well.
>
> There's explicit stated interest from about 4 large SNS's to use php
> shindig for their becoming an open social platform, most of which have
> expressed interest in contributing to shindig (some already are *waves to
> people from globant.com*).
>
> Plus there's currently 3 social network software writers who plan to
> release new versions of their products with shindig integrated this summer,
> some of which also expressed the desire to contribute.
>
> So there is already some actuated contributions happening and quite a few
> potentials in the future, so I'm hoping some of these will be become
> committers too :)
>
> All in all, i think we are gathering enough stakeholders on various fronts
> that the goal of guaranteeing the projects health in the future, even if one
> large party would pull out, is going well; So i share your opinion that the
> next ApacheCon could be a realistic goal
>
> -- Chris
>
>
> On May 16, 2008, at 3:53 PM, Santiago Gala wrote:
>
> I think that, with the alternate php server diversifying the code base
>> way beyond the original donation, the number of refactorings already
>> going on and the fact that there is people already in the committer pool
>> coming from different stakeholders, not to mention next committers to be
>> "invited", the project looks relatively mature for a quick graduation.
>> Next ApacheCON looks like a realistic horizon, IMO. What do you think?
>>
>
>
--
.-. --- .--. ..-
R o p u
Re: Proposed Apache Incubator board report for May 2008
Posted by Chris Chabot <ch...@xs4all.nl>.
While having the PHP shindig server by it's self is already a good
factor in this, in the PHP shindig implementation it's self I'm seeing
more and more interest from other people and parties too, so even in
this front the diversification is going well.
There's explicit stated interest from about 4 large SNS's to use php
shindig for their becoming an open social platform, most of which have
expressed interest in contributing to shindig (some already are *waves
to people from globant.com*).
Plus there's currently 3 social network software writers who plan to
release new versions of their products with shindig integrated this
summer, some of which also expressed the desire to contribute.
So there is already some actuated contributions happening and quite a
few potentials in the future, so I'm hoping some of these will be
become committers too :)
All in all, i think we are gathering enough stakeholders on various
fronts that the goal of guaranteeing the projects health in the
future, even if one large party would pull out, is going well; So i
share your opinion that the next ApacheCon could be a realistic goal
-- Chris
On May 16, 2008, at 3:53 PM, Santiago Gala wrote:
> I think that, with the alternate php server diversifying the code base
> way beyond the original donation, the number of refactorings already
> going on and the fact that there is people already in the committer
> pool
> coming from different stakeholders, not to mention next committers
> to be
> "invited", the project looks relatively mature for a quick graduation.
> Next ApacheCON looks like a realistic horizon, IMO. What do you think?
Re: Proposed Apache Incubator board report for May 2008
Posted by Santiago Gala <sa...@gmail.com>.
El jue, 15-05-2008 a las 14:58 -0700, Dan Peterson escribió:
> Good suggestions everyone -- I actually see only 2 issues to resolve prior
> to graduation.
>
> Is there a third that isn't coming to mind right now?
>
I think that, with the alternate php server diversifying the code base
way beyond the original donation, the number of refactorings already
going on and the fact that there is people already in the committer pool
coming from different stakeholders, not to mention next committers to be
"invited", the project looks relatively mature for a quick graduation.
Next ApacheCON looks like a realistic horizon, IMO. What do you think?
> Planning to submit the below in 2 hours:
+1 from me, looks good.
>
> 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
> - Aiming to get Infrastructure to provision a Zone (but progress is
> slow): https://issues.apache.org/jira/browse/INFRA-1585
> - Retired 10 inactive committers (from Google)
> - Shindig docs are coming together:
> http://chrisschalk.com/shindig_docs/shindig_sql_tutorial/shindig_data_tutorials.html
> - Technical progress:
> - Initial work towards implementing OpenSocial v0.8
> - Lots of progress getting new RESTful server implemented
> - Implemented full OAuth support
> - Top 3 things to resolve prior to graduation:
> - Improve diversity of committers (progress, but on-going)
> - Run through at least one release (seems like 0.8-compliance is a
> good time)
> - <there seem to be only 2>
>
> Thanks,
> -Dan
>
>
> On Wed, May 14, 2008 at 3:45 AM, Vincent Siveton <vs...@apache.org>
> wrote:
>
> > Hi Dan,
> >
> > Since Shindig build was capricious this month, I think that board
> > needs to be aware about INFRA-1585: we definitely need a CI and a zone
> > will help us to test snapshots.
> >
> > Cheers,
> >
> > Vincent
> >
> > 2008/5/14, Dan Peterson <dp...@google.com>:
> > > 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 <dp...@google.com>
> > > Date: Tue, Apr 8, 2008 at 8:30 AM
> > > Subject: Proposed Apache Incubator board report for April 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > > 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 <dp...@google.com>
> > > Date: Tue, Mar 11, 2008 at 12:16 AM
> > > Subject: Proposed Apache Incubator board report for March 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > >
> > > 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 <dp...@google.com>
> > > Date: Fri, Feb 29, 2008 at 3:35 AM
> > > Subject: State of the Shindig - February 2008
> > > To: shindig-dev@incubator.apache.org
> > >
> > >
> > > 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!
> > >
> >
--
Santiago Gala
http://memojo.com/~sgala/blog/
Re: Proposed Apache Incubator board report for May 2008
Posted by Dan Peterson <dp...@google.com>.
Good suggestions everyone -- I actually see only 2 issues to resolve prior
to graduation.
Is there a third that isn't coming to mind right now?
Planning to submit the below in 2 hours:
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
- Aiming to get Infrastructure to provision a Zone (but progress is
slow): https://issues.apache.org/jira/browse/INFRA-1585
- Retired 10 inactive committers (from Google)
- Shindig docs are coming together:
http://chrisschalk.com/shindig_docs/shindig_sql_tutorial/shindig_data_tutorials.html
- Technical progress:
- Initial work towards implementing OpenSocial v0.8
- Lots of progress getting new RESTful server implemented
- Implemented full OAuth support
- Top 3 things to resolve prior to graduation:
- Improve diversity of committers (progress, but on-going)
- Run through at least one release (seems like 0.8-compliance is a
good time)
- <there seem to be only 2>
Thanks,
-Dan
On Wed, May 14, 2008 at 3:45 AM, Vincent Siveton <vs...@apache.org>
wrote:
> Hi Dan,
>
> Since Shindig build was capricious this month, I think that board
> needs to be aware about INFRA-1585: we definitely need a CI and a zone
> will help us to test snapshots.
>
> Cheers,
>
> Vincent
>
> 2008/5/14, Dan Peterson <dp...@google.com>:
> > 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 <dp...@google.com>
> > Date: Tue, Apr 8, 2008 at 8:30 AM
> > Subject: Proposed Apache Incubator board report for April 2008
> > To: shindig-dev@incubator.apache.org
> >
> > 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 <dp...@google.com>
> > Date: Tue, Mar 11, 2008 at 12:16 AM
> > Subject: Proposed Apache Incubator board report for March 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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 <dp...@google.com>
> > Date: Fri, Feb 29, 2008 at 3:35 AM
> > Subject: State of the Shindig - February 2008
> > To: shindig-dev@incubator.apache.org
> >
> >
> > 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!
> >
>
Re: Proposed Apache Incubator board report for May 2008
Posted by Vincent Siveton <vs...@apache.org>.
Hi Dan,
Since Shindig build was capricious this month, I think that board
needs to be aware about INFRA-1585: we definitely need a CI and a zone
will help us to test snapshots.
Cheers,
Vincent
2008/5/14, Dan Peterson <dp...@google.com>:
> 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 <dp...@google.com>
> Date: Tue, Apr 8, 2008 at 8:30 AM
> Subject: Proposed Apache Incubator board report for April 2008
> To: shindig-dev@incubator.apache.org
>
> 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 <dp...@google.com>
> Date: Tue, Mar 11, 2008 at 12:16 AM
> Subject: Proposed Apache Incubator board report for March 2008
> To: shindig-dev@incubator.apache.org
>
>
> 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 <dp...@google.com>
> Date: Fri, Feb 29, 2008 at 3:35 AM
> Subject: State of the Shindig - February 2008
> To: shindig-dev@incubator.apache.org
>
>
> 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!
>