Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add license #45

Merged
merged 12 commits into from
May 29, 2022
Merged

Add license #45

merged 12 commits into from
May 29, 2022

Conversation

odedponcz
Copy link
Collaborator

Add BSL license

@odedponcz odedponcz requested a review from romange May 29, 2022 09:09
LICENSE.md Outdated

<u>Licensed Work</u>: Dragonfly including the software components, or any portion of them, and any modification.

<u>Change Date</u>: Change date is five (5) years from release date.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets put a date here: June 1, 2027

README.md Outdated
@@ -9,6 +9,8 @@

### Probably, the fastest in-memory store in the universe!

<<<<<<< HEAD
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you did not rebase properly.
please remove all the diffs here

README.md Outdated
@@ -392,3 +429,8 @@ we went on to implement the Redis and Memcached functionality. By now, we have i
And finally, <br>
<em>Our mission is to build a well-designed, ultra-fast, cost-efficient in-memory datastore for cloud workloads that takes advantage of the latest hardware advancements. We intend to address the pain points of current solutions while preserving their product APIs and propositions.
</em>
<<<<<<< HEAD

P.S. other engineers share a similar sentiment about what makes a good memory store. See, for example, [here](https://twitter.github.io/pelikan/2019/why-pelikan.html) and [here](https://twitter.github.io/pelikan/2021/segcache.html) blog posts from Twitter's memcache team, or [this post](https://medium.com/@john_63123/redis-should-be-multi-threaded-e28319cab744) from authors of keydb.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

README should not have any differences except if you add a license link somewhere

@romange romange self-requested a review May 29, 2022 15:23
@romange romange merged commit e5107c2 into main May 29, 2022
@romange romange deleted the fixit branch May 29, 2022 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants