Thanks David, and the proposal is now on the wiki.
On Thu, Nov 7, 2013 at 12:43 AM, David Crossley wrote:
> Andreas Neumann wrote:
> > Thank you for the feedback, it looks like the name Twill is appealing
> > enough. I will update the proposal with the new name.
> > I would also like to put the
Andreas Neumann wrote:
> Thank you for the feedback, it looks like the name Twill is appealing
> enough. I will update the proposal with the new name.
> I would also like to put the proposal on the incubator wiki (at
> https://wiki.apache.org/incubator/TwillProposal), can you please give me
> the p
Thank you for the feedback, it looks like the name Twill is appealing
enough. I will update the proposal with the new name.
I would also like to put the proposal on the incubator wiki (at
https://wiki.apache.org/incubator/TwillProposal), can you please give me
the privileges? (my user name is Andre
On Tue, Nov 5, 2013 at 6:26 PM, Henry Saputra wrote:
> I think Twill fits well with what Weave project trying to do with
> Hadoop and still in the spirit of the original weave name.
Indeed! Twill is a pretty good name for a project like this.
Thanks,
Roman.
-
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 wrote:
> Regarding the naming issue,
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 discussio
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 sour
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 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.
>
> --
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 wrote:
> Have you guys considered contributing this code directly to Had
Currently Weave has dependencies on libraries like Kafka, logback, asm,
etc, that might not be good idea to added all those as the core Hadoop
dependencies.
Thanks,
Terence
On Sun, Nov 3, 2013 at 11:21 PM, Roman Shaposhnik wrote:
> Have you guys considered contributing this code directly to Ha
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 wrot
On Tue, Oct 29, 2013 at 6:14 PM, Upayavira 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
>>
Random lurker project name suggestion: yarnbomb - see <
http://en.m.wikipedia.org/wiki/Yarn_bombing>
/me relurking
Steve
On Oct 30, 2013 2:00 PM, "Donald Whytock" wrote:
> Knit, crochet, macrame?
>
> Though, honestly, pulling lower-level components together into higher-level
> ones sounds a lit
Knit, crochet, macrame?
Though, honestly, pulling lower-level components together into higher-level
ones sounds a little like granny squares...
Don
On Wed, Oct 30, 2013 at 1:53 AM, Andreas Neumann wrote:
> Pardon my ignorance, I just looked it up and realized that warp and weft
> are indeed r
Marvin,
I agree that building a diverse community and users and committers will the
greatest challenge for Weave (or what it will be named). One of main
motivations for open-sourcing Weave is that it will benefit from the
variety of use cases that will emerge outside of our office, and will
eventu
Pardon my ignorance, I just looked it up and realized that warp and weft
are indeed related to weaving, so they might work.
I do have the impression, though, that most people would associate Warp
with the speed of light and not with weaving.
-Andreas.
On Wed, Oct 30, 2013 at 1:41 AM, Andreas Neum
Thanks for pointing out these similarities; we were not aware of Commons
Weaver. Given that Weaver is a sub-project of Commons, would the similarity
be tolerable? Also, since Weave and Wave are pronounced quite differently,
I am hoping that they are perceived as different enough.
The name Weave is
On Tue, Oct 29, 2013 at 12:53 PM, Andreas Neumann 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.
Leaving aside the naming issues, the proposal is well crafted and
In which case, maybe consider the related words:
Apache Warp
Apache Weft
Just a thought.
On 29 October 2013 22:14, Upayavira 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:
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].
>
> Matt
>
> [1] https://commons.apache.org/proper/commo
Hi,
I am concerned about potential confusion with Apache Commons Weaver [1].
Matt
[1] https://commons.apache.org/proper/commons-weaver/
On Tue, Oct 29, 2013 at 2:53 PM, Andreas Neumann wrote:
> I would like to propose Weave, an abstraction over Apache Hadoop® YARN to
> reduce the complexity
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
22 matches
Mail list logo
