All enterprise social collaboration platforms include gathering points whereby people can unite with others around a common goal; for example, a program or project, social interest, organization, market segment, product, corporate initiative, technology, etc. Within Quad – Cisco’s Enterprise Collaboration Platform and product – these gathering points are referred to as communities. The longevity of any given community will vary based on several factors, which include temporal needs, relevancy, and usefulness. Some communities will be required for a long time while others may only be needed for a short time. Without clear mechanisms to identify the usefulness of each community and manage those that reach end of life, a social collaboration platform can become difficult to manage from a community governance vantage point. The performance of the platform can be negatively impacted by excessive community clutter resulting from orphaned or unused communities.
There comes a time in the evolution of building a technology platform that you have to pause and look back where you’ve come from, before continuing on with the journey. As I think back to the formation of the Cisco Eos platform, it was a time of hard work and rapid growth.
The Cisco Media Solutions Group went from being a business unit with an idea, to truly taking form in 2007 when Cisco made three software acquisitions—Five Across, the assets of Tribe.net and the assets of Click.tv. From that day forward, we were charged with developing an innovative platform that could get media companies online in a simple, manageable way. That long journey started with the single though difficult step of uniting three independent companies and countless independent perspectives into a single team executing against a single vision.
As with any consolidation effort, tough decisions had to be made. One of the most important we faced was what development platform we were going to leverage. Our three teams had experience in just as many languages: Ruby on Rails, PHP, and Java – not to mention Adobe Flex and even a bit of C. After much debate, we chose to use Java for the back end, which includes the core Cisco Eos data and content components like blogs, discussions, and member profiles. And we chose PHP for the front end, the dynamic page-rendering environment that our users can customize for presentation to end consumers. Read More »
Hello, my name is David. I want to tell you a story. It’s a story about the people who imagined that there might be a way to enable humans to communicate across time and space. It’s about their passion and determination to pursue that dream, to boldly explore all the possibilities.
It’s also about a series of events that led us to the invention of new technologies, to the development of new systems and the ongoing investment in essential network infrastructure that enabled a bounty of telecommunication innovations that would ultimately benefit all humanity.
This story began to unfold more than 150 years ago. Since then, there’s been rapid progress. In fact, people are now accessing many types of multimedia content on a multitude of connected devices. The “connected life” reflects our desire to have many integrated services and experiences that are available anytime, anywhere, and on any device.
Today we’re launching a new project.
Welcome to the Connected Life Exchange – an evolving narrative about how people connect, communicate, and collaborate.