From 05b44ed99ded6a62b21600334a989dafb0ca3b9f Mon Sep 17 00:00:00 2001 From: jpl-jengelke Date: Mon, 8 Jan 2024 05:29:40 -0800 Subject: [PATCH 1/2] Slim Infusion: Add baseline SLIM templates with core information. ... --- .github/ISSUE_TEMPLATE/bug_report.md | 43 ++ .github/ISSUE_TEMPLATE/feature_request.md | 34 ++ .github/PULL_REQUEST_TEMPLATE.md | 13 + CHANGELOG.md | 701 +--------------------- CODE_OF_CONDUCT.md | 135 +++++ CONTRIBUTING.md | 350 +++++++++++ LICENSE | 216 +++++++ 7 files changed, 796 insertions(+), 696 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 CODE_OF_CONDUCT.md create mode 100644 CONTRIBUTING.md create mode 100644 LICENSE diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 00000000..c44e609d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,43 @@ +--- +name: Bug Report +about: Report a bug to help us improve +title: '[Bug]: ' +labels: 'bug' +assignees: '' + +--- + +**Checked for duplicates** + +> Have you checked for duplicate issue tickets? + +- Ex. Yes - I've already checked +- Ex. No - I haven't checked + +**Describe the bug** + +> A clear and concise description of what the bug is. Plain-text snippets preferred but screenshots welcome. + +Ex. When I did [...] action, I noticed [...] + +**What did you expect?** + +> A clear and concise description of what you expect to happen + +Ex. I expected [...] + +**Reproducible steps** + +> How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome. + +1. +2. +3. + +**What is your environment?** + +> Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue + +- Ex. Version of this software [e.g. vX.Y.Z] +- Ex. Operating System: [e.g. MacOSX with Docker Desktop vX.Y] +- ... diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 00000000..0b74a7aa --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,34 @@ +--- +name: New Feature +about: Suggest a new feature for us to implement +title: '[New Feature]: ' +labels: 'enhancement' +assignees: '' + +--- + +**Checked for duplicates** + +> Have you checked for duplicate issue tickets? + +- Ex. Yes - I've already checked +- Ex. No - I haven't checked + +**Alternatives considered** + +> Have you considered alternative solutions to your feature request? + +- Ex. Yes - and alternatives don't suffice +- Ex. No - I haven't considered + +**Related problems** + +> Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets. + +Ex. I'm frustrated when [...] happens as documented in issue-XYZ + +**Describe the feature request** + +> A clear and concise description of your request. + +Ex. I need or want [...] diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 00000000..8ef73bbc --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,13 @@ +## Purpose +- Clear, easy-to-understand sentences outlining the purpose of the PR +## Proposed Changes +- [ADD] ... +- [CHANGE] ... +- [FIX] ... +## Issues +- Links to relevant issues +- Example: issue-XYZ +## Testing +- Provide some proof you've tested your changes +- Example: test results available at ... +- Example: tested on operating system ... diff --git a/CHANGELOG.md b/CHANGELOG.md index f0d2f8d0..fb130d61 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,704 +1,13 @@ # Changelog -All notable changes to this project will be documented in this file. +All notable changes to this project will be documented in this file. -The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog). +## [X.Y.Z](https://github.com/NASA-AMMOS//releases/tag/X.Y.Z) - 2023-MM-DD -## [2.5.1](https://github.com/NASA-AMMOS/AIT-Core/compare/2.5.0...2.5.1) +### Added -### Merged +- -- Issue #502 - Fix broken leapsecond file generation [`#503`](https://github.com/NASA-AMMOS/AIT-Core/pull/503) - -### Commits - -- Issue #502 - Fix leapsecond file retrieval location [`06e49a2`](https://github.com/NASA-AMMOS/AIT-Core/commit/06e49a2f5da6d181956fa27b8b84f8b5211cd9ab) -- Fix malformed server config in docs pages [`64da97c`](https://github.com/NASA-AMMOS/AIT-Core/commit/64da97c44775e23cb0b336511d82403f8ef16143) -- Fix additional malformed server config in docs pages [`184d8be`](https://github.com/NASA-AMMOS/AIT-Core/commit/184d8bec62c274627ffd1bc488f4e70555caf8e7) -- Issue #502 - Update to latest leapsecond file [`8a2811e`](https://github.com/NASA-AMMOS/AIT-Core/commit/8a2811ef505379c7e7950a9a185ef34dbfaf0ec3) - -## [2.5.0](https://github.com/NASA-AMMOS/AIT-Core/compare/2.4.0...2.5.0) - 2023-07-26 - -### Merged - -- Issue #498 - Temporarily pin pyyaml to 5.3.1 [`#499`](https://github.com/NASA-AMMOS/AIT-Core/pull/499) - -### Commits - -- Prep for 2.5.0 release [`1badbd8`](https://github.com/NASA-AMMOS/AIT-Core/commit/1badbd80a4cc1e756fe368ad3344dd9f8d13ad3f) - -## [2.4.0](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.6-rc1...2.4.0) - 2023-01-25 - -### Merged - -- Issue #491 - Add logger type annotations for GUI mypy checks [`#492`](https://github.com/NASA-AMMOS/AIT-Core/pull/492) -- Issue #489 - Add PEP 561 compatibility changes [`#490`](https://github.com/NASA-AMMOS/AIT-Core/pull/490) -- Issue #487 - Drop old build status badges [`#488`](https://github.com/NASA-AMMOS/AIT-Core/pull/488) -- Issue #485 - Add GH action build status badge to README [`#486`](https://github.com/NASA-AMMOS/AIT-Core/pull/486) -- Issue #483- Add RTD build status badge to README [`#484`](https://github.com/NASA-AMMOS/AIT-Core/pull/484) -- Issue #478 - Update README pyenv install instructions [`#479`](https://github.com/NASA-AMMOS/AIT-Core/pull/479) -- Issue #480 - Fix incorrect tox-gh-actions version install [`#481`](https://github.com/NASA-AMMOS/AIT-Core/pull/481) -- Issue #467 - Add baseline GH Actions build [`#471`](https://github.com/NASA-AMMOS/AIT-Core/pull/471) -- Issue #376 - Add extension support to dtype.py [`#468`](https://github.com/NASA-AMMOS/AIT-Core/pull/468) -- Issue #469 - Update tox version pin to avoid 4.x releases [`#470`](https://github.com/NASA-AMMOS/AIT-Core/pull/470) -- Issue #465 - Add latest Python patch versions to .python-version file [`#466`](https://github.com/NASA-AMMOS/AIT-Core/pull/466) -- Update tox with multiple python versions for testing [`#463`](https://github.com/NASA-AMMOS/AIT-Core/pull/463) -- Issue #459 - Update to support Python3.10 [`#460`](https://github.com/NASA-AMMOS/AIT-Core/pull/460) -- Issue #201: Yaml file schema verification now works on included yaml files [`#452`](https://github.com/NASA-AMMOS/AIT-Core/pull/452) -- Issue #445 - Add multiprocess support for Plugins [`#455`](https://github.com/NASA-AMMOS/AIT-Core/pull/455) -- Issue #428 - Fix readthedocs build [`#453`](https://github.com/NASA-AMMOS/AIT-Core/pull/453) -- Issue #370: Use TempFile class throughout test suite [`#447`](https://github.com/NASA-AMMOS/AIT-Core/pull/447) -- Issue 448: Fix existing flake8 findings [`#449`](https://github.com/NASA-AMMOS/AIT-Core/pull/449) -- Issue #374: PCap headers' __str__() methods must return string [`#444`](https://github.com/NASA-AMMOS/AIT-Core/pull/444) -- Issue #371 - Refresh pkl cache files when out-of-date [`#432`](https://github.com/NASA-AMMOS/AIT-Core/pull/432) -- Issue #353: Update log error messages to use correct function names [`#442`](https://github.com/NASA-AMMOS/AIT-Core/pull/442) -- Issue #438 - Add ability to route packets based on APID [`#439`](https://github.com/NASA-AMMOS/AIT-Core/pull/439) -- Issue 440: Fix existing Flake8 findings [`#441`](https://github.com/NASA-AMMOS/AIT-Core/pull/441) - -### Fixed - -- Issue #491 - Add logger type annotations for GUI mypy checks [`#491`](https://github.com/NASA-AMMOS/AIT-Core/issues/491) -- Issue #489 - Add PEP 561 compatibility changes [`#489`](https://github.com/NASA-AMMOS/AIT-Core/issues/489) -- Issue #487 - Drop old build status badges [`#487`](https://github.com/NASA-AMMOS/AIT-Core/issues/487) -- Issue #478 - Update README pyenv install instructions [`#478`](https://github.com/NASA-AMMOS/AIT-Core/issues/478) -- Issue #467 - Add baseline GH Actions build [`#467`](https://github.com/NASA-AMMOS/AIT-Core/issues/467) -- Issue #469 - Update tox version pin to avoid 4.x releases [`#469`](https://github.com/NASA-AMMOS/AIT-Core/issues/469) -- Issue #465 - Add latest Python patch versions to .python-version file [`#465`](https://github.com/NASA-AMMOS/AIT-Core/issues/465) - -### Commits - -- issue-370 added TestFile to unit tests [`a3f5780`](https://github.com/NASA-AMMOS/AIT-Core/commit/a3f5780b64dd35e77356940ad096bc833aecfbb0) -- Issue #438 Implements a plugin which routes CCSDS packets by APID based on a table described in a .yaml file. [`7e2340f`](https://github.com/NASA-AMMOS/AIT-Core/commit/7e2340f9df86bbef8736441bc5b4b86b3fcfa246) -- issue-201 - fix unit test [`c48c6a5`](https://github.com/NASA-AMMOS/AIT-Core/commit/c48c6a5d498eed6c0cf36b02bd1ffc5041ed6135) -- Issue #376 - Add data type documentation page [`c34b5c4`](https://github.com/NASA-AMMOS/AIT-Core/commit/c34b5c46db112fde5e578451c1e513a277287656) -- completed issue-201 - validating included yaml files [`5a5e884`](https://github.com/NASA-AMMOS/AIT-Core/commit/5a5e8840a4f0c9fc3da783a55e9eddc51759d168) -- Preparation for 2.4.0 release [`eb777b8`](https://github.com/NASA-AMMOS/AIT-Core/commit/eb777b88d21602b9c53a1c03aaec95dd3cc8a4c1) -- Issue #376 - Update outdated sphinx-apidoc call in README [`7dc68a5`](https://github.com/NASA-AMMOS/AIT-Core/commit/7dc68a561290782d1e551efe8c91623b6d12a392) -- Fix existing flake8 findings [`02afadf`](https://github.com/NASA-AMMOS/AIT-Core/commit/02afadf4ceb67930b4f2ded0e5e34b0cae7c3104) -- issue 370 - __str_ must return string [`876ca26`](https://github.com/NASA-AMMOS/AIT-Core/commit/876ca26c366f8cdc024eee0549d3d7a2b4c977aa) -- Issue #376 - Add extension support to dtype [`0af08f5`](https://github.com/NASA-AMMOS/AIT-Core/commit/0af08f545298df53f7508df03f6c66d556baaef9) -- changed syntax to use the class in the context manager [`cc87ca7`](https://github.com/NASA-AMMOS/AIT-Core/commit/cc87ca7f49414e213f60ffd29fd93e56a9b42d8f) -- test_pcap.py removed code refering to 'tempfile' [`04ef56f`](https://github.com/NASA-AMMOS/AIT-Core/commit/04ef56f625398b7b146e4ad28662f9df3f6eaf2e) -- Issue #491 - Move logger globals for Python bug [`74f9778`](https://github.com/NASA-AMMOS/AIT-Core/commit/74f9778482a2c743006e687cca6fb75776711f2e) -- Fix existing flake8 findings [`90f6c77`](https://github.com/NASA-AMMOS/AIT-Core/commit/90f6c771ecc87398aee41c9cfaecac5915d799db) -- address Nico's comments [`6aa0c6c`](https://github.com/NASA-AMMOS/AIT-Core/commit/6aa0c6cddd40cfff33cb78c20cdc11668ac36def) -- Update log error messages to use correct function names [`a05ac63`](https://github.com/NASA-AMMOS/AIT-Core/commit/a05ac633d9266656172b54a5eea5e7303f2d10fe) -- Revert readthedocs python version to supported legacy version [`3e2998e`](https://github.com/NASA-AMMOS/AIT-Core/commit/3e2998e252aa642925821c4ba5b4145c7cc5e8fd) - -## [2.3.6-rc1](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.5...2.3.6-rc1) - 2022-04-13 - -### Merged - -- Issue #168 Add ability for plugins to publish to arbitrary topic [`#435`](https://github.com/NASA-AMMOS/AIT-Core/pull/435) -- Issue 427: Update AIT OpenMCT comp. provider to serve packets as fold… [`#433`](https://github.com/NASA-AMMOS/AIT-Core/pull/433) -- Issue 358: OpenMCT Plugin support for multiple clients and filtered telemetry [`#426`](https://github.com/NASA-AMMOS/AIT-Core/pull/426) -- Minor fixes to issues found in master [`#422`](https://github.com/NASA-AMMOS/AIT-Core/pull/422) -- Issue 371: Fix calls to logger in util pkl handling [`#423`](https://github.com/NASA-AMMOS/AIT-Core/pull/423) -- Add Packet Accumulator [`#418`](https://github.com/NASA-AMMOS/AIT-Core/pull/418) -- Add Packet Padder Plugin [`#417`](https://github.com/NASA-AMMOS/AIT-Core/pull/417) -- Update getDefaultDict to return CmdDict extensions when applicable [`#404`](https://github.com/NASA-AMMOS/AIT-Core/pull/404) -- Improve time handling in database insert method [`#421`](https://github.com/NASA-AMMOS/AIT-Core/pull/421) -- testing nested includes during test for 'dirty' (pickle) [`#416`](https://github.com/NASA-AMMOS/AIT-Core/pull/416) -- Issue-394 Add DSN paths to ait-create-dirs [`#396`](https://github.com/NASA-AMMOS/AIT-Core/pull/396) -- Fix ArrayType encode bug [`#402`](https://github.com/NASA-AMMOS/AIT-Core/pull/402) -- issue-#399 Fix error when IPV6 is disabled at kernel level [`#400`](https://github.com/NASA-AMMOS/AIT-Core/pull/400) -- Issue 383 - update poetry builds [`#385`](https://github.com/NASA-AMMOS/AIT-Core/pull/385) -- Issue-395 Add try except when attempting to pack opcode into struct. [`#397`](https://github.com/NASA-AMMOS/AIT-Core/pull/397) -- Ait-tlm-csv fields argument fix [`#387`](https://github.com/NASA-AMMOS/AIT-Core/pull/387) -- Update ait-tlm-csv cmd packet option description [`#388`](https://github.com/NASA-AMMOS/AIT-Core/pull/388) -- Change CSV-generating fields file to open 'r' mode [`#386`](https://github.com/NASA-AMMOS/AIT-Core/pull/386) -- Update Core package handling [`#381`](https://github.com/NASA-AMMOS/AIT-Core/pull/381) -- Dev Tool Updates [`#379`](https://github.com/NASA-AMMOS/AIT-Core/pull/379) -- Add "core.seq" to extensions documentation [`#378`](https://github.com/NASA-AMMOS/AIT-Core/pull/378) -- Issue #360 - Fix time handling in table encode / decode [`#361`](https://github.com/NASA-AMMOS/AIT-Core/pull/361) -- Issue #354 - Rework table support [`#355`](https://github.com/NASA-AMMOS/AIT-Core/pull/355) -- Issue #345 - Document 64-bit integer limitation in GUI [`#346`](https://github.com/NASA-AMMOS/AIT-Core/pull/346) -- Issue #341 - Update database API docs page [`#343`](https://github.com/NASA-AMMOS/AIT-Core/pull/343) -- Add historical query support to the OpenMCT plugin [`#349`](https://github.com/NASA-AMMOS/AIT-Core/pull/349) -- Issue #339 - Document Packet / Field naming constraints [`#340`](https://github.com/NASA-AMMOS/AIT-Core/pull/340) - -### Fixed - -- Update Core package handling [`#364`](https://github.com/NASA-AMMOS/AIT-Core/issues/364) -- Issue #360 - Fix time handling in table encode / decode [`#360`](https://github.com/NASA-AMMOS/AIT-Core/issues/360) -- Issue #345 - Document 64-bit integer limitation in GUI [`#345`](https://github.com/NASA-AMMOS/AIT-Core/issues/345) -- Issue #341 - Update database API docs page [`#341`](https://github.com/NASA-AMMOS/AIT-Core/issues/341) - -### Commits - -- Run black across codebase [`2834d47`](https://github.com/NASA-AMMOS/AIT-Core/commit/2834d4753bc247fe716665e7de69b0e6294ebf21) -- Initial pre-commit additions and cleanup. mypy compatibility fixes [`4573211`](https://github.com/NASA-AMMOS/AIT-Core/commit/4573211dc7949041b5ea60ba3a7769ab941468be) -- Issue #302 - Support historical queries in OpenMCT plugin [`39ecd2a`](https://github.com/NASA-AMMOS/AIT-Core/commit/39ecd2ad3ad1f4a72f4404e2460a9b43698d2ed3) -- Port tests to pytest [`6b5a779`](https://github.com/NASA-AMMOS/AIT-Core/commit/6b5a7798015bfc6d2f441ea6fd6518cce5fd42eb) -- Issue 427: Update AIT OpenMCT comp. provider to serve packets as folders of fields [`bd5cfd6`](https://github.com/NASA-AMMOS/AIT-Core/commit/bd5cfd6eb1c863bc25e90356c8676009f89679f0) -- Fix linting errors in dmc module [`61fbf57`](https://github.com/NASA-AMMOS/AIT-Core/commit/61fbf573c6f06e695f2c46c3f7ba16c248f9f3a0) -- bin script linting error cleanup [`b458412`](https://github.com/NASA-AMMOS/AIT-Core/commit/b458412363e6697f4ee965abddda6c74c4257678) -- Issue #354 - Table documentation update [`2867e2a`](https://github.com/NASA-AMMOS/AIT-Core/commit/2867e2a1be68a45278f0f8e5f0232fd07ff22731) -- Prep for 2.3.6-rc1 release [`48006cb`](https://github.com/NASA-AMMOS/AIT-Core/commit/48006cba87b0230dee7dc91db8cc4ad8ca4d73c7) -- Fix linting errors in db module [`89d38b5`](https://github.com/NASA-AMMOS/AIT-Core/commit/89d38b547af07e9160f59b96864d80e4d1ffa5c4) -- Linting related cleanup [`d557cef`](https://github.com/NASA-AMMOS/AIT-Core/commit/d557cefb79d95de77e624cf00f730906a6985c6e) -- Fix linting errors in tlm module. [`c5ae415`](https://github.com/NASA-AMMOS/AIT-Core/commit/c5ae415398ea2de2f58586d3d1d2c1dc93c61878) -- Fix linting errors in API module [`20aeb70`](https://github.com/NASA-AMMOS/AIT-Core/commit/20aeb70d576c8b71fdb80528061bc1b29ae8c4ac) -- Additional Core server linting fixes [`42b6539`](https://github.com/NASA-AMMOS/AIT-Core/commit/42b6539f2482252bb01cdef9886e2db70a4cd91e) -- issue-#420 Add Packet Accumulator [`9255006`](https://github.com/NASA-AMMOS/AIT-Core/commit/9255006bba7ce1762acf9a694877c08a6b717621) -- Fix linting errors in util module [`526b5f4`](https://github.com/NASA-AMMOS/AIT-Core/commit/526b5f4f9b71ef1bd62ce5b7ba60cebf2b9db985) -- Additional cfg.py module linting cleanup [`2820f1d`](https://github.com/NASA-AMMOS/AIT-Core/commit/2820f1ddcb8f99c7fab3cb10b19f194f2d2be9ed) -- Make sure sphinx-build is poetry compatible update README and installation doc [`bfdb9a6`](https://github.com/NASA-AMMOS/AIT-Core/commit/bfdb9a6a1cee2b8739d5fa59fdcda33b7b6d3af5) -- minor nose->pytest cleanup [`7a7e3bf`](https://github.com/NASA-AMMOS/AIT-Core/commit/7a7e3bf2cbb655965769bdf8364ced71695762e2) -- Additional mypy related updates and cleanup for full pipeline check [`ce725b5`](https://github.com/NASA-AMMOS/AIT-Core/commit/ce725b5d9d828a740f23d9092d8a314e2604d52f) -- Update ait-tlm-csv command and add documentation [`7e02fa8`](https://github.com/NASA-AMMOS/AIT-Core/commit/7e02fa875f8e113f0a7875c7a683d63c4a832aa7) -- Fix linting errors in seq module [`8f0b17f`](https://github.com/NASA-AMMOS/AIT-Core/commit/8f0b17f6c976ec28bf892ea877250e823a8f1988) -- Fix linting errors in val module [`896efd5`](https://github.com/NASA-AMMOS/AIT-Core/commit/896efd5e7eb40042afc6066a33c182396cc5e2f8) -- Fix linting errors in gds module [`8bb3ffa`](https://github.com/NASA-AMMOS/AIT-Core/commit/8bb3ffa33335e64113253f0c35f973cfd36d6ea9) -- Fix linting errors in dtype module. [`22f2efb`](https://github.com/NASA-AMMOS/AIT-Core/commit/22f2efb2d4ab4f9455a8099a6c85dfaa9a22918e) -- issue-#419 Add Packet Padder Plugin [`86bf9ce`](https://github.com/NASA-AMMOS/AIT-Core/commit/86bf9cebf77ee990f11d5ebef1d1e31799958467) -- Revert testdata changes [`511fa7e`](https://github.com/NASA-AMMOS/AIT-Core/commit/511fa7efc4db80799fad4409b746da8e93bef61f) -- Fix linting errors in cmd module [`093d26b`](https://github.com/NASA-AMMOS/AIT-Core/commit/093d26bb0a73c7e4a97205e4fad322753ed9f471) -- Update optional package install handling and add new depdencies [`6919de8`](https://github.com/NASA-AMMOS/AIT-Core/commit/6919de8aa3c40696e1d22229b9719c561c2f45ae) -- Fix unit-test related issues [`d6b088d`](https://github.com/NASA-AMMOS/AIT-Core/commit/d6b088d49da6227ff77df953f2dbd94793af2e72) -- Add getDefaultDict with extension unit tests [`4cd31ca`](https://github.com/NASA-AMMOS/AIT-Core/commit/4cd31cab11dc31b7d23942aec23b5a4944fddfac) -- Add tox support and rearrange test structuring [`aec5df4`](https://github.com/NASA-AMMOS/AIT-Core/commit/aec5df424b7b9e5234b1ddc2887ee850b87311ab) -- Fix linting errors in evr module [`a2b0013`](https://github.com/NASA-AMMOS/AIT-Core/commit/a2b0013a803437e82b4fe382026d6d69c8ef864f) -- Drop custom git hook install in prep for pre-commit changes [`2414dff`](https://github.com/NASA-AMMOS/AIT-Core/commit/2414dff8053c8edafea510f39c7f483c07d94feb) -- Fix linting erros in json module [`23d3076`](https://github.com/NASA-AMMOS/AIT-Core/commit/23d3076cf5e5d234a4f6cd377f755374d8e53890) -- Fix linting errors in limits module [`c5158d4`](https://github.com/NASA-AMMOS/AIT-Core/commit/c5158d41d0945af97ed2b457b0ef7c183ce4b418) -- Fix linting errors in geom module [`e805c64`](https://github.com/NASA-AMMOS/AIT-Core/commit/e805c64e7fa558dd13fa0400a95f2eebbe05895b) -- Fix linting errors in log module [`9baf9ea`](https://github.com/NASA-AMMOS/AIT-Core/commit/9baf9ea3cae4ba13495d8a1ea5d40435b83f347d) -- Clean up server.broker linting errors [`7e5c646`](https://github.com/NASA-AMMOS/AIT-Core/commit/7e5c646a0619b5f3f17e9377404b00c1ef1c0301) -- Cleanup linting errors in server.stream [`fb0a137`](https://github.com/NASA-AMMOS/AIT-Core/commit/fb0a1374ce74ac22ec971e887b08ed5d081936d1) -- Issue #434 Add ability for plugins to publish to arbitrary topic [`36f60a6`](https://github.com/NASA-AMMOS/AIT-Core/commit/36f60a6ced0c30b00eefe50090ebe323130ac6cb) -- Cleanup server.__init__ linting errors [`3cbd17d`](https://github.com/NASA-AMMOS/AIT-Core/commit/3cbd17d8bdf49a7ccc921bb32b8f8def3eb7a8f7) -- Fix linting errors in coord module [`3abd4d9`](https://github.com/NASA-AMMOS/AIT-Core/commit/3abd4d93ab9b1eb74cfd0b0eee3c96eef130aeb2) -- More black cleanup [`7939298`](https://github.com/NASA-AMMOS/AIT-Core/commit/79392987ea3e9638e707d9dea67e9ced45f597cd) -- core.__init__ linting error cleanup [`92a1f65`](https://github.com/NASA-AMMOS/AIT-Core/commit/92a1f65800ce8657ca183d5545895216e07fa59b) -- Issue #394 Add DSN paths to ait-create-dirs [`b0073a6`](https://github.com/NASA-AMMOS/AIT-Core/commit/b0073a64b5ab98cf039d07a68d5ab4d0bbd768fe) -- Issue #395 Add try except when attempting to pack opcode into struct. [`1e34a6d`](https://github.com/NASA-AMMOS/AIT-Core/commit/1e34a6d49012b8de7edf4f78db1e36e6423ea096) -- Cleanup server.server linting errors [`9bf5c51`](https://github.com/NASA-AMMOS/AIT-Core/commit/9bf5c5123030ea57c8c7ee55b2bb7a90055cfa39) -- Drop nose from setup.cfg [`f43a156`](https://github.com/NASA-AMMOS/AIT-Core/commit/f43a156a57029ff9414ddcb9ca47654a0d157688) -- Cleanup server.plugin linting errors [`688ead2`](https://github.com/NASA-AMMOS/AIT-Core/commit/688ead279a189151471dc1d1a8ffa91484765ef8) -- Fix linting errors in bsc module [`9277ed2`](https://github.com/NASA-AMMOS/AIT-Core/commit/9277ed20fadb11b6af148bf2e4fb7274bb59ae13) -- Issue 371: Fix calls to logger [`648d84d`](https://github.com/NASA-AMMOS/AIT-Core/commit/648d84dcb60c2107582aee4e0e088e5c16c8240e) -- Add support for array type in ArgDefn encode method [`fc9e5a3`](https://github.com/NASA-AMMOS/AIT-Core/commit/fc9e5a33a5cda0835fac7eb0a62f3f08a3041099) -- Clean up server.utils linting errors [`7c0e38b`](https://github.com/NASA-AMMOS/AIT-Core/commit/7c0e38b5b978502f2c467feaa5480f91e19b7cc0) -- server.plugins.__init__ linting error cleanup [`8f30508`](https://github.com/NASA-AMMOS/AIT-Core/commit/8f30508629b31daf61e2a2a04925086449c37d6e) -- Add flake8 exclusions for module level import errors [`390f223`](https://github.com/NASA-AMMOS/AIT-Core/commit/390f223636896ef5ecba83dfd3e3a272af5d0c6f) -- added comments to mame files causing new pickle cache [`3f2f0a4`](https://github.com/NASA-AMMOS/AIT-Core/commit/3f2f0a4472866a9705cf21b320eccc8e77a23f16) -- change print() statements to ait.log.debug() [`9265e49`](https://github.com/NASA-AMMOS/AIT-Core/commit/9265e49fbfef717f55bd6c16a6dfce5c09522601) -- Method cmd.getDefaultDict shall return CmdDict extensions if applicable [`9f3c91b`](https://github.com/NASA-AMMOS/AIT-Core/commit/9f3c91b99e98fc53ad3457cffd6f723181272561) -- Cleanup server.plugins.data_archive linting errors [`a67a88c`](https://github.com/NASA-AMMOS/AIT-Core/commit/a67a88cc5898fbc77eb1175ca3229e6d77b64bc4) -- server.handlers.__init__ linting error cleanup [`75a9826`](https://github.com/NASA-AMMOS/AIT-Core/commit/75a9826605dd472ef5c327bc4635d5be2ffdc2f2) -- Drop pylint and pep-related config [`cf506e5`](https://github.com/NASA-AMMOS/AIT-Core/commit/cf506e5ea58079f2677916b7621fc8a5a15acc07) -- Use values variable database execution [`04ec870`](https://github.com/NASA-AMMOS/AIT-Core/commit/04ec8705c929b2494985949c8b781842b8f63836) -- Remove invalid log statements in util.py [`5eb57d5`](https://github.com/NASA-AMMOS/AIT-Core/commit/5eb57d5d1d7069b16b67e303540ce889df47aca0) -- Update ait-tlm-csv cmd option description [`0677dd9`](https://github.com/NASA-AMMOS/AIT-Core/commit/0677dd9303f73853bad959cc97d22b9b4dfb7c8d) -- Fix linting errors in table module [`63e6502`](https://github.com/NASA-AMMOS/AIT-Core/commit/63e6502eb0d58385528d9196852a9e81b6d4287c) -- Fix linting errors in pcap module [`e0151e3`](https://github.com/NASA-AMMOS/AIT-Core/commit/e0151e3dc0aa67302f2e67c7a33b58e9bbee5089) -- Add tag files to .gitignore [`4768a7e`](https://github.com/NASA-AMMOS/AIT-Core/commit/4768a7eea7ece04b7eb82d5bba20b2f32cb1bf32) -- final nose removal cleanup [`9a648fd`](https://github.com/NASA-AMMOS/AIT-Core/commit/9a648fd6e0c42c9146ad0d74a28b64dd96c10ca7) - -## [2.3.5](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.4...2.3.5) - 2021-03-23 - -### Merged - -- Issue #337 - Update ait-seq-encode log message formatting [`#338`](https://github.com/NASA-AMMOS/AIT-Core/pull/338) - -### Fixed - -- Issue #337 - Update ait-seq-encode log message formatting [`#337`](https://github.com/NASA-AMMOS/AIT-Core/issues/337) - -### Commits - -- Prep for 2.3.5 release [`0045ffe`](https://github.com/NASA-AMMOS/AIT-Core/commit/0045ffe2d58fe1ecdcf0fda10ff6a57b6e1c475f) - -## [2.3.4](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.3...2.3.4) - 2021-03-19 - -### Merged - -- Issue #335 - Make Seq sequence id optional on initialization [`#336`](https://github.com/NASA-AMMOS/AIT-Core/pull/336) - -### Fixed - -- Issue #335 - Make Seq sequence id optional on initialization [`#335`](https://github.com/NASA-AMMOS/AIT-Core/issues/335) - -### Commits - -- Prep for 2.3.4 release [`65b2ddf`](https://github.com/NASA-AMMOS/AIT-Core/commit/65b2ddfdfa6df99c3574db134f8f07bbbfccc54d) - -## [2.3.3](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.2...2.3.3) - 2021-03-19 - -### Merged - -- Issue #330 - Fix seq encode / decode input format consistency [`#334`](https://github.com/NASA-AMMOS/AIT-Core/pull/334) -- Issue #329 - Update Seq for configurable Magic number and command sizes [`#332`](https://github.com/NASA-AMMOS/AIT-Core/pull/332) -- Issue #194 - Add support for seq extensions [`#331`](https://github.com/NASA-AMMOS/AIT-Core/pull/331) - -### Fixed - -- Issue #330 - Fix seq encode / decode input format consistency [`#330`](https://github.com/NASA-AMMOS/AIT-Core/issues/330) -- Issue #329 - Update Seq for configurable Magic number and command sizes [`#329`](https://github.com/NASA-AMMOS/AIT-Core/issues/329) - -### Commits - -- Prep for 2.3.3 release [`0a208c2`](https://github.com/NASA-AMMOS/AIT-Core/commit/0a208c2d03e5d6749b7976f22dcd4a79e5aef1a7) - -## [2.3.2](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.1...2.3.2) - 2021-03-11 - -### Merged - -- Issue #325 - Fix 0MQ data format update issues [`#326`](https://github.com/NASA-AMMOS/AIT-Core/pull/326) - -### Commits - -- Prep for 2.3.2 release [`b907e3c`](https://github.com/NASA-AMMOS/AIT-Core/commit/b907e3ce8d7a452607d08cc00cd7cafeb8dc4cdf) - -## [2.3.1](https://github.com/NASA-AMMOS/AIT-Core/compare/2.3.0...2.3.1) - 2021-03-11 - -### Merged - -- Issue #318 - Fix validation error message sorting issue [`#323`](https://github.com/NASA-AMMOS/AIT-Core/pull/323) - -### Fixed - -- Issue #318 - Fix validation error message sorting issue [`#318`](https://github.com/NASA-AMMOS/AIT-Core/issues/318) - -### Commits - -- Prep for 2.3.1 release [`e00e1cd`](https://github.com/NASA-AMMOS/AIT-Core/commit/e00e1cdf2744f7b6b49f02b8a5d4eb8aeb3e02bf) - -## [2.3.0](https://github.com/NASA-AMMOS/AIT-Core/compare/2.2.0...2.3.0) - 2021-03-10 - -### Merged - -- Issue #320 - Add limits_find_dn utility [`#321`](https://github.com/NASA-AMMOS/AIT-Core/pull/321) -- Issue #299 - Update server 0MQ data passing [`#322`](https://github.com/NASA-AMMOS/AIT-Core/pull/322) - -### Fixed - -- Issue #299 - Update server 0MQ data passing [`#299`](https://github.com/NASA-AMMOS/AIT-Core/issues/299) -- Issue #320 - Add limits_find_dn utility [`#320`](https://github.com/NASA-AMMOS/AIT-Core/issues/320) - -### Commits - -- Prep for 0.2.3 release [`fe90bc3`](https://github.com/NASA-AMMOS/AIT-Core/commit/fe90bc32cee36595197e1cd3b71a9c070b96038e) - -## [2.2.0](https://github.com/NASA-AMMOS/AIT-Core/compare/2.1.0...2.2.0) - 2021-02-10 - -### Merged - -- Issue #316 - Fix typo in server._load_streams_and_plugins [`#317`](https://github.com/NASA-AMMOS/AIT-Core/pull/317) -- Issue #313 - Update API telemetry handling functionality [`#314`](https://github.com/NASA-AMMOS/AIT-Core/pull/314) -- Database API Result Handling and SQLite bug fixes and improvements [`#311`](https://github.com/NASA-AMMOS/AIT-Core/pull/311) - -### Commits - -- Issue #313 - Update documentation with API telemetry stream updates [`0110c0c`](https://github.com/NASA-AMMOS/AIT-Core/commit/0110c0cc8ee9b3c17027075560279d5869acefff) -- Prep for 2.2.0 release [`e0d4bee`](https://github.com/NASA-AMMOS/AIT-Core/commit/e0d4bee6e46333287ac4c6d5f1f6b866a09b0592) -- Issue #313 - Change api-streams config attr to api-telemetry-streams [`83d621c`](https://github.com/NASA-AMMOS/AIT-Core/commit/83d621c3b3e113185234c3d38023bf7e2989f309) -- Update leapseconds file [`8bb54ab`](https://github.com/NASA-AMMOS/AIT-Core/commit/8bb54abcf41cb70a14f512fbec3ec35b292fa064) - -## [2.1.0](https://github.com/NASA-AMMOS/AIT-Core/compare/2.0.1...2.1.0) - 2020-12-16 - -### Merged - -- Issue #306 - Support lists in config directory expansion [`#312`](https://github.com/NASA-AMMOS/AIT-Core/pull/312) -- Issue #300 - Fix cfg import in db.py [`#301`](https://github.com/NASA-AMMOS/AIT-Core/pull/301) - -### Commits - -- Prep for 2.1.0 release [`0f67dd1`](https://github.com/NASA-AMMOS/AIT-Core/commit/0f67dd1a61e817ab1c1c9928b9c41e514a6908b5) - -## [2.0.1](https://github.com/NASA-AMMOS/AIT-Core/compare/2.0.0...2.0.1) - 2020-10-12 - -### Merged - -- Issue #297 - Pin greenlets to 0.4.16 for gevent 1.4 compatibility [`#298`](https://github.com/NASA-AMMOS/AIT-Core/pull/298) -- Issue #290 - Update server port configuration examples [`#294`](https://github.com/NASA-AMMOS/AIT-Core/pull/294) -- Issue #291 - Update documentation package path naming [`#295`](https://github.com/NASA-AMMOS/AIT-Core/pull/295) -- Issue 292: Fix call to util.toNumber() in ait_seq_send [`#293`](https://github.com/NASA-AMMOS/AIT-Core/pull/293) -- Issue #285 - Added more log info into dmc.py [`#288`](https://github.com/NASA-AMMOS/AIT-Core/pull/288) -- Updated dmc.py Logging info [`#2`](https://github.com/NASA-AMMOS/AIT-Core/pull/2) -- Resolved Issue #284 - Updated leapsecond.dat [`#286`](https://github.com/NASA-AMMOS/AIT-Core/pull/286) - -### Commits - -- Update CHANGELOG for 2.0.1 [`dc4dfbd`](https://github.com/NASA-AMMOS/AIT-Core/commit/dc4dfbde1d7829e8743dc03d3248cdbb0a8999d9) -- Issue #290 update server port config example in doc [`bfe1417`](https://github.com/NASA-AMMOS/AIT-Core/commit/bfe141762983cbc8a2ad519ceacb61acdc73acab) -- Updated Logging info [`2636107`](https://github.com/NASA-AMMOS/AIT-Core/commit/2636107aef90f4729273c4d988a6686a3ca23e27) -- Prep for 2.0.1 release [`ad0645b`](https://github.com/NASA-AMMOS/AIT-Core/commit/ad0645b3f3aa367138aab81fbf8a99050745fd6c) -- Issue #290 update server port config example in doc [`5d3ac9e`](https://github.com/NASA-AMMOS/AIT-Core/commit/5d3ac9e7331c1c8011eeae71c973a1deecb7b493) -- Issue #291 update server.handlers package path in doc [`88b27e3`](https://github.com/NASA-AMMOS/AIT-Core/commit/88b27e334ea409567c36f045d77dcefb66078597) -- Updated variable for strtime format log info [`d134040`](https://github.com/NASA-AMMOS/AIT-Core/commit/d1340405b1f2c180d97bad0b4a3184cc24c0d541) -- Issue #291 update server.plugins package path in doc [`d892d75`](https://github.com/NASA-AMMOS/AIT-Core/commit/d892d753e33cc2bc5eeacd4b56296b2dad581224) -- Update README.rst [`1b45472`](https://github.com/NASA-AMMOS/AIT-Core/commit/1b4547246bddd8f5d2899d88c38c09da9fe1406f) - -## [2.0.0](https://github.com/NASA-AMMOS/AIT-Core/compare/1.4.0...2.0.0) - 2020-04-28 - -### Merged - -- Issue #281 - Update CmdAPI with None udp_dest default [`#282`](https://github.com/NASA-AMMOS/AIT-Core/pull/282) -- Issue #277 - Remove ./src, ./test, and build/clean.py [`#278`](https://github.com/NASA-AMMOS/AIT-Core/pull/278) -- Issue #275 - Remove unneeded GDS utilities [`#276`](https://github.com/NASA-AMMOS/AIT-Core/pull/276) -- Issue #143 - CmdApi utilizes newly added server command entry point [`#274`](https://github.com/NASA-AMMOS/AIT-Core/pull/274) -- Issue #264 - Reverse indexing cleanup [`#271`](https://github.com/NASA-AMMOS/AIT-Core/pull/271) -- Issue #239 - Add ccsds packet validation test [`#270`](https://github.com/NASA-AMMOS/AIT-Core/pull/270) -- Issue #233 - document Python 3.7 compatibility [`#269`](https://github.com/NASA-AMMOS/AIT-Core/pull/269) -- Issue #242 - Document dependency on OpenMCT v0.14.0 [`#268`](https://github.com/NASA-AMMOS/AIT-Core/pull/268) -- Issue #262 - Prevent auto execute on import for ait_ccsds_send_example [`#263`](https://github.com/NASA-AMMOS/AIT-Core/pull/263) -- Python3 test updates for core and bin scripts, part 2 [`#259`](https://github.com/NASA-AMMOS/AIT-Core/pull/259) -- Update Travis build icon [`#261`](https://github.com/NASA-AMMOS/AIT-Core/pull/261) -- kkallas python3 test update [`#254`](https://github.com/NASA-AMMOS/AIT-Core/pull/254) -- Issue #251 - Specify Python version for RTD build [`#252`](https://github.com/NASA-AMMOS/AIT-Core/pull/252) -- Issue #228 - Fixed exception syntax errors [`#229`](https://github.com/NASA-AMMOS/AIT-Core/pull/229) -- Issue #231 - Add SeqGen CLI script to sequence documentation [`#232`](https://github.com/NASA-AMMOS/AIT-Core/pull/232) -- Issue #219 - Implement python 3 support [`#220`](https://github.com/NASA-AMMOS/AIT-Core/pull/220) -- Issue #224 - Merge config files between AIT-Core and AIT-DSN [`#225`](https://github.com/NASA-AMMOS/AIT-Core/pull/225) -- Issue #215 - Update OpenMCT plugin to support configurable telemetry stream names [`#223`](https://github.com/NASA-AMMOS/AIT-Core/pull/223) -- Issue #197 - Fixed project setup link in docs [`#222`](https://github.com/NASA-AMMOS/AIT-Core/pull/222) -- Issue #216 and #217 - Fix default plugins and handler package [`#218`](https://github.com/NASA-AMMOS/AIT-Core/pull/218) -- Issue #213 - Update handler package structure [`#214`](https://github.com/NASA-AMMOS/AIT-Core/pull/214) -- Issue #208 - Plugin restructure and cleanup [`#209`](https://github.com/NASA-AMMOS/AIT-Core/pull/209) -- Issue #211 - Fix typo in doc index page [`#212`](https://github.com/NASA-AMMOS/AIT-Core/pull/212) -- Issue #206 - Fix command duplicate opcode / name validation [`#207`](https://github.com/NASA-AMMOS/AIT-Core/pull/207) -- Issue #167 - Add !include capability to cmd.yaml [`#200`](https://github.com/NASA-AMMOS/AIT-Core/pull/200) -- Issue #202 - Add MPS Seq to AIT Seq conversion script [`#203`](https://github.com/NASA-AMMOS/AIT-Core/pull/203) -- Issue #204 - Create a standalone OpenMCT plugin [`#205`](https://github.com/NASA-AMMOS/AIT-Core/pull/205) -- Issue #69 - Update command config docs with byte ordering details [`#199`](https://github.com/NASA-AMMOS/AIT-Core/pull/199) -- Issue #67 - Correct packet names in API docs [`#198`](https://github.com/NASA-AMMOS/AIT-Core/pull/198) - -### Commits - -- Issue #75 - progress on moving gui over [`67b03e5`](https://github.com/NASA-AMMOS/AIT-Core/commit/67b03e5680bef42c15ec168fa829b0503c081f7b) -- GUI Issue #75 - Remove GUI plugin from core repo [`fa3fa0e`](https://github.com/NASA-AMMOS/AIT-Core/commit/fa3fa0e5a03ed8838f5a14ac8cc68f4402843a5c) -- GUI Issue #75 - Getting GUI Plugin to work within its own thread [`d20a75d`](https://github.com/NASA-AMMOS/AIT-Core/commit/d20a75d11dc93a276df739a2f402aecac66d16da) -- Server restructure and minor functionality changes [`c6c3d83`](https://github.com/NASA-AMMOS/AIT-Core/commit/c6c3d830da2303ec35c0c20fe2a2104ce10a4a18) -- Preparation for 2.0.0 [`877fa67`](https://github.com/NASA-AMMOS/AIT-Core/commit/877fa6715718202f26e86d6b0942647d6e0157d1) -- GUI Issue #75 - Moving config parsing and client creation from broker to server; bug fixes [`b9894e2`](https://github.com/NASA-AMMOS/AIT-Core/commit/b9894e27b111babd2f561b87edeadb0b9ee1f8e6) -- add changes [`d54176e`](https://github.com/NASA-AMMOS/AIT-Core/commit/d54176e3703c2d0f92a407350a87628cdfb54080) -- Updated CCSDSHandler class [`bb4856c`](https://github.com/NASA-AMMOS/AIT-Core/commit/bb4856c54b08547e90c6fd4a39c4c73ad3e40fec) -- GUI Issue #75 - Work on testing [`f701591`](https://github.com/NASA-AMMOS/AIT-Core/commit/f701591700a79276582cbf4ddffa57362410d431) -- Add CCSDSHandler class [`68d4568`](https://github.com/NASA-AMMOS/AIT-Core/commit/68d456893f78cc91b457c61c7b05d94fcf7beb1c) -- Prep for 2.0rc1.dev0 release (2.0 release candidate in development) [`3289f48`](https://github.com/NASA-AMMOS/AIT-Core/commit/3289f48b17842c48b47cd779e3d983404f951a64) -- GUI Issue #75 - Updates to documentation, docstrings, comments [`4c8cc3d`](https://github.com/NASA-AMMOS/AIT-Core/commit/4c8cc3da7ef3b4f9402e8fdf5e2791b1b440f1e5) -- GUI Issue #75 - Updating test_broker to test_server to incorporate changes [`e8d13d0`](https://github.com/NASA-AMMOS/AIT-Core/commit/e8d13d06395fc017144acba806a00e69bd5ab40c) -- GUI Issue #75 - Getting GUI subscriptions to log/telem inputs working [`0ad3a26`](https://github.com/NASA-AMMOS/AIT-Core/commit/0ad3a26d1c9e8bb4efa6441bc91944e5c049c16e) -- Issue #210 - Remove test files from API documentation [`e197a34`](https://github.com/NASA-AMMOS/AIT-Core/commit/e197a3456a1e8c2ffb40dcac9ac996dade7090a4) -- GUI Issue #75 - New docs [`af94194`](https://github.com/NASA-AMMOS/AIT-Core/commit/af94194f8a401562a6b3058c895e0560c717e46c) -- GUI Issue #75 - Adding stream with port input using gevent.server; adding handler for telemetry packets [`e152631`](https://github.com/NASA-AMMOS/AIT-Core/commit/e15263113979c32374b78b49eb4bad62391da292) -- GUI Isssue #75 - Adding docstrings; making methods private; removing unused file [`344fdc0`](https://github.com/NASA-AMMOS/AIT-Core/commit/344fdc036a829c8b0a13065b5006261e95cfd1ce) -- AIT-GUI Issue #75 - Starting work on new ait-server backend [`e700a22`](https://github.com/NASA-AMMOS/AIT-Core/commit/e700a229373dab443fbf1b8bdbd9e83bfd2b4768) -- python3 test update [`7085484`](https://github.com/NASA-AMMOS/AIT-Core/commit/708548490c117e3085c1b95fdf441af423ff01b1) -- Resolved more errors for ccsds unit test [`4b15cf2`](https://github.com/NASA-AMMOS/AIT-Core/commit/4b15cf2858ede2b5559fbc8e1eb48f004e8137f5) -- GUI Issue #75 - Testing broker stream parsing and creation [`ae67331`](https://github.com/NASA-AMMOS/AIT-Core/commit/ae673318782b920f50c7c3e47cb38e486126c20d) -- GUI Issue #75 - Updating tests to reflect new server design for stream creation [`d7b3aae`](https://github.com/NASA-AMMOS/AIT-Core/commit/d7b3aaec819d77581eaf568a59f2162ff4e3160c) -- AIT-GUI Issue #75 - Moving all config parsing out of stream class and into broker; removing need for input type specification (now inferred from input value) [`902e9c2`](https://github.com/NASA-AMMOS/AIT-Core/commit/902e9c2e254cdeef6a7eeef578373543c805f572) -- GUI Issue #75 - Breaking out stream creation into separate inbound/outbound functions; renaming ZMQInputStream to ZMQStream to avoid confusion with inbound/outbound streams; tests still need updating with new stream creation methods [`54780b3`](https://github.com/NASA-AMMOS/AIT-Core/commit/54780b3c4adb1a63d4348bfe7d18b46de4b26371) -- GUI Issue #75 - Starting work on plugin; extracting zmq functionality to common Client class [`e7f2db5`](https://github.com/NASA-AMMOS/AIT-Core/commit/e7f2db519d9a4d22250f1d8dcf67bc7012d470a6) -- GUI Issue #74 - Trying to transition everything to gevents; adding server class [`8134c9a`](https://github.com/NASA-AMMOS/AIT-Core/commit/8134c9a5e086b6dc792ba2379bf218c809c6906c) -- GUI Issue #75 [`38c25a1`](https://github.com/NASA-AMMOS/AIT-Core/commit/38c25a1496c8a53996a51229872d600af8020f9e) -- Readded config file [`b50301b`](https://github.com/NASA-AMMOS/AIT-Core/commit/b50301bac3ecdba4919f5c904ff78f2b416a5c05) -- Resolved some of the errors when running test_ccsds.py [`40ce075`](https://github.com/NASA-AMMOS/AIT-Core/commit/40ce0752bbe0bb7f15e19706083558bbc60f3f06) -- GUI Issue #75 - Adding capability for outbound streams to publish to port; adding command stream which subscribes to GUI and publishes commands to port [`f1b804c`](https://github.com/NASA-AMMOS/AIT-Core/commit/f1b804ca7ef4601562033b48e321529dea1e9020) -- GUI Issue #75 - Reorganizing and working on plugin [`7f488d5`](https://github.com/NASA-AMMOS/AIT-Core/commit/7f488d53cf60f31f700faa3b547ccb3a97f1fcaa) -- AIT-GUI Issue #75 - Work on Handler class, handler parsing and creation [`d50296c`](https://github.com/NASA-AMMOS/AIT-Core/commit/d50296c569916faea3fecf136ac5e10499a1b7d0) -- GUI Issue #74 - Cleanup of broker code [`5daac5d`](https://github.com/NASA-AMMOS/AIT-Core/commit/5daac5d4791d84c54829540133f28c1bf93a568f) -- GUI Issue #75 - Working on plugin config parsing and creation; making every client have a name and type attribute [`f94f8ba`](https://github.com/NASA-AMMOS/AIT-Core/commit/f94f8bac5c0a90bd97ca74c02906732553e91ec5) -- AIT-GUI Issue #75 - Work on making broker zeroMQ proxy and connecting streams with PUB/SUB sockets [`a230e6a`](https://github.com/NASA-AMMOS/AIT-Core/commit/a230e6a3653efdb147beee44ea4bc8b5769ab868) -- GUI Issue #75 - Updating imports, passing of zmq parameters, handler searching and instantiation [`7ce81a8`](https://github.com/NASA-AMMOS/AIT-Core/commit/7ce81a89d4fc9aa0899ea7a3fe897471e33c9c93) -- Issue #75 - Initial work on testing [`eadac90`](https://github.com/NASA-AMMOS/AIT-Core/commit/eadac90988fc245cd0f05e101145acedd53b9485) -- GUI Issue #75 - Adding some documentation [`dabf539`](https://github.com/NASA-AMMOS/AIT-Core/commit/dabf5397b87998ce8696ec4ecf27f103c1bb8af8) -- Server architecture documentation updates [`93320cb`](https://github.com/NASA-AMMOS/AIT-Core/commit/93320cbf056b3fb17b67990668feb9c463bf6951) -- GUI Issue #75 - Renaming AITServer to Server; renaming AITBroker to Broker [`2bf2917`](https://github.com/NASA-AMMOS/AIT-Core/commit/2bf2917725c4f977c637032573eea6442baa0ea7) -- GUI Issue #75 - More updates to unit tests [`f65f52a`](https://github.com/NASA-AMMOS/AIT-Core/commit/f65f52a5ee629ee672a4acd1be7efba995aafe0f) -- GUI Issue #75 - Making plugins specify outbound streams that subscribe to them instead of outbound streams specifying plugins they subscribe to [`adaa7ac`](https://github.com/NASA-AMMOS/AIT-Core/commit/adaa7ac2824d6f9a23fefd70cb0ee4ee33919ae1) -- AIT-GUI Issue #75 - Getting rid of inbound/outbound stream distinct classes; getting rid of stream input_type attribute since stream doesn't care about its input type [`91e98b1`](https://github.com/NASA-AMMOS/AIT-Core/commit/91e98b12647daa477966bce4c116c2400b222dde) -- AIT-GUI Issue #75 [`be299b3`](https://github.com/NASA-AMMOS/AIT-Core/commit/be299b3a1488500977a7dcdfc7993296d7628b47) -- GUI Issue #75 [`dcc54fc`](https://github.com/NASA-AMMOS/AIT-Core/commit/dcc54fc09b1994dd52702447b95b40df9930f766) -- Remove AIT GUI singleton object [`df2d3bf`](https://github.com/NASA-AMMOS/AIT-Core/commit/df2d3bfc94e4741831bc516e3b316c91ce00438c) -- GUI Issue #75 - Implementing plugin without greenlet as process method is called on message received through parent Client class; [`4ce6680`](https://github.com/NASA-AMMOS/AIT-Core/commit/4ce66809bb1e0485de350fa09ca71de571b2286a) -- Add telem limit monitor plugin [`02237ae`](https://github.com/NASA-AMMOS/AIT-Core/commit/02237ae87dbf1899ea9f60042516964f1d38fde7) -- Trying to replace prxy with custom loop for gevent [`1999acd`](https://github.com/NASA-AMMOS/AIT-Core/commit/1999acdfc614d4d2de2f1541963257401c7ffb14) -- Issue #162 - Added more robust handling of APID masking in CCSDSHandler [`f170819`](https://github.com/NASA-AMMOS/AIT-Core/commit/f1708193699b48ea32ab1281957ba348b5f393fa) -- Updated syntax for print statements [`6e20e27`](https://github.com/NASA-AMMOS/AIT-Core/commit/6e20e2757177ddf71df4dce0effb35c6f5bbff33) -- AitServer to AITServer rename [`2a30aef`](https://github.com/NASA-AMMOS/AIT-Core/commit/2a30aef880c90960a9c60d1685af0c35565bd323) -- AIT-GUI Issue #75 - Refactoring parsing of stream configs to generalize for inbound/outbound streams [`b27d790`](https://github.com/NASA-AMMOS/AIT-Core/commit/b27d7901e06e59e51ff08a3f8592b921a270be78) -- AIT-GUI Issue #75 - fixes, adding subscribe functionality, making topics stream/plugin names [`db6d9df`](https://github.com/NASA-AMMOS/AIT-Core/commit/db6d9df0f8da67be1c5160264f147fc5415487fc) -- GUI Issue #75 - porting data archival to plugin [`7901f37`](https://github.com/NASA-AMMOS/AIT-Core/commit/7901f375fd7304f70c1a7ff9291af5e66fdfa2b1) -- test [`01ecc97`](https://github.com/NASA-AMMOS/AIT-Core/commit/01ecc974eb953d2273ed258c5c7126605684dacb) -- investigate [`f4b47e3`](https://github.com/NASA-AMMOS/AIT-Core/commit/f4b47e340e4767c267221bf3f5366f1f89cfe511) -- GUI Issue #75 - Updates to stream input config and parsing [`925a2ea`](https://github.com/NASA-AMMOS/AIT-Core/commit/925a2ea217cf2d0689bf42f84615bc11c02fff44) -- Issue #132 - Add derived telemetry documentation [`8ec1855`](https://github.com/NASA-AMMOS/AIT-Core/commit/8ec1855525905144d3bc808d1da8228e7f453deb) -- Issue #178 - Fixed SQLite connect and commit functions [`24b9464`](https://github.com/NASA-AMMOS/AIT-Core/commit/24b9464b42c93b83e553b285f54436ef51b754c9) -- Issue #168 - CmdApi has new method for parsing arguments via cmd-arg definitions [`e51689a`](https://github.com/NASA-AMMOS/AIT-Core/commit/e51689a7a2699d9e59d747d785237f5e554e59ba) -- Issue #159 - Stream handles None return from handlers [`7fdedd1`](https://github.com/NASA-AMMOS/AIT-Core/commit/7fdedd16b9bcb74a8fb7ad72de8ab59d76610e76) -- bring config.yamli back to default [`cab0345`](https://github.com/NASA-AMMOS/AIT-Core/commit/cab0345579a22c46b40aa5575e46ba38c79549f4) -- Issue #224 - replace dsn section to AIT-DSN dsn section [`1ae3669`](https://github.com/NASA-AMMOS/AIT-Core/commit/1ae366946f81e3ee28cd6ce5d9e19f79a232f8de) -- Issue #159 - Added log messages for handler failures [`448f155`](https://github.com/NASA-AMMOS/AIT-Core/commit/448f15591462976f21f5a4845b36feff583584e2) -- GUI Issue #75 - Updates to DataArchive plugin to make db connection in initialization of plugin, not on every message; raises errors initialization so that plugin is killed; replaced regex string splitting [`7f071c5`](https://github.com/NASA-AMMOS/AIT-Core/commit/7f071c53ecc55fa66313536eff2860012f692eaf) -- Updates after rebase to get DataArchive working again [`3479ba8`](https://github.com/NASA-AMMOS/AIT-Core/commit/3479ba80a46e8170ac5a47f635ca319a82e7f38f) -- Issue #68 - Add sequence documentation and example [`cc6b5cc`](https://github.com/NASA-AMMOS/AIT-Core/commit/cc6b5cc8858f3c91ee606eafe7365ae465de62e3) -- Issue #66 - Updated test_dtype to include regression tests for type string [`6d7438f`](https://github.com/NASA-AMMOS/AIT-Core/commit/6d7438f7b58f66325a7553d66be8d0a47c1b259a) -- GUI Issue #75 - Removing ZMQ context and broker XPUB/XSUB sockets as arguments to clients; clients now access them directly through ait.broker [`13a6062`](https://github.com/NASA-AMMOS/AIT-Core/commit/13a6062cf7d8c5f7a61578afef628cfe2ddbfade) -- Removed extraneous cfg and log imports [`d243fa6`](https://github.com/NASA-AMMOS/AIT-Core/commit/d243fa6cbc2833437e3a99f47f45fc8f11631380) -- GUI Issue #75 - Further cleanup [`c3590c7`](https://github.com/NASA-AMMOS/AIT-Core/commit/c3590c7b9e4e5b0eb6492fd08281cccf45c13749) -- GUI Issue #75 - Fixing GUI thread blocking [`5a5508c`](https://github.com/NASA-AMMOS/AIT-Core/commit/5a5508cce301113384e5ce2dcaa96f29a712adfd) -- Issue #162 - Moved some functionality from handle to comp_apid in CCSDSPacketHandler [`692777a`](https://github.com/NASA-AMMOS/AIT-Core/commit/692777a9290ff3299c17b0fff77280c4c27623d4) -- Fixed logic for loading cmd arg table dict before default dict [`d6907df`](https://github.com/NASA-AMMOS/AIT-Core/commit/d6907dff3550a924c14f2cebb0a7b7f842f08ea2) -- Fixed some errors during ait-server startup and running test_server.py [`f1ac6da`](https://github.com/NASA-AMMOS/AIT-Core/commit/f1ac6da833e6f4e8709d61f01b0eebac8dd547fa) -- Issue #75 - Updates to broker logging and test example [`ed97d6e`](https://github.com/NASA-AMMOS/AIT-Core/commit/ed97d6e66d4d02ed9d79d44cf23742496f64062e) -- AitBroker to AITBroker rename [`8c0c47c`](https://github.com/NASA-AMMOS/AIT-Core/commit/8c0c47c73b6bc508459a4dcfba41265a89661b7e) -- Add ait-server docs and fix import execution [`06ee0c1`](https://github.com/NASA-AMMOS/AIT-Core/commit/06ee0c1290b5e9c01195da541ff8ae6693e33b3e) -- Fixed monkey patch warnings [`e693891`](https://github.com/NASA-AMMOS/AIT-Core/commit/e693891f8df43ec808f949eb3fdad5cb5427df53) -- GUI Issue #75 - Update tests to reflect change in stream input parsing [`a4d4977`](https://github.com/NASA-AMMOS/AIT-Core/commit/a4d4977f292781528b75225d6253579c6b35b865) -- Issue #66 - Strarg validation includes err mesg when arg is numeric [`d3c67d4`](https://github.com/NASA-AMMOS/AIT-Core/commit/d3c67d4a3e855eeeb032d11c42e5c7aa98d48b55) -- Updated openmct plugin to support configurable stream names [`7d4c778`](https://github.com/NASA-AMMOS/AIT-Core/commit/7d4c778f53bdb20f4e6dd49182ba0cab354238b9) -- Updates to get test_bsc.py to run [`fe602ad`](https://github.com/NASA-AMMOS/AIT-Core/commit/fe602ad3c2700c647a1d3c1277655ed9a094aee0) -- Issue #167 - add handle_includes func [`afa3954`](https://github.com/NASA-AMMOS/AIT-Core/commit/afa3954767806ca13797d7b96da8be5f6bdd15d8) -- Issue #281 - Update CmdAPI with None upd_dest default [`9f1d66f`](https://github.com/NASA-AMMOS/AIT-Core/commit/9f1d66f29ba3f4b1bf06020bf9f48ae7322dad07) -- Replaced mock import with unittest [`c07da09`](https://github.com/NASA-AMMOS/AIT-Core/commit/c07da0928e5a663b58dcf2d9ac861bf7373e534b) -- Updated IOError syntax [`751a8e4`](https://github.com/NASA-AMMOS/AIT-Core/commit/751a8e494801b9bf98ef144447cd08fe5298a350) -- Issue #185 - Fixed CCSDS Packet Handler APID comparison [`ea067b3`](https://github.com/NASA-AMMOS/AIT-Core/commit/ea067b3516ea90c13d73b8ec51234ad952fb8344) -- Add new command with fixed argument to cmd.yaml for testing [`0428bcf`](https://github.com/NASA-AMMOS/AIT-Core/commit/0428bcffa3165408d43f845e9849e81da012b6f0) -- Issue #190 - Add example script and update config script directory [`bc5ac7c`](https://github.com/NASA-AMMOS/AIT-Core/commit/bc5ac7ccc1f40f0736dd2a54cdcf65fa249055fd) -- Issue #99 - Add documentation about default command encoding format [`4dc7a72`](https://github.com/NASA-AMMOS/AIT-Core/commit/4dc7a72a4274ef635fdeda8788cc3529eb2c4915) -- Issue #142 - Reduce server.client log message noise [`036bf22`](https://github.com/NASA-AMMOS/AIT-Core/commit/036bf22c1293e981dbb418aa7bf949f9005610b7) -- Issue #169 - Changed pop to get in _create_plugin in server.py [`97dae70`](https://github.com/NASA-AMMOS/AIT-Core/commit/97dae70daa7c1def4b5117513320e9732a95ef8c) -- Dtype should encode str vals, added unit test case [`55c2ca1`](https://github.com/NASA-AMMOS/AIT-Core/commit/55c2ca1a7d4aa8a9ad745bffcec4f1a0389c4cb9) -- Updated default yaml loader [`700a3da`](https://github.com/NASA-AMMOS/AIT-Core/commit/700a3da622d3f9015890d34ef47c2ea4da209516) -- Updated install_requires package versions [`568af24`](https://github.com/NASA-AMMOS/AIT-Core/commit/568af24a2f67b608ced7dbcc5946b48f98dc158c) -- update format as a list [`e0951ea`](https://github.com/NASA-AMMOS/AIT-Core/commit/e0951eaee4b552fbcc7741d08e35cbeacb7f37e7) -- Update checks for data/streams being of file type [`7847516`](https://github.com/NASA-AMMOS/AIT-Core/commit/784751678d991c1892ec32a92a75754b06c0b26d) -- Moved config deep copy to beginning of method [`e5a7752`](https://github.com/NASA-AMMOS/AIT-Core/commit/e5a7752ad86f7cf7b7c2e08c74cd315db1bb4c6e) -- Make TelemetryLimitMonitor plugin robust to poorly formed input [`a133ef7`](https://github.com/NASA-AMMOS/AIT-Core/commit/a133ef7eff791c46c47a0731d5af40978c9eea98) -- Updated cPickle to pickle [`d6e8090`](https://github.com/NASA-AMMOS/AIT-Core/commit/d6e80907368349069aafefa387fc69b7e5bf2acc) -- Issue #159 - Changed variable names in PacketHandler [`e4a4e20`](https://github.com/NASA-AMMOS/AIT-Core/commit/e4a4e200f03458f97c8844dbf745566d6d978d70) -- Issue #159 - Fixed PacketHandler bug [`c60d722`](https://github.com/NASA-AMMOS/AIT-Core/commit/c60d722637e6003dfcac787850e3a16ea71dac39) -- Issue #75 - Moving server port defaults to init file; having broker check for them in configs first [`3bcdc80`](https://github.com/NASA-AMMOS/AIT-Core/commit/3bcdc80167d673d09f45023e7160a98384526a8f) -- Updated ait/core __init__.py, server.py, stream.py imports to be relative [`9d19ba8`](https://github.com/NASA-AMMOS/AIT-Core/commit/9d19ba8ec62367e8eb41e69bdb9eab17fd7d2518) -- Issue #159 - Updated error messages for handler [`fbd6cee`](https://github.com/NASA-AMMOS/AIT-Core/commit/fbd6cee6428518665cede787f09d4fbe23e1f7f9) -- Resolved some errors in getting the gui plugin to work [`c297ea3`](https://github.com/NASA-AMMOS/AIT-Core/commit/c297ea3da5514fb80af694178b75e3ff47844531) -- Issue #141 - Fix issue with optional Plugin attrs not being passed [`1b9d3b8`](https://github.com/NASA-AMMOS/AIT-Core/commit/1b9d3b87c4036886736ced25848634f2a1ec41ec) -- add GUI plugin setting [`bd6cfee`](https://github.com/NASA-AMMOS/AIT-Core/commit/bd6cfeed9deaaf6dcf84be497d4ceaf61ece478f) -- Issue #178 - Added commit statement and quotation marks to SQLiteBackend functions [`774b093`](https://github.com/NASA-AMMOS/AIT-Core/commit/774b0938ca2ee504765c6499d6a690742b0fbecb) -- Issue #171 - Changed plugins to accept pickle.dumps as input [`19be8bc`](https://github.com/NASA-AMMOS/AIT-Core/commit/19be8bc499fe1a41b0bd06039c8f2e1edb53ba61) -- Default dates must be formatted as str, wrap generator as list [`46653a0`](https://github.com/NASA-AMMOS/AIT-Core/commit/46653a03f8c4d9df2569775281987968e83ff5c8) -- Updated tlm packet byte calcuation [`251b944`](https://github.com/NASA-AMMOS/AIT-Core/commit/251b94476df50e86d157851107e55561fc5b6bdd) -- Added cfg import to multiple test_ files [`67be3eb`](https://github.com/NASA-AMMOS/AIT-Core/commit/67be3eb18d0c460cd086f111fee6c53dbd6dd605) -- Issue #180 - Insert default time column in SQLite create table function [`93f9cc9`](https://github.com/NASA-AMMOS/AIT-Core/commit/93f9cc961be7777c145d45216a6e9dae440a75ac) -- GUI Issue #75 - Docs for data archival plugin [`8f89e50`](https://github.com/NASA-AMMOS/AIT-Core/commit/8f89e50db25046b70fc257e4a57681b1c017c111) -- Issue #180 - Changed SQLite database insert to be based on fields [`63eb21e`](https://github.com/NASA-AMMOS/AIT-Core/commit/63eb21ef173f6f802fff1c822d997be099c2a898) -- Fixes for running test_val [`e34f773`](https://github.com/NASA-AMMOS/AIT-Core/commit/e34f7730d66bdc74bfbb48298c093a0298cc8a2b) -- Fixed client import and updated zmq send/recv to send_string/recv_string [`c1e3e6d`](https://github.com/NASA-AMMOS/AIT-Core/commit/c1e3e6d41aaa791cbd34b02f2eb50a36ffc962e2) -- Issue #159 - Dynamically type check handler for Stream log message [`95e786f`](https://github.com/NASA-AMMOS/AIT-Core/commit/95e786f692d85293947db026d555a0c33153c667) -- Issue #159 - Added log messages to Stream when handlers return None [`d3b824c`](https://github.com/NASA-AMMOS/AIT-Core/commit/d3b824c569e4c7982f250984354e44247e2cae6f) -- GUI Issue #75 - Fix bug related to stream port input parsing [`9490466`](https://github.com/NASA-AMMOS/AIT-Core/commit/94904664a1852979b5ceb6bddbb10c13822a61d4) -- GUI Issue #75 - Updates to server tests [`4f1b80c`](https://github.com/NASA-AMMOS/AIT-Core/commit/4f1b80c170d295728073bd1da25453769a2ad209) -- Read and write leapseconds.dat in binary [`5b38c3f`](https://github.com/NASA-AMMOS/AIT-Core/commit/5b38c3fc9760c4097dbd519f5d4a87d6ad42c1b2) -- Issue #150 - PortOutputClient to dump raw message data [`267e705`](https://github.com/NASA-AMMOS/AIT-Core/commit/267e705b943560cf0d3e49f72f0313eebd0494b8) -- Specify Python version in RTD config [`8d0483d`](https://github.com/NASA-AMMOS/AIT-Core/commit/8d0483d00a3197e3ff680fe71e8aa22c8b0c8b8e) -- Update README.rst [`310549d`](https://github.com/NASA-AMMOS/AIT-Core/commit/310549dcfc18dad647eb20c354b20b3bada6e5b1) -- Specify Python version in RTD config [`1b02d3f`](https://github.com/NASA-AMMOS/AIT-Core/commit/1b02d3f380d194efe2bc4e7a86765b4004a0256a) -- Update README.rst [`66f2ee0`](https://github.com/NASA-AMMOS/AIT-Core/commit/66f2ee05357056b0d4455129e1dc28c264d39634) -- Fixed exception syntax errors [`e2d0f15`](https://github.com/NASA-AMMOS/AIT-Core/commit/e2d0f15dde54719be7e405cc77b22aed3371f1c3) -- Fixed nosetest errors in dtype and dmc [`fb8dc7b`](https://github.com/NASA-AMMOS/AIT-Core/commit/fb8dc7b0cb25762e4530d1096c1794b27550bc63) -- Updated tlm packet simulate to match behavior in py2 [`e32aca8`](https://github.com/NASA-AMMOS/AIT-Core/commit/e32aca8dec8f318f880685f3fe0155216efd83c8) -- Fixed errors when running test_cmd.py [`a442277`](https://github.com/NASA-AMMOS/AIT-Core/commit/a44227787337aa48eaa948f27cbf9d9b2dae9ba6) -- Updated string formatting in tlm.py and util.py [`d969743`](https://github.com/NASA-AMMOS/AIT-Core/commit/d969743f01e8a0c1825b170e350be81d81308bc9) -- Issue #184 - Changed Ethernet_HS_Packet definition field name from time and updated docs [`05ef04e`](https://github.com/NASA-AMMOS/AIT-Core/commit/05ef04e9a84015deeb31806f63bb9aa5f8777308) -- Issue #159 - Removed logging messages [`b3e5701`](https://github.com/NASA-AMMOS/AIT-Core/commit/b3e5701f314abe5765d85bc2d5cd217062963874) -- GUI Issue #75 - Update to docs regarding inbound stream port inputs [`dc12eaa`](https://github.com/NASA-AMMOS/AIT-Core/commit/dc12eaa7daa10f67b4c586e9441753877cca1ffe) -- Issue #144 - Serialize PacketHandler output [`ed5e3e8`](https://github.com/NASA-AMMOS/AIT-Core/commit/ed5e3e8bd8e9049e7a892a9d8accca622e16ab38) -- Updates to CHANGELOG [`e628db4`](https://github.com/NASA-AMMOS/AIT-Core/commit/e628db4a413ed18c8bb0dc54387a723b1352227d) -- Pcap data field must be decoded to print [`13107db`](https://github.com/NASA-AMMOS/AIT-Core/commit/13107db3e6aa05cec8f6a223be068bfb7cba8400) -- fix GUI plugin setting [`1f3daa8`](https://github.com/NASA-AMMOS/AIT-Core/commit/1f3daa87d306e7fbd6765d087dd437b114f722c3) -- Updated travis config py version [`cf7b161`](https://github.com/NASA-AMMOS/AIT-Core/commit/cf7b161cc15c159b21e5f90239c19169afcadf22) -- Updated tlm simulate to use utf-8 encoding [`45bc194`](https://github.com/NASA-AMMOS/AIT-Core/commit/45bc19451e13bd8a7a4015724c6fda903c88c9b5) -- Added cfg import in test_notfiy.py [`031d1ce`](https://github.com/NASA-AMMOS/AIT-Core/commit/031d1cec5b35bb4c376e938ce2bda9b000b179e6) -- Restored U8 type for product_type field [`d1103d4`](https://github.com/NASA-AMMOS/AIT-Core/commit/d1103d4e88601c95fa0407723f9062c7f2219da8) -- Added cfg import to test_val.py [`28645cc`](https://github.com/NASA-AMMOS/AIT-Core/commit/28645cc36de0eb4b3132336e56a4ec9de4d94cd3) -- Fixed test file path in test_util.py [`e4f576b`](https://github.com/NASA-AMMOS/AIT-Core/commit/e4f576bcd120f4d5076ae91ea027b84fdb276e22) -- Added cfg import in test_dtype.py [`91df57a`](https://github.com/NASA-AMMOS/AIT-Core/commit/91df57abc3213219f310c7645c81f76b48a7c8f8) -- Fixed error when running test_cfg.py [`3436af7`](https://github.com/NASA-AMMOS/AIT-Core/commit/3436af7fe2604a222eed43871a61bab8a18b1d7c) -- Added cfg import to util.py [`aafd00c`](https://github.com/NASA-AMMOS/AIT-Core/commit/aafd00c388853b5429b6df7113259339d6dda61b) -- Updated tlm.yaml product_type field type to MSB_U32 [`7b379a5`](https://github.com/NASA-AMMOS/AIT-Core/commit/7b379a586f3b96cd7186b8079a910f566596fbc5) -- Updated string format in util.py [`86c7e4d`](https://github.com/NASA-AMMOS/AIT-Core/commit/86c7e4d5a61f4241597ec8263c4eb75fac475413) -- Iterate through dict copy since the size of original is changed during iteration [`a26be84`](https://github.com/NASA-AMMOS/AIT-Core/commit/a26be84ccfaa0a37b0b3c4fb6a1d15e865d6fb82) -- Updated project setup link to be internal doc reference [`e4a1475`](https://github.com/NASA-AMMOS/AIT-Core/commit/e4a1475f03a5130754c5b9bd2c0ab9f16f730a78) -- Fixed project setup link in docs [`c2355ce`](https://github.com/NASA-AMMOS/AIT-Core/commit/c2355ce6551019f816a9de17ade7900045ebaa06) -- Issue #208 - Update server docs to reference new plugin API pages [`14ad2c1`](https://github.com/NASA-AMMOS/AIT-Core/commit/14ad2c193995b43af10fadf8e2a3bc169cd4d079) -- Updated python requests version number requirement [`d93ab72`](https://github.com/NASA-AMMOS/AIT-Core/commit/d93ab7249967b7db3ee6ed90bbd521fdcc56b3ae) -- Issue #149 - Update default log_stream port [`a025c31`](https://github.com/NASA-AMMOS/AIT-Core/commit/a025c317e3dd50d9129c86101016f27961a48554) -- Fix typo in API documentation [`971ba68`](https://github.com/NASA-AMMOS/AIT-Core/commit/971ba688a13381dded93e3edb57c5eb47fb17d62) -- GUI Issue #75 - Updating docs on stream types [`4e67ec6`](https://github.com/NASA-AMMOS/AIT-Core/commit/4e67ec668e9041477de6cb04d2cc281d85995f39) -- GUI Issue #75 - Updating database docs, adding reference to Data Archive Plugin [`22e1792`](https://github.com/NASA-AMMOS/AIT-Core/commit/22e17928697c61c9d8da38aadcd7ccfabfeb3f30) -- Added eval to PortOutputClient publish [`3a35e93`](https://github.com/NASA-AMMOS/AIT-Core/commit/3a35e937a040c829174958596bedfa875bdf5e20) -- Updated TelemetryLimitMonitor plugin [`b882ce6`](https://github.com/NASA-AMMOS/AIT-Core/commit/b882ce6f4ffdab01fb3a595a335341368bb95400) -- Added type for derivation field in tlm.yaml [`e17a3df`](https://github.com/NASA-AMMOS/AIT-Core/commit/e17a3dff462d081f05e329a79ef18c532f577603) -- Issue #168 - Updating ait_seq_send.py to use new CmdApi.parseArgs() method [`b87bf20`](https://github.com/NASA-AMMOS/AIT-Core/commit/b87bf207891c64eb4057f8b041beb03581b88c82) -- Issue #159 - Added comments to PacketHandler [`7b466b8`](https://github.com/NASA-AMMOS/AIT-Core/commit/7b466b868644ad4eb60e7520253e711629cf1bc1) -- GUI Issue #75 - Adding pyzmq installation requirement [`e136d4c`](https://github.com/NASA-AMMOS/AIT-Core/commit/e136d4cd251d20ba9321a4f138122953915ba36b) - -## [1.4.0](https://github.com/NASA-AMMOS/AIT-Core/compare/1.3.0...1.4.0) - 2019-09-04 - -### Commits - -- Issue #7 - Adding DerivationDefinition class and updating Packet and PacketDefinition classes with derivations; adding derivation construction from yaml [`33baffc`](https://github.com/NASA-AMMOS/AIT-Core/commit/33baffcf390ce7c63930b47e8aeb81c3c850c4a7) -- Issue #7 - Renaming test packet names to be generic [`af14439`](https://github.com/NASA-AMMOS/AIT-Core/commit/af14439a9922ccecfa08de6c359516602e92c633) -- Issue #7 - Adding test of derivation definition class to test_tlm file [`3d54ec8`](https://github.com/NASA-AMMOS/AIT-Core/commit/3d54ec88c0c9837621e310b7c7e73e2079e39ff1) -- Issue #7 - adding derivation to json schema [`a5a48b5`](https://github.com/NASA-AMMOS/AIT-Core/commit/a5a48b52adca1e14b244dcd70780012ad101dd21) -- Update CHANGELOG [`d916c3c`](https://github.com/NASA-AMMOS/AIT-Core/commit/d916c3ce65e835034cf3c0e9a507f3cd97aee63c) -- Issue #7 - Adding check for derivations to Packet._hasattr, expanding test of DerivationDefinition [`f96b719`](https://github.com/NASA-AMMOS/AIT-Core/commit/f96b719ba3073ef718507da79aa46cf6ad3d7c46) -- Issue #7 - Adding derivation to default tlm.yaml file [`958637c`](https://github.com/NASA-AMMOS/AIT-Core/commit/958637ce98304b1949adb5e5e1b2cb3916f49021) -- Preparation for 1.4.0 release [`cf0bb29`](https://github.com/NASA-AMMOS/AIT-Core/commit/cf0bb2988a5ce49e3bf5c01f1a2747e93c383ea3) -- AIT-GUI Issue #92 - Adding notifications options to default config [`31a10d1`](https://github.com/NASA-AMMOS/AIT-Core/commit/31a10d1f46c7d970fb795be04d77c2f42f97428c) -- Name cleanup in configuration documentation [`478044b`](https://github.com/NASA-AMMOS/AIT-Core/commit/478044b91ed7149f5402be9b37a28ef652d81407) -- Update leapseconds config due to expected next update change [`615192e`](https://github.com/NASA-AMMOS/AIT-Core/commit/615192e3f79f82a4a53abe0872e28cbd49faad1f) -- AIT-GUI Issue #92 - Updating notif option example config [`96a4a75`](https://github.com/NASA-AMMOS/AIT-Core/commit/96a4a75610ec5d0b9726d8a8725abdca6c4589e9) - -## [1.3.0](https://github.com/NASA-AMMOS/AIT-Core/compare/1.2.0...1.3.0) - 2019-09-04 - -### Commits - -- Issue #83 - Baseline example configs across repos [`4bd59bb`](https://github.com/NASA-AMMOS/AIT-Core/commit/4bd59bbaae4ff6077e04aaadd93d6b760a6bb5e2) -- Issue #83 - Baseline example configs across repos [`8240bee`](https://github.com/NASA-AMMOS/AIT-Core/commit/8240bee22b0174dd73bb15c0727e521657cdccd5) -- Issue #83 - Baseline example configs across repos [`481f272`](https://github.com/NASA-AMMOS/AIT-Core/commit/481f272e37f95d7362686162705156724b4ba6b7) -- Issue #75 - Create script for generating dummy telemetry data for tests [`262dd9f`](https://github.com/NASA-AMMOS/AIT-Core/commit/262dd9f86b33fd6015678bcf5d7cdc9b162b4b27) -- Issue 121 - Expand telemetry when and dntoeu documentation [`0a048f7`](https://github.com/NASA-AMMOS/AIT-Core/commit/0a048f7f3e78c30bd90812d55dd2591c8082d788) -- Issue #119 - Update documentation on telemetry dictionary [`9d6346f`](https://github.com/NASA-AMMOS/AIT-Core/commit/9d6346f9c8779a1636276c8c3bb0c034282ac9c6) -- Issue #83 - Baseline example configs across repos [`7958265`](https://github.com/NASA-AMMOS/AIT-Core/commit/7958265994f593ede53caef08c6c0b6f47232324) -- Issue #115 - Config file referenced with relative path [`439f5da`](https://github.com/NASA-AMMOS/AIT-Core/commit/439f5daeb295af1ca2c7d33752ef2172782cf7a1) -- Issue #119 - Update documentation on telemetry dictionary [`8b4459e`](https://github.com/NASA-AMMOS/AIT-Core/commit/8b4459ea6dea6d1ab6766ba47531b0d7f3d887fb) -- Issue #83 - Baseline example configs across repos [`c3456ba`](https://github.com/NASA-AMMOS/AIT-Core/commit/c3456ba269ce294139d6d7129613c68626012e52) -- Issue #129: Update EVRType to better handle unknown EVRs [`074d1d3`](https://github.com/NASA-AMMOS/AIT-Core/commit/074d1d3d0eb8ab6a57904ebacf76a24b98dadaf5) -- Issue #25 - bliss_cmd_send hardcoded to 127.0.0.1 [`8e0e290`](https://github.com/NASA-AMMOS/AIT-Core/commit/8e0e2904bcd439794ab5061bef026a2a918dd599) -- Prep for release 1.3.0 [`a7a7e1e`](https://github.com/NASA-AMMOS/AIT-Core/commit/a7a7e1e53631d5483555999d038a1fa456b086fa) -- Issue #83 - Baseline example configs across repos [`92b7918`](https://github.com/NASA-AMMOS/AIT-Core/commit/92b7918826fc08e942052f09308e28b45a7f9e16) -- Update .gitignore [`0d99ec9`](https://github.com/NASA-AMMOS/AIT-Core/commit/0d99ec94df8589574770bc406ad8e22764a2b2a7) -- Issue #119 - Update documentation on telemetry dictionary [`64de9c5`](https://github.com/NASA-AMMOS/AIT-Core/commit/64de9c576ab883c1580532312b7797c3387d6b1b) -- Issue #83: Baseline example configs across repos [`93a63cf`](https://github.com/NASA-AMMOS/AIT-Core/commit/93a63cf50353364d89e2cea3b756f41226e89d30) -- Update Copyright date [`bd2cce1`](https://github.com/NASA-AMMOS/AIT-Core/commit/bd2cce176287974a2aac7211d8403e8360ca01e3) -- Issue #124 - Removing reload of default config file on test initialization [`a5b6213`](https://github.com/NASA-AMMOS/AIT-Core/commit/a5b6213fcbfe38fadd1e53445ce7965e9285fa0f) -- Update .gitignore [`cbe761a`](https://github.com/NASA-AMMOS/AIT-Core/commit/cbe761a0a8ad0ced5228784b93dd72e91a88b2c5) -- Issue #75 - Create script for generating dummy telemetry data for tests [`4d65696`](https://github.com/NASA-AMMOS/AIT-Core/commit/4d65696a72ee7e4931c8d77e77e5490c480f860d) -- Issue #83 - Baseline example configs across repos [`70cf2b0`](https://github.com/NASA-AMMOS/AIT-Core/commit/70cf2b02666cbf6ee23fa2d4d9cc96a9a6ca7bb6) -- Issue #83 - Baseline example configs across repos [`4fd96dd`](https://github.com/NASA-AMMOS/AIT-Core/commit/4fd96dd9c5f5b7cc0959c14286a9d9ddd3031926) - -## [1.2.0](https://github.com/NASA-AMMOS/AIT-Core/compare/1.1.0...1.2.0) - 2019-09-04 - -### Commits - -- Issue #112 - Expand EVR Format Message Handling [`57a54fe`](https://github.com/NASA-AMMOS/AIT-Core/commit/57a54fe0b212ab248fe016aff6a0be2cab238975) -- Prep for 1.2.0 release [`32f0673`](https://github.com/NASA-AMMOS/AIT-Core/commit/32f0673074ab0655f2f16c5a3ab9eefec2239159) -- Issue #109 - Add latest build release to travisci config [`0793b44`](https://github.com/NASA-AMMOS/AIT-Core/commit/0793b448095f76a99982007e23c30e8116ae797f) -- Issue #104: add unsecured SMTP server access [`db5b7cd`](https://github.com/NASA-AMMOS/AIT-Core/commit/db5b7cd2b0621f1a446eacb90363caa246e0fa15) -- Issue #109 - Drop release testing from travis.yaml [`b6a7b88`](https://github.com/NASA-AMMOS/AIT-Core/commit/b6a7b8857c0bfbda58d41fce75ec2ca0cf288107) -- Issue #109 - Explicity create tag for latest master build each deploy [`47f47a4`](https://github.com/NASA-AMMOS/AIT-Core/commit/47f47a4b6f27c94fe43c2cee9ebdb10b6b938449) -- Issue #109 - TravisCI release updates for tag naming [`82d30ba`](https://github.com/NASA-AMMOS/AIT-Core/commit/82d30ba45a88e1670f96f42b4bccb1b2390a2317) -- Issue #63 - Typos in install documentation [`41216ee`](https://github.com/NASA-AMMOS/AIT-Core/commit/41216ee3616e3b611a0fc5f068dd44e3d9b33970) -- Issue #79: ait-pcap help message cleanup [`8df4bd3`](https://github.com/NASA-AMMOS/AIT-Core/commit/8df4bd38a21e05b821b969264df552f1196ff162) -- Issue #79: ait-pcap help message cleanup [`a73b00d`](https://github.com/NASA-AMMOS/AIT-Core/commit/a73b00d5fb9bddc09ec25c79df0dcebef01c8471) -- Issue #109 - Update TravisCI build GH token handling for tagging latest [`92ec59a`](https://github.com/NASA-AMMOS/AIT-Core/commit/92ec59af786c019e15445e822b124d1f2e3d9814) -- Issue #109 - Only run deploy on non-tag build [`e240cfa`](https://github.com/NASA-AMMOS/AIT-Core/commit/e240cfa0e7d5ec0481e54cc22fb7e06c2f310434) -- Issue #101: ait-tlm-csv warning when field not detected results in a lot of spam [`de3204b`](https://github.com/NASA-AMMOS/AIT-Core/commit/de3204bd6c207cc075f70557a38cbaac9ab661d2) -- Issue #102: Allow comments inline with commands [`acc87b3`](https://github.com/NASA-AMMOS/AIT-Core/commit/acc87b3037a4ae9f9e89c8227d3526d0dbc9efbc) - -## [1.1.0](https://github.com/NASA-AMMOS/AIT-Core/compare/1.0.0...1.1.0) - 2019-09-04 - -### Commits - -- Issue #85 - Expand core.db backend support [`1168ec9`](https://github.com/NASA-AMMOS/AIT-Core/commit/1168ec9639b02f29b07bcd89f3db89f2a9531f6a) -- Issue #89 - Drop changelog and pypi scripts [`ee464a5`](https://github.com/NASA-AMMOS/AIT-Core/commit/ee464a51f690618f0bc35d6c0a7d2ea8a4d4e9df) -- Issue #85 - Add docs to DB classes [`60a403c`](https://github.com/NASA-AMMOS/AIT-Core/commit/60a403c758a982bb8132b2bf911b0a142fbffb68) -- Issue #58 - Remove contributing guide from Sphinx docs [`75479d7`](https://github.com/NASA-AMMOS/AIT-Core/commit/75479d7d724a7e49f98fd9505068c50fa84659cc) -- Issue #55 - Fix missing CHANGELOG releases [`ce536d6`](https://github.com/NASA-AMMOS/AIT-Core/commit/ce536d61e2db9d420530963dab53f7bad20a9f92) -- Issue #92 - Add extensions documentation [`493aa55`](https://github.com/NASA-AMMOS/AIT-Core/commit/493aa550bd127f141ec8ad6061ee10f944c47adb) -- Preparation for 1.1.0 release [`f4d72a4`](https://github.com/NASA-AMMOS/AIT-Core/commit/f4d72a45bcce477e64e53ad4bc0ae185e3b4106d) -- Issue #34: BLISS to AIT change for Latex dict software [`3cfdd6b`](https://github.com/NASA-AMMOS/AIT-Core/commit/3cfdd6bb495a119ebc5010caa047c35a984358f9) -- Issue #65 - Fix git hooks install on non-checkout version of repo [`15475e5`](https://github.com/NASA-AMMOS/AIT-Core/commit/15475e5733cc727ae3f9149d4717e3753f2b3cc8) -- Issue #97: add configurable subject and from address [`2513f41`](https://github.com/NASA-AMMOS/AIT-Core/commit/2513f41cb0d8f28011ff1577dfe93a3494270887) -- Issue #59 - Update README to match wiki landing page [`61382df`](https://github.com/NASA-AMMOS/AIT-Core/commit/61382dfa839d3119688e56cf3f2678a30599980e) -- Issue #85 - Add database docs to Sphinx [`c59ffd7`](https://github.com/NASA-AMMOS/AIT-Core/commit/c59ffd70eff96df9222e74807c6bac5c49772744) -- Issue #80 - Add default timestamp for get_GPS_offset_for_date [`af044cb`](https://github.com/NASA-AMMOS/AIT-Core/commit/af044cbbdff56c36339f3a678fa0e35163b314c1) -- Issue #94 - Fix typo in docs index [`ebfb75d`](https://github.com/NASA-AMMOS/AIT-Core/commit/ebfb75d9fc1167bcde8e13cc406e13fe076af51f) -- Issue #81 - Update Time40 size information [`1717eb2`](https://github.com/NASA-AMMOS/AIT-Core/commit/1717eb273eac54a6b1b2a226e0699fbc0f15e89c) - -## 1.0.0 - 2019-09-04 - -### Merged - -- Issue #33 - Switch BLISS naming to AIT [`#45`](https://github.com/NASA-AMMOS/AIT-Core/pull/45) -- Issue #514 - Update CmdAPI history handling to include cmd args [`#515`](https://github.com/NASA-AMMOS/AIT-Core/pull/515) -- Issue 484 fixes/updates to table encoding/decoding [`#509`](https://github.com/NASA-AMMOS/AIT-Core/pull/509) -- Issue #485 - Drop coord.ecef2geodetic function [`#486`](https://github.com/NASA-AMMOS/AIT-Core/pull/486) -- Issue #497: add time.sleep back to script [`#498`](https://github.com/NASA-AMMOS/AIT-Core/pull/498) -- Issue #487 - Switch all command sends to api.CmdAPI [`#488`](https://github.com/NASA-AMMOS/AIT-Core/pull/488) - -### Fixed - -- Issue #478 - Backport ECOSTRESS piecewise DN-to-EU functions [`#478`](https://github.com/NASA-AMMOS/AIT-Core/issues/478) - -### Commits - -- Initial import [`0550eaf`](https://github.com/NASA-AMMOS/AIT-Core/commit/0550eaf48c9998289f5a2408ac71d22739a79951) -- Update tlm/cmd dict Latex templates [`45d44aa`](https://github.com/NASA-AMMOS/AIT-Core/commit/45d44aa363acb9642ff4992a28d9513dbbb5699e) -- Issue #2 - Improve dmc leap second handling [`d655c7c`](https://github.com/NASA-AMMOS/AIT-Core/commit/d655c7c79c730369ed4d8478cb2cc95b162d6e28) -- Issue #31 - Add text and email notification support [`43a7204`](https://github.com/NASA-AMMOS/AIT-Core/commit/43a7204563367cff221123f5a1590dffa141fa75) -- Issue #512: Update table encode to allow outbin argument [`1dbad28`](https://github.com/NASA-AMMOS/AIT-Core/commit/1dbad286bf8fc1a7ec4d6e4508c0eaa461e2692f) -- Issue #471: add new bliss-tlm-csv script [`acf90b9`](https://github.com/NASA-AMMOS/AIT-Core/commit/acf90b9d32e3b2861d39d580431ab2dc6cb9db93) -- Issue #16 - Put docs on ReadTheDocs [`ad7ea47`](https://github.com/NASA-AMMOS/AIT-Core/commit/ad7ea477946ddbebca5b7603f83daec0e528cc13) -- Issue #26 - Guard against missing limit values in LimitDefinition [`4a493ca`](https://github.com/NASA-AMMOS/AIT-Core/commit/4a493cae09e738e09f156203c6fc8ddad2ea97b2) -- Issue #510: Add filename parsing the bliss_seq_encode [`b00ad24`](https://github.com/NASA-AMMOS/AIT-Core/commit/b00ad248e4637258a3c39df6c623bc9fde5951d9) -- Issue #52 - Convert README.md to README.rst for PyPi [`781d6e3`](https://github.com/NASA-AMMOS/AIT-Core/commit/781d6e373d2a0a9e4954ee5fc4699c02dddefcff) -- Issue #42 - Removed deprecated functions [`c9f713c`](https://github.com/NASA-AMMOS/AIT-Core/commit/c9f713c8778bf1ca1bc7d5e4a426040d10ec3706) -- Prep for 1.0.0 release [`16e520a`](https://github.com/NASA-AMMOS/AIT-Core/commit/16e520a97f9a757ccb07f903dc9368d7bc9812b5) -- Issue #467 - Remove eval from bsc bin script and fix arg parsing [`574148a`](https://github.com/NASA-AMMOS/AIT-Core/commit/574148aad25bb88d7e44cfc97355a23932588f95) -- Update bliss_seq_encode to allow multiple files [`ddae42c`](https://github.com/NASA-AMMOS/AIT-Core/commit/ddae42c0f5557c649da4c64bf4f7ed67e3144844) -- Prep for 0.37.0 release [`da62c47`](https://github.com/NASA-AMMOS/AIT-Core/commit/da62c4733261e4826ad980c04305b08183ca4641) -- Issue #465: persistence and when conditions added [`7cb71ac`](https://github.com/NASA-AMMOS/AIT-Core/commit/7cb71ac0a76fa98356fb33264bd99865a7415a2a) -- Issue #21 - Update README [`62102c7`](https://github.com/NASA-AMMOS/AIT-Core/commit/62102c7c947f1562e921b2d12be34e4582837a55) -- Issue #23 - Update Tlm to CSV script to support ground receipt time [`71d98e9`](https://github.com/NASA-AMMOS/AIT-Core/commit/71d98e95caee83673f873022f17fee2ca5d54766) -- Issue #472: add bliss-cmd-hist tool [`96df428`](https://github.com/NASA-AMMOS/AIT-Core/commit/96df428ec4fd7bc2afa557660f9d0067bb527934) -- Issue #491 - Add githook for ensuring that API docs are kept up to date [`d522a1d`](https://github.com/NASA-AMMOS/AIT-Core/commit/d522a1d229562d12beea7e30f78fc04f8d40cbfb) -- Issue #17 - Prepare to publish AIT-Core to Pypi [`f072e9b`](https://github.com/NASA-AMMOS/AIT-Core/commit/f072e9baae43f658d6eb8d24908bd817ea2094c3) -- Issue #43 - Remove doc upgrade script [`1f56e0c`](https://github.com/NASA-AMMOS/AIT-Core/commit/1f56e0c080f68958257df3910599f3d657042e22) -- Issue #510: Update sequence header to upload to FSW [`a7d184a`](https://github.com/NASA-AMMOS/AIT-Core/commit/a7d184ab1877be9d43fa3f1f6e586b28d944453b) -- Issue #24 - Set bliss_tlm_csv time default to ground receipt time [`771e96e`](https://github.com/NASA-AMMOS/AIT-Core/commit/771e96e58d6cd40aa85596eff159f0901ded65c6) -- Issue #520: update bliss-tlm-csv to handle raw telemetry [`cf0763b`](https://github.com/NASA-AMMOS/AIT-Core/commit/cf0763be4cbdf3009979625af9aaa610ebdb4966) -- Remove file if empty [`6dc13a6`](https://github.com/NASA-AMMOS/AIT-Core/commit/6dc13a6a9a049ec472d8ff98629ca3b5dd918699) -- Update API docs build [`9ef6fce`](https://github.com/NASA-AMMOS/AIT-Core/commit/9ef6fce675b9fb223ed50411c5240b203154e4da) -- Issue #1 - Add decorator for marking functions as deprecated [`63dc981`](https://github.com/NASA-AMMOS/AIT-Core/commit/63dc98168052817807c4e0290e09f427f62d747e) -- Issue #36 - Set TravisCI to ignore branches other than master on push [`b9b2528`](https://github.com/NASA-AMMOS/AIT-Core/commit/b9b25288511a4803884760771b3894ff912dfb0d) -- Issue #36 - Add initial TravisCI YAML config [`ca269a0`](https://github.com/NASA-AMMOS/AIT-Core/commit/ca269a051564b98ac269e18a8a4ed644212e9b93) -- Prep for 0.36.0 release [`6dd5866`](https://github.com/NASA-AMMOS/AIT-Core/commit/6dd586649eb405889a8b4c260b3096398a440fca) -- Prep for 0.35.0 release [`f6079b4`](https://github.com/NASA-AMMOS/AIT-Core/commit/f6079b48ec88e21d5f9469f3e6112361cf297837) -- Prep for 0.34.0 release [`244c5e6`](https://github.com/NASA-AMMOS/AIT-Core/commit/244c5e6fdc6eee1438810722f712d836ef5302b5) -- Prep for 0.33.2 point release [`a96c499`](https://github.com/NASA-AMMOS/AIT-Core/commit/a96c499a320d75b718867835b9ff2098030609a1) -- Issue #510: Update seq.py to more gracefully handle errors [`ae532e4`](https://github.com/NASA-AMMOS/AIT-Core/commit/ae532e43cb0acaffea0fb2541ee696a83dbd0dc8) -- Prep for 0.33.1 release [`ff8fc8f`](https://github.com/NASA-AMMOS/AIT-Core/commit/ff8fc8fa8cb8d418650af90a61ef9bce7b5294e3) -- Prep for 0.33.0 release [`86bc523`](https://github.com/NASA-AMMOS/AIT-Core/commit/86bc52314829e8d2b73e1b96496adc4118e41578) -- Prep for 0.32.0 [`eeb212b`](https://github.com/NASA-AMMOS/AIT-Core/commit/eeb212be251dc2bc162af172cece6485fa6b2aad) -- Prep for 0.31.1 release [`172bccb`](https://github.com/NASA-AMMOS/AIT-Core/commit/172bccbba7b7a43b970b8e6e551a093955fa7e1d) -- Prep for 0.31.0 release [`6113323`](https://github.com/NASA-AMMOS/AIT-Core/commit/61133237216dab610cd01b336e87f44c4fc57603) -- Prep for 0.30.0 release [`a5ef1e9`](https://github.com/NASA-AMMOS/AIT-Core/commit/a5ef1e97be6a25e62cb35783110d5fd69bdc39e5) -- Issue #8 - Fix inconsistent default leap second file name [`b21e52b`](https://github.com/NASA-AMMOS/AIT-Core/commit/b21e52be8d4f78ad12ce2eb7517d7e75981e5a73) -- Issue #5 - Add example script directory config [`daabad3`](https://github.com/NASA-AMMOS/AIT-Core/commit/daabad3e61e51eff6d220c89f07e5b5533507c35) -- Cleanup [`5b40f7d`](https://github.com/NASA-AMMOS/AIT-Core/commit/5b40f7db2fa741e1d242579bfc0e92e006c23047) -- Issue #507 - Update ArrayType class with __repr__ for better type reporting [`c9fd788`](https://github.com/NASA-AMMOS/AIT-Core/commit/c9fd78847042f7c092716ee33ef75aa4d9b0d1f5) -- Issue #489 - Clarify Limit expectations in docs [`7ae5a35`](https://github.com/NASA-AMMOS/AIT-Core/commit/7ae5a350158b1f265b396b3ee05fbe204d1a3a7f) -- Issue #469 - Fix bug in argument parsing in bliss_bsc_stop_handler [`14f8fc6`](https://github.com/NASA-AMMOS/AIT-Core/commit/14f8fc6ac39c870a96e3c8fdaa8097eb3254a382) -- Issue #46 - Add docs build badge to README [`29dda6c`](https://github.com/NASA-AMMOS/AIT-Core/commit/29dda6c520b7e466bc04de31c8743c737bc36810) -- Issue #36 - Add Travis CI build status to README [`29dbbb2`](https://github.com/NASA-AMMOS/AIT-Core/commit/29dbbb2a9fea6eafbf9a747fa18302acf2d4c47f) -- Issue #36 - Add BLISS_CONFIG envvar setting [`8749e5a`](https://github.com/NASA-AMMOS/AIT-Core/commit/8749e5a3a477cbed262cfa7b3e06c98e0406fe72) -- Issue #36 - Add BLISS_CONFIG envvar setting [`02d3b85`](https://github.com/NASA-AMMOS/AIT-Core/commit/02d3b857b228c190f28b765da5099b1fa05ab590) -- Issue #4 - Set default GUI tlm stream to valid packet name [`ffa7e3a`](https://github.com/NASA-AMMOS/AIT-Core/commit/ffa7e3a2475b41eb1e55d011d6ef7e305d94bb8a) -- Issue #518 - Print arguments when sending a command [`0464c40`](https://github.com/NASA-AMMOS/AIT-Core/commit/0464c40dd55ce105cf1b2e9a2eeeebf2d869a418) -- Update bliss_seq_encode to pass seqid to Seq object [`52c26b8`](https://github.com/NASA-AMMOS/AIT-Core/commit/52c26b85d52e9e599f0cd0806f469c80fa21f462) -- Issue #493 - Prefix command validation message with tag for filtering [`b2de44e`](https://github.com/NASA-AMMOS/AIT-Core/commit/b2de44e5e7d4a06480233ca31171ca8699ec1ac2) -- Update CmdAPI to log as COMMAND instead of info [`608f8d3`](https://github.com/NASA-AMMOS/AIT-Core/commit/608f8d327541513d72b3a929aa05d496ef620517) -- Fix spacing bug [`c430085`](https://github.com/NASA-AMMOS/AIT-Core/commit/c430085626fac9d0b87b759eb679c46146169832) -- Issue #482 - Switch gethostbyname() calls to getaddrinfo() [`7de1ab8`](https://github.com/NASA-AMMOS/AIT-Core/commit/7de1ab8cfffa000986fc8172e5119106555775fb) -- Update bin API docs [`b8acbd8`](https://github.com/NASA-AMMOS/AIT-Core/commit/b8acbd8d72fdb6c3729b865dcb519ce4017396df) -- Issue #47 - Add clean up for test table temp file [`2f0f357`](https://github.com/NASA-AMMOS/AIT-Core/commit/2f0f357d157fa6ae420aa693b799da113df22076) -- Issue #39 - Add CODEOWNERS [`c9a2962`](https://github.com/NASA-AMMOS/AIT-Core/commit/c9a296293fd155213bf20f2425dcf1f1114ef217) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..211738d9 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,135 @@ + +# Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, caste, color, religion, or sexual +identity and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the overall + community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or advances of + any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email address, + without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community administrators responsible for enforcement at +[@NikJPL (Aniwat.Nik.Sheurpukdi@jpl.nasa.gov)](https://github.com/NikJPL), +[@snnjpl (Shawn.N.Nguyen@jpl.nasa.gov)](https://github.com/snnjpl) or +[@sharimayer — Configuration Manager](https://github.com/sharimayer). +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of +actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or permanent +ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within the +community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.1, available at +[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. + +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. + +[homepage]: https://www.contributor-covenant.org +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html +[Mozilla CoC]: https://github.com/mozilla/diversity +[FAQ]: https://www.contributor-covenant.org/faq +[translations]: https://www.contributor-covenant.org/translations diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..c7a7574b --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,350 @@ +# Contributing to AIT-Core + +Thanks for taking the time to consider contributing! We very much appreciate your time and effort. This document outlines the many ways you can contribute to our project, and provides detailed guidance on best practices. We look forward to your help! + +## Prerequisites + +Before you begin contributing to our project, it'll be a good idea to ensure you've satisfied the below pre-requisites. + +### Developer Certificate of Origin (DCO) + +To accept your contributions for any kind of patch, you'll want to: +1. Understand what a Developer Certificate of Origin is. See [this](https://wiki.linuxfoundation.org/dco) guide. +2. Read and agree to the [terms](https://developercertificate.org) of the Developer Certificate of Origin. +3. Remember to add your Sign-Off for each patch contribution you submit to our project via either: + 1. By using the `-s` flag if using Git. See [these](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt--s) instructions. + 2. By including the following text in your patch contributions (i.e. pull requests) + ``` + Signed-off-by: Full Name + ``` + +Reviewers reviewing your patch will look for the sign-off before deciding to accept your contribution. + +### License + +Our project has our licensing terms, including rules governing redistribution, documented in our [LICENSE](LICENSE) file. Please take a look at that file and ensure you understand the terms. This will impact how we, or others, use your contributions. + +### Code of Conduct + +Our Code of Conduct helps facilitate a positive interaction environment for everyone involved with the team, and provides guidance on what to do if you experience problematic behavior. Read more in our [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md), and make sure you agree to its terms. + +### Governance Model + +Our Governance model helps outline our project's decision making and roles-based expectations. Read more in our [GOVERNANCE.md](GOVERNANCE.md). + +### Developer Environment + +For patch contributions, see our [Developer Documentation](https://github.com/NASA-AMMOS/AIT-Core/wiki) for more details on how to set up your local environment, to best contribute to our project. + +At a minimum however to submit patches (if using Git), you'll want to ensure you have: +1. An account on the Version Control System our project uses (i.e. GitHub). +2. The Version Control System client (i.e. Git) installed on your local machine. +3. The ability to edit, build, and test our project on your local machine. Again, see our [README.md](README.md) or detailed developer guide for more details + +### Communication Channels + +Before contributing changes to our project, it's a great idea to be familiar with our communication channels and to socialize your potential contributions to get feedback early. This will help give you context for your contributions, no matter their form. + +Our communication channels are: +- [Issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) - a regularly monitored area to report issues with our software or propose changes +- [Discussion board](https://github.com/NASA-AMMOS/AIT-Core/discussions) - a permanently archived place to hold conversations related to our project, and to propose as well as show+tell topics to the contributor team. This resource can be searched for old discussions. + +## Our Development Process + +Our project integrates contributions from many people, and so we'd like to outline a process you can use to visualize how your contributions may be integrated if you provide something. + +```mermaid +flowchart TD + repo_proj[(Our Repository)]-->|Fork|repo_fork[(Your Forked Repository)] + repo_fork-->|Make|patch(Your Changes) + patch-->|Submit|pr(Pull Request) + pr==>|Approved|repo_proj + pr-->|Changes Requested|repo_fork +``` + +### Fork our Repository + +Forking our repository, as opposed to directly committing to a branch is the preferred way to propose changes. + +See [this GitHub guide](https://docs.github.com/en/get-started/quickstart/fork-a-repo) on forking for information specific to GitHub.com + +#### Find or File an Issue + +Make sure people are aware you're working on a patch! Check out our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) and find an open issue you'd like to work against, or alternatively file a new issue and mention you're working on a patch. + +#### Choose the Right Branch to Fork + +Our project typically has the following branches available, make sure to fork either the default branch or a branch someone else already tagged with a particular issue ticket you're working with. +- `develop` — default branch, used for new code development +- `main` — release branch + +### Make your Modifications + +Within your local development environment, this is the stage at which you'll propose your changes, and commit those changes back to version control. See the [README.md](README.md) or development guide for more specifics on what you'll need as prerequisites to setup your local development environment. + +#### Commit Messages + +Commit messages to version control should reference a ticket in their title / summary line: + +``` +Issue #248 - Show an example commit message title +``` + +This makes sure that tickets are updated on GitHub with references to commits that are related to them. + +Commit should always be atomic. Keep solutions isolated whenever possible. Filler commits such as "clean up white space" or "fix typo" should be merged together before making a pull request, and significant sub-feature branches should be [rebased](https://www.youtube.com/results?search_query=git+rebase) to preserve commit history. Please ensure your commit history is clean and meaningful! + +Additionally, remember to "Sign-Off" on your commits to align with our [Developer Certificate of Origin (DCO) policy](#developer-certificate-of-origin-dco). + +### Submit a Pull Request + +Pull requests are the core way our project will receive your patch contributions. Navigate to your branch on your own fork within the version control system, and submit a pull request or submit the patch text to our project. + +Please make sure to provide a meaningful text description to your pull requests, whenever submitted. Our pull-request template will be auto-generated for you when you create your pull-request. See the template [here](.github/PULL_REQUEST_TEMPLATE.md). + +**Working on your first Pull Request?** See guide: [How to Contribute to an Open Source Project on GitHub](https://kcd.im/pull-request) + +### Reviewing your Pull Request + +Reviewing pull-requests, or any kinds of proposed patch changes, is an art. That being said, we follow the following best practices: +- **Intent** - is the purpose of your pull-request clearly stated? +- **Solution** - is your pull-request doing what you want it to? +- **Correctness** - is your pull-request doing what you want it to *correctly*? +- **Small Patches** - is your patch of a level of complexity and brevity that it can actually be reviewed by a human being? Or is does it involve too much content for one pull request? +- **Coding best practices** - are you following best practices in the coding / contribution language being used? +- **Readability** - is your patch readable, and ultimately maintainable, by others? +- **Reproducibility** - is your patch reproducible by others? +- **Tests** - do you have or have conducted meaningful tests? + +## Ways to Contribute + +### ⚠️ Issue Tickets + +> *Do you like to talk about new features, changes, requests?* + +Issue tickets are a very simple way to get involved in our project. It also helps new contributors get an understanding of the project more comprehensively. This is a great place to get started with the project if you're not sure where to start. + +See our list of issues at: https://github.com/NASA-AMMOS/AIT-Core/issues + +#### Cleaning up Duplicate Issues + +Often we receive duplicate issues that can confuse project members on *which* issue ticket to hold conversations upon. + +Here's how you can help: +1. Scan the list of *open* issue tickets for duplicate titles, or internal wording +2. If you find duplicates, copy / paste the below message on the conversation thread of the issue ticket *that has less participants* involved + +``` +This is a duplicate issue. Please migrate conversations over to [issue-XYZ](hyperlink to issue) +``` + +#### Good First Issues + +Issue tickets can vary in complexity, and issues labeled with `good first issue` labels are often a great way to get started with the project as a newcomer. + +Take a look at our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues), and filter by `good first issue` for issues that are low-complexity, and that will help you get familiar with our issue tracking and patch submission process. + +#### Suggesting New Issue Labels + +Labels within our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) are a great way to quickly sort through tickets. The project may not yet have labels to cover the full variety of issue tickets. Take a look through our list of issues, and if you notice a set of issue tickets that seem similar but are not categorized with an existing label, go ahead submit a request within one of the issues you've looked at with the following text: + +``` +I've noticed several other issues that are of the same category as this issue. Shall we make a new label for these types of issues? +``` + +#### Submitting Bug Issues + +Resolving bugs is a priority for our project. We welcome bug reports. However, please make sure to do the following prior to submitting a bug report: +- **Check for duplicates** - there may be a bug report already describing your issue, so check the [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) first. + +Here's some guidance on submitting a bug issue: +1. Navigate to our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) and file a new issue +2. Select a bug template (if available) for your issue + 1. Fill out the template fields to the best of your ability, including output snippets or screenshots where applicable +3. Follow the general guidelines below for extra information about your bug + 1. Include a code snippet if you have it showcasing the bug + 2. Provide reproducible steps of how to recreate the bug + 3. If the bug triggers an exception or error message, include the *full message* or *stacktrace* + 4. Provide information about your operating system and the version of our project you're using + +#### Submitting New Feature Issues + +We welcome new feature requests to help grow our project. However, please make sure to do the following prior to submitting a new feature request: +- **Check for duplicates** - there may be a new feature issue already describing your issue, so check the [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) first +- **Consider alternatives** - is your feature really needed? Or is there a feature within our project or with a third-party that may help you achieve what you want? + +Here's some guidance on submitting a new feature issue: +1. Navigate to our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) and file a new issue +2. Select a new feature template (if available) for your issue + 1. Fill out the template fields to the best of your ability + +#### Submitting Security Vulnerability Issues + +Security vulnerabilities should **not** be filed to the regular issue tracking system. + +Report your security vulnerabilities to (see contact links): [@jl-0](https://github.com/jl-0) or [@jeffreypon](https://github.com/jeffreypon) + +Please be sure to: +* Indicate the severity of the vulnerability +* Provide any workarounds, if you know them +* Provide return-contact information to follow-up with you if needed + +#### Reviewing Pull Requests + +Reviewing others' contributions is a great way to learn about best practices in both contributions as well as software. + +Take a look at our [pull requests tracking system](https://github.com/NASA-AMMOS/AIT-Core/pulls), and try the following options for providing a review: +1. Read the code / patch associated with the pull-request, and take note of any coding, bug, or documentation issues if found +2. Try to recreate the pull-request patch on your local machine, and report if it has issues with your system in particular +3. Scan over suggested feedback from other contributors, and provide feedback if necessary + +### 💻 Code + +⚠️ It's **highly** advised that you take a look at our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) before considering any code contributions. Here's some guidelines: +1. Check if any duplicate issues exist that cover your code contribution idea / task, and add comments to those tickets with your thoughts. +2. If no duplicates exist, create a new issue ticket and get a conversation started before making code changes using our [communication channels](#communication-channels). + +Once you have a solid issue ticket in hand and are ready to work on code, you'll want to: +1. Ensure you have development [prerequisites](#prerequisites) cleared. +2. Have your [development environment](#developer-environment) set up properly. +3. Go through our [development process](#our-development-process), including proposing changes to our project. + +Some guidelines for code-specific contributions: +- **Do your homework** - read-up on necessary documentation, like `README.md`s, developer documentation, and pre-existing code to see the intention and context necessary to make your contribution a success. It's important to _communicate_ what you're working on through our project [communication channels](#communication-channels) and get buy-in from frequent contributors - this will help the project be more receptive to your contributions! +- **Ask questions** - its important to ask questions while you work on your contributions, to check-in with frequent contributors on the style and the set of expectations to make your code contribution work well with pre-existing project code. Use our [communication channels](#communication-channels) +- **Keep positive** - code contributions, by their nature, have direct impacts on the output and functionality of the project. Keep a positive spirit as your code is reviewed, and take it in stride if core contributors take time to review, give you suggestions for your code or respectfully decline your contribution. This is all part of the process for quality open source development. +- **Comments** - include *useful* comments throughout your code that explain the intention of a code block, not a step-by-step analysis. See our [inline code documentation](#inline-code-documentation) section for specifics. + + +### 📖 Documentation + +Documentation is the core way our users and contributors learn about the project. We place a high value on the quality, thoroughness, and readability of our documentation. Writing or editing documentation is an excellent way to contribute to our project without performing active coding. + +⚠️ It's **highly** advised that you take a look at our [issue-tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) before considering any documentation contributions. Here's some guidelines: +1. Check if any duplicate issues exist that cover your documentation contribution idea / task, and add comments to those tickets with your thoughts. +2. If no duplicates exist, create a new issue ticket and get a conversation started before making documentation changes. + +Some guidelines for documentation best practices (summarized from Google's [excellent documentation guide](https://google.github.io/styleguide/docguide/best_practices.html)): +- **Minimum viable docs** - don't do less documentation than your users / developers need, but also don't do more +- **Changed code = changed docs** - if your code has changed, remember to update your documentation +- **Delete old docs** - continually clean your documentation tree, and remove outdated docs regularly + +#### Documentation Organization + +The overall structure of our project documentation is as follows: +- Source-controlled documentation + - [README.md](README.md) - top-level information about how to run, build, and contribute to the project + - [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) - best practices and guidance on how to work well with other people in the project, and suggestions on dealing with interpersonal issues + - [CONTRIBUTING.md](CONTRIBUTING.md) - guidance on contributing to the project + - `*.java` - inline documentation available inside code files +- Hosted documentation + - [Wiki Main-page](https://github.com/NASA-AMMOS/AIT-Core/wiki) +- Discussion Boards + - [Discussions](https://github.com/NASA-AMMOS/AIT-Core/discussions) + + + +For directions on contributing to our source-controlled documentation: +1. Ensure you have development [prerequisites](#prerequisites) cleared. +2. Have your [development environment](#developer-environment) set up properly. +3. Go through our [development process](#our-development-process), including proposing changes to our project. + + + +#### Writing Style + +To ensure documentation is readable and consistent by newcomers and experts alike, here are some suggestions on writing style for English: +- Use gender neutral pronouns (they/their/them) instead of he/she/his/her +- Avoid qualifiers that minimize the difficulty of a task at hand, e.g. avoid words like “easily”, “simply”, “just”, “merely”, “straightforward”, etc. Readers' expertise may not match your own, and qualifying complexity may deter some readers if the task does not match their level of experience. That being said, if a particular task is difficult or complex, do mention that. + +#### Common Wording + +Below are some commonly used words you'll want to leverage in your documentation contributions: +- **AMMOS** - Advanced Multi-Mission Operations System tool set. +- **Artifactory** - Lab-based artifact repository that stores compiled builds for reuse. +- **GitHub** - One word with capitalization of the 'G' and 'H'. +- **Jenkins** - Continuous Integration (CI) server that hosts many Lab builds. +- **MIPL** - Multimission Instrument Processing Lab which hosts the project containing this repository. +- **VICAR Java Build** - The build system that collects and compiles related code. + +#### Inline Code Documentation + +For language-specific guidance on code documentation, including style guides, see [Google's list of language style guides](https://google.github.io/styleguide/) for a variety of languages. + +Additionally, take a look at Google's recommendations on [inline code documentation](https://google.github.io/styleguide/docguide/best_practices.html#documentation-is-the-story-of-your-code) for best practices. + +#### Media + +Media, such as images, videos, sound files, etc., are an excellent way to explain documentation to a wider audience more easily. Include media in your contributions as often as possible. + +When including media into our version-control system, it is recommended to use formats such as: +- Diagrams: [Mermaid](https://mermaid-js.github.io/mermaid/#/) format +- Images: JPEG format +- Videos: H264 MPEG format +- Sounds: MP3 format + + +### ❓ Questions + +Answering questions is an excellent way to learn more about our project, as well as get better known in our project community. + +Here are just a few ways you can help answer questions for our project: +- Answer open questions in our [discussion forum](https://github.com/NASA-AMMOS/AIT-Core/discussions) +- Answer open questions mentioned in our [issue tracking system](https://github.com/NASA-AMMOS/AIT-Core/issues) + + +When answering questions, keep the following in mind: +- Be polite and friendly. See our [Code of Conduct](CODE_OF_CONDUCT.md) recommendations as you interact with others in the team. +- Repeat the specific question you are answering, followed by your suggestion. +- If suggesting code, repeat the line of code that needs to be altered, followed by your alteration +- Include any post-steps or checks to verify your answer can be reproduced + +### 🎨 Design + +Design files can help to guide new features and new areas of expansion for our project. We welcome these kinds of contributions. + +Here are just a few ways you can help provide design recommendations for our project: +- Create visual mockups or diagrams to increase usability of our project applications. This can apply to user interfaces, documentation structuring, or even code architecture diagrams. +- Conduct user research to understand user needs better. Save your findings within spreadsheets that the project team / contributors can review. +- Create art, such as logos or icons, to support the user experience for the project + +Each of the above can be contributed directly to repository code, and you should use our [development process](#our-development-process) to contribute your additions. + +### 🎟️ Meetups + +A great way to contribute towards our project goals is to socialize and encourage people to meet and learn more about each other. Consider ideas like: +- Propose workshops or meetups regarding some topic within our project +- Help point project contributors and community members to conferences and publications where they may socialize their unique innovations +- Schedule in-person or virtual happy-hours to help create a more social atmosphere within the project community + +For the above ideas, use our [communication channels](#communication-channels) to propose get-togethers. diff --git a/LICENSE b/LICENSE new file mode 100644 index 00000000..17c357d7 --- /dev/null +++ b/LICENSE @@ -0,0 +1,216 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + Copyright (c) 2022 California Institute of Technology ("Caltech"). + U.S. Government sponsorship acknowledged. + + All rights reserved. + + Redistribution and use in source and binary forms, with or without modification, are permitted provided + that the following conditions are met: + * Redistributions of source code must retain the above copyright notice, this list of conditions and + the following disclaimer. + * Redistributions in binary form must reproduce the above copyright notice, this list of conditions + and the following disclaimer in the documentation and/or other materials provided with the + distribution. + * Neither the name of Caltech nor its operating division, the Jet Propulsion Laboratory, nor the + names of its contributors may be used to endorse or promote products derived from this software + without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS + IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, + THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR + CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, + EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, + PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; + OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, + WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR + OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF + ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. From 7b78e9ebfcad8866cdd6e06d86e0cbab99934ff4 Mon Sep 17 00:00:00 2001 From: jpl-jengelke Date: Thu, 18 Jan 2024 16:27:07 -0800 Subject: [PATCH 2/2] Slim Infusion: Update baseline SLIM templates with core information. ... --- CONTRIBUTING.md | 39 ++------- LICENSE | 217 +----------------------------------------------- LICENSE.txt | 7 -- 3 files changed, 13 insertions(+), 250 deletions(-) delete mode 100644 LICENSE.txt diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c7a7574b..6e735adf 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,20 +6,6 @@ Thanks for taking the time to consider contributing! We very much appreciate you Before you begin contributing to our project, it'll be a good idea to ensure you've satisfied the below pre-requisites. -### Developer Certificate of Origin (DCO) - -To accept your contributions for any kind of patch, you'll want to: -1. Understand what a Developer Certificate of Origin is. See [this](https://wiki.linuxfoundation.org/dco) guide. -2. Read and agree to the [terms](https://developercertificate.org) of the Developer Certificate of Origin. -3. Remember to add your Sign-Off for each patch contribution you submit to our project via either: - 1. By using the `-s` flag if using Git. See [these](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt--s) instructions. - 2. By including the following text in your patch contributions (i.e. pull requests) - ``` - Signed-off-by: Full Name - ``` - -Reviewers reviewing your patch will look for the sign-off before deciding to accept your contribution. - ### License Our project has our licensing terms, including rules governing redistribution, documented in our [LICENSE](LICENSE) file. Please take a look at that file and ensure you understand the terms. This will impact how we, or others, use your contributions. @@ -28,10 +14,6 @@ Our project has our licensing terms, including rules governing redistribution, d Our Code of Conduct helps facilitate a positive interaction environment for everyone involved with the team, and provides guidance on what to do if you experience problematic behavior. Read more in our [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md), and make sure you agree to its terms. -### Governance Model - -Our Governance model helps outline our project's decision making and roles-based expectations. Read more in our [GOVERNANCE.md](GOVERNANCE.md). - ### Developer Environment For patch contributions, see our [Developer Documentation](https://github.com/NASA-AMMOS/AIT-Core/wiki) for more details on how to set up your local environment, to best contribute to our project. @@ -75,8 +57,8 @@ Make sure people are aware you're working on a patch! Check out our [issue track #### Choose the Right Branch to Fork Our project typically has the following branches available, make sure to fork either the default branch or a branch someone else already tagged with a particular issue ticket you're working with. -- `develop` — default branch, used for new code development - `main` — release branch +- `develop` — optional default branch, used primarily for new code development ### Make your Modifications @@ -94,8 +76,6 @@ This makes sure that tickets are updated on GitHub with references to commits th Commit should always be atomic. Keep solutions isolated whenever possible. Filler commits such as "clean up white space" or "fix typo" should be merged together before making a pull request, and significant sub-feature branches should be [rebased](https://www.youtube.com/results?search_query=git+rebase) to preserve commit history. Please ensure your commit history is clean and meaningful! -Additionally, remember to "Sign-Off" on your commits to align with our [Developer Certificate of Origin (DCO) policy](#developer-certificate-of-origin-dco). - ### Submit a Pull Request Pull requests are the core way our project will receive your patch contributions. Navigate to your branch on your own fork within the version control system, and submit a pull request or submit the patch text to our project. @@ -182,7 +162,7 @@ Here's some guidance on submitting a new feature issue: Security vulnerabilities should **not** be filed to the regular issue tracking system. -Report your security vulnerabilities to (see contact links): [@jl-0](https://github.com/jl-0) or [@jeffreypon](https://github.com/jeffreypon) +Report your security vulnerabilities to (see contact links): [@jl-0](https://github.com/jl-0) or [@sharimayer](https://github.com/sharimayer) Please be sure to: * Indicate the severity of the vulnerability @@ -238,7 +218,7 @@ The overall structure of our project documentation is as follows: - [README.md](README.md) - top-level information about how to run, build, and contribute to the project - [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) - best practices and guidance on how to work well with other people in the project, and suggestions on dealing with interpersonal issues - [CONTRIBUTING.md](CONTRIBUTING.md) - guidance on contributing to the project - - `*.java` - inline documentation available inside code files + - `*.java`, `*.py`, `*.sh`, etc. - inline documentation available inside code files - Hosted documentation - [Wiki Main-page](https://github.com/NASA-AMMOS/AIT-Core/wiki) - Discussion Boards @@ -290,12 +270,10 @@ To ensure documentation is readable and consistent by newcomers and experts alik #### Common Wording Below are some commonly used words you'll want to leverage in your documentation contributions: -- **AMMOS** - Advanced Multi-Mission Operations System tool set. -- **Artifactory** - Lab-based artifact repository that stores compiled builds for reuse. -- **GitHub** - One word with capitalization of the 'G' and 'H'. -- **Jenkins** - Continuous Integration (CI) server that hosts many Lab builds. -- **MIPL** - Multimission Instrument Processing Lab which hosts the project containing this repository. -- **VICAR Java Build** - The build system that collects and compiles related code. +- **AMMOS** - Advanced Multi-Mission Operations System tool set. AMMOS is also the eponymous organization that sponsors this repository. +- **Docker** - Containerization service used to perform automated build, release and deployment. +- **GitHub** - one word, and capitalization of the 'G' and the 'H' +- **GitHub Actions** - Continuous Integration (CI) services that facilitate build automation #### Inline Code Documentation @@ -347,4 +325,5 @@ A great way to contribute towards our project goals is to socialize and encourag - Help point project contributors and community members to conferences and publications where they may socialize their unique innovations - Schedule in-person or virtual happy-hours to help create a more social atmosphere within the project community -For the above ideas, use our [communication channels](#communication-channels) to propose get-togethers. +For the above ideas, use our [communication channels](#communication-channels) to propose get-togethers. + diff --git a/LICENSE b/LICENSE index 17c357d7..2ce669d2 100644 --- a/LICENSE +++ b/LICENSE @@ -1,216 +1,7 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ +Copyright 2013 California Institute of Technology - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION +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: - 1. Definitions. +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - Copyright (c) 2022 California Institute of Technology ("Caltech"). - U.S. Government sponsorship acknowledged. - - All rights reserved. - - Redistribution and use in source and binary forms, with or without modification, are permitted provided - that the following conditions are met: - * Redistributions of source code must retain the above copyright notice, this list of conditions and - the following disclaimer. - * Redistributions in binary form must reproduce the above copyright notice, this list of conditions - and the following disclaimer in the documentation and/or other materials provided with the - distribution. - * Neither the name of Caltech nor its operating division, the Jet Propulsion Laboratory, nor the - names of its contributors may be used to endorse or promote products derived from this software - without specific prior written permission. - - THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS - IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, - THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR - PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR - CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, - EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, - PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; - OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, - WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR - OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF - ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. diff --git a/LICENSE.txt b/LICENSE.txt deleted file mode 100644 index 2ce669d2..00000000 --- a/LICENSE.txt +++ /dev/null @@ -1,7 +0,0 @@ -Copyright 2013 California Institute of Technology - -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.