From 44329ed3baa6136cceabe19b9bf57c89821f7bf1 Mon Sep 17 00:00:00 2001 From: j-james Date: Tue, 28 Apr 2020 00:41:46 -0700 Subject: Add a "chronology" page detailing Re: Slack --- LICENSE | 668 +++++++++++++++++++++++++++++++++++++++++++++++++++-- README.md | 8 - _config.yml | 2 - assets/compass.jpg | Bin assets/mrbones.jpg | Bin 0 -> 260344 bytes chronology.html | 209 +++++++++++++++++ css/glow.css | 60 +++++ 7 files changed, 918 insertions(+), 29 deletions(-) delete mode 100644 README.md mode change 100755 => 100644 assets/compass.jpg create mode 100644 assets/mrbones.jpg create mode 100644 chronology.html create mode 100644 css/glow.css diff --git a/LICENSE b/LICENSE index 9cf1062..6da0c4a 100644 --- a/LICENSE +++ b/LICENSE @@ -1,19 +1,649 @@ -MIT License - -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. + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2020 j-james + 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 . + diff --git a/README.md b/README.md deleted file mode 100644 index 81d9586..0000000 --- a/README.md +++ /dev/null @@ -1,8 +0,0 @@ -# j-james's website - -:construction: Currently in a state of disrepair :construction: - -- [x] Link other GitHub repositories (math, htmlstuck, etc) -- [x] Configure domain name -- [ ] Use Jekyll again -- [ ] Forestry.io integration diff --git a/_config.yml b/_config.yml index fd5b07b..75b1796 100644 --- a/_config.yml +++ b/_config.yml @@ -1,6 +1,4 @@ title: j-james's website email: jj@j-james.me -description: >- # this means to ignore newlines until "baseurl:" - my beautiful website url: "https://j-james.github.io" github_username: j-james diff --git a/assets/compass.jpg b/assets/compass.jpg old mode 100755 new mode 100644 diff --git a/assets/mrbones.jpg b/assets/mrbones.jpg new file mode 100644 index 0000000..80b7955 Binary files /dev/null and b/assets/mrbones.jpg differ diff --git a/chronology.html b/chronology.html new file mode 100644 index 0000000..cf0dfe7 --- /dev/null +++ b/chronology.html @@ -0,0 +1,209 @@ + + + j-james | chronology + + + + + + Slack: An Obituary +

The Life and Times of the Re: Slack email thread

+
+

It Begins

+

On Friday, December 13, 2019, 3:58 PM [1], Enrique Chee wrote

+

To: spartronics-4915-mentors, Sean Eaton, Kristen Hailzip, Kiyomasa Toma, BCC: Me

+

Hello team,

+

The district has informed me that we must discontinue the use of Slack for the following reasons:

+

Due to the retention and reporting features, BISD has standardized on using Remind for communication purposes. Slack isn't managed by BISD, so we DON'T have any ability to retrieve and retain information like we do with Remind. I understand FIRST Robotics has adopted Slack as a communication tool which it utilizes to communicate with students and mentors as well as organize workload, but it does not meet the guidelines set out by the district.

+

Therefore effective today , I will have to deactivate your membership in our Slack workspace. Next week when meet as a team, we can discuss how to get us on REMIND. [2]

+

If you have any questions, please direct them to Sean Eaton , seaton@bisd303.org.

+

Enrique Chee, +
Physics Teacher/Science Dept.Chair

+

Coach of FIRST Robotic Team #4915 +
Bainbridge High School +
9330 NE High School Road +
Bainbridge Island, WA 98110 +

+

echee@bisd303.org +
Room 316 , 206 780-1358

+

The Captains' Account

+

On Saturday, December 14, 2019, Declan Freeman-Gleason wrote

+

To: Sean Eaton, Violet Advani, Peter Hall, Justice James, Chris Mentzer, Cruz Strom, Enrique Chee

+

Hello Mr. Eaton,

+

The Spartronics team captains have a couple of issues and requests regarding the recent developments with Spartronics' communication tools.

+

After reviewing Remind, we have found that it does not have a number of features which are important requirements for enabling easy, clear communication between team members. Learning and practicing clear communication is a major goal of our team, and we believe that Remind does a poor job of facilitating the type of communication we do because of the following specific reasons:

+
    +
  • Remind increases the difficulty of maintaining channels for different subjects to the point that it would become a significant burden for the team. Although you can create a “class” for each subject, you cannot easily have a chat with the entire class—you must either make a group chat, which requires you to maintain the list of people in the group chat, or you must create an announcement, which does not allow recipients to “reply all” (i.e. it hides their responses for everyone but the sender.)
    • +
  • Remind does not allow “threaded” communication; in Slack, you can create threads under a message, and all responses will be organized in that thread. This can significantly reduce clutter in the chat.
    • +
  • Remind does not allow us to import years of message and file sharing history from Slack; this information is deeply important for the continuity of the team, and using Remind would cause us to lose it.
      +
    • With kickoff in a few weeks, losing access to all of this information would negatively impact our season.
      • +
    +
    • +
  • Remind does not allow us to use notification bots that we had in Slack, like the Google Calendar bot that gave us important meeting reminder notifications, or the RSS bot that gave us notifications from FIRST.
    • +
  • Remind is not in standard use in the FIRST Robotics community.
    • +
+

These issues suggest that switching the team to Remind would be extremely problematic. The captains believe that there are alternatives which meet the school district requirements (auditability of all messages), and Spartronics’ requirements (message import, similar channel and thread features to Slack). One specific alternative is Mattermost:

+
    +
  • Mattermost is self-hosted, so it allows the export of all messages, including private messages, at any time. It is our undersanding that this fulfulls the district's main requiremnt.
    • +
  • Mattermost allows the import of all past Slack messages and files.
    • +
  • Mattermost operates almost exactly like Slack, and has the same channel management and threading features.
    • +
  • Mattermost has bots with comparable functionality to the important calendar and RSS bots we used on Slack.
    • +
  • Mattermost is in use by FIRST Robotics Competition teams, including the 2019 and 2018 world champions, team 254.
    • +
  • We have evaluated Mattermost and its message import features in the past (Declan set up an instance and imported all Spartronics messages and images), and we did not have any problems.
    • +
+

Please let us know what you think of Mattermost, if you have any other questions, or if there are any other requirements for a messaging solution that we missed. We consider this matter to of some urgency, because we need a working messaging option by kickoff on January 4th.

+

Thank you for your support, +
Chris, Cruz, Declan, Justice, Peter, Violet

+

On Monday, December 16, 2019, 9:34 AM, Sean Eaton wrote

+

To: Declan Freeman-Gleason

+

Thank you very much for your input in this matter, and your concerns with the limitations of Remind.

+
    +
  • Our BISD subscription to Remind provides a safe and legal way for BISD staff members, including coaches and advisors, to text students and their families.
    • +
  • When staff are texting students or families, our BISD Remind service is the only method to use.
    • +
  • These communications are public records and subject to request.
    • +
  • All BISD Remind exchanges are archived, and language should be fit for public display on a reader board.
    • +
+

Our District Technology Directory, Kiyo Toma, Mr. Chee, and I will be meeting to further discuss how Slack has been utilized in the past for the robotics team. The time and effort invested into Slack is definitely recognized by the administration. All of the messages I have received from Spartronics regarding Slack have been forwarded to Mr. Toma so he has the information you have provided. Currently, only the student accounts are diabled. Mr. Chee has full access to all content as the administrator, and has full capability to communicate with mentors and other FRC groups with Slack. The team design documents and discussion threads should all be accessible to Mr. Chee.

+

Thank you for reaching out with your concerns and your offer to find an alternative solution.

+

Sean Eaton +
Director of Career & Technology Education +
seaton@bisd303.org +
206-780-1263

+

I A M C A R E E R A N D T E C H N I C A L E D U C A T I O N I N S P I R E D

+

On Monday, December 16, 2019, 11:04 AM, Declan Freeman-Gleason wrote

+

A worrying response.

+

---------- Forwarded Message ---------- + [the above message]

+

Chris Rininger's Quest

+

[meanwhile...]

+

On Friday, December 13, 2019, 5:04 PM, Chris Rininger wrote

+

To: Enrique Chee

+

Is it possible to leave mentors on for a short time in order to retrieve pinned items and key links & files to move to the new system? No time to move things over will carry a pretty big impact - a major setback instead of a minor one.

+

On Friday, December 13, 2019, 5:08 PM, Enrique Chee wrote

+

I am sure it is but I will have to ask the district. We can discuss on Wed.

+

Enrique Chee, +
Physics Teacher/Science Dept.Chair

+

Coach of FIRST Robotic Team #4915 +
Bainbridge High School +
9330 NE High School Road +
Bainbridge Island, WA 98110

+

echee@bisd303.org +
Room 316 , 206 780-1358

+

On Saturday, December 14, 2019, 2:58 PM, Chris Rininger wrote

+

To: Sean Eaton CC: Enrique Chee, Kevin

+

Hi Sean,

+

Enrique, in his message, said to reach out to you with questions regarding this directive. I’m Cc’ing him + Kevin our marketing mentor who may be interested in chiming in. It was the marketing team that originally sought out Slack for the team.

+

There are some potential unintended consequences of this, including LESS visibility to team communications for the coach and the school. I’m going to close with that, though. Please review this email understanding that I’m not pushing back. I’m just providing information you and the HS admin may not be aware of. I’m in no way questioning anyone’s authority here, and we’ll work with whatever mandates.

+

I’ll start with the assertion that Slack is not controllable & monitorable. I looked into that, and actually it is. Coach already has control as Workspace Owner. As far as monitorability, it is possible to set up Slack in a way that a school/owner can monitor all communciations, including direct messages. More information here: https://slack.com/help/articles/204897248-Guide-to-Slack-import-and-export-tools Scroll down to Import and Export Tools by Plan, and you’ll find the following…

+
+

“Export: Workspace Owners and Admins may use Standard Export to export content from public channels. Standard Exports will include links to files, but not files themselves. If you export data from a workspace containing shared channels, only links to files shared by members of your workspace will be included in your export.

+
+
+

Workspace Owners must contact Slack and apply to export content from private channels and one to one or group direct messages. We will reject applications unless Workspace Owners show in each instance (a) valid legal process, or (b) consent of members, or (c) a requirement or right under applicable laws in order to export data.”

+
+

I think a public school will have no trouble satisfying the “valid legal process” and other requirements.

+

So let’s assume, even given the opportunty above, the decision remains that Slack must not be used by the team. The proposal is to use Remind instead because it is a school standard and it is controllable/monitorable by the school. What is missing is… Will it meet the communication needs of the robotics team? A prerequisite question to answer is… What are the communications needs of the robotics team? How are those needs different from the needs of a school class? The latter is the context of Redeem’s application design. If Redeem will not meet the team’s needs, then setting it up could be a net negative because a) it will require precious time and b) the time spent won’t result in the team’s needs being met anyway. In my career, I’ve seen many instances of a piece of software being selected for a team to use without first understanding the team’s requirements. The result is always a lot of time wasted setting the tool up only to find out doesn’t really do what is needed. Having the robotics team set up Remind could be like telling a technical graphics teacher to use Powerpoint as the class’s modelling software, when what is needed is CAD. Apples vs. oranges, despite seeming similar on the surface.

+

So what are the communications needs of the robotics team, and how are they different from a school class?

+
    +
  • A school has top-level admins and is composed of classes. A school class involves teacher, parent, and student roles. Within a class, it is appropriate for a teacher to be the only person able to communicate to everyone, and Remind is set up that way.
    • +
  • The closest analog to a Remind “school” is the robotics team itself, because both have layers of structure underneath the top level. The closest analog to a Remind “class” within the robotics team is the sub-team (like Mechanics or Programming). The first screen shot attached is of a mocked-up Remind school and class I made this morning. It does look like it could work like Slack on the surface, but digging deeper…
    • +
  • The robotics team is composed of sub-teams that operate via collaboration across all members (including students and mentors). While there are sub-team leads, when it comes to dialog, the newest freshman needs to be able to initiate a conversation with the whole group. (“I’m working on X, and I’m encountering this problem. What should I do?” Or… “I found this great resource! Take a look!”). While there are group chats of up to 9 people within a Remind class, only teachers seem to be able to initiate whole class communications, and students seem to not be able to reply. See the second attachment for the view of a student within Remind.
    • +
  • In order to bend Remind to the team’s needs, maybe each student could be set up as a teacher of each class (sub-team) they attend, but I assume that will enable other privileges that would be inappropriate. The group chat thing won’t be enough, because sub-teams are attended by dozens of people (including non-members) for effective sharing of information. The limit of 9 people per chat would create a stifling lack of visibility within each sub-team.
    • +
+

So it looks like Remind could be set up & used for basic announcements and communication between coach and students/parents, but it will not be able to meet the team’s communication needs previously met by Slack.

+

In that case, how will those needs be met instead? This is where we arrive at the risk of unintended consequences. My guess: What will happen is… Students will shift to the Discord platform, registered using non-school email addresses. I think many, many of them are already on this platform (originally for video gamers but now super widely used by teens generally). The consequences will be less visibility, less control, etc. than with Slack. Also, mentors will be out of the loop since few (or maybe none) are on Discord. Mentor-student collaboration is possibly the most valuable thing about the robotics team, and the negative impact of having no communication platform that meets those needs will be significant.

+

Recommendations:

+
    +
  • If it is possible, look into the Slack link enabling administrative monitoring. A path forward involving no need to switch communication platform two weeks before the season starts would be great.
    • +
  • If that is impossible, then Microsoft Teams is another option that has full team collaboration communications like Slack (anyone can initiate a dialog), and since I work at Microsoft, I know it is possible to set up Teams with monitoring and controls by admins.
    • +
  • Maybe there is a setting that the Remind company has on the back end of things that make a Remind class more like a Slack channel (i.e. allowing any member to initiate dialog with all others). If not, then I do not recommend even spending the time setting up Remind for robotics (other than maybe as a way for general announcements from coach to students and parents).
    • +
  • If none of the above are possible, then I think we may need to go back to something cruder like email distribution groups for all sub-teams, so any member can initiate conversation with all other members. This will be much less efficient than Slack (lots of email in the inbox – students who don’t use email…), but it could work in a pinch. And part of this also will be accepting the consequences of students using their own personal Discord accounts, invisible to all the grown ups. Given than risk, it seems worthwhile to look at the other options.
    • +
+

Thanks for reading – I hope we find a comms solution that can work for both the team and the school admin.

+

--Chris

+

On Monday, December 16, 2019, 9:32 AM, Sean Eaton wrote

+

Thank you very much for your input in this matter, and explaining the communication needs of the Robotics team.

+
    +
  • Our BISD subscription to Remind provides a safe and legal way for BISD staff members, including coaches and advisors, to text students and their families.
    • +
  • When staff are texting students or families, our BISD Remind service is the only method to use.
    • +
  • These communications are public records and subject to request.
    • +
  • All BISD Remind exchanges are archived, and language should be fit for public display on a reader board.
    • +
+

Our District Technology Directory, Kiyo Toma, Mr. Chee, and I will be meeting to further discuss how Slack has been utilized in the past for the robotics team. The time and effort invested into Slack is definitely recognized by the administration. All of the messages I have received from Spartronics regarding Slack have been forwarded to Mr. Toma so he has the information you have provided. Currently, only the student accounts are diabled. Mr. Chee has full access to all content as the administrator, and has full capability to communicate with mentors and other FRC groups with Slack. The team design documents and discussion threads should all be accessible to Mr. Chee.

+

Thank you for reaching out with your concerns and your offer to find an alternative solution.

+

Sean Eaton +
Director of Career & Technology Education +
seaton@bisd303.org +
206-780-1263

+

I A M C A R E E R A N D T E C H N I C A L E D U C A T I O N I N S P I R E D

+

On Monday, December 16, 2019, 11:53 AM, Sean Eaton wrote

+

Thank you Chris. I have setup a meeting with Mr. Chee and Mr. Toma to discus the options you and other members of Spartronics have put together. It would be very helpful to have a full list of the FRC team’s communications solution requirements, with input from student leaders and other mentors.

+

Sean Eaton +
Director of Career & Technology Education +
seaton@bisd303.org +
206-780-1263

+

I A M C A R E E R A N D T E C H N I C A L E D U C A T I O N I N S P I R E D

+

And Our Paths Collide

+

To: Spartronics Mentors, Spartronics Captains, Enrique Chee

+

On Tuesday, December 17, 2019, 1:45 PM, Chris Rininger wrote

+

Hi mentors and captains,

+

In a follow-up to Mr. Eaton, I offered to try to work with you all to pull together a list of the team’s requirements of a communications platform. He responded that this would be helpful.

+

I quickly created a Google sheet for this purpose and seeded it with a few requirements. I’m sure there are plenty more we can add.

+

Please review/contribute. Captains, if you want to take the lead on this, great! I do think this can help make the case for keeping Slack or at least for finding a tool that does meet the team’s needs.

+

Link: https://docs.google.com/spreadsheets/d/1j82Gi5tXfKcoUaoPa4M7XcvB5hIxdc8HVUw_ivhJC3w/edit?usp=sharing

+

Thanks, +
Chris

+

On Tuesday, December 17, 2019, 11:40 PM, Chris Rininger wrote

+

Thanks to those who contributed.

+

Cruz also shared the proposal the captains sent Mr. Eaton.

+

I’ve tried to merge everything together into a single list of around 20 requirements (many from Binnur – thanks 😊). I’m going to go ahead and share the link to Mr. Eaton, since I believe the meeting may be tomorrow. If anyone sees obvious gaps/inaccuracies, please go ahead and edit the sheet.

+

--Chris

+

On Wednesday, December 18, 2019, 8:11 AM, Kevin Hawkins wrote

+

I have a thought to share:

+

I do not think Sean E. is the right person to make our case. He’s not a policy maker, just following it.

+

Since time is of the essence, I believe we need to take this directly to the Asst Superintendent Erin Murphy, and loop in the Tech person for this District as I fear the higher ups won’t understand the nuisances of Slack.

+

Remind was implemented, as I understand it, because Coaches were communicating directly with student athletes. When there was an incident (well publicized), the District couldn’t easily retrieve the communications as they were on personal devices.

+

We focus on addressing that and we should be able to make our case.

+

My 2 cents

+

Kevin

+

On Wednesday, December 18, 2019, 9:07 AM, David Schiederman wrote

+

Talking directly with the district would probably be helpful. +
The question I have is, do we have an actual list of the districts requirements?

+

For instance, in the financial industry, especially where stock trading is involved, no messaging system can be used that does not do active monitoring and alerting on key words that might suggest insider trading. I've installed a couple of them in a previous life.

+

The same is true for education, but triggers on suggestions of harming others or harming oneself. While it focuses on the safety of the students, it's also a liability issue. Pulling logs or reports after the fact may not be sufficient. The district may also need to try and prevent an event.

+

David

+

On Wednesday, December 18, 2019, 3:20 PM, Declan Freeman-Gleason wrote

+

Another thing to add:

+

When the captains communicated with Mr. Eaton, we provided a clear option for the district: let us use Mattermost as an alternative. I think that it’s very important that we not only list requirements, but list also some tools that actually meet our requirements.

+

Having a specific tool that they can OK is easier for the district, and will hopefully expedite the entire process. In the email I sent to Sean Eaton (which I will forward to the mentors mailing list), the tool the captains suggested was Mattermost. Because of this, I’m going to add Mattermost’s name to the requirements spreadsheet as an alternative. I will also add Slack, because it appears that there is a private message export capability on request. I think this will give us better control over the discussion around what we are allowed to switch to, especially if we cite Mattermost/Slack (with reporting capabilities) as our specific preferred alternative in all of our communications.

+

On Wednesday, December 18, 2019, 4:18 PM, Declan Freeman-Gleason wrote

+

To: Chris Rininger, spartronics-4915-mentors, Declan Freeman-Gleason, Cruz Strom, Justice James, Violet Advani, Peter Hall, Chris Mentzer

+

Below is the email the captains sent to Mr. Eaton:

+

[the email the captains sent]

+

Back at it again with Chris Rininger

+

To: Sean Eaton

+

On Thursday, December 19, 2019, 11:36 AM, Chris Rininger wrote

+

Hi Sean,

+

The Conversation feature in Remind could help during the time between now and when we have a more Slack-like solution. It would *really* help to increase the number of people who may participate in a converstion from 9 to unlimited (or at least to, say, 25). By doing this, entire workgroups could fit into a Conversation.

+

Would you please look into whether or not this is possible?

+

Thanks! +
Chris

+

From Friday, December 20, 2019 [3] to Saturday, December 28, 2019

+

[the note desolation plays...]

+

On Sunday, December 29, 2019, 11:46 AM, Chris Rininger wrote

+

Hi Sean,

+

Just checking on this. A larger max number of people per Remind conversation (ideally unlimited so a whole “class” can be included) could help a lot. Maybe there is a setting at the “school” level accessible to the top-level admin of the school’s or the district’s Remind account?

+

Communications about Slack, Remind, etc have gone quiet over holiday time, but the needs met by Slack & not by Remind (or email) are still weighing heavily on our team. Given the importance of not-in-person communications & students’ reluctance to use email, the season is at stake.

+

Whatever can be done to expedite reinstating Slack (via No DM user agreement or whatever it takes) just for this season, please continue pursuing it with urgency. Beyond this season, there is time to look at other options, of course.

+

Thanks, +
Chris

+

On Thursday, January 2, 2020, 9:56 AM, Chris Rininger wrote

+

To: Justice James

+

Hi Justice, any update on creating the distribution lists and sharing them with the team? Thanks!

+

--Chris

+

Footnotes

+

[1]: 4PM on a Friday. :/

+

[2]: Chee has various idiosyncrasies - such as a tendency to put spaces around punctuation - that let us know, fairly accurately, what is and isn't written by him.

+

[3]: The last day of school before break.

+

+ diff --git a/css/glow.css b/css/glow.css new file mode 100644 index 0000000..b4d331b --- /dev/null +++ b/css/glow.css @@ -0,0 +1,60 @@ +body { + font-family: monospace; + background: #263238; + color: #D0D0D0; + font-size: 16px; + padding: 10px; +} +h1, h2, h3, h4, h5, h6 { + color: #00AFFF; + font-weight: bold; + font-size: 16px; +} +span { + background: #5F5FFF; + color: #FFFF87; + padding: 5px 10px 5px 10px; + border-radius: 5px; + font-weight: bold; + line-height: 30px; +} +h1::before { + content: "# "; +} +h2::before { + content: "## "; +} +h3::before { + content: "### "; +} +h4::before { + content: "#### "; +} +h5::before { + content: "##### "; +} +h6::before { + content: "###### "; +} +strong { + font-weight: bold; +} +a { + color: #00AF5F; + font-weight: bold; + text-decoration: none; +} +a::after { + content: " " attr(href) " "; + color: #008787; + text-decoration: underline; +} +blockquote { + border-left: 2px solid #D0D0D0; + padding-left: 15px; +} +img { + width: 100%; + height: auto; +} + -- cgit v1.2.3-70-g09d2