Yzena
/
Yc
2
1
Fork 0
Yzena's monorepo. Includes Yvm, Yao, Rig, Ur, and Yar. https://docs.yzena.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

53 lines
2.0 KiB

# ***** BEGIN LICENSE BLOCK *****
#
# Copyright 2017-2022 Yzena Tech
#
Add the actual license(s) to the repo These are the actual licenses to use the software: Yzena Viral User License, the Affero General Public License, and the Server Side Public License. Users and distributors must comply with all three. There may be those that think that they can use previous commits to this repo under just the Yzena Network License, which is what the headers said in those commits. However, this repo was not public at the time. It was public before, but it was under the Apache 2.0, and that was many commits ago, where there was really nothing interesting beyond what had been public. So since the code was not public, I could change the license freely, and I did, and I retroactively apply the licenses I am using now to previous versions. I can do that because I either wrote the code from scratch, or it was licensed such that I could relicense it. So if you think you might be sneaky, don't get any ideas; I *will* sue you if you violate any one of these three licenses. That said, I put this software under these licenses to make them radioactive to companies for long enough to establish myself and this software. I plan on relaxing these restrictions over time, in an intentional manner to follow the licensing arc described in <https://writing.kemitchell.com/2020/03/07/No-Posse.html>. After my Yzena licenses are improved and approved by a lawyer, I'll probably remove the SSPL first, then the AGPL, then I'll progressively move to freer Yzena licenses, though I may stay on the User series of licenses. So if you want to use this software, but it's too radioactive; give it time. Oh, and email me letting me know you're interested, but why you can't use it. Signed-off-by: Gavin Howard <gavin@yzena.com>
6 months ago
# Licensed under the Yzena Viral User License, Version 0.1 (the "Yzena Viral
# User License" or "YVUL"), the GNU Affero General Public License (the "GNU
# AGPL"), Version 3.0, and the Server Side Public License (the "SSPL"),
# Version 1. You may not use this file except in compliance with all of those
# licenses.
#
Add the actual license(s) to the repo These are the actual licenses to use the software: Yzena Viral User License, the Affero General Public License, and the Server Side Public License. Users and distributors must comply with all three. There may be those that think that they can use previous commits to this repo under just the Yzena Network License, which is what the headers said in those commits. However, this repo was not public at the time. It was public before, but it was under the Apache 2.0, and that was many commits ago, where there was really nothing interesting beyond what had been public. So since the code was not public, I could change the license freely, and I did, and I retroactively apply the licenses I am using now to previous versions. I can do that because I either wrote the code from scratch, or it was licensed such that I could relicense it. So if you think you might be sneaky, don't get any ideas; I *will* sue you if you violate any one of these three licenses. That said, I put this software under these licenses to make them radioactive to companies for long enough to establish myself and this software. I plan on relaxing these restrictions over time, in an intentional manner to follow the licensing arc described in <https://writing.kemitchell.com/2020/03/07/No-Posse.html>. After my Yzena licenses are improved and approved by a lawyer, I'll probably remove the SSPL first, then the AGPL, then I'll progressively move to freer Yzena licenses, though I may stay on the User series of licenses. So if you want to use this software, but it's too radioactive; give it time. Oh, and email me letting me know you're interested, but why you can't use it. Signed-off-by: Gavin Howard <gavin@yzena.com>
6 months ago
# You may obtain a copy of the Yzena Viral User License at
#
Add the actual license(s) to the repo These are the actual licenses to use the software: Yzena Viral User License, the Affero General Public License, and the Server Side Public License. Users and distributors must comply with all three. There may be those that think that they can use previous commits to this repo under just the Yzena Network License, which is what the headers said in those commits. However, this repo was not public at the time. It was public before, but it was under the Apache 2.0, and that was many commits ago, where there was really nothing interesting beyond what had been public. So since the code was not public, I could change the license freely, and I did, and I retroactively apply the licenses I am using now to previous versions. I can do that because I either wrote the code from scratch, or it was licensed such that I could relicense it. So if you think you might be sneaky, don't get any ideas; I *will* sue you if you violate any one of these three licenses. That said, I put this software under these licenses to make them radioactive to companies for long enough to establish myself and this software. I plan on relaxing these restrictions over time, in an intentional manner to follow the licensing arc described in <https://writing.kemitchell.com/2020/03/07/No-Posse.html>. After my Yzena licenses are improved and approved by a lawyer, I'll probably remove the SSPL first, then the AGPL, then I'll progressively move to freer Yzena licenses, though I may stay on the User series of licenses. So if you want to use this software, but it's too radioactive; give it time. Oh, and email me letting me know you're interested, but why you can't use it. Signed-off-by: Gavin Howard <gavin@yzena.com>
6 months ago
# https://yzena.com/yzena-viral-user-license/
#
# Unless required by applicable law or agreed to in writing, software
Add the actual license(s) to the repo These are the actual licenses to use the software: Yzena Viral User License, the Affero General Public License, and the Server Side Public License. Users and distributors must comply with all three. There may be those that think that they can use previous commits to this repo under just the Yzena Network License, which is what the headers said in those commits. However, this repo was not public at the time. It was public before, but it was under the Apache 2.0, and that was many commits ago, where there was really nothing interesting beyond what had been public. So since the code was not public, I could change the license freely, and I did, and I retroactively apply the licenses I am using now to previous versions. I can do that because I either wrote the code from scratch, or it was licensed such that I could relicense it. So if you think you might be sneaky, don't get any ideas; I *will* sue you if you violate any one of these three licenses. That said, I put this software under these licenses to make them radioactive to companies for long enough to establish myself and this software. I plan on relaxing these restrictions over time, in an intentional manner to follow the licensing arc described in <https://writing.kemitchell.com/2020/03/07/No-Posse.html>. After my Yzena licenses are improved and approved by a lawyer, I'll probably remove the SSPL first, then the AGPL, then I'll progressively move to freer Yzena licenses, though I may stay on the User series of licenses. So if you want to use this software, but it's too radioactive; give it time. Oh, and email me letting me know you're interested, but why you can't use it. Signed-off-by: Gavin Howard <gavin@yzena.com>
6 months ago
# distributed under the Yzena Viral User License is distributed under the
# following disclaimer:
#
# As far as the law allows, this software comes as is, without any
# warranty or condition, and no contributor will be liable to anyone for
# any damages related to this software or this license, under any kind of
# legal claim.
#
Add the actual license(s) to the repo These are the actual licenses to use the software: Yzena Viral User License, the Affero General Public License, and the Server Side Public License. Users and distributors must comply with all three. There may be those that think that they can use previous commits to this repo under just the Yzena Network License, which is what the headers said in those commits. However, this repo was not public at the time. It was public before, but it was under the Apache 2.0, and that was many commits ago, where there was really nothing interesting beyond what had been public. So since the code was not public, I could change the license freely, and I did, and I retroactively apply the licenses I am using now to previous versions. I can do that because I either wrote the code from scratch, or it was licensed such that I could relicense it. So if you think you might be sneaky, don't get any ideas; I *will* sue you if you violate any one of these three licenses. That said, I put this software under these licenses to make them radioactive to companies for long enough to establish myself and this software. I plan on relaxing these restrictions over time, in an intentional manner to follow the licensing arc described in <https://writing.kemitchell.com/2020/03/07/No-Posse.html>. After my Yzena licenses are improved and approved by a lawyer, I'll probably remove the SSPL first, then the AGPL, then I'll progressively move to freer Yzena licenses, though I may stay on the User series of licenses. So if you want to use this software, but it's too radioactive; give it time. Oh, and email me letting me know you're interested, but why you can't use it. Signed-off-by: Gavin Howard <gavin@yzena.com>
6 months ago
# You may obtain a copy of the GNU Affero General Public License at
#
# https://www.gnu.org/licenses/agpl-3.0.html
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the GNU Affero General Public License is distributed under
# the following disclaimer:
#
# This software is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero
# General Public License for more details.
#
# You may obtain a copy of the Server Side Public License at
#
# https://www.mongodb.com/licensing/server-side-public-license
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the Server Side Public License is distributed under the
# following disclaimer:
#
# This software is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Server
# Side Public License for more details.
#
# ****** END LICENSE BLOCK ******
add_subdirectory(io)