Let's update Hackpad!

Question

Let's update Hackpad!

Opened this issue 8 years ago · 11 comments

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.

Answer 1 · 2016-10-13T05:46:55.000Z

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

Answer 2 · 2016-10-13T13:46:00.000Z

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.

Answer 3 · 2016-11-13T07:16:30.000Z

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.

Answer 4 · 2016-11-13T07:19:20.000Z

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.

Answer 5 · 2017-01-09T11:52:10.000Z

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

Answer 6 · 2017-01-16T05:19:58.000Z

@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

Answer 7 · 2017-01-16T09:15:20.000Z

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

Answer 8 · 2017-01-16T18:14:54.000Z

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

Answer 9 · 2017-01-16T20:29:52.000Z

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

Answer 10 · 2017-01-17T09:17:53.000Z

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.

Answer 11 · 2017-01-18T06:14:06.000Z

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