incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Neumann <>
Subject Re: [VOTE] Accept Slider into the incubator
Date Tue, 29 Apr 2014 07:01:48 GMT
Andrew, Roman, Nick,

thanks for your insights. I can see that some competition within the
incubator can help with advancement of technology, and who knows, Slider
and Twill may have completely different motivations and focus on distinct
aspects of the same problem. I also agree that Slider can help existing
projects - such as HBase - to run over YARN sooner than Twill would -
Slider's goal is to make exactly that possible, whereas Twill's goal is a
bit more generic: to ease adoption of YARN for any type of application, be
it an existing one or yet to be developed. Building that true common
platform will sure take longer, and in the mean time I can see the value
that Slider will provide.

Now I am not sure what you mean by personality, Nick? Being a platform vs
being a solution for an immediate need? If that really is the distinction,
then they are different enough to justify separate projects.


On Sun, Apr 27, 2014 at 1:02 PM, Nick Burch <> wrote:

> On Sun, 27 Apr 2014, Roman Shaposhnik wrote:
>> That's actually a great point. The way I look at it is this: there's
>> nothing wrong with an alternative healthy community, but it has to be
>> healthy. So I guess what I'm really saying is this: it may behove us to
>> double click into the health of community for these types of overlapping
>> projects when it is time for them to graduate.
> One thing I'd also say - for new potential community members, there ought
> not to be confusion. I don't personally see a problem with us having
> multiple projects in one space, as long as we can explain to new community
> members which one they should pick for their needs. "We have two Java
> libraries for Fooing a Bar" isn't great. "If you need to Foo a Bar, we've
> Apache CoffeeBar in Java, or Apache SnakeBar in Python" does help people
> pick. "If you need to Foo your Bar, we've Apache SnapBar for low latency
> Fooing, or Apache BigSuperBar for highly scalable and fault tolerant
> batching Fooing" is good too. In both cases, there's a clear distinction
> for new people to work out which is right for them, so they can join the
> right community, or even go elsewhere if they need to.
> However, I worry if there are two related projects who disagree on
> personality rather than technology or architecture...
> Nick
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message