1.0 Abstract

The Project SocialSite development community would like to become an Apache project to gain the governance and diversity needed to survive and thrive as a viable open source project. This document covers the background, rational, goals, status and risk involved in incubating the project.

2.0 Background

Project SocialSite is an open source (CDDL/GPLv2) Social Networking Service based on Apache Shindig (incubating). The software is not simply a "canned" Social Network or Facebook-in-a-box type of web application; it's something different. Project SocialSite is designed to add social networking features to existing web applications and web sites. Project SocialSite is made up of two parts: 1) a social data server that supports the OpenSocial APIs and extensions and 2) a set of OpenSocial gadgets that provide a complete user-interface for social networking.

3.0 Rationale

Project SocialSite was developed internally by Sun Microsystems and released as open source under a dual CDDL/GPLv2 license in September 2008. Sun discontinued the project in January 2009, but development of the code-base has continued without salaried developers and the community has expressed interest in continuing as a project, so long as a level playing field can be established for contributors. To provide the governance needed to grow a viable and diverse development community, the Project SocialSite community would like to become an Apache project. Recently, Sun agreed to contribute the code base to the Apache Software Foundation to make this possible.

4.0 Initial Goals

The initial goals of the project are to build an active community, learn to operate as an Apache project, keep in sync with the evolving OpenSocial specifications and with the Apache Shindig (incubating) project and continue to improve performance and usability.

5.0 Current Status

This section covers the current status of Project SocialSite.

5.1 Meritocracy

Project SocialSite has been run under the Glassfish rules of governance, which dictate consensus-based decision making and some level of meritocracy. The community members are familiar with the Apache way and ready to work in an Apache-style meritocracy.

5.2 Community

The Project SocialSite community is relatively small, but some members are already usiing Project SocialSite in production. They are already working together by participating in mailing lists, contributing code and submitting issues and patches.

5.3 Core Developers

Project SocialSite was originally developed by employees of Sun Microsystems, but the community membership is no longer dominated by Sun.

5.4 Alignment

Well aligned with Apache in terms of technologies and licensing. The code-base makes extensive use of Apache technologies including Commons, Struts, Ant and Shindig. The community is happy with changing the license terms and Sun, the copyright holder, is willing to make the necessary code contribution.

6.0 Known Risks

This section covers the risks that the project will face as it progresses through incubation.

6.1 Orphaned products

Risk level: moderate to high. Project SocialSite is definitely an orphaned product, but this is mitigated by the facts that 1) development has continued after project cancellation and 2) members of the community intent to use the code in production on major sites. There is some risk that community members will not be able to commit the time necessary to build community and code necessary to achieve project status.

6.2 Inexperience with Open Source

Risk level: low. All of the community members have experience with open source and several have extensive experience with Apache.

6.3 Homogeneous Developers

Risk level: low. The community is diverse and made up of developers from different organizations.

6.4 Reliance on Salaried Developers

Risk level: moderate. The community includes members who are paid to work on the code and some who are not.

6.5 Relationships with Other Apache Products

Risk level: low to moderate. Project SocialSite is based on Apache products, but the most important of these products is still incubating (Shindig).

6.6 A Excessive Fascination with the Apache Brand

Risk level: low. The Project SocialSite community wants to become an Apache project to gain the governance and level playing field needed for viability, not any sort of marketing advantage.

7.0 Documentation

This section covers the details of the source code submission and code-base dependencies.

7.1 Initial Source

The initial source will come from the Subversion repository at Project SocialSite's Java.net based site.

7.2 Source and Intellectual Property Submission Plan

The plan is to 1) have Sun submit a the code grant paper work and 2) copy the code from Project SocialSite's trunk to the Apache Incubator's Subversion repository. Once that is done we will set about replacing license headers and changing names from Project SocialSite to Apache SocialSite and changing the package names from com.sun.socialsite to org.apache.socialsite.

7.3 External Dependencies

The Project SocialSite codebase has the following runtime dependencies:

And the following build-time dependencies:

7.4 Cryptography

Same Cryptography dependencies as Apache Shindig (incubating)

8.0 Required Resources

This section outlines the resources that the project will require.

8.1 Mailing lists

8.2 Subversion Directory

Requirement: One Subversion repository. Should be named "socialsite"

8.3 Issue Tracking

Requirement: One issue tracking system, JIRA prefered

8.4 Other Resources

9.0 Initial Committers

10.0 Affiliations

Affiliations are listed in section 9.0.

11.0 Sponsors

We propose that Apache SocialSite be sponsored by the Incubator itself.

11.1 Champion

11.2 Nominated Mentors

11.3 Sponsoring Entity

Apache Incubator

SocialSiteProposal (last edited 2009-09-20 23:05:28 by localhost)