Clarify context of SCIF app implementation - #4
Merged
Conversation
vsoch
reviewed
May 14, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the Pull Request (PR):
Claritfy the context of the SCIF app implementation.
Initial minimal context setting here... Having read through where/how we mention apps, and given that the SCIF implementation is and continues to be a maintained and tested part of the core code, I think we should go further toward having a separate top-level section that is more complete. We should then reference it from the usage / build / services pages.
Would love to get your thoughts @vsoch on whether this is a decent start, so we are at least guaranteed to be somewhat improved for the 3.8.0 release.
This fixes or addresses the following GitHub issues: