Skip to content

Frequently asked questions

The product interface and screenshots remain in Korean. Korean labels below are the text to look for on screen; the English wording explains them.

You need a GitHub account. There is no separate OSS Hub username or password. Your first sign-in takes you through consent, role selection, and basic profile information. See Getting started.

The program list, program details, and rankings are public. You must sign in to apply or submit documents. See What you can view before signing in.

Choose 학생 (Student) to apply to programs and submit documents. Choose 교직원 (Staff) to create and run programs. Students can start immediately; staff need administrator approval. If you chose incorrectly, select 역할을 다시 고르기 (Choose your role again) in registration step 3. See Getting started.

I registered as staff. Why can I not open the staff screens?

Section titled “I registered as staff. Why can I not open the staff screens?”

Your request is awaiting approval. Until an administrator approves it, you only see 교직원 승인을 기다리고 있습니다 (Waiting for staff approval). No separate approval notification is sent, so select 상태 새로고침 (Refresh status) to check. If it is taking too long, ask an administrator to review your request. Administrators can follow Process staff access requests.

I entered the wrong student number. Can I change it?

Section titled “I entered the wrong student number. Can I change it?”

You can only enter your student number once, so you cannot change it yourself. This also applies if you see an error saying another account already uses the number. Contact an administrator if a correction is needed. The interface does not describe the correction procedure.

Where do I create a team? Is there a joining code?

Section titled “Where do I create a team? Is there a joining code?”

There is no separate team creation screen or joining code. Enter a team name and select the students you want to invite on the application screen. When the number of selected students, including yourself, is within the program’s minimum and maximum, submitting registers the team, application, and invitations together. Invitees must accept to become members, and the number of accepted members must meet the minimum before approval. You can apply alone only if the program’s minimum is one person. Invitees accept or decline through 팀 초대 알림 (Team invitation notifications) at the top. See Form a team and apply and Invite teammates and respond to invitations.

Does application approval also approve our documents?

Section titled “Does application approval also approve our documents?”

No. Application approval and document review are separate. After an approved team submits documents, staff review each one with 승인 (Approve), 보완 요청 (Request changes), or 반려 (Reject). See Submit documents.

What should I do when changes are requested?

Section titled “What should I do when changes are requested?”

Read the request, revise the relevant items, and resubmit. If no reason is provided, ask the staff member responsible what needs changing. There is no separate resubmission expiry date. After the deadline, each change request permits one resubmission; further edits require a new change request. See Revise and resubmit after a change request.

You cannot make an initial submission after the deadline. Some programs may allow a grace period; submissions made during that period are marked late. If changes have been requested but the submission screen will not let you resubmit, contact the staff member responsible.

Yes. During the application period, the current team leader can revise the application and select 신청서 다시 제출 (Resubmit application). The team and its members remain unchanged, and staff do not need to reset the application to pending review first. To apply with a different team, select 신청 취소 (Cancel application) and apply again. After cancellation, the team and application no longer appear in lists. You cannot cancel if submission records or a linked repository exist. Read the rejection reason through 반려 사유 확인 (View rejection reason) in the dashboard notification. See Manage your team and reapply after rejection.

Can staff or administrators decide applications for their own team?

Section titled “Can staff or administrators decide applications for their own team?”

No. They cannot decide applications or review submissions for a team they belong to. They also cannot process their own staff access request.

Can one account be both staff and an administrator?

Section titled “Can one account be both staff and an administrator?”

Yes. Membership type and administrator access are managed separately. Both 교직원 (Staff) and 관리자 (Administrator) appear at the top, and the left menu has two groups. See Reset membership type and change administrator access.

You are signed out immediately and cannot sign in again. Submissions and consent and activity history are not deleted. Only an administrator can reactivate the account. Students can follow My settings and account deactivation; administrators can follow Deactivate and reactivate accounts.

When is a repository created, and who creates it?

Section titled “When is a repository created, and who creates it?”

If the program provisions repositories, one is created automatically when the application is approved, and team members are invited. Each person must accept their repository invitation on GitHub. To use a public repository you created yourself, the team leader registers its URL in 우리 팀 (Our team). See Check and register a repository.

See the Staff guide.