Re: [VOTE] CloudStack for Apache Incubator
On 04/09/2012 09:32 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 +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache DeltaSpike - CDI-Extensions
You can add me as a mentor to the project. Carl. - 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
Here is my +1 Carl. On 10/17/2011 10: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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.1, rc1
+1 On 10/11/2011 08:40 AM, Jim Jagielski wrote: +1 On Oct 4, 2011, at 1:00 PM, David Lutterkort 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 - 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 deltacloud 0.2.0
On 02/21/2011 01:02 PM, Jim Jagielski wrote: On Feb 21, 2011, at 11:34 AM, Niclas Hedhman wrote: On Tue, Feb 22, 2011 at 12:23 AM, Mark Strubergstrub...@yahoo.de wrote: I'm not really fit with ruby projects, but there are quite a few sources with LGPL license headers. e.g. ./lib/deltacloud/drivers/opennebula/opennebula_driver.rb is this ok for us? *shrug* It has not been in the past, and I can't recall seeing it changed... All sources on ASF is to be ALv2. Let me check this out... Jim, I remember RAT had worked through this case on the list before for external non-dep gems the way ruby works. Carl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.2.0
I voted on the project vote with +1. I believe the release vote requires another IPMC / member vote. Carl. On 02/14/2011 01:20 PM, David Lutterkort wrote: Hi all, I just uploaded a release candidate for Deltacloud 0.2.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.2.0/rc2/ Please vote on whether this should become the official 0.2.0 release by Thursday, 2011-02-17 11:00am PST (Saturday 2011-02-17 19:00 UTC, see http://bit.ly/e0Q2C5 for other local times) Overview of the high-level changes in this release: * Dynamically select driver through the X-Deltacloud-Driver HTTP header; allow passing in driver-specific endpoint with the X-Deltacloud-Provider header * New 'load_balancers' collection, supported for EC2 and GoGrid * Allow creation/deletion of blobs (S3, CloudFiles, Azure) * Return HTTP status 405 when trying to perform an action on a instance that is not available * Drivers + EC2 - security_group and public_ip features for instance creation - switched to aws gem + GoGrid: now have two hardware profiles + RHEV-M: completely rewritten; now uses RHEV-M REST API, not Powershell + Mock: - support 'keys' collection - switch to storage-only driver by setting provider to 'storage' I will update the website and docs to reflect those changes in time for the official release. 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: Missing reports: DeltaCloud, Droids, HISE, ISIS, Kitty, Lucy, Stonehenge, VCL, Wookie
It is on the wiki. DeltaCloud Deltacloud 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. Infrastructure: * Hudson configured to trigger build after commit (https://hudson.apache.org/hudson/job/apache-deltacloud-core/) Latest activity: * Deltacloud API was proclaimed as stable and version 0.1.0 was released * A new EC2 driver for Deltacloud API (in review process) * Client improved to be more stable * Deltacloud API is now Ruby 1.9 compatible Current issues: * Support for buckets (streaming) Signed off by mentor: cctrieloff On 11/15/2010 09:17 PM, Noel J. Bergman wrote: That means we're still missing DeltaCloud (promised for tomorrow), Droids, HISE, Stonehenge, VCL, and Wookie. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Missing reports: DeltaCloud, Droids, HISE, ISIS, Kitty, Lucy, Stonehenge, VCL, Wookie
I'll chase up Deltacloud to make sure it is in by tomorrow AM. Carl. On 11/15/2010 04:08 PM, Mattmann, Chris A (388J) wrote: Hey Noel, It's my understanding that Lucy isn't on this reporting cycle and was included on the wiki by mistake. Cheers, Chris On 11/15/10 12:03 PM, Noel J. Bergmann...@devtech.com wrote: All of these reports are missing and need to be posted IMMEDIATELY! - 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.mattm...@jpl.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
Re: Deltacloud Mentors, an Infra issue requires your attention.
On 09/10/2010 05:31 AM, Gav... wrote: https://issues.apache.org/jira/browse/INFRA-2867 Thanks :-) Gav... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Thanks, I'll take to the project and resolve. Thanks Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Quick project submission question
What is the view of having a project in Apache that pulls substantial components that are licensed under ASL as dependencies into the code base. I.e. not coping the code, but using components that have been built and maintained elsewhere under ASL but used as dependencies for running. I assume this is not an issue, based in the info posted on use of licenses -- however I'm interested in understand if others have had positive or negative experiences with such a case. Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Quick project submission question
On 09/08/2010 10:29 AM, Scott Wilson wrote: On 8 Sep 2010, at 15:13, Carl Trieloff wrote: What is the view of having a project in Apache that pulls substantial components that are licensed under ASL as dependencies into the code base. I.e. not coping the code, but using components that have been built and maintained elsewhere under ASL but used as dependencies for running. I assume this is not an issue, based in the info posted on use of licenses -- however I'm interested in understand if others have had positive or negative experiences with such a case. Hi Carl, Wookie has been using Ivy[1] to pull in external dependencies as part of the build process. It took a bit of initial effort to get right, but now works really nicely, and makes it much easier to track external libraries and check their licenses are compatible. You can also distinguish between dependencies that are needed for development, for building, and for distribution and downstream reuse. There is an Eclipse plugin for Ivy that works pretty well too. The only vaguely negative thing I found was the initial challenge of getting the hang of how Ivy works, but we had good help from other community members and from our mentors on that. [1] http://ant.apache.org/ivy/ - Scott Scott, Do you see any negative sides from the community perspective with the dependencies that or from projects outside of Apache? Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Quick project submission question
On 09/08/2010 11:06 AM, Scott Wilson wrote: On 8 Sep 2010, at 15:40, Carl Trieloff wrote: On 09/08/2010 10:29 AM, Scott Wilson wrote: On 8 Sep 2010, at 15:13, Carl Trieloff wrote: What is the view of having a project in Apache that pulls substantial components that are licensed under ASL as dependencies into the code base. I.e. not coping the code, but using components that have been built and maintained elsewhere under ASL but used as dependencies for running. I assume this is not an issue, based in the info posted on use of licenses -- however I'm interested in understand if others have had positive or negative experiences with such a case. Hi Carl, Wookie has been using Ivy[1] to pull in external dependencies as part of the build process. It took a bit of initial effort to get right, but now works really nicely, and makes it much easier to track external libraries and check their licenses are compatible. You can also distinguish between dependencies that are needed for development, for building, and for distribution and downstream reuse. There is an Eclipse plugin for Ivy that works pretty well too. The only vaguely negative thing I found was the initial challenge of getting the hang of how Ivy works, but we had good help from other community members and from our mentors on that. [1]http://ant.apache.org/ivy/ - Scott Scott, Do you see any negative sides from the community perspective with the dependencies that or from projects outside of Apache? Carl. I think it depends on the nature of the project you depend on. For the most part these are pretty mature, commonly used libraries. However in one case we did have the issue that we had a problem that was caused by a bug in a dependency (HtmlCleaner) where it wasn't very clear from the website whether the project was still active (patches not applied, no recent commits etc). In the end I just asked nicely on their tracker if it could be fixed, waited patiently, and eventually it was:-) I can imagine there might be problems if you got into a blame game with upstream projects, or where there is a combination of a big culture difference plus an unstable codebase. I think the answer is to evaluate dependencies from a community and sustainability viewpoint, not just a functional one. Thanks, the libs in question are mature and still actively maintained, this was helpful. Carl. - 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 Carl. On 08/18/2010 07:31 PM, Davanum Srinivas wrote: +1 -- dims Sent from my iPhone On Aug 18, 2010, at 7:11 PM, Joe Schaeferjoe_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 Schaeferjoe_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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Radical revamp
On 08/17/2010 07:48 PM, Ross Gardler wrote: On 17/08/2010 17:35, Carl Trieloff wrote: To this question, (what will make this model succeed or fail) I find myself not coming to defensible answers... I would love to see thoughts of others on this question. The thread implies it comes down to the 3+ members on the project. It's not that simple for me. A single member who either knows all they need to know or (more likely) knows when they need to ask for guidance from their peers is all that is needed if (and only if) the IPMC trusts that member to do the right thing. However, there are a number of reasons why a single mentor does not work out including some fundamental requirements for binding votes on certain activities. For me success or failure comes down to the quality of the mentoring and the willingness of the project committers to learn how to apply the Apache Way to their community. Ross, I buy that, however what guidelines would IPMC use to allow a podling to use this model? Does this mean we have 'lesser' and 'greater' members or mentors? Or is it a podling asking to use the model and then the IPMC deciding based on knowing who is on the podling PPMC to allow it, or if it is open to any podling, how do we as the IPMC understand that the project is ready to graduate? Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Radical revamp
On 08/17/2010 11:39 AM, Joe Schaefer wrote: - Original Message From: Ross Gardlerrgard...@apache.org To: general@incubator.apache.org Sent: Tue, August 17, 2010 8:45:01 AM Subject: Re: Radical revamp On 17/08/2010 13:21, Joe Schaefer wrote: [...] Isn't that why we encourage IPMC members to participate in discussions about our podlings? How do we expect people to learn without dialog and discussion- by reading our constantly- in-need-of-attention docs? We should be trusting our mentors to know when to ask for help and when to trust their instincts. We should be helping our mentors understand the boundaries of their expertise. We should be helping mentors understand what mentorship is - it should not be a box ticking exercise. I would be far more convinced that we should be trusting our mentors if mentors actually participated in writing incubator documentation, or engaged constructively in threads like this. The fact is there are no group controls over what a mentor says or does, it's purely a voluntary exercise, by people with limited to no training, with no direct benefit nor responsiblity related to it. [...] In this very thread a self confessed newcomer said that their experience of the incubator was just fine. Then they went on to say that the Apache Way is not about modifying processes to best fit your individual needs. This, to me, is incorrect. Perhaps. The Apache Way works precisely because we allow projects to change (most) processes to suit their individual communities. Whilst there are a few invariant processes to ensure IP is managed properly and communities are meritocratic pretty much everything can be modified on a per proejct/per community basis. That is the vast majority of processes in the ASF are best practice not check lists to be ticked off. IPMC members should indeed participate in discussions about what is the best way to solve problem x within this community, that is how we learn about best practice. We should *not* be writing more rules to constrain projects in ways that is not necessary for the Apache Way and is not necessary for the legal oversight of the foundation. What I've been trying to explain here with my experiment is that the best way to teach people about the Apache Way is to let them experience it for themselves. We don't actually do that here, and I'm trying to push a view that allows us to actually try it a little and see what happens. I've been following this thread, and have another mail written, but not posted, maybe I will at some point... however I find myself trying to understand what would be the key attributes that would make this proposal a wild success, or a failure for a podling. By success, I mean a well run ASF project. The proposal has caught my imagination, but I'm trying to understand the parameters of guidance in this model. To this question, (what will make this model succeed or fail) I find myself not coming to defensible answers... I would love to see thoughts of others on this question. The thread implies it comes down to the 3+ members on the project. thoughts... Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Report July] Deltacloud
- Project basically setup (info for 3 people still being worked to get ICLA correctly listed) - Code has been imported. - Working to get Code Grant on file - Project active, commits and mail list discussions have started. - The website has not been setup yet. Project is up, running and getting the wheels to start to turn. Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: *** MISSING Board Reports: Bluesky, Deltacloud, Lucene Connector Framework and River
David is currently on vacation, so I'll post a brief report for him: Deltacloud. Deltacloud is still in project setup. The main delay has been working the process of ICLA recording and account setup. Once the account requests have been processed, I expect I will be able to complete the project setup and the project will be able to get underway. Some discussion has happened between initial committers, but I expect the project to get going in earnest over the next week or so once accounts are created. Most of the other infra has been setup. regards Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: *** MISSING Board Reports: Bluesky, Deltacloud, Lucene Connector Framework and River
On 06/14/2010 01:14 PM, Luciano Resende wrote: On Mon, Jun 14, 2010 at 9:13 AM, Noel J. Bergmann...@devtech.com wrote: There are several missing reports. Bluesky, Deltacloud, Lucene Connector Framework, and River. POST THEM IMMEDIATELY! Here is the one for DeltaCloud (which I just added to wiki) = Deltacloud = 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. Deltacloud entered the incubator in 2010-05-17. Currently gathering initial contributors CLAs and working on setting up project infrastructure. === Thanks, should have read all the mail before I posted. Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Closed: (INCUBATOR-107) Setup DeltaCloud project
[ https://issues.apache.org/jira/browse/INCUBATOR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Trieloff closed INCUBATOR-107. --- Resolution: Fixed Moving setup to https://issues.apache.org/jira/browse/INFRA-2723 Closing Incubator JIRA. Setup DeltaCloud project Key: INCUBATOR-107 URL: https://issues.apache.org/jira/browse/INCUBATOR-107 Project: Incubator Issue Type: Task Components: policy, site, subversion, wiki Reporter: Carl Trieloff JIRA to track the setup of Deltacloud incubator project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Created: (INCUBATOR-107) Setup DeltaCloud project
Setup DeltaCloud project Key: INCUBATOR-107 URL: https://issues.apache.org/jira/browse/INCUBATOR-107 Project: Incubator Issue Type: Task Components: policy, site, subversion, wiki Reporter: Carl Trieloff JIRA to track the setup of Deltacloud incubator project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-107) Setup DeltaCloud project
[ https://issues.apache.org/jira/browse/INCUBATOR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12869336#action_12869336 ] Carl Trieloff commented on INCUBATOR-107: - Will be working through the following check/work list to setup deltacloud. http://incubator.apache.org/guides/mentor.html#add-incubation Setup DeltaCloud project Key: INCUBATOR-107 URL: https://issues.apache.org/jira/browse/INCUBATOR-107 Project: Incubator Issue Type: Task Components: policy, site, subversion, wiki Reporter: Carl Trieloff JIRA to track the setup of Deltacloud incubator project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-107) Setup DeltaCloud project
[ https://issues.apache.org/jira/browse/INCUBATOR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12869346#action_12869346 ] Carl Trieloff commented on INCUBATOR-107: - I'm setting up incubator status page. Setup DeltaCloud project Key: INCUBATOR-107 URL: https://issues.apache.org/jira/browse/INCUBATOR-107 Project: Incubator Issue Type: Task Components: policy, site, subversion, wiki Reporter: Carl Trieloff JIRA to track the setup of Deltacloud incubator project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Deltacloud into incubator
On 05/17/2010 01:09 PM, David Lutterkort wrote: Hi all, by my count, the vote for Deltacloud yielded 13 +1 votes and no 0 or -1 votes. I will work with Carl to get Deltacloud set up in the incubator. thanks to everybody for the very positive reception, David Thanks, I start the process tomorrow. regards Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Deltacloud Project
On 05/12/2010 08:45 PM, David Lutterkort 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 Just got back from travelling, catching up on discussions and all looks good so far, thus I'll start, +1 (binding vote). regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Whirr for Incubation
+1 Carl. On Wed, May 5, 2010 at 2:06 PM, Tom White tomwh...@apache.org wrote: We've added three mentors since starting the proposal thread, so I would like to start the vote to accept Whirr into the Apache Incubator. The proposal is included below and is also at: http://wiki.apache.org/incubator/WhirrProposal Please cast your votes: [ ] +1 Accept Whirr for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: Thanks, Tom = Whirr, a library of cloud services = == Abstract == Whirr will be a set of libraries for running cloud services. == Proposal == Whirr will provide code for running a variety of software services on cloud infrastructure. It will provide bindings in several languages (e.g. Python and Java) for popular cloud providers to make it easy to start and stop services like Hadoop clusters. The project will not be limited to a particular set of services, rather it will be expected that a range of services are developed, as determined by the project contributors. Possible services include Hadoop, HBase, !ZooKeeper, Cassandra. == Background == The ability to run services on cloud providers is very useful, particularly for proofs of concept, testing, and also ad hoc production work. Bringing up clusters in the cloud is non-trivial, since careful choreography is required. (Designing an interface that is convenient as well as secure is also a challenge in a cloud context.) Making services that runs on a variety of cloud providers is harder, even with the availability of libraries like libcloud and jclouds, since each platform's quirks and extra features must be considered (and either worked around, or possibly taken advantage of, as appropriate) . Whirr will facilitate sharing of best practices, both for a particular service (such as Hadoop configuration on a particular provider), and for common cloud operations (such as installation of dependencies across cloud providers). It will provide a space to share good configurations and will encode service-specific knowledge. == Rationale == There are already scripts in the Hadoop project that allow users to run Hadoop clusters on Amazon EC2 and other cloud providers. While users have found these scripts useful, their current home as a Hadoop Common contrib project has the following limitations: * Tying the scripts' release cycle to Hadoop's means that it is difficult to distribute updates to the scripts which are changing fast (new features and bugfixes). * The scripts support multiple versions of Hadoop, so it makes more sense to distribute them separately from Hadoop itself. * They are general: people want to contribute code for non-Hadoop services like Cassandra (for example: http://github.com/johanoskarsson/cassandra-ec2). * Having a uniform approach to running services in the cloud, hosted in one project, makes launching sets of complementary services easier for the user. Today, the scripts and libraries hosted within each project (e.g. in Hadoop, HBase, Cassandra) have slightly different conventions and semantics, and are likely to diverge over time. Building a community around cloud infrastructure services will help enforce a common approach to running services in the cloud. == Initial Goals == * Provide a new home for the existing Hadoop cloud scripts. * Add more services (e.g. HBase) * Develop Java libraries for Hadoop clusters * Add new cloud providers by taking advantage of libcloud and jclouds. * (Future) Run on own hardware, so users can take advantage of the same interface to control services running locally or in the cloud. == Current Status == === Meritocracy === The Hadoop scripts were originally created by Tom White, and have had a substantial number of contributions from members of the Hadoop community. By becoming its own project, significant contributors to Whirr would become committers, and allow the project to grow. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. For example, this project would provide a home to facilitate collaboration between the groups of Hadoop and HBase developers who are building cloud services. === Core developers === Tom White wrote most of the original code and is familiar with open source and Apache-style development, being a Hadoop committer and an ASF member. There have been a number of contributors who have provided patches to these scripts over time. Andrew Purtell who created the HBase cloud scripts is a HBase committer. Johan Oskarsson (Hadoop and Cassandra committer) ported the scripts to Cassandra. === Alignment === Whirr complements libcloud, currently in the Incubator. Libcloud provides multi-cloud provider support, while Whirr will provide multi-service support in the cloud. Whirr will build cloud components for several Apache projects, such
Re: [PROPOSAL] Deltacloud Project
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
Re: [PROPOSAL] Deltacloud Project
On 05/07/2010 10:21 AM, Davanum Srinivas wrote: Carl, if you need additional mentors, count me in. thanks, dims Dims, That would be great. Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Qpid graduates as TLP
I want to take a few minutes to thank everyone involved on our graduation. The Apache board has approved our graduation and we will begin the post graduation transition. Congratulations to the project and many thanks to all those that have taken an interest in Qpid regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] Qpid Graduation - for top level
Many thanks to our mentors, Carl. Paul Fremantle wrote: Congratulations! On Fri, Nov 14, 2008 at 8:51 PM, Carl Trieloff [EMAIL PROTECTED] wrote: Carl Trieloff wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Binding - names listed at: http://incubator.apache.org/whoweare.html (8 +1 binding) Niall Pemberton [EMAIL PROTECTED] Martijn Dashorst [EMAIL PROTECTED] Bertrand Delacretaz [EMAIL PROTECTED] Jim Jagielski [EMAIL PROTECTED] Craig L Russell [EMAIL PROTECTED] Yoav Shapira [EMAIL PROTECTED] Paul Fremantle [EMAIL PROTECTED] Ant Elder [EMAIL PROTECTED] (2 +1 non-binding) Daniel Kulp [EMAIL PROTECTED] Luciano Resende [EMAIL PROTECTED] no (0 or -1 votes) Many thanks to all those involved and that voted on the community vote etc... I will now pass the resolution onto the board. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] [VOTE] Qpid Graduation - for top level
Carl Trieloff wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Binding - names listed at: http://incubator.apache.org/whoweare.html (8 +1 binding) Niall Pemberton [EMAIL PROTECTED] Martijn Dashorst [EMAIL PROTECTED] Bertrand Delacretaz [EMAIL PROTECTED] Jim Jagielski [EMAIL PROTECTED] Craig L Russell [EMAIL PROTECTED] Yoav Shapira [EMAIL PROTECTED] Paul Fremantle [EMAIL PROTECTED] Ant Elder [EMAIL PROTECTED] (2 +1 non-binding) Daniel Kulp [EMAIL PROTECTED] Luciano Resende [EMAIL PROTECTED] no (0 or -1 votes) Many thanks to all those involved and that voted on the community vote etc... I will now pass the resolution onto the board. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
Jim Jagielski wrote: +1 ! (PS: Please add Email addresses to the Resolution). ack, will do so before I submit it to the board. many thanks Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Qpid Graduation - for top level
It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
Re: [VOTE] Graduate Buildr as TLP
+1 it is great project Carl. Luciano Resende wrote: [X] +1 Approve graduation of Buildr as a Top-Level Project (non-binding) On Mon, Nov 10, 2008 at 11:54 AM, Niklas Gustavsson [EMAIL PROTECTED] wrote: On Thu, Nov 6, 2008 at 6:03 PM, Alex Boisvert [EMAIL PROTECTED] wrote: [X] +1 Approve graduation of Buildr as a Top-Level Project Non binding. /niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Qpid Graduation - for top level (resolution)
Based on some feedback, here is the updated resolution. If there is no more feedback, I will start a vote in a day or two regards Carl. 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
Qpid Graduation - for top level (resolution)
It is with the support of our mentors and a community vote on our dev list that Qpid would like to proceed to graduation. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise). Qpid also continues to attract more contributors, so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Attached is the graduation resolution, which was critiqued (/bashed :-) on the general list on our last graduation attempt with updated would be PMC... Please review our resolution, and provide any feedback or questions before a vote is started on the general list to graduate Qpid as a top level project many thanks. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Andrew Stitcher * Carl Trieloff * Craig Russell * Gordon Sim * John O'Hara * Kim van der Riet * Lahiru Gunathilake * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Rupert Smith * Steve Huston * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
Re: Missing board reports: BlueSky, Empire-DB, Lucene.Net, Qpid, Thrift
David Crossley wrote: BlueSky, Empire-DB, Lucene.Net, Qpid, Thrift are missing their reports this month. http://wiki.apache.org/incubator/October2008 http://wiki.apache.org/incubator/ReportingSchedule -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I have posted the report Aidan had collected a week ago for Qpid. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache Qpid Incubating M3 (RC5)
As Adian is away on vacation I have summarized the thread. Binding votes marked with '*'. Here are the +1's across the release so far. Rajith RC5 http://www.mail-archive.com/general@incubator.apache.org/msg18855.html Carl RC5 http://www.mail-archive.com/general@incubator.apache.org/msg18898.html Gordon RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11732.html Arnaud RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11733.html Robert Greig RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11744.html Robert Godfrey RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11678.html *Paul Fremantle RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11745.html Steve RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11881.html Martin RC5 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11682.html *Craig RC4 http://www.mail-archive.com/general@incubator.apache.org/msg18841.html Lahiru RC4 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11643.html *Yoav RC2 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11573.html Alan Rc2 http://www.mail-archive.com/[EMAIL PROTECTED]/msg11557.html Dan had pointed out some omissions in the earlier RC's which have been corrected or no issues raised on the thread for some time now. If no one objects to the three binding votes that have been applied so far be to used to close this vote, I will close the vote Tuesday 30th September at 12 noon EST. For reference: Artifacts can be found at http://people.apache.org/~aidan/qpid/M3-RC5/ Release notes are located here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312117styleName=HtmlprojectId=12310520Create=Create please review/ vote/ comment/ regards, Carl. Marnie McCormack wrote: Hi All, I'm channelling Aidan this week By my calculations, we still require two further binding votes for this release. I wonder if anyone else could kindly take a look at the RC, lovingly crafted by Aidan, and possibly vote ? Thanks, Bfn, Marnie On Thu, Sep 11, 2008 at 8:03 PM, Paul Fremantle [EMAIL PROTECTED] wrote: +1 On Thu, Sep 11, 2008 at 7:56 PM, Robert Greig [EMAIL PROTECTED] wrote: +1 RG -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com
Re: [VOTE] Release Apache Qpid Incubating M3 (RC5)
Aidan Skinner wrote: On Thu, Sep 11, 2008 at 1:56 AM, Carl Trieloff [EMAIL PROTECTED] wrote: Are you able to summaries this vote so far for us. I believe we still need one binding vote. Since it's a restart I think we still need 3. Unless I'm missing something the vote currently stands at: +1's: 3, 0 binding Rajith Attapattu Robert Godfrey Martin Ritchie 0's: 0 -1's: 0 Having some more votes would be good :) - Aidan ok, as it is a reset - I have check the disclaimers, etc. Java has then under resources, but there is a file telling you where they are so +1 Carl
Re: [VOTE] Release Apache Qpid Incubating M3 (RC5)
Aidan, Are you able to summaries this vote so far for us. I believe we still need one binding vote. Carl. Martin Ritchie wrote: All looks good to me. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache Qpid Incubating M3 (RC4)
Aidan Skinner wrote: There were some problems with the NOTICE and LICENSE files in RC3 (is there a good guide to this anywhere? having all the individual licenses in LICENSE seems odd to me...) so I've rolled RC4[1] and would like to restart the vote to release Apache Qpid M3. I started the vote on qpid-dev at 2008-08-22: http://markmail.org/message/2a6pmx3sdgvh5bu5 And closed it on 2008-08-27 http://markmail.org/message/xb3qppr5krtdp43w There were: 8 +1s (1 of which was binding) 0 0's 0 -1's Which were cast by: Alan Conway Arnaud Simon Martin Ritchie Gordon Sim Carl Trieloff Yoav Shapira (binding) Rajith Attapattu Lahiru Gunathilake Artifacts can be found at http://people.apache.org/~aidan/qpid/M3-RC4/ Release notes are located here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312117styleName=HtmlprojectId=12310520Create=Create Please vote to: [+1] Release Apache Qpid M3 [0] que? [-1] No, there's still an issue with it which needs to be corrected - Aidan [1] I ran release.sh and uploaded the output, ritchiem did the actual leg work for this one Did a quick review - RC4 seems to have all the noted fixes in it. so my +1 stands. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache Qpid M3
they are located in the sub-dir for each language, and are specific for each lang. someone who installs C++ does not care about Python or Java readme etc or visa versa. Carl. Daniel Kulp wrote: Aidan, http://people.apache.org/~aidan/qpid/M3-RC2/qpid-incubating-M3.tar.gz doesn't have LICENSE/README/NOTICE files in the root where they would need to be. Dan On Wednesday 27 August 2008 12:49:49 pm Aidan Skinner wrote: It is with a building sense of anticipation that I am able to inform you that Qpid has voted to release Apache Qpid M3. I started the vote on 2008-08-22: http://markmail.org/message/2a6pmx3sdgvh5bu5 And closed it on 2008-08-27 http://markmail.org/message/xb3qppr5krtdp43w There were: 8 +1s (1 of which was binding) 0 0's 0 -1's Artifacts can be found at http://people.apache.org/~aidan/qpid/M3-RC2/ Release notes are located here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312117sty leName=HtmlprojectId=12310520Create=Create Please vote to: [+1] Release M3 [0] eh [-1] No, it has a significant carbon footprint, wears white shoes after labor day and also... - Aidan
Re: [DISCUSS] Do we really need an incubator?
From what I have seen many of the incubator releases have been better vetted than those from graduated projects. So I don't buy the argument. I also had to bite my tough on the maven thread.. I think it is mostly BS to give Java an easy route to publicity from inside incubator if no other coding language gets the same perks. So to be consistent, we might as well throw it all open. At that point the motivation to graduate is mostly removed. i.e. are we turning incubator into - did the project stay active to n months and is the IP clear? That would be what we are practically doing. I would personally vote -1 on the maven thread until Dims questions and the role of incubator in the new world is defined. Carl. Davanum Srinivas wrote: Roy, I see what you are saying... Do you agree that the intention is for the end user to pause for a second to understand what he/she is using and understand that there are some disclaimers etc that go along with a set of artifacts? Yes. may be this is the wrong way to enforce that intention. But may be the clever minds on the list can come up with brilliant ideas/patch to maven to make this happen in a better way? then we would not have this issue at all. Right? Yes, we are 100% behind our released artifacts. But we do need to let folks know that next month the code may not have a community behind it and hence a liability on the users since not all our projects pass incubation. No? thanks, dims On Mon, Jul 7, 2008 at 8:06 PM, Roy T. Fielding [EMAIL PROTECTED] wrote: Dims, I have to disagree. The releases that we allow incubating projects to make, with three +1s and a majority approval, are full Apache releases. They have been officially approved by the foundation and we are 100% responsible for their content. That's okay, because they also tend to receive far more detailed inspection and thus are better quality and more conforming to our policies then our pre-incubator TLPs. There is no reason for a separate repository. It certainly isn't relevant to a podling's desire to become a TLP -- that is more than adequately compensated by the freedom from slow IPMC approvals and ability to host their own website without the butt-ugly egg icon and disclaimers. A separate repo does not help protect users from incubator code, since users don't set the Maven configs that define which repos to use and which modules are dependencies. At best, what it does is add an irrelevant incubator layer on top of all Maven repo requests that masks the normal repo path from developers, introduces another way to inject insecure code, and wastes our bandwidth sending 404 responses to automated build requests. In contrast, if real incubator releases are allowed to be placed in the normal Maven locations, then the incubating config does not mask the normal Maven path, there is no need to send *all* repo requests to incubator first, the project documentation for Maven doesn't have to be a special-case, and releases are still subject to the same quality controls as all Apache releases. Regardless, the user never makes a decision regarding incubator code in the Maven repo. The user is either going to pull the incubator release directly and then build it using Maven with the provided pom, or some other project is going to make a decision to add the artifact (with incubator in its name) as a dependency. The Maven repo path is irrelevant to the user's decisions -- it just changes the background bit traffic and the load on our servers. In short, the policy is just plain stupid (speaking as a C developer who builds a few projects via Maven only a couple times a year). Yes, it would be nice if Maven was more secure, properly checked signatures, and properly delegated namespaces so that third-parties would be unable to add artifacts within other org's trees. None of those issues are specific to incubator. Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Podling status files
Martijn Dashorst wrote: I see a trend in podlings not filling in their status files. Shindig and Pig both have the bare template as their status file. Can someone (e.g. the mentors of said projects) update the status files please? I'm hoping for a completely checked status file, but in the very least I'd expect a list of initial committers augmented with the committers that were added after incubation started. A list of actual mentors is also welcomed. Martijn While we are on the subject, many people also do not do a svn up before they update their status files, etc and revert other projects files. I will not name names, but please make sure to not revert other projects status files when you update your project Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: about CCLA.
Edward J. Yoon wrote: Hello, I have some question about CCLA. Should we have a CCLA even if it is an individual work? and, In the similar context, how does that apply to an individual working for government agency? Thanks. If you are not independent -- i.e. work for a company then you should do a CCLA ICLA. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Tuscany Graduation as TLP
+1 Carl. ant elder wrote: After 29 months in the incubator, 19 releases, 25 new committers, and tons of emails the Apache Tuscany community (with support from our mentors) again feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://apache.markmail.org/message/lss5jhjxail7m67r We would like the resolution below to be presented to the board for consideration at the next possible board meeting. For additional information, the Tuscany status file is here: https://svn.apache.org/repos/asf/incubator/tuscany/STATUS Thanks in advance for your time and consideration. ...ant X. Establish the Apache Tuscany Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications built as compositions of service components. These components may be implemented with a range of technologies and connected using a variety of communication protocols. This software will implement relevant open standards including, but not limited to, the Service Component Architecture standard defined by the OASIS OpenCSA member section, and related technologies. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tuscany Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is responsible for the creation and maintenance of software related to Apache Tuscany; and be it further RESOLVED, that the office of Vice President, Apache Tuscany 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 Tuscany Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tuscany 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 Tuscany Project: * Adriano Crestani adrianocrestani at apache dot org * ant elder antelder at apache dot org * Brady Johnson bjohnson at apache dot org * Frank Budinsky frankb at apache dot org * Ignacio Silva-Lepe isilval at apache dot org * Jean-Sebastien Delfino jsdelfino at apache dot org * kelvin goodson kelvingoodson at apache dot org * Luciano Resende lresende at apache dot org * Mark Combellack mcombellack at apache dot org * Matthieu Riou mriou at apache dot org * Mike Edwards edwardsmj at apache dot org * Paul Fremantle pzf at apache dot org * Pete Robbins robbinspg at apache dot org * Raymond Feng rfeng at apache dot org * Simon Laws slaws at apache dot org * Simon Nash nash at apache dot org * Venkata Krishnan svkrish at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder be appointed to the office of Vice President, Apache Tuscany, 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 Apache Tuscany Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tuscany podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tuscany podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Account Request - Ted Ross- Qpid (incubating)
Dear root, Please create an id for Ted Ross on the Qpid project under Incubation. Preferred userid: tross Full name: Ted Ross Forwarding email address: [EMAIL PROTECTED] Requested Karma for: qpid ICLA is on file. Votes:(17: +1 which includes 3 bindings, and no -1 or 0.) Vote conducted on [EMAIL PROTECTED] and completed on [EMAIL PROTECTED] kind regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Report reviews
Marshall Schor wrote: Jukka Zitting wrote: Hi, I reviewed the submitted project reports for April. I'm not sure if people are actively following the page or the diffs, so here's a summary of my review. OK: * CouchDB * PDFBox (I'm a mentor) * Tika (I'm a mentor) OK with comments: * CXF - Good luck for the TLP! * Imperius - Issues before graduation? * JSPWiki - Issues before graduation? * Qpid - Did you understand the IPMC concerns about diversity? The report seems to indicate otherwise. Also missing: Qpid is ...? Incubating since? Comments where added in the report prior to additional reviews. * Sanselan - Issues before graduation? * Shindig - Issues before graduation? * UIMA - Too comfortable in the Incubator? Focus on growing the community and on graduating! Hi Jukka - We're not at all comfortable and have become recently more assertive in trying to entice other potentially interested parties to come and join in the development of UIMA. We completely agree with your point - we need to focus on growing our community and graduating. Please send any good prospective committers / PPMC members our way :-). -Marshall Report missing: * Buildr * FtpServer * Ivy * RCF * JuiCE * Lucene.Net BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Statements from Qpid mentors would help me decide... [WAS Re: [VOTE] Apache Qpid Graduation as TLP]
Rupert Smith wrote: Hi Daniel, Don't forget about me. I am a currently active Qpid committer and not an employee of either RedHat or JPMC. I am an independent consultant who operates through a company called The Badger Sett Ltd. and all my contributions to Qpid thus far have been completely 'legally' independent of the dominant parties. Seems I never made it onto the 0-10 credits page, but that is because I have still not found the time to fully read and provide feedback on it, as interesting as it looks. Rupert On Friday 21 March 2008, Paul Fremantle wrote: Yoav I have to say I think you have given a very good analysis. I think that QPid has come a huge way towards Apacheness. Diversity is not as great as it could be but meets the Incubator criteria. Huh? The graduation guide says there are at least 3 legally independent committers and I don't see that with Qpid. Dan, I think it has been proved that there are at least 3 legally independent committers - please can you revise your statement and/or vote. regards, Carl.
Re: Statements from Qpid mentors would help me decide... [WAS Re: [VOTE] Apache Qpid Graduation as TLP]
Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carl, If you take a step back and think about it...this process has been like pulling teeth. Don't you think there's room for all the folks on Qpid to be more open and forthcoming given this experience? I am sorry if that has been the case, but we also need to respect individuals. Let me add a few comments that might help. Over the course of the project we have received large contributions from at least 3+ legally independents. They include Rupert Smith (.NET), Colin Crist (Hermes integration / use cases), Tomas Restrepo (.NET). We also have 3 independents that have that have contributed significantly but may or may not be termed legally independent Bhupendra Bhardwaj (Java mgmt), Kevin Smith (TLS), Steven Shaw (Java). Depends if you want to rant or not. Over and above that we have no one company that has controlled the commit count as Martin has clearly pointed out. Additionally we have quite a few active independents currently on the project as Rajith has pointed out that will most like be voted on as committer if they follow through. All that said, we do have a set of committers that don't disclose there employer. Aside from that this should be enough to indicate that the project is well manged, welcoming and diverse, as the project is not overly dependent on one company. It should also be clear that we have or more than at least legally required number of parties in the project. We have seen a pattern of independents show and help create a feature they need and then become less active. I assume this is a pattern for those that can't write open source for a living but they are highly valued part of the Qpid community. personally I like people to speak for themselves, as that shows more than one face to the project. So maybe the info has not been concise but at least you know that we have a great passionate team and great mentors on this project kind regards, Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Apache Qpid Graduation as TLP
Qpid entered into the incubator November 2006, and has made releases, is in the process of closing down another minor release and well on the way to the next major release, added new committers, and cleaned up Karma prior to graduation vote. At this point the Apache Qpid community with support from its mentors feels that it is ready to graduate to an official top level project at Apache as indicated by the community and vote. We would like the resolution attached to this email to be presented to the board for consideration at the next board meeting. The charter and diversity have both been discussed: http://mail-archives.apache.org/mod_mbox/incubator-general/200803.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/incubator-general/200803.mbox/[EMAIL PROTECTED] Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 The Qpid Community (This vote has been started with the support of our mentors) == 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Alan Conway * Arnaud Simon * Carl Trieloff * Gordon Sim * John O'Hara * Marnie McCormack * Martin Ritchie * Paul Fremantle * Rajith Attapattu * Robert Greig * Robert Godfrey * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF Graduation as TLP
what is the diversity? Carl. Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me! Bruce Snyder wrote: | On Tue, Mar 18, 2008 at 9:08 AM, Daniel Kulp [EMAIL PROTECTED] wrote: | After 20 months in the incubator, 6 releases complete and 2 more on the | way shortly, several new committers, and too much email traffic :-), the | Apache CXF community (with support from our mentors) feels that we are | ready to graduate to an official top level project at Apache as | indicated by the community vote recorded at: | http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html | | We would like the resolution attached to this email to be presented to | the board for consideration at the next possible board meeting. | | For additional information, the CXF status file is here: | http://incubator.apache.org/projects/cxf.html | | Thank you in advance for your time and consideration. | | [ ] +1 | [ ] +0 | [ ] -1 | | +1 | | Woot! | | Bruce -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH3+ERgNg6eWEDv1kRAntlAJ0dGOaV3hL2JetKQZxQ2tB5JSdLggCfTV9T XO5US96T9bitGXnaqRo4l+c= =P/7h -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF Graduation as TLP
Daniel Kulp wrote: On Tuesday 18 March 2008, Carl Trieloff wrote: what is the diversity? Carl. This could have been asked as part of the resolution discussion instead of hijacking the vote, but was out last week - thanks for the info. Carl.
Re: Qpid Status page, was Re: Graduation resolution feedback - Qpid as TLP
Thanks Rajith, I guess we are then ready to start a vote. regards, Carl. Rajith Attapattu wrote: folks, I have updated the status page with the news items Carl posted. I also added Craig's name under mentors. It will take some time for it to get it synced. Regards, Rajith On Tue, Mar 18, 2008 at 2:13 PM, Carl Trieloff [EMAIL PROTECTED] wrote: Carl Trieloff wrote: Yoav Shapira wrote: No rush, I probably won't get to do it until Monday next week anyhow. Others are welcome to help as well, it's not all on your shoulders ;) Yoav We are also missing Criag as a mentor on our status page. Below I have started a list for news, please correct and add to the list. This is what I have dug out of the board reports so far. Carl Aug 06 - Acceptance into Incubator Sept 06 - Project setup Nov 06 - Creation of committer accounts Nov 06 - IP Clearance for code grant Jan 07 - New C++ build/ make system May 07 - Addition of new committers (7 by May) June 07 - Addition of .NET client June 07 - M1 release of Qpid July 07 - Addition of new committers (3 more by July) July 07 - Closing of legal questions on TCK passing all JMS TCK tests Oct 07 - M2 release of Qpid Nov 07 - Addition of new committers (2 more by Nov) Dec 07 - Moving of build system back to Ant Dec 07 - Set scope and dates for M2.1 Jan 08 - Vote of Qpid community to request graduation as TLP Feb 08 - Karma clean up, done by community process Updated, dates by looking at svn log. Carl.
Re: FW: (qpid) Diversity
Martin Ritchie wrote: On 06/03/2008, Noel J. Bergman [EMAIL PROTECTED] wrote: Daniel Kulp write: a quick svn log on their SVN repo for all commits since Jan 1 [suggests that] all but 4 commits since Jan 1 can easily be contributed to RedHat employees. I think the above should provide enough information about the health and diversity of the community that actually working on the code. What is the Qpid community's response to these findings? --- Noel Ok I have a few comments in response to the findings: - Firstly not all work is done on trunk so purely looking at trunk is not a good metric - Looking at the last two months especially as that includes the start of the year which is typically a quite period also will show poor commit numbers. - We are preparing for an M2.1 release so a lot of effort is being expended on that branch. My take would be to look at the last 6 months, which admittedly includes a number of holiday periods so the count of commits may be a little low. Since 2007-09 for the commits on the qpid repository shows: aconway 272 aidan 54 arnaudsimon 230 astitcher 16 cctrieloff 45 gsim 201 kpvdr 11 nsantos 8 rajith 169 rgodfrey 99 rgreig 98 rhs 151 ritchiem 593 rupertlssmith 468 1103RedHat 1312Non-Aligned So Redhat have less than half the commits to Qpid so I don't think this is something we should worry about. Keeping an eye on for sure, but over analysing the alignment of those people that don't want to or are not allowed to say who they work for is not something that Apache requires nor would it be beneficial. Saying that we are not diverse because a lot of work on trunk has been done by a small set of people over a two month period is not helpful to the discussion. It is also worth noting that volume of commits does not in anyway correspond to the quantity of code changed and even looking at lines changes cannot say anything for the quality. I think the fact that we have an active project that has matured to the point that where we feel as though we can self regulate in the Apache Way speaks far more to the community of the project than identifying who is paying the bills. The whole project worked very hard to pull together two servers and five client libraries for the M2 release all talking AMQP 0-8. We are again working as a community to provide a M2.1 release that will inter operate at AMQP 0-9 with other AMQP products outside the Apache world. I for one am looking forward to our future releases where we can again move the entire project on to the wholly different AMQP 0-10. What is the next step on this? Does the concern still exist or should we take the next step. regards Carl.
Re: Qpid Status page, was Re: Graduation resolution feedback - Qpid as TLP
I'm going to be off-line today. I will get you something (will pull from our board reports) and send that to you sometime this weekend - unless someone beats me to it :-) Carl. Yoav Shapira wrote: I'm happy to help update the status page, and I think I have the requisite SVN karma. What should we put on there? On Wed, Mar 5, 2008 at 1:47 PM, Luciano Resende [EMAIL PROTECTED] wrote: Shouldn't Qpid Status page (news section) have information regarding releases, voting new committers, etc These information help others to have an idea of the project dynamics ? See example [1]. [1] http://incubator.apache.org/projects/tuscany.html On Tue, Mar 4, 2008 at 7:31 AM, Carl Trieloff [EMAIL PROTECTED] wrote: Luciano Resende wrote: Have you guys been following the Graduation Guide [1][2], I was checking the status page [3] for getting information around QPid and it seems outdated. yes, I used the guide and we completed a process to clean up Karma and updated the status page a few weeks ago. Cliff had worked with us on most of the items on the status page early on, thus the dates a while back. We however did not rush to graduate so that we could get the apache processes down and benefit from the great input we have had from out mentors. Also, just out of curiosity, how are you guys doing regarding diversity, there was some discussion in the past suggesting that podlings should start disclosing members affiliation when entering and exiting incubation. There was a thread on this, which if you like I can did up -- problem is that it might have been miss-titled so it will take me a bit of digging to find it. The summary is as follows, we have added quite a large number of commiters throughout the project, just prior to graduation our Mentors suggested we use a community process to clean -up our Karma before graduating. This has been done and removed some 10+ inactive names off the list, which brings the committer count to 20. These are employed by multiple organizations. It should also be noted that we have received substantial contributions from 6 other people that are credited at http://cwiki.apache.org/qpid/people.html [1] http://incubator.apache.org/guides/graduation.html [2] http://incubator.apache.org/guides/graduation.html#notes-status We have completed all the step at the bottom of the page on: http://incubator.apache.org/projects/qpid.html Is it required to edit in comments on the no date items at the bottom of that page? -- If so we can do so. Carl. [3] http://incubator.apache.org/projects/qpid.html On Mon, Mar 3, 2008 at 6:31 AM, Carl Trieloff [EMAIL PROTECTED] wrote: Yoav Shapira wrote: On Mon, Mar 3, 2008 at 7:33 AM, Santiago Gala [EMAIL PROTECTED] wrote: less awareness of their activity in both directions. The worse part of it is that the lack of awareness will probably reduce the probability of any of the PMC members to be nominated for ASF membership... perpetuating the disconnect. Ahh, good one! Makes sense. Qpid PPMC, assuming no one objects, please add me to your TLP resolution as a PMC member. If someone objects, let's talk on qpid-private. Yoav Fantastic, glad to have you. Will add you when we send out an update or the vote. Carl. -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: (qpid) Diversity
sebb wrote: On 05/03/2008, Roland Weber [EMAIL PROTECTED] wrote: Marnie McCormack wrote: All, Several of our project (Qpid) memebers are legally in a difficult position disclosing their employer in Apache world. Does that mean they are contributing in their private time rather than as part of their jobs? If so, they should be considered as independents. If contributing to the project is part of their job responsibilities, they should be required to disclose the employer. If the actual employers cannot be disclosed, perhaps it would be possible to list the different companies anonymously? e.g. Company 1 employs Adrian, Barbara, Cedric Company 2 employs Peter, Quentin, Rick This might help with determining diversity. This could work, Carl.
Re: Graduation resolution feedback - Qpid as TLP
Luciano Resende wrote: Have you guys been following the Graduation Guide [1][2], I was checking the status page [3] for getting information around QPid and it seems outdated. yes, I used the guide and we completed a process to clean up Karma and updated the status page a few weeks ago. Cliff had worked with us on most of the items on the status page early on, thus the dates a while back. We however did not rush to graduate so that we could get the apache processes down and benefit from the great input we have had from out mentors. Also, just out of curiosity, how are you guys doing regarding diversity, there was some discussion in the past suggesting that podlings should start disclosing members affiliation when entering and exiting incubation. There was a thread on this, which if you like I can did up -- problem is that it might have been miss-titled so it will take me a bit of digging to find it. The summary is as follows, we have added quite a large number of commiters throughout the project, just prior to graduation our Mentors suggested we use a community process to clean -up our Karma before graduating. This has been done and removed some 10+ inactive names off the list, which brings the committer count to 20. These are employed by multiple organizations. It should also be noted that we have received substantial contributions from 6 other people that are credited at http://cwiki.apache.org/qpid/people.html [1] http://incubator.apache.org/guides/graduation.html [2] http://incubator.apache.org/guides/graduation.html#notes-status We have completed all the step at the bottom of the page on: http://incubator.apache.org/projects/qpid.html Is it required to edit in comments on the no date items at the bottom of that page? -- If so we can do so. Carl. [3] http://incubator.apache.org/projects/qpid.html On Mon, Mar 3, 2008 at 6:31 AM, Carl Trieloff [EMAIL PROTECTED] wrote: Yoav Shapira wrote: On Mon, Mar 3, 2008 at 7:33 AM, Santiago Gala [EMAIL PROTECTED] wrote: less awareness of their activity in both directions. The worse part of it is that the lack of awareness will probably reduce the probability of any of the PMC members to be nominated for ASF membership... perpetuating the disconnect. Ahh, good one! Makes sense. Qpid PPMC, assuming no one objects, please add me to your TLP resolution as a PMC member. If someone objects, let's talk on qpid-private. Yoav Fantastic, glad to have you. Will add you when we send out an update or the vote. Carl.
Re: Graduation resolution feedback - Qpid as TLP
sebb wrote: On 29/02/2008, Carl Trieloff [EMAIL PROTECTED] wrote: Comments on last version .. - It looks like you are using a non-applicable template for the board resolution. Take a look at other incubator graduation resolutions. - Specifically, the paragraph on establishing bylaws isn't applicable, and the incubator needs to be discharged of responsibility. -See below - only half of the above seems to have been addressed. Still seems recursive to me, see below. Take a look below at the update and see what you think... I believe I have fixed the recursion you noted. RESOLVED, that the initial Apache Qpid Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Qpid Project; and be it further Is the above paragraph needed? Checking with our mentors it seems that it is needed. any particular reason why you believe otherwise or just asking to be sure? Updated 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to the distributed messaging; a multiple language implementation providing daemons and API's for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Messaged Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Alan Conway * Arnaud Simon * Carl Trieloff * Gordon Sim * John O'Hara * Marnie McCormack * Martin Ritchie * Paul Fremantle * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 Qpid Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Qpid Project; and be it further RESOLVED, that all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
Re: Graduation resolution feedback - Qpid as TLP
Henri Yandell wrote: On Mon, Mar 3, 2008 at 12:23 AM, Upayavira [EMAIL PROTECTED] wrote: On Mon, 2008-03-03 at 12:12 +0800, Niclas Hedhman wrote: On Saturday 01 March 2008 22:18, sebb wrote: None of the mentors seem to be included. Perhaps this is normal for graduating podlings? Often Mentors have no direct involvement in the codebase being produced, and therefor no vested interested of committership/PMC. However, I, as a IPMC member, would expect the mentors to hang around the graduated PMC (for TLPs) a while after the graduation just to provide support if needed, and make sure everything is running smoothly. I would go one further - I'd expect at least some of the mentors to be members of the graduated PMC for some time. Without that, it is quite possible that we have a PMC that has no ASF members on it (of course, not all mentors are ASF members). Given that ASF members are the glue that keep the foundation together, having some members on every PMC is important. And in fact is the one form question that gets asked by the board when looking at the resolutions - Who are the members?. Cliff Schmidt Paul Fremantle Yoav Shapira Scott Deboy and most recently help from Craig Russell Paul and Yoav have indicated they will be remaining on the PMC post graduation. Carl.
Re: March of the Reports
Noel J. Bergman wrote: Needless to say, it is that time again, when Incubator Reports march towards their inevitable meeting with the Board. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Neol, This would be Qpid's month to report -- Should we create one, or just continue the graduation thread and if we pass the vote, take the resolution to the board, if the vote does not pass report next month? Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: March of the Reports
yea, you are right, me got it wrong in my head. Carl. Daniel Kulp wrote: Carl, According to: http://wiki.apache.org/incubator/ReportingSchedule Qpid isn't support to report till April. Dan On Tuesday 04 March 2008, Carl Trieloff wrote: Noel J. Bergman wrote: Needless to say, it is that time again, when Incubator Reports march towards their inevitable meeting with the Board. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Neol, This would be Qpid's month to report -- Should we create one, or just continue the graduation thread and if we pass the vote, take the resolution to the board, if the vote does not pass report next month? Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Graduation resolution feedback - Qpid as TLP
sebb wrote: On 04/03/2008, Carl Trieloff [EMAIL PROTECTED] wrote: sebb wrote: On 29/02/2008, Carl Trieloff [EMAIL PROTECTED] wrote: Craig L Russell wrote: Comments on last version .. - It looks like you are using a non-applicable template for the board resolution. Take a look at other incubator graduation resolutions. - Specifically, the paragraph on establishing bylaws isn't applicable, See below. and the incubator needs to be discharged of responsibility. -See below - only half of the above seems to have been addressed. Still seems recursive to me, see below. Take a look below at the update and see what you think... I believe I have fixed the recursion you noted. RESOLVED, that the initial Apache Qpid Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Qpid Project; and be it further Is the above paragraph needed? Checking with our mentors it seems that it is needed. any particular reason why you believe otherwise or just asking to be sure? Because of the comment above: Specifically, the paragraph on establishing bylaws isn't applicable, Happy to remove it -- any of our mentors want to comment? Some board reports have it some do not. For example the latest Synapse resolution does not. Updated 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 distributed messaging, for distribution at no charge to the public. May need to mention AMQP in the above paragraph. looking at some of the recent resolutions, they separated definition of the term used in the first paragraph to the third to avoid recursion... Based on comments I think it is cleaner to not try to expand the definition in two places. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to the distributed messaging; a multiple language the distributed messaging = distributed messaging ack implementation providing daemons and API's for publish API's = APIs ack subscribe, eventing and a wide range of message distribution patterns based on the Advanced Messaged Queuing Protocol (AMQP) and s/Messaged/Message/ ack related technologies such as (transaction management, federation, security, management); and be it further How is this distributed messaging different from ActiveMQ? Is it just because it is based on AMQP? yes, it is based on AMQP, provides native support for clients in multiple languages and focuses less on JMS as design center, rather AMQP and provides JMS as a client API if required. Much like Ant, Maven and Builder, all build systems but the way they do it is quite different. Update attached: 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid Project; and be it further RESOLVED, that the persons listed immediately below be and hereby
Re: FW: (qpid) Diversity
Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carl, Do they *all* have CCLA's? absolutely. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Graduation resolution feedback - Qpid as TLP
Yoav Shapira wrote: On Mon, Mar 3, 2008 at 7:33 AM, Santiago Gala [EMAIL PROTECTED] wrote: less awareness of their activity in both directions. The worse part of it is that the lack of awareness will probably reduce the probability of any of the PMC members to be nominated for ASF membership... perpetuating the disconnect. Ahh, good one! Makes sense. Qpid PPMC, assuming no one objects, please add me to your TLP resolution as a PMC member. If someone objects, let's talk on qpid-private. Yoav Fantastic, glad to have you. Will add you when we send out an update or the vote. Carl.
Re: Graduation resolution feedback - Qpid as TLP
Comments on last version .. - It looks like you are using a non-applicable template for the board resolution. Take a look at other incubator graduation resolutions. - Specifically, the paragraph on establishing bylaws isn't applicable, and the incubator needs to be discharged of responsibility. - Can you rework this; it's simply too recursive. Deconstruct Qpid Messaging back to it's purpose/definition. Thanks :) Attached is an updated charter with corrections for these. Please review Kind regards. 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 Qpid messaging implementation, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to the Qpid messaging implementation; a multiple language implementation based on the Advanced Messaged Queuing Protocol (AMQP) and related technologies such as messaging transaction management, federation, security, management; and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Alan Conway * Arnaud Simon * Carl Trieloff * Gordon Sim * John O'Hara * Marnie McCormack * Martin Ritchie * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 Qpid Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Qpid Project; and be it further RESOLVED, that all responsibility pertaining to the Qpid Project encumbered upon the Apache Incubator be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Graduation resolution feedback - Qpid as TLP
The Qpid community has being working through the process to graduate. Before we formally have one of our mentors start the vote on the Incubator lists we would like to invite any additional comments from the general list on the resolution. Background: The Qpid community has made releases, had many new commiters join the project, cleared all legal items and completed a process of cleaning up Karma using a community process. A community vote has been taken to check the project wants to graduate as TLP. The Qpid community would thus like to attempt graduation. Please take a few minutes and provide us feedback on the charter before we start the vote process. The Qpid project. Here is our 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 Apache Qpid Messaging implementations, 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 Qpid PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid PMC be and hereby is responsible for the creation and maintenance of the Qpid Messaging implementations, clients and related software components, based on software licensed to the Foundation; and for ensuring that the Qpid community pursue its goal of furthering the adoption of an open network protocol implementation for messaging in the spirit of the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Qpid 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 Qpid PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid PMC: Alan Conway Arnaud Simon Carl Trieloff Gordon Sim John O'Hara Marnie McCormack Martin Ritchie Rafael Schloming Rajith Attapattu Robert Greig Robert Godfrey NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be and hereby is appointed to the office of Vice President, Apache Qpid, 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 Qpid PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Qpid Project. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Graduation resolution feedback - Qpid as TLP
Guillaume Nodet wrote: On Thu, Feb 28, 2008 at 3:20 PM, Carl Trieloff [EMAIL PROTECTED] wrote: RESOLVED, that the Apache Qpid PMC be and hereby is responsible for the creation and maintenance of the Qpid Messaging implementations, clients and related software components, based on software licensed to the Foundation; and for ensuring that the Qpid community pursue its goal of furthering the adoption of an open network protocol implementation for messaging in the spirit of the Foundation; and be it further Should it be a bit more descriptive wrt to the technical goal of the QPid TLP ? The goal of a TLP in the ASF is to deliver software, not to furthering the adoption of anything ... The ASF does not promote any technology. Thanks for the feedback, we used ant project as the example as they have a very nice set of documented practices. On the second part I take the point on promoting technology, given that - do you think it would be good/better to explicitly name the specification we implement, or just make the description more embellished? Carl. Carl.
Re: Graduation resolution feedback - Qpid as TLP
Thanks, I'll correct. Carl. Craig L Russell wrote: Hi Carl, It looks like you are using a non-applicable template for the board resolution. Take a look at other incubator graduation resolutions. Specifically, the paragraph on establishing bylaws isn't applicable, and the incubator needs to be discharged of responsibility. Craig On Feb 28, 2008, at 6:20 AM, Carl Trieloff wrote: The Qpid community has being working through the process to graduate. Before we formally have one of our mentors start the vote on the Incubator lists we would like to invite any additional comments from the general list on the resolution. Background: The Qpid community has made releases, had many new commiters join the project, cleared all legal items and completed a process of cleaning up Karma using a community process. A community vote has been taken to check the project wants to graduate as TLP. The Qpid community would thus like to attempt graduation. Please take a few minutes and provide us feedback on the charter before we start the vote process. The Qpid project. Here is our 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 Apache Qpid Messaging implementations, 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 Qpid PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid PMC be and hereby is responsible for the creation and maintenance of the Qpid Messaging implementations, clients and related software components, based on software licensed to the Foundation; and for ensuring that the Qpid community pursue its goal of furthering the adoption of an open network protocol implementation for messaging in the spirit of the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Qpid 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 Qpid PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid PMC: Alan Conway Arnaud Simon Carl Trieloff Gordon Sim John O'Hara Marnie McCormack Martin Ritchie Rafael Schloming Rajith Attapattu Robert Greig Robert Godfrey NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be and hereby is appointed to the office of Vice President, Apache Qpid, 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 Qpid PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Qpid Project. Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Binding term
Craig L Russell wrote: I think it's confusing people to use the term binding in different contexts. I'd like to propose that the term is only used to refer to decisions/votes that are binding on The Apache Software Foundation, which means decisions/votes made by a duly authorized PMC. In particular, the following text implies that a PPMC has a binding voice: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: I'd prefer if the text only the PPMC member votes are binding were changed to only the PPMC member votes are counted. Better still, simply remove the entire text , and only the PPMC member votes are binding. Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! Agree with Craig, the text above took me a while to work out what was going and because PPMC votes are 'not' binding only IPMC votes are in the incubator. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
agree that rename is required. Carl. Paul Fremantle wrote: Hans My understanding is that you do need to change the package names, but I'd like to see who else chimes in here. Any decent Java IDE will rename the packages and fix up the code without too much hassle. Paul On 1/22/08, Hans Granqvist [EMAIL PROTECTED] wrote: Hi I want to move a failed incubation project (TSIK) to Google Code, but the source is full of org.apache.* packages, so I'm not sure what the right way to do this is. (The code would keep the same ASF 2.0 license.) Changing the package names will break any and all code, so if it'd be great if that's avoidable. Thanks, Hans - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Move Project Yoko to Apache Geronimo and Apache CXF
Just to make sure I understand what is happening here - Yoko is going away/ending and getting merged into Geronimo and CXF? Carl. Alexey Petrenko wrote: +1 2007/12/11, Matt Hogstrom [EMAIL PROTECTED]: Below is a proposal that was discussed and brought forward by the Yoko Community. In a nutshell the proposal is to create a Yoko sub-project of Apache Geronimo for the Core ORB and to move the bindings to CXF. Please read the proposal below for all the detail. This proposal was brought forward to the Apache Geronimo and Apache CXF communities. Both communities have voted to accept this proposal. Vote results from Apache Geronimo were 20 +1 votes and no 0 or -1 votes. 17 were binding from the Geronimo PMC. CXF Results on the CF Dev list were 13 +1 votes and 1 0 vote I am now bringing this to the Incubator for final approval so that the code can be moved from Incubator to the respective receiving projects. This proposal was previously sent to the IPMC for comment while the respective communities discussed and voted. During that time there has been no comments that indicated there was an issue so I bring this vote back to the Incubator for finalization: [ ] +1 Approve the below proposal and code migration to Apache Geronimo and CXF respectively [ ] 0 No opinion [ ] -1 Do not approve of the move (please provide rationale If someone wants to comment on this thread please use the Alternate [DISCUSS] thread and not the vote thread. This vote will conclude on Dec 14th at 0900 ET. Original Proposal The members of project yoko have been considering the future of Yoko as a project. There have been several milestones delivered and the project is used by other ASF projects. The project is not as active as other ASF projects and it makes sense to move the code from Yoko to other projects. The Yoko team has the following proposal for your consideration. Proposed Code Donation from Project Yoko to Apache CXF and Apache Geronimo The Yoko community has been successful in delivering several milestones of the ORB implementation while in the Apache Incubator. These milestones are used by other Apache projects (namely Geronimo and Harmony) to support their releases. The WebServices bindings are dependent on CXF. The Yoko community has decided that the Yoko project does not have quite the momentum to carry itself as an independent project but has sufficient value for other projects for them to consider receiving the code and committers for that code-base as sub-projects. Since the code under consideration is used by Apache Geronimo, Apache CXF and Apache Harmony the movement of the code should continue to allow for independent releases so the code can be easily shared with other dependent projects. The proposed division is: yoko-spec-corba - this is the org.omg interface classes. rmi-spec - this is the javax.rmi spec implementation core - This is the actual ORB implementation. rmi-impl - This is the implementation of the RMIIIOP support. These modules are also used by Harmony. In addition to the code we propose that the following committers in Apache Yoko be accepted as committers in Apache Geronimo given their demonstration of delivering code, creating releases and functioning as a community. Those noted with asterisks are already Geronimo committers. Continued involvement with the core: Rick McGuire * David Jencks * Alan Cabrera * Lars Kuhne Alexey Petrenko Darren Middleman The remainder of the modules in Yoko are part of the webservices support and are independent of the underlying ORB implementation. api -- interface classes used for the web services support. bindings -- code to implement the CORBA-Web services bindings. tools -- tools for generation WSDL and IDL for the bindings maven-plugin -- some maven plugins that can use the tools for generating binding-related build artifacts. None of the maven-plugin code is used by the ORB. There is also a distribution directory with some sample applications. One set of samples demonstrates using the core ORB, the other set is for WebServices. We recommend that the distribution directory should move to Apache CXF as the webservices examples use the orb samples to bind them as web services. Since Apache Geronimo's only use of CORBA is for exporting EJBs, these samples are not particularly valuable for Geronimo. The Yoko community did not have any committers that expressed an interest in continuing work on these bindings. As such, only the code would be moving to apache CXF. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal Draft]BlueSky-Wish to ADD
J Aaron Farr wrote: Ting Peng [EMAIL PROTECTED] writes: Now, we are going to move our project BlueSky (Blue Sky Distance Collaboration System) to Apache Incubator for future development... 你好 The proposal is interesting, but I have a few concerns. I can't get to http://202.117.16.176/ from Hong Kong, so I cannot see the code or website. link also does not work from US. Carl.
Re: 'Handling Crypto..' - River project
Top-posting as it is related but different question. I would like to contribute to the apache legal questions/ answers / discussing. What is the process for joining apache legal? (I am not a lawyer) Carl. William A. Rowe, Jr. wrote: Keep in mind, Sun stuff wasn't necessarily handled under generally available open source TSU (exception) classifications, but as commercial product. This is, in part, why distributors may have issues using our exceptions and our classifications (their export legal advisors know better). For these questions, always kick them across to [EMAIL PROTECTED] please :) Bill Jim Hurley wrote: We're (River incubator project) trying to comply with: Handling Cryptography within an ASF Release http://www.apache.org/dev/crypto.html This process talks only about software that has been self classified as 5D002 (has strong crypto classification). Parts of the Sun Jini Technology Starter Kit (the base contribution for the River project) were classified as 5D992.b.1, which is a different classification. From the ASF perspective, should we treat this (5D992) classification as effectively no crypto? Need some guidance and insight to help us understand what we need to do to comply. thanks -Jim [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
We could add rules indefinitely to make just about anyone not usable... I don't have any issues with Pig. Carl. Yoav Shapira wrote: Hey, On 9/24/07, Doug Cutting [EMAIL PROTECTED] wrote: Niclas Hedhman wrote: a) The name Pig is somewhat provocative (not kosher/halal) and I would like to hear the rationale behind the name, and whether there are any willingness to look for another name. It is not meant to be provocative. It is named after the animal and is not an acronym. It also provides a convenient name for the query language, Pig Latin. I'm sure that the developers would have some regret about changing the name, but if it were truly determined to be offensive then I believe there would be a willingness to change it. As another Jewish person on the list, I don't find it the least bit provocative. It's a freakin' animal, that's all ;) In fact, I'm a big fan of more fun names around here. Succubus, Imperius, Pig, all are great in my book. I'm tried of four-letter acronyms and packaging that's been through N layers of marketing analysis ;) Let's not do this: http://video.google.com/videoplay?docid=36099539665548298 Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NMS
Coping incubator general and apache legal lists on this thread for additional comments on this topic. Carl. John O'Hara wrote: Yes, IBM are I fully paid up licensee of Java technology - and can do whatever they like with it. I asked permission of IBM if we could implement the XMS API some time back, and they said they did not have the right to grant that approval Unless Apache has a license to do this that I am not aware of, we are not on safe ground since NMS is clearly a derived work of JMS. Wait for the lawyers John On 01/06/07, Colin Crist [EMAIL PROTECTED] wrote: In case you've not seen this, IBM have long since rendered the JMS API into C++, C and C# http://www.ibm.com/developerworks/websphere/library/techarticles/0509_philli ps/0509_phillips.html Colin. -Original Message- From: Arnaud Simon [mailto:[EMAIL PROTECTED] Sent: 01 June 2007 15:34 To: [EMAIL PROTECTED]; general@incubator.apache.org Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: NMS Hello, We have been thinking about implementing the NMS API as part of the QPID .Net client. However we are concerned about potential legal issues. It seems to me that the NMS API is very similar to the JMS one but the JMS specification specifically licenses the technology only for Java. This is the relevant license, copied directly from the JMS Spec document: Subject to the terms and conditions of this license, Sun hereby grants you a fully-paid, non-exclusive, non-transferable, worldwide, limited license (without the right to sublicense) under Sun's intellectual property rights to review the Specification internally solely for the purpose of designing and developing your Java applets and applications intended to run on the Java platform. Other than this limited license, you acquire no right, title or interest in or to the Specification or any other Sun intellectual property. The Specification contains the proprietary information of Sun and may only be used in accordance with the license terms set forth herein. This license will terminate immediately without notice from Sun if you fail to comply with any provision of this license. Upon termination or expiration of this license, you must cease use of or destroy the Specification. Does anybody know if this concern has already been raised? Regards Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PPMC guidance on new committers
One more question on this topic as I have also seen differing views from different members of the Incubator PMC on: Who can and who can not send the account setup mail to root? Given each new committer vote will have 3 PMC votes, why does a mentor have to send the account setup to root? Why can't the mail to root just contain a link to the vote result with 3 PMC members on it from the general list? Some PMC members have the view that any PPMC member should be able to send the account setup to root to learn the system, others say it has to be a mentor. Cliff has kindly taken care of most of these mail for us so far so this is more theoretical, however having clarity on this in the document would also be good as I have wondered about the reasoning behind this practice. If the mail to root has to be cc-ed to general list and PPMC and has 3 PMC votes on it then it would seem to me that it could be send by anyone. Carl. Craig L Russell wrote: Having seen this identical discussion at least half a dozen times, I've committed changes to the guides/ppmc document removing the distracting (P) from the discussion on new committers. The new text says Only votes cast by Incubator PMC members are binding. If the vote is positive, and the contributor accepts the responsibility of a committer for the project, the contributor formally becomes an Apache committer. An Incubator PMC member should then follow the documented procedures to complete the process, and CC both the Incubator PMC and the PPMC when sending the necessary e-mails to root. I included the redundant Incubator in Incubator PMC simply to reinforce Noel's comment that PMC means Incubator PMC. Craig On May 29, 2007, at 8:49 PM, Noel J. Bergman wrote: Yoav Shapira wrote: I voted +0, not having had time to review the proposed committer's contributions. +1 != +0 I always thought (and the documentation at http://incubator.apache.org/guides/ppmc.html) says PPMC votes are binding. It says (P), and the (P) clearly does not belong. Notice that elsewhere it properly says PPMC, with no (), and the places that are wrong were PMC to which someone added (P). Likewise IPMC should simply be PMC. There is only one PMC: the Incubator PMC. I don't know how to say this more clearly. The PPMC is not a recognized entity in the ASF Bylaws. The PMC is the legal entity, and only PMC votes count in any ASF project. PPMC members should still vote, as can other members of the community, but as a legal matter, only PMC votes are binding. This is not Incubator policy, it is how the ASF works. It is the same in Jakarta, for example, where any Jakarta Committer who isn't on the PMC can vote, but only Jakarta PMC votes count. For years people didn't understand this, but please understand that Jakarta is the source of many of the wrong and bad practices in ASF projects that didn't go through either the HTTP Server project or the Incubator. the documentation link above is out of date. It was never in date. It is wrong, regardless of date. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PPMC guidance on new committers
Craig L Russell wrote: Hi Carl, On May 30, 2007, at 6:14 AM, Carl Trieloff wrote: One more question on this topic as I have also seen differing views from different members of the Incubator PMC on: Who can and who can not send the account setup mail to root? Given each new committer vote will have 3 PMC votes, why does a mentor have to send the account setup to root? Why can't the mail to root just contain a link to the vote result with 3 PMC members on it from the general list? This is a question that I believe only infrastructure can answer. The issue is that right now, root has to respond only to emails from PMC chairs, and it's easy to verify that it's really the PMC chair sending the request. Some PMC members have the view that any PPMC member should be able to send the account setup to root to learn the system, others say it has to be a mentor. Cliff has kindly taken care of most of these mail for us so far so this is more theoretical, however having clarity on this in the document would also be good as I have wondered about the reasoning behind this practice. If the mail to root has to be cc-ed to general list and PPMC and has 3 PMC votes on it then it would seem to me that it could be send by anyone. If anyone can send the request, then root has to do more work by verifying the vote thread, following the link provided in the message, to make sure that the request is valid. I agree that it's better for the PPMC members themselves to be able to make the request to root, but I'd have to leave it up to infrastructure to decide if they can handle it. Craig, Thanks, that is a meaningful/practical reason. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] Arnuad Simon as committer for Qpid
The following vote has been open for 6 days, Here is the vote result to add Arnuad Simon to the Qpid project. regards Carl. Vote results so far 15 +1 votes 1 0 No -1. +1 votes Cliff Schmidt Paul Frematle Alan Conway Kevin Smith Andrew Stitcher Rajith Attapattu Tomas Restrepo Kim van der Riet Martin Ritchie Rupert Smith Gordon Sim Robert Grieg Robert Godfrey Carl Trieloff Rafael Schloming 0 vote: Yoav Shapira Vote thread -- note two links as I first incorrectly posted without [vote], added [vote] minutes later... http://mail-archives.apache.org/mod_mbox/incubator-qpid-dev/200705.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/incubator-qpid-dev/200705.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding new committers process
Noel J. Bergman wrote: Upayavira wrote: If your private@ list vote had three +1s from IPMC members (e.g. your mentors), then IMO all you need to do is inform the IPMC of the vote when complete. Should probably notify the PMC at the time of the vote. the request for an account should be sent by an IPMC member, likely one of your mentors. +1 The idea of the IPMC taking control seems a little strange - I cannot imagine the IPMC being sufficiently organised/motivated to do that work. Your mentor however, who is also an IPMC member, should be sufficiently motivated. Agreed. I don't personally want to see the IPMC private list given over to voting in new committers on podlings. That would make, IMO that list pretty unusable. My take on Noel's comments is that the podling should ensure that it has got 3 +1s from IPMC members. Correct. IMO, a notice of the vote to private@ isn't a bad idea, and shouldn't be a high volume issue. A suggestion that one of our mentors had made to us was to do a poll for concerns on the private list to see if PPMC was happy with the committer to be added to the project (notice and to see if any of PPMC have concerns). If all went well on the PPMC list, the suggestion was to then conduct the vote on the public list. So far this has worked quite well. The vote that I posted to the general list earlier today was done in this manner. Carl.
Re: Adding new committers process
Noel J. Bergman wrote: Carl Trieloff wrote: A suggestion that one of our mentors had made to us was to do a poll for concerns on the private list to see if PPMC was happy with the committer to be added to the project (notice and to see if any of PPMC have concerns). If all went well on the PPMC list, the suggestion was to then conduct the vote on the public list. So far this has worked quite well. That's similar to a suggestion of Roy's. yes. The vote that I posted to the general list earlier today was done in this manner. Unless I've miscounted, there's an issue with that vote. Resolvable. See my reply. A vote has been added to clear it up. Thanks Henri. Carl.
Re: WANTED: Another Mentor for QPid
Yoav, Yes thank you, that would be great. Regards, Carl. Yoav Shapira wrote: Qpid peeps, I'll be glad to help as a qpid mentor if you still need someone. Yoav On 5/14/07, Martin Ritchie [EMAIL PROTECTED] wrote: Hi, just wanted to keep this thread alive as it has been almost a month and we are still a mentor short. Regards On 12/04/07, Carl Trieloff [EMAIL PROTECTED] wrote: Brian, It would be fantastic to have you help us out in Qpid if you can make it happen. regards Carl. Brian McCallister wrote: On Apr 10, 2007, at 10:58 PM, Brian McCallister wrote: If someone can step up to help OpenJPA I will trade off :-) I haven't been a fantastic mentor for OpenJPA, anyway :-( (Not trying to ditch OpenJPA, just trying to open up options :-) -Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Martin Ritchie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Add Tomas Restrepo as a Qpid Committer
Please could a IPMC member help us with the IPMC 3rd vote for this committer Carl. Paul Fremantle wrote: +1 from me Paul On 4/10/07, Cliff Schmidt [EMAIL PROTECTED] wrote: On 3/15/07, Marnie McCormack [EMAIL PROTECTED] wrote: All, This vote closed on Tuesday night and the result is as follows: Votes Cast: 9+ 0- Thus, Tomas Restrepo should now be created as a committer on the Qpid project. Although this vote closed several weeks ago, I'm adding my +1 as one of the mentors and a member of the Incubator PMC. Cliff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Add Rupert Smith as a Qpid Committer
Please could a IPMC member help us with the IPMC 3rd vote for this committer Carl. Paul Fremantle wrote: +1 from me. Paul On 4/10/07, Cliff Schmidt [EMAIL PROTECTED] wrote: On 3/15/07, Marnie McCormack [EMAIL PROTECTED] wrote: All, This vote closed on Tuesday night and the result is as follows: Votes Cast: 9+ 0- Thus, Rupert Smith should now be created as a committer on the Qpid project. Although this vote closed several weeks ago, I'm adding my +1 as the mentor and member of the Incubator PMC. Cliff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Add Kevin Smith as a Qpid Committer
Please could a IPMC member help us with the IPMC 3rd vote for this committer Carl. Paul Fremantle wrote: +1 from me. Paul On 4/10/07, Cliff Schmidt [EMAIL PROTECTED] wrote: On 3/15/07, Marnie McCormack [EMAIL PROTECTED] wrote: All, This vote closed on Tuesday night and the result is as follows: Votes Cast: 6+ 0- Thus, Kevin Smith should now be created as a committer on the Qpid project. Although this vote closed several weeks ago, I'm adding my +1 as the mentor and member of the Incubator PMC. Cliff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing reports
Jukka Zitting wrote: Hi, The reports from the following projects are still missing: FtpServer Heraldry Ivy JuiCE Lucene.Net NMaven Qpid Please add your reports to http://wiki.apache.org/incubator/April2007. PS. The TripleSoup and UIMA reports are missing the incubating since information. BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I thought I had done ours (Qpid) -- anyway I will make sure it is up on the wiki COB today. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WANTED: Another Mentor for QPid
Brian, It would be fantastic to have you help us out in Qpid if you can make it happen. regards Carl. Brian McCallister wrote: On Apr 10, 2007, at 10:58 PM, Brian McCallister wrote: If someone can step up to help OpenJPA I will trade off :-) I haven't been a fantastic mentor for OpenJPA, anyway :-( (Not trying to ditch OpenJPA, just trying to open up options :-) -Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: January 2007 Incubator Report (Revised)
Noel J. Bergman wrote: Carl Trieloff wrote: We created a report for Qpid. I guess that we mailed it to the wrong location, where should the report be sent for inclusion? The Wiki is the staging area for the report, or you can post to [EMAIL PROTECTED] Where did you send it? --- Noel Noel, Here is the mail, Should sent it for us and should be able to tell you where he sent it. Regards Carl. snip from our list Hello fellow PPMC memebers, I have put together a report with some help from Carl that I present here for your comments and suggestions. I would like to submit this report on Friday so if you can get your comments to me by then I will integrate them and post the results. -- Martin January Incubator Report for Apache Qpid. The Apache Qpid Project provides an open and interoperable, multiple language implementations of the Advanced Messaged Queuing Protocol (AMQP) specification Date of entry to the Incubator : 2006-09 Top three items to resolve before graduation 1. Defining a policy for adding new committers 2. Understanding the details between JCP and announce compliance 3. Making sure we are comfortable with the working relationship between Qpid and the AMQP Working Group. Our STATUS file is up-to-date. * Any legal, cross-project or personal issues that still need to be addressed? The whole project has not gone through release review and the license files and notices need to be checked for all languages and components. * Latest developments. Since entering into incubation we have had one release of the java code base (M1). Development has been moving forward. with improvements in memory footprint management passing the JMS TCK in with the java broker. Addition of .NET client Contributions from 5+ non committers The creation of the first draft of Web site General progress on all models in the code base * Plans and expectations for the next period? During the next period we plan on improving the stability of all language variants. Working towards a standard interoperability test suite and improved test code coverage of the whole code base. To this end we would like to get all the languages passing each others tests. We will also be pushing forward official JMS compliance certification for both brokers. Would like to create a release of the full code set
Re: January 2007 Incubator Report (Revised)
Fixed typo in-line... Carl Trieloff wrote: Noel J. Bergman wrote: Carl Trieloff wrote: We created a report for Qpid. I guess that we mailed it to the wrong location, where should the report be sent for inclusion? The Wiki is the staging area for the report, or you can post to [EMAIL PROTECTED] Where did you send it? --- Noel Noel, Here is the mail, Martin sent it for us and should be able to tell you where he sent it. Regards Carl. snip from our list Hello fellow PPMC memebers, I have put together a report with some help from Carl that I present here for your comments and suggestions. I would like to submit this report on Friday so if you can get your comments to me by then I will integrate them and post the results. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: January 2007 Incubator Report (Revised)
Noel, We created a report for Qpid. I guess that we mailed it to the wrong location, where should the report be sent for inclusion? Carl Noel J. Bergman wrote: More and more ASF Members continue to join the Incubator PMC to help shephard projects through the process. ActiveMQ is the latest of a recent string of ASF Projects asking to go TLP. Solr requested graduation to the Lucene project. Synapse graduated to the WS project. Agila has been placed into a dormancy status, with only the retirement of the mailing lists outstanding (http://issues.apache.org/jira/browse/INFRA-1056). AltRMI is also being placed in a dormant status. Others are likely to follow. We may suggest that other TLPs that have dormant codebases move them to a dormant/ (or some such) area of the Incubator, so that people can see the existance of the code, and it can be revived in-place if a community forms around it. === Incubator monthly reports for January 2007 The following projects failed to report on time: * Ivy * JuiCE * Qpid * Roller === Agila === Agila was retired this quarter with only the retirement of the mailing lists outstanding (http://issues.apache.org/jira/browse/INFRA-1056). === CXF === Project name - CXF Description - SOA enabling framework, web services toolkit Date of entry - August, 2006 Top three items to resolve - 1. Diversity - Active commiters are 90% IONA people 2. Growth of community - related to diversity, we have not yet had the opportunity to add additional commiters. The traffic on the dev list is steady. With milestone 1 out, we are beginning to attract users. Traffic on the user list is now growing. 3. Not enough documentation or work occuring on the wiki. Community aspects: * Lots of discussions about various topics (Reliable Messaging, tooling, etc...) occuring on the dev list. * Released milestone 1 in December. A bit late, but more feature were added and stability and number of bugs have been good. * Working with the Yoko folks about transitioning to CXF (from ObjectWeb Celtix) * Started working with the Geronimo folks to integrate with them. * Created a eclipse plugin/bundle of our code for the Eclipse STP project for them to integrate our code. Code aspects: * Milestone 1 released, working on setting features for the next RC. (hopefully around March) * Started discussing some architectural changes, especially in regard to the tooling. === Felix === Felix is an implementation of the OSGi R4 service platform. Community * The community is working toward incubator gradution. * Continued organization of the wiki (and generated web site), creating the subproject documentation section with new documentation on for various subprojects, including a placeholder for the Felix Commons initiative. * Voted Karl Pauls as Release Manager. * Community voted on and released Felix 0.8.0-incubator. * A Felix-related talk was given at ApacheCon 2006 in Austin, Texas. * We have seen an apparent influx of new community members based on some new faces being active on the mailing list and even a new contributor (Chris Custine). * Emil Ivov announced the 1.0-alpha1 release of SIP Communicator, a Felix-based multi-protocol instant messenger and SIP software phone. Software * Felix 0.8.0-incubator approved by the Incubator PMC and is available for download. * Felix Commons initiative started in earnest with the goal of creating bundles out of popular open source libraries, headed by Enrique Rodriguez. John Conlon submitted several POM files for various libraries and Felix Meschberger and Tim Moloney have also expressed interest in doing so. * Several patches from Felix Meschberger improving the framework's ability to be used in embedded use cases, particularly issues surrounding framework shutdown and clean up. * Created a new Maven 2 plugin for creating OSGi bundles, which uses the BND tool from Peter Kriens. This plugin is quite a bit different than the existing plugin, but the goal is to try to merge the two if possible. * Major patch to iPOJO by Clement Escoffier. * Initial prototyping of require bundle functionality complete in Richard Hall's sandbox, work has begun to transition to trunk. * Patch submitted by Chris Custine to implement bundle manifest header localization. * Patch submitted by Kamen Petroff to allow additional imports to be specified for the old Maven plugin. * Rick Litton worked with the Eclipse community to get their extension point mechanism working on Felix, this effort will continue as bundle localization and require-bundle capabilities are added to Felix. Licensing and other isses * Committed latest OSGi Alliance source code, which is the official release licensed under the Apache license. * Committed OSGi Alliance Foundation source code (licensed under the Apache license), which provides stubs for javax.microedition.io, so that we can compile everything again.
[ANN] The Qpid M1 released
The Qpid M1 release has been placed at: http://people.apache.org/dist/incubator/qpid/M1-incubating/java/ Download pages will be updated shortly Regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] vote result for Qpid M1
Thank you for all those that helped, I will post a release ANN once the release has been posted. Regards Carl. Vote Summary 0 -1 or 0 votes 2+1 Mentors binding 2+ 1 Incubator binding 12 +1 PPMC 4+1 Others Incubator Votes Davanum Srinivas Brian McCallister Mentors --- Cliff Schmitt Paul Fremantle PPMC Alan Conway Kim van der Riet Martin Ritche Marnie McCormack Steve Vinoski Gordon Sim Robert Grieg Rajith Attapatta John O'Hara Bhupendra Bhardwaj Rafael Schloming Carl Trieloff Others -- Suresh Kodichath Frank Lynch Sam Joyce Tejeswar Das - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Qpid M1
I will leave the vote open it till Wednesday at which time I will provide a summary of the final vote. Qpid has the votes required for releasing, with vote running longer than 72 hours and thus would like to provide notice of closing the vote Wednesday if there are any additional votes. Thanks to all that have helped so far, regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Qpid M1
Brian McCallister wrote: Concern: Was there any resolution on the AMQP licensing terms (1) in relation to making releases? I think it is okay, but how it fits into the current draft guidelines (2) I am unsure. I think Cliff voted for this, so I suspect it is okay. Just want to make sure :-) Yes, the issue in B-2 was resolved, we took the item identified at project proposal time back to the Specification Working Group, to be voted on, corrected it and that correction has been reflected in the specification license included in the release. The link you reference includes the update: https://svn.apache.org/repos/asf/incubator/qpid/branches/M1/specs/license.amqp.txt Regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Qpid M1
The Qpid community voted on and almost approved to release qpid-java-1.0-incubator-M1, we are a vote short. I would thus like to request the Incubator PMC to review the release and if someone could help us get this remaining vote to be able to request to publish the release. You can preview the release at: http://people.apache.org/~rajith/qpid-release/M1/ which includes the links to the binary and sources releases. The svn branch used for the M1 release is located at: https://svn.apache.org/repos/asf/incubator/qpid/branches/M1/ The results of the vote held on the Qpid dev list where as follows Vote Summary 0 -1 or 0 votes 2 +1 Mentors 12 +1 PPMC 4 +1 Others Mentors --- Cliff Schmitt Paul Fremantle PPMC Alan Conway Kim van der Riet Martin Ritche Marnie McCormack Steve Vinoski Gordon Sim Robert Grieg Rajith Attapatta John O'Hara Bhupendra Bhardwaj Rafael Schloming Carl Trieloff Others -- Suresh Kodichath Frank Lynch Sam Joyce Tejeswar Das Regards Carl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Qpid M1
something went wrong on line wrap, re-send so that vote count can be understood. The Qpid community voted on and almost approved to release qpid-java-1.0-incubator-M1, we are a vote short. I would thus like to request the Incubator PMC to review the release and if someone could help us get this remaining vote to be able to request to publish the release. You can preview the release at: http://people.apache.org/~rajith/qpid-release/M1/ which includes the links to the binary and sources releases. The svn branch used for the M1 release is located at: https://svn.apache.org/repos/asf/incubator/qpid/branches/M1/ The results of the vote held on the Qpid dev list where as follows Vote Summary 0 -1 or 0 votes 2+1 Mentors 12 +1 PPMC 4+1 Others Mentors --- Cliff Schmitt Paul Fremantle PPMC Alan Conway Kim van der Riet Martin Ritche Marnie McCormack Steve Vinoski Gordon Sim Robert Grieg Rajith Attapatta John O'Hara Bhupendra Bhardwaj Rafael Schloming Carl Trieloff Others -- Suresh Kodichath Frank Lynch Sam Joyce Tejeswar Das Regards Carl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Including snapshot dependencies from other ASF projects
For development releases, it seems like it should be quite reasonable and maybe needed to use snapshots, however when doing a major release it would seem that you would take all possible effort not to use snapshots, and only use them if absolutely required. Carl. Paul Querna wrote: John O'Hara wrote: I don't think its the same as releasing another projects code. A good example is when SubVersion included APR as part of its code base. No one would have confused that as a release of APR, and it was patched and modded, and the APR team were kept in the loop. For the most part, in the more-recent past, Subversion shipped with the version of APR that HTTPD shipped with, which sometimes was a SVN snapshot, and sometimes as release. In the most-recent past, Subversion has only been shipping with real APR releases, unpatched. HTTPD now also only ships with real APR releases, unpatched. -Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JiniProposal - BraintreeProposal
Having been through this, may I suggest listing all the project terms/values/etc and write a script to randomly combines them -- (and yes we have a script that does this... :-) The months of normal naming practices did not turn up a non trademarked/place/etc name... Carl. Johnson, Eric wrote: It is also one in Massachusetts, USA -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Cooper Sent: Thursday, October 26, 2006 12:03 PM To: general@incubator.apache.org Subject: Re: JiniProposal - BraintreeProposal On 10/24/06, Noel J. Bergman [EMAIL PROTECTED] wrote: Jim Hurley wrote: The third preference (braintree) seems fairly clean, so we are going to go with this name for our project proposal. I am looking forward to seeing JINI move into the Incubator, but out of curiosity, did Braintree Software (www.braintree.com) not come up in your search? They appear to be defunct, although the domain still exists, and I was able to pull up the current domain registration via OpenSRS. Didn't we also agree not to use proper nouns and place names? Braintree is a town in Essex, UK. -- Martin Cooper --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Glasglow to Qpid
I have completed the rename on the wiki from Blaze to Glasgow to Qpid. The updated page (only the name and ASF resources to be setup have changed). The new page can be found at: http://wiki.apache.org/incubator/QpidProposal Project setup can now be done with Qpid for the name and qpid lowercase to be used for the resources. Details are in the proposal. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Glasgow - new name proposal
If there are no more last comments on the name by COB, I will update the proposal with Qpid and we will use this for ASF resource setup. Regards Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Glasgow - new name proposal
I think we have a new name, we need to come to agreement on how to do the CaPs. a.) Qpid b.) QPid c.) QPID I like a, then c. Carl. sophitia que wrote: I am +1 on the name. On 8/10/06, Craig L Russell [EMAIL PROTECTED] wrote: On Aug 10, 2006, at 11:49 AM, Archit Shah wrote: +1 for Qpid or QPid or QPID. +1 I'd prefer if the acronym expansion is left unspecified as well. Craig To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
