search

project-iris / iris

Decentralized cloud messaging
iris.karalabe.com
Other
570 stars 32 forks source link

Reorganize project #22

Closed karalabe closed 10 years ago

karalabe commented 10 years ago

Iris is currently organized as one repo for the core messaging middleware and separate repos for the individual language bindings. Adding docker support would introduce yet another repo, and opening up the talks and playground would again add a lot of stuff.

It could be worthwhile to reorganize the iris family of repos into a single large one (i.e. similar to how camlistore is laid out). Proposals are welcome as to how best to this. The important thing would be that individual libs and the likes should be easily and naturally accessible using the core tools of the specific language environments.

thedrow commented 10 years ago

I suggest moving iris and the bindings into an organization repo and mentioning the bindings in the README. I don't really think there's any value in mingling Erlang client code and Go client code and possibly Python client code.

karalabe commented 10 years ago

Suggestion heeded, I've began migrating Iris into organizational accounts on both GtiHub project-iris as well as Twitter @iriscmf. Details and updates at https://groups.google.com/forum/#!topic/project-iris/Nu5I4vaoOrY

karalabe commented 10 years ago

Done.