Forking them Hackpads! about hackpad HOT 18 CLOSED

@dokterbob I am not aware there is a trademark for the name hackpad, see http://www.wipo.int/branddb/en/. Also, it seems dropbox is not really interested in this project anymore.

I propose to fork the project to this organization I created https://github.com/hackpad and all who are interested in contributing can be added to it.

Is there a better way to talk to you than in this issue? :) Maybe we can set up a slack or irc channel?

from hackpad.

Sure let's start with Jetty and Solr issues, and whatever bugs there might be. At least with API:s and auth there was some issues that would need to be solved to implement data import/export.

And sure, when we have a fork there should be a separate discussion about whatever additional features people might come up with. We might even expect them to start turning up once the master is maintained once again.

from hackpad.

Ok, so not much response so far. I'd like to take some action anyways. ;)

Unless I get a response by, let's say, tomorrow, I'll create a GH organization for 'whackpad' and will fork hackpad into it. I'll invite @leandermelms, @jaakkokorhonen and @ToniIltanen as maintainers. I will make sure to create an issue here to redirect potential contributors, as Dropbox seems to have completely taken their hands off this project.

I might or might not:

• Do a search & replace in the hackpad source with whackpad.
• Try and get the site running
• Reserve an appropriate domain name
• Copy issues to the new repository

If you have some remarks or comments relating to the above, let me know.

from hackpad.

I'm willing to participate, if we can gather up a community for this!

from hackpad.

Yes, I'm in too. +1 for OpenPad. And if someone's interested in

• voting functionality, that would be cool.

from hackpad.

Thanks for the feedback so far!

@jaakkokorhonen What do you mean with voting functionality? Like polls? Or for collaboration in the development team (in which case I recommend Loomio.

from hackpad.

@dokterbob not Loomio. Something more agile, like a "+1", "reaction" or "thumbs up" for prioritizing proposals or proposed tasks.

from hackpad.

• Passport.js based auth strategies, similar to HackMD's implementation of it (easy to add a new auth strategy, or use multiple auth protocols in paraller)

from hackpad.

I think just maintaining the project should be a primary focus and adding new features should come secondary. I would like to propose to keep this discussion to how, whether and who would maintain a community fork, rather than discussing the roadmap and features (but feel free to create seperate issues for those!).

from hackpad.

@dokterbob While implementing data import/export to/from Hackpad, where would you prefer to write them, to git?

from hackpad.

@jaakkokorhonen Some kind of JSON download of the user data seems the right way here. First implement import/export in the fork and then write imort from Hackpad.

from hackpad.

As already mentioned in #62 one of the top priorities should be updating Solr and Jetty. Solr is now a standalone service and should be deintegrated from Hackpads core.

I've already started updating Jetty but the time I can invest is limited. I'm happy to share all insights gained in the architecture of hackpad. I suggest to create a jetty9 branch to begin with.

from hackpad.

+1 for whackpad

from hackpad.

@dokterbob Sounds good!

from hackpad.

@dokterbob With Stek.io we would like to play a part in the future of Hackpad because we love the tool and it doesn't deserve to die! So let's see how we can work together! One thing about the name: I think it would be a shame to not use the original Hackpad name and don't see a reason not to do it. Hackpad is open source so the idea is to start using it. And with the name, i assume. Grts

from hackpad.

from hackpad.

@pors I am pretty sure Hackpad would be legally considered a trademark by Dropbox, even though they didn't register it. This means legal issues might force us to change the project's name at a later stage. It also means that Dropbox's hackpad.com will be running an older, inferior, version of a project with the same name - which is out of our control. Have a look at https://en.wikipedia.org/wiki/Unregistered_trademark

Looking at the history of several other FOSS projects that forked from their trademarked counterparts, you'll see that name changing towards a 'community owned' name is a common pattern. I'm talking LibreOffice, Chromium, MariaDB to name a few.

Good idea about communication. I've just created #hackpad on FreeNode (IRC) and #hackpad:chat.weho.st (recommend the latter, check out https://riot.im/). Hope to meet you all there.

from hackpad.

The fork has been made, recreated all migration-specific points as issues there. Let's continue our work and discussion there!

https://github.com/whackpad/whackpad

from hackpad.