[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-191415-105":53,"doc-detail-191415-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","open-source-united-common-policy-framework-rc1-code-and-governance-stage-guide","Open Source United - Common Policy Framework RC1 - 代码与治理阶段指南","","Open Source United Common Policy Framework RC1 defines organizational principles for delivering open source projects with neutrality, independence, and alignment to UN common goals. It outlines expectations for contributing back to the community, embedding security from the outset through peer reviews and audits, and fostering inclusive participation via outreach, mentorship, language accessibility, and lower entry barriers. It also covers reuse-oriented design, comprehensive documentation for multiple audiences, the RISE recognition and empowerment approach, and how to sustain and scale solutions using long-term funding and adaptable architectures. The framework further specifies stage-based governance, licensing, cataloging, code hosting, and capacity building requirements across S1 to S3.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/open-source-united-common-policy-framework-rc1-code-and-governance-stage-guide/191415/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/open-source-united-common-policy-framework-rc1-code-and-governance-stage-guide/191415.png","ImageObject",442,249,{"name":88,"@type":89},"Jacob","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-02","2026-09-03",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",8,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What does “Open by Default” require for projects?","Question",{"text":109,"@type":110},"Projects should establish open source as the default development approach and remain impartial, neutral, and independent, avoiding tight coupling with commercial products or promotion of specific commercial interests.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How is “Secure by Design” implemented across software projects?",{"text":114,"@type":110},"Security must be embedded from the outset and maintained through thorough peer reviews, regular audits, and adherence to best security practices to keep a secure code base across all projects.",{"name":116,"@type":107,"acceptedAnswer":117},"What is the purpose of the stage model (S1, S2, S3) in the framework?",{"text":118,"@type":110},"The stage model specifies which governance and operational elements are optional, recommended, or required at each stage, covering areas such as core policy statements, licensing compliance, software cataloging, code hosting platform choices, and capacity building.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},191415,1788408482,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":126,"read_time":141},962084931830,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","| 1\u003Cbr>Open by Default | Making Open Source the standard approach for our projects. Reinforce our commitment to existing practices by establishing Open Source as the default approach for development within our organization. Ensure that our projects remain impartial, neutral, and independent, aligning with the common goals of the UN, while avoiding tight coupling with commercial products or the promotion of any specific commercial interests. |\n| --- | --- |\n| 2\u003Cbr>Contribute Back | Encouraging everyone to actively participate in the Open Source ecosystem. This principle emphasizes that contributions should not be just about using Open Source but also actively giving back to the community through code, documentation, or other forms of engagement. |\n| 3\u003Cbr>Secure by Design | Making security a priority in all our software projects, not just Open Source. Security practices should be embedded from the outset, with thorough peer reviews, regular audits, and adherence to best security practices to maintain a secure code base across all projects. |\n| 4\u003Cbr>Foster Inclusive Participation and Community Building | Enabling and facilitating diverse and inclusive contributions from all, while creating a supportive and collaborative environment. Create inclusive communities by engaging in targeted outreach, mentorship programs, and providing tools that support contributors from diverse backgrounds. This includes efforts to reach underrepresented groups, ensuring language accessibility, and providing resources that lower the barriers to entry for participation. |\n\n\n| 5\u003Cbr>Design for ReusabilityWhite Labeling | Designing projects with the intent to be reused by other teams and organizations, through service-agnostic architecture components, configurability, easy installation, and modularity.\u003Cbr>Adopt a service-agnostic approach and Open Standards, our projects will be interoperable across various platforms and ecosystems. Ensure that our solutions are flexible, adaptable, and easily transferable, allowing different teams and organizations to tailor them to their needs. |\n| --- | --- |\n| 6\u003Cbr>Provide Documentation (using, implementing, developing, managing) | Providing thorough documentation for end-users, integrators, and developers to ensure the value of the project. Provide clear, comprehensive and provide step-by-step instructions, examples, tutorials, and multilingual documents where possible. Documentation should cater to different audiences, from end-users to developers, ensuring that anyone can effectively use, implement, or contribute to the project. |\n| 7\u003Cbr>RISE (Recognize, Incentiv ize, Support, and Empower) | Welcoming participation from all, empowering individuals and communities to actively participate, raise awareness, and acquire skills in Open Source.\u003Cbr>Emphasize the importance of recognizing and incentiviz ing contributions while providing the necessary support and resources to enable meaningful participation. |\n| 8\u003Cbr>Sustain and Scale | Supporting the development of solutions that are sustainable in the long term and scalable to meet the evolving needs of the UN system and beyond. Prioritize humanity by utilizing open source technology in ways that center human needs. This includes establishing long-term funding models, fostering partnerships, engaging with the community regularly, and building solutions with adaptable architectures. This approach will ensure that projects can evolve and scale as needed, effectively meeting future challenges and demands. |\n\n\n| ID | Guidelines | Governance Structure (open source team, project, OSPO…) | Core Policy\u003Cbr>Statements | Licensing &\u003Cbr>Compliance | Software\u003Cbr>Catalog | Code Hosting\u003Cbr>Platform | Capacity\u003Cbr>Building |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| S1 | Stage 1 | Optional | Recommended | Required | Recommended | Recommended | Optional |\n\n\n| ID | Guidelines | Governance Structure (open source team, project, OSPO…) | Core Policy\u003Cbr>Statements | Licensing &\u003Cbr>Compliance ","cbCaif7ZAGcwWqtW","https://ap.wps.com/l/cbCaif7ZAGcwWqtW","pdf",530683,29,"English","# Guiding Principles\n## Open by Default\n## Contribute Back\n## Secure by Design\n## Foster Inclusive Participation and Community Building\n## Design for Reusability - White Labeling\n## Provide Documentation (using, implementing, developing, managing)\n## RISE (Recognize, Incentivize, Support, and Empower)\n## Sustain and Scale\n# Stage-Based Governance Overview\n## S1\n## S2\n## S3","[{\"question\":\"What does “Open by Default” require for projects?\",\"answer\":\"Projects should establish open source as the default development approach and remain impartial, neutral, and independent, avoiding tight coupling with commercial products or promotion of specific commercial interests.\"},{\"question\":\"How is “Secure by Design” implemented across software projects?\",\"answer\":\"Security must be embedded from the outset and maintained through thorough peer reviews, regular audits, and adherence to best security practices to keep a secure code base across all projects.\"},{\"question\":\"What is the purpose of the stage model (S1, S2, S3) in the framework?\",\"answer\":\"The stage model specifies which governance and operational elements are optional, recommended, or required at each stage, covering areas such as core policy statements, licensing compliance, software cataloging, code hosting platform choices, and capacity building.\"}]","Open Source United - Common Policy Framework RC1 - 代码与治理阶段指南 | PDF",10]