diff --git a/Cargo.toml b/Cargo.toml index 3b16248..7d1477b 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -5,7 +5,7 @@ name = "flowfin-core" version = "0.0.0" edition = "2024" -license = "AGPL-3.0-or-later" +license = "MIT OR Apache-2.0" description = "The shared core every Flowfin client uses: reaching a server, holding a session, caching, artwork, playback position and measurement." repository = "https://github.com/Flowfin/core" publish = false diff --git a/LICENSE b/LICENSE deleted file mode 100644 index ac46125..0000000 --- a/LICENSE +++ /dev/null @@ -1,661 +0,0 @@ - GNU AFFERO GENERAL PUBLIC LICENSE - Version 3, 19 November 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU Affero General Public License is a free, copyleft license for -software and other kinds of works, specifically designed to ensure -cooperation with the community in the case of network server software. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -our General Public Licenses are intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - Developers that use our General Public Licenses protect your rights -with two steps: (1) assert copyright on the software, and (2) offer -you this License which gives you legal permission to copy, distribute -and/or modify the software. - - A secondary benefit of defending all users' freedom is that -improvements made in alternate versions of the program, if they -receive widespread use, become available for other developers to -incorporate. Many developers of free software are heartened and -encouraged by the resulting cooperation. However, in the case of -software used on network servers, this result may fail to come about. -The GNU General Public License permits making a modified version and -letting the public access it on a server without ever releasing its -source code to the public. - - The GNU Affero General Public License is designed specifically to -ensure that, in such cases, the modified source code becomes available -to the community. It requires the operator of a network server to -provide the source code of the modified version running there to the -users of that server. Therefore, public use of a modified version, on -a publicly accessible server, gives the public access to the source -code of the modified version. - - An older license, called the Affero General Public License and -published by Affero, was designed to accomplish similar goals. This is -a different license, not a version of the Affero GPL, but Affero has -released a new version of the Affero GPL which permits relicensing under -this license. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU Affero General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Remote Network Interaction; Use with the GNU General Public License. - - Notwithstanding any other provision of this License, if you modify the -Program, your modified version must prominently offer all users -interacting with it remotely through a computer network (if your version -supports such interaction) an opportunity to receive the Corresponding -Source of your version by providing access to the Corresponding Source -from a network server at no charge, through some standard or customary -means of facilitating copying of software. This Corresponding Source -shall include the Corresponding Source for any work covered by version 3 -of the GNU General Public License that is incorporated pursuant to the -following paragraph. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the work with which it is combined will remain governed by version -3 of the GNU General Public License. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU Affero General Public License from time to time. Such new versions -will be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU Affero General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU Affero General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU Affero General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - core, the shared core every Flowfin client uses: server access, session, cache, artwork and the speed budget. - Copyright (C) 2026 Nils Lehnen - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU Affero General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program 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 should have received a copy of the GNU Affero General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If your software can interact with users remotely through a computer -network, you should also make sure that it provides a way for users to -get its source. For example, if your program is a web application, its -interface could display a "Source" link that leads users to an archive -of the code. There are many ways you could offer source, and different -solutions will be better for different programs; see section 13 for the -specific requirements. - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU AGPL, see -. diff --git a/LICENSE-APACHE b/LICENSE-APACHE new file mode 100644 index 0000000..d645695 --- /dev/null +++ b/LICENSE-APACHE @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/LICENSE-MIT b/LICENSE-MIT new file mode 100644 index 0000000..12a52c1 --- /dev/null +++ b/LICENSE-MIT @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2026 Nils Lehnen + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/NOTICE.md b/NOTICE.md index 0831054..9ea7abf 100644 --- a/NOTICE.md +++ b/NOTICE.md @@ -4,5 +4,7 @@ This software is developed for lawful use. Operators and users are responsible for making sure that their deployment and use comply with the laws that apply to them, including copyright and data protection law. The project does not endorse or support unlawful use of any kind, and nothing -in it is designed to enable such use. The [license](LICENSE) contains the -full warranty and liability disclaimer. +in it is designed to enable such use. The core is offered under +`MIT OR Apache-2.0`, and each of the two texts, [LICENSE-MIT](LICENSE-MIT) and +[LICENSE-APACHE](LICENSE-APACHE), contains the full warranty and liability +disclaimer. diff --git a/README.md b/README.md index 1765298..3853e66 100644 --- a/README.md +++ b/README.md @@ -175,6 +175,14 @@ this repository treats as one, and what a reporter gets back. ## License -AGPL-3.0, copyright 2026 Nils Lehnen. +`MIT OR Apache-2.0`, at your choice, copyright 2026 Nils Lehnen. -The full text is in [LICENSE](LICENSE). +The two texts are in [LICENSE-MIT](LICENSE-MIT) and +[LICENSE-APACHE](LICENSE-APACHE). Either one on its own is enough; which of +them you take is yours to pick. + +This repository published under AGPL-3.0-or-later until 2026-09-05. A copy +received under those terms keeps them, and what changed on that day is the +terms the core is offered on from it. The answer that stands, the reason given +for it, and the dependency set that follows from it are in +[0303. The licence the core is offered under](docs/decisions/0303-the-licence-the-core-is-offered-under.md). diff --git a/docs/decisions/0011-the-language-the-toolchain-and-the-binding-layer.md b/docs/decisions/0011-the-language-the-toolchain-and-the-binding-layer.md index 2aa5ff6..57ca274 100644 --- a/docs/decisions/0011-the-language-the-toolchain-and-the-binding-layer.md +++ b/docs/decisions/0011-the-language-the-toolchain-and-the-binding-layer.md @@ -124,6 +124,10 @@ A client embeds this library, so entry 2's answer is what carries entry 1's answ to eleven clients rather than stopping at this repository. That follows from the pair and is not a decision of this record. +Entry 1 was answered a second time and the answer above is the one that was +superseded. The answer that stands is +[0303](0303-the-licence-the-core-is-offered-under.md). + ## What the standard library supplies, and what it does not This section exists because the difference decides how large the dependency graph diff --git a/docs/decisions/0091-what-the-first-release-contains.md b/docs/decisions/0091-what-the-first-release-contains.md index 3988693..3c10a60 100644 --- a/docs/decisions/0091-what-the-first-release-contains.md +++ b/docs/decisions/0091-what-the-first-release-contains.md @@ -76,6 +76,10 @@ from #74 linked and summarised, and the licence named: gh api repos/Flowfin/core --jq '.license.spdx_id' AGPL-3.0 +The licence the reading above names is the one that was superseded. What #95 +names is the answer that stands, in +[0303](0303-the-licence-the-core-is-offered-under.md). + ## What it does not contain, said before it is installed rather than after No user interface. No playback of anything. No client for any platform. Those diff --git a/docs/decisions/0103-what-admits-a-dependency-and-what-is-refused.md b/docs/decisions/0103-what-admits-a-dependency-and-what-is-refused.md index 0114946..ba54cac 100644 --- a/docs/decisions/0103-what-admits-a-dependency-and-what-is-refused.md +++ b/docs/decisions/0103-what-admits-a-dependency-and-what-is-refused.md @@ -2,7 +2,7 @@ Date: 2026-08-24 -Status: accepted. Supersedes nothing. Superseded by nothing. +Status: accepted. Supersedes nothing. Superseded by 0303. Narrowed-by: 0243, on the fourth behaviour refused outright, a dependency that writes to a log diff --git a/docs/decisions/0268-a-conjunctive-licence-expression.md b/docs/decisions/0268-a-conjunctive-licence-expression.md index b1b33eb..0d1de12 100644 --- a/docs/decisions/0268-a-conjunctive-licence-expression.md +++ b/docs/decisions/0268-a-conjunctive-licence-expression.md @@ -203,6 +203,11 @@ are satisfiable inside the work this core is distributed as, by the enumeration that work's own licence carries, rather than by anybody's judgement about whether they read as permissive. +The licence this ground reads is not the one the core is offered under from +2026-09-05. This half is re-read against the answer that stands in +[0303](0303-the-licence-the-core-is-offered-under.md), which is also where the +other half below is read as the ground that survives the move. + The second half of the ground is that the admitted set already carries both shapes, so no obligation class arrives with this term. The notice condition is `MIT`'s: diff --git a/docs/decisions/0303-the-licence-the-core-is-offered-under.md b/docs/decisions/0303-the-licence-the-core-is-offered-under.md new file mode 100644 index 0000000..a9845ea --- /dev/null +++ b/docs/decisions/0303-the-licence-the-core-is-offered-under.md @@ -0,0 +1,472 @@ +# 0303. The licence the core is offered under, and the dependency set that follows from it + +Date: 2026-09-05 + +Status: accepted. Supersedes 0103. Superseded by nothing. + +Issue: #303 + +## The decision + +The core is offered under `MIT OR Apache-2.0`, at the recipient's choice, +superseding the `AGPL-3.0-or-later` answer this board recorded on 2026-08-24; +and because the outbound licence is the premise +[0103](0103-what-admits-a-dependency-and-what-is-refused.md) derives its licence +set from, that record is superseded here rather than edited, with its worth test, +its outright refusals, its clause for a standing requirement, its test-tree split +and its removal rule carried forward unchanged and its licence set reversed in +direction. + +## The two answers, and which one stands + +Entry 1 of #1 was answered twice on that issue. The first, read out of the issue +that holds it: + + gh api repos/Flowfin/core/issues/1/comments \ + --jq '.[] | select(.created_at | startswith("2026-08-24")) | .body' | sed -n '3p' + Entry 1, recorded rather than newly decided: the fleet-wide licence answer covers this board - AGPL-3.0-or-later, the variant settled today on Flowfin/hub#1. + +The second, and the one that stands: + + gh api repos/Flowfin/core/issues/1/comments \ + --jq '.[] | select(.created_at | startswith("2026-09-04T21:44")) | .body' | head -1 + The answer of 2026-09-04 stands: MIT OR Apache-2.0. Entry 1 was answered twice because the second reading revisited it with the reason the first did not carry, that a core whose purpose is to be linked by clients this organisation does not write cannot be copyleft in any strength; the 2026-08-24 entry is superseded by that reading, and the record in docs/decisions/ says so in one sentence rather than leaving two answers on this issue for the next reader. + +The reason given for the second is the sentence quoted inside it: a core whose +whole purpose is to be linked by clients this organisation does not write cannot +be copyleft in any strength. The first answer carried no reason of its own beyond +the fleet-wide variant it adopted, which is what made it revisitable without +anything new having happened. + +The pair rather than either member alone is the second half of that answer, in +the same comment's own words: `MIT`'s four paragraphs for a recipient who wants +nothing else, `Apache-2.0` for the express patent grant and the defensive +termination, which matter when the subject is formats and protocols that vendors +consider theirs. A recipient picks either. + +## What a licence already granted keeps + +Every commit on the default branch before this one was published under +`AGPL-3.0-or-later`, and anybody who received a copy under those terms keeps them +for that copy. A licence is a grant to a recipient rather than a property of a +repository, so what changes here are the terms the core is offered on from this +commit, and nothing already given is revoked. What made the change possible at +all is that there is one author to renegotiate with, which #1 read rather than +assumed: + + git log --format='%aN' origin/main | sort -u + Nils Lehnen + gh api repos/Flowfin/core/contributors --jq '.[] | "\(.login) \(.contributions)"' + iderex 211 + +## The licence set + +Named explicitly, because a general principle is a thing two readers apply +differently. That sentence is +[0103](0103-what-admits-a-dependency-and-what-is-refused.md)'s and it is why this +record enumerates rather than states a test. + +Admitted anywhere in the graph, shipping tree or test tree: `MIT`, `Apache-2.0`, +`BSD-2-Clause`, `BSD-3-Clause`, `ISC`, `Zlib`, `Unlicense`, `CC0-1.0`, +`Unicode-3.0`. A dual offer that includes one of these is admitted on that +member, which is how the two most common offers in this ecosystem arrive. + +Refused, and this is the half that moves: `MPL-2.0`, `LGPL-2.1-or-later`, +`LGPL-3.0-or-later`, `GPL-2.0-only`, `GPL-2.0-or-later`, `GPL-3.0-or-later`, +`AGPL-3.0-or-later`. Every strength of copyleft is in the refused half now, and +six of those seven were in the admitted half under the answer this record +supersedes. + +Refused for a second reason, which is that they are not free software licences at +all whatever their terms say about source, and which the direction does not +touch: `SSPL-1.0`, `BUSL-1.1`, `Elastic-2.0`, anything carrying the Commons +Clause, and every licence with a non-commercial or field-of-use restriction. + +Refused, finally, and this is the one that arrives most often, also untouched: a +package with no licence statement at all, which is not permissive by default but +reserved by default. + +## Why the set is shaped this way, which is the sentence that reversed + +The superseded record derived its set from one-way compatibility in the copyleft +direction, in its own words: + + git show origin/main:docs/decisions/0103-what-admits-a-dependency-and-what-is-refused.md | sed -n '84,88p' + Why the set is shaped this way. The core is distributed under + AGPL-3.0-or-later, so the one-way compatibility is the direction that matters: a + permissive or weak-copyleft node can be carried inside this work, and a node whose + own terms forbid the conditions AGPL-3.0-or-later imposes cannot, whichever way + round it is more convenient. + +Under `MIT OR Apache-2.0` the direction runs the other way and the admitted half +shrinks. A work offered on those terms grants a recipient the choice of either, +so what may be carried inside it is what everybody conveying it can satisfy under +either member. That admits obligations of a shape both members already carry - +carrying a notice, preserving attribution, disclaiming warranty, a bar on using a +name to promote - and it refuses an obligation that reaches the work the material +is combined with, because neither member imposes one and a client author reading +`MIT OR Apache-2.0` on this core has not agreed to one. + +Two grounds do that refusing and they are worth keeping apart, because only the +first is a compatibility fact. + +The strong and weak copyleft family - `GPL`, `AGPL`, `LGPL` in every variant - +imposes conditions on the combined work: the whole conveyed work under the same +terms, or, for `LGPL`, the relinking condition over a client binary. A client +that links this core cannot meet either while offering their own client on their +own terms, and eleven clients this organisation does not write is exactly the +population that would have to. Refused because the terms cannot be met inside +what this core is offered as. + +`MPL-2.0` is refused on the second ground, which is a choice rather than a +compatibility fact, so it is written as one. Its copyleft is per file and its own +third section permits a Larger Work under other terms, so a client could convey a +binary containing `MPL-2.0` files while offering their client permissively. What +travels with those files is a source-availability obligation on them, owed by +whoever conveys the binary. That obligation is invisible in `MIT OR Apache-2.0`, +which is the whole of what a client author reads before linking, and it would +arrive in eleven repositories that never read a record saying it was there. The +multiplier is the argument, and it is the same one the superseded record opens +with: every dependency this core takes is taken eleven times. + +`GPL-2.0-only` is no longer the term the set names specially. The superseded +record named it because it was the one widely used free licence in its refused +half and the `-only` was the whole of the difference. With the whole copyleft +column refused, the `-only` distinguishes nothing here, and the term sits in the +refused half beside its `-or-later` sibling rather than ahead of it. + +What this set does not settle, carried forward unchanged: a node whose licence is +stated one way in its manifest and another way in its own tree. The manifest is +what a tool reads and the tree is what a court reads. Where the two disagree the +node is refused until they agree, because a licence nobody can state is the same +problem as none. + +## 0268 re-read against the premise that moved + +[0268](0268-a-conjunctive-licence-expression.md) decides two things, and only one +of the two grounds it gives for the second rests on the premise this record +moves. + +Its conjunction rule stands untouched, and it is restated here as part of the set +above rather than left for a reader to combine: a conjunction is admitted only +where every member is admitted, one member in the refused half refuses the whole +expression, and a member the set names in neither half leaves the expression +UNDECIDED, which is not admitted. A dual offer inside a conjunction is read on +its admitted member. Nothing in that rule depends on which licence the core is +offered under. + +`Unicode-3.0` stays in the admitted half, and the ground for it is now the second +of that record's two rather than the first. The first mapped the term's three +conditions onto the supplementary terms `AGPL-3.0-or-later` enumerates as ones +that may supplement it, quoting this repository's own licence file to do so. That +file is not what the core is offered under any more, so the mapping is a reading +of a licence this work no longer carries and it decides nothing here. + +The second ground survives the move intact, because it is about the admitted half +rather than about the outbound licence. The term's three conditions are a notice +carried with the copies or in the documentation, a warranty and liability +disclaimer, and a bar on using a copyright holder's name to promote. The first +two are `MIT`'s and the third is `BSD-3-Clause`'s third clause, both of which are +in the admitted half above, so admitting `Unicode-3.0` adds a fourth notice to +carry and no obligation class a client author or an operator was not already +meeting. There is no source-availability condition in it, no field-of-use +restriction, no non-commercial restriction, and no term reaching a work the +material is combined with, which is the test this record states. + +So `unicode-ident` stays admitted, and the collision +[0243](0243-the-means-a-certificate-is-validated-with.md) left open by name stays +closed, on a ground read out of the licence the core is offered under today. + +## What a dependency has to be worth + +Carried forward from the superseded record, because none of it rests on the +outbound licence. + +A dependency enters this core only where writing the equivalent here would cost +more than carrying somebody else's release cadence, security response and licence +for as long as the core lives. Every dependency this core takes is taken eleven +times, because a client embeds the core and embeds its graph, and that multiplier +is what makes the ordinary test insufficient: a dependency that saves an afternoon +here is a binary-size negotiation on a television, a store review somebody else +sits through, and a licence obligation in a repository this one never sees. + +Carrying it means four things at once. Its release cadence, because every release +is a change the gate has to run against. Its security response, because the core +inherits whatever answer the dependency gives to an advisory, including silence. +Its licence, in eleven client repositories rather than in this one. Its reach, +because a dependency that pulls its own graph is not one dependency, and the +count that matters is the transitive one, read rather than assumed. + +Against that, what writing it here costs: the code, the tests, the review, and +the same security response for the core's own account. Where the thing being +replaced is small, well specified, and already has a test somebody would write +anyway, the answer is usually to write it. Where it is a protocol, a parser of +somebody else's format, or a cryptographic primitive, the answer is usually not, +because a wrong implementation of any of the three is a defect nobody sees until +it is exploited. + +## What is refused outright, whatever it is worth + +Five behaviours, each of which overturns a decision this board took somewhere +else, so that admitting the dependency would move a decision without a record. +Carried forward, with +[0243](0243-the-means-a-certificate-is-validated-with.md)'s narrowing of the +fourth written into it rather than pointed at, so that a reader of this record +reads the rule in force. + +A dependency that reaches the network on its own. +[0069](0069-every-host-the-core-may-contact.md) decides every host the core may +contact and #70 is the test that fails when it reaches one nobody configured. A +node with its own client, its own updater, or its own exporter defeats both, and +the defeat is invisible in a diff. + +A dependency that reads or writes the filesystem without being told where. +[0040](0040-the-cache-store-interface.md) puts the storage location in the +client's hands, and a node that picks its own cache directory has taken that +decision away from eleven client authors who each had a reason. + +A dependency that starts a thread the core did not ask for. +[0009](0009-the-concurrency-model.md) says two lanes and nothing else, no work +posted to a shared pool and no timer thread of its own. A node with a background +worker is a third lane the core does not own, cannot size and cannot stop, and +#115's stop call then returns while something is still running. + +A dependency that writes to a log. +[0100](0100-the-diagnostics-interface.md) and +[0071](0071-what-may-leave-through-a-diagnostic-event.md) decide what leaves the +core and in what shape, and a node writing to a global logger is a second exit +for exactly the values 0071 classifies field by field. Narrowed by +[0243](0243-the-means-a-certificate-is-validated-with.md): what is refused is +writing to a log, and linking a logging facade whose sink is absent is not that, +on the condition that the core installs no logger and states that it installs +none. The reasoning behind that narrowing and what it costs are in that record. + +A dependency that carries its own field-bearing surface, which +[0061](0061-the-span-facility.md) supplied by refusing a real candidate rather +than by arguing from a principle. A tracing library's spans carry attributes, so +#71's redaction rule would have to cover a second facility rather than one. The +cost has nothing to do with what the dependency does on its own, and it is the +ground least likely to be noticed at the moment of taking one. + +## A dependency a record already standing requires + +Carried forward unchanged, because it is a rule about worth rather than about +licences. + +[0041](0041-how-a-cache-key-is-built.md) requires a cryptographic digest, +[0105](0105-an-entry-this-version-did-not-write.md) rests on the same +requirement, and [0011](0011-the-language-the-toolchain-and-the-binding-layer.md) +measures that the toolchain offers none. So a landed record already needs a +dependency, and a rule written without that case would refuse the digest under a +clause nobody wrote for it. + +The clause. Where a record that has already landed states a requirement the means +cannot meet, a dependency meeting exactly that requirement is admitted on the +record's authority rather than on this one's, provided it is the smallest thing +that meets it, its licence is in the set above, and none of the five outright +refusals applies to it. What this record contributes in that case is the licence +set and the five behaviours, not the judgement of worth, because the worth was +already decided by the record that stated the requirement. + +The bound on that clause. It admits a dependency for the requirement the record +states and nothing else in the same package. A package offering a digest and a +transport is admitted for the digest only if the transport is separable; where it +is not, the transport is a second dependency and is judged on its own terms. + +## The test tree and the shipping tree + +Carried forward unchanged. They carry different risk and one rule for both is +either too strict for the suite or too loose for what an operator installs. + +In the shipping tree, everything above applies in full. + +In the test tree, the worth test is relaxed and nothing else is. A test-only +dependency is not distributed, so its size on a television, its release cadence +in eleven client repositories and its behaviour on an operator's machine are not +costs anybody pays. What still applies without relaxation: the licence set, +because a licence obligation attaches to what is distributed and a test fixture +can end up distributed by accident; and the five behaviours, because a node that +starts a thread or reaches the network inside the suite is a node that makes the +suite's verdict depend on something outside the run. A flaky gate is the specific +failure, and it is worse than a slow one because it teaches people that red means +nothing. + +What no relaxation reaches: a dependency that is in the test tree today and the +shipping tree tomorrow is judged as a shipping dependency on the day it moves, +not grandfathered by having been there. + +## How one leaves + +Carried forward unchanged. A dependency with no stated removal condition is +permanent, so one is written when it enters, beside the clause that admitted it. + +The condition is written so a reader can look at the world and say whether it has +happened. Three shapes cover almost every case. The means grows the facility: +[0011](0011-the-language-the-toolchain-and-the-binding-layer.md) already names +this for the source of unpredictable bytes, where a stable compiler gaining one +retires the dependency and the client seam together. The requirement disappears: +a record is superseded and what it required is no longer required. The cost +turns: the dependency's transitive count, its size on the smallest target, or its +advisory history crosses a number that was written down when it entered. + +"When we no longer need it" is not such a condition and is refused as one. + +## Where the line lives + +Every dependency carries, beside its entry in the manifest, one line naming the +clause of this record that admitted it and one naming what would retire it. The +manifest rather than a separate document, because a separate list is a thing that +drifts from the graph it describes, and the drift is invisible until somebody +audits it. + +#87 produces the bill of materials, which is where the graph is read back, and +#19 is what refuses a graph that does not match the committed lockfile or that +carries a known advisory. Neither reads this record, and nothing in this +repository refuses a dependency admitted by no clause today. The rule is carried +by the review and by the line beside the entry until something reads it. + +The two entries standing in the manifest cite the superseded record by number and +they are not rewritten here. Every statement they make about a licence is still +true - both members of `MIT OR Apache-2.0` are in the admitted half above, and +`ureq-proto`'s graph reaches no conjunction - so what is stale in them is the +number and not the judgement. That is a residual this change leaves rather than +one it repairs, and it is written here so a reader meeting `0103` beside a +manifest entry knows which record the clause now lives in. + +## The graph as it stands, read against this set + +Nothing in the resolved graph is admitted only by the clause that moves. Read at +the head of the branch this record lands on: + + cargo metadata --format-version 1 --locked \ + | jq -r '.packages[] | select(.name != "flowfin-core") | "\(.name) \(.version) \(.license)"' \ + | sort + base64 0.23.1 MIT OR Apache-2.0 + block-buffer 0.12.1 MIT OR Apache-2.0 + bytes 1.12.1 MIT + cfg-if 1.0.4 MIT OR Apache-2.0 + cpufeatures 0.3.0 MIT OR Apache-2.0 + crypto-common 0.2.2 MIT OR Apache-2.0 + digest 0.11.3 MIT OR Apache-2.0 + http 1.5.0 MIT OR Apache-2.0 + httparse 1.10.1 MIT OR Apache-2.0 + hybrid-array 0.4.14 MIT OR Apache-2.0 + itoa 1.0.18 MIT OR Apache-2.0 + libc 0.2.189 MIT OR Apache-2.0 + log 0.4.34 MIT OR Apache-2.0 + sha2 0.11.0 MIT OR Apache-2.0 + typenum 1.20.1 MIT OR Apache-2.0 + ureq-proto 0.6.1 MIT OR Apache-2.0 + +Sixteen packages, every one of them a single admitted term or a dual offer both +of whose members are admitted. The shrinking set costs this graph nothing. + +That is a reading of one day's graph and not a promise about the next entry. What +changes here is which entries can arrive at all, and the population now refused +is a real one in this ecosystem rather than a hypothetical: an `MPL-2.0` node is +the shape most likely to be proposed and refused under the set above. + +## What this does not decide + +Where the assembled notices for a release live. That is #74's and #87's question, +and the superseded record did not answer it either. + +Whether anything in this repository reads a licence expression. Nothing does. The +set above is applied by the review and by the line beside a manifest entry, which +is what the superseded record already says of itself. + +What the hosting provider's own listing reports for a repository offering two +licences. That listing is a state on the provider rather than a byte in this +tree, and what the tree carries is the two texts at the root and the expression +in the manifest. + +## Why this is written down before the code + +An outbound licence that two artefacts state differently is the cheapest kind of +wrong and the most expensive to leave standing. It is the first thing a client +author checks before writing a line against this core, and until this change the +answer they found was the one that had been superseded on the issue that took it: +four statements of one fact, in the manifest, the readme, the licence file and +the provider's listing, all of them the earlier answer. + +The dependency set is the second half and it cannot lag behind the first. A rule +whose stated ground is a licence the work is no longer offered under is a rule +two readers apply differently, and the direction it gets wrong is the permissive +one: a reader applying the superseded set admits a copyleft node, the node lands, +and a licence obligation is the one class of mistake here that deleting the +dependency later does not repair. Taking it now costs nothing in the graph, which +the reading above measures; taking it after a copyleft node has landed costs that +node and everything resting on it. + +## Alternatives, and what each cost + +**Keep `AGPL-3.0-or-later` and close the question the other way.** Costs nothing +to execute, since the tree already publishes it, and it is what a reader who +never opened #1 would assume. What it costs is the plan: eleven clients this +organisation does not write cannot link an `AGPL-3.0-or-later` core without +becoming that themselves, which is the reason the second answer gives and the one +the first did not carry. + +**`MIT` alone.** Four paragraphs, the shortest thing anybody has to read, and the +most widely understood. It carries no express patent grant, so a contributor +keeps whatever patent claim they hold over what they contributed, and the subject +here is formats and protocols vendors consider theirs. The pair costs one more +file and buys that grant. + +**`Apache-2.0` alone.** The patent grant and the defensive termination without +the second file. It cannot be combined with `GPL-2.0-only` code, and it is the +longer text a small client author reads. Offering the pair leaves that choice to +the recipient instead of taking it for them. + +**`MPL-2.0`, the middle option #1 lists.** Per-file copyleft, so changes to the +core's own files come back and a client linking it does not become `MPL-2.0`. It +costs a per-file header convention, and it puts a source-availability obligation +on eleven client repositories that a permissive expression does not - which is +the same obligation the set above refuses to accept from a dependency, and +accepting it outbound while refusing it inbound is a position that cannot be +argued. + +**Supersede only the licence and edit +[0103](0103-what-admits-a-dependency-and-what-is-refused.md)'s set in place.** +The smallest diff by a wide margin. [0001](0001-decision-records.md) forbids it: +a change to what a record decided is a new record, and the licence set is what +that record decided. Editing it would also erase the reasoning that was available +when it was written, which is what a decision record is kept for. + +**Write the licence record and leave +[0103](0103-what-admits-a-dependency-and-what-is-refused.md) standing with a +pointer.** Cheaper than a full successor, and it keeps the worth test, the +behaviours and the clause in one place rather than restating them. +[0267](0267-a-record-that-narrows-one-clause-of-another.md)'s field is for a +clause narrowed while the rest stands, and this is a premise replaced: the +sentence that derives the set is false under the answer that stands, and a reader +who stops at the header of a record whose central enumeration has reversed reads +the wrong set. The cost paid instead is length, which is this record restating +what did not move. + +## What would reverse this + +A client, or an organisation adopting one, is unable to ship because of a term in +either member of the pair. That is the pair failing at the only thing it was +chosen for, and what replaces it is a record naming the term and the offer that +avoids it. + +The core stops being something a client links, so that neither the outbound +permissive answer nor the eleven-times multiplier behind the dependency set +holds. Both halves rest on that shape, and without it the rule is stricter than +its reason. + +The licence set refuses a dependency that a landed record requires and nothing +admitted by the set can meet. Then the set and the record are in conflict, and +which of the two moves is a decision above both rather than an exception written +into either. + +A dependency admitted under the clause for a standing requirement is measured to +carry more than the requirement, twice. One case is a package judged wrongly; two +is the clause being wider than it reads, and it is replaced by one naming what a +package may contain beside the thing it was taken for. + +Something in this repository begins to read the line beside a manifest entry, for +example under #87 or #19. This record is then superseded by one describing what +is refused rather than what is expected, because a rule nothing refuses is a +suggestion and this record says so of itself. diff --git a/docs/decisions/README.md b/docs/decisions/README.md index b90f495..d592163 100644 --- a/docs/decisions/README.md +++ b/docs/decisions/README.md @@ -71,3 +71,4 @@ their wording, is under `## Decisions` in [CONTRIBUTING.md](../../CONTRIBUTING.m - [0272. The route next up is read from](0272-the-route-next-up-is-read-from.md) - [0291. The provider the socket waits on, and what the wait costs](0291-the-provider-the-socket-waits-on.md) - [0292. The means the core speaks HTTP with, and what it costs](0292-the-means-the-core-speaks-http-with.md) +- [0303. The licence the core is offered under, and the dependency set that follows from it](0303-the-licence-the-core-is-offered-under.md)