Re: Welcome to OpenDashboards!

[Chris Spiliotopoulos]

Hi Rene,

thank you very much for the contribution!  A great first step forward.  Can
you send me you Github account so I can send you an invitation to join
OpenDashboards?  I will also create a new OpenDashboards org @ Docker Hub
so we could start gathering the new containers in one place.

Since you have done a lot of work on the social side of things, I think it
would be great if we had your open source projects under the new
OpenDashboards org as plug-n-play components that anyone could use.  To be
honest, I'd really like to plug your social API module to our dashboard and
see where this would take our product. :)

Please feel free to share your thoughts.  I'll also send you an invitation
for our Slack team where we can a more dynamic conversation on all these
topics.

Best regards,
Chris

On Wed, Nov 25, 2015 at 11:51 AM, René Peinl <rene.pe...@hof-university.de>
wrote:

> Hi *,
> since some of you requested a version of Shindig that is just working out
> of the box with no lengthy installation and configuration, we've finally
> published our Docker image of Shindig 2.5.2 running on Apache Tomcat 7 with
> Open JDK 7 and our integration code to use neo4j (1.98) as a storage
> backend.
> This version has some additional enhancements compared to the original
> version like friend suggestions based on existing friends and their
> connections as well as queries to determine the connections between two
> people.
> It can be downloaded from Docker Hub
> https://hub.docker.com/r/rpeinl/shindig-ws-neo4j/
> I hope that helps some of you to get up to speed.
> Feedback welcome.
> Regards
> René
>
>
> -Ursprüngliche Nachricht-
> Von: Chris Spiliotopoulos [mailto:chrysanthos.spiliotopou...@gmail.com]
> Gesendet: Montag, 23. November 2015 11:54
> An: dev@shindig.apache.org
> Betreff: Welcome to OpenDashboards!
>
> Hi friends,
>
> after gathering all your wishes, proposals and votes on the recently
> created Trello <https://trello.com/b/hUTQuH6q/codename-apache-shindig-2015
> >
> board toady a new open source organization over at GitHub under the name
> of OpenDashboards <https://github.com/orgs/OpenDashboards> has been
> created that will be used as our common placeholder for all the things we
> want to see happening from now on.
>
> In order to send out invitations to anyone that wishes to join this new
> effort, please make sure you have a GitHub account and post it back to me
> either as a reply to this email or directly through our new Slack <
> https://opendashboards.slack.com> space (channel *github-org*).  For
> those who still haven't signed up with the OpenDashboards Slack team,
> please send me your email as well and I will send you an invitation.
>
> Please keep in mind that although this new effort has started off as a
> shelter for the Apache Shindig project can clearly  have a bright future,
> since 'dashboarding' is and will be a common requirement for many
> companies, organizations and individual technology solutions.  Having
> stated that, I have a vision that OpenDashboards can easily become the next
> one-stop shop for diverse dashboarding solutions given the appropriate
> context and positioning in the technology space.
>
> I believe that we should all urge the companies we represent to join the
> effort and contribute to the evolution of an ecosystem we all could benefit
> from.  Also, we could start building collaborations with other open source
> projects and solutions in the same space, or even with various verticals in
> order to start getting attention and traction.
>
> Now that we have a new home, the next step is to transfer the Apache
> Shindig project to a new repository @ Github at its latest stable version.
> So, @Ryan can you give us the status from your side (and Apache's of
> course)?  Have you cleared things up regarding the transfer?
>
> Best regards,
> Chris
>
>
>
>
> --
> Chris Spiliotopoulos
>
> Solutions Architect | @LinkedIn
> <https://www.linkedin.com/pub/chris-spiliotopoulos>| @Twitter <
> https://twitter.com/chefArchitect>
>
>


-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
<https://www.linkedin.com/pub/chris-spiliotopoulos>| @Twitter
<https://twitter.com/chefArchitect>

Re: Welcome to OpenDashboards!

[Chris Spiliotopoulos]

Hi Rene,

just sent you the invitations.  No problem with that.  In the context of
gathering existing resources from the community it would be great if we
just got some links to what's already available as an open source project
(Github, etc).  This way, when we have enough resources to create web site
for OpenDashboards users can find their way around stuff.

Best regards,
Chris



On Wednesday, November 25, 2015, René Peinl <rene.pe...@hof-university.de>
wrote:

> Hi Chris,
> my Github account is rpeinl.
> I have no problems of sharing the components. I don't think it makes sense
> to copy them, however, so why not just link to Github?
> Regards
> René
>
> -Ursprüngliche Nachricht-----
> Von: Chris Spiliotopoulos [mailto:chrysanthos.spiliotopou...@gmail.com
> <javascript:;>]
> Gesendet: Mittwoch, 25. November 2015 12:16
> An: dev@shindig.apache.org <javascript:;>
> Betreff: Re: Welcome to OpenDashboards!
>
> Hi Rene,
>
> thank you very much for the contribution!  A great first step forward.
> Can you send me you Github account so I can send you an invitation to join
> OpenDashboards?  I will also create a new OpenDashboards org @ Docker Hub
> so we could start gathering the new containers in one place.
>
> Since you have done a lot of work on the social side of things, I think it
> would be great if we had your open source projects under the new
> OpenDashboards org as plug-n-play components that anyone could use.  To be
> honest, I'd really like to plug your social API module to our dashboard and
> see where this would take our product. :)
>
> Please feel free to share your thoughts.  I'll also send you an invitation
> for our Slack team where we can a more dynamic conversation on all these
> topics.
>
> Best regards,
> Chris
>
> On Wed, Nov 25, 2015 at 11:51 AM, René Peinl <rene.pe...@hof-university.de
> <javascript:;>>
> wrote:
>
> > Hi *,
> > since some of you requested a version of Shindig that is just working
> > out of the box with no lengthy installation and configuration, we've
> > finally published our Docker image of Shindig 2.5.2 running on Apache
> > Tomcat 7 with Open JDK 7 and our integration code to use neo4j (1.98)
> > as a storage backend.
> > This version has some additional enhancements compared to the original
> > version like friend suggestions based on existing friends and their
> > connections as well as queries to determine the connections between
> > two people.
> > It can be downloaded from Docker Hub
> > https://hub.docker.com/r/rpeinl/shindig-ws-neo4j/
> > I hope that helps some of you to get up to speed.
> > Feedback welcome.
> > Regards
> > René
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Chris Spiliotopoulos
> > [mailto:chrysanthos.spiliotopou...@gmail.com <javascript:;>]
> > Gesendet: Montag, 23. November 2015 11:54
> > An: dev@shindig.apache.org <javascript:;>
> > Betreff: Welcome to OpenDashboards!
> >
> > Hi friends,
> >
> > after gathering all your wishes, proposals and votes on the recently
> > created Trello
> > <https://trello.com/b/hUTQuH6q/codename-apache-shindig-2015
> > >
> > board toady a new open source organization over at GitHub under the
> > name of OpenDashboards <https://github.com/orgs/OpenDashboards> has
> > been created that will be used as our common placeholder for all the
> > things we want to see happening from now on.
> >
> > In order to send out invitations to anyone that wishes to join this
> > new effort, please make sure you have a GitHub account and post it
> > back to me either as a reply to this email or directly through our new
> > Slack < https://opendashboards.slack.com> space (channel
> > *github-org*).  For those who still haven't signed up with the
> > OpenDashboards Slack team, please send me your email as well and I will
> send you an invitation.
> >
> > Please keep in mind that although this new effort has started off as a
> > shelter for the Apache Shindig project can clearly  have a bright
> > future, since 'dashboarding' is and will be a common requirement for
> > many companies, organizations and individual technology solutions.
> > Having stated that, I have a vision that OpenDashboards can easily
> > become the next one-stop shop for diverse dashboarding solutions given
> > the appropriate context and positioning in the technology space.
> >
> > I believe that we should all urge the companies we represent to join
> > the effort and contribute to the evolution of an ecosystem we all
> > could benefit from.  Also, 

New Slack channel for Open Dashboards

[Chris Spiliotopoulos]

Hi all,

I thinks it's about time to move this and future discussions over to a new
medium, as emails have become convoluted.

To keep the ball rolling, I created a new Slack team @
opendashboards.slack.com.  The OpenDashboards name got the most votes so
far so we have something to start with.  We can change that in the future.

I sent a few invites to those I could find directly from my gmail account.
Those of you who signup feel free to send invites to others.

I have created a couple of public channels for starters in sync with the
Trello board.

Voting for the new Github org name ends on Sunday night so show us some
love 

On Monday morning I will creatw a new org @ Github and we start a new
chapter.

Have a great weekend!

Best regards,
Chris

Next steps

[Chris Spiliotopoulos]

Hi all,

A few days have passed since I launched the Trello board
https://trello.com/b/hUTQuH6q/codename-apache-shindig-2015 and people have
spoken.

It's pretty clear that most of us want to move over to Github and the
project to be hosted under a new organization name that will act as an
umbrella for a set of new subprojects.

I've created 2 new lists: one for suggesting and voting for an org name and
the other for suggesting other useful projects using latest technologies
and trends.

The way i see it is that the original monolith should be transferred as is,
as many people are hesitant of breaking it down.  This will allow us to
keep the original engine version at a stable state and at the same allow us
to focus on the creation of a shareable ecosystem of new age services and
components.

So go to Trello, suggest names and vote. By the end of this week we must
have finalists to get things going.

Best regards,
Chris

Re: About Apache Shindig termination

[Chris Spiliotopoulos]

Holla Alberto,

Thanks for reaching out to me!  It's great to see other professionals
shouting out about their dependency and vision on this project, even at
this final moment.

It's never too late.  Let's wait for things to clear on the Apache side and
for others to put their thoughts on the table.

We all have expereiences and case studies to share so it sounds very
exciting so far.

Best regards,
Chris
On Nov 11, 2015 6:36 PM, "Alberto Rodriguez"  wrote:

> Hi Chris,
>
> sorry for the direct approach but I wasn't subscribe to the dev mailing
> list of Apache Shindig and I've just found out all your messages about the
> project termination (I can't reply to the thread)
>
> We, at Stratio, have been creating a visualization tool: Stratio Viewer
>  which is very
> gadget-focused and we've been using Apache Shindig to render our gadgets.
>
> We share all your thoughts about the next steps that the project should
> take, move it to github, create a nice web page to gather people around the
> project and start getting rid of the monolithic architecture of the project
> (in the last weeks we've even created a light-weight version of Shinding).
>
> So please add our +1 to all the things that you've proposed and
> also...I've just subscribe to the dev list so if you don't mind send a
> message to the list so I'll be able to reply to it.
>
> Kind regards,
>
> Alberto Rodriguez
>
> Vía de las dos Castillas, 33, Ática 4, 3ª Planta
> 28224 Pozuelo de Alarcón, Madrid
> Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd
> *
>

Re: Terminate the Apache Shindig Project

[Chris Spiliotopoulos]

ttic.
> > Thanks.
> > > > >
> > > > > -Ryan
> > > > >
> > > > > [1]
> > https://cwiki.apache.org/confluence/display/SHINDIG/Board+Reports
> > > > >
> > > > > -- Forwarded message -
> > > > > From: Ryan Baxter <rbaxte...@apache.org>
> > > > > Date: Mon, Oct 5, 2015 at 9:29 PM
> > > > > Subject: Terminate the Apache Shindig Project
> > > > > To: bo...@apache.org <bo...@apache.org>
> > > > > Cc: priv...@shindig.apache.org <priv...@shindig.apache.org>
> > > > >
> > > > >
> > > > > WHEREAS, the Project Management Committee of the Apache
> DirectMemory
> > > > > project has chosen by vote to recommend moving the project to the
> > > > >  Attic; and
> > > > >
> > > > > WHEREAS, the Board of Directors deems it no longer in the best
> > > > > interest of the Foundation to continue the Apache Shindig project
> > > > > due to inactivity;
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that the Apache Shindig
> > > > > project is hereby terminated; and be it further
> > > > >
> > > > > RESOLVED, that the Attic PMC be and hereby is tasked with
> > > > > oversight over the software developed by the Apache Shindig
> > > > > Project; and be it further
> > > > >
> > > > > RESOLVED, that the office of "Vice President, Apache Shindig" is
> > > > > hereby terminated; and be it further
> > > > >
> > > > > RESOLVED, that the Apache Shindig PMC is hereby terminated.
> > > > >
> > > >
> > >
> >
>



-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
<https://www.linkedin.com/pub/chris-spiliotopoulos>| @Twitter
<https://twitter.com/chefArchitect>

Re: Terminate the Apache Shindig Project

[Chris Spiliotopoulos]

Hi Raj,

well I guess this makes 2 of us!  Let's wait for what others have to say
just to get a clear view of all the perspectives.

Cheers



On Sun, Nov 8, 2015 at 2:10 PM, Raj Janorkar <raj.janor...@gmail.com> wrote:

> Hi Chris,
> i am ready.
> Last year i was thinking to write documentation with examples but couldn't
> do that. i hate apache way of trunk and website.
>
> This time i can help creating few html pages.
>
> Regards,
> Raj
>
> On Sunday 8 November 2015, Chris Spiliotopoulos <
> chrysanthos.spiliotopou...@gmail.com> wrote:
>
> > Hi all,
> >
> > having listened carefully to all the voices from the community so far, I
> > have come down to the following conclusion.
> >
> > There are many professionals among us that have been working in the
> shadows
> > supporting this project in diverse ways - evangelizing, advocating,
> > integrating, etc. without the 'shoulders' of a bold-named company like
> > Google or IBM (who has been the active maintainer of this project for a
> > number of years now).
> >
> > My gut feeling so far has told me that - as has already happened with
> many
> > other technologies - these companies usually invest an amount of time and
> > money for experimenting with different types of technologies and if
> things
> > don't go as planned in the long run, what seems to be happening is that
> > some other company takes over on the experiment and so on, until no big
> > name is really interested any more.
> >
> > During this lifecycle, many other companies are starting to adopt the
> > technologies and they are indeed putting them into good use to serve
> their
> > purposes.  And this is exactly where we stand at the moment.  I can
> totally
> > understand the feelings coming from Ichiro and Darren and at the same
> time
> > I get Ryan's point of view.  So how do we handle this situation?
> Speaking
> > for myself, as I come from Greece and I have to live and work in a
> country
> > that is in crisis mode for quite a few years now, all I can say is that a
> > crisis can be the mother of invention and change for a better tomorrow.
> > And this is exactly how I see this situation - in a metaphorical way of
> > course :)
> >
> > I think that now is the right time to make a change.  Things have changed
> > in our industry during the last 10 years and so have trends and
> > communities.  Maybe 10 years ago, the Apache Foundation was the place to
> be
> > but now this is definitely not the case - of course this doesn't mean
> that
> > the foundation is not the birthplace of great technologies.  But all the
> > action now is over at GitHub.
> >
> > So, since Ryan gave us the green light (from the foundation's
> perspective)
> > that the project can be migrated, I'm outlining my proposals:
> >
> >- We break down the Shindig project into a number of distinct parts -
> >personally I've never used the OpenSocial features and have no
> interest
> > in
> >them since I'm heavily focused on the gadget containment and rendering
> >facilities.  But there are people like Rene who have invested a lot of
> > time
> >and work on extending the OpenSocial features.
> >- We give it a brand new name - never liked the name Shindig in the
> >first place (speaking for myself once more).  I think that this is
> very
> >important since we want to make a bold statement to communities that
> > this
> >technology is active, we're using it and others should try it out
> > because
> >it may solve them a number of problems.
> >- Create a modern web site on GitHub where we can all share our
> >experiences through show cases, usage examples and tutorials
> >- We start thinking around the concept of a gadget-centered
> marketplace
> >- in the context of show casing stuff.  If I remember correctly
> Darren's
> >team has already launched a project which is very similar to the
> iGoogle
> >web site so he could certainly provide some ideas.
> >- Issues and feature requests can be handled directly though GitHub
> in a
> >more agile and community oriented approach without any of the
> > bureaucratic
> >processes imposed by the Apache Foundation.  Once the 'monolith' is
> > broken
> >down into different projects then it would be more manageable and
> people
> >having certain skills could join forces
> >- By utilizing technologies like Docker there is no need for hosting
> >resources and sample material - we can bundle our examp

Re: Terminate the Apache Shindig Project

[Chris Spiliotopoulos]

Raj,

I think rushing into things will just bring us to the same situation but at
a different location this time.

Let's just leave Ryan to do what he's been told to do and wait for others
input regarding the calls to action I suggested.  If we really want to make
a fresh start, then this should include a new perspective on things and
processes.

I can hardly agree with you regarding the monolith project - I think that
if someone wants to put a 'body tag' on this thing is to just leave it as
it is.  Let's just wait for others to give their feedback on the renaming
and splitting options and I'm sure that things will get clearer.

Regards,
Chris

On Mon, Nov 9, 2015 at 3:16 AM Raj Janorkar <raj.janor...@gmail.com> wrote:

> Okay.
>
> Thank you Ryan.
>
> On Mon, Nov 9, 2015 at 11:12 AM, Ryan Baxter <rbaxte...@apache.org> wrote:
>
> > Raj, I need to check with the board about what to do here.  The board
> voted
> > to move the project to the attic so I have a feeling that will need to
> > happen first to officially retire the project in the Apache's eyes.  Then
> > you can take the code and do what you please with the code.  At this
> point
> > since the project has officially been terminated I don't think we can do
> a
> > release.
> >
> > On Sun, Nov 8, 2015 at 8:07 PM Raj Janorkar <raj.janor...@gmail.com>
> > wrote:
> >
> > > Hi Ryan,
> > >
> > > Before moving to Github, It would be great to release the FINAL version
> > > with all the changes done in since last release.
> > >
> > > What says?
> > >
> > > On Mon, Nov 9, 2015 at 11:05 AM, Raj Janorkar <raj.janor...@gmail.com>
> > > wrote:
> > >
> > > > Hi Ryan,
> > > >
> > > > Thank you.
> > > >
> > > > I think it would be good if we officially move this project to
> github.
> > If
> > > > not possible then put this project to attic and then just create
> single
> > > > copy on github, so that we have one project for all dev community to
> > > > concentrate on. Otherwise we will end up creating same project in
> > > different
> > > > places with different versions and customization which is very hard
> to
> > > > track and focus on.
> > > >
> > > > If you all okay i can checkout the project from apache and put it
> into
> > > > github, if there is way anybody know directly moving from apache to
> > > github
> > > > then we can do that way.
> > > >
> > > > What you think about this Ryan/Chris/Darren and all others?
> > > >
> > > > Thank You.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Nov 9, 2015 at 10:52 AM, Ryan Baxter <rbaxte...@apache.org>
> > > wrote:
> > > >
> > > >> Hi Guys,
> > > >>
> > > >> It is great to see your enthusiasm for the project!  I still need to
> > go
> > > >> through the process of moving the project to attic in Apache, but I
> > > don't
> > > >> see why you cant take the pieces you want and start a "new" project
> > > >> elsewhere.
> > > >>
> > > >> On Sun, Nov 8, 2015 at 5:07 PM Raj Janorkar <raj.janor...@gmail.com
> >
> > > >> wrote:
> > > >>
> > > >>> Thats Great Site Darren.
> > > >>> Lets give new life to Shindig.
> > > >>>
> > > >>> I am sure there are so many other sites using shindig.
> > > >>>
> > > >>> Regards, Raj
> > > >>>
> > > >>> On Monday 9 November 2015, Darren Bond <db...@globalcad.com>
> wrote:
> > > >>>
> > > >>> > Hi Raj,
> > > >>> >
> > > >>> > We did the same and produced www.blueg.com
> > > >>> >
> > > >>> > Happy to share some experiences too.
> > > >>> >
> > > >>> > Kind regards,
> > > >>> >
> > > >>> > Darren
> > > >>> >
> > > >>> > - Reply message -
> > > >>> > From: "Raj Janorkar" <raj.janor...@gmail.com <javascript:;>>
> > > >>> > To: "Chris Spiliotopoulos" <chrysanthos.spiliotopou...@gmail.com
> > > >>> > <ja

Re: Terminate the Apache Shindig Project

[Chris Spiliotopoulos]

nger developers and diverse audiences.  Most of us are
already doing this for our companies, why not share the foundation work
with others and start building a community?

Lack of development activity doesn't necessarily mean lack of interest or
potential.  In Shindig's case this is a good thing because we have a stable
framework in our hands.  But most of the people in the tech business
doesn't know such a thing exists.  And I'm sure that this is not
irreversible.

Kind regards,
Chris



On Thu, Oct 8, 2015 at 12:31 AM, Raj Janorkar <raj.janor...@gmail.com>
wrote:

> Hi Ryan,
>
> This is really sad news.
> I am really thankful of your and dev team support you all helped me lot.
>
> As Darren Said Shindig is very much stable and i dont see any isues at the
> moment.
>
> Just one thing i can see so many bug fixed since last release. So will
> there be final release Ryan? If you can that would be great and may be your
> last favour to all of us and your loved baby Shindig.
>
> I dont see any future of apache rave either, people are so busy switching
> between millions of apps on their iphone. so no gadgets based sites are
> their interest But history repeats itself.
>
> lets see what comes next.
>
> Thank you
>
>
> On Thursday 8 October 2015, Darren Bond <db...@globalcad.com> wrote:
>
> > Dear All,
> >
> > This is very sad news indeed. Apache Shindig is at the core of several of
> > our very popular sites - we consider it a mature product that does
> exactly
> > what it should, and does it very well indeed. Perhaps that's partly the
> > reason for the lack of user support requests!
> >
> > You, the dev team, kindly helped us resolve a number of issues back in
> > 2014 and we've never looked back since - we love Apache Shindig!
> >
> > Thank you for all your commitment, love, sweat and tears developing the
> > project - we truly value what you have created and will continue its use
> > well into the future.
> >
> > Kind regards,
> >
> > Darren
> >
> >
> > -Original Message-
> > From: Ryan Baxter [mailto:rbaxte...@apache.org <javascript:;>]
> > Sent: 07 October 2015 19:32
> > To: dev@shindig.apache.org <javascript:;>
> > Subject: Fwd: Terminate the Apache Shindig Project
> >
> > Hi fellow Shindig Devs,
> >
> > I would like to let you all know that the Shindig PMC has voted to
> > terminate the Shindig project and move it to the attic.  I have already
> > informed the Apache board about the termination in this months board
> report
> > (below).
> >
> > As most of you have probably noticed we have seen a decline in
> > participation in all aspects of the project over the past months and the
> > downward trend has been happening for over a year now.  This can
> certainly
> > be seen in our reports to the board [1].
> >
> > If anyone has any questions please let me know, and I will be sure to
> keep
> > everyone up to date as we transition the project to the attic.  Thanks.
> >
> > -Ryan
> >
> > [1] https://cwiki.apache.org/confluence/display/SHINDIG/Board+Reports
> >
> > -- Forwarded message -
> > From: Ryan Baxter <rbaxte...@apache.org <javascript:;>>
> > Date: Mon, Oct 5, 2015 at 9:29 PM
> > Subject: Terminate the Apache Shindig Project
> > To: bo...@apache.org <javascript:;> <bo...@apache.org <javascript:;>>
> > Cc: priv...@shindig.apache.org <javascript:;> <
> priv...@shindig.apache.org
> > <javascript:;>>
> >
> >
> > WHEREAS, the Project Management Committee of the Apache DirectMemory
> > project has chosen by vote to recommend moving the project to the  Attic;
> > and
> >
> > WHEREAS, the Board of Directors deems it no longer in the best interest
> of
> > the Foundation to continue the Apache Shindig project due to inactivity;
> >
> > NOW, THEREFORE, BE IT RESOLVED, that the Apache Shindig project is hereby
> > terminated; and be it further
> >
> > RESOLVED, that the Attic PMC be and hereby is tasked with oversight over
> > the software developed by the Apache Shindig Project; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Shindig" is hereby
> > terminated; and be it further
> >
> > RESOLVED, that the Apache Shindig PMC is hereby terminated.
> >
> >
> >
>



-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
<https://www.linkedin.com/pub/chris-spiliotopoulos>| @Twitter
<https://twitter.com/chefArchitect>

Re: Terminate the Apache Shindig Project

[Chris Spiliotopoulos]

Hi Ryan,

thanks for the response - points taken.  Let's see what the future holds :)

Best regards

On Thu, Oct 8, 2015 at 4:07 PM, Ryan Baxter <rbaxte...@apache.org> wrote:

> Hi Chris, thanks for the very thoughtful email.  In general I agree with
> what you are saying.  Some more comments inline.
>
> On Thu, Oct 8, 2015 at 5:54 AM Chris Spiliotopoulos <
> chrysanthos.spiliotopou...@gmail.com> wrote:
>
> > Hi all,
> >
> > instead of becoming emotional I prefer sharing some thoughts with
> everyone
> > in this thread.  Well, to be honest I think that everyone expected this
> to
> > happen at some point.  Of course not due to lack of support from the dev
> > team - this had always been superb - but rather due to lack of awareness
> > regarding this (IMHO) ground-breaking technology and I'm referring to the
> > gadgets side of things.
> >
> > I've been using gadgets for quite a few years and I've managed to
> convince
> > people about the benefits of having a fully decoupled system with
> pluggable
> > apps either in-house or 3rd party.  Of course as I have stated in the
> past
> > this had always been a steep curve as very few people are aware of this
> > technology but in the end everybody would buy in after seeing the
> results.
> > During these years I have managed to 'tame the beast' as resources had
> > always been scattered and very few and eventually was able to put it to
> > work for producing great dashboard apps and in the future (I hope)
> > marketplaces as well.
> >
> > My personal feeling is that most of the people using Shindig for a long
> > time now are here for its gadget rendering capabilities and the potential
> > it provides towards a fully decoupled architecture where app devs can
> work
> > independently from platform devs but eventually everything can work
> > together a a whole with minimum orchestration efforts.  This has been my
> > personal experience so far anyways.  Having said that, I've always felt
> > that the Shindig project had always been to large / broad in
> functionality
> > lacking clearly not dev but rather promotional & awareness efforts.
> >
> > Another factor that always helped me rest assured in a way regarding its
> > usefulness and future  is that major companies like Google, Atlassian and
> > others with very popular products have also been using this technology
> as a
> > core component of their infrastructure until now.  Although Google who
> > open-sourced the tech seems that it progressively deprecates some of
> their
> > products who had major touch points with the gadgets spec, still keeps it
> > alive in products like Gmail, Google apps, etc plus they have been
> hosting
> > the official Gadgets API site for a long time now.  One of the puzzling
> > questions though is why these companies (apart from the IBM people who
> kept
> > the project running) were never openly involved with the promotion and
> > support of the tech in order to reach broader audiences through real-life
> > use cases?  Correct me if I'm wrong but I've come to the conclusion that
> > these companies are maintaining probably ports of certain Shindig
> > components that have extended them in order to meet their requirements.
> > This is easy to speculate since reading the documentation of their
> products
> > shows clearly that there are extensions not supported by Shindig
> > out-of-the-box - once I had a chat with a guy working at Jive at the time
> > and he told me that they wrote their own security layer around their
> gadget
> > containers.
>
>
> > I'll have to agree with Darren that due to the robustness of the
> framework
> > most integrators are more than ok with the standard features it has to
> > offer and therefore this might have caused the side-effect to the
> > maintainers to since there are no new requests / ticket activities then
> > this framework has fulfilled its purpose and has become out of fashion.
> I
> > personally think that gadget tech has a future and a lot to offer when it
> > comes down to specific use cases - dashboards and marketplaces being a
> > couple for starters.  After I received this mail today morning, I had a
> > quick search on the web to see if there are any real alternatives but I
> > found none.  Has the plug-n-play model on the web become old fashioned
> > then?  Are composable  web apps like dashboards coming to an end?  I
> don't
> > think so.
> >
> > I have not seen anything else that is as robust as gadgets so far,
> although I have heard some buzz around these things called "

Re: Preserving content from docs.opensocial.org

[Chris Spiliotopoulos]

Hi Matt,

as here in Apache Shindig we're in the process of face-lifting and
restructuring the web site - as well as gathering and re-organizing our
resources - could you give us an indication of when you think of bringing
the wiki down, so that I can export the pages?


Cheers,
Chris

On Mon, Nov 17, 2014 at 8:50 PM, Matthew Marum vp-proje...@opensocial.org
wrote:

 OpenSocial is looking at decommissioning docs.opensocial.org (aka
 https://opensocial.atlassian.net/wiki/display/OS/Home) which is our old
 Confluence wiki.  Most of the content on the wiki is pretty old but the
 OpenSocial Officers wanted to make sure that any content that needed to be
 saved was retrieved by the Apache Rave and Apache Shindig communities.  All
 the OpenSocial specifications and the supporting process documentation are
 currently hosted and will continue to be hosted on Github (
 https://github.com/OpenSocial/spec/) and OpenSocial.org.

 Are there any links between Apache Shindig and Rave documentation to
 docs.opensocial.org?  Or are there any links that MUST stay active on the
 wiki?  For that matter, are there any links to an *.opensocial.org web
 property that MUST stay active that we should be aware of?

 *Matthew Marum*
 *VP of Projects*
 *email: vp-proje...@opensocial.org vp-proje...@opensocial.org*
 *skype: mgmarum*




-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
https://www.linkedin.com/pub/chris-spiliotopoulos| @Twitter
https://twitter.com/chefArchitect

Re: Site redesign - Confluence resource page

[Chris Spiliotopoulos]

Hi Stanton,

thanks for the upvote mate!  Well, I marked the Documentation  Site page
with X as redundant to be honest, as it contains links to the rest of the
menu items.  Maybe X was not the best choice - sorry for that.

Regarding the comments, as soon as I log in to Confluence, the comment
editor is visible.  Check again if you can.

Cheers,
Chris

On Thu, Nov 13, 2014 at 3:35 PM, Stanton Sievers ssiev...@apache.org
wrote:

 Hi Chris,

 Thanks for pulling this together!

 Are comments disabled on the page?  I don't see a way to leave comments
 even after login.

 Anyway, my one comment is that you've marked Documentation - Center as
 broken, but it works for me.  I get directed to [1].

 Thanks!
 -Stanton

 [1] http://shindig.apache.org/documentation_centre.html

 On Wed, Nov 12, 2014 at 8:30 AM, Chris Spiliotopoulos 
 chrysanthos.spiliotopou...@gmail.com wrote:

  Hi all,
 
  I've created a new wiki page
  https://cwiki.apache.org/confluence/display/SHINDIG/Web+Site+Redesign
  for
  gathering all resources related to the site redesign. I uploaded the
  current site map diagram containing all internal / external resources.
 
  Use this for reference.
 
  Cheers,
  Chris
 
 
 
  --
  Chris Spiliotopoulos
 
  Solutions Architect | @LinkedIn
  https://www.linkedin.com/pub/chris-spiliotopoulos| @Twitter
  https://twitter.com/chefArchitect
 




-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
https://www.linkedin.com/pub/chris-spiliotopoulos| @Twitter
https://twitter.com/chefArchitect

Fwd: Site redesign - Confluence resource page

[Chris Spiliotopoulos]

Hi all,

I've created a new wiki page
https://cwiki.apache.org/confluence/display/SHINDIG/Web+Site+Redesign for
gathering all resources related to the site redesign. I uploaded the
current site map diagram containing all internal / external resources.

Use this for reference.

Cheers,
Chris



-- 
Chris Spiliotopoulos

Solutions Architect | @LinkedIn
https://www.linkedin.com/pub/chris-spiliotopoulos| @Twitter
https://twitter.com/chefArchitect

Re: Implementation Guide

[Chris Spiliotopoulos]

Darren, thanks for the contribution proposal - sounds great!  IMO the logo
should express plug-ability (gadgets)  social connectivity (OpenSocial
APIs).

René, to be honest I had you in mind!  I had been watching closely all the
discussion at the time regarding your contribution and I think it
would be more than great to write a tutorial on this.



On Thu, Oct 9, 2014 at 10:38 AM, René Peinl rene.pe...@hof-university.de
wrote:

 Hi Raj,
 we are using Shindig in our project for collecting events from Liferay,
 XWiki, Alfresco and OpenXchange and presenting them as an Activity Stream
 inside a Liferay portlet. We are using the neo4j Backend we contributed as
 a storage solution. This allows us to offer social networking that provides
 friend suggestions and shows the shortest path between two people not
 directly connected, both as a Liferay portal.
 I could contribute a case description to the implementation guide, if you
 like.
 A demo with these systems will be available early 2015 I guess.
 Regards
 René

 -Ursprüngliche Nachricht-
 Von: Raj Janorkar [mailto:raj.janor...@gmail.com]
 Gesendet: Donnerstag, 9. Oktober 2014 01:53
 An: dev@shindig.apache.org
 Betreff: Re: Implementation Guide

 Hi Ryan,

 I think we need

 1) Great Logo for shindig
 2) Attractive yet simple template for doco.
 3) Few shindig implementations on web, this will help users to understand
 how shindig work and what extend it can be enhanced.

 These will help shindig to attract new users/developers.

 Sorry i do not have skill to develop logo. If we dont get any i am happy
 to find some font which will look good for name shindig, let me know.


 Regards,
 Raj

 On Thu, Oct 9, 2014 at 6:33 AM, Ryan Baxter rbaxte...@apache.org wrote:

  Chris many other popular apache projects keep the project
  documentation on the project sitetake a look at Apache HTTP,
  Apache Tomcat, and Apache Hadoop.  Not sure if they have all moved
  over to Apache CMS or not but I would rather stick with the
  convention.
 
  Agree on a new logo, if anyone has the skills to come up with one that
  would be great.
 
  On Wed, Oct 8, 2014 at 4:17 AM, Chris Spiliotopoulos
  chrysanthos.spiliotopou...@gmail.com wrote:
   Hi all,
  
   the question is how we should balance the material between Apache
   CMS and Confluence.  I think that all technical guides and resources
   should go
  into
   Confluence - making it the official documentation space, rather than
  just a
   wiki - and all the high-level reference / 'marketing' / news
   material
  into
   the web site.
  
   I'm having a look at different Bootstrap themes in order to select a
   few, submit the initial list and let the people involved decide.  As
   I've already said, I think we should use a vibrant theme that shouts
   Hey,
  have
   a look inside. It's good stuff! therefore my attention is grabbed
   by 'landing page' / 'agency' parallax type themes.
  
   One thing that is missing though, is a kick-ass Shindig logo.  Is
   someone willing to create one?  Raj, if you could suggest a
   Bootstrap theme that would be great.
  
   In the following days, I'll post a selection of themes as a
   reference and we can vote.  Also, I'll try and write down a
   suggested link structure
  for
   the new site and also a scaffolding for the technical docs in
 Confluence.
  
   Let me know what you think.
  
   Cheers,
   Chris
  
   On Wed, Oct 8, 2014 at 2:27 AM, Ryan Baxter rbaxte...@apache.org
  wrote:
  
   OK well for reference check out the website docs [1].  Let me know
   if you have any problems.
  
   [1] http://shindig.apache.org/documentation_website.html
  
   On Tue, Oct 7, 2014 at 7:24 PM, Raj Janorkar
   raj.janor...@gmail.com
   wrote:
Hi Ryan,
   
In my work place i am using Confluence. so i don't think there
will be problem to me.
   
Regards,
Raj
   
On Tue, Oct 7, 2014 at 7:17 AM, Ryan Baxter rbaxte...@gmail.com
  wrote:
   
Chris and Raj, appreciate you both stepping up!  Are you
familiar
  with
how to use Apache CMS to edit the Shindig site?
   
On Thu, Oct 2, 2014 at 7:09 AM, Raj Janorkar
raj.janor...@gmail.com
  
wrote:
 I am also in.
 though i am new here but ready to help wherever i can.

 Thank you for this great step.

 On Thu, Oct 2, 2014 at 7:14 PM, Chris Spiliotopoulos 
 chrysanthos.spiliotopou...@gmail.com wrote:

 Hi all,

 I am willing to take the first step forward on this but I
 expect
  all
 the
 people in this group to contribute / suggest / vote on
 important
   things
 that will make the Shindig project come back to life and
 start receiving attention.  Based on the steps that Ryan
 suggested:


  *1.  We use the Shindig site as the place to keep the
   documentation.
  It
 is
  CMS based [1] so no need to know how to write HTML.*


 First we need to decide on an awesome  clean theme for the
  website

Re: Implementation Guide

[Chris Spiliotopoulos]

Hi all,

the question is how we should balance the material between Apache CMS and
Confluence.  I think that all technical guides and resources should go into
Confluence - making it the official documentation space, rather than just a
wiki - and all the high-level reference / 'marketing' / news material into
the web site.

I'm having a look at different Bootstrap themes in order to select a few,
submit the initial list and let the people involved decide.  As I've
already said, I think we should use a vibrant theme that shouts Hey, have
a look inside. It's good stuff! therefore my attention is grabbed by
'landing page' / 'agency' parallax type themes.

One thing that is missing though, is a kick-ass Shindig logo.  Is someone
willing to create one?  Raj, if you could suggest a Bootstrap theme that
would be great.

In the following days, I'll post a selection of themes as a reference and
we can vote.  Also, I'll try and write down a suggested link structure for
the new site and also a scaffolding for the technical docs in Confluence.

Let me know what you think.

Cheers,
Chris

On Wed, Oct 8, 2014 at 2:27 AM, Ryan Baxter rbaxte...@apache.org wrote:

 OK well for reference check out the website docs [1].  Let me know if
 you have any problems.

 [1] http://shindig.apache.org/documentation_website.html

 On Tue, Oct 7, 2014 at 7:24 PM, Raj Janorkar raj.janor...@gmail.com
 wrote:
  Hi Ryan,
 
  In my work place i am using Confluence. so i don't think there will be
  problem to me.
 
  Regards,
  Raj
 
  On Tue, Oct 7, 2014 at 7:17 AM, Ryan Baxter rbaxte...@gmail.com wrote:
 
  Chris and Raj, appreciate you both stepping up!  Are you familiar with
  how to use Apache CMS to edit the Shindig site?
 
  On Thu, Oct 2, 2014 at 7:09 AM, Raj Janorkar raj.janor...@gmail.com
  wrote:
   I am also in.
   though i am new here but ready to help wherever i can.
  
   Thank you for this great step.
  
   On Thu, Oct 2, 2014 at 7:14 PM, Chris Spiliotopoulos 
   chrysanthos.spiliotopou...@gmail.com wrote:
  
   Hi all,
  
   I am willing to take the first step forward on this but I expect all
   the
   people in this group to contribute / suggest / vote on important
 things
   that will make the Shindig project come back to life and start
   receiving
   attention.  Based on the steps that Ryan suggested:
  
  
*1.  We use the Shindig site as the place to keep the
 documentation.
It
   is
CMS based [1] so no need to know how to write HTML.*
  
  
   First we need to decide on an awesome  clean theme for the website
   that
   will be responsive and attractive.  As Bootstrap is already being
 used
   that
   should be no prob, but we need to use a theme that will rock.  Please
   suggest themes from other sites that you find attractive and user
   friendly.  For instance, I find the SailsJS http://sailsjs.org/
 theme
   very clear for reading.  Also, if someone could deal with the art
 work
   that
   would be very useful.
  
  
  
   
*2.  We create a getting started guide, containing the minimal set
of steps to get someone up and running.*
  
  
   
*3.  We create a detailed implementation guide that addresses how
someone
would extend Shindig to build their own implementation.*
  
  
   Next, we need to make a map of the current structure of the web site
   and
   then suggest alternatives on how the new site should be structured.
   The
   key here is that it should be self explanatory and guide you
   step-by-step
   on how to do from the simplest to the most advanced task.  Newcomers
   should
   feel comfortable with it so that they start with an appetite to learn
   more
   about this project.
  
   This part requires an initial gathering of all existing resources and
   cleansing.  Everything should be relevant to the latest version
of the framework.  A few months ago I had created a GitHub project
   https://github.com/theChefArchitect/os-examples-container-embedded
   with
   a
   sample embedded container in a Spring web app written for this
 purpose.
   I've also noticed that the maintenance of the PHP version has
 stopped.
   All
   these cluttered resources should be gathered in one place initially
 and
   then decide which of them should be used as a reference for the new
   documentation.
  
  
*4.  In the process of doing this we cleanup/consolidate the
 Shindig
site
and the wiki.*
  
  
   One important thing that should be decided is where the
 documentation /
   tutorials should be hosted.  At the moment the web site acts as a
 proxy
   for
   different documentation locations around the web and some hard-core
   tech
   docs live under Atlassian's Confulence site
   https://opensocial.atlassian.net/wiki/display/OSREF. What's the
 story
   with that?  Will the documentation be hosted under Confluence or
 under
   the
   web site?
  
   Overall, this task requires collaborative effort and should be done
 in
   baby
   steps.  Documentation / guides are important

Re: Implementation Guide

[Chris Spiliotopoulos]

Hi all,

I am willing to take the first step forward on this but I expect all the
people in this group to contribute / suggest / vote on important things
that will make the Shindig project come back to life and start receiving
attention.  Based on the steps that Ryan suggested:


 *1.  We use the Shindig site as the place to keep the documentation. It is
 CMS based [1] so no need to know how to write HTML.*


First we need to decide on an awesome  clean theme for the website that
will be responsive and attractive.  As Bootstrap is already being used that
should be no prob, but we need to use a theme that will rock.  Please
suggest themes from other sites that you find attractive and user
friendly.  For instance, I find the SailsJS http://sailsjs.org/ theme
very clear for reading.  Also, if someone could deal with the art work that
would be very useful.




 *2.  We create a getting started guide, containing the minimal set
 of steps to get someone up and running.*



 *3.  We create a detailed implementation guide that addresses how someone
 would extend Shindig to build their own implementation.*


Next, we need to make a map of the current structure of the web site and
then suggest alternatives on how the new site should be structured.  The
key here is that it should be self explanatory and guide you step-by-step
on how to do from the simplest to the most advanced task.  Newcomers should
feel comfortable with it so that they start with an appetite to learn more
about this project.

This part requires an initial gathering of all existing resources and
cleansing.  Everything should be relevant to the latest version
 of the framework.  A few months ago I had created a GitHub project
https://github.com/theChefArchitect/os-examples-container-embedded with a
sample embedded container in a Spring web app written for this purpose.
I've also noticed that the maintenance of the PHP version has stopped.  All
these cluttered resources should be gathered in one place initially and
then decide which of them should be used as a reference for the new
documentation.


 *4.  In the process of doing this we cleanup/consolidate the Shindig site
 and the wiki.*


One important thing that should be decided is where the documentation /
tutorials should be hosted.  At the moment the web site acts as a proxy for
different documentation locations around the web and some hard-core tech
docs live under Atlassian's Confulence site
https://opensocial.atlassian.net/wiki/display/OSREF. What's the story
with that?  Will the documentation be hosted under Confluence or under the
web site?

Overall, this task requires collaborative effort and should be done in baby
steps.  Documentation / guides are important but then there are plenty of
other stuff needed to make this project gain a vibrant community - e.g.
gadgets hosted on the site for tutorials and show cases, API documentation
/ integration, social media presence, etc.

Looking forward to your responses.

Cheers,
Chris


On Thu, Oct 2, 2014 at 12:12 AM, Ryan Baxter rbaxte...@apache.org wrote:

 Does anyone feel especially passionate about this topic and want to
 step up and take the lead on this?

 On Wed, Sep 17, 2014 at 4:26 AM, Darren Bond db...@globalcad.com wrote:
  Hi Ryan,
 
  This sounds like a really great start. I'm sure a clean and clear
 getting started guide + detailed implementation guide that can be easily
 located on the Shindig site will make a huge difference on the take-up of
 this impressive framework.
 
  Kind regards,
 
  Darren
 
 




-- 
Chris Spiliotopoulos

Solutions Architect