You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 [email protected]
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
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 #57.
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
The text was updated successfully, but these errors were encountered: