GC-STEM repositories support teaching, learning, and collaboration. Students, faculty, staff, contributors, and visitors are expected to help maintain a respectful and inclusive community.
People bring different experiences, languages, abilities, and levels of technical knowledge. Questions and mistakes are a normal part of learning.
- Respectful Participation
- Academic Integrity
- Privacy and Security
- Where This Applies
- Report a Concern Privately
- Moderation and Review
- Status
- Treat others with courtesy and respect.
- Focus feedback on ideas, code, and processes.
- Explain suggestions clearly and give others room to ask questions.
- Ask for clarification when a message's meaning or tone is unclear.
- Respect personal boundaries and requests to end an interaction.
- Credit other people's work and contributions.
- Allow time for replies. Participants work at different times and balance learning with other responsibilities.
Disagreement is welcome when expressed respectfully. Harassment, discrimination, threats, personal attacks, unwanted sexual conduct, spam, impersonation, and retaliation are unacceptable.
Follow the course's rules for collaboration, reused material, and AI assistance. Cite sources and disclose assistance when required.
Do not misrepresent authorship or share restricted assessment materials. Share assignment solutions only when course instructions permit it.
If you are unsure what assistance or sharing is allowed, ask your instructor privately. Do not investigate or debate suspected academic-integrity violations in public GitHub conversations.
Protect other people's personal, academic, and account information.
Before posting files, screenshots, or logs, remove student records, grades, private feedback, personal contact details, private communications, passwords, and other credentials.
Do not conduct security testing without authorization or use code to harm others. Authorized instructional security activities must remain within the assignment's permitted scope.
If you encounter exposed information, follow private security reporting.
This code applies to repository-related issues, discussions, pull requests, reviews, commits, wikis, and associated collaboration spaces. It also applies when someone officially represents the repository community.
SNHU policies, course requirements, and GitHub's terms also apply.
Do not post sensitive conduct reports in a public issue or discussion.
- Students: Contact your instructor using the private method listed in Brightspace.
- If the concern involves your instructor, or you are uncomfortable reporting to them: Contact your academic advisor or the SNHU reporting office identified in your student policies.
- Other participants: Use the institutional or repository contact identified in the affected repository's README.
- GitHub policy violations: Use GitHub Support.
Describe what happened, where and when it occurred, and any relevant links. Share sensitive evidence only through an appropriate private channel.
Reports should be handled with care for privacy, consistent with institutional procedures and any required investigation or referral.
Maintainers are the people responsible for managing a repository. They may clarify expectations, request corrections, remove content, limit conversations, restrict participation, or refer concerns to the appropriate institutional process.
Responses should consider the circumstances, severity, impact, and any repeated behavior. Serious concerns may require immediate action.
If a restriction affects access to required coursework, maintainers should coordinate with the responsible course owner to identify an approved way to continue the course.
Academic or institutional disciplinary decisions follow the applicable institutional process. Repository moderation does not replace that process.
This code is provisional while institutional review is pending. It does not replace SNHU policies, course requirements, or GitHub's terms.