Skip to content

Commit

Permalink
update English guide
Browse files Browse the repository at this point in the history
  • Loading branch information
haksungjang committed Nov 29, 2023
1 parent 8cfcb9b commit ffabfda
Show file tree
Hide file tree
Showing 26 changed files with 224 additions and 1,532 deletions.
192 changes: 92 additions & 100 deletions content/en/guide/opensource_for_enterprise/3-process/_index.md

Large diffs are not rendered by default.

Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
85 changes: 39 additions & 46 deletions content/en/guide/opensource_for_enterprise/4-tool/_index.md

Large diffs are not rendered by default.

154 changes: 75 additions & 79 deletions content/en/guide/opensource_for_enterprise/5-training/_index.md

Large diffs are not rendered by default.

37 changes: 15 additions & 22 deletions content/en/guide/opensource_for_enterprise/6-conforming/_index.md
Original file line number Diff line number Diff line change
@@ -1,50 +1,43 @@
---
title: "6. 준수"
linkTitle: "6. 준수"
title: "6. Conformance"
linkTitle: "6. Conformance"
weight: 60
type: docs
description: >
---

Companies that have built an open source program (open source policy / process / tools / organization) that complies with all requirements except ISO/IEC 5230 3.6, ISO/IEC 18974 3.4 can document and specify the following two things.

ISO/IEC 5230 3.6, ISO/IEC 18974 3.4를 제외한 모든 요구사항을 준수하는 오픈소스 프로그램(오픈소스 정책 / 프로세스 / 도구 / 조직)을 구축한 기업은 다음 두가지를 문서화하여 명시할 수 있습니다.

이를 위해 ISO 표준은 공통적으로 다음과 같이 오픈소스 정책을 알리기 위한 문서화된 절차를 요구합니다.
For this, ISO standards commonly require the following documented procedures to announce open source policies.

{{% alert title="ISO/IEC 5230 - License Compliance" color="success" %}}

* 3.6.1.1 A document affirming the program specified in §3.1.4 satisfies all the requirements of this document.<br>`3.1.4조에서 명시한 프로그램이 이 규격의 모든 요구사항을 충족함을 확인하는 문서`
* 3.6.2.1 A document affirming the program meets all the requirements of this document, within the past 18 months of obtaining conformance validation.<br>`프로그램이 적합성 인증을 획득한 후 지난 18개월 동안 이 규격 버전(v2.1)의 모든 요구사항을 충족하고 있음을 확인하는 문서`
* 3.6.1.1 A document affirming the program specified in §3.1.4 satisfies all the requirements of this document.
* 3.6.2.1 A document affirming the program meets all the requirements of this document, within the past 18 months of obtaining conformance validation.

{{% /alert %}}


{{% alert title="ISO/IEC 18974 - Security Assurance" color="warning" %}}

* 3.4.1.1: Documented Evidence affirming the Program specified in §3.1.4 satisfies all the requirements of this document.<br>`§3.1.4에 명시된 프로그램이 이 문서의 모든 요구 사항을 충족함을 확인하는 문서화된 증거.`
* 3.4.2.1: A document affirming the Program meets all the requirements of this specification, within the past 18 months of obtaining conformance validation.<br>`프로그램이 적합성 인증을 획득한 후 지난 18개월 동안 이 규격의 모든 요구사항을 충족하고 있음을 확인하는 문서`
* 3.4.1.1: Documented Evidence affirming the Program specified in §3.1.4 satisfies all the requirements of this document.
* 3.4.2.1: A document affirming the Program meets all the requirements of this specification, within the past 18 months of obtaining conformance validation.

{{% /alert %}}

따라서, 다음의 내용을 문서화할 수 있습니다.
Therefore, you can document the following:

1. 기업의 오픈소스 프로그램이 ISO/IEC 5230, ISO/IEC 18974 의 모든 요구사항을 충족함
2. 적합성 인증을 획득한 후 18개월 이상 ISO/IEC 5230, ISO/IEC 18974의 모든 요구 사항을 충족하는 상태 유지를 보장함
1. The company's open source program complies with all the requirements of ISO/IEC 5230, ISO/IEC 18974
2. Guarantee to maintain a state that meets all the requirements of ISO/IEC 5230, ISO/IEC 18974 for more than 18 months after obtaining conformance validation

기업은 위의 내용을 오픈소스 정책에 포함시킬 수도 있고, 외부에 공개되어 있는 웹사이트를 통해 게재할 수도 있습니다.
The company can include the above in its open source policy, or it can be posted through a publicly available website.

아래 이미지와 같이 SK텔레콤에서 오픈소스 포털사이트에 이에 대한 내용을 게재한 것을 참고할 수 있습니다.
You can refer to the content posted on the open source portal site of SK Telecom as shown in the image below.
![](sktiso.png)
[https://sktelecom.github.io/compliance/iso5230/](https://sktelecom.github.io/compliance/iso5230/)


이렇게 하면 ISO 표준 규격 중 아래의 파란색으로 표시된 요구사항을 충족할 수 있다.
By doing so, you can meet the requirements marked in blue in the ISO standard specifications.

![](totalno.png)



여기까지 완료하면 기업은 드디어 ISO/IEC 5230, ISO/IEC 18974의 모든 요구사항을 충족하게 됩니다.



Once you have completed this, your company will finally meet all the requirements of ISO/IEC 5230, ISO/IEC 18974.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions content/en/guide/opensource_for_enterprise/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@

---
title: "ISO Standard-Based Enterprise "
title: "ISO Standard-Based Enterprise Open Source Management Guide"
linkTitle: "Open Source Management Guide"
weight: 20
type: docs
Expand Down Expand Up @@ -40,6 +40,6 @@ So, what should companies do to comply with the standards? It needs to have the
3. Process
4. Tools
5. Education
6. Announcement
6. Conformance

To comply with the standards, companies must adhere to these six components:
Loading

0 comments on commit ffabfda

Please sign in to comment.