John Lewis presents on open sourcing projects with Jasig. He discusses open source licensing options and intellectual property management best practices. Jasig offers infrastructure, community support, and an incubation process to help projects implement these practices and build sustainable open source communities.

1. Open Source Your Project (With Jasig) John A. Lewis Chief Software Architect Unicon, Inc. Jasig 2010 Conference 9 March 2010 © Copyright Unicon, Inc., 2010. Some rights reserved. This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/

3. Open Source Licensing

4. Intellectual Property Management

5. Building Community

6. What Does Jasig Offer?

7. What Is Open Source?

9. Open Source Software (OSS)

10. Free/Open Source Software (FOSS)

13. Think Free as in “Free Speech”

14. Not (necessarily) Free as in “Free Beer”

16. Grew out of GNU community

17. Promoters of GNU Public License (GPL)

19. Grew out of disagreements with GNU/FSF

20. Less dogmatic / more practical

21. Approves Licenses as “Open Source”

23. Open Source Definition (OSI) 1. Free Redistribution 2. Source Code 3. Derived Works 4. Integrity of The Author's Source Code 5. No Discrimination Against Persons or Groups 6. No Discrimination Against Fields of Endeavor 7. Distribution of License 8. License Must Not Be Specific to a Product 9. License Must Not Restrict Other Software 10. License Must Be Technology-Neutral

24. Open Source Licensing

27. Contribute to public domain (“no rights reserved”)

31. There is no requirement for copyleft in “Free Software” or “Open Source” – Copyleft is a separate concern

33. How far the copyleft requirements reach (e.g. source files, compiled together, dynamic linking)

36. If other software cannot be licensed under the GPL then they are incompatible and cannot be combined

38. Strong copyleft that defines “derivative work” as anything that runs in the scope of the process (including dynamic linking)

39. Lesser GNU Public License (LGPL) has weaker copyleft that applies only to source code compiled together into binary (e.g. libraries)

40. Affero GNU Public License (AGPL) has extended definition to trigger copyleft on network usage (e.g. web sites)

42. No copyleft provisions (does require preservation of copyrights and disclaimers)

43. Compatible with GPLv3, but not w/ GPLv2

44. 2nd most popular FOSS license

45. Used by projects that want comprehensive license without copyleft

49. Easy to read and understand

50. Doesn't address patents or trademarks

51. Lacks language legal advisers prefer

53. Weaker copyleft than LGPL (applies to individual source code files only)

54. Incompatible with the GPL (due to minor but complex restrictions)

56. Common Public Attribution License (CPAL) : requires “attribution” of original developer – usually large logo / splash screen (“Badgeware”)

59. LGPL: weak Copyleft

60. GPL: strong Copyleft

61. AGPL: strong Copyleft that covers SaaS

62. Intellectual Property Management

64. Project with multiple contributing people/organizations may have multiple copyright holders

65. Cannot tell by looking at the license

66. Choice for handling copyrights (Intellectual Property Policy) is separate from License

69. Can be joint assignment or sole assignment w/ broad grant-back copyright license

70. Include a patent license to avoid interference with contributed code

74. Nice compromise, less extreme

75. Used by Apache Software Foundation for all of its projects

78. Two year effort by Mozilla project to relicense code from 450 contributors

84. FSFE FLA for copyright assignment

85. Sun CLA for joint copyright assignment

88. copy of all relevant license files

90. Ensure headers are maintained and audited

91. Document contributor policy on website and provide the CLA for download

92. Building Community

94. Issue Tracking

95. Wiki

96. Continuous Integration

97. Code Review

99. Wikis / Blogs

100. IRC Channel

101. Conference Calls

102. Project Coordination

103. Meetups / User Groups

104. Conference

107. Screenshots

108. Demo Video

109. Demo Site

110. Easy Download

111. Easy Install

113. Responsive Forums

114. Case Studies

115. Regular News

116. Press Releases

117. Sustainability Plan

118. What Does Jasig Offer?

120. Duly elected Board Of Directors

121. Full-time Executive Director

122. Project Steering Committees

123. Large Existing Institutional Membership

124. Solid Financial Performance

125. General Administration & Logistics

126. A Cool Logo!

128. License under Apache License, version 2.0

129. Specific Guidelines Implementing Licensing

130. Jasig Contributor Agreements

131. Logistics for Records Management

133. Full Incubation Process Flow

135. Community & Project Governance

138. Subversion for Source Control

139. JIRA for Issue Tracking

140. Confluence for Wiki

141. Lyris for Mailing Lists

142. Moving to JIRA Studio (sometime soon)

144. Annual Conference and “Unconference”

145. Network Effect, Cross Pollination

146. Related Projects

147. Extended Relationship to other Communities (Kuali, Apache, Sakai, Fluid, Duraspace, etc.)

149. http://www.jasig.org/about

150. http://www.jasig.org/licensing

151. http://www.jasig.org/jasig-project-incubation

152. Questions & Answers John A. Lewis Chief Software Architect Unicon, Inc. [email_address] www.unicon.net