Host our own Etherpad instance

[RichardLitt]

Each week, I create the sprint issue, and manually create Etherpads by opening links in the issue, and then copying in and editing the template for these notes manually. This takes time, and it could all hypothetically be automated.

To automate this process so that we can do it in one click each week, removing the onus on me to do it, we should run our own Etherpad instance and allow API usage. The repo for this is here: https://github.com/ether/etherpad-lite

Ideally, of course, we would run Etherpad on IPFS. But, for now, running our own etherpad gateway might be smart. This also reduces our dependance on Mozilla's.

[flyingzumwalt]

👍

[daviddias]

Now that we moved to hackpad, can we close this?

Having an hackpad/etherpad on IPFS sounds like a great idea and should be added to ipfs/notes

[daviddias]

Actually it is mentioned here: ipfs/notes#40 (comment) in the CRDT discussion, but it could use its own issue.

[RichardLitt]

No longer needed as we use HackMD. Closing this; I opened ipfs/notes#190 to log potential work here in the future.