IT之家 6 月 3 日消息 開(kāi)放原子開(kāi)源基金會(huì)是致力于推動(dòng)全球開(kāi)源產(chǎn)業(yè)發(fā)展的非營(yíng)利機(jī)構(gòu)，于 2020 年 6 月正式獲得民政部批準(zhǔn)在北京成立，由阿里巴巴、百度、華為、浪潮、360、騰訊、招商銀行等十家龍頭科技企業(yè)聯(lián)合發(fā)起，由工信部作為業(yè)務(wù)指導(dǎo)單位。開(kāi)放原子開(kāi)源基金會(huì)擬通過(guò)共建、共治、共享的方式，系統(tǒng)性打造信息產(chǎn)業(yè)和工業(yè)開(kāi)源開(kāi)放框架，搭建國(guó)際開(kāi)源社區(qū)，提升行業(yè)協(xié)作效率，賦能千行百業(yè)。目前開(kāi)放原子開(kāi)源基金會(huì)業(yè)務(wù)范圍主要包括為各類開(kāi)源軟件、開(kāi)源硬件、開(kāi)源芯片、開(kāi)源內(nèi)容提供中立的知識(shí)產(chǎn)權(quán)托管、戰(zhàn)略咨詢、法務(wù)咨詢、項(xiàng)目運(yùn)營(yíng)、品牌營(yíng)銷和教育培訓(xùn)等服務(wù)。
今天，OpenHarmony 2.0 孵化和運(yùn)營(yíng)者開(kāi)放原子開(kāi)源基金會(huì)發(fā)布了孵化項(xiàng)目畢業(yè)標(biāo)準(zhǔn) v1.0。
1. 代碼與文檔 (Code and Document)
OA-CD-10
【中】項(xiàng)目代碼是易于找到的，并且能被公開(kāi)訪問(wèn)。
【EN】The project's code is easily discoverable and publicly accessible.
OA-CD-20
【中】可以使用常用的標(biāo)準(zhǔn)工具對(duì)項(xiàng)目代碼進(jìn)行重復(fù)構(gòu)建。
【EN】The code can be built in a reproducible way using widely available standard tools.
OA-CD-30
【中】應(yīng)通過(guò)源代碼管理系統(tǒng)保留項(xiàng)目代碼的完整變更歷史，所有已發(fā)布版本都可以被重新構(gòu)建。
【EN】The full history of the project's code is available via a source code control system, in a way that allows any released version to be recreated.
OA-CD-40
【中】每一行代碼必須由具備強(qiáng)認(rèn)證機(jī)制的提交者通過(guò)源代碼管理系統(tǒng)建立，當(dāng)提交第三方貢獻(xiàn)時(shí)，提交備注中要包含可靠的代碼來(lái)源信息。
【EN】The provenance of each line of code is established via the source code control system, in a reliable way based on strong authentication of the committer. When third-party contributions are committed, commit messages provide reliable information about the code provenance.
OA-CD-50
【中】項(xiàng)目必須有最終用戶文檔，例如：API、CLI、儀表板、安裝部署、配置等。
【EN】The project must have end-user docs in place such as API use, CLI use, Dashboard use, Deployment use, Configuration use.
OA-CD-60
【中】項(xiàng)目應(yīng)具有可證實(shí)的用戶支持歷史，可以是在郵件列表或 issue 系統(tǒng)中的答復(fù)。
【EN】The project should have a proven history of providing user support,such as replies in mailing list or issue systems.
2. 流程 (Process)
OA-PR-10
【中】項(xiàng)目需要有符合業(yè)界最佳實(shí)踐的代碼提交流程。
【EN】The project requires a code commit process that meets industry best practices.
OA-PR-20
【中】項(xiàng)目團(tuán)隊(duì)?wèi)?yīng)該與營(yíng)銷團(tuán)隊(duì)一起確定合適的官方名稱。
【EN】The project should have engaged with marketing team to check suitable official name.
OA-PR-30
【中】項(xiàng)目需要通過(guò)獨(dú)立的第三方安全審計(jì)。
【EN】The project should have completed an independent and third party security audit.
OA-PR-40
【中】項(xiàng)目必須使用基金會(huì)基礎(chǔ)設(shè)施團(tuán)隊(duì)認(rèn)可的任務(wù)、缺陷和設(shè)計(jì)跟蹤工具。
【EN】The project must use task, defect and design track tools that approved by infrastructure team of OpenAtom Foundation.
3. 許可證與版權(quán) (Licenses and Copyright)
OA-LC-10
【中】代碼發(fā)布需要滿足項(xiàng)目所采用開(kāi)源許可證的合規(guī)性 / 兼容性要求，且符合開(kāi)放原子開(kāi)源基金會(huì)的知識(shí)產(chǎn)權(quán)政策。
【EN】The code is released under the open source license that project used, meets the compatibility requirements，and complies with OpenAtom Foundation's IPR policy.
4. 發(fā)布 (Releases)
OA-RE-10
【中】發(fā)布要包含源代碼，分發(fā)時(shí)需要采用標(biāo)準(zhǔn)開(kāi)放的打包格式，以便長(zhǎng)期保持可讀性。
【EN】Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.
OA-RE-20
【中】發(fā)布由項(xiàng)目的項(xiàng)目管理委員會(huì)批準(zhǔn)。
【EN】Releases are approved by the project's PMC (Project Management Committee).
OA-RE-30
【中】發(fā)布需要進(jìn)行數(shù)字簽名或帶有哈希摘要，以校驗(yàn)下載包的完整可靠。
【EN】Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
OA-RE-40
【中】發(fā)布必須包含源代碼，也可同時(shí)發(fā)布二進(jìn)制文件。
【EN】Release must include source code; convenience binaries can be distributed alongside source code.
OA-RE-50
【中】發(fā)布過(guò)程必須有詳細(xì)的文檔說(shuō)明，并且是可重復(fù)進(jìn)行的。根據(jù)文檔指引，任何人能夠獨(dú)立生成發(fā)布所需的所有制品。
【EN】The release process is documented and repeatable to the extent that anyone is able to independently generate the complete set of artifacts required for a release.
OA-RE-60
【中】項(xiàng)目必須有清晰的版本計(jì)劃，并且必須制定至少 2 個(gè)常規(guī)的后續(xù)里程碑。
【EN】The project must have a clear roadmap and must have followed at least two common milestones.
5. 質(zhì)量 (Quality)
OA-QU-10
【中】項(xiàng)目對(duì)代碼的質(zhì)量要開(kāi)放且誠(chéng)實(shí)。
【EN】The project is open and honest about the quality of its code.
OA-QU-20
【中】項(xiàng)目的安全性是最高優(yōu)先級(jí)的。
【EN】The project puts a very high priority on secure software.
OA-QU-30
【中】需要提供一套規(guī)范化的安全響應(yīng)流程。
【EN】The project requires a standardized security response process.
OA-QU-40
【中】項(xiàng)目要重視兼容歷史版本，盡可能將所有不兼容的變更文檔化，并提供工具和使用說(shuō)明幫助用戶過(guò)渡到新的特性。
【EN】The project puts a high priority on backwards compatibility, aims to document any incompatible changes and provides tools and documentation to help users transition to new features.
OA-QU-50
【中】項(xiàng)目應(yīng)該努力及時(shí)響應(yīng)已上報(bào)的 BUG。
【EN】The project strives to respond to documented bug reports in a timely manner.
OA-QU-60
【中】該項(xiàng)目必須具有合理的 CI 流程 / 工具、單元測(cè)試及測(cè)試代碼覆蓋率。
【EN】The project must have decent CI process/tools, unit test and test code coverage.
OA-QU-70
【中】項(xiàng)目對(duì)登記的 issue 應(yīng)進(jìn)行合理的分類、分級(jí)。
【EN】The project should have a decent record of triaging incoming issues.
6. 社區(qū) (Community)
OA-CO-10
【中】項(xiàng)目有一個(gè)眾所周知的主頁(yè)。
【EN】The project should have a well-known homepage.
OA-CO-20
【中】社區(qū)歡迎所有出自善意、行為受尊重、為項(xiàng)目增添價(jià)值的參與者的貢獻(xiàn)。
【EN】The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.
OA-CO-30
【中】貢獻(xiàn)包含但不局限于源代碼，也可以是文檔、建設(shè)性的錯(cuò)誤報(bào)告、建設(shè)性的討論、市場(chǎng)推廣或者其他任何會(huì)為項(xiàng)目增值的內(nèi)容。
【EN】Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project.
OA-CO-40
【中】社區(qū)要符合賢能治理的精神，隨著時(shí)間的推移，為項(xiàng)目增值的貢獻(xiàn)者會(huì)被賦予更多的權(quán)利和責(zé)任。
【EN】The community strives to be meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.
OA-CO-50
【中】社區(qū)的運(yùn)作基于具有決策權(quán)的成員的共識(shí)，避免一言堂。
【EN】The community operates based on consensus of its members who have decision power. Dictators, benevolent or not, are not welcome in projects.
OA-CO-60
【中】項(xiàng)目致力于及時(shí)解答用戶的問(wèn)題。
【EN】The project strives to answer user questions in a timely manner.
OA-CO-70
【中】項(xiàng)目需要在項(xiàng)目網(wǎng)站或 Readme 顯示項(xiàng)目的孵化狀態(tài)。
【EN】The project should list project’s incubation status prominently on website/readme.
OA-CO-80
【中】項(xiàng)目有一定數(shù)量的活躍提交者和相當(dāng)規(guī)模的代碼提交數(shù)量和合并數(shù)量。
【EN】The project should have a healthy number of committers, and demonstrate a substantial ongoing flow of commits and merged contributions.
OA-CO-90
【中】項(xiàng)目應(yīng)明確定義項(xiàng)目治理和提交者的管理流程。
【EN】The project should explicitly define a project governance and committer process.
OA-CO-100
【中】項(xiàng)目應(yīng)至少在主要代碼倉(cāng)庫(kù)中提供公開(kāi)的使用者列表（例如提供 ADOPTERS.md，或在項(xiàng)目網(wǎng)站上展示采用者的 Logo 列表）。
【EN】The project should have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).
7. 共識(shí)建立 (Consensus Building)
OA-CS-10
【中】該項(xiàng)目維護(hù)著具有決定權(quán)的貢獻(xiàn)者的公開(kāi)列表 - 項(xiàng)目管理委員會(huì)由這些貢獻(xiàn)者組成。
【EN】The project maintains a public list of its contributors who have decision power -- the project's Project Management Committee consists of those contributors.
OA-CS-20
【中】決策由項(xiàng)目治理委員會(huì)成員的共識(shí)形成，并在主要的溝通渠道中記錄。要考慮社區(qū)意見(jiàn)，如有異議，項(xiàng)目管理委員會(huì)擁有最終決定權(quán)。
【EN】Decisions are made by consensus among Project Management Committee members and are documented on the project's main communications channel. Community opinions are taken into account but the Project Management Committee has the final word if needed.
OA-CS-30
【中】無(wú)法通過(guò)討論形成共識(shí)的情況下，可以使用文檔化的投票規(guī)則來(lái)達(dá)成目標(biāo)。在項(xiàng)目中，否決權(quán)只對(duì)代碼提交有效，且否決要求有合理的技術(shù)性理由。
【EN】Documented voting rules are used to build consensus when discussion is not sufficient. In projects, vetoes are only valid for code commits and are justified by a technical explanation.
OA-CS-40
【中】所有重要的討論都應(yīng)該以書(shū)面形式在項(xiàng)目的主要溝通渠道上異步進(jìn)行。對(duì)項(xiàng)目會(huì)產(chǎn)生影響的線下、面對(duì)面或私下的討論也應(yīng)在該渠道記錄下來(lái)。
【EN】All important discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel.
8. 中立性 (Independence)
OA-IN-10
【中】項(xiàng)目獨(dú)立于任何公司或組織。
【EN】The project is independent of any company or organization.
OA-IN-20
【中】項(xiàng)目必須有不少于三方的核心評(píng)審團(tuán)隊(duì)。
【EN】The project must have a diverse core reviewers team (at least 3).
OA-IN-30
【中】貢獻(xiàn)者的社區(qū)角色權(quán)限不應(yīng)受雇傭關(guān)系變化而影響。
【EN】The role & permissions of contributors in the community should not be affected when their employment relationship changes.
OA-IN-40
【中】項(xiàng)目畢業(yè)需要至少三位 TOC 成員提名進(jìn)入畢業(yè)流程。
【EN】The project should require at least 3 TOC members to step forward as sponsors to enter graduation process.
9. 成熟度 (Maturity)
OA-MA-10
【中】至少三個(gè)獨(dú)立用戶成功將項(xiàng)目用于生產(chǎn)環(huán)境，TOC 根據(jù)質(zhì)量和范圍判定用戶是否有效。
【EN】The project should be used successfully in production by at least 3 independent end users which, in the TOC‘s judgement, are of adequate quality and scope.
10. 其它 (Others)
OA-OT-10
【中】項(xiàng)目畢業(yè)需獲取全部 TOC 席位 2/3 的贊同票。
【英】To enter graduation, the project should receive the affirmative vote of two-thirds of the authorized TOC.
OA-OT-20
【中】上述指標(biāo)由于項(xiàng)目的類型、范圍和大小不同有一定的偏差，因此 TOC 對(duì)上述指標(biāo)有一定的自由裁量權(quán)。
【EN】Since these metrics can vary significantly depending on the type, scope and size of a project, the TOC has final judgement over the level of activity that is adequate to meet these criteria.
廣告聲明：文內(nèi)含有的對(duì)外跳轉(zhuǎn)鏈接（包括不限于超鏈接、二維碼、口令等形式），用于傳遞更多信息，節(jié)省甄選時(shí)間，結(jié)果僅供參考，IT之家所有文章均包含本聲明。