From 69921f506c02f65606498cfb4c083c6d8f91f125 Mon Sep 17 00:00:00 2001 From: dmaier-redislabs Date: Wed, 20 Mar 2024 23:54:23 +0200 Subject: [PATCH] Changes in the context of the Redis license change --- README.md | 2 + community/_index.md | 30 +++---------- docs/about/_index.md | 11 +++-- docs/about/governance.md | 91 ---------------------------------------- docs/about/license.md | 77 ++++++++++------------------------ docs/about/sponsors.md | 43 ------------------- 6 files changed, 37 insertions(+), 217 deletions(-) delete mode 100644 docs/about/governance.md delete mode 100644 docs/about/sponsors.md diff --git a/README.md b/README.md index a9401a1c9b..873edc9a6f 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # Redis documentation +OPEN SOURCE LICENSE VS. TRADEMARKS. The three-clause BSD license gives you the right to redistribute and use the software in source and binary forms, with or without modification, under certain conditions. However, open source licenses like the three-clause BSD license do not address trademarks. For further details please read the [Redis Trademark Policy](https://www.redis.com/legal/trademark-policy)." + ## Clients All clients are listed under language specific sub-folders of [clients](./clients) diff --git a/community/_index.md b/community/_index.md index 09e6949d5c..b67d2a2aaf 100644 --- a/community/_index.md +++ b/community/_index.md @@ -3,7 +3,7 @@ title: Community linkTitle: Community --- -Since 2009, the Redis open source project has inspired an enthusiastic and active community of users and contributors. We continue to be committed to fostering an open, welcoming, diverse, inclusive, and healthy community. +Since 2009, the Redis project has inspired an enthusiastic and active community of users and contributors. We continue to be committed to fostering an open, welcoming, diverse, inclusive, and healthy community. ## Code of Conduct @@ -29,29 +29,15 @@ For occasional updates on the new Redis releases, you can either [subscribe to t To keep up with the latest from Redis Inc., including news on Redis Cloud and Redis Stack, consider [following the Redis Twitter feed](https://twitter.com/redisinc). -## Project governance - -Redis has adopted a [light governance model](/docs/about/governance) led by individuals who have made significant contributions to Redis and demonstrated a long-term commitment to the project. - -Learn more about the project's governance and the Redis Core Team on the [Redis governance page](/docs/about/governance). - -## Conferences and meetups - -Redis regularly sponsors conferences and meetups. Recent conferences include: - -* [Redis Days 2022](https://redis.com/redisdays/) - -* [RedisConf 2021](https://redis.com/redisconf/) - -* [RedisConf 2020](https://www.youtube.com/c/Redisinc/playlists?view=50&sort=dd&shelf_id=4) - ## Contributing to Redis -There are many ways to contribute to Redis, starting with documentation all the way to changes to the open source Redis server. Here are a few ways you can get involved. +> Future releases of Redis will be dual-licensed under a source-available license. You can choose between the [Redis Source Available License 2.0 (RSALv2)](/docs/about/license) or the Server Side Public License v1 (SSPLv1). + +There are many ways to contribute to Redis, starting with documentation all the way to changes to the Redis server. Here are a few ways you can get involved. ### Contributing to docs -The [Redis docs](https://github.com/redis/redis-doc) are open source, and we'd love to incorporate your contributions. For small changes and typos, we recommend creating a pull request against [redis-doc repo](https://github.com/redis/redis-doc/pulls). +We welcome contributions to the [Redis docs](https://github.com/redis/redis-doc). For small changes and typos, we recommend creating a pull request against [redis-doc repo](https://github.com/redis/redis-doc/pulls). ### Reporting bugs @@ -61,8 +47,4 @@ For larger doc changes, we ask that you first create an issue describing your pr ### Client libraries -The Redis client libraries are nearly always open source and accepting of contributions. Consult the contribution guidelines for the library you're interested in. - -### Hacktoberfest - -Redis is participating in [Hacktoberfest 2022](/community/hacktoberfest/). +The Redis client libraries are nearly always open source and accepting of contributions. Consult the contribution guidelines for the library you're interested in. \ No newline at end of file diff --git a/docs/about/_index.md b/docs/about/_index.md index 4b80f25497..56dc574a12 100644 --- a/docs/about/_index.md +++ b/docs/about/_index.md @@ -2,14 +2,17 @@ title: Introduction to Redis linkTitle: "About" weight: 10 -description: Learn about the Redis open source project +description: Learn about Redis aliases: - /topics/introduction - /buzz --- -Redis is an open source (BSD licensed), in-memory __data structure store__ used as a database, cache, message broker, and streaming engine. Redis provides [data structures](/docs/data-types/) such as -[strings](/docs/data-types/strings/), [hashes](/docs/data-types/hashes/), [lists](/docs/data-types/lists/), [sets](/docs/data-types/sets/), [sorted sets](/docs/data-types/sorted-sets/) with range queries, [bitmaps](/docs/data-types/bitmaps/), [hyperloglogs](/docs/data-types/hyperloglogs/), [geospatial indexes](/docs/data-types/geospatial/), and [streams](/docs/data-types/streams/). Redis has built-in [replication](/topics/replication), [Lua scripting](/commands/eval), [LRU eviction](/docs/reference/eviction/), [transactions](/topics/transactions), and different levels of [on-disk persistence](/topics/persistence), and provides high availability via [Redis Sentinel](/topics/sentinel) and automatic partitioning with [Redis Cluster](/topics/cluster-tutorial). +Redis is an open source (BSD licensed), in-memory __data structure store__ used as a database, cache, message broker, and streaming engine. + +> Future releases of Redis will be dual-licensed under a source-available license. You can choose between the [Redis Source Available License 2.0 (RSALv2)](/docs/about/license) or the Server Side Public License v1 (SSPLv1). + +Redis provides [data structures](/docs/data-types/) such as [strings](/docs/data-types/strings/), [hashes](/docs/data-types/hashes/), [lists](/docs/data-types/lists/), [sets](/docs/data-types/sets/), [sorted sets](/docs/data-types/sorted-sets/) with range queries, [bitmaps](/docs/data-types/bitmaps/), [hyperloglogs](/docs/data-types/hyperloglogs/), [geospatial indexes](/docs/data-types/geospatial/), and [streams](/docs/data-types/streams/). Redis has built-in [replication](/topics/replication), [Lua scripting](/commands/eval), [LRU eviction](/docs/reference/eviction/), [transactions](/topics/transactions), and different levels of [on-disk persistence](/topics/persistence), and provides high availability via [Redis Sentinel](/topics/sentinel) and automatic partitioning with [Redis Cluster](/topics/cluster-tutorial). You can run __atomic operations__ on these types, like [appending to a string](/commands/append); @@ -40,4 +43,4 @@ Redis is written in **ANSI C** and works on most POSIX systems like Linux, \*BSD, and Mac OS X, without external dependencies. Linux and OS X are the two operating systems where Redis is developed and tested the most, and we **recommend using Linux for deployment**. Redis may work in Solaris-derived systems like SmartOS, but support is *best effort*. There is no official support for Windows builds. -
\ No newline at end of file +
diff --git a/docs/about/governance.md b/docs/about/governance.md deleted file mode 100644 index 879f109eb7..0000000000 --- a/docs/about/governance.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: "Redis open source governance" -linkTitle: "Governance" -weight: 3 -description: > - Governance model for the Redis open source project -aliases: - - /topics/governance ---- - -From 2009-2020, Salvatore Sanfilippo built, led, and maintained the Redis open source project. During this time, Redis had no formal governance structure, operating primarily as a [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life)-style project. - -As Redis grew, matured, and expanded its user base, it became increasingly important to form a sustainable structure for its ongoing development and maintenance. Salvatore and the core Redis contributors wanted to ensure the project’s continuity and reflect its larger community. With this in mind, a new governance structure was adopted. - -## Current governance structure - -Starting on June 30, 2020, Redis adopted a _light governance_ model that matches the current size of the project and minimizes the changes from its earlier model. The governance model is intended to be a meritocracy, aiming to empower individuals who demonstrate a long-term commitment and make significant contributions. - -## The Redis core team - -Salvatore Sanfilippo named two successors to take over and lead the Redis project: Yossi Gottlieb ([yossigo](https://github.com/yossigo)) and Oran Agra ([oranagra](https://github.com/oranagra)) - -With the backing and blessing of Redis Ltd., we took this opportunity to create a more open, scalable, and community-driven “core team” structure to run the project. The core team consists of members selected based on demonstrated, long-term personal involvement and contributions. - -The current core team members are: - -* Project Lead: Yossi Gottlieb ([yossigo](https://github.com/yossigo)) from Redis Ltd. -* Project Lead: Oran Agra ([oranagra](https://github.com/oranagra)) from Redis Ltd. -* Community Lead: Itamar Haber ([itamarhaber](https://github.com/itamarhaber)) from Redis Ltd. -* Member: Zhao Zhao ([soloestoy](https://github.com/soloestoy)) from Alibaba -* Member: Madelyn Olson ([madolson](https://github.com/madolson)) from Amazon Web Services - -The Redis core team members serve the Redis open source project and community. They are expected to set a good example of behavior, culture, and tone in accordance with the adopted [Code of Conduct](https://www.contributor-covenant.org/). They should also consider and act upon the best interests of the project and the community in a way that is free from foreign or conflicting interests. - -The core team will be responsible for the Redis core project, which is the part of Redis that is hosted in the main Redis repository and is BSD licensed. It will also aim to maintain coordination and collaboration with other projects that make up the Redis ecosystem, including Redis clients, satellite projects, major middleware that relies on Redis, etc. - -#### Roles and responsibilities - -The core team has the following remit: - -* Managing the core Redis code and documentation -* Managing new Redis releases -* Maintaining a high-level technical direction/roadmap -* Providing a fast response, including fixes/patches, to address security vulnerabilities and other major issues -* Project governance decisions and changes -* Coordination of Redis core with the rest of the Redis ecosystem -* Managing the membership of the core team - -The core team aims to form and empower a community of contributors by further delegating tasks to individuals who demonstrate commitment, know-how, and skills. In particular, we hope to see greater community involvement in the following areas: - -* Support, troubleshooting, and bug fixes of reported issues -* Triage of contributions/pull requests - -#### Decision making - -* **Normal decisions** will be made by core team members based on a lazy consensus approach: each member may vote +1 (positive) or -1 (negative). A negative vote must include thorough reasoning and better yet, an alternative proposal. The core team will always attempt to reach a full consensus rather than a majority. Examples of normal decisions: - * Day-to-day approval of pull requests and closing issues - * Opening new issues for discussion -* **Major decisions** that have a significant impact on the Redis architecture, design, or philosophy as well as core-team structure or membership changes should preferably be determined by full consensus. If the team is not able to achieve a full consensus, a majority vote is required. Examples of major decisions: - * Fundamental changes to the Redis core - * Adding a new data structure - * Creating a new version of RESP (Redis Serialization Protocol) - * Changes that affect backward compatibility - * Adding or changing core team members -* Project leads have a right to veto major decisions - -#### Core team membership - -* The core team is not expected to serve for life, however, long-term participation is desired to provide stability and consistency in the Redis programming style and the community. -* If a core-team member whose work is funded by Redis Ltd. must be replaced, the replacement will be designated by Redis Ltd. after consultation with the remaining core-team members. -* If a core-team member not funded by Redis Ltd. will no longer participate, for whatever reason, the other team members will select a replacement. - -## Community forums and communications - -We want the Redis community to be as welcoming and inclusive as possible. To that end, we have adopted a [Code of Conduct](https://www.contributor-covenant.org/) that we ask all community members to read and observe. - -We encourage that all significant communications will be public, asynchronous, archived, and open for the community to actively participate in using the channels described [here](https://redis.io/community). The exception to that is sensitive security issues that require resolution prior to public disclosure. - -To contact the core team about sensitive matters, such as misconduct or security issues, please email [redis@redis.io](mailto:redis@redis.io). - -## New Redis repository and commits approval process - -The Redis core source repository is hosted under [https://github.com/redis/redis](https://github.com/redis/redis). Our target is to eventually host everything (the Redis core source and other ecosystem projects) under the Redis GitHub organization ([https://github.com/redis](https://github.com/redis)). Commits to the Redis source repository will require code review, approval of at least one core-team member who is not the author of the commit, and no objections. - -## Project and development updates - -Stay connected to the project and the community! For project and community updates, follow the project [channels](https://redis.io/community). Development announcements will be made via [the Redis mailing list](https://groups.google.com/forum/#!forum/redis-db). - -## Updates to these governance rules - -Any substantial changes to these rules will be treated as a major decision. Minor changes or ministerial corrections will be treated as normal decisions. diff --git a/docs/about/license.md b/docs/about/license.md index 31291c669e..6f78dd1f2a 100644 --- a/docs/about/license.md +++ b/docs/about/license.md @@ -10,76 +10,43 @@ aliases: --- -* Redis is **open source software** released under the terms of the **three clause BSD license**. Most of the Redis source code was written and is copyrighted by Salvatore Sanfilippo and Pieter Noordhuis. A list of other contributors can be found in the git history. +* Redis is source-available software, available under the terms of the RSALv2 and SSPLv1 licenses. Most of the Redis source code was written and is copyrighted by Salvatore Sanfilippo and Pieter Noordhuis. A list of other contributors can be found in the git history. The Redis trademark and logo are owned by Redis Ltd. and can be used in accordance with the [Redis Trademark Guidelines](https://redis.com/legal/trademark-guidelines/). * RedisInsight is licensed under the Server Side Public License (SSPL). -* Redis Stack Server, which combines open source Redis with Search and Query features, JSON, Time Series, and Probabilistic data structures is dual-licensed under the Redis Source Available License (RSALv2), as described below, and the [Server Side Public License](https://en.wikipedia.org/wiki/Server_Side_Public_License) (SSPL). For information about licensing per version, see [Versions and licenses](/docs/about/about-stack/#redis-stack-license). +* Redis Stack Server, which combines open source Redis with Search and Query features, JSON, Time Series, and Probabilistic data structures is dual-licensed under the Redis Source Available License (RSALv2), as described below, and the [Server Side Public License](https://redis.com/legal/server-side-public-license-sspl/) (SSPL). For information about licensing per version, see [Versions and licenses](/docs/about/about-stack/#redis-stack-license). -## Licences: - -### Three clause BSD license - -Every file in the Redis distribution, with the exceptions of third party files specified in the list below, contain the following license: - -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions are met: - -* Redistributions of source code must retain the above copyright notice, - this list of conditions and the following disclaimer. - -* Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in the - documentation and/or other materials provided with the distribution. - -* Neither the name of Redis nor the names of its contributors may be used - to endorse or promote products derived from this software without - specific prior written permission. - -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" -AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE -ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE -LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR -CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF -SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS -INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN -CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) -ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE -POSSIBILITY OF SUCH DAMAGE. +## Licenses: ### REDIS SOURCE AVAILABLE LICENSE (RSAL) 2.0 - -_Last updated: November 15, 2022_ +Last updated: November 15, 2022 #### Acceptance By using the software, you agree to all of the terms and conditions below. - + #### Copyright License The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject to the limitations and conditions below. #### Limitations -You may not make the functionality of the software or a modified version available to third parties as a service, or distribute the software or a modified version in a manner that makes the functionality of the software available to third parties. -Making the functionality of the software or modified version available to third parties includes, without limitation, enabling third parties to interact with the functionality of the software or modified version in distributed form or remotely through a computer network, offering a product or service the value of which entirely or primarily derives from the value of the software or modified version, or offering a product or service that accomplishes for users the primary purpose of the software or modified version. +You may not make the functionality of the software or a modified version available to third parties as a service, or distribute the software or a modified version in a manner that makes the functionality of the software available to third parties. Making the functionality of the software or modified version available to third parties includes, without limitation, enabling third parties to interact with the functionality of the software or modified version in distributed form or remotely through a computer network, offering a product or service the value of which entirely or primarily derives from the value of the software or modified version, or offering a product or service that accomplishes for users the primary purpose of the software or modified version. You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software. Any use of the licensor’s trademarks is subject to applicable law. - + #### Patents The licensor grants you a license, under any patent claims the licensor can license, or becomes able to license, to make, have made, use, sell, offer for sale, import and have imported the software, in each case subject to the limitations and conditions in this license. This license does not cover any patent claims that you cause to be infringed by modifications or additions to the software. If you or your company make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company. #### Notices -You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms. -If you modify the software, you must include in any modified copies of the software prominent notices stating that you have modified the software. +You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms. If you modify the software, you must include in any modified copies of the software prominent notices stating that you have modified the software. #### No Other Rights @@ -91,38 +58,38 @@ If you use the software in violation of these terms, such use is not licensed, a #### No Liability -_**As far as the law allows, the **software** comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.**_ +As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim. #### Definitions -The **licensor** is the entity offering these terms, and the software is the software the licensor makes available under these terms, including any portion of it. +The licensor is the entity offering these terms, and the software is the software the licensor makes available under these terms, including any portion of it. -To **modify** a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission other than making an exact copy. The resulting work is called a **modified version** of the earlier work. +To modify a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission other than making an exact copy. The resulting work is called a modified version of the earlier work. **you** refers to the individual or entity agreeing to these terms. -**your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. +**your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. **control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect. -**your licenses** are all the licenses granted to you for the software under these terms. -use means anything you do with the software requiring one of your licenses. +**your licenses** are all the licenses granted to you for the software under these terms. -**trademark** means trademarks, service marks, and similar rights. +**use** means anything you do with the software requiring one of your licenses. +**trademark** means trademarks, service marks, and similar rights. -### Third-party files and licenses +#### Third-party files and licenses Redis uses source code from third parties. All this code contains a BSD or BSD-compatible license. The following is a list of third-party files and information about their copyright. -* Redis uses the [LHF compression library](http://oldhome.schmorp.de/marc/liblzf.html). LibLZF is copyright Marc Alexander Lehmann and is released under the terms of the **two-clause BSD license**. +* Redis uses the [LHF compression library](http://oldhome.schmorp.de/marc/liblzf.html). LibLZF is copyright Marc Alexander Lehmann and is released under the terms of the two-clause BSD license. -* Redis uses the `sha1.c` file that is copyright by Steve Reid and released under the **public domain**. This file is extremely popular and used among open source and proprietary code. +* Redis uses the sha1.c file that is copyright by Steve Reid and released under the public domain. This file is extremely popular and used among open source and proprietary code. -* When compiled on Linux, Redis uses the [Jemalloc allocator](https://github.com/jemalloc/jemalloc), which is copyrighted by Jason Evans, Mozilla Foundation, and Facebook, Inc and released under the **two-clause BSD license**. +* When compiled on Linux, Redis uses the [Jemalloc allocator](https://github.com/jemalloc/jemalloc), which is copyrighted by Jason Evans, Mozilla Foundation, and Facebook, Inc and released under the two-clause BSD license. -* Inside Jemalloc, the file `pprof` is copyrighted by Google Inc. and released under the **three-clause BSD license**. +* Inside Jemalloc, the file pprof is copyrighted by Google Inc. and released under the three-clause BSD license. -* Inside Jemalloc the files `inttypes.h`, `stdbool.h`, `stdint.h`, `strings.h` under the `msvc_compat` directory are copyright Alexander Chemeris and released under the **three-clause BSD license**. +* Inside Jemalloc the files inttypes.h, stdbool.h, stdint.h, strings.h under the msvc_compat directory are copyright Alexander Chemeris and released under the three-clause BSD license. -* The libraries **hiredis** and **linenoise** also included inside the Redis distribution are copyright Salvatore Sanfilippo and Pieter Noordhuis and released under the terms respectively of the **three-clause BSD license** and **two-clause BSD license**. \ No newline at end of file +* The libraries hiredis and linenoise also included inside the Redis distribution are copyright Salvatore Sanfilippo and Pieter Noordhuis and released under the terms respectively of the three-clause BSD license and two-clause BSD license. \ No newline at end of file diff --git a/docs/about/sponsors.md b/docs/about/sponsors.md deleted file mode 100644 index 1426a14509..0000000000 --- a/docs/about/sponsors.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: "Redis sponsors" -linkTitle: "Sponsors" -weight: 4 -description: Current and former Redis sponsors -aliases: - - /topics/sponsors ---- - -From 2015 to 2020, Salvatore Sanfilippo's work on Redis was sponsored by [Redis Ltd.](https://redis.com) Since June 2020, Redis Ltd. has sponsored the [governance of Redis](/topics/governance). Redis Ltd. also sponsors the hosting and maintenance of [redis.io](https://redis.io). - -Past sponsorships: - -* The [Shuttleworth Foundation](https://en.wikipedia.org/wiki/Shuttleworth_Foundation) has donated 5000 USD to the Redis project in form of a flash grant. -* From May 2013 to June 2015, the work [Salvatore Sanfilippo](http://twitter.com/antirez) did to develop Redis was sponsored by [Pivotal](http://gopivotal.com). -* Before May 2013, the project was sponsored by VMware with the work of [Salvatore Sanfilippo](http://twitter.com/antirez) and [Pieter Noordhuis](http://twitter.com/pnoordhuis). -* [VMware](http://vmware.com) and later [Pivotal](http://pivotal.io) provided a 24 GB RAM workstation for Salvatore to run the Redis CI test and other long running tests. Later, Salvatore equipped the server with an SSD drive in order to test in the same hardware with rotating and flash drives. -* [Linode](https://linode.com), in January 2010, provided virtual machines for Redis testing in a virtualized environment. -* Slicehost, January 2010, provided Virtual Machines for Redis testing in a virtualized environment. -* [Citrusbyte](http://citrusbyte.com), in December 2009, contributed part of Virtual Memory implementation. -* [Hitmeister](http://www.hitmeister.de/), in December 2009, contributed part of Redis Cluster. -* [Engine Yard](http://engineyard.com), in December 2009, contributed blocking POP (BLPOP) and part of the Virtual Memory implementation. - -Also thanks to the following people or organizations that donated to the Project: - -* Emil Vladev -* [Brad Jasper](http://bradjasper.com/) -* [Mrkris](http://mrkris.com/) - -The Redis community is grateful to [Redis Ltd.](http://redis.com), [Pivotal](http://gopivotal.com), [VMware](http://vmware.com) and to the other companies and people who have donated to the Redis project. Thank you. - -## redis.io - -[Citrusbyte](https://citrusbyte.com) sponsored the creation of the official -Redis logo (designed by Carlos Prioglio) and -transferred its copyright to Salvatore Sanfilippo. - -They also sponsored the initial implementation of this site by -[Damian Janowski](https://twitter.com/djanowski) and [Michel -Martens](https://twitter.com/soveran). - -The `redis.io` domain was donated for a few years to the project by [I Want My -Name](https://iwantmyname.com).