Contact

SK Telecom OSPO Contact

All open source-related inquiries and requests regarding SK Telecom’s products and services can be directed to OSPO (Open Source Program Office). OSPO is the dedicated organization responsible for enterprise open source management, responding to inquiries on various topics including license review, security assessment, policy consultation, and technical support.

Email Contact

SK Telecom OSPO Email Address: opensource@sktelecom.com

You can inquire about various topics via email:

• Open Source Adoption: You can request license review, security assessment, and compliance verification when planning to adopt external open source in your products.
• Open Source Contribution: You can request CLA/DCO review, legal risk assessment, and contribution approval when contributing to external open source projects.
• Open Source Release: You can consult on project evaluation, license selection, and release preparation when planning to publicly release technology developed at SK Telecom as open source.
• Policy and Guidance: You can consult on open source policies, usage/contribution/release guidance, license understanding, and compliance processes.
• Technical Support: You can consult on technical issues such as open source management tool usage, automation methods, and security vulnerability response.

Response Time: We respond within 2-3 business days.

Online Channels

GitHub

All of SK Telecom’s open source projects are managed through our GitHub Organization.

GitHub Organization: https://github.com/sktelecom

You can engage in the following activities in each project’s repository:

• Issues: Report bugs, request features, ask questions, and make suggestions. SK Telecom’s development team regularly monitors and responds.
• Discussions: Engage in general discussions, share ideas, and participate in community conversations.
• Pull Requests: Contribute code, fix bugs, and suggest improvements to directly participate in projects.

Security Issue Reporting

If you discover a security vulnerability in an open source project, we recommend not reporting it as a public issue. Instead, please email the security contact specified in the project’s README or SECURITY.md file directly. This prevents vulnerabilities from being exploited before patches are distributed to other users.

When reporting security issues, please include:

• Detailed description of the vulnerability
• Reproduction method (PoC, Proof of Concept)
• Impact assessment
• Proposed solution (if available)

Before You Inquire

FAQ and Guidance Documents

Reviewing the following documents first can help you find answers to most common questions:

• Open Source Usage Guide: Procedures and precautions when adopting external open source in your products
• Open Source Contribution Guide: Process and precautions when contributing to external open source projects
• Open Source Release Guide: Procedures for publicly releasing SK Telecom technology as open source
• OSPO Page: OSPO roles, provided tools, and publicly released projects
• OSRB Page: Open source decision-making structure and review criteria

Common Questions

Q: Can we use a specific open source?

• A: Please refer to the Open Source Usage Guide or contact opensource@sktelecom.com.

Q: We want to publicly release code our team developed as open source.

• A: Please read the Open Source Release Guide first, then apply for OSPO consultation.

Q: We want to contribute code to an external open source project.

• A: Review the Open Source Contribution Guide, then obtain OSPO’s review.

Q: What is a license?

• A: Refer to the license explanation on the OSPO page or decision criteria on the OSRB page.

Q: What open source projects has SK Telecom released?

• A: You can check on our Projects page.

Related Organizations

Internal Governance Organizations

SK Telecom’s open source governance is operated through collaboration between OSPO and OSRB:

• OSPO (Open Source Program Office): Executes open source policies, provides guidance, and supports developers
• OSRB (Open Source Review Board): Establishes open source policies, makes decisions, and manages risks

For more detailed governance information, please refer to the About page.