Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
== Initial Committers == || '''Name''' || '''Email''' || '''Affiliation''' || '''iCLA''' || || Paul Fremantle || p...@apache.org || Individual, wso2.com || yes || || Jonathan Marsh || jonat...@wso2.com || Individual, wso2.com || || || Peter Linnell || plinn...@apache.org || Individual, suse.com || || || Afkham Azeez || az...@apache.org || Individual wso2.com || yes || || Lakmal Warusawithana || lak...@wso2.com || Individual wso2.com || || || Damitha Kumarage || dami...@apache.org || Individual wso2.com || yes || || Samisa Abeysinghe || sam...@apache.org || Individual wso2.com || yes || || Nirmal Fernando || nirmal070...@apache.org || Individual wso2.com || yes || || Sajith Kariyawasam || saj...@wso2.com || Individual wso2.com || || || Lahiru Sandaruwan || lahi...@wso2.com || Individual wso2.com || || || Isuru Haththotuwa || isu...@wso2.com || Individual wso2.com || || || Madhura Peiris || madh...@wso2.com || Individual wso2.com || || || Mariangela Hills || mariang...@wso2.com || Individual wso2.com || || || Marlon Pierce || mpie...@apache.org || Individual, Indiana University || yes || || Suresh Marru || sma...@apache.org || Individual, Indiana University || yes || || Amila Jayasekara || ami...@apache.org || Individual, Indiana University || yes || || David Nalley || da...@gnsa.us || Citrix || yes || || Chip Childers || chipchild...@apache.org || SunGard Availability Services || yes || || Joe Brockmeier || j...@apache.org || Individual, Citrix || yes|| || Noah Slater || nsla...@apache.org || Individual, Engine Yard || yes|| || John Kinsella || j...@apache.org || Individual, Stratosec || yes|| || Lahiru Gunathilake || lah...@apache.org || Individual, Indiana University || yes || || Nandana Mihindukulasooriya || nand...@apache.org || Individual, Center for Open Middleware || yes || || Isuru Perera || isu...@wso2.com || Individual, wso2.com || || || Reka Thirunavakurussu || r...@wso2.com || Individual, wso2.com || || || Andrew Hart || ah...@apache.org || Individual, NASA Jet Propulsion Laboratory || yes || == Sponsors == === Champion === Ross Gardler, Apache === Nominated Mentors === 1. Afkham Azeez az...@apache.org (Member) 2. Suresh Marru sma...@apache.org (Member) 3. Marlon Pierce mpie...@apache.org (Member) 4. Chip Childers chipchild...@apache.org (Member) 5. Mohammad Nour mn...@apache.org (Member) 6. Noah Slater nsla...@apache.org (Member) === Sponsoring Entity === The Apache Incubator [1] http://wiki.apache.org/incubator/StratosProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Accept jclouds into the Apache Incubator. On Tue, Apr 23, 2013 at 11:40 AM, Roman Shaposhnik r...@apache.org wrote: On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com
Re: New challenges (Was: NOMINATIONS for Incubator PMC Chair)
+1 for nominating Benson. On Fri, Oct 5, 2012 at 9:04 AM, Matt Hogstrom m...@hogstrom.org wrote: I prefer simple. I'd rather see nominations and votes done via-email with IPMC votes noted as (binding). My +1 for nominating Benson. On Oct 2, 2012, at 10:07 AM, sebb seb...@gmail.com wrote: Indeed, but that might be better done if/when Steve is enhanced to support private (as opposed to secret) votes, as hopefully that would not require the same overhead. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com
Re: [VOTE] Graduate Oozie podling from Apache Incubator
+1 (binding) -- dims On Aug 11, 2012, at 7:14 PM, Steve Loughran steve.lough...@gmail.com wrote: On 10 August 2012 16:12, Alejandro Abdelnur t...@cloudera.com wrote: This is a call for vote to graduate Oozie podling from Apache Incubator. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator +1, binding - 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: Board will be proposing a new TLP
+1 straight to TLP -- dims On Jun 30, 2012, at 7:23 AM, Jim Jagielski j...@jagunet.com wrote: For those not following board@, the board is proposing the creation of a new TLP (tentatively called Apache Steve) which will serve as the project behind our STV and voting tools. The impetus behind this was when I suggested to the OpenStack people to use STV for their voting system, which kind of re-kicked the idea in my head that our voting tools were too good to not provide as releasable code to the world at large. Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... The board would like to recommend to the Incubator that the board simply proceed with the creation of this project at the next board meeting. Thx. - 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] Retire Kato
+1 binding -- dims On Jun 26, 2012, at 7:20 PM, Alan D. Cabrera l...@toolazydogs.com wrote: +1 binding Regards, Alan On Jun 26, 2012, at 4:29 PM, Benson Margulies wrote: Based on the status of this podling as reported in the June board report, I propose that the IPMC retire the Kato podling. I'm not sure how long a vote for this should remain open. here is my +1. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wink status (Was: Shepherds for podling reports)
Jukka, Agree with your and Ant's assessment -- dims On Sun, May 20, 2012 at 5:40 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, May 10, 2012 at 2:37 PM, ant elder ant.el...@gmail.com wrote: So strictly speaking this doesn't seem to meet the documented Incubator graduation requirements. Thanks for the insight! It sounds like Wink should try attracting more active committers or go try graduating into a subproject as discussed. Alternatively, as you say, a viable enough TLP could be formed if enough committed mentors or other IPMC members are willing to step up to provide enough diverse oversight for a standalone Wink PMC. PS. I talked with Steve Loughran about his mentorship in Wink. He's no longer actively involved, so I removed him from the list of Wink mentors. That leaves Wink with Kevan and Davanum as mentors. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - 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 binding -- dims On Apr 10, 2012, at 9:52 AM, Daniel Kulp dk...@apache.org wrote: +1 binding Dan On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote: 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 CloudStack is open source, many design documents and discussions that should have been publicly available and accessible were not
Re: [DISCUSS] Re: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)
+1 to Jukka. Many Many Thanks to Noel for guiding us all these years. On Thu, Feb 9, 2012 at 9:31 PM, Noel J. Bergman n...@devtech.com wrote: Ross Gardler wrote: I'm ready to vote, but Chris said it looks like the remaining folks (including me) that were in the running have aligned beyond the following nominee: Where is the mail from Noel saying he is no longer standing? Have I missed something? There wasn't one. I was traveling when the vote started. No worries. I have no issue with standing down after 8 years, and Jukka is an excellent and active successor. I was exceedingly pleased to see his message that he had reconsidered, was willing to stand as Incubator PMC Chair, and would rotate out of the JackRabbit VP position. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] DeviceMap to join the Apache incubator
* devicemap-commits @ incubator.apache.org * devicemap-private @ incubator.apache.org === Subversion Directory === http://svn.apache.org/repos/incubator/devicemap === Issue Tracking === DMAP project in JIRA. == Sponsors == === Champion === Bertrand Delacretaz === Nominated Mentors === * Sylvain Wallez * Kevan Miller * Bertrand Delacretaz === Sponsoring Entity === Incubator PMC *** DeviceMap proposal ends *** - 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 -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Openmeetings to Apache Incubator
as graphs: Java Web-Start application (Screen-Sharing and Recording) http://openmeetings.googlecode.com/svn-history/r4162/docs/Red5.webstart.png Java Web-Application (http://openmeetings.googlecode.com/svn-history/r4162/docs/Red5.webapp.png ). === Cryptography === OpenMeetings can be deployed using HTTPS and RTMPS (Flash Streaming and Remoting over SSL): http://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS = Required Resources = Subversion Directory: https://svn.apache.org/repos/asf/incubator/openmeetings Issue Tracking: JIRA (OPENMEETINGS) Required Mailing lists: * openmeetings-u...@incubator.apache.org * openmeetings-...@incubator.apache.org * openmeetings-comm...@incubator.apache.org Wiki, Webspace: Confluence or similar software where we can integrate our current wiki and documentation (http://code.google.com/p/openmeetings/wiki/MainPage?tm=6) Other Resources: Continuous integration and Nightly Builds may eventually require hardware We are currently hosted on googlecode. There was an option in googlecode available to transfer a googlecode project to Apache. We would like to ask the hosting staff at Googlecode if they could maybe give us advice how we can easily get a copy of our project to import it into the new project space at Apache. == Initial Committers == * Sebastian Wagner seba.wagner at gmail dot com * Oliver Becherer (smoeker) ich at oliver-becherer dot name * Rodion Volkov volkov.rodion at gmail dot com * Alexei Fedotov aaf at apache dot org * Evgeny Rovinsky e.rovinsky at gmail dot com * Maxim Solodovnik solomax666 at gmail dot com * Sascha Xander sascha.xander at googlemail dot com * Johnny Strom johnny.strom at osp dot fi * Eugen Schwert eugen.schwert at googlemail dot com If any other existing Apache or Openmeetings committers would like to be grandfathered into the list then feel free to ask. = Sponsors = === Champion === * Andrus Adamchik aadamchik at apache dot org === Mentors === Volunteers, please. * Alexei Fedotov aaf at apache dot org * Jim Jagielski jim at apache dot org * Ross Gardler rgardler at apache dot org * Yegor Kozlov yegor at apache dot org === Sponsoring Entity === We would like to ask the Incubator PMC to sponsor Openmeetings. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Deltacloud to TLP
+1 Sent from my iPhone On Oct 18, 2011, at 11:08 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1... Cheers, Chris On Oct 17, 2011, at 7:42 AM, David Lutterkort wrote: Hi all, as described in the discussion thread[1], the Deltacloud community feels that we are ready to graduate to a top-level Apache project. To that end, I'd like to have a vote by the IPMC so that we can put the resolution given below onto the agenda of the next Apache Board meeting. Please vote by Thursday, 2011-10-20, 8am PDT. Since starting incubation in May, 2010, we've made several releases, added contributors, and have the support of our mentors to graduate. Thanks for your consideration, and voting, David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201110.mbox/%3c1318464232.2751.7.ca...@melon.watzmann.net%3e Resolution: === 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 implementing web service API's for interacting with cloud providers, and corresponding client libraries, 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 Deltacloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Deltacloud Project be and hereby is responsible for the creation and maintenance of software related to web service API's for interacting with cloud providers, and corresponding client libraries; and be it further RESOLVED, that the office of Vice President, Deltacloud 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 Deltacloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Deltacloud 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 Deltacloud Project: * Marios Andreou (mar...@apache.org) * Michal Fojtik (mfoj...@apache.org) * Jim Jagielski (j...@apache.org) * Chris Lalancette (clala...@apache.org) * David Lutterkort (lut...@apache.org) * Sang-Min Park (sp...@apache.org) * Carl Trieloff (cctriel...@apache.org) * Eric Woods (wood...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Lutterkort be appointed to the office of Vice President, Deltacloud, 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 Deltacloud Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Deltacloud Project; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Deltacloud podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Deltacloud podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - 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] Accept Apache Callback for incubation
+1 Sent from my iPhone On Oct 11, 2011, at 5:09 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, As discussed, the PhoneGap project would like to enter the Incubator under the Apache Callback name (potential alternative names to be discussed during incubation). The initial proposal has been well received and there are no major open issues, so it's time to vote! Thus I'm now calling a formal VOTE on the Apache Callback proposal as included below. The proposal is also available at http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on the PhoneGap wiki, and I'll place a copy for our archives on the Incubator wiki as soon as it stops giving me internal server errors. Please VOTE: [ ] +1 Accept Apache Callback for incubation [ ] -1 Don't accept Apache Callback for incubation because... This vote is open for the next 72 hours. Everyone is welcome to participate, but only votes from the Incubator PMC members are binding. Thanks! My vote is +1. Best regards, Jukka Zitting Apache Callback Proposal Abstract Apache Callback is a platform for building native mobile applications using HTML, CSS and JavaScript. Proposal Apache Callback allows web developers to natively target Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian and Samsung Bada with a single codebase. The Callback APIs are based on open web standards. The Callback bridge technology enables access to native device capabilities. Utilizing the Callback bridge native plugins allow for any type of native access from the embedded webview. Background -- Apache Callback is the free software evolution of the popular PhoneGap project. PhoneGap evolved from a hack that enabled a FFI (Foreign Function Interface) to an embedded WebView on iOS to a complete suite of tools for tackling parity across many mobile device and desktop platforms. PhoneGap has always focused on two complementary goals. Our first goal, is to see the web as a first class development platform. Not a sandbox without a filesystem but a real first class platform that includes access to the local system apis, sensors and data, in addition to first class tooling such as system debuggers. The second goal of PhoneGap is for the project to cease to exist. This is not a nihilistic sentiment, rather we at the PhoneGap project are providing a reference implementation for web browsers to assist and guide the standardization process of browser APIs. The name and trademark of PhoneGap will become the commercial entity for the project. The source, code, documentation and related assets will all be contributed to the Apache Foundation as Callback. The Callback name comes from the event of the same name that is fired when the FFI bridge is established. Rationale - The dominate window to the web is quickly becoming devices, mostly phones. The manufacturers of devices, creators of mobile operating systems, and authors of web browsers are consolidating. (In many cases these are all already the same company.) Those stakeholders may see a future for the web but their bottom line is not necessarily motivated to participate in an open web. It is especially clear that while many of these platforms have been seeing some level of strategic neglect in favor of enhanced experiences at the price locking developers into their respective platforms. The Callback project exists to bring the focus back to an open and accessible web. Initial Goals - * License all PhoneGap source code and documentation to the Apache Software Foundation. (We already name the Apache license in our CLA.) * Setup and standardize the open governance of the Callback project. * Rename all assets from PhoneGap to Callback in project src, docs, tests and related infrastructure. Current Status -- Callback is a mature software project recently shipping 1.0 on July 29, 2011. Meritocracy --- Callback has always been a project driven by merit and, in a sense, our solution is brute force requiring many collaborating developers to solve our goals. It would be far easier, and perhaps more correct, for the Callback project to port a single web browser codebase, and API bindings, across platforms but our executable size would be appreciably larger, unacceptably so for mobile, and our target abstraction would be only tertiary to maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in
Re: [VOTE] release deltacloud 0.4.1, rc1
+1 from me. On Tue, Oct 4, 2011 at 1:00 PM, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded the first release candidate for Deltacloud 0.4.1. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.1/rc1/ Please vote on the release candidate by Saturday, 2011-10-07 15:00 PDT KEYS: http://www.apache.org/dist/incubator/deltacloud/KEYS svn tag: https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.1-rc1 This release is mostly a bug fix release. It also adds support for the Google Storage API. Detailed list of changes: * change how dependencies are managed: canonical deps are now in the gemspecs Server: * clarify how user_data injection should work; make sure all drivers accept base64 encoded data and make the decoded version available to instance * fix URL generation so that server works when run behind a reverse proxy * init script: honor defaults from sysconfig file * init script: fix 'status', properly background deltacloudd * deltacloudd: support verbose option * Drivers: + Condor - use UUIDTools instead of UUID to simplify deps + Google - new driver for Google storage API + RHEV-M - treat status as case-insensitive - inject data through a virtual floppy rather than modifying the instance storage directly + vSphere - report minimum of max memory across all hosts in a data center, so that instances can be placed on any host - user_data is placed in file 'deltacloud-user-data.txt' Client: * fix parsing of enums in HWP properties * fix handling of float value for number of vCPU in HWP I will update the website and docs to reflect those changes in time for the official release. David -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
benefits for both the ASF and the project in adopting the brand to better reach the community = Documentation = 1. [[https://github.com/raffaeleguidi/DirectMemory|The original DirectMemory HomePage]] 2. [[https://github.com/raffaeleguidi/DirectMemory/wiki|The original DirectMemory Wiki]] 3. [[https://github.com/raffaeleguidi/DirectMemory/issues|The DirectMemory Issue Tracker (used also for enhancements, feature requests and discussion)]] = Initial Source = The intial source comprises code developed on [[https://github.com/raffaeleguidi/DirectMemory/|GitHub]] contributed under Grant from Raffaele P. Guidi for Directmemory. = Source and Intellectual Property Submission Plan = Source code will be moved from [[https://github.com/raffaeleguidi/DirectMemory/|GitHub]] space inside the SVN space of the podling. = External Dependencies = * Google Guava collections - http://code.google.com/p/guava-libraries/ - Apache License V2.0 * Protostuff - http://code.google.com/p/protostuff/ - Apache License V2.0 * JoSQL - http://josql.sourceforge.net/ - Apache License V2.0 * AspectJ - http://www.eclipse.org/org/ - Eclipse Public License (Category B, used only in binary form) * SLF4J - http://www.slf4j.org/ - MIT License (Category A) * Logback - http://logback.qos.ch/ - dual licensed under EPL v1.0 and LGPL 2.1 (Category B, but not really a dependency as it is astracted by the SLF4j facade) '''Build/Test time dependencies''' * Maven - http://maven.apache.org/ - Apache License V2.0 * JUnit - http://www.junit.org/ - CPL License v1.0 - (Category B, used only in binary form) * JUnit Benchmarks - http://labs.carrotsearch.com/junit-benchmarks.html - Apache License V2.0 = Cryptography = The project does not handle cryptography in any way. = Required Resources = * Mailing lists * directmemory-private (with moderated subscriptions) * directmemory-dev * directmemory-user * directmemory-commits * Subversion directory * https://svn.apache.org/repos/asf/incubator/directmemory * Website * Wiki (!DirectMemory) * Issue Tracking * JIRA (!DirectMemory) = Initial Committers = Names of initial committers - in alphabetical order - with current ASF status: * Christian Grobmeier grobmeier at apache dot org (ASF Member) * Ioannis Canellos iocanel at apache dor org (ASF Committer) * Maurizio Cucchiara mcucchiara at apache dot org (ASF Committer) * Olivier Lamy olamy at apache dot org (ASF Member) * Raffaele P. Guidi raffaele dot p dot guidi at gmail dot com (ICLA Signed) * Simone Gianni simoneg at apache dot org (ASF Member) * Simone Tripodi simonetripodi at apache dot org (ASF Member) * Tommaso Teofili tommaso at apache dot org (ASF Member) = Sponsors = == Champion == * Christian Grobmeier grobmeier at apache dot org == Nominated Mentors == * Anthony Elder antelder at apache dor org * Christian Grobmeier grobmeier at apache dot org * Olivier Lamy olamy at apache dot org * Sylvain Wallez sylvain at apache dot org * Tim Williams twilliams at apache dot org == Sponsoring Entity == * The Apache Incubator = Other interested people (in alphabetical order) = * TBD - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new accounts
https://id.apache.org/acreq/ - yes. On Tue, Sep 27, 2011 at 3:42 PM, Benson Margulies bimargul...@gmail.com wrote: Apologies to all, but my memory is leaky and my google skills faulty. I've got a podling's worth of accounts to create. Do I use the 'member' link on the new submission form for this purpose? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Accumulo incubator proposal: Statement of Concern
Folks, A bit of back story of a slightly similar situation before. We have had Axis/Axis2 projects in Apache for a long time and along came the XFire proposal (http://wiki.apache.org/incubator/CeltiXfireProposal) and we had the same kind of discussions as i see here. Flash forward, Both Axis2 and CXF are flourishing, there are folks who are working on components that get used by both projects like XmlSchema and WSS4J. So my 2 cents, take a deep breath and think of ways to collaborate even if it means 2 code bases with some common code, it does not have to be one code base for one situation/scenario. Do reach out to each other, hang out on each others mailing lists to make that collaboration happen. thanks, dims On Wed, Sep 7, 2011 at 4:14 PM, Stack st...@duboce.net wrote: On Wed, Sep 7, 2011 at 12:47 PM, Billie J Rinaldi billie.j.rina...@ugov.gov wrote: On Wednesday, September 7, 2011 1:34:20 PM, Stack st...@duboce.net wrote: I agree w/ Doug that 'unlikely to' is not a correct characterization. Would the following alteration be more accurate? It may be possible to incorporate the desired features of Accumulo into HBase. However, the amount of work required at the current time would slow development of HBase and Accumulo considerably. From my perspective, that is more the case though your second sentence above comes across as a setup for our not integrating. But rumor has it though that the differences while small looking when described in a short incubator proposal, in implementation, the code is very different making an integration project, unfortunately, a piece of work. Yes, the implementation is very different, and we had difficulty capturing that in the proposal. Understood. hbase TRUNK coprocessors seem to be a more generic Iterator facility Some types of functions (e.g. query-time aggregation) can be implemented in both coprocessors and iterators, but coprocessors will not easily support the entirety of iterator functionality. Nor is the reverse true. The two models present different programming mechanisms for server-side processing. It would be useful to have both in the same project. I'll take your word for it not having seen the code. St.Ack - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Accumulo incubator proposal: Statement of Concern
Sounds great! -- dims On Wed, Sep 7, 2011 at 5:21 PM, Billie J Rinaldi billie.j.rina...@ugov.gov wrote: On Wednesday, September 7, 2011 4:14:26 PM, Stack st...@duboce.net wrote: From my perspective, that is more the case though your second sentence above comes across as a setup for our not integrating. How about this? It may be possible to incorporate the desired features of Accumulo into HBase. However, the amount of work required would slow development of HBase and Accumulo considerably. We believe this warrants a podling for Accumulo at the current time. We expect active cross-pollination will occur between HBase and podling Accumulo and it is possible that the codebases and projects will ultimately converge. Billie - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - 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
[X] +1 Accept OpenOffice.org for incubation (binding) On Fri, Jun 10, 2011 at 12:20 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 6/10/2011 11:02 AM, Sam Ruby wrote: Please cast your votes: [ ] +1 Accept OpenOffice.org for incubation +1 [binding] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Accept OpenOffice.org for incubation
Simon, Anyone interested can VOTE. If u see some of the votes they have (binding) in the text, those are from folks on the incubator pmc. Ultimately if we see a whole bunch of -1's then we check which way the pmc voted to decide if the proposal was accepted or not. So please go ahead and vote to register your view. -- dims On Fri, Jun 10, 2011 at 12:45 PM, Simon Phipps si...@webmink.com wrote: For us outsiders, can you explain who is allowed to vote and in what way, please? S. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Accept OpenOffice.org for incubation
binding is used by members of the incubator pmc [1] -- dims [1] http://people.apache.org/committers-by-project.html#incubator-pmc On Fri, Jun 10, 2011 at 12:50 PM, Ian Lynch ianrly...@gmail.com wrote: Sorry for ignorance but what does binding - non-binding mean? -- Ian Ofqual Accredited IT Qualifications (The Schools ITQ) www.theINGOTs.org +44 (0)1827 305940 The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Accept OpenOffice.org for incubation
Counters typically check the names against the pmc roster, so it's ok -- dims On 06/10/2011 01:38 PM, Christian Grobmeier wrote: Yes, me too. On Fri, Jun 10, 2011 at 7:17 PM, Benson Margulies bimargul...@gmail.com wrote: I forgot to add (binding) to my +1, but I don't think I'm alone. On Fri, Jun 10, 2011 at 1:12 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 6/10/2011 12:04 PM, Sanjiva Weerawarana wrote: (Officially I'm on the incubator PMC I believe but I have not been active .. so lets chalk this up for non-binding.) Then you just cast a binding vote. Feel free to change it, or withdraw it, but the committee roster determines which binds. Not active ... in the past week? month? year? ever? That simply does not matter and vote counters don't apply such a metric :) - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Corporate Contribution [Blondie's Parallel Lines...]
Steve, In the interest of completeness, please point out that folks from IBM did join and work on Axis2 which was a complete rewrite from scratch, got that integrated into other Apache projects like Geronimo. thanks, dims On Tue, Jun 7, 2011 at 9:27 AM, Steve Loughran ste...@apache.org wrote: On 06/03/2011 03:58 AM, Sam Ruby wrote: On Thu, Jun 2, 2011 at 10:24 PM,robert_w...@us.ibm.com wrote: Corporate assignments are notorious at the ASF for disappearing communities. Sometimes, there is momentum to keep going, often times there is not. Communities are based on individuals. And individuals are often employed by corporations, and are their jobs sometimes entail contributing to open source communities. I think we all understand how this works. But do you have any hard numbers, for example, showing a higher abandonment rate for projects with more corporate assignments? That would be an interesting correlation to show. Of course, we must also consider the projects that never came into existence at all, for lack of corporate sponsorship. That number is harder to estimate. I can confirm that is is a common enough phenomenon to warrant highlighting in the standard template: http://incubator.apache.org/guides/proposal.html#template-reliance-on-salaried-developers And just because corporate withdrawals are notorious does not mean they are common, or that they are the greatest risk we should consider. The Boston Strangler and Jack the Ripper were also notorious, but you have a great risk of death falling down stairs. The issue with corporate reassignments is that everyone just vanishes. They get reassigned, and go away. In OSS, individuals tend to drift off, go onto what else interests them, or whatever. The turnover/year may be the same, but the way the turnover happens is different. to make things worse, because the paid FTEs tend to work full time on the projects, they understand the code well, gain committers status through their contributions, and so when they go, a big chunk of the active knowledge goes along with their departure Examples Axis 1.x: IBM staffers all vanish. Harmony: IBM FTEs all vanish. I don't think we need any more, given that these show that IBM has a track record of doing this. Maybe not your bit of the company, but we outsiders can't tell that - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice
fwiw, Bob Sutor is not a committer or on the incubator PMC or a member of the ASF [1]. Here's the list of folks on the incubator PMC who will vote on the proposal [2] [1] http://people.apache.org/committer-index.html [2] http://people.apache.org/committers-by-project.html#incubator-pmc On Mon, Jun 6, 2011 at 12:36 PM, Greg Stein gst...@gmail.com wrote: On Mon, Jun 6, 2011 at 12:17, Florian Effenberger flo...@documentfoundation.org wrote: Hi Jim, Jim Jagielski wrote on 2011-06-06 18.06: The reality is that IBM employees wearing their IBM hats, have made it crystal clear on the general@incubator list that IBM is going to force The Apache Foundation to take the project. How? I am *not* saying you would be influenced or forced - I'd never doubt that you are deciding independent. However, what people may give the feeling that something's wrong are statements like these: http://www.sutor.com/c/2011/06/some-remarks-on-openoffice-going-to-apache/comment-page-1/#comment-5309 it is a done deal That might create wrong impressions... I'll repeat what Jim said: how do you think IBM can force us to take the project? Bob can say whatever he'd like on his blog. The software grant is a done deal. I happen to believe the proposal will be accepted, but it is not a done deal. In any case... stop assuming that what *one* person says is representative of the entire (ASF) community. That simply isn't true. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice: were are we now?
If IBM pulls a harmony, TDF can just use the Apache licensed code that's available and run with it. Here the problem currently is how to make things work if/when the podling gets accepted and folks start contributing, stick around for a long time with lots of good contributions from multiple sources. http://www.mail-archive.com/discuss@documentfoundation.org/msg06529.html -- dims On 06/05/2011 08:32 PM, Sanjiva Weerawarana wrote: Attempting to guess IBM strategy around this ... IMO the reason this whole thing is happening is because with TDF there no longer was a place that downstream proprietary aggregators of OO like IBM could use to build a closed-source solution (no org to do a dual license with). The Apache license is (one of) the best options for that and certainly the Apache brand doesn't hurt towards building a credible alternative to MS Office. To that extent it wouldn't surprise me at all to see IBM donating whatever their proprietary add-ons from their Lotus product to this project and thereby taking a larger role. My concern from the ASF's point of view is that how do we protect from IBM doing a Harmony on this? I guess one advantage is that there's nothing else out there and an office work toolset is a necessary feature for many vendors ... so there's relatively little risk of a TCK or an OpenJDK type alternative happening. If MSFT decides to open up office (not likely) or Google decides to open source their corresponding apps bits (again, not likely at least until OO has a credible Web offering) something could happen but those are far fetched at this point. After all that, TDF has unfortunately been left holding the wrong end of the stick :(. If I was in TDF I'd definitely feel screwed by Oracle .. but really this is not just Oracle but rather the larger value-add community around OO saying lets get together. That is not possible without the Apache license as those guys all want to make proprietary products. ASF is not the bad guy but rather the one who has all the features to host this project as a result. To that extent those value-add types are using ASF but that's not necessarily a bad way for this project to get started. Whether it succeeds long term is a function of it becoming a true ASF project with a multitude of disparate contributors etc.. The people who will only contribute to a copyleft license (and I know a few OO contributors like that) will not come over this world .. so to that extent this is a community fork and we cannot do brand sharing as that'll confuse end-users. Sanjiva. On Mon, Jun 6, 2011 at 2:29 AM, robert_w...@us.ibm.com wrote: Joe Schaefer joe_schae...@yahoo.com wrote on 06/05/2011 04:22:35 PM: Sounds great, but so far I count only 2 committers on the project associated with IBM. IMO you're off by a factor or so, so claims that IBM intends to take this project seriously will be discounted by me until that is rectified. Joe, it will be my pleasure to astonish you. But it will take a few more days ;-) It is amazing how much paperwork is involved, at a large corporation, to enable such things. -Rob - 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: Apache OpenOffice.org Incubator Proposal: Collaboration with TDF/LO
Simon, As a Incubator PMC member, I'd like to hear what the TDF folks think about this suggested path. In the end the people who do the day-to-day work will end up collaborating or not...But, here's my +1 that implies that i'd like folks who are signing on to this podling do their best to make this happen. -- dims On 06/03/2011 06:26 PM, dsh wrote: +1 (I like the positive tone that tries to omit words having a negative connotation) Cheers Daniel On Sat, Jun 4, 2011 at 12:16 AM, Simon Phipps si...@webmink.com wrote: I suggest: The LibreOffice project is an important partner in the OpenOffice.org community, with an established potentially highly complementary focus on the GNU/Linux community as well as on Windows and Mac consumer end-users. We will seek to build a constructive working and technical relationship so that the source code developed at Apache can be readily used downstream by LibreOffice, as well as exploring ways for upstream contributions to be received as much as possible within the constraints imposed by mutual licensing choices. There will be other ways we may be able to collaborate, including jointly sponsored public events, interoperability 'plugfests', standards, shared build management infrastructure, shared release mirrors, coordination of build schedules, version numbers, defect lists, and other downstream requirements. We will make this relationship a priority early in the life of the podlet. S. - 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: Volunteering for the Apache OpenOffice podling?
Philip, please check here - http://people.apache.org/committer-index.html I don't think i see your name there -- dims On Thu, Jun 2, 2011 at 8:53 PM, Phillip Rhodes motley.crue@gmail.com wrote: Hmmm... I was never a committer, somebody else applied that patch... but I was asked to fax in a CLA. Not sure if that helps or not. :-) Phil On Jun 2, 2011 8:25 PM, Sam Ruby ru...@intertwingly.net wrote: On Thu, Jun 2, 2011 at 8:02 PM, Phillip Rhodes motley.crue@gmail.com wrote: On Thu, Jun 2, 2011 at 7:20 PM, Jim Jagielski j...@jagunet.com wrote: Under the list of proposed committers, yes. -- Awesome. I should already have a CLA on file, from when I made a contribution to Roller Weblogger a few years back. That was, however, some time ago. Is there a way to confirm that my CLA info is on file and good to go? Look here: http://people.apache.org/committer-index.html Thanks, Phil - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Flume for the Apache Incubator
integration with projects such as Apache Hive, data stores such as Apache HBase, Apache Cassandra and Voldemort, and several Apache Lucene-related projects. == An Excessive Fascination with the Apache Brand == We would like Flume to become an Apache project to further foster a healthy community of contributors and consumers around the project. Since Flume directly interacts with many Apache Hadoop-related projects by solves an important problem of many Hadoop users, residing in the the Apache Software Foundation will increase interaction with the larger community. = Documentation = * All Flume documentation (User Guide, Developer Guide, Cookbook, and Windows Guide) is maintained within Flume sources and can be built directly. * Cloudera provides documentation specific to its distribution of Flume at: http://archive.cloudera.com/cdh/3/flume/ * Flume wiki at GitHub: https://github.com/cloudera/flume/wiki * Flume jira at Cloudera: https://issues.cloudera.org/browse/flume = Initial Source = * https://github.com/cloudera/flume/tree/ == Source and Intellectual Property Submission Plan == * The initial source is already licensed under the Apache License, Version 2.0. https://github.com/cloudera/flume/blob/master/LICENSE == External Dependencies == The required external dependencies are all Apache License or compatible licenses. Following components with non-Apache licenses are enumerated: * org.arabidopsis.ahocorasick : BSD-style Non-Apache build tools that are used by Flume are as follows: * AsciiDoc: GNU GPLv2 * FindBugs: GNU LGPL * Cobertura: GNU GPLv2 * PMD : BSD-style == Cryptography == Flume uses standard APIs and tools for SSH and SSL communication where necessary. = Required Resources = == Mailing lists == * flume-private (with moderated subscriptions) * flume-dev * flume-commits * flume-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/flume == Issue Tracking == JIRA Flume (FLUME) == Other Resources == The existing code already has unit and integration tests so we would like a Hudson instance to run them whenever a new patch is submitted. This can be added after project creation. = Initial Committers = * Andrew Bayer (abayer at cloudera dot com) * Jonathan Hsieh (jon at cloudera dot com) * Aaron Kimball (akimball83 at gmail dot com) * Bruce Mitchener (bruce.mitchener at gmail dot com) * Arvind Prabhakar (arvind at cloudera dot com) * Ahmed Radwan (ahmed at cloudera dot com) * Henry Robinson (henry at cloudera dot com) * Eric Sammer (esammer at cloudera dot com) = Affiliations = * Andrew Bayer, Cloudera * Jonathan Hsieh, Cloudera * Aaron Kimball, Odiago * Bruce Mitchener, Independent * Arvind Prabhakar, Cloudera * Ahmed Radwan, Cloudera * Henry Robinson, Cloudera * Eric Sammer, Cloudera = Sponsors = == Champion == * Nigel Daley == Nominated Mentors == * Tom White * Nigel Daley == Sponsoring Entity == * Apache Incubator PMC -- // Jonathan Hsieh (shay) // Software Engineer, Cloudera // j...@cloudera.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal]: Libcloud to become a TLP
++ - 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 -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Wink 1.1.3-incubating (RC1)
+1 from me (binding) On Sat, Apr 30, 2011 at 7:37 PM, Luciano Resende luckbr1...@gmail.com wrote: On Thursday, April 21, 2011, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Apr 18, 2011 at 2:34 PM, Luciano Resende luckbr1...@gmail.com wrote: The Wink community has completed a vote on it's 1.1.3 release (1.1.3-incubating) and is now looking for IPMC approval to publish the release. Please review and vote on RC1 of the Wink 1.1.3-incubating release. The distribution artifacts, RAT reports, and Maven staging repository are available for review at: http://people.apache.org/~lresende/wink/wink-1.1.3-incubating/ The release tag is at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.1.3-incubating-RC1/ Vote thread: http://www.mail-archive.com/wink-dev@incubator.apache.org/msg04040.html Anyone else available to review this release ? We need one more IPMC Ping ? We still need one more binding vote. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 On Fri, Feb 25, 2011 at 5:30 AM, Arje Cahn a.c...@hippo.nl wrote: [X] +1 Accept Rave into the incubator - Arjé -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [libcloud] Re: [VOTE] Release Apache Libcloud 0.4.2
+1 from me (binding) -- dims On Wed, Jan 12, 2011 at 11:39 AM, Paul Querna p...@querna.org wrote: Poke to general@ people, we need more IPMC votes for this release to happen :( On Mon, Jan 10, 2011 at 10:00 PM, Jerry Chen je...@apache.org wrote: Hi all, With 6x +1 votes (including 2 binding), and no -1 votes, the vote seeks the approval of the IPMC. Thanks, Jerry On Jan 8, 2011, at 12:10 AM, Jerry Chen wrote: Hi all, Test tarballs for Apache Libcloud 0.4.2 are available at: http://people.apache.org/~jerry/libcloud-0.4.2/ Please test and place your votes: +/- 1 [ ] Release Apache Libcloud 0.4.2 Vote closes on Sunday January 9, 2011 at 10pm PST. This release includes the EC2NodeLocations fix to restore backward compatibility in the EC2 driver, as well as new drivers, improvements to deployment capabilities, and libcloud.security module for SSL certificate verification. For more information on SSL verification: http://wiki.apache.org/incubator/LibcloudSSL For the full list of changes, see: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.2/CHANGES Cheers, Jerry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Wave into the incubator
+1 -- dims On 11/30/2010 03:10 AM, Christopher Brind wrote: +1 (non-binding) On 30 November 2010 06:52, Dan Peterson dpeter...@google.com wrote: Hi everyone, Please vote on the acceptance of Wave into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) The earlier discussion thread can be found at: http://apache.markmail.org/message/3ebtccdxvipp2732?q=general%40incubator.apache.org+list:org.apache.incubator.general+order:date-backwardpage=2 The vote options: [ ] +1 Accept Wave for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Thanks, -Dan Apache Wave Proposal (Apache Incubator) = Abstract = Apache Wave is the project where wave technology is developed at Apache. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). = Proposal = A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. WIAB is a server that hosts waves. The best analogy for this is a mail server with a web client. WIAB is comprised of a few high-level components: the client and the server. They have the following major functionality (though this is not an exhaustive list): * Client *A dynamic web client for users to create, edit, and search waves. Users can access this client by directly visiting the server in a browser. * Gadgets provide the ability to insert, view, and modify the UI -- exposing the Wave Gadgets API ( http://code.google.com/apis/wave/extensions/gadgets/guide.html) * A console client that can create and edit waves via a command-line-like interface. * Server * Hosts and stores waves. WIAB comes with a default storage mechanism. The administrators of the server may configure it to use alternative storage mechanisms. * Indexing, allowing for searching the waves a user has access to. * Basic authentication, configurable to delegate to other systems. * Federation, allowing separate Wave in a Box servers to communicate with each other using the Wave Federation Protocol ( http://www.waveprotocol.org/federation). * Robots, using the Wave Robots API, ( http://code.google.com/apis/wave/extensions/robots/) may interact with waves on a WIAB instance. = Background = Wave expresses a new metaphor for communication: hosted conversations. This was created by Lars and Jens Rasmussen after observation of people's use of many separate forms of communication to get something done, e.g, email, chat, docs, blogs, twitter, etc. The vision has always been to better the way people communicate and collaborate. Building open protocols and sharing code available in an open and free way is a critical part of that vision. Anyone should be able to bring up their own wave server and communicate with others (much like SMTP). We hope this project will allow everyone to easily gain the benefits of Wave with a standard implementation of Wave – in a box. = Rationale = Wave has shown it excels at small group collaboration when hosted by Google. Although Wave will not continue as a standalone Google product, there is a lot of interest from many organizations in both running Wave and building upon the technology for new products. We are confident that with the community-centric development environment fostered by the Apache Software Foundation, WIAB will thrive. = Initial Goals = The initial goals of the project are: 1. To migrate the codebase from code.google.com and integrate the project with the ASF infrastructure (issue management, build, project site, etc). 1. To quickly reach a state where it is possible to continue the development of the Wave In a Box implementation under the ASF project. 1. To add new committers to the project and grow the community in The Apache Way. = Current Status = The open source Wave in a Box project has existed in various forms for approximately 16 months (starting out life as the FedOne open source project). FedOne began in July 2009 in order to accelerate adoption of the wave federation protocol, and serve as a proof of concept that a non-Google implementation of the wave federation protocol could interoperate with the Google production instance. It worked. FedOne's existence lead to a prototype by Novell that demonstrated federation between Google Wave and Novell Pulse (now known as Vibe). In addition, in May of 2010, SAP unveiled a prototype version of SAP StreamWork that federated with both Novell Pulse and Google Wave. All three systems interoperated, sharing real-time
Re: [VOTE] Aries Graduation to TLP
+1 -- dims On Mon, Nov 22, 2010 at 7:09 AM, Guillaume Nodet gno...@gmail.com wrote: +1 On Mon, Nov 22, 2010 at 12:51, Jeremy Hughes hugh...@apache.org wrote: Hi IPMCers and Incubator community, The Aries community has been discussing graduation and we feel we are ready to graduate to a new TLP [1]. We subsequently voted [2]. As a commnunity we were unanimous in deciding to graduate to a new TLP. We voted [3] on putting forward the resolution below for the next Board meeting to promote Aries to an Apache TLP and graduate from the Incubator. As per the graduation guide [4], the Aries PPMC voted on the position of Chair. That Vote is here [5] and Result is here [6] (Aries PPMC list membership required). Please VOTE on the below resolution for promoting Aries to an Apache TLP and graduating from the Incubator. The VOTE is open for 72 hours. [ ] +1 Accept Aries' graduation from the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Aries' graduation from the Incubator because ... ## Resolution to create a TLP from graduating Incubator podling X. Establish the Apache Aries 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 a set of pluggable Java components enabling an enterprise OSGi application programming model for deployment to a variety of OSGi based runtimes, 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 Aries Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Aries Project be and hereby is responsible for the creation and maintenance of software related to a set of pluggable Java components enabling an enterprise OSGi application programming model for deployment to a variety of OSGi based runtimes; and be it further RESOLVED, that the office of Vice President, Apache Aries 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 Aries Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Aries 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 Aries Project: * A. J. David Bosschaert dav...@apache.org * Adam Wojtuniak awojtun...@apache.org * Alan Cabrera a...@apache.org * Alan T Keane a...@apache.org * Alasdair Nottingham n...@apache.org * Andrew Osborne o...@apache.org * Bartosz Kowalewski bko...@apache.org * Bertrand Delacretaz bdelacre...@apache.org * Carsten Ziegeler cziege...@apache.org * Chris Wilkinson cwil...@apache.org * Davanum Srinivas d...@apache.org * David Jencks djen...@apache.org * Emily Jiang eji...@apache.org * Eoghan Glynn egl...@apache.org * Graham Charters g...@apache.org * Guillaume Nodet gno...@apache.org * Hiram R. Chirino chir...@apache.org * Holly Cummins cummi...@apache.org * Ian Robinson irob...@apache.org * J. Daniel Kulp dk...@apache.org * James Strachan jstrac...@apache.org * Jarek Gawor ga...@apache.org * Jean Sebastien Delfino jsdelf...@apache.org * Jeremy Hughes hugh...@apache.org * Joseph Alan Bohn jb...@apache.org * Kevan Lee Miller ke...@apache.org * Kiril Malenkov Mitov kmi...@apache.org * Lei Wang rwo...@apache.org * Lin Sun lin...@apache.org * Mark Nuttall mnutt...@apache.org * Niklas Gustavsson n...@apache.org * Nikolai Dimitrov Tankov nikol...@apache.org * Par Niclas Hedhman nic...@apache.org * Richard McGuire rickmcgu...@apache.org * Sabine Heider heider...@apache.org * Sergey Beryozkin serg...@apache.org * Stuart McCulloch mccu...@apache.org * Timothy James Ward timothyjw...@apache.org * Valentin Mahrwald mahrw...@apache.org * Violeta Georgieva Georgieva violet...@apache.org * Zhaohui Feng rf...@apache.org * Zoe Slattery z...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jeremy Hughes be appointed to the office of Vice President, Apache Aries, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until
Re: [VOTE] Accept Stanbol for incubation
://github.com/ogrisel and
http://bitbucket.org/ogrisel
* Ozgur Kilic (ozgur AT srdc DOT com DOT tr) - SRDC
* Rupert Westenthaler (rupert DOT westenthaler AT gmail DOT com) -
Salzburg Research
* Sebastian Germesin (sebastian DOT germesin AT dfki DOT de) - DFKI
* Stefane Fermigier (sf AT fermigier DOT com) - Nuxeo SA
* Szabolcs Grunwald (szaby DOT gruenwald AT salzburgresearch DOT at)
- Salzburg Research
* Tilman Becker (becker AT dfki DOT de) - DFKI
* Valentina Presutti (valentina DOT presutti AT cnr DOT it) - CNR
* Walter Kasper (kasper AT dfki DOT de) - DFKI - OpenLogos project
lead, http://openlogos-mt.sourceforge.net/
* Wernher Behrendt (wernher DOT behrendt AT gmail DOT com) - Salzburg
Research
* Wolfgang Maass (wolfgang DOT maass AT unisg DOT de) - University of
St. Gallen
The following initial committers are not members of the IKS consortium:
* Andreas Kuckartz (a DOT kuckartz AT ping DOT de)
* Ard Schrijvers (ard AT apache DOT org)
* Tommaso Teofili (tommaso AT apache DOT org)
== Sponsors ==
=== Champion ===
* Bertrand Delacretaz (bdelacretaz AT apache DOT org)
=== Nominated Mentors ===
* Ted Dunning (tdunning AT apache DOT org)
* Ross Gardler (rgardler AT apache DOT org)
* Upayavira (upayavira AT apache DOT org)
* Isabel Drost (isabel AT apache DOT org)
=== Sponsoring Entity ===
Apache Incubator.
== Appendix A: list of dependencies ==
Here's the list of Maven groupIds of the current Stanbol dependencies,
omitting org.apache.* and commons-* groupIds but including transitive
dependencies.
{{{
asm
com.aetrion.flickr
com.beetstra.jutf7
com.drewnoakes
com.googlecode.json-simple
com.hp.hpl.jena
com.ibm.icu
com.sun.jersey
com.sun.xml.bind
dom4j
edu.smu.tspell
eu.iksproject
hermit
info.aduna.commons
it.unimi.dsi.fastutil.chars
javax.activation
javax.mail
javax.servlet
javax.ws.rs
javax.xml
javax.xml.bind
javax.xml.stream
jetty
jtidy
junit
local.jrdf
log4j
mysql
net.fortuna.ical4j
net.fortuna.mstor
net.sf.jacob-project
net.sf.kxml
net.sourceforge
net.sourceforge.juniversalchardet
org.antlr
org.bibsonomy
org.bouncycastle
org.clojars.thnetos
org.codehaus.castor
org.codehaus.jackson
org.codehaus.jettison
org.codehaus.woodstox
org.freemarker
org.hsqldb
org.htmlparser
org.jaudiotagger
org.jdom
org.json
org.mockito
org.mortbay.jetty
org.nsdl.mptstore
org.openrdf.sesame
org.ops4j.base
org.ops4j.pax.exam
org.ops4j.pax.runner
org.osgi
org.samba.jcifs
org.scala-lang
org.semanticdesktop.aperture
org.semanticdesktop.nepomuk
org.semanticweb.owlapi
org.semweb4j
org.slf4j
org.textmining
org.wymiwyg
owl-link
owlapi
ronaldhttpclient
stax
trove
xerces
xmlpull
}}}
-
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
--
Davanum Srinivas :: http://davanum.wordpress.com
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Boot strapping Android projects @ Apache
Channeling my asimov...How about daneel :) -- dims On Wed, Nov 10, 2010 at 10:40 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Nov 10, 2010 at 4:16 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Sorry Bertrand, but I can't see the relation between Droids and Android related set of projects either under Labs/Incubator or both ? Would explain please :) ? IIUC Bruno suggests using droids.apache.org for this new effort. That would collide with the Droids podling (http://incubator.apache.org/projects/droids.html) once it graduates, so the droids subdomain is already reserved IMO. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Celix for incubation
+1 -- dims Sent from my iPhone On Oct 28, 2010, at 3:47 PM, Richard S. Hall he...@ungoverned.org wrote: +1 - richard On 10/28/10 15:42, Marcel Offermans wrote: After the initial discussions about Celix have finished, we now have three mentors and would like to call a vote to accept Celix into the Apache Incubator. The proposal is included below and can also be found at: http://wiki.apache.org/incubator/CelixProposal Please cast your votes: [ ] +1 Accept Celix for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: Greetings, Marcel Celix = Abstract = Celix is a OSGi like implementation in C with a distinct focus on interoperability between Java-OSGi and Celix. = Proposal = Celix will be an implementation of the OSGi specification adapted to C. It will follow the API as close as possible, but since the OSGi specification is written primarily for Java, there will be differences (Java is OO, C is procedural). An important aspect of the implementation is interoperability between Java-OSGi and Celix. This interoperability is achieved by porting and implementing the Remote Services specification in Celix. These Services will be made available in separate bundles. = Background = In embedded/realtime situations software is mostly implemented in C. In situations where interoperability and dynamics are important, a good architecture and design principle is needed. OSGi provides such middleware for Java based systems. To be able to have such dynamic environment implemented in C, a OSGi like implementation is needed. Besides a dynamic environment, OSGi also makes it easier to reuse parts of the system, reducing time needed to implement and maintain software. The implementation started with the basics to make it possible to load libraries dynamically, and steadily grown towards an implementation where large parts of the OSGi framework API is implemented. The implementation of Celix is heavily based on Apache Felix (where appropriate it is even a direct port of the Apache Felix code (Java) to C). Since distributed systems are used more and more in services based environments, a scalable and transparent solution is needed for remote communication. The OSGi specification describes remote services, this specification will be a part of the first release. Remote services also make it possible to communicate between Java-OSGi and Celix. To achieve this interoperability, both Java and C implementations of remote services for a common protocol are needed. For local services JNI can be used, for remote services SOAP and/or REST can be used. In the latter case, Apache CXF can be used to implement the Remote Services API in Java. = Rationale = In embedded/realtime/distributed environments there is a need to be able to create dynamic and maintainable software. Currently there are no off the shelf middleware/frameworks for this. Celix tries to provide such a framework. The choice to base the implementation on the OSGi specification makes it possible for a developer to use Celix as well as Java OSGi implementation without much differences and without a steep learning curve. The community and user driven platform created by Apache provides a great base for middleware such as Celix. Also the fact that Celix is based on Apache Felix, and Apache Felix is hosted by Apache, makes it a logical choice to have Apache as home for this project. = Initial Goals = * Provide a basic implementation of the OSGi Framework API * Provide an implementation of Remote Services to be able to create distributed systems (and Celix- OSGi interoperability). * Build/Expand a community using/developing Celix * OSGi like implementation in C * Provide a module/component based software solution for embedded Platforms o Real-Time software o Distributed systems o Provide Services based solution * Investigate if Apache Portable Runtime can be used for platform abstraction = Current Status = == Meritocracy == Celix was created by Alexander Broekhuis. While he is no active committer/participant of Apache projects, he has used Open Source and is well known with it and how a meritocracy works. Currently there are several other possible committers. To be able to create and maintain complex middleware (such as Celix) a good structure is needed. A meritocracy following the rules and traditions of the ASF is a good choice for Celix. == Community == Currently the Celix community exists out of the core developers, and the users integration Celix in an end-user product (all from Thales). == Core Developers == * Alexander Broekhuis (Luminis) * Jasper Gielen (Humiq) * Herman ten Brugge (Thales) == Alignment == Celix is heavily based on Apache Felix. Since Apache Felix is an Apache project it makes sense to develop Celix
Re: [VOTE] [RESULT] Approve the release of apache-esme-incubating-1.1
+1 from me On 10/07/2010 11:52 PM, Richard Hirsch wrote: Hi all, after more than 72 hours, this vote has started and together with those received on the podling list [1], we have now received sufficient IPMC binding votes to proceed with the release of ESME 1.1. We got 3 binding IPMC +1 votes and no 0 or -1 votes as listed below: +1 Dick Hirsch +1 Daniel Kulp +1 Bertrand Delacretaz I'll proceed with distribution [2]. As a IPMC member, do I have access to www.apache.org/dist? Do I just copy the material from http://people.apache.org/~rhirsch/esme/ directly into http://www.apache.org/dist/incubator/esme/ and replace the old KEYS file with the new one? Thanks D. [1] http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/201010.mbox/%3caanlktim_jhcbvzao6ou-dt_adicgyhsi7+pj-a+9y...@mail.gmail.com%3e - 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: [libcloud] [VOTE] Release Apache Libcloud 0.4.0
+1 from me. On Wed, Oct 6, 2010 at 4:36 PM, Paul Querna p...@querna.org wrote: Test tarballs for Apache Libcloud 0.4.0 are available at: http://people.apache.org/~pquerna/dev/libcloud-0.4.0/ Please test and place your votes please; +/- 1 [ ] Release Apache Libcloud 0.4.0 Vote closes on Monday October 11, 2010 at 10am PST. This is our first release of the 0.4 and trunk for a couple months, it includes many bug fixes, a few new features, and removal of the dependency on Zope.Interface. It is based upon this tag: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.0 Thanks, Paul -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kitty to Enter the Incubator
+1 (binding) On Wed, Sep 29, 2010 at 3:24 PM, matt...@matthewsacks.com wrote: Hi List, I would like to do a quick sanity check on this thread. Please correct me if I am wrong, but we have 2 binding PMC votes, 2 new contributors (Rainer Jung and Senaka Fernando) and 1 new mentor (Kevan Miller). I believe my facts to be accurate. I plan on updating the Wiki next week to reflect this when I complete some travels, and create a fork for a Groovy port to begin that work. Thanks, Matthew -Original Message- From: Alan D. Cabrera l...@toolazydogs.com Sent: Wednesday, September 22, 2010 9:00am To: general@incubator.apache.org Subject: Re: [VOTE] Kitty to Enter the Incubator +1 Regards, Alan On Sep 15, 2010, at 12:20 AM, msacks wrote: At the advisement of the list, we have created a brand-new thread here for voting on the kitty proposal. The wiki page is located at: http://wiki.apache.org/incubator/KittyProposal Thanks. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a few more votes... Re: [PROPOSAL] Kitty to Enter the Incubator
+1 from me (binding) On Mon, Sep 13, 2010 at 9:11 AM, Jim Jagielski j...@jagunet.com wrote: So far I see 2 clear (binding) +1s for the proposal... Calling out for more ;) On Sep 7, 2010, at 8:29 PM, Matthew Sacks wrote: Hello, Peary Chiu and myself would like to announce the Proposal for the Kitty, Production Tomcat utility. Our proposal is as follows (we have also attached a PDF for convenience): kitty, lightweight, Production-class Java application server performance diagnostic administration utility Abstract A lightweight, production focused, Java-based application server performance diagnostic and management utility Proposal • Provide a lightweight utility for managing Tomcat and Geronimo application servers with powerful performance diagnostics and troubleshooting abilities primarily for supporting Tomcat in production/high volume use. • (future) Provide support for all Java application servers Background The answer is simple, there is not a lightweight, command line administration utility that can be utilized across open source application servers. There are many utilities which have been created such as jmxsh, but they do not solve the problem of having a lightweight administration / debugging client for troubleshooting these open source application servers such as Apache Tomcat and Geronimo. Rationale There needs to be a lightweight, administration client that targets production use based on the experience of those administering Tomcat (and other open source Java application servers) in high-volume, large scale production environments. Such an administration tool will help further these open source application servers in production, large-installation grade implementations and better support such “industrial-grade” use. Initial Goals kitty is an existing open source project, with two contributors. We would bring in more folks with experience in managing high-volume production Web sites to contribute to the architecture of the kitty project. Currently we have two committers both with high-volume, production Web experience. We’d also leverage feedback from the community in this context and integrate that into the utility to provide a truly powerful management and performance diagnostic utility for Tomcat/Geronimo and other Java application servers. We will add common diagnostic hooks into the application as a first step, for example, show available memory, threading problems, JDBC, and Web application diagnostic hooks. The application will run in script mode (future) for automation purposes, or interactive mode, so it can be used for ad-hoc troubleshooting. Supported Platforms • Apache Tomcat 6.0+ Future Support • Apache Geronimo • All other Java application servers Known Risks Currently the application is coded in Jython. Jython makes a suitable fit for many command-line administration tools. We plan on creating a pure, Groovy-based port of kitty in the next few weeks, primarily for ease of compilation to Java classes. We understand that developing this in Jython makes it faster to develop the utility, but increases it’s complexity for compilation. We are in the process of converting the project to Groovy to address this issue, within two weeks from the date of this proposal. Initial Source http://github.com/msacks/kitty External Dependencies Jython 2.5.1 Documentation - README (Documentation) http://github.com/msacks/kitty/blob/master/README - How Kitty was Born http://www.tomcatexpert.com/blog/2010/05/17/creating-custom-tools-monitoring-tomcat Initial Committers Matthew Sacks (matt...@glasscodeinc.com) Peary Chiu (pearyc...@gmail.com) Jim Jagielski (j...@jimgjag.com) Stuart Williams (p...@pidster.com) Required Resources • Subversion • Jira • Wiki • Website Space • Hudson Mailing Lists kitty-dev kitty-commits kitty-user Subversion Repository https://svn.apache.org/repos/asf/incubator/kitty Issue Tracking Jira; project known as ‘kitty’ Affiliations Matthew Sacks (self) Peary Chiu (self, also employed by Edmunds Inc) Jim Jagielski (ASF/ VMware) Stuart Williams (VMware/ASF) Champion Jim Jagielski Sponsors: Nominated Mentors Jim Jagielski Stuart Williams Mark Thomas Sponsor Apache Incubator ASF-kitty-Tomcat-proposal.pdf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Accepting patches in a podling
David, Yes, current practice is exactly what Benson outlined. thanks, dims On 09/13/2010 08:58 PM, Benson Margulies wrote: All patches should be attached to JIRAs with the 'grant' checkbox checked. Only if they are large do you then have to contemplate asking for a CLA and going through the clearance process. Or so I understand it. On Mon, Sep 13, 2010 at 8:55 PM, David Lutterkortlut...@redhat.com wrote: What is the offical process for accepting patches from non-comitters in a podling ? Is it enough to insist that contributors that are not committers have a CLA on file or do I also have to make them file each patch in jira ? David - 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: [RESULT] [VOTE] Patricia Shanahan for committer account
+1 -- dims On Aug 23, 2010, at 5:26 PM, Craig L Russell craig.russ...@oracle.com wrote: I'm very happy to see Patricia contributing so enthusiastically. +1 Craig On Aug 23, 2010, at 2:16 PM, Benson Margulies wrote: We are short one IPMC vote for a new River committer. She's been an enthusiastic contributor. -- Forwarded message -- From: Jukka Zitting jukka.zitt...@gmail.com Date: Mon, Aug 23, 2010 at 4:22 PM Subject: [RESULT] [VOTE] Patricia Shanahan for committer account To: river-priv...@incubator.apache.org Hi, On Sat, Aug 14, 2010 at 1:32 PM, Peter Firmstone j...@zeus.net.au wrote: Patricia has showed a continued interest in Apache River, I believe that she'll be an asset, if we can encourage her to stick around. I'd like to see her offered a commiter account. This vote passes as follows (* marks an IPMC vote): +1 Benson Margulies * +1 Jukka Zitting * +1 Peter Firmstone +1 Tom Hobbs Thanks for voting! We still need one more IPMC vote to ratify this decision. Benson promised to follow up on this with the IPMC. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - 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] experimental delegation of new committer votes to PPMC
+1 -- dims Sent from my iPhone On Aug 18, 2010, at 7:11 PM, Joe Schaefer joe_schae...@yahoo.com wrote: Now that the board has declared there are no legal obstacles to what I have proposed, I'd like to restart the vote. Thanks for your patience and consideration. - Original Message From: Joe Schaefer joe_schae...@yahoo.com To: general@incubator.apache.org Sent: Mon, August 16, 2010 1:44:08 PM Subject: [VOTE] experimental delegation of new committer votes to PPMC I have come to the realization that I'm not going to convince Noel to see things my way any time soon, so I'd like to now ask for a formal majority consensus vote on relaxed rules for the 3 aforementioned projects. Specifically, for thrift, sis, and esme, I wish to remove the current rule that requires 3 votes from IPMC members to approve a vote on a new committer, effectively delegating the decision to the PPMC. Additionally the pre-ack would be removed, but no other process changes are anticipated. Here's my +1. - 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: an experiment
Craig, in my mind, it's not the number of steps that we eliminate, it's the message that we send. Instead of saying you all are *under* the microscope, we say that real quickly a few of you will become part of the microscope and look in on not just yours but also other podlings...my 2 cents. thanks, dims On Thu, Aug 12, 2010 at 2:21 PM, Craig L Russell craig.russ...@oracle.com wrote: On Aug 11, 2010, at 10:45 AM, Joe Schaefer wrote: The first idea should be fairly straightforward: that for the projects I participate in (so far thrift and sis), that the IPMC delegates to the PPMC the decision-making process for voting in new committers: basically rolling back the clock to May 1, 2007 on guides/ppmc.html. Before we set ourselves up for disappointment based on unrealistic expectations, this proposal is fairly modest. Here's the current process for getting new committers into an incubating project: 1. Identify candidates 2. Discuss candidates on podling-private 3. Agree that candidate should be a committer 4. Vote on podling-private 5. Wait for everyone's vote 6. Inform incubator PMC of results of vote 7. Vote in incubator PMC if not all three mentors have voted 8. Invite committer 9. Send ICLA 10. Wait for ICLA registration 11. Send root request for committer 12. Wait for root to create account 13. Update asf authorization file for new account 14. Done All this proposal does is to eliminate step 7 in the case where the Mentors are AWOL. That said, I support the idea behind this modest proposal, and just need to see the details (several modifications have been proposed). Infra also needs to support this proposal, as the main reason for item 7 is to get root to recognize that the incubator PMC has taken official action (three votes in favor of a new committer) which has been an infrastructure requirement (also part of the details). Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] NPanday to enter the incubator
+1 -- dims Sent from my iPhone On Aug 12, 2010, at 2:32 PM, Craig L Russell craig.russ...@oracle.com wrote: +1 Craig On Aug 6, 2010, at 8:21 AM, Brett Porter wrote: Hi, We have finalised the proposal with the additional committer and it has now been posted for a couple of weeks, so I'd like to put it to a vote. With the weekend included, I'll tally the votes after 5 days (120 hours). Thanks, Brett Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - 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: an experiment
Fair enough :) Sent from my iPhone On Aug 12, 2010, at 3:10 PM, Craig L Russell craig.russ...@oracle.com wrote: Hi Dims, On Aug 12, 2010, at 12:05 PM, Davanum Srinivas wrote: Craig, in my mind, it's not the number of steps that we eliminate, it's the message that we send. Instead of saying you all are *under* the microscope, we say that real quickly a few of you will become part of the microscope and look in on not just yours but also other podlings...my 2 cents. I think your comment is in regard to Joe's other proposal that all committers become part of the incubator PMC. I didn't address that proposal here. Craig thanks, dims On Thu, Aug 12, 2010 at 2:21 PM, Craig L Russell craig.russ...@oracle.com wrote: On Aug 11, 2010, at 10:45 AM, Joe Schaefer wrote: The first idea should be fairly straightforward: that for the projects I participate in (so far thrift and sis), that the IPMC delegates to the PPMC the decision-making process for voting in new committers: basically rolling back the clock to May 1, 2007 on guides/ppmc.html. Before we set ourselves up for disappointment based on unrealistic expectations, this proposal is fairly modest. Here's the current process for getting new committers into an incubating project: 1. Identify candidates 2. Discuss candidates on podling-private 3. Agree that candidate should be a committer 4. Vote on podling-private 5. Wait for everyone's vote 6. Inform incubator PMC of results of vote 7. Vote in incubator PMC if not all three mentors have voted 8. Invite committer 9. Send ICLA 10. Wait for ICLA registration 11. Send root request for committer 12. Wait for root to create account 13. Update asf authorization file for new account 14. Done All this proposal does is to eliminate step 7 in the case where the Mentors are AWOL. That said, I support the idea behind this modest proposal, and just need to see the details (several modifications have been proposed). Infra also needs to support this proposal, as the main reason for item 7 is to get root to recognize that the incubator PMC has taken official action (three votes in favor of a new committer) which has been an infrastructure requirement (also part of the details). Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! --- -- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - 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: an experiment
+1 to IPMC delegates to the PPMC the decision-making process for voting in new committers (one question, would they need an ACK from IPMC - similar to how PMC's send a note to the board for an ACK for new pmc members)? In the 2nd question, significant committers, are we asking mentors to identify such candidates for addition to IPMC, especially release managers for example? if so, +1 for that as well. thanks, dims On 08/11/2010 01:45 PM, Joe Schaefer wrote: So. Following some advice given to me by Sam Ruby, I'd like to start experimenting with different organizational and procedural approaches to the projects I participate in here. What I want to do is to see how far I can push the envelope on the whole notion of empowerment and self-governance in an incubating project, following the lessons I've learned from httpd's treatment of the subprojects it happens to be responsible for. The first idea should be fairly straightforward: that for the projects I participate in (so far thrift and sis), that the IPMC delegates to the PPMC the decision-making process for voting in new committers: basically rolling back the clock to May 1, 2007 on guides/ppmc.html. The second idea is more controversial: to hold IPMC votes to admit all significant committers to those projects to the IPMC itself. The purpose of this concept is to allow those who best know the codebase to provide IPMC oversight over it, especially as it pertains to releases. I welcome your comments, criticisms, and other feedback. Thanks. - 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: an experiment
On 08/11/2010 05:19 PM, Donald Woods wrote: On 8/11/10 1:45 PM, Joe Schaefer wrote: So. Following some advice given to me by Sam Ruby, I'd like to start experimenting with different organizational and procedural approaches to the projects I participate in here. What I want to do is to see how far I can push the envelope on the whole notion of empowerment and self-governance in an incubating project, following the lessons I've learned from httpd's treatment of the subprojects it happens to be responsible for. The first idea should be fairly straightforward: that for the projects I participate in (so far thrift and sis), that the IPMC delegates to the PPMC the decision-making process for voting in new committers: basically rolling back the clock to May 1, 2007 on guides/ppmc.html. How about requiring at least one mentor on the vote, so there is still some oversight? Having all mentors vote is good but not necessary...IMHO The second idea is more controversial: to hold IPMC votes to admit all significant committers to those projects to the IPMC itself. The purpose of this concept is to allow those who best know the codebase to provide IPMC oversight over it, especially as it pertains to releases. Would still like this to be an opt-in, where any existing PMC member interested in helping with the Incubator could request membership and be added after 72 hours (expanding ASF member rules to apply to all PMC members.) For committers (non-PMC members), I'd want an existing IPMC or PMC member nominate the person to the IPMC and require a 72hr lazy consensus, since IPMC members are expected to mentor and teach new podlings about the Apache way. By PMC you mean PPMC? i am confused. I welcome your comments, criticisms, and other feedback. Thanks. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: an experiment
Ant, My personal opinion (and i am hoping!) was that such individuals from ppmc's who end up in ipmc would help build bridges between podlings and will help get lessons learned (when any ppmc has issues/problems/roadblocks) back to their ppmc. This is one area where i've seen people struggle, folks from different projects learning the same lessons the hard way. I am not too worried about binding vote one podling ppmc member have over another podling's release. the binding is for me a legal thing (as in we need 3 binding ipmc votes for a release). -- dims On 08/11/2010 06:16 PM, ant elder wrote: On Wed, Aug 11, 2010 at 6:45 PM, Joe Schaeferjoe_schae...@yahoo.com wrote: The second idea is more controversial: to hold IPMC votes to admit all significant committers to those projects to the IPMC itself. The purpose of this concept is to allow those who best know the codebase to provide IPMC oversight over it, especially as it pertains to releases. Without some more explanation I'm not that convinced about doing that. The main purpose of the IPMC is to vote on the graduation of poddlings, why should some random ASF poddling newbie get a binding vote on the graduation of _any_ poddling? I'm guessing the motivation for this proposal is not to give poddling committers binding votes on other poddling graduations but to give them binding votes on their own poddling activities, and that i agree with. The things they need binding votes on is their committer votes, ppmc votes (they already have that), and release votes - lets just give them those. ...ant - 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: an experiment
Joe, Can they not +1 it either? :) seriously, it would be a bit hard to track 2 levels of ipmc members -- dims On 08/11/2010 07:24 PM, Joe Schaefer wrote: - Original Message From: Davanum Srinivasdava...@gmail.com To: general@incubator.apache.org Sent: Wed, August 11, 2010 6:28:17 PM Subject: Re: an experiment Ant, My personal opinion (and i am hoping!) was that such individuals from ppmc's who end up in ipmc would help build bridges between podlings and will help get lessons learned (when any ppmc has issues/problems/roadblocks) back to their ppmc. This is one area where i've seen people struggle, folks from different projects learning the same lessons the hard way. Good point. I am not too worried about binding vote one podling ppmc member have over another podling's release. the binding is for me a legal thing (as in we need 3 binding ipmc votes for a release). I think ant is more concerned about graduation votes. We could simply write a new rule that podling committers on the IPMC brought in through my initiative MUST ABSTAIN from graduation votes. I don't think the board would be the least bit upset if we did that. - 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] Deltacloud Project
+1 On Thu, May 13, 2010 at 12:15 AM, Luciano Resende luckbr1...@gmail.com wrote: On Wed, May 12, 2010 at 5:45 PM, David Lutterkort lut...@redhat.com wrote: Hi all, after the discussion so far [1], I'd like to put Detlacloud for a vote for acceptance into the Apache Incubator according to the proposal[2] I _think_ I've added everybody who expressed interest in being a mentor or initial committer to the proposal - if I have forgotten anybody, please holler. Please reply to this mail with your vote. David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c1273174879.7253.99.ca...@avon.watzmann.net%3e [2] http://wiki.apache.org/incubator/DeltacloudProposal +1 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Carl, if you need additional mentors, count me in. thanks, dims On Fri, May 7, 2010 at 9:18 AM, Carl Trieloff cctriel...@redhat.com wrote: On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
+1 from me -- dims Sent from my iPhone On May 6, 2010, at 6:08 PM, Craig L Russell craig.russ...@oracle.com wrote: +1 Craig On May 6, 2010, at 12:41 PM, David Lutterkort wrote: Hi, I would like to propose the Deltacloud API[1] for addition to the Apache incubator. I have added the initial proposal to the Wiki[2]; it is also included below for convenience. There are a few additional people that have expressed interest in becoming initial committers; I am waiting for their express consent to list them as committers, and will add them to the Wiki as I get that. We are looking forward to any and all feedback and/or questions on the proposal. We already have two mentors, but would very much welcome additional volunteers to help steer Deltacloud through the incubation process. David [1] http://deltacloud.org/ [2] http://wiki.apache.org/incubator/DeltacloudProposal Deltacloud, a cross-cloud web service API = Abstract Deltacloud defines a web service API for interacting with cloud service providers and resources in those clouds in a unified manner. In addition, it consists of a number of implementations of this API for the most popular clouds. Proposal * Define a REST-based API for managing and manipulating cloud resources in a manner that isolates the API client as much as possible from the particulars of specific cloud API's * Provide an open API definition for cloud providers for their IaaS clouds and a basis on which PaaS providers can layer their offering * Provide image management and directory capabilities as part of the API * The current implementation allows instance lifecycle management (create, start, stop, destroy, reboot), and querying of related resources like available images, instance sizes, and allowed instance actions for a number of public and private clouds * Currently supported are Amazon EC2, Eucalyptus, Rackspace, RimuHosting, GoGrid, OpenNebula, and RHEV-M * Future enhancements should broaden the scope of the API to include networking, firewalling, authentication, accounting, and image management Background -- An important issue for cloud users is that of avoiding lock-in to a specific cloud. By providing a cross-cloud API for infrastructure-as-a-service (IaaS) clouds, Deltacloud addresses this concern and strives to provide the best possible API for writing cloud-management applications that can target multiple clouds. There are also no efforts currently to define a truly open-source cloud API, one for which there is a proper upstream, independent of any specific cloud provider. Deltacloud API strives to create a community around building an open-source cloud API in a manner that fully allows for tried-and-true open source mechanisms such as user-driven innovation. By providing a web-service API, Deltacloud is language agnostic, and one of its subordinated goals is to provide a practical vocabulary for talking about IaaS cloud resources and operations on them. Rationale - IaaS clouds provide numerous advantages to their users, for example, making provisioning new servers more agile. If users directly use the 'native' cloud API's, they risk locking themselves in to the API of a specific cloud provider. There is therefore a strong need for an API that can be used across a wide range of public and private clouds, and that can serve as the basis for developing cloud management applications; in contrast to several existing language-specific efforts in this direction, Deltacloud is conceived as a web service. This will allow the project to attract a broad community of users of the API and cloud providers interested in offering a truly open-source API, with a proper upstream community. We strongly believe that the best way to drive such an API effort is by developing the API and open-source implementations of the API side- by-side. Initial Goals - Deltacloud is an existing open source project; initially started by Red Hat, it has attracted a number of outside contributors. We look at moving this project to the ASF as the next step to broaden the community, and put the project on solid footing since the ASF governance model is well suited for the Deltacloud project goals. The ASF is a great location for Deltacloud to build a community and will benefit from ASL licensing. Current Status -- Deltacloud API is licensed under the LGPL: * Deltacloud Website (http://deltacloud.org) There are two projects hosted there: the API under consideration here and the Aggregator (not part of this proposal, though also open source) * Deltacloud git repository (http://git.fedorahosted.org/git/?p=deltacloud/core.git;a=summary ) * Deltacloud mailing lists - users (https://fedorahosted.org/mailman/listinfo/deltacloud- users) - developers
Re: [VOTE] Accept Whirr for Incubation
support in the cloud. Whirr will build cloud components for several Apache projects, such as Hadoop, HBase, !ZooKeeper, Cassandra, and hopefully more. == Known Risks == === Orphaned products === There is a risk that Whirr will not gain adoption. However, the current Hadoop scripts seem to be fairly widely used. The small number of initial committers is also a risk, although by starting the project it is expected that new contributors will quickly be attracted to the project and help it grow. === Inexperience with Open Source === The initial code comes from Hadoop where it was developed in an open-source, collaborative way. All the initial committers are committers on other Apache projects, and are experienced in working with new contributors. === Homogenous Developers === The initial set of committers is from a diverse set of organizations, and geographic locations. They are all experienced with developing in a distributed environment. === Reliance on Salaried Developers === It is expected that Whirr will be developed on salaried and volunteer time, although all of the initial developers will work on it mainly on salaried time. === Relationships with Other Apache Products === Whirr will depend on many other Apache Projects as already mentioned above (e.g. Hadoop, !ZooKeeper). If the project develops some common infrastructure then it is possible that it becomes a dependency on a project that wishes to use that infrastructure for running in the cloud. === A Excessive Fascination with the Apache Brand === We think that Whirr will benefit from the community sharing ideas and best practices for running cloud services. The ASF does a great job at building communities, which is why we want to build Whirr at Apache. == Documentation == Information on the current scripts and general background can be found at * http://wiki.apache.org/hadoop/AmazonEC2 * http://archive.cloudera.com/docs/ec2.html * http://hbase.s3.amazonaws.com/hbase/HBase-EC2-HUG9.pdf * http://www.slideshare.net/steve_l/new-roles-for-the-cloud == Initial Source == * http://svn.apache.org/viewvc/hadoop/common/trunk/src/contrib/cloud/ * http://github.com/tomwhite/whirr == Source and Intellectual Property Submission Plan == The initial source is already in an Apache project's SVN repository (Hadoop), so there should be no action required here. == External Dependencies == The existing external dependencies all have Apache compatible licenses: boto (MIT), libcloud (Apache 2.0), simplejson (MIT). Jclouds is not a dependency of the current source, but it is Apache 2.0 licensed, so it will be possible to use it in the future if required. == Cryptography == Whirr uses standard APIs and tools for SSH and SSL. == Required Resources == === Mailing lists === * whirr-private (with moderated subscriptions) * whirr-dev * whirr-commits * whirr-user === Subversion Directory === * https://svn.apache.org/repos/asf/incubator/whirr === Issue Tracking === * JIRA Whirr (WHIRR) === Other Resources === The existing code already has unit and integration tests so we would like a Hudson instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committers == * Tom White (tomwhite at apache dot org) * Andrew Purtell (apurtell at apache dot org) * Johan Oskarsson (johan at apache dot org) * Steve Loughran (stevel at apache dot org) * Patrick Hunt (phunt at apache dot org) == Affiliations == * Tom White, Cloudera * Andrew Purtell, Trend Micro * Johan Oskarsson, Twitter * Steve Loughran, HP Labs * Patrick Hunt, Yahoo! == Sponsors == === Champion === * Tom White === Nominated Mentors === * Doug Cutting * Tom White * Steve Loughran === Sponsoring Entity === * Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Traffic Server as a TLP
+1 On Mon, Apr 19, 2010 at 3:29 PM, Noel J. Bergman n...@devtech.com wrote: +1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Termination of WSRP4J podling
+1 On Wed, Apr 14, 2010 at 3:10 AM, ant elder ant.el...@gmail.com wrote: +1 ...ant On Wed, Apr 14, 2010 at 1:37 AM, Ate Douma a...@douma.nu wrote: The Portals PMC as Sponsor of the WSRP4J podling as well as the project community itself has voted [1,2] positive [3] to terminate the podling due to lack of interest to continue the project. I would like to call the Incubator PMC to ratify this decision. Please vote on terminating the WSRP4J podling: [ ] +1, terminate WSRP4J [ ] -1, do not terminate WSRP4J Here's my +1 Regards, Ate [1] http://mail-archives.apache.org/mod_mbox/portals-general/201004.mbox/%3c4bbe524b.4090...@douma.nu%3e [2] http://mail-archives.apache.org/mod_mbox/portals-wsrp4j-user/201004.mbox/%3c4bbe524b.4090...@douma.nu%3e [3] http://mail-archives.apache.org/mod_mbox/portals-general/201004.mbox/%3c4bc500fa.6060...@douma.nu%3e - 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 -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Subversion podling for graduation
+1 On Fri, Feb 12, 2010 at 1:00 PM, Jim Jagielski j...@jagunet.com wrote: Looks like the trademark issues are being resolved, so +1 ! On Feb 11, 2010, at 11:08 PM, Greg Stein wrote: Hello all, I started a discussion thread a week-ish ago to seek out issues for Subversion's graduation. The couple bits that were raised[1] have been handled, I believe. So with that said, I am unaware of any potential showstoppers, and would like to request a vote for graduating the Subversion podling. Should this result in a successful vote, I will put a resolution before the Board (for its Feb 17 mtg) to construct a new Subversion PMC. Please vote: [ ] +1 Graduation [ ] -1 Hold, and continue incubating Thanks! Cheers, -g [1] incubator status page, and java bindings package name - 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 -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Cassandra to an Apache TLP
+1 -- dims On 01/31/2010 10:27 PM, Craig L Russell wrote: +1 Craig On Jan 28, 2010, at 11:59 AM, Eric Evans wrote: Greetings, We took the feedback from the earlier discussion[1] here and added our active mentors to the proposed PMC, (for a total of 7 people), then ran that through a new community vote[2]. [1] http://thread.gmane.org/gmane.comp.apache.incubator.general/24427 [2] http://thread.gmane.org/gmane.comp.db.cassandra.user/2157 There didn't seem to be any other feedback, so I'd like to start an official vote to recommend graduation of Apache Cassandra to a top-level project. Please cast your vote: [ ] +1 to recommend Cassandra's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, (because...) The vote will be open for 72 hours. Thanks, -- Eric Evans eev...@rackspace.com cassandra-resolution.txt - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp! - 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: Fwd: [VOTE] Copyright issue (ESME-47)
+1 from me -- dims On 01/19/2010 06:15 AM, Bertrand Delacretaz wrote: Forwarding to Incubator PMC, your votes are welcome (and sorry about re-voting...we at ESME changed our minds slightly) -- Forwarded message -- From: Anne Kathrine Petterøe yoji...@gmail.com Date: Tue, Jan 19, 2010 at 12:10 PM Subject: [VOTE] Copyright issue (ESME-47) To: esme-...@incubator.apache.org PPMC and IPMC, please re-vote on the following regarding copyright issue ESME-47. 1. The Apache license block will be added at the beginning of each source file: /* Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the License); you may not use this file except in compliance with * the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ 2. The Apache License block will be followed by a legacy comment (Only in files where the WorldWide Conferencing notice currently exists, except any files where user dpp has not made any contribution): /* * Portions Copyright 2009 WorldWide Conferencing, LLC */ 3. A NOTICE file with the following text will be added: Apache Foo Incubating Code Copyright 2010 The Apache Software Foundation. This product includes software developed at The Apache Software Foundation (http://www.apache.org/). For details, please see this legal-discuss mailing list thread: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201001.mbox/%3cf767f0601001110028n54d85d03xaf703119fa08d...@mail.gmail.com%3e - 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 Apache Shindig as an Apache Top Level Project
+1 -- dims On 01/14/2010 06:58 AM, ant elder wrote: +1 ...ant On Thu, Jan 14, 2010 at 11:41 AM, Vincent Siveton vsive...@apache.org wrote: Hi, Thanks for the positive feedback on the proposal to graduate Shindig as a TLP [1]. I would like to start an official vote to recommend the graduation of Apache Shindig as a Top Level Project to the Board. To that end I have prepared the resolution for the Board below to be presented for consideration at the upcoming Board meeting. Community graduation vote thread: http://shindig-dev.markmail.org/message/c47amdxjtntkjij5 Please cast your vote: [ ] +1 to recommend Shindig's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, because ... The vote will be open for 72 hours. Cheers, Vincent [1] http://apache.markmail.org/message/qvpyymihv6gyh5a7 --- Begin Proposed Board Resolution --- 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 the implementation of an OpenSocial container and OpenSocial API 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 Shindig PMC, is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Shindig Project be and hereby is responsible for the creation and maintenance of software related to the OpenSocial API specifications, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Shindig be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of Apache Shindig, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Shindig PMC; 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 Shindig PMC: * Ian Boston (ieb at apache dot org) * Kevin Brown (etnu at apache dot org) * Chris Chabot(chabotc at apache dot org) * Chico Charlesworth (chico at apache dot org) * Cassie Doll (doll at apache dot org) * Evan Gilbert (evan at apache dot org) * John Hjelmstad (johnh at apache dot org) * Paul Lindner (lindner at apache dot org) * Daniel Peterson (dpeterson at apache dot org) * Louis Ryan (lryan at apache dot org) * Henning Schmiedehausen (henning at apache dot org) * Vincent Siveton (vsiveton at apache dot org) * Upayavira (upayavira at apache dot org) * Adam Winer (awiner at apache dot org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Paul Lindner be appointed to the office of Vice President, Apache Shindig, 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 Apache Shindig be and hereby is tasked with the migration and rationalization of the Apache Incubator Shindig podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Shindig podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Remove me from commiters
Jason, Please clarify. Did you get any email from anyone involved in wink? thanks, dims On Tue, Nov 24, 2009 at 4:04 AM, Jason Dillon ja...@planet57.com wrote: Sorry folks, after my massive falling out with IBM I'm unable to help out with any more wink development. I wish things had turned out differently, mostly on the heads of IBM... no chance I will *ever* work with them again. I wish you all the best, but I am afraid I can not continue working on this project. Sorry it has taken so long, got some threatening emails from IBM on the subject, so I kept quiet. But I feel its not fair, so i wanted to officially resign. I hope that does not have any effect or your graduation. Sorry, --jason - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Remove me from commiters
Paul, Please don't jump the gun - Do you feel that the project needs further independent mentors? There is no communication from Jason to the ppmc mailing list or the priv...@incubator mailing list and i certainly haven't received any personal email. Yes, If anyone wants to help us with mentoring, Very welcome. Just not like this. thanks, dims On Tue, Nov 24, 2009 at 5:27 AM, Paul Fremantle pzf...@gmail.com wrote: Jason It is very worrying that you got threatening emails from anyone involved in the project. Have you brought this up with the mentors? Do you feel that the project needs further independent mentors? Paul On Tue, Nov 24, 2009 at 9:04 AM, Jason Dillon ja...@planet57.com wrote: Sorry folks, after my massive falling out with IBM I'm unable to help out with any more wink development. I wish things had turned out differently, mostly on the heads of IBM... no chance I will *ever* work with them again. I wish you all the best, but I am afraid I can not continue working on this project. Sorry it has taken so long, got some threatening emails from IBM on the subject, so I kept quiet. But I feel its not fair, so i wanted to officially resign. I hope that does not have any effect or your graduation. Sorry, --jason - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Remove me from commiters
Thanks for clarifying Jason. Am very sorry to hear about this. If i can be of any help, please let me know. -- dims On 11/24/2009 07:49 AM, Jason Dillon wrote: No, this was all internal to IBM not to do with any Apache commiters or members. --jason On Nov 24, 2009, at 5:27 PM, Paul Fremantle wrote: Jason It is very worrying that you got threatening emails from anyone involved in the project. Have you brought this up with the mentors? Do you feel that the project needs further independent mentors? Paul On Tue, Nov 24, 2009 at 9:04 AM, Jason Dillonja...@planet57.com wrote: Sorry folks, after my massive falling out with IBM I'm unable to help out with any more wink development. I wish things had turned out differently, mostly on the heads of IBM... no chance I will *ever* work with them again. I wish you all the best, but I am afraid I can not continue working on this project. Sorry it has taken so long, got some threatening emails from IBM on the subject, so I kept quiet. But I feel its not fair, so i wanted to officially resign. I hope that does not have any effect or your graduation. Sorry, --jason - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com Oxygenating the Web Service Platform, www.wso2.com - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Remove me from commiters
Paul, No apologies needed :) All of us are certainly trying to do the best we can given our life experiences. thanks, -- dims On 11/24/2009 08:16 AM, Paul Fremantle wrote: My apologies. I misunderstood Jason's note. And I certainly wasn't trying to criticize you. only trying to put myself in the place of someone having an argument with IBM and having two IBM employees as mentors on the project. The mentors could be fantastic and independent as indeed you are, but it still might be an issue. However, I can see that in this case it wasn't an issue. Best, as ever Paul On Tue, Nov 24, 2009 at 12:11 PM, Davanum Srinivasdava...@gmail.com wrote: Paul, Please don't jump the gun - Do you feel that the project needs further independent mentors? There is no communication from Jason to the ppmc mailing list or the priv...@incubator mailing list and i certainly haven't received any personal email. Yes, If anyone wants to help us with mentoring, Very welcome. Just not like this. thanks, dims On Tue, Nov 24, 2009 at 5:27 AM, Paul Fremantlepzf...@gmail.com wrote: Jason It is very worrying that you got threatening emails from anyone involved in the project. Have you brought this up with the mentors? Do you feel that the project needs further independent mentors? Paul On Tue, Nov 24, 2009 at 9:04 AM, Jason Dillonja...@planet57.com wrote: Sorry folks, after my massive falling out with IBM I'm unable to help out with any more wink development. I wish things had turned out differently, mostly on the heads of IBM... no chance I will *ever* work with them again. I wish you all the best, but I am afraid I can not continue working on this project. Sorry it has taken so long, got some threatening emails from IBM on the subject, so I kept quiet. But I feel its not fair, so i wanted to officially resign. I hope that does not have any effect or your graduation. Sorry, --jason - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - 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] Accept Apache Clerezza into the incubator
+1, bring Clerezza into Incubator On 11/23/2009 01:32 PM, Reto Bachmann-Gmür wrote: Please vote on accepting Apache Clerezza for incubation at the Apache Incubator. The full proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal http://wiki.apache.org/incubator/AceProposal. We ask the Incubator PMC to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross, Karl and Reinhard volunteering to be Mentors. Please cast your votes: [ ] +1, bring Clerezza into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Clerezza into Incubator, because... The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. - - - - - - - - - - Abstract Clerezza is an OSGi-based modular application and set of components (bundles) for building RESTFul Semantic Web applications and services. Proposal Clerezza can be used as a platform providing all the compile and runtime requirement for building semantic applications, or used as individual bundles within an OSGi framework, e.g. Apache Sling, Apache ServiceMix, or the Eclipse platform. Clerezza provides: * An API modeling the W3C RDF standard without any vendor specific additions. * Adapter for various triple stores including Sesame, Jena TDB, and Mulgara. * Front-End adaptors, currently to run applications written against the Jena API. Support for RDF2Go is planned. * A JAX-RS implementation designed to work in an OSGi environment and allowing to provide Root-Resources as OSGi services. * Web access to RDF graphs, including a SPARQL-Endpoint. * Extensions to JAX-RS allowing to bind Root-Resource classes to specific RDF-Types rather than to URI-Paths. * Templating mechanism (Renderlets) allowing to render RDF resources returned by JAX-RS resource methods to various formats * Support for Scala for writing modules, ScalaServerPages to easily write renderlets, DSL for accessing graphs. * Authentication and authorization based on JAAS and OSGi Conditional Permission Admin * Support for user bundles: Users can have a permission to upload their own sandboxed bundles. The URI space these bundles are allowed to register their JAX-RS resources can be limited with a prefix. * Scripting: Scripting based on javax.script (currently support for JRuby and Scala) * Documentation: Bundles can provide their documentation in RDF. These are used for online documentation as well as for building Maven sites (with a Maven reporting plugin) The RDF abstraction layer can be used independently of other aspects of Clerezza. It allows applications to be written regardless the used backend. In its purpose, it is similar to RDF2Go, but provides a significantly more modular interface allowing e.g. to independently switch the storage, querying, or serialization layer. Furthermore, it doesn't introduce concepts alien to the RDF model such as blank node labels, but is in its core strictly limited to RDF semantics. The JAX-RS implementation can also be used independently of any other components. It allows OSGi services to provide a RESTful interface to their methods. By being based on wymiwyg WRHAPI, it can run both on the default OSGi Web Service as well as on a jetty instance listening on a different port. Background The current web trends focusing on information sharing, interoperability and collaboration. Therefore the behaviour of the end-user has changed over the last years: end-users not only consuming information they also producing content anytime anywhere - in contrast to non-interactive websites where users are limited to the passive viewing of information that is provided to them. Since the end-users are sensitized to the possibilities of the web the web application requirements increases. Examples of such applications are social-networking sites, wikis, blogs and mashups. The REST paradigm and Semantic Web technologies support these trends and form the basis for the upcoming Web of Data (a.k.a. linked data, Web 3.0). They change the paradigms for developing complex Web applications. Clerezza allows to develop applications that integrate perfectly in the Semantic Web providing all accessible resources in machine understandable formats without imposing additional burdens on the developer. Additionally, thanks to the flexibility of the RDF model used as back-end, some tedious database related tasks required for traditional Web application development are no longer needed. Rationale Most Web application framework are not designed to leverage the full power of HTTP but often try to reproduce non Web design patterns for the Web environment. In general, application frameworks are oriented towards relational or hierarchical data structures. While attempts to overcome this such as Drupal have become very popular, they do not at their core base on the stack of Semantic Web standards. Clerezza will prove that
Re: Explanation of the extra pain (was: Two other issues to discuss for Subversion)
I agree with Joe. thanks, dims On 11/13/2009 03:50 PM, Joe Schaefer wrote: - Original Message From: Greg Steingst...@gmail.com To: general@incubator.apache.org Sent: Fri, November 13, 2009 12:23:04 PM Subject: Explanation of the extra pain (was: Two other issues to discuss for Subversion) Okay. I *think* that is pretty much the background/rationale (please refine/add/etc). But that said, we recognize the pain. Are there *other* ways that we can achieve the same effects without the double-move? (of lists and repos) Are there avenues of communication that Incubator can manage? For example, rather than putting @incubator.apache.org in all the mailing lists, can it have a mandatory header/footer for each message? Can the repository have a big README.INCUBATION at the root? The Incubator still has control of all releases, so it still can manage branding on all releases. Can we tweak ViewVC to dynamically insert a header This repository area is part of an Apache Incubator podling. etc etc. I am opposed to changing the typical resource layout for an incubating project. Release management is one of the most important aspects of code management at Apache, and frankly there are incubating projects (eg Thrift) that have no clue how that works. Incubator is not only a training ground, it is a proving ground too. We have low barriers to entry because we make clear to the public that these projects are only granted provisional access to the brand. - 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: Insanity. Apache Incubator should be about education
Jukka, Agreed. thanks, dims On 11/11/2009 01:47 AM, Jukka Zitting wrote: Hi, On Tue, Nov 10, 2009 at 11:53 PM, Davanum Srinivasdava...@gmail.com wrote: Jukka, Not so sure... because that dist may contain code that we may not allow. Personally I'd be happy with a plan from the Subversion team that shows how they're going to address any issues that may be raised in the review. 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: [PROPOSAL][VOTE] Subversion
Brian, Do you mind sending an email to pmcs AT apache.org to inform them that they should be using this new version of Apache pom? And any other additional instructions needed to enable this feature to work. thanks, dims On 11/11/2009 03:51 PM, Brian Fox wrote: What is happening in some Java projects, via Maven's release plugin, is disturbing since the source release only exist in the subversion repository This problem has been solved and is no longer valid. Any repetition of the old news is total fud. We have for many months now been providing proper source releases for EVERYTHING in the maven project and just recently promoted the same to the Apache pom making it automatic for any Apache project with the new pom. See links below for more info: http://old.nabble.com/Update-on-ASF-Release-requirements-ts23379350.html#a23379350 http://old.nabble.com/-VOTE--Apache-%28parent-POM%29-version-7-ts26221188.html As far as I understand the requirements, this issue is completely resolved so lets stop saying that Maven produces incorrect releases. It was never an issue with the tool itself, but as a project we've fixed it and are sharing it to all projects at Apache using Maven. - 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: [PROPOSAL][VOTE] Subversion
Dan, It's up to each project to get their releases correct - Yes. But not everyone hangs out on the d...@maven or gene...@incubator. Hence the request to broadcast. I really don't understand the why? - No one is trying to mandate using a specific pom across all PMC(s). Just the fact that there was a problem that was actively worked on and fixed and the proposed solution. Basically telling pmcs take it or leave it. At the very least pay attention that the jars that they release should be build-able using the source zip(s). -- dims On 11/11/2009 05:22 PM, Daniel Kulp wrote: On Wed November 11 2009 4:52:23 pm Davanum Srinivas wrote: Brian, Do you mind sending an email to pmcs AT apache.org to inform them that they should be using this new version of Apache pom? And any other additional instructions needed to enable this feature to work. Why? It's up to each project to get their releases correct. That version of the Apache pom isn't required to get the needed source bundles created. I know for CXF, the current parent poms don't work at all and thus we SHOULDN'T use it. Dan thanks, dims On 11/11/2009 03:51 PM, Brian Fox wrote: What is happening in some Java projects, via Maven's release plugin, is disturbing since the source release only exist in the subversion repository This problem has been solved and is no longer valid. Any repetition of the old news is total fud. We have for many months now been providing proper source releases for EVERYTHING in the maven project and just recently promoted the same to the Apache pom making it automatic for any Apache project with the new pom. See links below for more info: http://old.nabble.com/Update-on-ASF-Release-requirements-ts23379350.html# a23379350 http://old.nabble.com/-VOTE--Apache-%28parent-POM%29-version-7-ts26221188 .html As far as I understand the requirements, this issue is completely resolved so lets stop saying that Maven produces incorrect releases. It was never an issue with the tool itself, but as a project we've fixed it and are sharing it to all projects at Apache using Maven. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][VOTE] Subversion
I think this is a pretty important issue worth spamming but whatever -- dims On 11/11/2009 05:43 PM, Daniel Kulp wrote: Actually, the vote was kind of withdrawn to update it to new descriptors. Thus, its not available yet. In anycase, no need to spam all the PMCs, especially those not using Maven. Just keep an eye on the annou...@maven list. When available, it will be announced there. Dan On Wed November 11 2009 4:52:23 pm Davanum Srinivas wrote: Brian, Do you mind sending an email to pmcs AT apache.org to inform them that they should be using this new version of Apache pom? And any other additional instructions needed to enable this feature to work. thanks, dims On 11/11/2009 03:51 PM, Brian Fox wrote: What is happening in some Java projects, via Maven's release plugin, is disturbing since the source release only exist in the subversion repository This problem has been solved and is no longer valid. Any repetition of the old news is total fud. We have for many months now been providing proper source releases for EVERYTHING in the maven project and just recently promoted the same to the Apache pom making it automatic for any Apache project with the new pom. See links below for more info: http://old.nabble.com/Update-on-ASF-Release-requirements-ts23379350.html# a23379350 http://old.nabble.com/-VOTE--Apache-%28parent-POM%29-version-7-ts26221188 .html As far as I understand the requirements, this issue is completely resolved so lets stop saying that Maven produces incorrect releases. It was never an issue with the tool itself, but as a project we've fixed it and are sharing it to all projects at Apache using Maven. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][VOTE] Subversion
Thanks Brian! On 11/11/2009 06:22 PM, Brian Fox wrote: On Wed, Nov 11, 2009 at 5:50 PM, Davanum Srinivasdava...@gmail.com wrote: I think this is a pretty important issue worth spamming but whatever I think it's worth noting, I've had several projects asking for it to be available so they can use it and ditch their homebrew solutions. When it's promoted to the repo, I'll send a notice. Dan, perhaps on the maven dev list, I'd like to understand why it won't work for cxf...but fwiw, we made it possible to replace the default descriptor bundle with your own so hopefully even if we can't make the descriptor work for cxf, the rest is still applicable. - 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] Request for Waiver of Make a Release requirement for Incubator graduation
I agree with the following, i don't think a waiver is needed right now... This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. thanks, dims On 11/10/2009 01:49 PM, ant elder wrote: On Tue, Nov 10, 2009 at 6:17 PM, Greg Steingst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven prtingojects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html -0 I'm not at all familiar with how the Subversion project works so as an IPMC member I don't see how I can decide this before they've even started incubating. This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. ...ant - 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: Two other issues to discuss for Subversion
Personally i am ok with #1, but i am not sure if svn switch --relocate too much of a burden for you guys :) On 11/10/2009 02:27 PM, Greg Stein wrote: There are two other issues to discuss for the Subversion podling: * moving the mailing lists directly to @subversion.apache.org * placing the source code at /subversion/ rather than /incubator/subversion/ We are hoping to minimize overall disruption to the community with a move to incubator space, then a move to apache space. Cheers, -g - 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: Two other issues to discuss for Subversion
Now that you have explained :) +1 from me. -- dims On 11/10/2009 02:43 PM, Greg Stein wrote: LOL Well... the problem is that an svn mv from /incubator/subversion/ to /subversion/ introduces an artificial breakage in the history. It is actually quite disruptive for tracking history (which is very important to us). (and yes, because of that history issue, I personally have no problem putting podlings at the top-level in our repository; it *is* version control, and we can always remove failed podlings' code from anywhere) Cheers, -g On Tue, Nov 10, 2009 at 14:38, Davanum Srinivasdava...@gmail.com wrote: Personally i am ok with #1, but i am not sure if svn switch --relocate too much of a burden for you guys :) On 11/10/2009 02:27 PM, Greg Stein wrote: There are two other issues to discuss for the Subversion podling: * moving the mailing lists directly to @subversion.apache.org * placing the source code at /subversion/ rather than /incubator/subversion/ We are hoping to minimize overall disruption to the community with a move to incubator space, then a move to apache space. Cheers, -g - 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 - 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: Insanity. Apache Incubator should be about education
Jukka, Not so sure... because that dist may contain code that we may not allow. Greg, Is there any code in there that is not Apache compatible? i see some in the contrib section... http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn-clean thanks, dims On 11/10/2009 04:25 PM, Jukka Zitting wrote: Hi, On Tue, Nov 10, 2009 at 8:28 PM, Greg Steingst...@gmail.com wrote: Unfortunately, some documentation needs to be brought in sync. See: http://incubator.apache.org/guides/graduation.html#checklist I'm nitpicking, but even there we only ask the podlings to demonstrate ability to create Apache releases. Per Joe, I think it makes sense to run podlings through a release to teach them the ropes, rather than lump that onto Infrastructure. But I also believe we should provide waivers when appropriate. Fair enough. As an alternative, how about submitting http://subversion.tigris.org/downloads/subversion-1.6.6.tar.bz2 for IPMC review? That should require no extra work from and no special waivers for Subversion. 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: [PROPOSAL][VOTE] Subversion
+1 from me. On 11/04/2009 03:36 PM, Matthias Wessendorf wrote: +1 :-) On Wed, Nov 4, 2009 at 9:12 PM, Greg Steingst...@gmail.com wrote: Subversion is a version control system. You probably know it well as it is the version control system employed by the Apache Software Foundation. The Subversion project would like to join the Apache Software Foundation to remove the overhead of having to run its own corporation. The Subversion project is already run quite like an Apache project, and already counts a number of ASF Members amongst its committers. Work on Subversion was originally started at CollabNet; Karl Fogel was hired in January 2000. Jim Blandy, at RedHat, already had an initial design for the storage system, which was incorporated into the FS design. In February Brian Behlendorf invited Greg Stein to contribute his WebDAV experience to Subversion. Ben Colins-Sussman was hired in April 2000 to work on the project. In that same month the first all hands meeting was held, where a number of interested people came together to talk about the project. Subversion was run as an open source project since the early days. Now, more than nine years later, it retains a healthy community, and has a good number of committers. In the life span of Subversion, several committers have switched employers and have maintained involvement. The committership is diverse, both geographically as well as in terms of employment. The equivalent of the PMC consists of all the full committers to the Subversion project (currently around 55 people). The community uses the voting process also used at the ASF. Releases are signed off by gathering votes/digital signatures of each committer who verified the release candidate. We feel the ASF and Subversion communities are very compatible, witness the cross interest that already exists. There is both a vibrant developer as well as a large and active user community. Technology-wise, Subversion builds on APR, and implements two Apache HTTP Server modules. Note that Subversion has a number of related projects, which are not part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse). More information on Subversion can be found at http://www.subversion.org/ and http://subversion.tigris.org/. The Subversion Corporation has a license to all source code, and has CLAs on file for nearly all it's committers. That is, we have all but one or two full committers, and some percentage of partial committers. We have a number of *user-configurable* dependencies which are not compatible with the AL: - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL. (An alternative HTTP client library, libsvn_ra_serf uses the Serf library under ALv2.) - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is under Academic Free License 2.1 or=GPL-2. (This support is for integration for KDE and GNOME's authentication providers.) - libintl (This library provides translation support for systems without a proper internationalization library.) - BDB (This is used by the libsvn_fs_base system which stores its data in BDB; an alternative repository system called fs_fs does not have this dependency.) --- Required Resources - Mailing lists - dev - issues - users - private - commits - announce - breakage (see http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552) - We will work with the Infrastructure team to transfer the subscriber listings to the new destinations. - Subversion: - We have not made a decision whether we prefer Subversion should be imported into the main ASF Subversion repository or be hosted as a separate repository to enable early testing of the repository code. We intend to discuss this during the Incubation process before the code is imported. It is also understood that ASF infrastructure team may be willing to run custom pre-release Subversion server builds for the entire ASF, so this separate repository option may not be required. - The Subversion source code can be found at: http://svn.collab.net/repos/svn/. - Issue tracking - We haven't made a decision between JIRA or Bugzilla at this time and expect this decision to be made as part of the Incubation process. Our current issue tracking system uses Issuezilla (a fork of Bugzilla) and we have not yet decided whether we want to import our previous issues into the new system and will decide this in the course of the Incubation process. - Our current issue tracker is at http://subversion.tigris.org/issue-tracker.html. - Buildbot - We currently use buildbot across a number of platforms and configurations for automated builds and testing. Over time, we would like to migrate these services to Apache infrastructure where appropriate. - Our
Re: [VOTE] Accept Libcloud proposal for incubation
+1 from me. On 10/28/2009 04:17 PM, Bertrand Delacretaz wrote: [X ] +1 Accept Libcloud for incubation Looks cool, good luck! -Bertrand - 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] Accept Aries proposal for incubation
Folks, I see Niall, Leo, Jeremy, Robert, Bill and Guillaume respond to concerns from Jim and Niclas. It would be invaluable if any incubator PMC members with concerns (or without!) could help us as mentors during the incubation process. Here's the list of votes so far (see below). Noel, can you please chime in with your VOTE? I am hoping that other incubator PMC members who have not VOTE'd would cast their ballot as well thanks, dims Davanum Srinivas+1 Craig L Russell +1 Ant Elder +1 Daniel Kulp +1 Matthias Wessendorf +1 Kevan Miller+1 James Strachan +1 Guillaume Nodet +1 Alan D. Cabrera +1 Luciano Resende +1 Carsten Ziegeler+1 Bill Stoddard +1 Niklas Gustavsson +1 Jim Jagielski -1 Niall Pemberton +1 Donald Woods+1 Joe Bohn+1 Daniel S. Haischt +1 Niclas Hedhman -1 Ralph Goers +1 Leo Simons +1 Robert Burrell Donkin +1 On 09/18/2009 04:50 AM, Robert Burrell Donkin wrote: On Fri, Sep 18, 2009 at 8:05 AM, Niclas Hedhmannic...@hedhman.org wrote: On Fri, Sep 18, 2009 at 1:27 AM, Bill Stoddardwgstodd...@gmail.com wrote: I am having a really difficult time getting my head around Jim and Niclas' objections that this is an umbrella project. I think Jim came up with a good lithmus test; If it is unclear what should NOT go into a project... So, when I read the proposal the second time, my interpretation is that there is no actual boundary, other than perhaps OSGi. If it was only specs, then I would support Richard's notion that the community should work towards Felix sub-project (which was a sore point), but the scope is enterprise OSGi, which is just about as wide as it gets. Perhaps the group as such has much better ideas on what they mean, fair enough, but then *I* would like to see it in the proposal. After all, it is very common around here that the proposal will become the basis for the project charter (if any), so *I* think it is better to address this early (and often ;-) )... it is not conventional here to insist on a set exit strategy before a proposal is approved. perhaps this innovation is one that should be considered but IMHO it's not really workable to do that this late in the acceptance process. targeting an exit as a felix sub-project would require the aries proposes to start again with approval from the felix proposal and so on. it may also prove controversial. i would also be worried about settling on exit as a felix sub-project now. i'm a big felix fan and think it runs very well. but i think there's a limit on how far it can scale without loosing it's cohesiveness as a community. i would like see felix continue to act as a home for cross cut OSGi components factored out of existing apache codebases. if there are going to be a large number of new OSGi specs with a distinctive enterprise identity (whatever that means) then i worry that the felix project may find themselves flooded and lose direction. i also worry that if no distinctive identity develops for enterprise specifications then aries is going to have scope issues. i'm not sure that this can be resolved right now: the specification process doesn't seem mature enough yet. but i don't see this as a reason to tell aries to come back later. code and community first. i would expect that the project reports include detail on the specifications they intend to implement and what progress has been made towards a tight definition of enterprise (whether as a distinctive group of specifications or a good description) - robert - 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] Accept Aries proposal for incubation
for further development: http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint * IBM will also contribute code for: o container-managed JPA support in an OSGi environment. o making OSGi services visible to Java EE components through JNDI. o packaging web components as bundles and a URL handler for recognizing and converting non-bundled Web components * We will also be soliciting implementations of other OSGi enterprise application-centric specifications. External Dependencies * Apache Ant http://ant.apache.org Apache License * Apache Commons http://commons.apache.org Apache License * Junit (Java unit test framework) http://junit.sourceforge.net CPL v1.0 license: http://junit.sourceforge.net/cpl-v10.html * Apache Felix (implementation of the OSGi Core and Compendium specifications - compliance level unknown) http://felix.apache.org Apache License (hosted by ASF). * Eclipse Equinox (compliant implementation of the OSGi Core Specification and Compendium specifications) http://eclipse.org/equinox/ Eclipse Public License * OpenJPA http://openjpa.apache.org Apache License * Serp http://serp.sourceforge.net/ BSD * Apache Geronimo http://geronimo.apache.org Apache License Required Resources Mailing lists aries-private (with moderated subscriptions) aries-dev aries-commits aries-user Subversion Directory http://svn.apache.org/repos/asf/incubator/aries Issue Tracking JIRA (ARIES) Web Site Confluence (Aries) Initial Committers Names of initial committers with affiliation and current ASF status: * Alan Cabrera (LinkedIn, ASF Member) * Alasdair Nottingham (IBM) * Andrew Osborne (IBM) * Bernd Kolb (SAP) * Carsten Ziegeler (Individual, ASF member) * Dan Kulp (Progress, ASF member) * David Bosschaert (Progress, ASF committer) * David Jencks (IBM, ASF member) * Dimo Stoilov (SAP) * Eoghan Glynn (Progress, ASF committer) * Graham Charters (IBM) * Guillaume Nodet (Progress, ASF member) * Hiram Chirino (Progress, ASF member) * Ian Robinson (IBM) * James Strachan (Progress, ASF member) * Jarek Gawor (IBM, ASF member) * Jean-Sebastien Delfino (IBM, ASF committer) * Jeremy Hughes (IBM, ASF committer) * Joe Bohn (IBM, ASF committer) * Lin Sun (IBM, ASF committer) * Kiril Mitov (SAP) * Mark Nuttall (IBM) * Niklas Gustavsson (individual, ASF committer) * Nikolai Tankov (SAP) * Oisin Hurley (Progress) * Peter Peshev (SAP) * Raymond Feng (IBM, ASF committer) * Rick McGuire (IBM, ASF committer) * Roman Roelofsen (ProSyst) * Sabine Heider (SAP) * Sergey Beryozkin (Progress, ASF committer) * Stuart McCulloch (individual, ASF committer) * Timothy Ward (IBM) * Todor Boev (ProSyst) * Valentin Mahrwald (IBM) * Violeta Georgieva (SAP) * Zoe Slattery (IBM) Affiliations The majority of the initial committers listed on the proposal initially are employed by IBM corp or Progress Software. One objective of the incubator is to attract a diverse community of contributors and we anticipate future contributors to have other affiliations. Indeed, since the proposal was initially posted, further initial committers have volunteered from SAP, ProSyst, LinkedIn and some individuals. Sponsors Champions Kevan Miller, Guillaume Nodet Nominated Mentors Guillaume Nodet, Davanum Srinivas (Dims), Kevan Miller Sponsoring Entity The incubator. Successful graduation from Incubator should result in Aries becoming a new TLP. - 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: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Hi Peter, Excellent! I am hoping that the champions - in this case Kevan Miller and Guillaume Nodet - will chime in on next steps. thanks, dims On 09/09/2009 01:45 PM, Peter Peshev wrote: Hi Jeremy, We from SAP would like to join and nominate six people for the proposed Aries project. What's the process - should I just add the six names on the wiki ? Maybe we could discuss this offline to not spam the whole mailing list. Unfortunately none of the suggested people from our side has experience in Apache project , but I hope that’s not an issue. Best Regards Peter Peshev On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hugheshugh...@apache.org wrote: Cross-pollination and help from the Felix community have been talked about several times and I absolutely welcome that. As such, please would Felix committers willing to spend time helping the (proposed) Aries podling add their names to the initial committer list on the proposal wiki [1]. This naturally extends beyond Felix committers. Apologies for x-post to d...@felix ... I wanted to attract as many as possible :-) [1] http://wiki.apache.org/incubator/AriesProposal Thanks, Jeremy 2009/9/5 Davanum Srinivasdava...@gmail.com: Karl, Please don't get me wrong. Felix is choice for an excellent *destination* TLP. The Incubator PMC itself was setup to take away the responsibility for training incoming folks from existing TLP(s). So my gut feeling is that we should allow the incubation process to go on and decide on destination and scope once the project is ready to graduate. I am sure the folks on the proposal would love to get any and every help they can get to graduate as well as on the technical front. Please do continue to provide help and guidance. thanks, dims On 09/05/2009 10:29 AM, Karl Pauls wrote: On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivasdava...@gmail.com wrote: Karl, There are *many* TLP(s) with overlapping scope as James Strachan pointed out earlier in the thread. I don't see the need to shoe horn a new community with new code into an existing TLP just because of scope. For all you know by the time they get out of the incubator their scope may change a bit (or more). I'm sorry if it looked like I wanted to shoe horn anything into felix. That wasn't my goal as for me it was a question of where I would like it to happen and as I said earlier already, not the end of the world if not. regards, Karl thanks, dims On 09/05/2009 04:31 AM, Karl Pauls wrote: The question is about the scope and goals of Aries and more specifically about the part where it is about being an umbrella for OSGi EE spec implementations where it has been argued that this could/should be done at felix - 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 - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Ralph, Not yet. Let's wait for the discussions to wrap up. thanks, dims On 09/06/2009 02:59 AM, Ralph Goers wrote: On Sep 5, 2009, at 10:36 AM, Niall Pemberton wrote: Voting against a bunch of people forming a new community here at the ASF is v.disappointing and goes against what IMO the ASF is all about. If the Felix community wants to get involved with their efforts then great, if not then don't try to block what they want to do. As others have said there are various options for graduation, but I think you've made Felix less rather than more likely by your antagonism to this proposal. I'm +1 to this proposal and hoping Felix members with shared interests get involved. Is this an actual vote thread to accept the proposal? Ralph - 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: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Richard, I did agree with you that Felix would make a great choice as a destination TLP. The situation with ServiceMix/Karaf is not the same as what is happening here with a new set of incoming committers and code. I sincerely do hope that cross-pollination happens even when the podling is in incubator. thanks, dims On Wed, Sep 2, 2009 at 3:30 PM, Richard S. Hallhe...@ungoverned.org wrote: * -1 for the portion of the proposal creating yet another community for implementing OSGi specs at Apache since the Felix community would happily welcome more contribution (just like recently occurred with ServiceMix members being accepted as Felix committers and PMC members for the Karaf subproject) On 09/06/2009 12:39 AM, Richard S. Hall wrote: I support the creation of a new community around an EE component model for OSGi and OSGi specs dependent upon this technology; however, I believe the Felix project is the best choice to work on independent OSGi specs since we have been doing it for years and it would guarantee cross-project collaboration. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Stuart, Thanks a ton. Please do join the aries mailing list(s) after we VOTE on (and hopefully accept) the proposal. All the action will shift there from this mailing list. thanks, dims On 09/05/2009 11:08 PM, Stuart McCulloch wrote: 2009/9/5 Davanum Srinivasdava...@gmail.com One more question, Will there be a problem of folks on d...@felix not being able or willing to participate in a new podling? (If the folks presenting this proposal do wish to start off as a podling) Personally speaking I'd be willing to help out where possible regardless of where it starts off. I doubt I'm experienced enough in the Apache Way to be a mentor, but having been on the OSGi Enterprise Expert Group in the past I am interested in seeing solutions in this space. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Marcel, I believe it was an oversight to have missed mentioning ACE. Hopefully one of the proposed committers will comment on this aspect. thanks, dims On 09/06/2009 08:29 AM, Marcel Offermans wrote: It probably got swamped in the discussion, but, on Sep 1, 2009, at 22:20 , Marcel Offermans wrote: On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote: Relationships with Other Apache Projects I know ACE is only in incubation, but is there a reason for not mentioning it in this list? To me it makes sense to also consider technology to deploy and update OSGi components and I think ACE could fit in there nicely. Does anybody want to comment on this? I would definitely like to collaborate on making ACE work well with anything Aries produces (since you were hinting it's not a single project but more a series of components). Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Karl, There are *many* TLP(s) with overlapping scope as James Strachan pointed out earlier in the thread. I don't see the need to shoe horn a new community with new code into an existing TLP just because of scope. For all you know by the time they get out of the incubator their scope may change a bit (or more). thanks, dims On 09/05/2009 04:31 AM, Karl Pauls wrote: The question is about the scope and goals of Aries and more specifically about the part where it is about being an umbrella for OSGi EE spec implementations where it has been argued that this could/should be done at felix - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Richard, #2 - Finished impls could quickly be released as non-incubator artifacts. is also something that i am not comfortable with, at least until the new committers get off the ground, attract a user community and show that they are able to follow the ASF way. Ideally my hope is that d...@felix folks should guide the community being formed within the incubation podling process. If we can get anyone interested join in as a mentor and/or committer that would be wonderful. thanks, dims On 09/04/2009 06:04 PM, Richard S. Hall wrote: On 9/4/09 16:49, Davanum Srinivas wrote: Richard, I see your viewpoint better now. Thanks. One more question, Will there be a problem of folks on d...@felix not being able or willing to participate in a new podling? (If the folks presenting this proposal do wish to start off as a podling) Dims, since I don't speak for all Felix community members, I can't really answer that question. I imagine that interested parties would contribute, but certainly a benefit of at least doing any independent OSGi spec impls at Felix is you will automatically get the oversight of people who have been doing it for years, if not their contribution. The separation could possibly make life simpler too for those willing to help, since: 1. People interested only in the OSGi spec impls do not necessarily have to be involved on Aries mailing lists that will likely incorporate a lot of discussion about the Aries component model and related content. 2. Finished impls could quickly be released as non-incubator artifacts. - richard thanks, dims On 09/04/2009 04:31 PM, Richard S. Hall wrote: On 9/4/09 16:10, Davanum Srinivas wrote: Richard, On 09/04/2009 03:49 PM, Richard S. Hall wrote: So, no, I am not saying everything should, but in general, it would be nice if the spec impls started there since we have a community of OSGi users and OSGi experts who are very active and receptive, many of whom also work in the EE space. Will the people mentioned not participate if Aries is a separate podling to start with? After all destination PMC can be determined during graduation process. Also the incubation process is to show new incoming team how Apache works etc..is that better done as a podling or as a felix sub project? If we continue the same thought process, will there every be any incubator podling with for any OSGi related activity? Yes, and I mentioned this, but that seems to get lost somehow. In short, it makes sense for spec impls tied to the Aries component model (for example), to be hosted there, but there is little need to create another project to incubate generic OSGi spec impls, since the Felix community was set up for that. The reality is, most OSGi specs are not huge projects so we likely wouldn't want TLPs for all of them, but nothing stops a subproject started at Felix from going TLP if it takes on a life of its own. Choices are 1) Podling - TLP 2) Podling - Felix Sub project 3) Podling - Felix Sub project - TLP 4) Felix Sub project 5) Felix Sub project - TLP The first 3 effectively uses incubator process(es) to educate the incoming folks and provides a strong grounding in ASF-land (at least that is what the intention is :) So, why should we bypass incubator? Again, there was already a project incubated to educate incoming folks on how to create open source OSGi spec impls at Apache, so why do we need to repeat that process? Your phrasing of this question implies we are trying to somehow skirt the Apache way, but educating incoming people via contributions and meritocracy to an existing project is not some shortcut. - richard thanks, dims - 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 - 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: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Karl, Please don't get me wrong. Felix is choice for an excellent *destination* TLP. The Incubator PMC itself was setup to take away the responsibility for training incoming folks from existing TLP(s). So my gut feeling is that we should allow the incubation process to go on and decide on destination and scope once the project is ready to graduate. I am sure the folks on the proposal would love to get any and every help they can get to graduate as well as on the technical front. Please do continue to provide help and guidance. thanks, dims On 09/05/2009 10:29 AM, Karl Pauls wrote: On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivasdava...@gmail.com wrote: Karl, There are *many* TLP(s) with overlapping scope as James Strachan pointed out earlier in the thread. I don't see the need to shoe horn a new community with new code into an existing TLP just because of scope. For all you know by the time they get out of the incubator their scope may change a bit (or more). I'm sorry if it looked like I wanted to shoe horn anything into felix. That wasn't my goal as for me it was a question of where I would like it to happen and as I said earlier already, not the end of the world if not. regards, Karl thanks, dims On 09/05/2009 04:31 AM, Karl Pauls wrote: The question is about the scope and goals of Aries and more specifically about the part where it is about being an umbrella for OSGi EE spec implementations where it has been argued that this could/should be done at felix - 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: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
13:23, Niclas Hedhman wrote: Kevan, Was a contact with Felix made prior to dropping the proposal here? I got the impression that wasn't the case, which I find surprising... If I am wrong, what was the meat of such? I'm also less happy with the rhetoric here repeated over and over, seemingly uninterested in discussion of reaching a solution everyone can accept. (From both camps, btw) -- Niclas On Sep 4, 2009 12:53 AM, Kevan Millerkevan.mil...@gmail.com wrote: On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote: On Thu, Sep 3, 2009 at 3:19 AM, William A. Ro... Totally agree. Had certainly hoped that Felix committers would be interested in joining... --kevan - To unsubscribe, e-mail: gene... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - 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 -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Richard, On 09/04/2009 03:49 PM, Richard S. Hall wrote: So, no, I am not saying everything should, but in general, it would be nice if the spec impls started there since we have a community of OSGi users and OSGi experts who are very active and receptive, many of whom also work in the EE space. Will the people mentioned not participate if Aries is a separate podling to start with? After all destination PMC can be determined during graduation process. Also the incubation process is to show new incoming team how Apache works etc..is that better done as a podling or as a felix sub project? If we continue the same thought process, will there every be any incubator podling with for any OSGi related activity? In short, it makes sense for spec impls tied to the Aries component model (for example), to be hosted there, but there is little need to create another project to incubate generic OSGi spec impls, since the Felix community was set up for that. The reality is, most OSGi specs are not huge projects so we likely wouldn't want TLPs for all of them, but nothing stops a subproject started at Felix from going TLP if it takes on a life of its own. Choices are 1) Podling - TLP 2) Podling - Felix Sub project 3) Podling - Felix Sub project - TLP 4) Felix Sub project 5) Felix Sub project - TLP The first 3 effectively uses incubator process(es) to educate the incoming folks and provides a strong grounding in ASF-land (at least that is what the intention is :) So, why should we bypass incubator? thanks, dims - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Richard, I see your viewpoint better now. Thanks. One more question, Will there be a problem of folks on d...@felix not being able or willing to participate in a new podling? (If the folks presenting this proposal do wish to start off as a podling) thanks, dims On 09/04/2009 04:31 PM, Richard S. Hall wrote: On 9/4/09 16:10, Davanum Srinivas wrote: Richard, On 09/04/2009 03:49 PM, Richard S. Hall wrote: So, no, I am not saying everything should, but in general, it would be nice if the spec impls started there since we have a community of OSGi users and OSGi experts who are very active and receptive, many of whom also work in the EE space. Will the people mentioned not participate if Aries is a separate podling to start with? After all destination PMC can be determined during graduation process. Also the incubation process is to show new incoming team how Apache works etc..is that better done as a podling or as a felix sub project? If we continue the same thought process, will there every be any incubator podling with for any OSGi related activity? Yes, and I mentioned this, but that seems to get lost somehow. In short, it makes sense for spec impls tied to the Aries component model (for example), to be hosted there, but there is little need to create another project to incubate generic OSGi spec impls, since the Felix community was set up for that. The reality is, most OSGi specs are not huge projects so we likely wouldn't want TLPs for all of them, but nothing stops a subproject started at Felix from going TLP if it takes on a life of its own. Choices are 1) Podling - TLP 2) Podling - Felix Sub project 3) Podling - Felix Sub project - TLP 4) Felix Sub project 5) Felix Sub project - TLP The first 3 effectively uses incubator process(es) to educate the incoming folks and provides a strong grounding in ASF-land (at least that is what the intention is :) So, why should we bypass incubator? Again, there was already a project incubated to educate incoming folks on how to create open source OSGi spec impls at Apache, so why do we need to repeat that process? Your phrasing of this question implies we are trying to somehow skirt the Apache way, but educating incoming people via contributions and meritocracy to an existing project is not some shortcut. - richard thanks, dims - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Let me clarify why i asked that question, When we started the Wink Podling there was strong recommendation that the incoming folks should work under CXF which already has a JAX-RS implementation. Once we did start the podling we have had guidance from just Dan Kulp from CXF and not from anyone else :( thanks, dims On 09/04/2009 04:49 PM, Davanum Srinivas wrote: Richard, I see your viewpoint better now. Thanks. One more question, Will there be a problem of folks on d...@felix not being able or willing to participate in a new podling? (If the folks presenting this proposal do wish to start off as a podling) thanks, dims On 09/04/2009 04:31 PM, Richard S. Hall wrote: On 9/4/09 16:10, Davanum Srinivas wrote: Richard, On 09/04/2009 03:49 PM, Richard S. Hall wrote: So, no, I am not saying everything should, but in general, it would be nice if the spec impls started there since we have a community of OSGi users and OSGi experts who are very active and receptive, many of whom also work in the EE space. Will the people mentioned not participate if Aries is a separate podling to start with? After all destination PMC can be determined during graduation process. Also the incubation process is to show new incoming team how Apache works etc..is that better done as a podling or as a felix sub project? If we continue the same thought process, will there every be any incubator podling with for any OSGi related activity? Yes, and I mentioned this, but that seems to get lost somehow. In short, it makes sense for spec impls tied to the Aries component model (for example), to be hosted there, but there is little need to create another project to incubate generic OSGi spec impls, since the Felix community was set up for that. The reality is, most OSGi specs are not huge projects so we likely wouldn't want TLPs for all of them, but nothing stops a subproject started at Felix from going TLP if it takes on a life of its own. Choices are 1) Podling - TLP 2) Podling - Felix Sub project 3) Podling - Felix Sub project - TLP 4) Felix Sub project 5) Felix Sub project - TLP The first 3 effectively uses incubator process(es) to educate the incoming folks and provides a strong grounding in ASF-land (at least that is what the intention is :) So, why should we bypass incubator? Again, there was already a project incubated to educate incoming folks on how to create open source OSGi spec impls at Apache, so why do we need to repeat that process? Your phrasing of this question implies we are trying to somehow skirt the Apache way, but educating incoming people via contributions and meritocracy to an existing project is not some shortcut. - richard thanks, dims - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Wink 0.1 (RC-3)
+1 from me. thanks, dims On 08/19/2009 08:12 AM, sebb wrote: On 19/08/2009, Snitkovsky, Martinmartin.snitkov...@hp.com wrote: The Wink community voted on and approved the release of Apache Wink 0.1 The voting mail thread can be viewed at: http://tiny.cc/es4Zu We would now like to request the approval of the Incubator PMC for this release. The Maven staging area is at: https://repository.apache.org/content/repositories/wink-staging-026/ The distributions are in: https://repository.apache.org/content/repositories/wink-staging-026/org/apache/wink/apache-wink/0.1-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-0.1-incubating/ (revision 8046487) Release signing key was uploaded to http://www.pramberger.at/peter/services/keyserver/; http://pgp.mit.edu/ public key servers Release signing KEYS file can be download from SVN https://svn.apache.org/repos/asf/incubator/wink/tags/wink-0.1-incubating/KEYS The sigs and hashes all look OK; archive contents looks OK. NOTICE and LICENSE look OK; manifests look OK. One minor problem from before: The wink-0.1-incubating-*.jar files look to be a combination of the client, common, server, spring and webdav jars, yet the NOTICE files say Apache Wink WebDav. These should say Apache Wink. IMO this is not a release blocker, but it should be fixed before the next release as it's confusing. Thanks, Martin - 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] Mothball/Pause Lokahi
+1 On 08/12/2009 10:29 AM, Richard S. Hall wrote: +1 On 8/12/09 0:50, Niclas Hedhman wrote: PMC and others, Lokahi's community has collapsed long time ago and albeit Noel's repeated efforts to create interest around the project, there is no signs of any improvement. I am therefor calling a vote to mothball/pause the project. Please place your votes. [ ] +1, go ahead and mothball/pause Lokahi, [ ] -1, don't mothball/pause Lokahi, because... (reason is optional, but appreciated) Cheers - 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: [PROPOSAL][VOTE] Wookie - a W3C widget engine with Google Wave extension
+1 -- dims On 07/14/2009 06:53 AM, Matthias Wessendorf wrote: +1 (IPMC binding) On Tue, Jul 14, 2009 at 12:19 PM, Matthias Wessendorfmat...@apache.org wrote: +1 On Tue, Jul 14, 2009 at 12:15 PM, Ross Gardlerrgard...@apache.org wrote: I would like to formally present the incubator proposal for Apache Wookie, a W3C widget engine with Google Wave extension The full proposal can be found at http://wiki.apache.org/incubator/WookieProposal Vote will close in a little over 72 hours at mid day (BST, UTC + 1) Friday 17th July. http://www.timeanddate.com/worldclock/fixedtime.html?month=7day=17year=2009hour=12min=0sec=0p1=136 Ross -- Ross Gardler 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Wink] Podling setup steps
Folks, Wink is now on JIRA https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310940 Per #5 below, please send me your JIRA id's (you can create one yourself if you haven't already!) for me to add you in as a committer. thanks, dims PS: i subscribed a few folks who had not already joined the wink-dev@ mailing list to that list. If you wish to use another email address, please let me know. On Wed, May 27, 2009 at 8:38 PM, Davanum Srinivas dava...@gmail.com wrote: fyi, wink-dev@ / wink-commits@ / wink-private@ are in ready. Please subscribe by sending one email each to wink-dev-subscribe@ / wink-commits-subscribe@ / wink-private-subscribe@ thanks, dims On Wed, May 27, 2009 at 8:59 AM, Davanum Srinivas dava...@gmail.com wrote: Eli, Nick, #1) Created an svn area for Wink https://svn.apache.org/repos/asf/incubator/wink/ #2) Requested Apache Infra to create mailing lists https://issues.apache.org/jira/browse/INFRA-2068 Can you please help with these tasks? #1) Make sure that everyone on the team has filled in their Individual CLA (See form at http://www.apache.org/licenses/). Once they filled it up and faxed it in, In a few days it will show up in Unlisted CLA's section here - http://people.apache.org/~jim/committers.html #2) Please fill up the CCLA (See form at http://www.apache.org/licenses/) one for each of your employer and fax it in. #3) Please send me the list of email id's and preferred id's (Apache ID for svn and email) for each committer proposed in the Wink proposal. That will help me get the id's created for each of them #4) Please fill up a Software grant and fax it in (http://www.apache.org/licenses/) #5) Please ask everyone to create an id in JIRA and let me know what their JIRA id's are. I'll create the JIRA space when the mailing list gets created. Others Tasks that i need to do: #1) Get Wink listed under http://incubator.apache.org/projects/ Tasks for later for the participants once we get started: #1) Help draft report to the Apache Board (see details in wiki - http://wiki.apache.org/incubator/) Lastly, Till we get wink-dev@ setup, please use gene...@incubator for all communication and add a [Wink] in the subject for us to easily find the emails. Please let me know if you need more information. You may want to read up more on the setup process etc here (http://incubator.apache.org/guides/mentor.html) thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache JSecurity/Ki rename - choose your favorite!
+1 Aseca On 05/30/2009 04:31 PM, Craig L Russell wrote: +1 Aseca Craig On May 29, 2009, at 7:29 AM, Les Hazlewood wrote: Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Sling as Top Level Project
[X ] +1 to recommend Sling's graduation On 05/29/2009 04:26 PM, Bertrand Delacretaz wrote: [X ] +1 to recommend Sling's graduation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Wink] Podling setup steps
Eli, Nick, #1) Created an svn area for Wink https://svn.apache.org/repos/asf/incubator/wink/ #2) Requested Apache Infra to create mailing lists https://issues.apache.org/jira/browse/INFRA-2068 Can you please help with these tasks? #1) Make sure that everyone on the team has filled in their Individual CLA (See form at http://www.apache.org/licenses/). Once they filled it up and faxed it in, In a few days it will show up in Unlisted CLA's section here - http://people.apache.org/~jim/committers.html #2) Please fill up the CCLA (See form at http://www.apache.org/licenses/) one for each of your employer and fax it in. #3) Please send me the list of email id's and preferred id's (Apache ID for svn and email) for each committer proposed in the Wink proposal. That will help me get the id's created for each of them #4) Please fill up a Software grant and fax it in (http://www.apache.org/licenses/) #5) Please ask everyone to create an id in JIRA and let me know what their JIRA id's are. I'll create the JIRA space when the mailing list gets created. Others Tasks that i need to do: #1) Get Wink listed under http://incubator.apache.org/projects/ Tasks for later for the participants once we get started: #1) Help draft report to the Apache Board (see details in wiki - http://wiki.apache.org/incubator/) Lastly, Till we get wink-dev@ setup, please use gene...@incubator for all communication and add a [Wink] in the subject for us to easily find the emails. Please let me know if you need more information. You may want to read up more on the setup process etc here (http://incubator.apache.org/guides/mentor.html) thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Wink] Podling setup steps
fyi, wink-dev@ / wink-commits@ / wink-private@ are in ready. Please subscribe by sending one email each to wink-dev-subscribe@ / wink-commits-subscribe@ / wink-private-subscribe@ thanks, dims On Wed, May 27, 2009 at 8:59 AM, Davanum Srinivas dava...@gmail.com wrote: Eli, Nick, #1) Created an svn area for Wink https://svn.apache.org/repos/asf/incubator/wink/ #2) Requested Apache Infra to create mailing lists https://issues.apache.org/jira/browse/INFRA-2068 Can you please help with these tasks? #1) Make sure that everyone on the team has filled in their Individual CLA (See form at http://www.apache.org/licenses/). Once they filled it up and faxed it in, In a few days it will show up in Unlisted CLA's section here - http://people.apache.org/~jim/committers.html #2) Please fill up the CCLA (See form at http://www.apache.org/licenses/) one for each of your employer and fax it in. #3) Please send me the list of email id's and preferred id's (Apache ID for svn and email) for each committer proposed in the Wink proposal. That will help me get the id's created for each of them #4) Please fill up a Software grant and fax it in (http://www.apache.org/licenses/) #5) Please ask everyone to create an id in JIRA and let me know what their JIRA id's are. I'll create the JIRA space when the mailing list gets created. Others Tasks that i need to do: #1) Get Wink listed under http://incubator.apache.org/projects/ Tasks for later for the participants once we get started: #1) Help draft report to the Apache Board (see details in wiki - http://wiki.apache.org/incubator/) Lastly, Till we get wink-dev@ setup, please use gene...@incubator for all communication and add a [Wink] in the subject for us to easily find the emails. Please let me know if you need more information. You may want to read up more on the setup process etc here (http://incubator.apache.org/guides/mentor.html) thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
