Re: [VOTE] Accept Apache Streams as an Incubator Project
+1 Sander On Wed, Nov 14, 2012 at 3:24 PM, Ross Gardler rgard...@opendirective.comwrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Wookie podling from the incubator
+1 Sander On Fri, Oct 26, 2012 at 2:43 AM, Suresh Marru sma...@apache.org wrote: + 1, all the best as a TLP. Updates to the resolution as Jukka suggested: X. Establish the Apache Wookie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an implementation of the W3C Widgets family of specifications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Wookie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Wookie Project be and hereby is responsible for the creation and maintenance of software related to implementation of the W3C Widgets family of specifications; and be it further RESOLVED, that the office of Vice President, Apache Wookie be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Wookie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Wookie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Wookie Project: * Scott Wilsonscot...@apache.org * Ate Douma a...@apache.org * Ross Gardlerrgard...@apache.org * Matt Franklin mfrank...@apache.org * Paul Sharples psharp...@apache.org * Kris Popat krispo...@apache.org * Raido Kuli ra...@apache.org * Hoang Minh Tien h...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Scott Wilson be appointed to the office of Vice President, Apache Wookie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Wookie PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Wookie Project; and be it further RESOLVED, that the Apache Wookie Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Wookie podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Wookie podling encumbered upon the Apache Incubator Project are hereafter discharged. On Oct 24, 2012, at 2:32 PM, Scott Wilson scott.bradley.wil...@gmail.com wrote: This is a call for vote to graduate the Wookie podling from Apache Incubator. Wookie entered the Incubator in July of 2009. During incubation, Wookie has: * Produced 5 releases * Added 3 new Committer/PPMC members * Cleared IP on all donations * Learned to self-govern and engage the community * Received and applied multiple community patches The Wookie community has voted to proceed with graduation [1] and the result can be found at [2]. Please VOTE on the resolution below: [ ] +1 Graduate Wookie from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate Wookie from the Incubator because.. This vote will be open for at least 72 hours. [1] http://markmail.org/message/jcgdcacn535jqwqy [2] http://markmail.org/message/hp2bggjhec7vpdch == X. Establish the Apache Wookie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to an implementation of the W3C Widgets family of specifications for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Wookie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Wookie Project be and hereby is responsible for the creation and maintenance of software related to implementation of the W3C Widgets family of specifications; and be it further RESOLVED, that the office of Vice President, Apache Wookie be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Wookie Project, and to have primary responsibility for management
RE: [VOTE] [PROPOSAL] Allura to enter the Incubator
+1 (non-binding) Sander OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk -Original Message- From: Rich Bowen [mailto:rbo...@rcbowen.com] Sent: 21 June 2012 17:35 To: general@incubator.apache.org Subject: [VOTE] [PROPOSAL] Allura to enter the Incubator Hi, We are proposing Allura to be admitted to the Apache Incubator, and would like to request that the IPMC votes on this issue. The requisite 72 hours has passed since the initial proposal. The proposal may be found at http://wiki.apache.org/incubator/AlluraProposal Please cast your vote. [ ] +1 I recommend that Allura becomes an Apache Incubator project [ ] 0 Abstain or don't care [ ] -1 No, I do not recommend that Allura becomes an Apache Incubator project yet (because ...) -- Rich Bowen rbo...@rcbowen.com :: @rbowen rbo...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] CloudStack for Apache Incubator
+1 (non-binding) Sander OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk -Original Message- From: Kevin Kluge [mailto:kevin.kl...@citrix.com] Sent: 10 April 2012 02:32 To: general@incubator.apache.org Subject: [VOTE] CloudStack for Apache Incubator Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. The proposal is available at [1] and I have also included it below. Please vote with: +1: accept CloudStack into Incubator +0: don't care -1: do not accept CloudStack into Incubator (please explain the objection) The vote is open for at least 72 hours from now (until at least 19:00 US-PST on April 12, 2012). Thanks for the consideration. -kevin [1] http://wiki.apache.org/incubator/CloudStackProposal Abstract CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration platform. Proposal CloudStack provides control plane software that can be used to create an IaaS cloud. It includes an HTTP-based API for user and administrator functions and a web UI for user and administrator access. Administrators can provision physical infrastructure (e.g., servers, network elements, storage) into an instance of CloudStack, while end users can use the CloudStack self-service API and UI for the provisioning and management of virtual machines, virtual disks, and virtual networks. Citrix Systems, Inc. submits this proposal to donate the CloudStack source code, documentation, websites, and trademarks to the Apache Software Foundation (ASF). Background Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual machines to end users. CloudStack additionally provides baremetal OS installation to end users via a self-service interface. The management of physical resources to provide the larger goal of cloud service delivery is known as orchestration. IaaS clouds are usually described as elastic -- an elastic service is one that allows its user to rapidly scale up or down their need for resources. A number of open source projects and companies have been created to implement IaaS clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General Public License version 3 (GPL v3) in 2010. Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache License v2 in April, 2012. Rationale IaaS clouds provide the ability to implement datacenter operations in a programmable fashion. This functionality is tremendously powerful and benefits the community by providing: - More efficient use of datacenter personnel - More efficient use of datacenter hardware - Better responsiveness to user requests - Better uptime/availability through automation While there are several open source IaaS efforts today, none are governed by an independent foundation such as ASF. Vendor influence and/or proprietary implementations may limit the community's ability to choose the hardware and software for use in the datacenter. The community at large will benefit from the ability to enhance the orchestration layer as needed for particular hardware or software support, and to implement algorithms and features that may reduce cost or increase user satisfaction for specific use cases. In this respect the independent nature of the ASF is key to the long term health and success of the project. Initial Goals The CloudStack project has two initial goals after the proposal is accepted and the incubation has begun. The Cloudstack Project's first goal is to ensure that the CloudStack source includes only third party code that is licensed under the Apache License or open source licenses that are approved by the ASF for use in ASF projects. The CloudStack Project has begun the process of removing third party code that is not licensed under an ASF approved license. This is an ongoing process that will continue into the incubation period. Third party code contributed to CloudStack under the CloudStack contribution agreement was assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack project has begun the process of amending the previous CloudStack contribution agreements to obtain consent from existing contributors to change the CloudStack project's license. In the event that an existing contributor does not consent to this change, the project is prepared to remove that contributor's code. Additionally, there are binary dependencies on redistributed libraries that are not provided with an ASF-approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal. Although
RE: IP Clearance - transferral or licensing of copyright ownership?
From: Robert Burrell Donkin [mailto:robertburrelldon...@gmail.com] Sent: 22 September 2011 11:20 To: general@incubator.apache.org Subject: Re: IP Clearance - transferral or licensing of copyright ownership? Hi Sander Hi Robert, Many thanks for your detailed reply, that's been very helpful. snip On the other hand, the ASF general FAQ states that the copyright of ASF projects is owned by the ASF, more specifically The members own the code [5]. It is the collective copyright that is owned by Apache Projects are composed by a selection process undertaken by the PMC from a variety of contributions. Each contributor owns the copyright in their patch but the creative act of composition entitles Apache to claim collective copyright for the final work. This collective copyright claim is noted in the NOTICE. The header for each document should acknowledge that Apache has licensed (from the original contributions) the rights required to offer the document to the public under the Apache License, Version 2 but almost always will not contain a copyright claim. I think it's mostly the distinction between copyright on the individual contributions and the 'collective copyright' which was the missing piece in my puzzle. :) snip The documentation needs improvement in this area. I'd be glad to review patches and work with anyone would could find some cycles to contribute. Anyone want to start by diving in with suggestions? I'll try to come up with some initial suggestions for the resources I've consulted following your explanation. Sander Robert [1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
IP Clearance - transferral or licensing of copyright ownership?
I'm trying to get my head around the IP clearance process and specifically about what happens to the copyright ownership during that process. Although IP clearance gets discussed once in a while on this list I couldn't find a clear answer in the archives on this specific point. When a project with a pre-existing code base joins the incubator, does the copyright of that code base get transferred to the ASF or will it be licensed to the ASF? Reading through the IP clearance guide [1], it mentions the Software Grant Agreement (SGA) and going to the text [2] it states that it is a License Agreement to grant a license to the ASF. Also the CCLA [3] and the ICLA [4] are license agreements. I interpret that to mean that the copyright ownership remains with the licensor and only a license is granted. On the other hand, the ASF general FAQ states that the copyright of ASF projects is owned by the ASF, more specifically The members own the code [5]. Also the IP Clearance template [6] has a check that says Check and make sure that the papers that transfer rights to the ASF been received. But it seems that the SGA and *CLAs are just license agreements and don't include a transferral of rights? I must be missing something obvious here but I'm not sure what. Going through a few NOTICE files of projects doesn't really make it clearer, because some only specify the ASF as copyright owner and others specify in general terms that it includes software [originally] developed at X. I know copyright ownership might not be a big deal to many here, but we are dealing with many open source projects where the project lead has a very strong sense of ownership over the code. Besides educating them about the issues I want to make sure I get the facts right. Sander [1] http://incubator.apache.org/guides/mentor.html#initial-ip-clearance [2] http://www.apache.org/licenses/software-grant.txt [3] http://www.apache.org/licenses/cla-corporate.txt [4] http://www.apache.org/licenses/icla.txt [5] http://www.apache.org/foundation/faq.html#who-owns-apache-code [6] http://incubator.apache.org/ip-clearance/ip-clearance-template.html OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept OpenOffice.org for incubation
Please cast your votes: [ ] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation +1 (non-binding) Sander - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
