Skip to content

Draft Guide to Maintaining SciDoc#2899

Open
gmg228 wants to merge 4 commits intodevfrom
update_scidoc_guide
Open

Draft Guide to Maintaining SciDoc#2899
gmg228 wants to merge 4 commits intodevfrom
update_scidoc_guide

Conversation

@gmg228
Copy link
Copy Markdown
Contributor

@gmg228 gmg228 commented Mar 27, 2026

Context

Issue(s) closed by this pull request: closes #2807

Updates and additions to the RuFaS model require concurrent updates to documentation and methodology. Updating and maintaining scientific documentation is largely conducted by RuFaS SME team, with support from SWE. These guidelines were created to inform maintainers how to ensure documentation stays current and connect them with resources (templates etc.) to streamline this process.

Draft Guide

What

This PR is to create the guide in the current Wiki.

Why

Proper and up to date documentation is integral to maintaining transparency with the open-source RuFaS model.

How

Creating this file for reference will ensure updates are straightforward and consistent.

Test plan

NA

Input Changes

NA

Output Changes

  • N/A

Filter

@gmg228 gmg228 self-assigned this Mar 27, 2026
@gmg228 gmg228 requested a review from KFosterReed March 27, 2026 12:06
@github-actions
Copy link
Copy Markdown
Contributor

Current Coverage: 99%

Mypy errors on update_scidoc_guide branch: 1190
Mypy errors on dev branch: 1190
No difference in error counts

@github-actions
Copy link
Copy Markdown
Contributor

🚨 Please update the changelog. This PR cannot be merged until changelog.md is updated.

@github-actions
Copy link
Copy Markdown
Contributor

Current Coverage: 99%

Mypy errors on update_scidoc_guide branch: 1195
Mypy errors on dev branch: 1195
No difference in error counts

@github-actions
Copy link
Copy Markdown
Contributor

🚨 Please update the changelog. This PR cannot be merged until changelog.md is updated.

Copy link
Copy Markdown
Collaborator

@morrowcj morrowcj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a few comments and minor language suggestions in the google doc.

Regarding your slack message:

  1. I think the guidelines make sense
  2. I think there is an appropriate level of detail
  3. I don't have suggestions about workflow
  4. No questions or concerns.

@gmg228
Copy link
Copy Markdown
Contributor Author

gmg228 commented Apr 1, 2026

Thank you so much for reviewing!

I looked through your suggested edits and comments and they all make sense to me! I'll incorporate what I can today and find answers to the comments that I cannot resolve alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Outline internal/maintainers process for keeping scientific documentation up to date (for team review & feedback)

2 participants