From 8c297a0c4638a905bde799a97c07777b2256fc1c Mon Sep 17 00:00:00 2001 From: Jason Self Date: Sat, 29 Jun 2019 21:11:25 -0700 Subject: [PATCH 1/1] Add The Aven --- COPYING | 674 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ aven.txt | 501 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 1175 insertions(+) create mode 100644 COPYING create mode 100644 aven.txt diff --git a/COPYING b/COPYING new file mode 100644 index 0000000..f288702 --- /dev/null +++ b/COPYING @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 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 General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is 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. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + 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. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + 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 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. Use with the GNU Affero General Public License. + + 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 Affero 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 special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU 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 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 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 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. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU 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 General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + 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 GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. diff --git a/aven.txt b/aven.txt new file mode 100644 index 0000000..55089bd --- /dev/null +++ b/aven.txt @@ -0,0 +1,501 @@ +$-- Copyright (C) 2019 Jason Self +$-- SPDX-License-Identifier: GPL-3.0-or-later + +You can redistribute and/or modify this under the terms of the GNU +General Public License as published by the Free Software Foundation, +either version 3 of the License, or (at your option) any later +version. + +> "Space isn't lonely; it's all about perspective. You run a ship long +> enough, and you're bound to collide with something out there in the +> dark." --Captain Isaac Marshal, 1091 kNA. + +Third shift was always a pain as far as Hector was concerned. It was +bad enough to miss out on precious sleep while the rest of the ship +dozed comfortably in their bunks, but what really killed him was how +boring it was. No coordinates to plot, no adjustments to make, no +orders to follow. I can't believe I'm wishing for someone to order me +around, he grumbled to himself mentally. Telltales flickered on the +control station in front of him indicating the ship's status. +Everything was running smoothly, just like it had been yesterday, and +the night before, and the one before that. He leaned back in his chair +and propped a foot up on the console. Napping on watch was strictly +forbidden, but it wasn't like anything was going to happen anyway. + +At least, that's what he was in the middle of telling himself when the +beeping started. A light changed from green to pulsing yellow, and two +more that had been previously unlit now highlighted the contours of +his face with a bright blinking red. The sound of his feet hitting the +floor echoed through the small bridge as he began to manipulate the +controls. Something had set off the proximity alarm. They weren't due +at the trading post for another week, so this was definitely a +problem. Passive sensors couldn't tell him anything he didn't already +know - there was something out there big enough to endanger the ship +and it was statistically likely that they were going to hit it if he +didn't do something. Reaching across the console, his first order of +business was to get a second pair of hands at the controls. And heap +this responsibility on someone else, he thought, cursing his earlier +desire for something to do. "Captain to the bridge. I repeat, captain +to the bridge," his voice echoed through the ship's PA system. To his +credit, his tone sounded much calmer than he felt. + +Cry for help accomplished, he began to frantically flip switches +across the board. Screens lit up as the active lidar scans began +reporting a more detailed picture of the space around the ship. Not an +asteroid or a comet, Hector confirmed. Not a planet, either, which at +least meant they hadn't accidentally drifted off course during his +shift. He couldn't decide if that was a silver lining or not. + +"Status," came a gruff voice from over Hector's left shoulder as he +continued to probe the system. + +He didn't have to look back to recognize who it belonged to. "Unknown +contact, sir, tripped over our passive sensor bubble one minute and +thirty-seven seconds ago. Might be space debris, or a derelict, but +all I know so far is that it's not natural and it's on a collision +course," reported the watchman. + +"Well get us off a collision course, then. We can worry about what it +is after," the captain replied. Grey haired but physically fit enough +to make anyone give second thought to antagonizing him, the man held +an imposing presence. + +"Aye aye, captain. Adjusting course by two degrees, vertical," Hector +acknowledged. Turning left or right would have potentially served the +same purpose, but even small changes in angle would exponentially +increase their travel time to the trading post over a long enough +distance. Better to go above or below whatever this object was and +recalibrate their y-axis accordingly later. + +Another body plopped into the seat at the station to Hector's right; +this one a mess of gangly limbs and thick-rimmed glasses. "Can't leave +you alone for more than a few hours without you getting bored and +putting us in a game of chicken with the nearest planet, can we, +Hector?" taunted the crew member. + +"Shove off, Liz, it's not a planet and I didn't do anything," retorted +Hector. + +Liz, short for Elizabeth - although she would try and convince anyone +she met it was short for Lizard - snorted in amusement at Hector's +exasperation. "Enough of that, you two," reprimanded the captain. +"Hector, you're chair one. Maintain pilot's duties. Liz, chair two, +scanners. Tell me what we're dealing with here." + +A chorus of "Chair one, aye," and "Chair two, aye," met the captain's +orders before the bridge fell into a professional silence. They +weren't a military vessel by any means, but there was a discipline to +the crew that came innate with the hazards of running a salvage ship. +It was dangerous work. People died with little to no warning when care +and attention to detail weren't heeded. Jokes and a lack of formality +were tolerated but, when necessary, the Aven became the tightest run +ship in the sector. + +"Might be another ship, captain," Liz reported after just a few +moments. + +"Distress signal?" + +"Negative, sir. There's no emissions coming off that boat. No beacon, +no communications, nothing. Their engines aren't even lit - that's why +the computer had to take a minute to decide what it even was. The +non-organic shape triggered the funny-business alarms, but whatever's +over there is cold as a rock," she explained. + +Sensing a bonus payday, Hector turned to face the captain. "Sounds +like a salvage opportunity to me, sir," he said, hopefully. "Should I +slow us down?" + +Sitting with his chin resting on one hand like The Thinker made flesh, +the captain didn't reply immediately. Expectant silence filled the +bridge. Finally stirring, he shrugged slightly and said, "Bring our +relative velocity to zero, match course, and give me an estimate on +how much time this is going to add to our delivery date." + +"Aye, aye, sir," Hector replied with a grin. Bending to the task, he +began to manipulate the flight controls. From an outside perspective, +the Aven made a sharp 145 degree turn before flipping backwards and +firing its boosters to apply the brakes. Inside, they felt no shift in +gravity from their seats. "Computer says that - not counting any time +we spend salvaging - re-accelerating and course correcting will add +roughly two days to our trip, sir," the pilot reported as they +completed their maneuver. + +"Hopefully this is worth the delay," the captain mumbled in return. +Neither Hector nor Liz knew if he was speaking to them, or to himself, +so they agreed through their silence as they continued to monitor +their respective stations. + +Time seemed to slow down now that the initial rush of activity had +passed. It would be a couple hours until they came alongside the ghost +ship. Liz had wandered off somewhere, only to return with half a +ration bar between her teeth. "Mith anthn?" she tried to vocalize. + +Not bothering to look up from his console, Hector asked, "What?" + +"I said, did I miss anything?" + +"Nadda. We're still pinging 'em every fifteen minutes or so, but +nobody is picking up. Starting to look like she really is abandoned." + +"Did we ever think she wasn't?" Liz replied. + +"We shouldn't take anything at face value out here," interjected the +captain. "Liz, go wake up Chen and fill him in." Liz looked like she +was about to protest the fact that she'd just sat back down, but +thought better of it. Leaving the cabin, she went to wake the final +member of the salvage ship's crew. Chen was, for lack of a better +term, the muscle. Any operation that put suits outside the airlock had +Chen in the lead. He'd grown up on a heavy gravity world, and while he +wasn't the smartest spacer in the sector, his reaction times and his +considerable strength had saved everyone's life at least once. + +A fresh beep came from Hector's station. Glancing down, he pressed a +few buttons before turning to address the captain, "Sir, the derelict +is in visual range." + +"Shunt it over here, then," the old man replied. Moving a gimbal that +contained a screen towards himself, he waited for the relevant data to +appear on his command station. Numbers began to pour across the +display. Swiping away from the hard data on ship mass and other +minutiae, he brought up a graphic of the ship itself. Stubby and +bulbous, it reminded him of a collection of mushrooms growing off of +some central log structure. There was no obvious front or back, or any +visual place for any kind of thruster or engine. Stranger still was +the color. The nearest star shining light on their little piece of the +galaxy was a yellow dwarf a few hundred million klicks away, and it +bounced off the hull of this ship like an iridescent beetle. After a +moment of additional calculation, the computer suggested a depression +in the hull that was - as accurately as it could guess - a point of +entry. "This thing smells fishy as all hell, but anything this weird +is probably worth a decent chunk of coin, too," the captain thought +out loud. + +Before Hector could discuss the suspicious nature of the vessel +further, Liz and Chen returned. Suited in standard EVA gear, the bulky +white outfit made the small bridge seem even more crowded than it +actually was. "We're ready whenever you are, captain," Liz said. +Grunting in acknowledgement, the old man stood and made his way +towards the back of the ship to find his own suit. Standard procedure +would have one man remain behind to mind the Aven, in this case +Hector, while the rest performed an initial valuation and then got to +looting.Silently happy to be the one left behind, Hector wanted +nothing to do with the strange ship now that he'd had time to study it +more. Humanity knew that they weren't alone in space. Encountering the +unknown wasn't the issue, not exactly. There was just something +unsettling about the design of the ship. Something inherently wrong, +like how certain patterns and colors would awaken an instinctual +wrongness - a genetic memory to ward off dangerous behavior. Stay away +from that poisonous creature, the brain says, you've never seen one +before, but you know it's trouble. + +Liz and Chen wandered back out of the bridge as the moment of truth +drew nearer. "Testing, one, two, can you hear me, Heckler?" Chen's +baritone voice came through the console. + +"Don't call me that," Hector replied, holding down the transmission +button. + +No laughter came through the comms to taunt him, but he knew that Chen +and Liz were having another chuckle at his expense. Being the newest +member of the crew came with the expected downsides, but he couldn't +help acting the way he did. Heckler had stuck as a nickname after his +second ever salvage job, when he constantly tried to warn Chen how +irresponsibly dangerous he was being. The captain would have probably +reigned the behavior in eventually, but it was obvious that he +wouldn't get involved if he didn't need to. Chen wasn't entitled or +inherently rude, but it was easy to lose his respect by over-managing +him. The captain knew that. "Thirty seconds until airlock cycles," +reported the familiar, commanding voice. Speak of the devil. "We won't +be deploying the tunnel or trying to pressurize against their hull. +Too uneven, and we don't even know if their atmosphere plays nice with +ours. Suits will be on tethers until I say otherwise." + +Hector didn't need to reply unless he was asked a specific question or +the computer provided him with data the captain needed to hear, so he +kept the line clear and just listened. Mentally counting down the +seconds, he imagined he could feel the airlock opening as he hit zero. +It would have been entirely in his imagination, of course. Small white +figures emerged from the side of the Aven as he watched on one of the +close-range visual sensor screens. Each suit trailed a braided metal +harness that connected them to the open airlock door. They could +retract themselves manually at any time, or Hector could choose to +pull everyone back with the big red emergency button on his console. +It had been drilled into him over and over that no matter how anxious +he got, he shouldn't touch that button unless he was ready for the +captain to physically obliterate him. So far he'd managed to resist +the urge. + +"Door's locked. Should we try knocking?" Chen asked as they +congregated around the area the computer had decided was an entrance. +Without waiting for an answer, he pulled a small laser welder from his +tool belt and ignited the tip. + +"Careful, if that ship's pressurized, you might blow yourself away +when you put a hole in the hull," Hector reminded him, unable to +resist his need to interject on the quiet comm line. + +A hand waved on the tiny screen, and Hector was pretty sure that Chen +was flipping the camera the bird. "This is why you're a heckler, +Heckler." + +"The door, Chen," the captain's voice overruled any dispute before it +could escalate. Hector stilled in his chair, and Chen went back to +preparing his welder. Once he had the beam tip at a satisfactory +length, he went to work, cutting along a slight depression that could +have been the seal of a door. Or it could have been a fancy engraving +of the ship's name, for all we know, Hector thought to himself. The +Aven had actually been the Scavenger at one point in time, after all - +at least until the paint had worn off the front and back ends of the +label. + +A few tense moments later, and a man-sized hole had opened up on the +side of the foreign craft. If the interior had been pressurized, +they'd either cut into a pocket of empty space between the hull and an +interior hallway, or the pressure was so low that it had simply leaked +out through the cut. One by one the shapes of the three salvage +operators disappeared into the hole, leaving Hector to stare at their +tether cables. "Hallways are empty. Clean, though, almost like they've +been recently maintained. Everything's that same strange rainbow hue +in here," Liz narrated for Hector's sake. "Doors every twenty meters +or so. Slightly smaller than human average. Good thing Chen's head +isn't too full since he's likely to knock it at least a couple times +in here." + +"At least I don't go to school for eight years only to end up on a +salvage ship," Chen retorted. + +"Low blow!" + +Chuckles ensued as the good natured ribbing subsided. Hector was glad +they were having a good time, because he was a ball of nervous +anxiety. After a few moments of radio silence, he began to grow even +more uneasy. "Guys, you still there?" he asked. + +Static crackled for a second before the response came though. "-at the +end of the hall. Going to crack it with the welder and hope the bridge +is on the other side," Chen said through the fuzzy connection. + +"You're breaking up," Hector advised, "Partial copy on your last." + +He was greeted only by more static, with the occasional flare of +volume. This is absolutely the last thing I need, he thought, glancing +at the big red emergency button. They weren't quite in 'worth getting +obliterated over' territory yet, but the urge was definitely rising. +After another two minutes of no contact, he stood from his chair and +began pacing. With the captain's chair and the two console stations +jutting up in the middle of the room, there wasn't much room to work +off his stress. As he lapped the room for the third time, "Hector!" +shouted out over the speakers, followed by garbled white noise. + +Three quick, long strides put him in front of the console. Slamming +his hand down on the transmit button, he asked, "Say again, I repeat, +say again." Looking frantically over his screens while he waited for a +response, movement caught his eye on the visual of the outside of the +ship. Something dark was crawling around on the outside of the other +ship's hull. What the hell…? he thought, moving to try and adjust the +zoom. Before he could refocus the camera, however, one of the tethers +went slack, and his attention was drawn back to the entrance. Someone +slowly drifted out. Maybe they knew about the dark figure too, and +were going to investigate? No… there was something too stiff about the +way they were floating. Then their figure rotated, and Hector saw the +large red blotch on the front of the crisp white suite. "Oh, fu-" + +A loud bang on the Aven's hull interrupted him. Flinching, he glanced +at the door leading towards the back of the ship. His first instinct +was to seal the compartments between him and the airlock. Halfway to +the first set of doors, he realized he was acting out of order in his +panic, and turned back to slam the retracting button on the tethers. +The other two lines hadn't gone slack, and he could only hope that he +was rescuing live people right now and not reeling in corpses. This +was so not part of my contract, he whined to himself as he ran towards +the back of the Aven. Through the galley, crew bunks, and medical, +each room passed like a blur before he arrived at the airlock. +Engineering was on the far side of the hall, but there wasn't anything +he could do to seal that without locking himself in the back of the +ship. Each section was divided by a large bulkhead door. Normally, +these doors would automatically seal in the event of an atmospheric +breach to a part of the ship. Now they would act as buffers between +himself and whatever was out there. + +Yanking hard on a bright yellow handle caused a cacophony of gears and +counterweights to groan momentarily. Each door started to slide shut +slowly at first, then picking up speed to slam closed after a few +seconds. When was the last time these things got serviced? Hector +wondered. His fear was making his reactions sarcastically inane, but +he couldn't help it. How was he supposed to process what was going on +outside? Making his way back through each individual area, he repeated +the routine. Pull the lever, confirm the door seals, move on. + +Once he made it back to the bridge, he went back to the screen showing +him the situation outside. The outside of the other ship's hull was +now covered in dark figures. It almost looked like they were a part of +the iridescent pattern; like black polka spots swarming and coalescing +along with the rainbow hues of the smooth, bulbous exterior. "Screw +this," Hector said out loud, grabbing at the pilot's controls. +Engaging the thrusters while people were still outside on tethers was +a big protocol no-no, but he didn't care at this point. Engines flared +and the ship kicked away from the assumed derelict. "Can anyone hear +me? Are you guys there?" he asked as he flew, hoping that whatever had +been jamming their communications wouldn't affect them any more. + +Only silence replied, and a grim expression set itself on Hector's +face. He could check the airlock camera later. His first priority was +getting the hell out of Dodge. Another bang sounded somewhere against +the hull. Had one of those things managed to jump between the two +ships before he'd escaped? The Aven didn't have any guns on board. +Hyperventilating, Hector decided to try and run a series of sensor +scans on his own ship's hull. There would be some interference from +the overly short range, but he should still get something. Data began +scrolling across his screen. Metal composites, radiation, things that +you'd normally find on the surface of a spaceship. There. Something +organic, carbon-based, unknown origin. Whatever that was, it was +hitchhiking, and he wanted it off. + +"Did you seal these doors, you asshole?" Liz suddenly shouted through +the comm net. + +Nearly jumping out of his seat at the sudden sound, Hector yelped +embarrassingly. Good thing he wasn't transmitting unless he had the +button held down. He cleared his throat, and replied, "You're alive! +Yeah, I sealed them. I don't know what you guys found out there, but I +didn't want one of them getting in here." + +"Well we are out here and we want in," Liz said angrily. + +Hector wanted to snap at her for laying into him when they were +obviously dealing with bigger problems right now. Instead he asked, +"Who's hurt? I saw someone was injured on the video feed before I +pulled you all in." + +Quiet filled the bridge and Hector was afraid that the radio had cut +out again when Liz finally said, "Chen didn't make it. I'm fine. So's +the captain, but he's unconscious. Knocked his head when you yanked us +out." + +Hector took a deep breath. He was prepared to face casualties as a +part of life on a salvage ship, but not like this. Not from a hostile +force. Speaking of hostile forces… "Liz, one of those things is on the +Aven's hull, I'm pretty sure. Close that outer airlock door if you +haven't already. I'll come back and let you farther in soon." + +"Soon better mean 'I'm walking back there now and the only reason I'm +not replying is because I can't stay and press the comms button'," she +replied, a note of fear undercutting her snark and anger. + +Manually unsealing each door took a lot longer than closing them +initially had. Each one struggled to fully open. The one between the +bunk room and the infirmary didn't want to open at all, and Hector had +to scrounge around for something to pry at the gap with. Settling for +a metal tube that had originally acted as a curtain rod to separate +the ship's restroom from the common area, he managed to make a gap +wide enough to slip through. Please, please don't close again, he +prayed as he finished crossing through to the other side. These +bulkheads didn't have portholes, but he could imagine Liz standing on +the other side of the door fidgeting impatiently. He pushed the +emergency lever back up into its cradle and waited. At first nothing +happened, then the servo-mechanisms cranked to life and began to +retract. + +Liz had already moved Chen's body and the captain's unconscious form +from the airlock proper to the small hallway between medical and +engineering. "About time," she said critically. Her helmet was off, +but she was otherwise still dressed in her bulky EVA suit. Same with +the captain. She hadn't bothered to remove Chen's, and Hector decided +that was fine by him. + +"Let's get the captain on the other side of this door, and close it up +again," he said as he moved to position himself by the older man's +legs. Liz took his arms, and together they hobbled him through the +door. More banging echoed through the hull, and Hector crossed his +fingers that this thing didn't have the strength to breach the metal +shell on its own. "What happened over there, anyway? I lost contact +with you guys and the next thing I know Chen's body is floating out in +front of my camera." + +Liz's gaze was unfocused, and when she started to reply it sounded +almost detached. "We started cutting on a door we thought might lead +to the front of the ship, but it was filled with these creatures. We +don't know if it was the bridge, a dormitory, or even a brig, but they +moved fast. Chen was at the front, of course, and one of them stabbed +him with a spear-looking thing. The captain threw a salvaging charge +at the entrance and we started booking it back down the hallway. +Explosion must have taken out at least ten of the suckers, but after +they regrouped they started coming after us on the floor, the walls, +the ceiling…" She stopped talking, staring down at the captain's limp +form. "He started pulling on Chen's tether, trying to get him out from +behind the swarm, but we took a wrong turn and got herded deeper into +the ship, so he gave up. I guess the swarm must have finished carrying +his body the rest of the way out the front door. Then you pulled us +back, right through the pack. It was like a haunted house roller +coaster." + +Hector didn't know what to say. Deciding to focus on what he could do +here and now, he gestured towards the medical exam table in the middle +of the room. "Let's get the cap up on there and make sure he doesn't +have a concussion or anything." Liz nodded wordlessly. He'd need to +keep an eye on her, too. Watch for deeper symptoms of psychological +shock. But right now he needed her help, and maybe giving her +something to do would help distract her. More banging against the +hull. "Liz, I need you to take care of the captain. I'm going to try +and throw our hitchhiker off the ship." + +She nodded again, moving mechanically as she pulled up a diagnostic +screen to check the captain's vitals. Hector quickly walked back +towards the bridge, determined to do whatever he had to to shake their +unwanted guest. Settling into the pilot's seat with a calm smoothness +that concealed the knot in his gut, he began flipping switches to warm +up various thrusters. Salvage ships were built to make minute +adjustments while working around dangerous conditions, and he was +going to abuse that fact now. Putting the Aven through an evasive +course of twists, rolls, and other high-g maneuvers was easy enough to +start. The hard part came when the internal gravity generators +couldn't keep up with the quick and random changes that he was +initiating. He began to feel his body being pulled around as he bucked +the ship like a wild bronco. Inertia strained, and warning lights +began to flicker on as he kept stressing the system. Maneuvering +thrusters burned out when they competed to push the ship in opposite +directions, victims of Hector's inability to precisely keep track of +every switch he was flipping in an effort to move as randomly as +possible. The hull itself began to groan. Another warning light +flickered red; this one telling him that if he kept his antics up, +he'd lose integrity. + +Forced into easing up on his whipping about, he flipped a master +switch. All of the thrusters killed themselves at once, and the ship +settled into calmness. They were probably rotating wildly, but it was +all in one direction and the internal gravity could handle that. No +banging greeted him when he listened intently. Time to run another +scan of the hull. Fingers crossed, he started the process. "Well?" Liz +asked as she appeared behind him. + +"We'll know in a second. How's the captain?" + +"He's going to have one hell of a headache when he wakes up, but he'll +be fine," she said. Between riding out the gravity dancing, and +working the medical systems, she appeared to have recovered some of +her composure. + +Data once again streamed onto the console screen, and Hector looked +for the telltale organics. Nothing. "We're clear," he breathed a sigh +of relief as he leaned back in his chair. + +"Thank God," Liz said, echoing the gradual relaxation that seemed to +sweep throughout the ship. + +Bending forward to work the console once more, Hector began the +arduous process of resetting their destination. After their impromptu, +erratic, off-course trip, the computer struggled to re-calibrate their +ETA to the trading station. "Might be two weeks instead of one, at +this point," he mused out loud. + +Liz settled into the chair next to him, closing her eyes and propping +her feet on the console. "It could take a month, for all I care, as +long as the trip is nice and boring," she said idly. Amen to that, he +thought, glancing at a blinking light on his console. Labelled +'Transmitting,' it sat next to a looped video recording playing +innocuously on his screen. Bulbous shapes of rainbow sheen stared back +at him, along with bright green text showing a set of coordinates, and +a warning. Hopefully no one else would run afoul of the hostile +species any time soon. Chances were low that the message was even +necessary. Space was a big place, after all. \ No newline at end of file -- 2.31.1