Faculty Student Git Service (sgit) Terms of Service

Rules and policies for using the university faculty version control platform integrated with USOS for students and teaching staff.

§ 1. Purpose of the Service

  1. The Faculty Student Git service (sgit) is an IT service provided to students and academic staff exclusively for educational coursework, laboratory exercises, academic projects, and thesis development.
  2. The service is integrated with the University Student Management System (USOS) and Central Authentication Service (CAS). Access to course organizations and laboratory groups is synchronized automatically based on USOS course allocations.
  3. Use of the platform for private, commercial, or non-educational purposes unrelated to the faculty's academic curriculum is strictly prohibited.

§ 2. Data Safety & Personal Backups (No Guarantee)

  1. The service is provided on an "as is" and "as available" basis. While the administrators strive to ensure high reliability, no guarantee is provided against data loss, repository corruption, or server failures.
  2. Both students and instructors have an absolute obligation to maintain their own independent, up-to-date local copies (backups) of all their source code, projects, and educational materials.
  3. Because Git is fundamentally a distributed version control system, every local clone on your computer contains a full copy of the repository history. You must ensure your work is kept safe on your own machine.
  4. The Faculty, University, and system administrators bear no liability whatsoever for any lost work, corrupted commits, inability to access the service, or academic consequences (e.g. lost grades, inability to evaluate an assignment, or missed submission deadlines) arising from a user's failure to maintain personal backups.

§ 3. Availability & Maintenance Breaks

  1. Scheduled maintenance breaks, infrastructure upgrades, and system updates are ordinarily scheduled outside primary university teaching hours (i.e. outside 8:00 AM – 8:00 PM).
  2. In critical or emergency situations (such as urgent security vulnerability patching, hardware malfunctions, network outages, or database corruption), maintenance breaks may occur at any time, including during daytime teaching hours (8:00 AM – 8:00 PM), without prior notice.
  3. Users must plan their work and push their code well ahead of deadlines. An approaching submission deadline does not preclude emergency maintenance necessary to preserve system integrity.

§ 4. Coordinator & Teacher Roles

  1. Course Coordinators and course instructors are responsible for enforcing clean repositories of their students and monitoring what their students store in their repositories.
  2. The Course Coordinator defines task templates, repository configurations, deadlines, and environmental restrictions (such as IP lab restrictions or automated Docker verification checks).
  3. Instructors have the right and duty to inspect student repositories, verify proper usage of .gitignore, and require students to remove unnecessary build artifacts, dependencies, or large files.

§ 5. Usage & Repository Size Limits

  1. The default repository size limit is 4.0 MiB.
  2. Repositories are strictly intended for storing lab/project source code only — NOT for data storage.
  3. The following items must never be tracked or stored in repositories:
    • Data sets (large CSV, JSON, XML, SQLite, or raw database dumps),
    • Media assets (video recordings, audio files, uncompressed high-resolution images),
    • Compiled binaries, executables, and build outputs (e.g. *.exe, *.dll, *.so, *.class, bin/, obj/, build/, target/),
    • Dependency directories and package caches (e.g. node_modules/, venv/, .env/, vendor/),
    • Compressed archives (e.g. *.zip, *.tar.gz, *.rar, *.7z).
  4. All transient build outputs and local environments must be excluded using a properly configured .gitignore file. Refer to the Git Guide for best practices.
  5. Increases to the repository size limit may be granted only in reasonable, well-justified cases upon formal request approved by the Course Coordinator and system administration.
  6. Repositories which do not follow the rules will be deleted without further notice.

§ 6. Acceptable Use Policy & Security

  1. Each user is strictly responsible for all actions performed using their university account, SSH keys, and access tokens.
  2. Sharing credentials, circumventing network restrictions (such as lab-only or campus WiFi enforcement), bypassing push rate limits, or tampering with container test runners constitutes a violation of university disciplinary regulations.
  3. Users must never commit sensitive information into repositories, including:
    • Passwords, private SSH keys, TLS certificates, and API tokens,
    • Personal data protected under GDPR / privacy laws,
    • Malicious code, spyware, or security penetration tools without express course authorization.
  4. Repositories violating security policies or these Terms of Service will be deleted immediately without further notice.
  1. All coursework source code must be created independently, respecting academic integrity and intellectual property laws.
  2. Plagiarism, unauthorized copying of another student's work, or publishing assignment solutions publicly without instructor consent is strictly prohibited.

§ 8. Final Provisions

  1. Logging into and using the service signifies full acknowledgment and acceptance of these Terms of Service.
  2. Matters not covered by these Terms are governed by the Warsaw University of Technology Academic Regulations, Faculty IT Administration Rules, and applicable national laws.
  3. The person responsible for this service is Maciej Spychała. Inquiries regarding course repositories or platform policies should be directed to the responsible person or respective course coordinators.