Are you all sure this is how we want to run an open source project?
I can say I wrote this code but it doesn't make it right.
When we contribute code to the open source community we prefer the better
good then our own private ego.

I have been working with the zeppelin project since its beginning and I
trust the way it is managed.
R interpreter is a great contribution but does not worth trashing the
project or our community.

I hope we find a way to take words back and act as we are expected of.
On Mon, 16 Nov 2015 at 22:22 elbamos <g...@git.apache.org> wrote:

> Github user elbamos commented on the pull request:
>
>
> https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157158373
>
>     To anyone who may be coming here from today's blog post and confused
> by these comments about the current status:
>
>     The RInterpreter for zeppelin works fine with Spark 1.4.x, and should
> compile straight out of the box.
>     The travis build is failing because of bugs in other parts of the way
> Zeppelin interfaces with Spark.
>     I expect to be pushing a new revision of the Interpreter, with Spark
> 1.5.x support, in the next day or so.
>
>     Why the comments about the PR?  Yesterday I discovered that someone
> (Felix Cheung) had been demo'ing this code to R user groups on the West
> Coast, claiming to have done the work. One of the lead Zeppelin developers
> was present for at least one of these demos.
>
>     Short version of the backstory:  When I'd announced the project to the
> Zeppelin developer's list, Felix had pleaded to participate. I said "ok,"
> but Felix failed to do any work.  Not a single line of code.  When I told
> him I was making the PR without him, he threatened that if he was not given
> credit he would sabotage the project by claiming that the code had been
> stolen from him.  He carried-through with his threat, and I had to produce
> chat logs and e-mail chains to demonstrate that he was lying.
> Unfortunately, he's apparently also friends with at least one of the lead
> Zeppelin developers.
>
>     In any event, I will be deciding after the next push how I will move
> forward.
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Reply via email to