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
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the commit history and added files in the slim_infusion branch, then compare those templates and documentation files with this repository. Confirm which files are tailored for this repository and what integration assistance is needed. Done means the Lab-approved documentation and templating standards are integrated with minimal upkeep for the CogE and developers.
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
- TypeScript
- Stars
- 1
- Forks
- 2
- 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.
More from NASA-AMMOS/plandev-ts-user-code-runner
-
Support importsOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
NASA-AMMOS/plandev-ts-user-code-runner#28 · 1 comment ·
All issues in NASA-AMMOS/plandev-ts-user-code-runner
Similar issues
-
comp/desktop desktop/shell os/windows P3 tool/file type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NousResearch/hermes-agent#145928 ·
Maintainers usually reply within 1 day
-
compiler-dom: stringifyStatic renders :disabled="0" as a present attributePossibly taken @DaZuiZui claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vuejs/core#16051 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
integration:coding-agents
Difficulty 1/5 Under an hour Newbie friendliness 83/100
vectorize-io/hindsight#6151 ·
Maintainers usually reply within 1 day
-
DogFooding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
OpenAEV-Platform/openaev#8768 ·
Maintainers usually reply within 1 day