Why Incubation? (Susan)

Spread the Jasig Community wealth to other projects
Ensure community guided development
Mentor and sponsor projects to be as successful as possible

Incubation Goals = Jasig Goals (Susan)

Robust projects
healthy communities
active governance

Where are we? (Susan)

Creation of Incubation Process began in 2008
Began Incubating projects while creating process
Graduated Bedework Project May 2010
Since then 6 portlets and now, .NET CAS client and FIFER, Community of Practice

Who are we? (Susan)

Susan Bramhall (Yale University) (chair)
Tim Carroll (University pf Illinois)
Cris Holdorph (Unicon)
Tuyhang Ly (Rutgers University)
Benito J. Gonzalez (University of California, Merced)
Steve Swinsburg (Australian National University)

The Incubation Process

How to submit a or start a new project (Benito)

Go to Jasig Jira ( https://issues.jasig.org/ )
Find the Incubation project
Create a new Incubation project - Candidate Proposal issue** Fill in Summary, Description, Overview (and other required fields)
- If project is a coding project, begin process of signing ICLA/CCLA's

Resources and Support (Benito)

Mentor (who gets assigned your Incubation Jira issue) - will help you through the incubation process
Wiki (Confluence) - an area for project documentation
Mailing List - Jasig supported e-mail list support (hosted by University of Wisconsin)
Subversion - Jasig source code control repository
Jira - Individual Project Issue Tracking

Criteria for exiting to sponsored project (Cris)

Legal

CLAs
License / notice etc (mention licensing plugin)

Community

multiple committers / institutions / adopters
future support

Governance

Steering committee
voting
etc

Alignment & Synergy

Integration with other Jasig projects where appropriate
Synergy with other Jasig projects

Infrastructure

Wiki (Confluence) - project documentation exists
Mailing List - one or more e-mail lists exist (where this project can be discussed)
Subversion - project source code is checked into Jasig source code repository
Jira - project level issue tracking exists

Communities of Practice (Benn)

What is a Community of Practice?
- ObWikipedia: A community of practice (CoP) is, according to cognitive anthropologists Jean Lave and Etienne Wenger, a group of people who share an interest, a craft, and/or a profession. The group can evolve naturally because of the members' common interest in a particular domain or area, or it can be created specifically with the goal of gaining knowledge related to their field. It is through the process of sharing information and experiences with the group that the members learn from each other, and have an opportunity to develop themselves personally and professionally (Lave & Wenger 1991).
- Jasig: A non-project group assembled to share information within and advance the state of a specific domain. A CoP will not write code, other than perhaps some proof of concept or reference work.
Current Jasig COPs
- 2-3-98: The 2-3-98 Project provides support for college and university administrators, managers, and practitioners wishing to take advantage of both openness - as an organizational and operational orientation - and open initiatives, in order to reduce costs and increase choice.
- FIFER: The FIFER (Free IDM Framework for Education & Research) initiative is intended to advance the development and adoption of open source identity management software for higher education. This initiative is a direct result of conversations among identity management architects, application developers, and campus technologists who have identified a need for increased availability and promotion of affordable, sustainable, and suitable identity solutions for their campuses.
  - Also, FIFER-API
Incubation Process
- Somewhat lighter weight than for projects, owing largely to lack of issues around maintenance of code.

What's Incubating? (Tim)

Jen - uMobile if she is in the room
Pete Boyson - 5 minutes on ThinkSpace
Andy - Deployer portlet
Marvin - .NET CAS client
Anthony - Newsreader
Benn OR or Jeremy

What's New?