Re: Code import for Apache Accumulo
On 11/4/13, 8:45 PM, Eric Whyne wrote: I just scanned through the ip-clearance page and came away a bit confused after reading this sentence. *This form is not for new projects.* This is for projects and PMCs that have already been created and are receiving a code donation into an existing codebase. We've brought raccumulo out of our internal repos and are now hosting it publicly here. The plan is for this to be it's new home. https://github.com/DataTacticsCorp/raccumulo Uhh... what? I thought this entire discussion was that you wanted raccumulo to be a part of Apache Accumulo. If you're planning to host it on your company's Github page, why are we having this discussion? Developer ICLAs are complete and filed with secretary@apache Data Tactics CCLA is complete and filed with secretary@apache A good goal seems to be having the project included as a contrib project here: http://accumulo.apache.org/contrib.html Again, I'm confused about your Github comment *and* having it be a contrib (sub project) to Accumulo. Some of my most recent questions: Of course, the big question, what is the apache way to do that? We want to do that, we're learning the process and we have more code we want to donate to the community. The Apache Way can be summed up by (taken from http://www.apache.org/foundation/how-it-works.html): - collaborative software development - commercial-friendly standard license - consistently high quality software - respectful, honest, technical-based interaction - faithful implementation of standards - security as a mandatory feature You can think of it as guidelines and best practices designed to help you grow communities around software projects. Is it ip-clearance, since it's a large code donation to an apache project? This is a prerequisite to inclusion into the ASF. Is it incubation as a sub-project? If incubation is the right way, would it preclude initiating the ip-clearance now? Incubation would also require IP clearance (as the ASF would still hold the copyright). Incubation != sub-project, however sub-project sometimes leads into incubation as their own project (e.g. HBase, Hive, Pig, ZooKeeper to name a few). This typically depends on how the top-level project wants to do business. R/ Eric On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: +1 Sent from my iPhone On Nov 4, 2013, at 12:25 PM, Jim Jagielski j...@jagunet.com wrote: +1 On Oct 30, 2013, at 8:22 AM, David Nalley da...@gnsa.us wrote: Hi Josh: Separate repo (or not), release cycles, etc are project decisions. As far as importation of the code; it almost certainly needs to go through IP Clearance. http://incubator.apache.org/ip-clearance/ If you have questions or need help with that process, don't hesitate to ask. --David On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser els...@apache.org wrote: Hi, Over at Apache Accumulo, we just got a nice bit of code that integrates the R programming language (via RStudio) with Accumulo. This was done completely by the community (non-committers) and we're trying to figure out what's best for it and where it can live. The general consensus for us is that we would want to import it into it's own repository (treat it as a contrib-project) since Accumulo has no need to depend on it and thus it can be versioned at its own pace. The contributors are currently working on ICLA/CCLA forms, but I wanted to see what else we (the Accumulo PMC) would need to do to import this code. Thanks! - Josh - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code import for Apache Accumulo
I just scanned through the ip-clearance page and came away a bit confused after reading this sentence. *This form is not for new projects.* This is for projects and PMCs that have already been created and are receiving a code donation into an existing codebase. We've brought raccumulo out of our internal repos and are now hosting it publicly here. The plan is for this to be it's new home. https://github.com/DataTacticsCorp/raccumulo Developer ICLAs are complete and filed with secretary@apache Data Tactics CCLA is complete and filed with secretary@apache A good goal seems to be having the project included as a contrib project here: http://accumulo.apache.org/contrib.html Some of my most recent questions: Of course, the big question, what is the apache way to do that? We want to do that, we're learning the process and we have more code we want to donate to the community. Is it ip-clearance, since it's a large code donation to an apache project? Is it incubation as a sub-project? If incubation is the right way, would it preclude initiating the ip-clearance now? R/ Eric On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: +1 Sent from my iPhone On Nov 4, 2013, at 12:25 PM, Jim Jagielski j...@jagunet.com wrote: +1 On Oct 30, 2013, at 8:22 AM, David Nalley da...@gnsa.us wrote: Hi Josh: Separate repo (or not), release cycles, etc are project decisions. As far as importation of the code; it almost certainly needs to go through IP Clearance. http://incubator.apache.org/ip-clearance/ If you have questions or need help with that process, don't hesitate to ask. --David On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser els...@apache.org wrote: Hi, Over at Apache Accumulo, we just got a nice bit of code that integrates the R programming language (via RStudio) with Accumulo. This was done completely by the community (non-committers) and we're trying to figure out what's best for it and where it can live. The general consensus for us is that we would want to import it into it's own repository (treat it as a contrib-project) since Accumulo has no need to depend on it and thus it can be versioned at its own pace. The contributors are currently working on ICLA/CCLA forms, but I wanted to see what else we (the Accumulo PMC) would need to do to import this code. Thanks! - Josh - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code import for Apache Accumulo
If we eventually get the code hosted on https://git-wip-us.apache.org/repos/asf it should be no problem to propagate updates to or from the github page, depending on how things worked out. This model seemed to make sense at the time. I had noticed that the accumulo core was doing the same thing. This also had the added benefit of having a place where the code could be subject to public scrutiny and version controlled as we got it to an acceptable state. I noticed some notes in the apache documents about coding standards and there was the whole licensing concern etc... There has already been some modification of the code since Aaron uploaded the .tgz here https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and adding documentation. Sub-project is identified as an incubation graduation status. I think in accumulo project vocabulary sub-projects are contrib projects? Am I right to think this? I think you had offered to help kick off incubation. Is that the right path to a contrib project or is there a different way to get there from here? R/ Eric On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser josh.el...@gmail.com wrote: On 11/4/13, 8:45 PM, Eric Whyne wrote: I just scanned through the ip-clearance page and came away a bit confused after reading this sentence. *This form is not for new projects.* This is for projects and PMCs that have already been created and are receiving a code donation into an existing codebase. We've brought raccumulo out of our internal repos and are now hosting it publicly here. The plan is for this to be it's new home. https://github.com/DataTacticsCorp/raccumulo Uhh... what? I thought this entire discussion was that you wanted raccumulo to be a part of Apache Accumulo. If you're planning to host it on your company's Github page, why are we having this discussion? Developer ICLAs are complete and filed with secretary@apache Data Tactics CCLA is complete and filed with secretary@apache A good goal seems to be having the project included as a contrib project here: http://accumulo.apache.org/contrib.html Again, I'm confused about your Github comment *and* having it be a contrib (sub project) to Accumulo. Some of my most recent questions: Of course, the big question, what is the apache way to do that? We want to do that, we're learning the process and we have more code we want to donate to the community. The Apache Way can be summed up by (taken from http://www.apache.org/ foundation/how-it-works.html): - collaborative software development - commercial-friendly standard license - consistently high quality software - respectful, honest, technical-based interaction - faithful implementation of standards - security as a mandatory feature You can think of it as guidelines and best practices designed to help you grow communities around software projects. Is it ip-clearance, since it's a large code donation to an apache project? This is a prerequisite to inclusion into the ASF. Is it incubation as a sub-project? If incubation is the right way, would it preclude initiating the ip-clearance now? Incubation would also require IP clearance (as the ASF would still hold the copyright). Incubation != sub-project, however sub-project sometimes leads into incubation as their own project (e.g. HBase, Hive, Pig, ZooKeeper to name a few). This typically depends on how the top-level project wants to do business. R/ Eric On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: +1 Sent from my iPhone On Nov 4, 2013, at 12:25 PM, Jim Jagielski j...@jagunet.com wrote: +1 On Oct 30, 2013, at 8:22 AM, David Nalley da...@gnsa.us wrote: Hi Josh: Separate repo (or not), release cycles, etc are project decisions. As far as importation of the code; it almost certainly needs to go through IP Clearance. http://incubator.apache.org/ip-clearance/ If you have questions or need help with that process, don't hesitate to ask. --David On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser els...@apache.org wrote: Hi, Over at Apache Accumulo, we just got a nice bit of code that integrates the R programming language (via RStudio) with Accumulo. This was done completely by the community (non-committers) and we're trying to figure out what's best for it and where it can live. The general consensus for us is that we would want to import it into it's own repository (treat it as a contrib-project) since Accumulo has no need to depend on it and thus it can be versioned at its own pace. The contributors are currently working on ICLA/CCLA forms, but I wanted to see what else we (the Accumulo PMC) would need to do to import this code. Thanks! - Josh - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Tajo-0.2-incubating RC3
+1 (binding) Congrats! On Mon, Nov 4, 2013 at 9:16 PM, Hyunsik Choi hyun...@apache.org wrote: Hi folks This is the fourth candidate for Apache Tajo-0.2-incubating, and it is also the first official release for Tajo. The PPMC vote [1][2][3] was passed with 3 binding +4s and no -1. Release git tag is at: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc3 Release notes is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/RELEASE_NOTES.html Release artifacts, signatures, md5, and sha1 are at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/ and the KEYS file containing the PGP keys used to sign the release can currently be found at: http://people.apache.org/keys/group/tajo.asc The RAT report is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/rat.txt Please vote [ ] +1 release this package as apache-tajo-0.2-incubating [ ] -1 do not release this package because ... Thanks, Hyunsik Choi [1] http://markmail.org/message/cvwzgdfkq2zfmmbo [2] http://markmail.org/message/crhbpagwo3pvm4et [3] http://markmail.org/message/kofx3nfjzcr7chqu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache VXQuery Incubating 0.2 (RC4)
On Oct 30, 2013, at 10:29 PM, Till Westmann wrote: Hi Dave, On Oct 11, 2013, at 6:08 AM, Dave Fisher dave2w...@comcast.net wrote: On Oct 11, 2013, at 2:03 AM, ant elder wrote: Vinayak, the release does not need to be redone yet. If it really looks like this will hold up getting another vote raise a ASF legal JIRA ( https://issues.apache.org/jira/browse/LEGAL) asking to confirm that ODC-BY is ok. It holds me up. Even though https://issues.apache.org/jira/browse/LEGAL-182 is not yet closed, both Craig and Chris agreed on the JIRA that it would be acceptable to include the database in its current use in an incubating release of Apache VXQuery. If this is acceptable for you as well and if you would vote +1 on this RC, we would be able to finally get the first release out. No, I am looking for resolution, Craig and Chris are also able to VOTE here at the IPMC - the release is not large and would not take them long. If you think it is not acceptable in its current state, would you be comfortable voting on a new RC that does not contain the file? Yes, I would, definitely. I should be able to find the time within a 72 hour window of a VOTE start. Regards, Dave Thanks, Till On Fri, Oct 11, 2013 at 6:39 AM, Vinayak Borkar vinay...@gmail.com wrote: Hi Dave, Before I can VOTE I have questions. (1) What is the following file? A apache-vxquery-0.2-incubating/**vxquery-core/src/test/** resources/documents/dblp.xml.**gz Am I correct that this shows up in your LICENSE as: ==**==** === The DBLP (http://dblp.uni-trier.de/db/) database in vxquery-core/src/test/**resources/documents/dblp.xml.**gz can be used under the terms and conditions of the Open Data Commons Attribution License (ODC-BY 1.0). The full ODC-BY 1.0 license text is avaialable at http://opendatacommons.org/**licenses/by/1.0/http://opendatacommons.org/licenses/by/1.0/ I don't see this license on http://www.apache.org/legal/**3party.htmlhttp://www.apache.org/legal/3party.html Can you show me a reference from the Legal Discuss list: http://www.apache.org/**foundation/mailinglists.html#**foundation-legalhttp://www.apache.org/foundation/mailinglists.html#foundation-legalthat puts this in Class A? I think that this is required otherwise the project will need to find a better way of packaging this source dependency. The file is a standard XML file that is used for unit testing the parsing capabilities of the software. It is not critical to the release itself. Just to confirm, if there is no such mention on the mailing lists, do we have to create a new release without this dependency? Thanks, Vinayak (2) Does the podling intend in this VOTE to authorize the release of the convenience binary artifacts that are also in the directory? I see from discussions on the project that this is NOT intended. At least that is how I view this email. [2] [2] http://mail-archives.apache.**org/mod_mbox/incubator-** vxquery-dev/201310.mbox/%**3C1591541861.240305.** 1381162348269.open-xchange%**40email.1und1.de%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-vxquery-dev/201310.mbox/%3C1591541861.240305.1381162348269.open-xchange%40email.1und1.de%3E Regards, Dave On Oct 7, 2013, at 8:59 AM, Till wrote: Please verify and vote on the fourth release candidate for our first release apache-vxquery-0.2-incubating. The tag to be voted on is https://svn.apache.org/repos/**asf/incubator/vxquery/tags/** apache-vxquery-0.2-incubating/https://svn.apache.org/repos/asf/incubator/vxquery/tags/apache-vxquery-0.2-incubating/ at revision 1528941. The artifacts, signatures, md5, and sha1 are at: https://repository.apache.org/**content/repositories/** orgapachevxquery-128/org/**apache/vxquery/apache-vxquery/** 0.2-incubating/apache-vxquery-**0.2-incubating-source-release.**ziphttps://repository.apache.org/content/repositories/orgapachevxquery-128/org/apache/vxquery/apache-vxquery/0.2-incubating/apache-vxquery-0.2-incubating-source-release.zip https://repository.apache.org/**content/repositories/** orgapachevxquery-128/org/**apache/vxquery/apache-vxquery/** 0.2-incubating/apache-vxquery-**0.2-incubating-source-release.**zip.aschttps://repository.apache.org/content/repositories/orgapachevxquery-128/org/apache/vxquery/apache-vxquery/0.2-incubating/apache-vxquery-0.2-incubating-source-release.zip.asc https://repository.apache.org/**content/repositories/** orgapachevxquery-128/org/**apache/vxquery/apache-vxquery/** 0.2-incubating/apache-vxquery-**0.2-incubating-source-release.**zip.md5https://repository.apache.org/content/repositories/orgapachevxquery-128/org/apache/vxquery/apache-vxquery/0.2-incubating/apache-vxquery-0.2-incubating-source-release.zip.md5 https://repository.apache.org/**content/repositories/**
Re: [PROPOSAL] Weave for Apache Incubator
Hi Andrei, thanks for offering, we are happy about any help we can get. On Mon, Nov 4, 2013 at 10:43 AM, Andrei Savu as...@apache.org wrote: IMO it's a good idea to keep this a separate project - the same way we have Curator for ZooKeeper. If you are looking for one more mentor I'm happy to help. -- Andrei Savu On Sun, Nov 3, 2013 at 11:21 PM, Roman Shaposhnik r...@apache.org wrote: Have you guys considered contributing this code directly to Hadoop? From what you are describing it sounds like a developer friendly library wrapped around YARN (along the lines of kitten: https://github.com/jwills/kitten). Thanks, Roman. On Tue, Oct 29, 2013 at 12:53 PM, Andreas Neumann a...@apache.org wrote: I would like to propose Weave, an abstraction over Apache Hadoop® YARN to reduce the complexity of developing distributed applications, as an Apache Incubator podling. The proposal is included in plain text. I would also like to put this on the wiki, but I appear to lack privileges to create pages. What do I need to do to get permission? -Andreas. Abstract Weave is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. Proposal Weave is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Weave also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. Background == Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Weave is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Weave, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Weave also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Weave is not a replacement for YARN, it’s a framework that operates on top of YARN. Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Weave’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Weave as an Apache project makes sense because Weave is a framework built on top of YARN, and Weave uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). Current Status == Weave was initially developed at Continuuity. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository. Meritocracy --- Our intent with this incubator proposal is to start building a diverse developer community around Weave following the Apache meritocracy model. Since Weave was initially developed in early 2013, we have had fast adoption and contributions within Continuuity. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. Community - Weave is currently being used internally at Continuuity and is at the core of our products. We hope to extend our contributor base significantly and we will invite all who are interested in simplifying the development of distributed applications to participate. Core Developers
Re: [PROPOSAL] Weave for Apache Incubator
Regarding the naming issue, we understand that Weave may be problematic, so we did a little bit of searching for a new name. Here is a list of name candidates in order of our preference: - Tartan - Sisal - Twill Do these ring a bell or raise concerns? A quick search did not bring up any open source projects named Tartan, but there appear to be some non-Apache projects named Sisal and Twill. I am not sure how unique a project name has to be, it is really hard to find something that does not exist at all... On Wed, Oct 30, 2013 at 11:28 AM, David Nalley da...@gnsa.us wrote: On Tue, Oct 29, 2013 at 6:14 PM, Upayavira u...@odoko.co.uk wrote: And Apache Wave too (which is what I first saw before I read the title more carefully). Upayavira On Tue, Oct 29, 2013, at 09:12 PM, Matt Benson wrote: Hi, I am concerned about potential confusion with Apache Commons Weaver [1]. So it might also be a trademark related issue. Weave has a TM registration pending from Intuit in the software space. There's also OIC Weave - which is data visualization software. No judgement - just things to consider and weigh (and that will need to be dealt with when you handle the podling name search) --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Weave for Apache Incubator
I mentioned this offline to others too. We've had lots of discussions in the past about contrib projects overall in Hadoop and we moved away from there. The same started happening with YARN, and we took a stand that YARN shouldn't run into the same umbrella issue. You can see the JIRA discussions on Paas On YARN etc for more context. As for Weave, it represents a good programming model (threads) alongside MR and so deserves its own home IMO. Thanks, +Vinod On Nov 3, 2013, at 11:21 PM, Roman Shaposhnik wrote: Have you guys considered contributing this code directly to Hadoop? From what you are describing it sounds like a developer friendly library wrapped around YARN (along the lines of kitten: https://github.com/jwills/kitten). Thanks, Roman. On Tue, Oct 29, 2013 at 12:53 PM, Andreas Neumann a...@apache.org wrote: I would like to propose Weave, an abstraction over Apache Hadoop® YARN to reduce the complexity of developing distributed applications, as an Apache Incubator podling. The proposal is included in plain text. I would also like to put this on the wiki, but I appear to lack privileges to create pages. What do I need to do to get permission? -Andreas. Abstract Weave is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. Proposal Weave is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Weave also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. Background == Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Weave is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Weave, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Weave also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Weave is not a replacement for YARN, it’s a framework that operates on top of YARN. Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Weave’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Weave as an Apache project makes sense because Weave is a framework built on top of YARN, and Weave uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). Current Status == Weave was initially developed at Continuuity. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository. Meritocracy --- Our intent with this incubator proposal is to start building a diverse developer community around Weave following the Apache meritocracy model. Since Weave was initially developed in early 2013, we have had fast adoption and contributions within Continuuity. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. Community - Weave is currently being used internally at Continuuity and is at the core of our products. We hope to extend our contributor base significantly and we will invite all who are interested in simplifying the development of distributed applications to participate. Core Developers --- Weave is currently being developed by five engineers at Continuuity: Terence
Wiki access
I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com
Re: Wiki access
P. Taylor Goetz wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. As explained at the front page top-right, you need to tell us your Wiki username. http://wiki.apache.org/incubator/ -David Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
What is your Wiki login name? On 6 November 2013 00:55, P. Taylor Goetz ptgo...@gmail.com wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
P. Taylor Goetz Thanks and my apologies for being a little thick regarding the right process. I'm kind of juggling eggs right now... P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com On Nov 5, 2013, at 8:01 PM, sebb seb...@gmail.com wrote: What is your Wiki login name? On 6 November 2013 00:55, P. Taylor Goetz ptgo...@gmail.com wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
P. Taylor Goetz wrote: P. Taylor Goetz Thanks and my apologies for being a little thick regarding the right process. I'm kind of juggling eggs right now... Okay, done now. I did not realise that spaces were allowed. -David P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com On Nov 5, 2013, at 8:01 PM, sebb seb...@gmail.com wrote: What is your Wiki login name? On 6 November 2013 00:55, P. Taylor Goetz ptgo...@gmail.com wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Weave for Apache Incubator
I think Twill fits well with what Weave project trying to do with Hadoop and still in the spirit of the original weave name. Other than name, the proposal looks good. Looking forward to the VOTE thread. - Henry On Tue, Nov 5, 2013 at 3:18 PM, Andreas Neumann a...@apache.org wrote: Regarding the naming issue, we understand that Weave may be problematic, so we did a little bit of searching for a new name. Here is a list of name candidates in order of our preference: - Tartan - Sisal - Twill Do these ring a bell or raise concerns? A quick search did not bring up any open source projects named Tartan, but there appear to be some non-Apache projects named Sisal and Twill. I am not sure how unique a project name has to be, it is really hard to find something that does not exist at all... On Wed, Oct 30, 2013 at 11:28 AM, David Nalley da...@gnsa.us wrote: On Tue, Oct 29, 2013 at 6:14 PM, Upayavira u...@odoko.co.uk wrote: And Apache Wave too (which is what I first saw before I read the title more carefully). Upayavira On Tue, Oct 29, 2013, at 09:12 PM, Matt Benson wrote: Hi, I am concerned about potential confusion with Apache Commons Weaver [1]. So it might also be a trademark related issue. Weave has a TM registration pending from Intuit in the software space. There's also OIC Weave - which is data visualization software. No judgement - just things to consider and weigh (and that will need to be dealt with when you handle the podling name search) --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
