Readme installation

[jrcain-usgs]

Reorganized the info in ISIS readme, moving some important info to ASC Docs, editing for conciseness, and removing unnecessary and overly verbose sections.

View proposed new README

Description

Extracted the Following Sections, moving each to its own ASC Doc page:

• Installing ISIS
• Setting Up the ISIS Data Area
• ISIS Test Data

Condensed sections remaining on README for now:

• RFC
• System Requirements
• Semantic Versioning

Updated section:

• Citing ISIS (with current 8.3.0 version DOI)

Related Issue

Fixes #5500
Fixes #5650

How Has This Been Validated?

Readme previewed via VS Code markdown preview rendering.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change (update to the documentation; no code change)
• Breaking change (fix or feature that would cause existing functionality to change)
• Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

• I have read and agree to abide by the Code of Conduct
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• I have added tests to cover my changes.
• I have added myself to the .zenodo.json document.
• I have added my user impacting change to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5679".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5679".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[Kelvinrr]

We can just change the logo like that, it would need to get reviewed by others first. I would argue to return it back to what it was and if we want to change it we can do something to update logos as a whole since some libraries might need ones.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5679".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[jrcain-usgs]

Changed logo back.

The reason to consider a different one is readability.

In the old logo, the ISIS text and the image behind are right on top of each other, and have a lot of intersecting lines between them, which limits readability.

I changed it to brown for the ISIS docs to get better contrast, which helps but doesn't solve the root readability issue.

[Kelvinrr]

@jrcain-usgs even if there are good reasons we need to have a conversation about these changes before they are worked, let alone merged. I would recommend also removing the logo from the PR.

[Kelvinrr]

just some comments

[Kelvinrr]

We need something that is a more general "this is how you run ISIS tests" not just how to install isis test data. Those linked docs cover it but maybe name this link "'How to run ISIS tests"

[jrcain-usgs]

"How to run ISIS Tests" is currently under the "Building ISIS" Doc. Here's a small PR to link to "ISIS Test Data" from "Building ISIS." And with that, I can safely remove the ISIS Test Data link from the README.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5679".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5679".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.