Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
Hi Niranjan, Dulitha, It's fantastic to see you and others wanting to dive in and you're all more than welcome. We're looking forward to your involvement to the fullest extent possible in this community. The initial aim of the community right now is to meet the incubator entry requirements, enter the incubator, and immediately form the PPMC and associated mailing lists. That way we can evaluate new committers based on their contribution activity via standard meritocratic guidelines. Without cluttering this thread, we can continue with these and other discussions there once these structures are in place. Hopefully this will not take long and we can get started quickly. Until then please start looking at the initial code and trying to find low hanging issues to get a jump start. Cheers, Alex On Tue, Sep 24, 2013 at 9:06 AM, Niranjan Karunanandham niranjan.k...@gmail.com wrote: +1 for the proposal and I would like to be added as a committer to the usergrid project. I wasn't able to add myself as a committer before voting was called for. Therefore I request if the champion or a mentor can add me to the proposal. Thanks. On Tue, Sep 24, 2013 at 7:30 AM, Dulitha Wijewantha dulit...@gmail.comwrote: +1 for the proposal. I would liked to get added as an initial committer to the user-grid project. I didn't get a chance to add to the proposal before the vote was called. It would be great if the champion or a mentors can add it in the proposal (since now going under a vote). Thanks On Mon, Sep 23, 2013 at 11:46 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 9:15 AM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) It's probably an email client issue. From the `Message-Id:` header of Sanjiva's emails, it looks like might be using Gmail. With Gmail, changing the subject from '[PROPOSAL]...' to '[VOTE]...' -- or from '[VOTE]...' to '[DISCUSS]...' as I've done here -- is not enough to start a new conversation, i.e. thread. Gmail de-dupes subjects where only bracketed text changes. There's not much to do for it except to raise awareness every once in a while. Marvin Humphrey - 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, -- Alex
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (non binding) On 09/23/2013 05:44 AM, Jim Jagielski wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at major global companies in the media, retail, telecommunication and government spaces. The Apache Software Foundation's Way, by putting community before the code, will help Usergrid establish a vibrant, more diverse community to provide these features freely to downstream users. The incubation
Re: [VOTE] first milestone release of Apache Drill (incubating)
On 24 Sep 2013, at 0:11, Ted Dunning wrote: - moving trademarks@ to bcc to avoid mixing private and public lists *Christian*, Do you withdraw this -1 now that Shane has said that we don't have to wait for PODLINGNAMESEARCH-16 to close? I will edit the product status page to reflect current (non) progress. Yes, I withdraw my -1 and give a +1 (I did some more basic checks). Sorry for holding you up, but I felt it was necessary to apply the process and see if it is as we wanted it. Thanks also for your help and patience! On Sun, Sep 22, 2013 at 6:44 AM, Christian Grobmeier grobme...@gmail.comwrote: Hi, Could you please explain why the projects thinks a trademark process is not required? http://incubator.apache.org/**projects/drill.htmlhttp://incubator.apache.org/projects/drill.html For me it is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I don't see why Drill is an exception, but maybe I have missed something. Until I know more, I need to -1 this. Thanks! On Tue, Sep 17, 2013 at 03:29:46PM -0700, Ted Dunning wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%**3CCAKa9qDkMxJp-r8v+**ZwabM5E4b5osrypJyp+DuPvq2LR-** d70...@mail.gmail.com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%3CCAKa9qDn1+**TnKVP=p_=Lh==mOS=azctUz6_** Qvsm4U3Z4gdhHHgQ@mail.gmail.**com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~**jacques/apache-drill-1.0.0-m1.**rc4/http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-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] Apache Chukwa graduation
Eric, we discussed a little on trademarks and it has been said it is recommended to wait for the name search issue to resolve, but not necessary required. The PMC needs to decide themselves to take the risk. If there is an infringement reported to trademarks, it may result in renaming. As concerned on the ASF trademarks, I think everybody should complete the process. However as an IPMC member I do not see much problems with this name. Therefore I withdraw my -1 and give it a +1. Good luck! On 24 Sep 2013, at 7:33, Eric Yang wrote: Thanks. We will request trademarks to look into it. regards, Eric On Mon, Sep 23, 2013 at 5:59 AM, Christian Grobmeier grobme...@gmail.comwrote: On 22 Sep 2013, at 22:59, Eric Yang wrote: We did the name search in 2009, 2010, and 2012 via different Apache processes while we were a sub-project of Hadoop, and repeat the name search process for incubator. The podling name search has been updated in https://issues.apache.org/**jira/browse/PODLINGNAMESEARCH-**19https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-19. I think trademark should not be an issue, Apache Chukwa (TM) has been listed on hadoop.apache.org for years. Hope this addresses the concerns. As the docs say, you can only work with the trademark when Trademark VP has resolved the mentioned issue. Since the issue is open for pretty long time, I will try to urge it on trademarks regards, Eric On Sun, Sep 22, 2013 at 6:38 AM, Christian Grobmeier grobme...@gmail.com wrote: -1 (binding) I have not seen a successful resolution of this process: http://www.apache.org/foundation/marks/naming.htmlhttp://www.apache.org/**foundation/marks/naming.html h**ttp://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I have seen some effort have been made in 2010: http://incubator.apache.org/projects/chukwa.htmlhttp://incubator.apache.org/**projects/chukwa.html http://**incubator.apache.org/projects/**chukwa.htmlhttp://incubator.apache.org/projects/chukwa.html The process has changed meanwhile and needs to be documented. The process has been discussed at general@incubator and should be known. Maybe I missed the issue (Jira being slow today for me). Please send me a successfully resolved issue number and I will turn into +1. Thanks! On Fri, Sep 20, 2013 at 6:52 PM, Eric Yang ey...@apache.org wrote: The Apache Chukwa project entered incubator in July of 2010. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Chukwa community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/chukwa-graduation-votehttp://s.apache.org/chukwa-**graduation-vote http://s.**apache.org/chukwa-graduation-**votehttp://s.apache.org/chukwa-graduation-vote [2] http://s.apache.org/chukwa-graduation-resulthttp://s.apache.org/chukwa-**graduation-result http://s.**apache.org/chukwa-graduation-**resulthttp://s.apache.org/chukwa-graduation-result [3] http://s.apache.org/chukwa-graduation-Resolutionhttp://s.apache.org/chukwa-**graduation-Resolution http://**s.apache.org/chukwa-**graduation-Resolutionhttp://s.apache.org/chukwa-graduation-Resolution Resolution: X.Establish the Apache Chukwa 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 data streaming and visualization for Hadoop services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Chukwa Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Chukwa Project be and hereby is responsible for the creation and maintenance of a software project related to data streaming, monitoring and visualization for Hadoop services; and be it further RESOLVED, that the office of Vice President, Apache Chukwa 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 Chukwa Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Chukwa Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to
Re: binary release artifacts
I closed LEGAL-178 with the resolution Not A Problem, which is quite different to a resolution of Fixed or Resolved or Answered. From my investigation, things like the text of the AL and various posts in the mailing lists over the years answered the question to my satisfaction. I doubt everyone agrees yet but the answers for me are: - there is no need to vote on the convenience binary artifacts - in fact voting on them is a bit pointless as you can't easily verify the contents anyway, and the ASF only does source releases. - its ok to have unvoted on convenience binaries in the ASF distribution areas - there is no requirement to have LICENSE/NOTICE files in the root directory of a convenience binary However i think it would take a fair bit of work to build enough consensus around any documentation update. So just closing LEGAL-178 as Not A Problem seemed much easier now that it seems like no one is insisting any historic artifacts be removed. Happy to continue discussing this as it does seem an interesting topic, but if we do could it be in a new thread not so tied to Chukwa. ...ant On Mon, Sep 23, 2013 at 11:42 PM, Luciano Resende luckbr1...@gmail.comwrote: On Mon, Sep 23, 2013 at 2:23 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 1:45 PM, Luciano Resende luckbr1...@gmail.com wrote: Thanks for the summary Marvin, how about we take the chance to update our policy/documentation to clarify the social norm regarding placement of LICENSE/NOTICE in the top level of a distribution but also clarify that, any artifact being release by an Apache Project should be reviewed and voted, as there were some suggestions on this thread that this was not the case. If we can't clarify that on ASF level, at least we can clarify that on the IPMC level. I understand the motivation, but I'm actually in favor of keeping the status quo. As Joe Schaefer pointed out, the VOTE only applies to the canonical source release. Binary artifacts cannot be official releases of the ASF, and the IPMC cannot override that policy. Is there any written policy that states that ? I have never heard that the ASF can't have binary artifacts as official releases ? Also, from Joe's message, I think he was mentioning what is done in the context of HTTPD, not necessarily stating a policy or the social norm here at Apache. Additionally, we still have a lot of work to do to squash licensing documentation bugs in our canonical source releases. When we can't even get our official releases right, I don't think it makes sense to dilute our already thin quality control resources. Marvin Humphrey The issue I see, particularly when evaluating maven based java source releases (no binaries at all), is that the a lot of the dependencies for a project might be transient making much harder and much more work to evaluate a source only release. While reviewing a binary release, you have listed all the binary dependencies and all it's associated license, making the review process much simpler, allowing the reviewer to concentrate on making sure the dependencies are allowed, no specific jars got unaccounted on the license/notice, etc... [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3CBF8E0313-15C2-4375-8470-FE0A1DA917C5%40yahoo.com%3E -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: [VOTE] : Release Apache Sentry 1.2.0 incubating (rc0)
Hi Shreepadma, I am withdrawing my -1 as this has been resolved. Please note, I believe this name will ask for trouble, esp with getsentry.com. I also believe you should discuss this in your project if you really want to take on the risk of this name prior graduation. Thanks, Christian On 24 Sep 2013, at 0:30, Shreepadma Venugopalan wrote: Hi Christain, Name search JIRA for Sentry has been resolved. Are you OK with changing your vote? Cheers, Shreepadma On Sun, Sep 22, 2013 at 11:59 AM, Christian Grobmeier grobme...@gmail.comwrote: Shreepadma Venugopalan schrieb: On Sun, Sep 22, 2013 at 11:06 AM, Christian Grobmeier grobme...@gmail.comwrote: Shreepadma Venugopalan schrieb: Per this document: http://www.apache.org/foundation/marks/naming.html, its required to start the name search process before we release any packages. It doesn't mention the name has to be cleared before a release. OK, maybe it's no phrased well. But surely you understand why the name must be cleared before any package is released? Well, the way the rule reads today is the search process has to start before a release can happen. If the name has to be cleared before a release, it needs to be explicitly stated that way. On the end of the document one can read: The V.P. Branding will finally approve your request. Important: you must wait until your trademark has been approved. There is no lazy consensus. Once the name is approved, you can resolve the JIRA issue and work with your new trademark. Incubator Podlings: please don't forget to update your Incubator status page. It says, you can only work with your trademark when VP has approved the mark. For me this includes a release. You maybe can guess that it can cause trouble when you work with a brand with has not checked. Only recently we had to rename a subproject of project because the brand was not checked accordingly. We can either discuss about grammar or spelling issues, which this document surely has (they are mostly my fault). Or we can simply try to understand what problems it solves and act like that. For me trademarks clearance are as important as a clean IP. If I were you, I would keep this vote running, but make the outcome pending to the response. Now, as Jira is available to me again I can see there a couple of (software) projects using the name Sentry already. Like for example: getsentry.com Given the high number of other which use the name (346 search results on github) I have concerns we will run into a trademark conflict here and insist you wait until trademarks@ has approved your mark. + cc Trademarks Cheers Christain We have already started a name search JIRA for Apache Sentry. Here's the name search JIRA for Apache Sentry: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-38 OK, then lets wait until this has been closed. The project status page (http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html) has also been updated to reflect it. I can't see a note. Maybe its not yet published? I think the voting can continue on this RC. I disagree. First clear the name, then release. Anyway I will propose a change on the process document to make the intention more clear. Cheers Cheers. Shreepadma Thanks. Shreepadma On Sun, Sep 22, 2013 at 6:41 AM, Christian Grobmeier grobme...@gmail.comwrote: -1 (binding). As per this document: http://incubator.apache.org/**projects/sentry.html http://incubator.apache.org/projects/sentry.html the trademark process has not been resolved. It is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html Thanks! On 22 Sep 2013, at 7:02, Shreepadma Venugopalan wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~**shreepadma/sentry-1.2.0/ http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/**repos/asf/incubator-sentry/** repo?p=incubator-sentry.git;a=**log;h=refs/tags/release-1.2.0-**rc0 https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/**keys/group/sentry.asc https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=**sentry%20vote%20release#query:**
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (non binding) On Tue, Sep 24, 2013 at 3:44 PM, Imesh Gunaratne imesh.gunara...@gmail.comwrote: +1 (non binding) On Tue, Sep 24, 2013 at 12:52 PM, Bruno Mahé bm...@apache.org wrote: +1 (non binding) On 09/23/2013 05:44 AM, Jim Jagielski wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/**incubator/UsergridProposalhttps://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention
Re: [VOTE]: Graduate Apache jclouds as an Apache Top Level Project
On Sep 23, 2013, at 2:57 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Reminder - it'd be great to get more eyes and make sure we're not missing anything for graduation. Thanks! + 1 (already voted on PPMC list, just cheer leading for others to look over) Andrew, Since 5 IPMC member/mentors already voted on the Podling dev list, I do not think any further votes are needed. But as you put it rightly, more eyes and reviews will be better. I would just put a end time to close the vote. Since the next board meeting is 3 weeks away, no hurry though. Suresh A. On Fri, Sep 20, 2013 at 5:00 PM, Andrew Bayer andrew.ba...@gmail.comwrote: argh, line breaks all vanished in weird ways. Here's a better format: The Apache jclouds project entered incubation in April of 2013, and since then has shipped two releases, added a committer, and transitioned thoroughly into the Apache Way for decision-making, development process, etc. Our website[1] conforms, so far as we can tell, with Apache's standards, the existing jclouds registered trademark has been transferred to the ASF[2], we've decided on a set of project bylaws[4], and now we've held a vote[5] on a graduation resolution[6, and below] to be added to the agenda for the next ASF board meeting. The vote has passed[7] with 7 binding PPMC +1s and 4 binding mentor +1s, so on behalf of the Apache jclouds project, I'd like to request the IPMC's approval for our graduation. Thanks! Please cast your vote: [ ] +1 Graduate the Apache jclouds podling from Apache Incubator as a TLP [ ] +0 Indifferent to the graduation status of Apache jclouds podling [ ] -1 Reject graduation of Apache jclouds podling from Apache Incubator because ... The vote will be open for 72 hours, until 5pm PDT on Monday, September 23rd. [1]: http://jclouds.incubator.apache.org/ [2]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-37 [3]: http://apache.markmail.org/thread/q6sqwspp55sjtk2v [4]: https://wiki.apache.org/jclouds/Bylaws [5]: http://markmail.org/thread/vnnvej3q7sla3btl [6]: https://wiki.apache.org/jclouds/GraduationCharter [7]: http://apache.markmail.org/thread/55d6vle5be43gwtv Thanks again - The Apache jclouds project --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache jclouds Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache jclouds Project be and hereby is responsible for the creation and maintenance of a software project related to providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API; and be it further RESOLVED, that the office of Vice President, jclouds 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 jclouds Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache jclouds 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 jclouds Project: * Adrian Cole (adrianc...@apache.org) * Andrew Bayer(aba...@apache.org) * Andrew Gaul (g...@apache.org) * Andrew Phillips (andr...@apache.org) * Becca Wood (silky...@apache.org) * Everett Toews (ever...@apache.org) * David Nalley(ke4...@apache.org) * Ignasi Barrera (n...@apache.org) * Ioannis Canellos(ioca...@apache.org) * Matt Stephenson (matts...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrew Bayer be and hereby is appointed to the office of Vice President, jclouds, 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 jclouds Project be and hereby is tasked with the migration and rationalization of the Apache Incubator jclouds podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator jclouds podling encumbered upon the Apache Incubator PMC are hereafter discharged. On Fri, Sep 20, 2013 at 4:49 PM, Andrew Bayer andrew.ba...@gmail.comwrote: The Apache jclouds project entered incubation in April of
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+ 1 (binding). Good project and I will vote nevertheless, but given there is interest, why not have a 3rd Mentor on board? This is not essential but as discussed at various times, makes release and other IPMC binding decisions easy. I do not want to trigger a discussion on, if we want to change the proposal after the VOTE started, but hopefully adding a 3rd mentor should be non-controversial. May be we can volunteer/obligate the champion to double duty as Mentor as well :) Suresh On Sep 23, 2013, at 8:44 AM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) On Sep 24, 2013, at 3:14 AM, Alex Karasulu akaras...@apache.org wrote: Hi Niranjan, Dulitha, It's fantastic to see you and others wanting to dive in and you're all more than welcome. We're looking forward to your involvement to the fullest extent possible in this community. The initial aim of the community right now is to meet the incubator entry requirements, enter the incubator, and immediately form the PPMC and associated mailing lists. That way we can evaluate new committers based on their contribution activity via standard meritocratic guidelines. Without cluttering this thread, we can continue with these and other discussions there once these structures are in place. Hopefully this will not take long and we can get started quickly. Until then please start looking at the initial code and trying to find low hanging issues to get a jump start. Cheers, Alex On Tue, Sep 24, 2013 at 9:06 AM, Niranjan Karunanandham niranjan.k...@gmail.com wrote: +1 for the proposal and I would like to be added as a committer to the usergrid project. I wasn't able to add myself as a committer before voting was called for. Therefore I request if the champion or a mentor can add me to the proposal. Thanks. On Tue, Sep 24, 2013 at 7:30 AM, Dulitha Wijewantha dulit...@gmail.comwrote: +1 for the proposal. I would liked to get added as an initial committer to the user-grid project. I didn't get a chance to add to the proposal before the vote was called. It would be great if the champion or a mentors can add it in the proposal (since now going under a vote). Thanks On Mon, Sep 23, 2013 at 11:46 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 9:15 AM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) It's probably an email client issue. From the `Message-Id:` header of Sanjiva's emails, it looks like might be using Gmail. With Gmail, changing the subject from '[PROPOSAL]...' to '[VOTE]...' -- or from '[VOTE]...' to '[DISCUSS]...' as I've done here -- is not enough to start a new conversation, i.e. thread. Gmail de-dupes subjects where only bracketed text changes. There's not much to do for it except to raise awareness every once in a while. Marvin Humphrey - 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, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
Sanjiva has expressed interest in helping out as a mentor, but I'm not sure if he's officially asking. If he does, I'm a big +1 on adding him. If you are also interested, that would give Usergrid a nice solid 4 mentors, which I think is pretty much on the mark. On Sep 23, 2013, at 9:49 PM, Jake Farrell jfarr...@apache.org wrote: Jim Do you need any additional mentors for this? -Jake On Mon, Sep 23, 2013 at 12:15 PM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) On Sep 23, 2013, at 12:03 PM, Sanjiva Weerawarana sanj...@wso2.com wrote: Are you going to start a VOTE thread? +1 in any case :-). On Mon, Sep 23, 2013 at 6:14 PM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
It's great to see many cool and exciting new projects joining Apache Incubator. +1 from my side On Fri, Sep 20, 2013 at 3:54 PM, Sanjiva Weerawarana sanj...@wso2.comwrote: +1 - there's a lot of overlap / commonality of objective between BaaS and the set of services provided by Apache Stratos (incubating) to developers of apps. I'm very happy to see this come to ASF and will be happy to mentor if you guys need another one. Cheers, Sanjiva. On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent
Re: [VOTE]: Release Apache Sentry 1.2.0 incubating (rc0)
+1 (binding) -- Andrei Savu On Sun, Sep 22, 2013 at 8:02 AM, Shreepadma Venugopalan shreepa...@apache.org wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that
Re: [VOTE] first release of Apache Blur (incubating)
+1 (binding) Nice work guys! -- Andrei Savu On Tue, Sep 24, 2013 at 3:50 AM, Aaron McCurry amccu...@gmail.com wrote: We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Am I correct in assuming that the affiliation is WSO2? On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale ==
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 On 23 September 2013 22:44, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at major global companies in the media, retail, telecommunication and government spaces. The Apache Software Foundation's Way, by putting community before the code, will help Usergrid establish a vibrant, more diverse
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1. I'll add you to the proposal On Sep 24, 2013, at 8:54 AM, Jake Farrell jfarr...@apache.org wrote: I would be interested in helping as a mentor for Usergrid if slots are available -Jake On Tue, Sep 24, 2013 at 7:43 AM, Jim Jagielski j...@jagunet.com wrote: Sanjiva has expressed interest in helping out as a mentor, but I'm not sure if he's officially asking. If he does, I'm a big +1 on adding him. If you are also interested, that would give Usergrid a nice solid 4 mentors, which I think is pretty much on the mark. On Sep 23, 2013, at 9:49 PM, Jake Farrell jfarr...@apache.org wrote: Jim Do you need any additional mentors for this? -Jake On Mon, Sep 23, 2013 at 12:15 PM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) On Sep 23, 2013, at 12:03 PM, Sanjiva Weerawarana sanj...@wso2.com wrote: Are you going to start a VOTE thread? +1 in any case :-). On Mon, Sep 23, 2013 at 6:14 PM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Thanks. Am I correct in assuming that the affiliation is WSO2? Yes. On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
Yes I was volunteering to mentor .. please add me. Sanjiva. On Tue, Sep 24, 2013 at 5:13 PM, Jim Jagielski j...@jagunet.com wrote: Sanjiva has expressed interest in helping out as a mentor, but I'm not sure if he's officially asking. If he does, I'm a big +1 on adding him. If you are also interested, that would give Usergrid a nice solid 4 mentors, which I think is pretty much on the mark. On Sep 23, 2013, at 9:49 PM, Jake Farrell jfarr...@apache.org wrote: Jim Do you need any additional mentors for this? -Jake On Mon, Sep 23, 2013 at 12:15 PM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) On Sep 23, 2013, at 12:03 PM, Sanjiva Weerawarana sanj...@wso2.com wrote: Are you going to start a VOTE thread? +1 in any case :-). On Mon, Sep 23, 2013 at 6:14 PM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced,
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, Thanks for your clarification. I could not express my interest in joining Usergrid as a committer before we started the Voting process. If it is not a problem, please add me as a committer. Thanks Imesh Gunaratne Committer PMC Member, Apache Stratos Technical Lead, WSO2 Inc On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Am I correct in assuming that the affiliation is WSO2? On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
All done. Thx! On Sep 24, 2013, at 9:24 AM, Sanjiva Weerawarana sanj...@wso2.com wrote: Yes I was volunteering to mentor .. please add me. Sanjiva. On Tue, Sep 24, 2013 at 5:13 PM, Jim Jagielski j...@jagunet.com wrote: Sanjiva has expressed interest in helping out as a mentor, but I'm not sure if he's officially asking. If he does, I'm a big +1 on adding him. If you are also interested, that would give Usergrid a nice solid 4 mentors, which I think is pretty much on the mark. On Sep 23, 2013, at 9:49 PM, Jake Farrell jfarr...@apache.org wrote: Jim Do you need any additional mentors for this? -Jake On Mon, Sep 23, 2013 at 12:15 PM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) On Sep 23, 2013, at 12:03 PM, Sanjiva Weerawarana sanj...@wso2.com wrote: Are you going to start a VOTE thread? +1 in any case :-). On Mon, Sep 23, 2013 at 6:14 PM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Added. On Sep 24, 2013, at 9:24 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Thanks. Am I correct in assuming that the affiliation is WSO2? Yes. On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for
Re: [VOTE] Apache Chukwa graduation
+1 - binding Regards, Alan On Sep 20, 2013, at 10:52 AM, Eric Yang ey...@apache.org wrote: [ ] +1 Graduate Chukwa podling from Incubator [ ] +0 Indifferent to graduation status of Chukwa [ ] -1 Reject graduation of Chukwa podling from Incubator because ...
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
As I have requested before can you add me into the committer list as well. I am interested in contributing to user-grid. Thanks Dulitha R. Wijewantha Software Engineer Tel: 94112793140 | Mobile:94112793140 dulit...@gmail.com |http://dulithawijewantha.com On Sep 24, 2013, at 7:05 PM, Jim Jagielski j...@jagunet.com wrote: Added. On Sep 24, 2013, at 9:24 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Thanks. Am I correct in assuming that the affiliation is WSO2? Yes. On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Correction: Imesh Gunaratne Committer PPMC Member, Apache Stratos (Incubating) Technical Lead, WSO2 Inc Thanks Imesh On Tue, Sep 24, 2013 at 7:02 PM, Imesh Gunaratne im...@apache.org wrote: Hi Jim, Thanks for your clarification. I could not express my interest in joining Usergrid as a committer before we started the Voting process. If it is not a problem, please add me as a committer. Thanks Imesh Gunaratne Committer PMC Member, Apache Stratos Technical Lead, WSO2 Inc On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Am I correct in assuming that the affiliation is WSO2? On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
WSO2 affiliation? On Sep 24, 2013, at 9:49 AM, Dulitha Rasanga Wijewantha dulit...@gmail.com wrote: As I have requested before can you add me into the committer list as well. I am interested in contributing to user-grid. Thanks Dulitha R. Wijewantha Software Engineer Tel: 94112793140 | Mobile:94112793140 dulit...@gmail.com |http://dulithawijewantha.com On Sep 24, 2013, at 7:05 PM, Jim Jagielski j...@jagunet.com wrote: Added. On Sep 24, 2013, at 9:24 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski j...@jagunet.com wrote: No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a please add me as a committer, which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Thanks. Am I correct in assuming that the affiliation is WSO2? Yes. On Sep 24, 2013, at 8:21 AM, Nirmal Fernando nirmal070...@gmail.com wrote: Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando nirmal070...@apache.orgwrote: Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Tue, Sep 24, 2013 at 4:25 AM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) If a podling wants to add anyone who asks to the initial committers list, that's their choice, but it's no longer the only option. See the May 2012 thread on general@incubator entitled Open enrollment: http://markmail.org/thread/kkh5ilbiqu7p3hy7 So now we have a situation where the proposal has been modified while the VOTE is underway and a personnel dispute has arisen. This is exactly the kind of situation that the language added to the proposal guide back in June was intended to avert: http://incubator.apache.org/guides/proposal.html#vote When the proposal seems finished and some sort of consensus has emerged, the proposal should be put to a vote. If the wiki is used to develop the proposal, please ensure that the wiki matches the final proposal then add a notice to the wiki that development of the document is now complete: /!\ '''FINAL''' /!\ This proposal is now complete and has been submitted for a VOTE. Embed the final proposal text or a link to a specific revision number of the wiki proposal page in the email which kicks off the VOTE thread. If a change is required after the vote has been called then the vote must be cancelled, the change made, and the vote restarted. Alternatively, Mentors will advise on how to make the change once the proposal has been accepted if this is appropriate. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Graduate Apache jclouds as an Apache Top Level Project
And a belated +1, not that it needs the extra vote, but jclouds functions great! On Tue, Sep 24, 2013 at 3:56 AM, Suresh Marru sma...@apache.org wrote: On Sep 23, 2013, at 2:57 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Reminder - it'd be great to get more eyes and make sure we're not missing anything for graduation. Thanks! + 1 (already voted on PPMC list, just cheer leading for others to look over) Andrew, Since 5 IPMC member/mentors already voted on the Podling dev list, I do not think any further votes are needed. But as you put it rightly, more eyes and reviews will be better. I would just put a end time to close the vote. Since the next board meeting is 3 weeks away, no hurry though. Suresh A. On Fri, Sep 20, 2013 at 5:00 PM, Andrew Bayer andrew.ba...@gmail.com wrote: argh, line breaks all vanished in weird ways. Here's a better format: The Apache jclouds project entered incubation in April of 2013, and since then has shipped two releases, added a committer, and transitioned thoroughly into the Apache Way for decision-making, development process, etc. Our website[1] conforms, so far as we can tell, with Apache's standards, the existing jclouds registered trademark has been transferred to the ASF[2], we've decided on a set of project bylaws[4], and now we've held a vote[5] on a graduation resolution[6, and below] to be added to the agenda for the next ASF board meeting. The vote has passed[7] with 7 binding PPMC +1s and 4 binding mentor +1s, so on behalf of the Apache jclouds project, I'd like to request the IPMC's approval for our graduation. Thanks! Please cast your vote: [ ] +1 Graduate the Apache jclouds podling from Apache Incubator as a TLP [ ] +0 Indifferent to the graduation status of Apache jclouds podling [ ] -1 Reject graduation of Apache jclouds podling from Apache Incubator because ... The vote will be open for 72 hours, until 5pm PDT on Monday, September 23rd. [1]: http://jclouds.incubator.apache.org/ [2]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-37 [3]: http://apache.markmail.org/thread/q6sqwspp55sjtk2v [4]: https://wiki.apache.org/jclouds/Bylaws [5]: http://markmail.org/thread/vnnvej3q7sla3btl [6]: https://wiki.apache.org/jclouds/GraduationCharter [7]: http://apache.markmail.org/thread/55d6vle5be43gwtv Thanks again - The Apache jclouds project --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache jclouds Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache jclouds Project be and hereby is responsible for the creation and maintenance of a software project related to providing a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API; and be it further RESOLVED, that the office of Vice President, jclouds 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 jclouds Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache jclouds 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 jclouds Project: * Adrian Cole (adrianc...@apache.org) * Andrew Bayer(aba...@apache.org) * Andrew Gaul (g...@apache.org) * Andrew Phillips (andr...@apache.org) * Becca Wood (silky...@apache.org) * Everett Toews (ever...@apache.org) * David Nalley(ke4...@apache.org) * Ignasi Barrera (n...@apache.org) * Ioannis Canellos(ioca...@apache.org) * Matt Stephenson (matts...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrew Bayer be and hereby is appointed to the office of Vice President, jclouds, 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 jclouds Project be and hereby is tasked with the migration and rationalization of the Apache Incubator jclouds podling; and be it further RESOLVED, that all responsibility pertaining to the
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (binding) Thanks, Senaka. On Tue, Sep 24, 2013 at 6:49 PM, Olivier Lamy ol...@apache.org wrote: +1 On 23 September 2013 22:44, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at
Re: [RESULT] first milestone release of Apache Drill (incubating)
This vote has closed and has passed according to majority vote because it has at least 3 +1 votes and more +1 than -1 votes. The final tally is this: *Binding +1 votes* Ted Dunning Steve Loughran Benson Margulies Grant Ingersoll Henry Saputra Isabel Drost-Fromm *Binding -1 votes* Christian Grobmeier As a side note, Christian's negative vote had to do with name search hygiene which has, in fact, been completed but not approved by VP Brands (Shane). Shane has said that approval should not gate the release and if we delayed the result of this vote, I expect that Christian would reverse his vote, based on his off-thread comments. On Mon, Sep 23, 2013 at 3:42 PM, Ted Dunning ted.dunn...@gmail.com wrote: - trademarks@ to avoid mixing public and private threads Christian, Shane has answered your worry about whether VP Brands has to close the name search before DRILL can release. I have created the link you requested on the podling status page. Note again that the name search was done *a year ago*. Far from neglecting naming issues, this podling has been very far out in front on this issue. The hangup is entirely with VP Brands. Release votes are majority votes in any case [1]. I would prefer it if we had complete consensus here, so if you can update your vote, I would appreciate it. On Sun, Sep 22, 2013 at 6:44 AM, Christian Grobmeier grobme...@gmail.comwrote: Hi, Could you please explain why the projects thinks a trademark process is not required? http://incubator.apache.org/**projects/drill.htmlhttp://incubator.apache.org/projects/drill.html For me it is required to clear the name before a product is published: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html I don't see why Drill is an exception, but maybe I have missed something. Until I know more, I need to -1 this. Thanks! On Tue, Sep 17, 2013 at 03:29:46PM -0700, Ted Dunning wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%**3CCAKa9qDkMxJp-r8v+**ZwabM5E4b5osrypJyp+DuPvq2LR-** d70...@mail.gmail.com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.**org/mod_mbox/incubator-drill-** dev/201309.mbox/%3CCAKa9qDn1+**TnKVP=p_=Lh==mOS=azctUz6_** Qvsm4U3Z4gdhHHgQ@mail.gmail.**com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~**jacques/apache-drill-1.0.0-m1.**rc4/http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
To abide, I have cancelled the vote. I would encourage people who STILL want to be added, and if I have not done so, to ANNOUNCE their intention in this thread and then take on the responsibility of adding themselves. I will kick off another VOTE on Thursday (the 26th) at noon eastern. I will make the proposal as FINAL and no changes will be allowed/accepted at that point. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (non binding) On Tue, Sep 24, 2013 at 12:52 PM, Bruno Mahé bm...@apache.org wrote: +1 (non binding) On 09/23/2013 05:44 AM, Jim Jagielski wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/**incubator/UsergridProposalhttps://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at major global companies in the media, retail, telecommunication
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I'd expect apache committers or members that are interested in a podling's product will express that by joining with code and/or documentation improvements, and as a result get voted in as committers just like anyone else. In fact, the Incubation Policy says about mentors (section Committers at the bottom of [1]): On acceptance of a candidate project, the assigned Mentors shall be given access to the Podling's repository for the duration of the incubation process. [...] To be given full committer privileges, such as the right to add new code to the repository, the Mentor must earn them as would any other potential new committer. I'm not specifically against it, I just like to understand why this is a good idea. Lieven On Sep 24, 2013, at 3:14 AM, Alex Karasulu akaras...@apache.org wrote: Hi Niranjan, Dulitha, It's fantastic to see you and others wanting to dive in and you're all more than welcome. We're looking forward to your involvement to the fullest extent possible in this community. The initial aim of the community right now is to meet the incubator entry requirements, enter the incubator, and immediately form the PPMC and associated mailing lists. That way we can evaluate new committers based on their contribution activity via standard meritocratic guidelines. Without cluttering this thread, we can continue with these and other discussions there once these structures are in place. Hopefully this will not take long and we can get started quickly. Until then please start looking at the initial code and trying to find low hanging issues to get a jump start. Cheers, Alex On Tue, Sep 24, 2013 at 9:06 AM, Niranjan Karunanandham niranjan.k...@gmail.com wrote: +1 for the proposal and I would like to be added as a committer to the usergrid project. I wasn't able to add myself as a committer before voting was called for. Therefore I request if the champion or a mentor can add me to the proposal. Thanks. On Tue, Sep 24, 2013 at 7:30 AM, Dulitha Wijewantha dulit...@gmail.comwrote: +1 for the proposal. I would liked to get added as an initial committer to the user-grid project. I didn't get a chance to add to the proposal before the vote was called. It would be great if the champion or a mentors can add it in the proposal (since now going under a vote). Thanks On Mon, Sep 23, 2013 at 11:46 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 9:15 AM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) It's probably an email client issue. From the `Message-Id:` header of Sanjiva's emails, it looks like might be using Gmail. With Gmail, changing the subject from '[PROPOSAL]...' to '[VOTE]...' -- or from '[VOTE]...' to '[DISCUSS]...' as I've done here -- is not enough to start a new conversation, i.e. thread. Gmail de-dupes subjects where only bracketed text changes. There's not much to do for it except to raise awareness every once in a while. Marvin Humphrey - 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, -- Alex - 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] Usergrid BaaS Stack for Apache Incubator
Forgot to add the link. On Tue, Sep 24, 2013 at 2:40 PM, Lieven Govaerts lieven.govae...@gmail.com wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I'd expect apache committers or members that are interested in a podling's product will express that by joining with code and/or documentation improvements, and as a result get voted in as committers just like anyone else. In fact, the Incubation Policy says about mentors (section Committers at the bottom of [1]): [1]: http://incubator.apache.org/incubation/Incubation_Policy.html#Committers On acceptance of a candidate project, the assigned Mentors shall be given access to the Podling's repository for the duration of the incubation process. [...] To be given full committer privileges, such as the right to add new code to the repository, the Mentor must earn them as would any other potential new committer. I'm not specifically against it, I just like to understand why this is a good idea. Lieven On Sep 24, 2013, at 3:14 AM, Alex Karasulu akaras...@apache.org wrote: Hi Niranjan, Dulitha, It's fantastic to see you and others wanting to dive in and you're all more than welcome. We're looking forward to your involvement to the fullest extent possible in this community. The initial aim of the community right now is to meet the incubator entry requirements, enter the incubator, and immediately form the PPMC and associated mailing lists. That way we can evaluate new committers based on their contribution activity via standard meritocratic guidelines. Without cluttering this thread, we can continue with these and other discussions there once these structures are in place. Hopefully this will not take long and we can get started quickly. Until then please start looking at the initial code and trying to find low hanging issues to get a jump start. Cheers, Alex On Tue, Sep 24, 2013 at 9:06 AM, Niranjan Karunanandham niranjan.k...@gmail.com wrote: +1 for the proposal and I would like to be added as a committer to the usergrid project. I wasn't able to add myself as a committer before voting was called for. Therefore I request if the champion or a mentor can add me to the proposal. Thanks. On Tue, Sep 24, 2013 at 7:30 AM, Dulitha Wijewantha dulit...@gmail.comwrote: +1 for the proposal. I would liked to get added as an initial committer to the user-grid project. I didn't get a chance to add to the proposal before the vote was called. It would be great if the champion or a mentors can add it in the proposal (since now going under a vote). Thanks On Mon, Sep 23, 2013 at 11:46 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 9:15 AM, Jim Jagielski j...@jagunet.com wrote: Did you see what you replied too?? propose a vote and the subject sez [VOTE]. :) It's probably an email client issue. From the `Message-Id:` header of Sanjiva's emails, it looks like might be using Gmail. With Gmail, changing the subject from '[PROPOSAL]...' to '[VOTE]...' -- or from '[VOTE]...' to '[DISCUSS]...' as I've done here -- is not enough to start a new conversation, i.e. thread. Gmail de-dupes subjects where only bracketed text changes. There's not much to do for it except to raise awareness every once in a while. Marvin Humphrey - 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, -- Alex - 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] Usergrid BaaS Stack for Apache Incubator
Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (non-binding) Good luck! I would be interested in being a committer on user-grid due to the synergies that seem possible between Apache Knox (incubating) and user-grid. If this is something that you would welcome then I would be happy to join as an initial committer. Regardless, good luck and enjoy! On Tue, Sep 24, 2013 at 12:57 PM, Senaka Fernando sen...@apache.org wrote: +1 (binding) Thanks, Senaka. On Tue, Sep 24, 2013 at 6:49 PM, Olivier Lamy ol...@apache.org wrote: +1 On 23 September 2013 22:44, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
+1 (non-binding) Lieven On Mon, Sep 23, 2013 at 2:44 PM, Jim Jagielski j...@jagunet.com wrote: After a useful and successful proposal cycle, I would like to propose a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Voting to run for 72+ hours... Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at major global companies in the media, retail, telecommunication and government spaces. The Apache Software Foundation's Way, by putting community before the code, will help Usergrid
Re: [VOTE] Release Apache Spark 0.8.0-incubating (RC6)
[ ] +1 Release this package as Apache Spark 0.8.0-incubating [ ] -1 Do not release this package because ... +1 (binding!) Ben. To learn more about Apache Spark, please see http://spark.incubator.apache.org/ [1] http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201309.mbox/%3CCABPQxsvS14wfiABj32b_%2BgtLafmDog%3DcbWjn7v4FoqG5g-a7mQ%40mail.gmail.com%3E - Patrick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] first release of Apache Blur (incubating)
+1 (binding) congrats! On Mon, Sep 23, 2013 at 5:50 PM, Aaron McCurry amccu...@gmail.com wrote: We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release - 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
On Tue, Sep 24, 2013 at 02:40:19PM +0200, Lieven Govaerts wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I said initial proposal stage. After accepted and it actually becomes a podling then, of course, the podling decides how high or low that bar is. But we aren't talking about that. -- === Jim Jagielski [|] j...@jagunet.com [|] http://www.jaguNET.com/ Great is the guilt of an unnecessary war ~ John Adams - 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
On Wed, Sep 25, 2013 at 1:34 AM, Jim Jagielski j...@jagunet.com wrote: On Tue, Sep 24, 2013 at 02:40:19PM +0200, Lieven Govaerts wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I said initial proposal stage. After accepted and it actually becomes a podling then, of course, the podling decides how high or low that bar is. But we aren't talking about that. So during the initial proposal stage anyone who volunteers goes in without having to contribute? There's no input from the perspective podliing? -- Best Regards, -- Alex
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Wed, Sep 25, 2013 at 01:59:21AM +0600, Alex Karasulu wrote: On Wed, Sep 25, 2013 at 1:34 AM, Jim Jagielski j...@jagunet.com wrote: On Tue, Sep 24, 2013 at 02:40:19PM +0200, Lieven Govaerts wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I said initial proposal stage. After accepted and it actually becomes a podling then, of course, the podling decides how high or low that bar is. But we aren't talking about that. So during the initial proposal stage anyone who volunteers goes in without having to contribute? There's no input from the perspective podliing? How can they have contributed if its a new podling? -- === Jim Jagielski [|] j...@jagunet.com [|] http://www.jaguNET.com/ Great is the guilt of an unnecessary war ~ John Adams - 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
We definitely want participation, that's what this is all about, but I'm a little bit surprised at the number of folks all from the same company affiliation who want to be committers that have had heretofore no involvement or interest in the project for it's previous 2 years of ASLv2 existence on GitHub. Would really like to see some code contributions to at least make sure there's an understanding of the architecture, but maybe that's not the way the process works. On Tue, Sep 24, 2013 at 3:59 PM, Alex Karasulu akaras...@apache.org wrote: On Wed, Sep 25, 2013 at 1:34 AM, Jim Jagielski j...@jagunet.com wrote: On Tue, Sep 24, 2013 at 02:40:19PM +0200, Lieven Govaerts wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I said initial proposal stage. After accepted and it actually becomes a podling then, of course, the podling decides how high or low that bar is. But we aren't talking about that. So during the initial proposal stage anyone who volunteers goes in without having to contribute? There's no input from the perspective podliing? -- Best Regards, -- Alex
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Wed, Sep 25, 2013 at 2:14 AM, Jim Jagielski j...@jagunet.com wrote: On Wed, Sep 25, 2013 at 01:59:21AM +0600, Alex Karasulu wrote: On Wed, Sep 25, 2013 at 1:34 AM, Jim Jagielski j...@jagunet.com wrote: On Tue, Sep 24, 2013 at 02:40:19PM +0200, Lieven Govaerts wrote: On Tue, Sep 24, 2013 at 1:25 PM, Jim Jagielski j...@jagunet.com wrote: Alex, if people want to join and add themselves as committers, then they can. The bar to entry for podlings during the initial proposal stage is I'm interested :) Is there some more background available on why the barrier is set this low in the incubator? It seems unnatural to me. A large part of incubation of course is to attract new committers, but why not let the podling decide on which barrier it wants to use? I said initial proposal stage. After accepted and it actually becomes a podling then, of course, the podling decides how high or low that bar is. But we aren't talking about that. So during the initial proposal stage anyone who volunteers goes in without having to contribute? There's no input from the perspective podliing? How can they have contributed if its a new podling? So fill the bus with anybody who volunteers? That does not sound meritocratic. OK in the immortal words of a friend, I'm going to just be a committer on every podling from now on. -- Best Regards, -- Alex
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Wed, Sep 25, 2013 at 2:45 AM, Alex Karasulu akaras...@apache.org wrote: However, when the CEO of a company adamantly volunteers to mentor a perspective podling, and within 36 hours a few of his employees also volunteer, then people start thinking things. And this is very natural. I'm not saying they're founded or not founded. I'm saying, the probabilities have a suggestive quality, hinting that there may be some back channel coordination activities at play. Such activities are often considered not very sincere. Alex, yes we discussed inside WSO2 that being part of Usergrid would be a good thing for us because we plan to build a product that uses that codebase. As part of that decision we decided that some of our engineers will join the project at this stage. Is there *anything* wrong with that? Exactly what other things are you thinking of when you say people start thinking things? If Usergrid becomes an ASF project we don't even need to contribute *AT ALL* - we can just take the stuff and use it and ship it and sell and make money and party on. Welcome to the ASF and to the Apache license. Wouldn't you really rather have us investing time and money into it too? And w.r.t. mentoring - I'm a member and I have a right to offer to mentor. You could've replied and accepted or said no thanks for reason XYZ. You did neither. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Request to add as contributor to edit the Incubator wiki
My wiki username is Niranjan Karunanandham. Please add as a Contributor with permission to edit the Incubator wiki. Thanks. -- *Niranjan Karunanandham* Senior Software Engineer M: +94 777 749 661 http:///
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
Alex: - only I from WSO2 offered to mentor AFAIK. I hereby withdraw my suggestion. Senaka Fernando, sent a +1 binding vote but he's an ASF Member . Senaka is not even remotely involved with this particular work - we have 250+ people in WSO2. - given your explanation and feeling I will ask the WSO2 employees to withdraw from the offer to be part of this project. Ed: - It was my second mail that suggested a Stratos connection, not the first - There was no intention, whatsoever, to tie Usergrid to Stratos .. Jim said something towards that aspect and I already replied saying of course not. Guys relax. We were not trying to screw your project up. We were trying to be part of the community using an approach that has been used here for a long time .. people volunteer to join the project and get added on as initial committers. I just saw Roy's old mail about piling-on. So let me use my CEO powers to ask my team to withdraw and we will participate thru the list as appropriate (or not). Good luck. Sanjiva. On Wed, Sep 25, 2013 at 4:51 AM, Ed Anuff e...@anuff.com wrote: Sanjiva, two points I'd like to make: 1) You have stated from your first email on this topic that you'd like to introduce a dependency on Stratos. The community doesn't want to do this. It's not a business thing, we just want a minimum footprint architecture based on Tomcat and Cassandra. What has worried me over the last 24 hours is that it looked like you might be trying to stack the vote with enough people to force that issue. I apologize if I'm overreacting or misreading your intention but I didn't really see anything about what you guys were excited about other than that. 2) The code has been ASLv2 for years, even it hasn't been at Apache. No barriers to using it in your project or your company's products. Obviously, it's better if it's all at the ASF, that's why we're here. So, it's unfair for you to play the business intentions card on this. BTW, please note that I'm not talking about Stratos in my previous point as an WSO2 product, if it is one (I'm really not that familiar with your product line), I just mean the Apache Stratos project. 3) I have no disrespect for what you're doing with Stratos. It looks really good and it seems like a project I'd love to contribute to. But just like it would have been uncool if a bunch of people had joined Cassandra while it was in incubator to force it to rebase on CouchDB, it would not be cool if that was your goal here. I thought it was okay for projects to have their own directions. Usually, people join open source projects as committers after having demonstrated they have some interest in what's been done so far. I have a sinking feeling that this could all be just a big misunderstanding, but I'd also be remiss if in the interests of project transparency, I didn't call out these concerns. Thanks, Ed On Tue, Sep 24, 2013 at 5:25 PM, Sanjiva Weerawarana sanj...@wso2.com wrote: I'm writing with my WSO2 hat on: Ed, we didn't participate in this project in Github is that it was a Github project run by Apigee, a competitor of ours. When the project becomes an ASF project, it becomes an *ASF* project and its no longer that of a particular company. We just donated one of our products to form an ASF project (Apache Stratos - Incubating) and we don't look at it as our project at all any more. In the proposal stage of that we tried hard to get other people to sign up to becoming contributors (aka initial committers) because we so absolutely *want* others to commit and write code for it - that's *why* we brought it to ASF. We'd love to get any and all of our competitors to joint Stratos - that means we succeeded in achieving our objectives in bringing it to Apache. The reason so many (aka 3?) from WSO2 have expressed interest in this project is (a) because we want to offer an MBaaS product and we plan to build on this, and (b) because Stratos itself has a set of common services which is not different from the services that this offers to Webapp developers. We try hard to avoid re-writing code (the WSO2 stack uses probably 250 other open source projects) and this seems like a perfect fit. Over time we plan to have probably 5-6 people contributing to this project and building on it for our product as well as for Stratos (as appropriate and as the Stratos community feels its what's right for that project). Being in Apache means we WSO2 feel no risk of collaborating on this project because its going to be (if successful) an *ASF* project owned by no single company. I hope this helps you understand the WSO2 interest. Now with my Apache Member hat on: If your objective of coming to Apache is not to divest control and let a full scale Apache community bloom around it then IMO you should reconsider whether this is the right thing to do for the business interests of Apigee.
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Sep 24, 2013, at 6:58 PM, Alex Karasulu akaras...@apache.org wrote: Put yourself in their shoes for a second? It's a big leap of faith for some projects to come and propose for incubation. You just scared the bejesus out of these guys even if they wanted to work with you. You have also made it clear that the proposed podling will be incredibly careful about who and when they give karma and merit to, potentially scaring off a huge number of potential committers, regardless of affiliation, who have likely gotten the impression that the current committer list consider themselves unimpeachable and a self-sustaining oligarchy. I, for one, did not see any piling on, certainly nothing close to the levels that prompted that discussion from years ago nor that prompted Roy's post, at the start of all this. And FWIW, just because Roy expresses an opinion, it does not make it Biblical; Not that I don't agree with most of what Roy's comment indicates, but also starting off a podling with a heavy-handed control also hamstrings the podling just as badly. It's called moderation. It's actually quite useful. - 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
On Sep 24, 2013, at 7:21 PM, Ed Anuff e...@anuff.com wrote: Sanjiva, two points I'd like to make: 1) You have stated from your first email on this topic that you'd like to introduce a dependency on Stratos. The community doesn't want to do this. Ignoring the whole 'what it is' that the community doesn't want to do (the Stratos thing which I myself addressed), it's useful to recall that we really don't know what the commumity wants or does not want, if by community we mean the Usergrid podling community. Maybe the current Usergrid community doesn't, but that doesn't mean that eventually the community might want otherwise. To be clear, this has nothing to do with the specifics, but rather a reminder that when a project becomes an *Apache* project, the direction, goals and desires of the project come from the community around it, and not from any corporate entity involved in it. With healthy projects, this is done via the PMC, but for podlings, it places a MUCH larger chunk of that responsibility onto the Mentors... These Mentors would step in and prevent, for example, WSO2 employees from pushing a WSO2 agenda, same as they would prevent a similar Apigee effort. Or Oracle. Or whoever. If I could offer one final word of advice: when this proposal is resubmitted (if it is), add some Mentors who fully grok this, and have the guts to back it up and to Do What's Right for the sake of the podling. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept Storm into the Incubator
Doug Cutting wrote: On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: I'd like to call a vote to accept Storm as a new Incubator podling. This passes, with lots of +1 votes (plenty by PMC members) and no -1 votes. Thanks for voting. Doug Someone from the Storm project needs to follow the initial steps: http://incubator.apache.org/clutch.html#h-Project http://incubator.apache.org/guides/mentor.html#Overview -David - 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
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
Re: binary release artifacts
On 24 September 2013 10:05, ant elder ant.el...@gmail.com wrote: I closed LEGAL-178 with the resolution Not A Problem, which is quite different to a resolution of Fixed or Resolved or Answered. From my investigation, things like the text of the AL and various posts in the mailing lists over the years answered the question to my satisfaction. I doubt everyone agrees yet but the answers for me are: - there is no need to vote on the convenience binary artifacts They still have to have NOTICE and LICENSE files, the contents of which must agree with the bits actually included. And Incubator releases must have the DISCLAIMER. - in fact voting on them is a bit pointless as you can't easily verify the contents anyway, and the ASF only does source releases. It's still possible to vote on the NOTICE/LICENSE files. Also, if the binary clearly contains a prohibited dependency it should be possible for reviewers to comment on this. - its ok to have unvoted on convenience binaries in the ASF distribution areas I don't think that's true if my assumptions regarding NL files above are correct. - there is no requirement to have LICENSE/NOTICE files in the root directory of a convenience binary But they should be there (or in META-INF). However i think it would take a fair bit of work to build enough consensus around any documentation update. So just closing LEGAL-178 as Not A Problem seemed much easier now that it seems like no one is insisting any historic artifacts be removed. Happy to continue discussing this as it does seem an interesting topic, but if we do could it be in a new thread not so tied to Chukwa. ...ant On Mon, Sep 23, 2013 at 11:42 PM, Luciano Resende luckbr1...@gmail.comwrote: On Mon, Sep 23, 2013 at 2:23 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Sep 23, 2013 at 1:45 PM, Luciano Resende luckbr1...@gmail.com wrote: Thanks for the summary Marvin, how about we take the chance to update our policy/documentation to clarify the social norm regarding placement of LICENSE/NOTICE in the top level of a distribution but also clarify that, any artifact being release by an Apache Project should be reviewed and voted, as there were some suggestions on this thread that this was not the case. If we can't clarify that on ASF level, at least we can clarify that on the IPMC level. I understand the motivation, but I'm actually in favor of keeping the status quo. As Joe Schaefer pointed out, the VOTE only applies to the canonical source release. Binary artifacts cannot be official releases of the ASF, and the IPMC cannot override that policy. Is there any written policy that states that ? I have never heard that the ASF can't have binary artifacts as official releases ? Also, from Joe's message, I think he was mentioning what is done in the context of HTTPD, not necessarily stating a policy or the social norm here at Apache. Additionally, we still have a lot of work to do to squash licensing documentation bugs in our canonical source releases. When we can't even get our official releases right, I don't think it makes sense to dilute our already thin quality control resources. Marvin Humphrey The issue I see, particularly when evaluating maven based java source releases (no binaries at all), is that the a lot of the dependencies for a project might be transient making much harder and much more work to evaluate a source only release. While reviewing a binary release, you have listed all the binary dependencies and all it's associated license, making the review process much simpler, allowing the reviewer to concentrate on making sure the dependencies are allowed, no specific jars got unaccounted on the license/notice, etc... [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201309.mbox/%3CBF8E0313-15C2-4375-8470-FE0A1DA917C5%40yahoo.com%3E -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Wed, Sep 25, 2013 at 5:57 AM, Jim Jagielski j...@jagunet.com wrote: On Sep 24, 2013, at 6:58 PM, Alex Karasulu akaras...@apache.org wrote: Put yourself in their shoes for a second? It's a big leap of faith for some projects to come and propose for incubation. You just scared the bejesus out of these guys even if they wanted to work with you. You have also made it clear that the proposed podling will be incredibly careful about who and when they give karma and merit to, potentially scaring off a huge number of potential committers, regardless of affiliation, who have likely gotten the impression that the current committer list consider themselves unimpeachable and a self-sustaining oligarchy. That's a big leap and not fair to presume unless you've watched this community in action under incubation. Are they traumatized by this whole mess? Perhaps, but if they let it stigmatize them into not letting any including WSO2 employees rightfully earn their place as committers then they have a problem and should not be here. I, for one, did not see any piling on, certainly nothing close to the levels that prompted that discussion from years ago nor that prompted Roy's post, at the start of all this. And FWIW, just because Roy expresses an opinion, it does not make it Biblical; Not that I don't agree with most of what Roy's comment indicates, but also starting off a podling with a heavy-handed control also hamstrings the podling just as badly. How can you be sure they're going to have heavy-handed control tactics in place?
Re: KEYS files within source archives
On 23 September 2013 21:57, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Sep 18, 2013 at 8:25 PM, Dave Brondsema d...@brondsema.net wrote: Do you have a KEYS file posted somewhere besides within the release? Thanks for a good spot and thoughtful observation, Dave. This is worth discussing. MHO: supplying a KEYS file within the source archive is worthless at best. +1 On Wed, Sep 18, 2013 at 9:50 PM, Ted Dunning ted.dunn...@gmail.com wrote: It is in version control as per custom. Drill uses git so it might not be quite as obvious if you are used to SVN. See, for instance, https://git-wip-us.apache.org/repos/asf?p=incubator-drill.git;a=blob;f=KEYS;h=205469b84b8bda60fcb87486182d4fb7caf0485d;hb=HEAD There may be precedent but it seems to me that including a KEYS file within a source archive shouldn't be considered a best practice. (For the record, so long as the KEYS file is available from somewhere else safe, I don't think the issue blocks Drill's release candidate.) The canonical place for KEYS files is the distribution area. This is automatically archived, so the KEYS file is available for use with archives as well. Now that changes to our distribution area are captured via version control (dist.apache.org), is there any reason to maintain KEYS in the master branch any more? +1 There was talk a while back of transitioning to an LDAP-centric key scheme, but there are flaws with that approach: former RMs who leave the community suddenly causing the key needed for an old release to become unavailable, etc. Indeed. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept Storm into the Incubator
David Crossley wrote: Doug Cutting wrote: On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: I'd like to call a vote to accept Storm as a new Incubator podling. This passes, with lots of +1 votes (plenty by PMC members) and no -1 votes. Thanks for voting. Doug Someone from the Storm project needs to follow the initial steps: http://incubator.apache.org/clutch.html#h-Project http://incubator.apache.org/guides/mentor.html#Overview Argh, do not panic :-) I see now that it is listed. Must have been looking at a stale page. -David - 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
+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
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
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 -- *Niranjan Karunanandham* Senior Software Engineer M: +94 777 749 661 http:///
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
I'd start with Baldr (if a vote passes) to avoid relocation Le 25 sept. 2013 01:18, Olivier Lamy ol...@apache.org a écrit : So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best catch from a unique point of view. I like Baldr very much from that meaning. Lets see if there are more names the next days. Romain Manni-Bucau schrieb: Why not CoMon? Remind commons monitoring, that's fun and closer to english so easier to propagate IMO. Le 20 sept. 2013 12:59, Jean-Baptiste Onofré j...@nanthrax.net a écrit : I like the Apache Leitstand name. Regards JB On 09/20/2013 09:51 AM, Tammo van Lessen wrote: So if German is en vogue already, I'd propose Apache Leitstand [1], which means control room. I think it would make also a nice name when pronounced in English. This of course only works if the GUI is an important piece of the project, which is the case if I understood correctly. Cheers, Tammo [1] http://de.wikipedia.org/wiki/**Leitstand http://de.wikipedia.org/wiki/Leitstand On Fri, Sep 20, 2013 at 3:23 AM, Olivier Lamy ol...@apache.org wrote: So It looks we have more interested folks. But before starting the vote I'd like to find an other name for the project. Someone proposed Baldur or Balder (note, It's a popular germanic god). So as a French guy this proposition looks to be rude for me :-). More seriously, this name doesn't hurt me. If any other propositions, it's time to speak. Cheers -- Olivier On 16 September 2013 08:25, Tammo van Lessen tvanles...@gmail.com wrote: Am 15.09.2013 15:35 schrieb Romain Manni-Bucau rmannibu...@gmail.com : Hi Angular is great but i hope well keep extensibility possible without js. In all case well get at least a thread on it to discuss about the stack we want and well use ;) Looking forward to that discussion ;) I'd prefer progressive enhancement over SPAs in this context as well. Or even http://roca-style.org. Tammo -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache. **orggeneral-h...@incubator.apache.org -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**org general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - 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
Honestly the point that keeps getting missed here is that everything we do at Apache proceeds at a notoriously slow pace so people can adjust accordingly. All things considered, would it be better if Sanjiva and colleagues ASKED to be included in the proposal instead of just adding themselves in an ad hoc fashion? In this case, perhaps so, but not because this is settled law, but because there is significant skepticism and doubt that really doesn't belong in a place like Apache. Too much time is being wasted on appearances and lip service is being paid to folks with well-established levels of trust and expertise on how to collaborate and ultimately govern here. 99% of the time attracting the talent of existing committers is a welcome event, even when one of them is a CEO who is pushing a few people along. This is no big deal folks, and shouldn't be treated like one. Competing corps collaborate every day here on a mutually successful basis, and I fully expect that to continue to be the case with this polling no matter what process is used to setup the initial committer list. On Sep 24, 2013, at 11:51 PM, 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.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 -- *Niranjan Karunanandham* Senior Software Engineer M: +94 777 749 661 http:/// - 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
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 Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
Re: [VOTE]: Release Apache Sentry 1.2.0 incubating (rc0)
Voting is now closed and has passed with the following tally, Binding +1s: Patrick Hunt, Arvind Prabhakar, Andrei Savu Non binding +1s: Xuefu Zhang, Jarcec Cecho, Ashish Paliwal. Thanks to everyone who voted! Shreepadma On Tue, Sep 24, 2013 at 5:11 AM, Andrei Savu as...@apache.org wrote: +1 (binding) -- Andrei Savu On Sun, Sep 22, 2013 at 8:02 AM, Shreepadma Venugopalan shreepa...@apache.org wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
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 Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/ - 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
Hi Joseph, On Wed, Sep 25, 2013 at 10:09 AM, Joseph Schaefer joe_schae...@yahoo.comwrote: Honestly the point that keeps getting missed here is that everything we do at Apache proceeds at a notoriously slow pace so people can adjust accordingly. All things considered, would it be better if Sanjiva and colleagues ASKED to be included in the proposal instead of just adding themselves in an ad hoc fashion? What we did was, just a request to be added as a committer, we never went and added ourselves in an ad hoc manner. In this case, perhaps so, but not because this is settled law, but because there is significant skepticism and doubt that really doesn't belong in a place like Apache. Too much time is being wasted on appearances and lip service is being paid to folks with well-established levels of trust and expertise on how to collaborate and ultimately govern here. 99% of the time attracting the talent of existing committers is a welcome event, even when one of them is a CEO who is pushing a few people along. This is no big deal folks, and shouldn't be treated like one. Competing corps collaborate every day here on a mutually successful basis, and I fully expect that to continue to be the case with this polling no matter what process is used to setup the initial committer list. On Sep 24, 2013, at 11:51 PM, 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:/// - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Nirmal C.S.Nirmal J. Fernando Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
Re: [DISCUSS] Usergrid BaaS Stack for Apache Incubator
On Wed, Sep 25, 2013 at 10:22 AM, Nirmal Fernando nirmal070...@gmail.comwrote: I've written below, wearing my Apache hat. 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. and the below statement, wearing my WSO2 hat. 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 Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/ -- Best Regards, Nirmal C.S.Nirmal J. Fernando Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
