SLIM integration: Infusion of Lab-approved documentation and templating standards
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the commit history in the slim_infusion branch and compare its added files with the current repository. Identify which templates and documentation files are intended for Landform and what integration assistance they require. Done means the applicable Lab-approved documentation and templating standards are incorporated with the repository-specific adjustments described by the branch.
Written by the indexing model from the issue text.
Description
Checked for duplicates
Yes -- New feature, new files.
Alternatives considered
Yes - This is a Lab-approved and suggested addition to all NASA-AMMOS repositories.
Related problems
Many repos don't provide comprehensive documentation and/or are missing key areas of standardized documentation focus. This feature adds standardized documentation per Lab-approved standards.
Describe the feature request
A number of template and documentation files are being added to the repository in support of the SLIM project. These files are suggested by MGSS and will serve to promote cohesion between NASA-AMMOS products. The files provided are tailored to the current repository with minimal integration assistance and upkeep requested of the CogE and/or developers.
See commit history in the slim_infusion branch for added files.
- Dominant language
- C#
- Stars
- 40
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
dette technique priorité: basse zone: service
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
damiensabau/nexus-lobby#25 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sebastienros/jint#4282 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pyrevitlabs/pyRevit#3792 ·
Maintainers usually reply within 1 day