Move repositories from @haadcode to @orbitdb #4
Description
In a private discussion, we went over these repositories and wrote some brief notes on these repositories under @haadcode's namespace. There are a few repositories in @haadcode that might be better placed in @orbitdb, a few which would be better off deleted or archived, and some more which can just stay where they are.
@haadcode: Can you take a look at these, perform the appropriate action, and then check them off this list and close this issue, please?
Move these to @orbitdb:
- example-orbitdb-webpack - An example how to use orbitdb through webpack.
- ipfs-post - Datastructure for orbit-chat post. Rename, too.
- orbit-db-channelstore - Prototype of channelstore.
- orbit-db-http-server
Archive
Please archive these repositories. You can do this in the settings. Alternatively, delete them. We had marked them for deletion, but I don't think that's actually necessary; archiving them clearly shows they're not maintained or relevant, and keeps a track record in case you get subpoenaed by the Open Source police.
Leave alone or undecided
We didn't decide what to do with these. Check these off when you've gone through and done the appropriate thing.
- go-ipfs-log - Prototype, long time ago, not finished.
@kexhas some go-ipfs stuff, too. Keep. Contact Kex. - immutabledb - A way of doing a datastore, to use everything. Can store quite a bit of things. Instead of using IPFS, use anything else.
- logplease
- planet-express - Twitter prototype. May have some screenshots. Kind of cool.
- pouchdb-adapter-orbitdb - @haadcode will look into it.
- proto2 - Visualization of orbitdb's dataflow and functions that may not work. Out of date.
And, in the IPFS Shipyard:
- ipfs-pubsub-peer-monitor - Monitor peers joining and leaving an IPFS PubSub topic.
When you've done this, ping me please, as we should add the moved repositories to the directory in #3.