Re: [VOTE] Graduate Apache Stratos as a TLP
+1. Deepal +1 -Jake On Thu, May 1, 2014 at 11:03 PM, Suresh Marru sma...@apache.org wrote: Please VOTE to indicate if Apache Stratos is ready to graduate as a Top Level Project. The board resolution is included below. [ ] +1 Graduate Apache Stratos as a TLP [ ] +0 Don't care. [ ] -1 Don't graduate Apache Stratos as a TLP because… Cheers, Suresh === Board Resolution == Establish the Apache Stratos Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to providing an implementation of a Platform-as-a-Service Framework. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Stratos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Stratos Project be and hereby is responsible for the creation and maintenance of software related to providing an implementation of a Platform-as-a-Service Framework; and be it further RESOLVED, that the office of Vice President, Stratos 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 Stratos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Stratos 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 Stratos Project: Ant Elder (antel...@apache.org) Paul Fremantle (p...@apache.org) Jonathan Marsh (jonathanma...@apache.org) Afkham Azeez (az...@apache.org) Peter Linnell (plinn...@apache.org) Lakmal Warusawithana (lak...@apache.org) Damitha Kumarage (dami...@apache.org) Samisa Abeysinghe (sam...@apache.org) Nirmal Fernando (nirmal070...@apache.org) Sajith Kariyawasam (saj...@apache.org) Lahiru Sandaruwan (lahi...@apache.org) Isuru Haththotuwa (isu...@apache.org) Madhura Mendis (madh...@apache.org) Mariangela Hills (mariang...@apache.org) Suresh Marru (sma...@apache.org) Chip Childers (chipchild...@apache.org) Joe Brockmeier (j...@apache.org) Noah Slater (nsla...@apache.org) Nandana Mihindukulasooriya (nand...@apache.org) Isuru Perera (is...@apache.org) Reka Thirunavakurussu (r...@apache.org) Deepal Jayasinghe (dee...@apache.org) Debo Dutta (dedu...@apache.org) Udara Liyanage (ud...@apache.org) Manula Chathurika Thantriwatte (man...@apache.org) Imesh Gunaratne (im...@apache.org) Pradeep Fernando (pradee...@apache.org) Chris Snow (cs...@apache.org) Melan Nimesh (me...@apache.org) Jason Daly (jasondaly...@apache.org) Chanaka Jayasena (chan...@apache.org) Jeffrey Nguyen (jeffr...@apache.org) Anh Tu Nguyen (t...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lakmal Warusawithana be appointed to the office of Vice President, Stratos, 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 Stratos 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 Stratos Project; and be it further RESOLVED, that the Apache Stratos Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Stratos podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Stratos podling encumbered upon the Apache Incubator Project 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 Apache Stratos 3.0.0 Incubating RC4
+1. Deepal +1 (binding) -- Azeez On Fri, Oct 25, 2013 at 10:53 PM, Lahiru Sandaruwan lahi...@wso2.comwrote: Hi all, This is the forth release candidate for Apache Stratos 3.0.0-incubating, the very first Stratos release at Apache. This is the IPMC vote. The PPMC vote [1] passed, with 9 binding +1s, including 2 from mentors/IPMC (Ant Elder and Chip Childers) and no -1s. This release fixes the following issues(Same as RC1): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314521version=12324964 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314521version=12324964 *** Please download, test and vote. The vote runs for 72 hours, until Monday, 10.30 am PST, 11.00 am IST. Note that we are voting upon the source (tag), binaries are provided for convenience. This wiki page[1] explains Downloading the Release Candidate, Verifying the Candidate, Building Apache Stratos from source, and Carrying out a Smoke Test. We have explained configuring guides[2] and user guides[3] at wiki. Further, [4], [5], and [6] blogs also explain the testing release candidate packs using scripts in EC2 and Openstack IaaSes. The reason for not providing sample cartridges is that we test Cartridges based on Ubuntu cloud images and therefore we cannot distribute those with the release. Hence the blog posts [5] and [6]. Thanks. Binary files and source files: https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-rc4/ https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-rc1/ https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-rc1/ Maven staging repos: https://repository.apache.org/content/repositories/orgapachestratos-116/ https://repository.apache.org/content/repositories/orgapachestratos-174/ https://repository.apache.org/content/repositories/orgapachestratos-097/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tag;h=ab166c282897d9db4d3f22863e67fdc8ddcccd61 Tree view of the tag, https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tree;h=661b5e19e00497431f552468535052751f115303;hb=c042d6df7becda9f38100aeb7c130b2a8870cb46 https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tag;h=baff4979db295625e6951534712bb3b6bbc65273 Stratos KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-rc1/KEYS [1] https://cwiki.apache.org/confluence/display/STRATOS/Testing+Procedure [2] https://cwiki.apache.org/confluence/display/STRATOS/Getting+Started [3] https://cwiki.apache.org/confluence/display/STRATOS/User+Guide [4] http://imesh.gunaratne.org/a/1/blog/getting-started-with-apache-stratos-incubating-initial-release/ [5] http://dineshmethsiri.blogspot.com/2013/09/create-ec2-apache-stratos-ami.html [6] http://melannj.blogspot.com/2013/09/quick-start-apache-stratos-from-ec2.html Thanks. https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-rc1/KEYS [ ] +1 [ ] 0 [ ] -1 (explain why) -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
Apache is community over code, but here is more like code over community. As a community we should be able to tolerate the conflicts of interest. Once the project is incubated in Apache, the project belongs to Apache and direction and future of the project should be decided by the community, not just the people who bring the project. I do not see that here. If this would have been a vote, I might -1. Deepal Are you guys wearing Apache hats or WS02 hats? If you're wearing Apache hats, then I'd expect a bit less fealty to your CEO's request and a little more OK, I see your point, but I'm really excited about the project, here's what I'd like to do on the project, do you mind adding me as an initial committer?. Granted that email doesn't convey tone-of-voice very well, but the messages from WSO2 employees sound kind of snarky. Now, on the general question of piling-on I have to agree with Roy. The incubator always encourages people to build a community, and then bring that community to Apache. If an incubating project's existing community is hugely diluted by Apache folks at the incubator proposal stage, then it becomes a code dump, which we try to discourage. If we care about community over code, then surely we have to show some respect for the community that comes to Apache. Common courtesy suggest that you offer your help to that community, not impose your help on it. Cheers, Greg. On 2013-09-25, at 12:52 AM, Nirmal Fernando nirmal070...@gmail.com wrote: hmm.. it appears to me that though you pushed the project into ASF, your intentions were not pure and you don't want any competitor of Apigee to be joined to the project (by going on your words, it is quite natural to think so.) even if they showed their genuine interest on helping the project out, with their know-how on related areas. As Sanjiva requested, I'm gonna hereby withdraw my humble request to be added as a committer. On Wed, Sep 25, 2013 at 9:21 AM, Niranjan Karunanandham niranjan.k...@gmail.com wrote: I was actually looking forward to contributing for this project where ever possible but I think people have misunderstood our intentions. As requested by my CEO, I would like to withdraw my committer request. On Wed, Sep 25, 2013 at 7:36 AM, Dulitha Wijewantha dulit...@gmail.com wrote: +1 for the Dave Fisher's example. I believe most of the people have misunderstood our intentions. We were offering to help the project to grow and graduate faster. I am withdrawing my committer request as our CEO asked too. But honestly speaking - if you guys are *scared* of the *community* and what the *community* is - I don't believe you shouldn't mention the below words in the proposal - *Although we are aware of the strength of the Apache brand, we are primarily * *interested in the transforming power of the Apache Way to help guide* *Usergrid towards a more diversified and meritocratic community* In my humble opinion - the above line should not be a part of the proposal since the Apache way has always been to gather a community around the proposal who have shown interest towards the idea. Cheers On Wed, Sep 25, 2013 at 5:50 AM, Dave Fisher dave2w...@comcast.net wrote: On Sep 24, 2013, at 3:19 PM, Bertrand Delacretaz wrote: On Tue, Sep 24, 2013 at 10:23 PM, Alex Karasulu akaras...@apache.org wrote: ...So fill the bus with anybody who volunteers? That does not sound meritocratic It's been like that for a while in the Incubator, people who sign up as initial committers for a podling usually don't have to demonstrate any merit. When the time comes to graduate the podling, it's perfectly fine to ask it to prune its list of committers and PMC members in order to keep only people who have demonstrated their committment during incubation. When OpenOffice.org was brought to the Incubator there was open enrollment. There were over 70 Initial Committers. I had no experience with OpenOffice. I did have an understanding of the ASF. I could help and I did. It was tough to have such a large list many were OpenOffice.org people who never really adapted to the ASF. We had all these people on the PPMC. When graduation time came we managed to reduce the PMC to 25. We left the Initial Committers connected. It hasn't really been a problem. My point is that without the Initial Committer free for all I think that AOO would not be as successful as now. Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- *Dulitha R. Wijewantha** Software Engineer* Tel: 94112793140 | Mobile: 94112793140 dulit...@gmail.com | http://dulithawijewantha.com -- *Niranjan Karunanandham* Senior Software Engineer M: +94 777 749 661 http:/// -- Best Regards, Nirmal C.S.Nirmal J. Fernando Senior
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
A true open source contributor does not have a CEO, and takes the personal judgements not what CEO or someone asked you to do. Deepal I was actually looking forward to contributing for this project where ever possible but I think people have misunderstood our intentions. As requested by my CEO, I would like to withdraw my committer request. On Wed, Sep 25, 2013 at 7:36 AM, Dulitha Wijewantha dulit...@gmail.comwrote: +1 for the Dave Fisher's example. I believe most of the people have misunderstood our intentions. We were offering to help the project to grow and graduate faster. I am withdrawing my committer request as our CEO asked too. But honestly speaking - if you guys are *scared* of the *community* and what the *community* is - I don't believe you shouldn't mention the below words in the proposal - *Although we are aware of the strength of the Apache brand, we are primarily * *interested in the transforming power of the Apache Way to help guide* *Usergrid towards a more diversified and meritocratic community* In my humble opinion - the above line should not be a part of the proposal since the Apache way has always been to gather a community around the proposal who have shown interest towards the idea. Cheers On Wed, Sep 25, 2013 at 5:50 AM, Dave Fisher dave2w...@comcast.net wrote: On Sep 24, 2013, at 3:19 PM, Bertrand Delacretaz wrote: On Tue, Sep 24, 2013 at 10:23 PM, Alex Karasulu akaras...@apache.org wrote: ...So fill the bus with anybody who volunteers? That does not sound meritocratic It's been like that for a while in the Incubator, people who sign up as initial committers for a podling usually don't have to demonstrate any merit. When the time comes to graduate the podling, it's perfectly fine to ask it to prune its list of committers and PMC members in order to keep only people who have demonstrated their committment during incubation. When OpenOffice.org was brought to the Incubator there was open enrollment. There were over 70 Initial Committers. I had no experience with OpenOffice. I did have an understanding of the ASF. I could help and I did. It was tough to have such a large list many were OpenOffice.org people who never really adapted to the ASF. We had all these people on the PPMC. When graduation time came we managed to reduce the PMC to 25. We left the Initial Committers connected. It hasn't really been a problem. My point is that without the Initial Committer free for all I think that AOO would not be as successful as now. Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- *Dulitha R. Wijewantha** Software Engineer* Tel: 94112793140 | Mobile: 94112793140 dulit...@gmail.com | http://dulithawijewantha.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
The Apache way is *community over code*, as a healthy community we should encourage community growth. IMO I do not consider adding a new member to the initial committer list as a big change to the proposal. In fact, now I believe if we had a separate VOTE for him, we will not have this much traffic in this thread. Deepal It seems clear that the majority of IPMC members believe this change on a vote in progress is not acceptable. I note that this change is different to the trademark promise made earlier since that one had been agreed in the discuss thread. That change was merely bringing the proposal into line with the discussion. This change was discussed after the vote had been called, which is quite different. I can also understand the concern that there is a potential for a slippery slope here (although I will note this is not the first time proposals have been tweaked during a vote - which should just be a formality since consensus is gauged through discussion). I am disappointed that following (what appears to be) unwritten rules to the letter rather than in the spirit of community development is more important to the IPMC members who have spoken, but I have to accept the majority opinion. I consider my wrists well and truly slapped and appreciate that nobody has gone so far as to veto the vote. I trust someone who believes this is a fixed rule rather than a social-norm by which we are guided will now go and document it appropriately in [2] (see ISSUE 09 [1]). (I keep wanting to delete that last sentence as it feels like a parting shot - it's not meant that way, it is an important point. I don't agree with this new rule, but I do appear to be in the minority. In an attempt to prove it's not a parting shot I've make the change myself in r866129: Index: content/incubation/Process_Description.html === --- content/incubation/Process_Description.html (.../production/incubator) (revision 866128) +++ content/incubation/Process_Description.html (.../staging/incubator/trunk) (revision 866128) @@ -231,6 +231,8 @@ getting feedback about what is actually happening. The Sponsor will typically take about 7-10 days before announcing a vote result. /p +pOnce the vote has been called the proposal should be considered fixed. + No further changes are accepted./p pIf that vote is affirmative, the Sponsor (unless the Sponsor is already the Incubator PMC) will propose to the ) Ross [1] http://wiki.apache.org/incubator/IncubatorIssues2013#Issue_09_-_People_do_not_follow_through_to_improve_Incubator_documentation [2] http://incubator.apache.org/incubation/Process_Description.html On 18 June 2013 17:12, Daniel Shahaf danie...@apache.org wrote: On Tue, Jun 18, 2013 at 01:34:39PM +0100, Ross Gardler wrote: However, in this specific case the social norm *should* be to allow the change to proceed - that's the most efficient process. Modifying a vote that has started is a slippery slope. (The same is true for reusing version numbers: ANY change to something that has been tagged must get a new version number - no matter how small the change may be.) One solution is to restart the vote. Another is to run a parallel vote for the delta/amendment. Concretely, can't you just start a thread on private@ saying The would-be-PPMC has consensus on inviting X as a committer? This would allow you to invite X to be a committer shortly after the original vote ends. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stratos proposal as an incubating project
+1. Deepal I would like to invite the IPMC vote to accept the Stratos proposal [1]. I want to clarify that this vote is for the Stratos project to enter the incubator as a standard podling under the existing incubation policy. The acceptance or otherwise of the probationary TLP idea is a separate issue that will be explored during the first month of incubation, potentially resulting in a further IPMC vote. This vote is *only* for accepting the Stratos project as a podling. [ ] +1 Accept the Stratos project as an incubating project [ ] +0 [ ] -1 Do not accept the Stratos project as an incubating project because... (provide reason) It's late on Friday evening here in the UK. I'll let this vote run well into next week to allow for the weekend. Thank you for your votes. Ross - 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: [DISCUSS] Accept Stratos as an Apache Incubation Project
Great to see WSO2 Stratos coming to Apache, and I would love to join/help this project. Deepal On Tue, Jun 11, 2013 at 5:10 AM, Ross Gardler rgard...@opendirective.comwrote: It's with great pleasure that I invite the IPMC to review a new proposal [1] for the Apache Incubator. Please let us know if you have any questions or comments - as you will see there are plenty of people on the initial commit list ready and willing to answer your questions. I copy the full text of the proposal for your convenience: = Stratos - A PaaS Framework = == Abstract == Stratos will be a polyglot [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]] framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform-wide insight including monitoring and billing. == Proposal == The Stratos PaaS framework will encompass four layers: 1. An [[ http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic layer that can interface with a wide variety of IaaS systems to provide elastic resources, and for multiple IaaS infrastructures to be automated at one time (hybrid clouds.) 2. A PaaS Controller with a cloud controller that automates and monitors IaaS runtime interactions, distributes artifacts to the underlying runtimes, deploys workloads, directs runtime traffic to the right runtimes using a tenant-aware elastic load balancer, and provides a portal for monitoring and provisioning of tenants on the system. 3. Foundational Services including security, logging, messaging, registry, storage (relational, file, and noSQL), task management, and billing. Foundational services will be loosely-coupled to allow swapping in alternate foundational services. 4. A Cartridge Architecture allowing frameworks, servers, and other runtimes to participate in the advantages of the system. The Cartridge Architecture must support multi-tenant workloads, and provide for various levels of tenant isolation and policy-based control over provisioning. Together these layers offer a foundational layer upon which applications and middleware frameworks can be deployed to speed time-to-market and simplify the development of scalable applications, as well as provide a high level of resource sharing and centralized management that can deliver lowest resource, infrastructure, and management costs. == Background == The Stratos Project has been under development[a] at http://wso2.org under the Apache 2.0 license and the Apache Way governance model since 2010. It initially was focussed on providing PaaS benefits to the users of WSO2 Carbon middleware platform. In version 2.0, to be released in summer 2013, extensive work has been done to clearly separate out the PaaS framework from the products (cartridges) that run on top of it. Stratos now has the ability to run arbitrary workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more. == Rationale == PaaS is in demand by enterprises and organizations of all sizes. The drive towards instance provisioning, high resource utilization and thus low cost, combined with a wide platform of general-purpose services to build on, PaaS has the opportunity to accelerate the development cycle and innovation index of a new class of applications, services, and business models. PaaS offerings are widely diversified but largely associated with powerful corporate interests. With the commencement of the Stratos project at Apache, vendors and users will have a neutral community free from corporate governance restrictions, with which to collaborate and accelerate the development of a platform that provides wide benefits across the industry. As a flexible framework, we expect a wide variety of platforms to leverage the technology to fill specific niches and needs. == Current Status == Stratos has been in development since 2010 at WSO2, under the Apache License and under the Apache Way. Contribution to Apache, from which many of the core components are sourced, should be very straightforward. == Meritocracy == The contributors have a longstanding commitment and practice of meritocracy in their personal and professional capacities. Many of the committers on the existing project are already Apache Committers. == Community == The committers recognize the need to support more significant contributions from a broad swath of the industry and community. Apache is the obvious choice for a project that already embodies Apache values and is driven by developers who are committers on many other Apache projects. Stratos has appeal, and should attract community members, from among a number of constituencies: * Private PaaS deployment within an enterprise to benefit enterprise application deployment. * PaaS providers wishing to leverage a PaaS toolkit to build a PaaS
Re: [VOTE] Apache Spark for the Incubator
+1, Deepal +1 Andrew On 06/07/2013 10:34 PM, Mattmann, Chris A (398J) wrote: Hi Folks, OK discussion has died down, time to VOTE to accept Spark into the Apache Incubator. I'll let the VOTE run for at least a week. So far I've heard +1s from the following folks, so no need for them to VOTE again unless they want to change their VOTE: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* * -indicates IPMC [ ] +1 Accept Spark into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept Spark into the Apache Incubator because.. Proposal text is below. === Abstract === Spark is an open source system for large-scale data analysis on clusters. === Proposal === Spark is an open source system for fast and flexible large-scale data analysis. Spark provides a general purpose runtime that supports low-latency execution in several forms. These include interactive exploration of very large datasets, near real-time stream processing, and ad-hoc SQL analytics (through higher layer extensions). Spark interfaces with HDFS, HBase, Cassandra and several other storage storage layers, and exposes APIs in Scala, Java and Python. Background Spark started as U.C. Berkeley research project, designed to efficiently run machine learning algorithms on large datasets. Over time, it has evolved into a general computing engine as outlined above. Spark¹s developer community has also grown to include additional institutions, such as universities, research labs, and corporations. Funding has been provided by various institutions including the U.S. National Science Foundation, DARPA, and a number of industry sponsors. See: https://amplab.cs.berkeley.edu/sponsors/ for full details. === Rationale === As the number of contributors to Spark has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Spark is a natural fit for the Apache foundation: Spark already interoperates with several existing Apache projects (HDFS, HBase, Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar with the Apache process and and subscribes to the Apache mission - the team includes multiple Apache committers already. Finally, joining Apache will help coordinate the development effort of the growing number of organizations which contribute to Spark. == Initial Goals == The initial goals will most likely be to move the existing codebase to Apache and integrate with the Apache development process. Furthermore, we plan for incremental development, and releases along with the Apache guidelines. === Current Status === == Meritocracy == The Spark project already operates on meritocratic principles. Today, Spark has several developers and has accepted multiple major patches from outside of U.C. Berkeley. While this process has remained mostly informal (we do not have an official committer list), an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Spark project would include several of these participants as committers from the onset. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. === Community === Acceptance into the Apache foundation would bolster the already strong user and developer community around Spark. That community includes dozens of contributors from several institutions, a meetup group with several hundred members, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many exist at UC Berkeley, there is a representative cross sampling of other organizations including Quantifind, Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. === Alignment === Our proposed effort aligns with several ongoing BIGDATA and U.S. National priority funding interests including the NSF and its Expeditions program, and the DARPA XDATA project. Our industry partners and collaborators are well aligned with our code base. There are also a number of related Apache projects and dependencies, that will be mentioned in the Relationships with Other Apache products section. == Known Risks == === Orphaned Products === Given the current level of investment in Spark - the risk of the project being abandoned is minimal. There are several constituents who are highly incentivized to continue development. The U.C. Berkeley AMPLab relies on Spark as a platform for a large number of long-term research projects. Several companies have build verticalized products which are tightly dependent on Spark. Other companies have devoted significant internal infrastructure investment in Spark. === Inexperience with Open Source === Spark has
Re: [VOTE] CloudStack for Apache Incubator
+1, Deepal +1 (non binding) On Tue, Apr 10, 2012 at 10:51 AM, Davanum Srinivas dava...@gmail.com wrote: +1 binding -- dims On Apr 10, 2012, at 9:52 AM, Daniel Kulp dk...@apache.org wrote: +1 binding Dan On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote: Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. The proposal is available at [1] and I have also included it below. Please vote with: +1: accept CloudStack into Incubator +0: don't care -1: do not accept CloudStack into Incubator (please explain the objection) The vote is open for at least 72 hours from now (until at least 19:00 US-PST on April 12, 2012). Thanks for the consideration. -kevin [1] http://wiki.apache.org/incubator/CloudStackProposal Abstract CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration platform. Proposal CloudStack provides control plane software that can be used to create an IaaS cloud. It includes an HTTP-based API for user and administrator functions and a web UI for user and administrator access. Administrators can provision physical infrastructure (e.g., servers, network elements, storage) into an instance of CloudStack, while end users can use the CloudStack self-service API and UI for the provisioning and management of virtual machines, virtual disks, and virtual networks. Citrix Systems, Inc. submits this proposal to donate the CloudStack source code, documentation, websites, and trademarks to the Apache Software Foundation (ASF). Background Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual machines to end users. CloudStack additionally provides baremetal OS installation to end users via a self-service interface. The management of physical resources to provide the larger goal of cloud service delivery is known as orchestration. IaaS clouds are usually described as elastic -- an elastic service is one that allows its user to rapidly scale up or down their need for resources. A number of open source projects and companies have been created to implement IaaS clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General Public License version 3 (GPL v3) in 2010. Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache License v2 in April, 2012. Rationale IaaS clouds provide the ability to implement datacenter operations in a programmable fashion. This functionality is tremendously powerful and benefits the community by providing: - More efficient use of datacenter personnel - More efficient use of datacenter hardware - Better responsiveness to user requests - Better uptime/availability through automation While there are several open source IaaS efforts today, none are governed by an independent foundation such as ASF. Vendor influence and/or proprietary implementations may limit the community's ability to choose the hardware and software for use in the datacenter. The community at large will benefit from the ability to enhance the orchestration layer as needed for particular hardware or software support, and to implement algorithms and features that may reduce cost or increase user satisfaction for specific use cases. In this respect the independent nature of the ASF is key to the long term health and success of the project. Initial Goals The CloudStack project has two initial goals after the proposal is accepted and the incubation has begun. The Cloudstack Project's first goal is to ensure that the CloudStack source includes only third party code that is licensed under the Apache License or open source licenses that are approved by the ASF for use in ASF projects. The CloudStack Project has begun the process of removing third party code that is not licensed under an ASF approved license. This is an ongoing process that will continue into the incubation period. Third party code contributed to CloudStack under the CloudStack contribution agreement was assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack project has begun the process of amending the previous CloudStack contribution agreements to obtain consent from existing contributors to change the CloudStack project's license. In the event that an existing contributor does not consent to this change, the project is prepared to remove that contributor's code. Additionally, there are binary dependencies on redistributed libraries that are not provided with an ASF-approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal. Although CloudStack is open source, many design documents
Re: NOMINATIONS for Incubator PMC Chair
If he has not resigned, why do we have this vote (or why started this vote) ? forcing him to resign ? Deepal I'd like to nominate Noel to continue as chair. Noel hasn't resigned, and we don't have a consensus on rotation. So I think any vote we hold to recommend a chair to the board should include the option of his sticking in place unless he chooses to remove himself from the running. - 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: NOMINATIONS for Incubator PMC Chair
On 1/29/2012 3:09 PM, Benson Margulies wrote: +1 But shouldn't we agree on a rotationi/reelection before we do the nominations? Christian, I hate to repeat myself, but could I direct your attention to my recent message? If you think that a rotation policy should come first, start a thread proposing a rotation policy, and we can all leave this one sit until that one achieves a consensus in some +1. Deepal direction or another. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Openmeetings to Apache Incubator
+1, definitely. Deepal +1 On 7 November 2011 22:53, Andrus Adamchik and...@objectstyle.org wrote: Opemeetings proposal has been discussed a few times here before. The group of developers behind it worked hard (and succeeded) to address all potential obstacles to the Incubator acceptance and to the following incubation. They even went an extra mile and collected all ICLAs in adbvance. So now I am starting the vote to accept Openmeetings to Apache Incubator. The proposal is also available at: http://wiki.apache.org/incubator/OpenmeetingsProposal Please cast your votes: [ ] +1 Accept Openmeetings for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Andrus --- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a --- == OpenMeetings Project Proposal == == Abstract == Openmeetings is a web conferencing solution. == Proposal == Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming. == Background == Openmeetings was developed since 2007 by Sebastian Wagner and willing developers. The project ships a release approximately once per quarter. It was developed using LGPL license, and developers are currently thinking of re-licensing it under Apache License 2.0. The project started as module by Sebastian Wagner for an ELearning platform (Dokeos) and was then split into a separated project. That is the reason why there is a strong relation to educational institutions that are using OpenMeetings and there are integrations for platforms like Moodle, ATutor, Sakai, STudIP or ILias available (http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation to educational institutions also subsequently lead to some projects funded by the EU where OpenMeetings was involved, for example by the Swedish/Finnish Centre of Open-Source !OpenKarken (Case-Study about the EU project at OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-collaborate-using-oss ) The integration and internationalization of the project was a primary focus right from the start of the project. Since Version 0.5 there is a Language-Editor (http://code.google.com/p/openmeetings/wiki/LanguageEditor) to edit labels, export and import them as XML and you can use those XML files for future installations (or contribute it to the community). There are currently around 30 languages available. Since version 0.5.1 there is also a SOAP API to integrate !OpenMeetings. We constantly improve this SOAP/REST API (http://code.google.com/p/openmeetings/wiki/SoapMethods) with new functionality with a strong focus on security and usability. The auth-mechnism is quite similar to OAuth, you create some token and then assign rights to the token. (Documentation for Single Sign On: http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow) The project name !OpenMeetings and logos are inspired by Ludovic Gasc who has been the project manager at Dokeos at the time Sebastian split !OpenMeetings as separated project. Red5 Server provides an Edge-Orion-Clustering (http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringConfiguration). We hope to extend this clustering solution with support for rtmpt and rtmps and integrate that into our application as native clustering option. == Rationale == Last year most major vendors started commercial web conferencing solutions. This is an important part of software ecosystem, and there is an urge to consolidate open source development efforts in this direction. According to several studies demand for synchronous Communication, in opposite to asynchronous Communication like wiki's or email, will raise the upcoming years. For example Gartner promises that 2011 the market will grow 20% according to their Magic Quadrant report 2010 ( http://www.gartner.com/DisplayDocument?doc_cd=205941 ). Openmeetings is a unique solution in terms of patent purity and potentially can grow into solution built on top of the fully open source stack. That is why it is a good candidate for consolidating web conferencing community efforts. == Initial Goals == Each of project committers has their own set of goals, but we all share the following. * Move to Apache. * Become popular. To become popular we plan to do the following. * Improve ecosystem around the project. * Improve release process. * Improve project testing and stability. * Apply modular architecture/SOA for better integration with other projects. == Current Status == We have agreed on applying for the Apache Foundation and preparing our proposal for the vote. Technical status of the project is: Current stable tree is 1.8.x, Trunk is 1.9. ===
Re: [VOTE] Accept Airavata into the Incubator
+1. Deepal +1 (binding), with the caveat that I personally think it might be easier to split WS-Messenger off to the Axis PMC sooner rather than later if everyone feels like it will end up there anyway. As a side note - the W3C is looking for implementations of the WS-RA specs, which include Eventing... Airavata might be interested in participating in that. [1] --Glen [1] http://www.w3.org/News/Public/pnews-20110502 On 5/2/11 5:32 PM, Ross Gardler wrote: I would like to call a vote to accept Airavata for entry into the Apache Incubator. The proposal thread can be found at [1] and the proposal text is at [2] [ ] +1 Accept Airavata into the incubator [ ] -1 Do NOT accept Airavata into the incubator because... Thanks, Ross [1] http://markmail.org/message/rhdiuwcexalfndim [2] http://wiki.apache.org/incubator/AiravataProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Airavata for the incubator
+1 for the proposal. Deepal On Sat, Apr 23, 2011 at 5:53 PM, Ross Gardler rgard...@apache.org wrote: I would like to propose Airavata for entry into the Apache Incubator. The full proposal can be found at [1] and is copied at the end of this mail. For those in a hurry here's a quick summary: Airavata is a software toolkit currently used to build science gateways but that has a much wider potential use. It provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. Users can use Airavata back end services and build gadgets to deploy in open social containers such as Apache Rave and modify them to suite their needs. Airavata builds on general concepts of service oriented computing, distributed messaging, and workflow composition and orchestration. Airavata will provide web interfaces and scalable Service Oriented Architecture based backend services to build or enhance Science Gateway (see https://www.teragrid.org/web/science-gateways/) and similar environments. Airavata will specifically focus on: 1. sophisticated server-side tools for registering and managing large scale applications on computational resources. 2. graphical user interfaces to construct, execute, control, manage and reuse of scientific workflows. 3. interfacing and interoperability with with various external (third party) data and provenance management tools The project team consists of a number of existing Apache Committers and the code comes from the same stable as some of the code donated to Apache Rave (Incubating). We welcome your questions, suggestions, observations and support. Ross [1] http://wiki.apache.org/incubator/AiravataProposal FULL PROPOSAL TEXT == = Airavata Proposal for Apache Incubator = == Abstract == Airavata is a software toolkit currently used to build science gateways but that has a much wider potential use. It provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. Users can use Airavata back end services and build gadgets to deploy in open social containers such as Apache Rave and modify them to suite their needs. Airavata builds on general concepts of service oriented computing, distributed messaging, and workflow composition and orchestration. == Proposal == Airavata will provide web interfaces and scalable Service Oriented Architecture based backend services to build or enhance Science Gateway (see https://www.teragrid.org/web/science-gateways/) and similar environments. Airavata will specifically focus on: 1. sophisticated server-side tools for registering and managing large scale applications on computational resources. 2. graphical user interfaces to construct, execute, control, manage and reuse of scientific workflows. 3. interfacing and interoperability with with various external (third party) data and provenance management tools. == Background == Working in close quarters with Apache Axis2 committers and inspired by the true open source community driven software development of ASF, Suresh Marru and Marlon Pierce have been pioneering the idea of a Science Gateways software-based Apache project since late 2008. Many Apache members have fostered these ideas and guided them to arrive at this proposal. Currently the software is a actively used in various science gateways. But the tools are general purpose and build upon widely used Apache tools like Axis2, ODE engine. The core team is motivated to expand the community and build a community welcoming both synergistic software components and also new usage scenarios. It is perhaps worth noting that one of the three seed projects that make up the Apache Rave (Incubating) project is also the product of this same team and is derived from the same Science Gateways community. == Rationale == The nature of computational problems has evolved from simple desktop calculations to complex, multidisciplinary activities that require the monitoring and analysis of remote data streams, database and web search and large ensembles of simulations. In the academic domain Science Gateways have emerged to address these needs and have built software platforms that provide a community of users with the ability to easily solve computational problems within a specific domain. The tools developed to support these gateways are potentially of value to any organisation needing to perform complex computations. Gateways provide a convenient interface to the underlying infrastrucure without the need for a deep understanding of the intricacies that infrastructure. We summarize the rationale for choosing The Apache Software Foundation (ASF) below. This is what we hope to gain from participating in the
Re: [VOTE] Approve the M2 release of Apache Stonehenge
+1 Deepal On Fri, Jul 9, 2010 at 12:25 AM, Paul Fremantle pzf...@gmail.com wrote: +1 Paul On Tue, Jul 6, 2010 at 2:58 PM, Jim Jagielski j...@apache.org wrote: +1 On Jul 5, 2010, at 1:15 PM, Ben Dewey wrote: Hi, The Apache Stonehenge community has voted for the M2 release of Apache Stonehenge. We are now asking the approval from the Incubator PMC to publish the release. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practice and interoperability. I have uploaded the Apache Stonehenge M2 release artifacts here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The CHANGELOG is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ChangeLog The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take4/ The release vote on the stonehenge-dev mailing list resulted in 8 +1 votes and no 0 or -1 votes. +1 votes are from *Ben Dewey *Kent Brown *Pablo Cibraro *Selvaratnam Uthaiyashankar *Chintana Wilamuna *Kamaljit Bath *Nick Hauenstein *Scott Golightly Vote Mail Thread is here: http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg02559.html More information about the project can be found here: [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html [Project Page] http://incubator.apache.org/stonehenge/ Please vote to approve this release. [] +1 Publish [] 0 no opinion [] -1 Don't publish (and reasons why) Regards, -Ben Dewey - 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 -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://blogs.deepal.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Deltacloud Project
+1 Deepal +1 ...ant On Thu, May 13, 2010 at 1:45 AM, David Lutterkort lut...@redhat.com wrote: Hi all, after the discussion so far [1], I'd like to put Detlacloud for a vote for acceptance into the Apache Incubator according to the proposal[2] I _think_ I've added everybody who expressed interest in being a mentor or initial committer to the proposal - if I have forgotten anybody, please holler. Please reply to this mail with your vote. David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c1273174879.7253.99.ca...@avon.watzmann.net%3e [2] http://wiki.apache.org/incubator/DeltacloudProposal - 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 -- If we knew what it was we were doing, it would not be called research, would it? - Albert Einstein http://blogs.deepal.org http://deepal.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Project look very interesting to me, so I would like to contribute too. Deepal Carl, if you need additional mentors, count me in. thanks, dims On Fri, May 7, 2010 at 9:18 AM, Carl Trieloff cctriel...@redhat.com wrote: On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- If we knew what it was we were doing, it would not be called research, would it? - Albert Einstein http://blogs.deepal.org http://deepal.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Two other issues to discuss for Subversion
How about the website ? (I can not find any information about the project, mentors, committers etc.. ) http://incubator.apache.org/projects/subversion.html -Deepal There are two other issues to discuss for the Subversion podling: * moving the mailing lists directly to @subversion.apache.org * placing the source code at /subversion/ rather than /incubator/subversion/ We are hoping to minimize overall disruption to the community with a move to incubator space, then a move to apache space. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thank you! http://blogs.deepal.org http://deepal.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Approve Ben Dewey as a committer for Stonehenge incubator project
+1. Thanks, Deepal On Thu, Jun 18, 2009 at 2:16 PM, Kamaljit Bathkamaljit.b...@microsoft.com wrote: Hi, The Apache Stonehenge community has voted to approve Ben Dewey as a committer for the Apache Stonehenge Incubator project. We are now asking the approval from the Incubator PMC for the same. Results of voting in the Stonehenge community: 9 (+1 non-binding), 1 (PMC Binding) , 1 (IPMC Binding) votes from the following folks: Kamaljit Bath Michael Champion Drew Baird Kent Brown Avantika Agarwal Scott Golightly Abu Obeida Bakhach Selvaratnam Uthaiyashankar Chintana Wilamuna Daniel Kulp (PMC Binding) Paul Fremantle (IPMC Binding) Ben has so far reported 30 JIRA issues, submitted many patches and been very active on the stonehenge dev mailing listhttp://www.mail-archive.com/stonehenge-...@incubator.apache.org/http:/www.mail-archive.com/stonehenge-...@incubator.apache.org/. He has also proposed many improvements and new additions to the Stock Trader application. Here are some of the JIRA issues with patches submitted by Ben: https://issues.apache.org/jira/browse/STONEHENGE-46 https://issues.apache.org/jira/browse/STONEHENGE-39 https://issues.apache.org/jira/browse/STONEHENGE-34 https://issues.apache.org/jira/browse/STONEHENGE-33 https://issues.apache.org/jira/browse/STONEHENGE-28 https://issues.apache.org/jira/browse/STONEHENGE-20 https://issues.apache.org/jira/browse/STONEHENGE-19 https://issues.apache.org/jira/browse/STONEHENGE-14 https://issues.apache.org/jira/browse/STONEHENGE-12 https://issues.apache.org/jira/browse/STONEHENGE-57 Please vote to approve Ben as a committer. [] +1 Approve [] +0 [] -0 [] -1 Don't approve Regards, Kamal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgmailto:general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.orgmailto: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] Approve the M1 release of Apache Stonehenge (third try)
+1. Thank you! Deepal On Mon, Jun 1, 2009 at 1:02 PM, Jim Jagielski j...@jagunet.com wrote: +1 On Jun 1, 2009, at 2:43 AM, Selvaratnam Uthaiyashankar wrote: Hi, The Apache Stonehenge community has voted for the M1 release of Apache Stonehenge. We are now asking the approval from the Incubator PMC to publish the release. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. I have uploaded the Apache Stonehenge M1 release artifacts here: http://people.apache.org/~shankar/stonehenge/m1/take4/ The key is here: http://people.apache.org/~shankar/stonehenge/m1/take4/KEYS RAT reports are here: http://people.apache.org/~shankar/stonehenge/m1/rat_report/take4/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m1_incubator_take4/ The release vote on the stonehenge-dev mailing list resulted in *nine* +1 votes and no 0 or -1 votes. +1 votes are from *Drew Baird *Chintana Wilamuna *Paul Fremantle *Ben Dewey *Kent Brown *Abu Obeida Bakhach *Nandana Mihindukulasooriya *Kamaljit Bath *Selvaratnam Uthaiyashankar This includes one IPMC vote from: *Paul Fremantle Vote Mail Thread is here: http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg01030.html Previous attempts on gene...@incubator list is here: http://www.mail-archive.com/general@incubator.apache.org/msg21414.html http://www.mail-archive.com/general@incubator.apache.org/msg21453.html More information about the project can be found here: [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html [Project Page] http://incubator.apache.org/stonehenge/ Please vote to approve this release. [] +1 Publish [] +0 [] -0 [] -1 Don't publish Regards, Shankar - 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] Approve the M1 release of Apache Stonehenge (Second try)
+1 - Deepal On Thu, May 21, 2009 at 10:16 AM, Selvaratnam Uthaiyashankar uthaiyashan...@gmail.com wrote: Hi, The Apache Stonehenge community has voted for the M1 release of Apache Stonehenge. We are now asking the approval from the Incubator PMC to publish the release. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. I have uploaded the Apache Stonehenge M1 release artifacts here: http://people.apache.org/~shankar/stonehenge/m1/take3/ The key is here: http://people.apache.org/~shankar/stonehenge/m1/take3/KEYS RAT reports are here: http://people.apache.org/~shankar/stonehenge/m1/rat_report/take3/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m1_incubator_take3/ The release vote on the stonehenge-dev mailing list resulted in *eight* +1 votes and no 0 or -1 votes. +1 votes are from *Kent Brown *Ben Dewey *Kamaljit Bath *Nandana Mihindukulasooriya *Abu Obeida Bakhach *Chintana Wilamuna *Paul Fremantle *Selvaratnam Uthaiyashankar This includes one IPMC vote from: *Paul Fremantle Vote Mail Thread is here: http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg00945.html Previous attempt on gene...@incubator list is here: http://www.mail-archive.com/general@incubator.apache.org/msg21414.html More information about the project can be found here: [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html [Project Page] http://incubator.apache.org/stonehenge/ Please vote to approve this release. [] +1 Publish [] +0 [] -0 [] -1 Don't publish Regards, Shankar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stonehenge into the Incubator
]) * Afkham Azeez ([MAILTO] [EMAIL PROTECTED]) * Ruwan Linton ([MAILTO] [EMAIL PROTECTED]) * Deepal Jayasinghe ([MAILTO] [EMAIL PROTECTED]) * Nandana Mihindukulasooriya ([MAILTO] [EMAIL PROTECTED]) Affiliations * Samisa Abeysinghe WSO2 * Drew Baird Microsoft * Kamaljit Bath Microsoft * Michael Champion Microsoft * Glen Daniels WSO2 * Senaka Fernando University of Moratuwa * Paul Fremantle WSO2 * Daniel Kulp Progress Software * Mark Little Red Hat * Jonathan Marsh WSO2 * Ole Matzura Eviware * Niclas Reimertz Eviware * Selvaratnam Uthaiyashankar WSO2 * Carl Trieloff Red Hat * Sanjiva Weerawarana WSO2 * Afkham Azeez WSO2 * Ruwan Linton WSO2 * Nandana Mihindukulasooriya WSO2 Sponsors Champion * Paul Fremantle ([MAILTO] [EMAIL PROTECTED]) Nominated Mentors * Danese Cooper ([MAILTO] [EMAIL PROTECTED]) * Daniel Kulp ([MAILTO] [EMAIL PROTECTED]) * Matthieu Riou ([MAILTO] [EMAIL PROTECTED]) * Jim Jagielski ([MAILTO] [EMAIL PROTECTED]) Sponsoring Entity * Incubator -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POLOKA proposal in context of existing Apache projects
I think we can keep this as the same level as Sandesha and Ramparrt. I mean we do not have any modules other than core stuff under Axis2. Deepal Serge, Unfortunately i won't be able to help much at this time due to time pressures. Hopefully one of my fellow PMC members may be interested in moving this forward. Best Wishes. thanks, dims On Fri, Nov 7, 2008 at 3:54 PM, Mankovskii, Serge [EMAIL PROTECTED] wrote: Hi Davanum, In our search for a Champion and Sponsor for the Poloka proposal http://wiki.apache.org/incubator/PolokaProposal We looked into the Savan, ServiceMix, Axis2, and MUSE projects. We find that it makes most sense, so far, to have Poloka as a project under Axis2. It also makes sense to go into the ServiceMix, that implements WS-Notification already, but objectives of ServiceMix and POLOKA are somewhat different in respect to POLOKA goal to provide a stand-alone reference implementation of the spec. Bringing entire ServiceMix in the picture might be too much. However ServiceMix could benefit from the POLOKA work in the future. Poloka (http://poloka.org) could create an Axis2 module implementing handlers creating a messaging network for a federation of Axis2 servers. This way we would be able to support - Standalone WS-Notification compliant notification producer and notification consumer - Standalone WS-BrokeredNotification broker - Federation of WS-BrokeredNotification brokers. It would make sense to integrate Savan functionality within Poloka as time goes but not other way around. I think so because Poloka objective is broader than Savan objective in respect to: - Broker support Broker support is defined in WS-Notification and not in WS-Eventing. Although it is possible that once a broker with WS-Eventing interface is created, the picture might change. - Subscription WS-Eventing defines subscription language based on XPath (content-based semantic). WS-Notification defines subscription Filers using Topic Dialects (topic-based semantic), XPath over message content (content-based semantic, same as in WS-Eventing), and resource properties (optional and unclear semantics, needs refinement in the spec). - Matching performance It seems that we can improve performance of XPath matching based on the research done by the PADRES http://research.msrg.utoronto.ca/pub/Padres project. It would be equally applicable to WS-Notification and WS-Eventing. Naweed Tajuddin, a Master student of Prof. Arno Jacobsen, is looking specifically into this issue for his master thesis. What do you think? We are looking for the input and guidance of the Apache community in moving the POLOKA proposal forward. Please help! Regards Serge -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java Jabber Server
Petar Tahchiev wrote: Hi guys, today I was looking for a Jabber server implemented entirely in Java, and the only results that I got was this: ---(free)--- http://www.codecobra.com/chime/ http://www.open-im.net/ http://www.tigase.org/ http://www.igniterealtime.org/projects/openfire/index.jsp (commercial)--- http://www.adobe.com/special/antepo/?products.opnserver (no longer available - bought by Adobe) Does anyone (besides me) think that we can build something better? Waiting for your suggestions. I also like to contribute to this , if you are going to implement. sometimes ago I wanted to build a Jabber (XMPP) implementation based Stax implementation. May be this is a good chance for that. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
Noel J. Bergman wrote: Yoav Shapira wrote: Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. You mean trademark? :-) Noel , I cam imagine why did you ask this question :) -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Publish the Woden Milestone 6 release
+1, indeed Deepal I checked it out, seems cleanly packaged, with incubation notice and licenses. +1 from me. Paul On 9/27/06, John Kaputin (gmail) [EMAIL PROTECTED] wrote: The Woden developer community has voted on and approved a proposal to release Woden 1.0.0 M6 (Milestone 6). The proposal recieved six +1 votes, including three from WS PMC members. There were no -1 or 0 votes. The proposal can be seen at [1]. The six +1 votes were from: Eran Chinthaka (WS PMC) Arthur Ryman Jeremy Hughes (WS PMC) Oshani Seneviratne Davanum Srinivas (WS PMC) John Kaputin We would now like to request the permission of the Incubator PMC to publish the Woden M6 archives on the Woden Download page at [2]. Please vote by 1pm EST, Friday September 29th 2006. [1] Proposal, http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200609.mbox/[EMAIL PROTECTED] [2] Download, http://people.apache.org/dist/ws/woden/milestones/1.0.0M6-incubating/ Thanks, John Kaputin -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
