OpenNTF.org IP Resolutions For Steering Committee Meeting 2009 07 16
Upcoming SlideShare
Loading in...5
×
 

OpenNTF.org IP Resolutions For Steering Committee Meeting 2009 07 16

on

  • 1,868 views

These are the proposed resolutions for OpenNTF.org. They will be brought for vote during the July 16th, 2009 Steering Committee Conference Call

These are the proposed resolutions for OpenNTF.org. They will be brought for vote during the July 16th, 2009 Steering Committee Conference Call

Statistics

Views

Total Views
1,868
Views on SlideShare
1,569
Embed Views
299

Actions

Likes
0
Downloads
2
Comments
0

7 Embeds 299

http://www.openntf.org 213
http://www.johndavidhead.com 56
http://openntf.org 23
http://blog.openntf.org 3
http://www.edbrill.com 2
http://www.slideshare.net 1
http://www.sogou.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

OpenNTF.org IP Resolutions For Steering Committee Meeting 2009 07 16 OpenNTF.org IP Resolutions For Steering Committee Meeting 2009 07 16 Presentation Transcript

  • OpenNTF Alliance IP Working Group Resolutions for Steering Committee Consideration, July 16, 2009
  • IP Resolutions • IP resolutions are in several categories: – Licensing Model – Process issues – Requests to Technical Committee to implement infrastructure support 2
  • IP Resolutions Licensing Model 3 View slide
  • Resolution #1 – Project Repository Licenses • That OpenNTF Project Repository should use the following licenses: – Apache License Version 2 • Contributors should execute Individual Contributor License Agreements (based on Apache's text) • Corporate Contribution License Agreements to cover contributions by employees (based on Apache's text) • Use of the Apache process of applying license – with the exception that OpenNTF contributors may maintain their own copyrights • May include content licensed under an Apache- compatible license (as determined by the Apache Software Foundation http://www.apache.org/legal/resolved.html or the OpenNTF IP Manager). 4 View slide
  • Resolution #1 – Project Repository Licenses (cont) • That OpenNTF Project Repository should use the following licenses: – GPL3 – LGPL3 – Affero GPL3 _________________________________________________________ 5
  • Resolution #2 – Release Catalog Repository Licenses • That OpenNTF should provide two Release Catalogs – One Catalog for the Apache License Version 2 approved releases – Second Catalog for the GPL Licenses (GPL3, LGPL3, Affero GPL3) – The Catalogs will be of same functionality, with the same workflow process but separate workflow queues – Both Catalogs will receive equal promotion on OpenNTF.org, including the following areas: • Site Navigation • OpenNTF.org Blog • Any promotion done by THE OPENNTF.ORG ALLIANCE _________________________________________________________ 6
  • Resolution #3 – Membership Agreement That the IP Manager create a draft edited version of the Membership Agreement that: – Permits Contributors as well as Committers to be part of the Technical Committee – Removes inconsistencies between the Membership Agreement that the Licensing Policy _________________________________________________________ • The IP Policy would describe the policy under which contributions are made, rather than act as the license itself. • Specifically, contributions from Member employees would be covered by ICLAs or a CCLA rather than by the text of the IP Policy. 7
  • Resolution #4 – IP Manager Role That the IP Manager Role be broken into the following roles: IP Manager – Site Governance IP Manager – Apache IP Manager – GPL That the IP Manager will provide legal guidance for the specified license type and release catalog. That Peter Tanner, IBM, be named IP Manager – Site Governance and IP Manager – Apache. That OpenNTF.org solicit an IP Manager – GPL, who has a legal background in Intellectual Property or an individual with experience in Open Source Intellectural Property matters. _________________________________________________________ • 8
  • Resolution #5 – Documentation That the IP Manager create a new description of the Contribution Process based on the Resolutions passed at this July 16, 2009 Steering Committee meeting. That the IP Manager develop the documentation and process for a contributor to submit themselves to be a Committer That the IP Manager develop legal language that an OpenNTF.org user can include on their website or blog that allows for one of the approved OpenNTF.org licenses and specifies how code and samples can be reused _________________________________________________________ • 9
  • IP Resolutions Process Issues 10
  • Resolution #6 – Dual Repository That a dual repository approach, as discussed during the IP WG meeting of June 19, 2009 and further discussed in the IP WG Forum, by implemented, and that the website and contribution documents be amended appropriately. _________________________________________________________ The two repositories are: 1. The Project Repository, in which Contributors may post their contributions/projects. This would be the working area and will be presented with standard public contribution disclaimers that all content is owned by the author Repository is defined as the NSF that houses source code as attachments and associated meta- information in a single Domino database 2. The Release Catalogs (two), one for each License type, in which projects may be released after they have been through the release process (Committer Checklist). 11
  • Resolution #7 – Committers That a Committer process be set up for both Release Catalogs and where a Committer can not approve both Apache and GPL license projects. All documentation and site services for committers will be duplicated for each release catalog _________________________________________________________ 12
  • Resolution #8 – Committer Approval That a Project Release must be approved by a Committer other than the original Contributor/Committer as part of the Managed Repository release process. _________________________________________________________ • This is to ensure that a second set of eyes verify that the Committer Checklist has been completed 13
  • IP Resolutions Requests to Technical Committee to implement infrastructure support – 14
  • Resolution #9 – Release Catalogs Creation That the Technical Committee create two Release Catalogs. These repository will only allowed cleared releases by a Committer. An automated workflow process would facilitate this process to be as automatic as possible. Each license type will receive it's own Release Catalog of equal functionality. Based on the License Type selected in a project, approved releases of will be directed to the Release Catalog of that License Type. The Release Catalogs will be based on the current Catalog design. The user interface will focus on the consumers of the releases _________________________________________________________ 15
  • Resolution #10 – Project License Modifications That the Technical Committee modify the Project Release form to allow for the following licenses: GNU GPL3 GNU LGPL 3 GNU Affero GPL3 Apache License _________________________________________________________ 16
  • Resolution #11 – Code Bin License Modifications That the Technical Committee modify the Code Bin submission form to allow for the following licenses: Academic Free License GNU GPL3 GNU LGPL 3 GNU Affero GPL3 Apache License Eclipse Public License -v 1.0 _________________________________________________________ 17
  • Resolution #12 – User Status Fields That the Technical Committee implement Status fields for the User Profile. This field will be editable only by the IP Manager. The IP Manager would set the Status Fields based on the agreements that the User and/or his/her employer have executed. _________________________________________________________ • These fields would include fields for the following – depending on the final IP model that OpenNTF chooses: – Employer Copyright Waiver – Individual Copyright License Agreement – Corporate Copyright License Agreement – Membership Agreement (ie is User employed by Member). – License Type Filter (listing of all license types on the Project, this filters what is seen by the logged in user in the Project Repository and which Release Catalogs are displayed). Default is set to “All” 18
  • Resolution #13 – Project Properties That the Technical Committee implement the following new properties on a Project, editable by the Project Owner: – Who can create project releases? • Project Owner Only, Specified Users – Who can submit major releases (1.0) to the Release Catalog? • Project Owner Only, Specified Users – Who can submit minor updates (1.X) to the Release Catalog? • Project Owner Only, Specified Users – 19
  • Resolution #14 – Adding Contributors to Projects That the Technical Committee implement a feature to allow a Project Chef to only allow Project Contributors who meet the conditions of being a Contributor. _________________________________________________________ • This will require that the potential Contributor has an Employer Waiver or has signed an ICLA depending on the IP Model to be followed. 20
  • Resolution #15 – Release Request • That the Technical Committee modify the Project Release process to allow the Project Owner or the named delgates to submit a Release for Committer Approval. This process will determine which License Type is selected for the project (Apache or GPL) and direct the workflow request to the proper queue. _________________________________________________________ 21
  • Resolution #16 – License Filter for Projects & Releases • That the Technical Committee modify the Project Repository to display only projects that meet the License Type filter on the User Profile • That the Technical Committee modify the Catalog link to only display the appropriate Release Catalogs to meet the License Type filter on the User Profile • That the Technical Committee will create vanity URL's for each Release Catalog for direct access 22
  • Resolution #17 – IP Documentation Repository That the Technical Committee will create a repository for Company Membership, Individual Membership, Contribution Agreements, Committer Submissions, and Employee Copyright Waiver paperwork. This repository would be accessible by the Steering committee and editable by the IP Manager(s) _________________________________________________________ • This currently being handled through the IP Manager Notes Mail repository. 23
  • Resolution #18 – Third Party License Agreement • Direct the IP Manager – Governance to create a Third Party License Agreement that allows third parties to donate their licensed code and/or products and provide protection of their copyright. 24
  • Resolution #19 – Technical Committee Membership • That the membership of the Technical Committee be changed to allow for any OpenNTF.org registered user who signs the ICLA. 25