search

Bridgewater / scala-notebook

Interactive Scala REPL in a browser
Other
741 stars 155 forks source link

Create a Github scala-notebook organization? #57

Open nightscape opened 9 years ago

nightscape commented 9 years ago

Hi all,

I really like scala-notebook, but looking at Github's network graph it looks as if everyone is doing his own thing and there are many long-lived forks whose functionality is not merged back into the main project. The

Also forks like spark-notebook (advanced functionality but specialized to Spark) and alternative projects like ScalaKata or Zeppelin were created which are trying to achieve something similar with slightly different focus.

IMO a lot of energy gets lost by reinventing the wheel that many times instead of reusing a stable basis which scala-notebook could provide.

What do you think of creating a top-level scala-notebook organization on Github where more collaborators can have access rights and maintenance can be distributed on more shoulders?

Best regards Martin

KenCoder commented 9 years ago

Hey Martin

Thanks for the suggestion - that's a pretty good idea. Let me see what I can do.

Ken

On Tue, Apr 7, 2015 at 6:23 AM, Martin Mauch notifications@github.com wrote:

Hi all,

I really like scala-notebook, but looking at Github's network graph it looks as if everyone is doing his own thing and there are many long-lived forks whose functionality is not merged back into the main project. The

Also forks like spark-notebook https://github.com/andypetrella/spark-notebook (advanced functionality but specialized to Spark) and alternative projects like ScalaKata https://github.com/MasseGuillaume/ScalaKata or Zeppelin http://zeppelin-project.org/ were created which are trying to achieve something similar with slightly different focus.

IMO a lot of energy gets lost by reinventing the wheel that many times instead of reusing a stable basis which scala-notebook could provide.

What do you think of creating a top-level scala-notebook organization on Github where more collaborators can have access rights and maintenance can be distributed on more shoulders?

Best regards Martin

— Reply to this email directly or view it on GitHub https://github.com/Bridgewater/scala-notebook/issues/57.