-
Notifications
You must be signed in to change notification settings - Fork 0
Status Issues and Discussions
The main IT 140 repository is the central place to check course-wide technical status and to find shared GitHub support channels.
The main repository README contains the current status of:
- Course automation by platform
- Course activity repositories
- Known availability information
Check it before assuming that a missing repository or unavailable feature is a problem:
https://github.com/GC-STEM/it140
The wiki does not repeat the full status tables because status can change during course development and maintenance.
The main README may show two kinds of status.
Development status describes where an artifact is in its development lifecycle, such as:
- Planned
- Requirements
- Design
- Construction
- Alpha Testing
- Beta Testing
- Ready for Pilot
- Maintenance
- Archived
A development status tells you how mature an artifact is. It does not always mean the artifact is currently available to students.
Operational status describes current availability, such as:
- 🟢 Live — currently available
- 🟡 Known Issue — available or partially available with a known problem
- 🔴 Unavailable — not currently available
Use the current README rather than memorizing a status you saw earlier in the term.
An Issue is used to report a specific problem, defect, or requested improvement that can be tracked.
- Course-wide automation problems
- Problems with the main course repository
- Incorrect course-wide status information
- Problems affecting shared course automation or technical resources
Main course Issues:
https://github.com/GC-STEM/it140/issues
- Module One setup instruction problems
- Platform-specific first-time setup problems
- Errors in the Windows, macOS, Linux, or CVD setup workflow
- Setup documentation improvements
Setup Tasks Issues:
https://github.com/GC-STEM/it140-m1-setup-tasks/issues
For detailed setup troubleshooting guidance, see the Setup Tasks wiki:
https://github.com/GC-STEM/it140-m1-setup-tasks/wiki/Setup-Problems-and-Support
A Discussion is better for a question or conversation that may be useful to other students and faculty.
Main course Discussions:
https://github.com/GC-STEM/it140/discussions
Examples include:
- Asking whether others have seen the same behavior
- Clarifying how a shared course tool works
- Discussing a workaround
- Sharing a solution to a technical problem
- Asking a question that may benefit students in more than one course section
Your Brightspace section may also have a General Questions discussion. Follow your instructor's guidance about which discussion space to use.
A useful rule is:
| Situation | Better Place |
|---|---|
| Something is broken and needs to be tracked | Issue |
| Documentation contains an error or omission | Issue |
| You have a specific improvement request | Issue |
| You have a question | Discussion |
| You want to compare experiences or possible solutions | Discussion |
| You solved a problem that may help others | Discussion |
| The problem is with SNHU account access or another university system | SNHU support channel |
When you are unsure, a Discussion is often a good place to start. Faculty can identify whether the problem should also become a tracked Issue.
Check for an existing answer first:
- Read the current repository README.
- Search GitHub Issues.
- Search GitHub Discussions.
- Search your course section's General Questions discussion.
- Compare the problem with the final summary and log from any course script you ran.
If you create a new report, include enough information for someone else to reproduce or understand the problem.
Useful information includes:
- Your environment or operating system
- The course activity
- The script or tool involved
- What you were trying to do
- What you expected
- What happened instead
- The exact error message
- What you already tried
- The relevant log or screenshot, when appropriate
Before posting publicly, review your text, screenshots, and logs.
Do not post:
- Passwords
- Authentication codes
- Access tokens
- Recovery codes
- Student identification numbers
- Private contact information
- Other credentials or secrets
- Complete solutions to graded assignments
If a log or screenshot contains private information, remove or hide that information before sharing it.
Problems involving systems such as university account access, Brightspace, or access to a university-provided service may require the SNHU IT Service Desk rather than a GitHub Issue.
Use the support instructions in your IT 140 course or the Setup Tasks support page to choose the appropriate channel.
If you asked a public question and found the solution, consider posting what worked.
A short follow-up helps:
- Classmates with the same problem
- Instructors recognize repeat problems
- Course maintainers improve documentation or automation
- Future students find a confirmed solution