Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's update Hackpad! #43

Open
nikosprodro opened this issue Mar 30, 2017 · 12 comments
Open

Let's update Hackpad! #43

nikosprodro opened this issue Mar 30, 2017 · 12 comments

Comments

@nikosprodro
Copy link
Collaborator

Issue by leandermelms
Mon Sep 19 09:36:06 2016
Originally opened as dropbox/hackpad#62


Hi,
Hackpad is great but needs some polishing for performance and security reasons.
I started to update some of the dependencies. Most of them where simple replacements without any modifications needed.
I recently tried to update jetty (from 6 to 9). Jetty 9 offers Http/2 support (up to x15 performance increase!) and it's been roughly 7 years since jetty 6. For this, major modifications are necessary as jetty has evolved / changed significantly. As one might guess, jetty deeply used in almost all AppJet components. Some functionality needs to be redesigned as jetty has dropped depreciated classes AppJet uses heavily.

Is anyone interested in collaborating on this? I'm happy to exchange progess.

@nikosprodro
Copy link
Collaborator Author

Comment by andreabedini
Thu Oct 13 05:46:55 2016


@leandermelms do you have a fork you are working on?

@nikosprodro
Copy link
Collaborator Author

Comment by leandermelms
Thu Oct 13 13:46:00 2016


Yes, but unfortunately I've scheduled updating dependencies which require greater effort until I'm satisfied with the front-end implementation and the JS code, talking to the Scala backend.

IMHO updating Jetty and Solr is important though, since each of them are ~ 5 years old. Jetty 6 is still considered stable. However, HTTP/2 support would be very desirable to have.

Please let me know if you're interested in working on this.

@nikosprodro
Copy link
Collaborator Author

Comment by ztl8702
Sun Nov 13 07:16:30 2016


I am interested. Hackpad has a better UX than out-of-the-box etherpad. For some reasons I cannot use hackpad in some environments and have to use self-hosted solutions. Having used Hackpad, etherpad looked primitive to me.

However, Hackpad seems much harder to setup than etherpad. I am thinking maybe we can back-port some parts of Hackpad to etherpad and contribute to the etherpad community as a whole.

@nikosprodro
Copy link
Collaborator Author

Comment by ztl8702
Sun Nov 13 07:19:20 2016


Or maybe they have made significant changes outside etherpad and it is no longer relavent to back-port to etherpad. I am not sure. I need some help in understand the architecture of Hackpad.

@nikosprodro
Copy link
Collaborator Author

Comment by dokterbob
Mon Jan 9 11:52:10 2017


@ztl8702 @leandermelms @andreabedini We just created a community fork, see #67. Hope you'll join our efforts!

@nikosprodro
Copy link
Collaborator Author

Comment by nzinfo
Mon Jan 16 05:19:58 2017


@ALL @ztl8702 @leandermelms @andreabedini @dokterbob I forked Hackpad, and due to etherpad has move to node.js platform, become etherpad-lite. I think it's hard to put the changes back.
And the Hackpad's tech stack is quite out-of-date. So my plan is moving the js code into modern node.js style (Reactlize, etc ), and re-implementing all the API and URL routings in python

@nikosprodro
Copy link
Collaborator Author

Comment by nzinfo
Mon Jan 16 09:15:20 2017


My Fork https://github.com/coreseekdev/librepad/

@nikosprodro
Copy link
Collaborator Author

Comment by dokterbob
Mon Jan 16 18:14:54 2017


Great work!

Would you be interested in joining our efforts at https://github.com/whackpad/whackpad?

@nikosprodro
Copy link
Collaborator Author

Comment by nzinfo
Mon Jan 16 20:29:52 2017


@dokterbob What changes have been made in Whackpad by now ?

@nikosprodro
Copy link
Collaborator Author

Comment by dokterbob
Tue Jan 17 09:17:53 2017


Practically none, we’ve just changed the name and updated the README a bit. Plus some tickets have been made.

I guess the main difference (with the original hackpad) is it’s meant to be a community effort in that we hope to move forward with some kind of consensus on most decisions (within reasonability, i.e. not taking a lot of time in discussions).

Maybe you could join us on #hackpad at Freenode or #hackpad:chat.weho.st on Matrix/Riot to discuss details.

@nikosprodro
Copy link
Collaborator Author

Comment by nzinfo
Wed Jan 18 06:14:06 2017


Thank you for your invitation, now a days, I'm engaged with hacking Snabb. :) So, I'm afraid that I might have no time dissus it on irc, etc. My plan about Librepad/Hackpad has listed in README.md, It will take 1~2 month or even more.
If you decided to re-write the whole backend ( I'm not a JAVA guy, I love to write py/lua/cpp/go ), I'll join the project.

BTW, You can take my changes :)

Best Wishes,
Li

@pors
Copy link
Contributor

pors commented Jun 11, 2017

@leandermelms @ztl8702 we are actively developing hackpad on this repo now https://github.com/hackpad/hackpad/. We are going for the long run here, and if you would like to join our efforts that would be great!

Just leave a comment here and we can discuss next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants