OSS Hub

---

Screenshots

[!NOTE] The service and these screenshots are in Korean. The people, GitHub IDs, and programs shown are made-up examples. The screens may differ slightly from the live service.

Features

• 🧭 Browse without an account. The program list, program details, ranking, and public projects need no sign-in.
• 👥 Apply as a team. The team leader invites members and submits the application, which also registers the team.
• ✅ Decide from one list. Staff approve or reject each team from the team list, and a rejection needs a reason.
• 🐙 Repositories on approval. If a program issues repositories, each approved team gets a private repository and its members get invitations.
• 📄 Documents tracked one by one. Each required document has its own deadline and review status, and after a revision request the team can resubmit by a set date.
• 📦 Bulk download. Staff download submitted files as a ZIP with a 제출현황.csv manifest.
• 📊 Hourly activity and a public ranking. The service collects GitHub activity every hour and shows a weekly chart per team member and a public ranking.
• 📣 Boards and notifications. Each program has a board for notices and questions. Decisions arrive as in-app notifications and deadline reminders as email.

How a program runs

flowchart LR
  Explore[Browse] --> Apply[Form a team and apply]
  Apply --> Decision{Application decision}
  Decision -->|Approved| Work[Work and submit documents]
  Decision -->|Rejected| Rejected[Rejected]
  Rejected -->|Leader revises within the application period| Apply
  Work --> Review{Document review}
  Review -->|Revision requested| Work
  Review -->|Approved or rejected| Done[Review finished]

1. Browse. Application dates, the schedule, and required documents are visible without signing in.
2. Form a team and apply. Sign in with GitHub, name the team, and invite members by name or GitHub ID. Only the team leader can submit the application.
3. Application decision. Staff approve or reject each team, and the result arrives as an in-app notification. If the program issues repositories, each approved team gets a private repository and its members get invitations. A rejected application can be revised and resubmitted by the team leader while the application period is open.
4. Work and submit documents. Teams work in their repository. Only approved applications can submit documents.
5. Document review. Staff approve, reject, or request a revision for each document. Approval and rejection are final. After a revision request, the team resubmits by the date staff set. Once a team resubmits after the deadline, it cannot change the document until the review is done.

Approving an application does not approve its documents. A plan and a final report are separate items, so each keeps its own deadline and status even when the dates match.

• Repository invitations. Each member accepts their own GitHub invitation.
• Linking your own repository. The team leader or staff can register it. A repository outside the organization must be public.
• Making a repository public. If the team said on the application that it plans to make it public, staff can make it public after the program ends and required documents are approved.
• Files. The service accepts PDF, HWP, and ZIP files up to 5 MB.
• Grace deadlines. When staff set a grace deadline, the service accepts submissions until then and marks them late.
• Deadline email. If the program turns this on, members of approved teams that have not submitted a required document due within 24 hours get an email at 9:00 a.m. each day. Each member must also turn on email and set a mail address in their settings.
• Ranking and collection scope. The GitHub activity policy (in Korean) explains what is collected and shown.

Roles

Role	Starts	Can do	Guide (English)
Student (학생) · STUDENT	On sign-up	Apply to programs, join teams, submit and resubmit documents, see their own repositories and activity	Student guide
Staff (교직원) · STAFF, meaning faculty and administrative staff	After approval	Create programs, including filling one in from a notice URL, decide on applications, review documents and request revisions, see student activity statistics	Staff guide
Administrator (관리자) · ADMIN	When granted	Everything staff can do, plus users and permissions, audit logs, system status, and manual collection	Administrator guide

Member type and administrator permission are separate, so one account can be both staff and an administrator. Neither staff nor administrators can decide on their own team's application or review its documents.

Getting help

• The FAQ answers common questions.
• Ask the staff member in charge or an administrator about a specific program.
• Report bugs and suggest changes in GitHub Issues.
• Report security problems through the security policy, not a public issue.

Adapting OSS Hub for your organization

OSS Hub is open source under the MIT license. The public instance serves Chonnam National University; running a separate instance requires your own infrastructure and integration credentials.

This is the beginning of the README. Read the rest at the original. Read the full README ↗