Preserve twemproxy copyright about dynomite

[timiblossom]

We did reedit our tech blog to acknowledge this fact. We still keep the history of commits. We retain all of Twitter's copyrights on all the files that we used as well as other copyrights. We modified the content in a way that best fits us in accordance to licenses.

[fj]

@timiblossom Is there a particular problem with putting that copyright notice in the README, given that you already acknowledged it in the tech blog? It would literally be a one-line addition.

[antirez]

Update: a few minutes after Manju twitted (without complaining) that it's a fork, the Dynomite project authors immediately documented it in the FAQ section of the Wiki: https://github.com/Netflix/dynomite/wiki/FAQ.

EDIT: Btw note that since there is apparently not a License problem at all, since copyright is retained where needed and so forth, there is not a problem. Moreover, while it's nice to acknowledge that a given project is a fork, there are people out there (for example me) that write open source in given licenses exactly in order to allow the code to be reused, with cut&paste, and search&replace and whatever is needed, as soon as the derivative work is ok with respect of the original license.

[timiblossom]

We already put that in the NOTICE file a while ago.

https://github.com/Netflix/dynomite/blob/master/NOTICE

[timiblossom]

@antirez, @aphyr and @fj.

Thanks for the feedback. We actually planed to reach out to all you guys for feedback but apparently, we did not do it soon enough and did not have enough time. To close the loop, Twemproxy is mentioned on our wiki, tech blog, and all copyrights are retained in all files and the NOTICE.

[antirez]

@timiblossom thank you. I'm very exciting about Dynomite, given that Redis Cluster is a master-slave system to have a (semantically very far away) Amazon Dynamo-alike layer is great, so I look forward to your project with great interest. Also it's C so I also hope to find the time to play with it, check the source code, and time permitting, contribute if I can.

[timiblossom]

@antirez please feel free to spam us anytime. Looking forward to your feedback, ideas and contributions if you have the time.

Btw, I did borrow/copy, or whatever term that is, 2 of your files :). I hope you don't mind this late notice.

Redis is an awesome software and I think we, Dynomite team, are lucky with the fact that Redis exists.

[aphyr]

I'm really happy for you to close this if you don't think it's important; it's just a suggestion that folks who read the blog post (prior to this morning's update) and README might assume that this is a de novo Netflix project.

[antirez]

@timiblossom thanks for the kind words! No prob at all with copying my files :-) It's the whole point.

@aphyr I think the suggestion was accepted, so it's closing-after-acting IMHO, not ignoring. The original blog post was updated, and the FAQ that is going to be read by most people that dig a bit more into the project is going to clearly disclose that originally Twemproxy was forked. About the README update, that's author's pick.

[timiblossom]

@aphyr please correct me if I am wrong, but I thought NOTICE file is where we put the references and copyrights. README is the document which contains what a new user should know to get started.

If this tradition is broken and twemproxy is ok to add the acknowledgement about using FreeBSD code as twemproxy's foundation code block as well as others, we will immediately do the same.

[aphyr]

In my experience, including a short copyright section in the README is typical, NOTICE covers in-tree dependencies, and LICENSE handles the top-level project license fine print. That's what Twemproxy and most Clojure/Ruby projects seem to do, but I dunno, maybe conventions are different in the C world! Not an expert here. :)