List view
[Related Strategic goal](https://github.com/todogroup/governance/blob/main/goals.md) Co-leads: Annania, Ashley - Re-take recurrent conversations interest in topics like the CRA, the EU AI Act, and definitions around Open Source Software in AI - Proactively communicate Agenda recurrent topics ahead of scheduled meetings - Implement a feedback system after calls (e.g slack survey) to gauge participant interest, satisfaction, and suggestions for future topics # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## Highlight 2 Brief Description OUTPUT: [Link]() ## Highlight 3 Brief Description OUTPUT: [Link]()
Due by December 31, 2024•1/1 issues closed- Build content for an exam designed for developers working in enterprises and students aspiring to work in enterprise environments with a focus on open source software (OSS) usage and contribution. - Work closely with LF Training to develop the initial Minimum Viable Product (MVP) for the certification course. Get Steering Committee member's approval and review of exam questions. - Identify developers within participating organizations to take a beta version of the exam # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## September: SME Item Writing Phase CODE Certification is now in the Item Writing Phase. We have collected over 20 SMEs to contribute in this phase. - The LF Cert team conducted an Item Writing Workshop and is currently providing Office Hours to help SMEs navigate through the LF Education platform to build the exam questions. - In total, SMEs must help write 200 questions across the different exam outline sections (e.g 1 question from Issues & Pull/Merge Requests; 4 questions from Intellectual Property, Software Licensing, and Open Source Legalities; 3 questions from SBOMs; 2 questions from Contributing to Upstream Projects). - The beta version is expected to be launched at LFMS. To achieve this, we need each author to submit at least 10 questions before October 8th (Tuesday). More details here: https://github.com/todogroup/governance/issues/349 ## August: Moved to JTA Survey Responses to this survey Certified Open Developer for Enterprise (CODE) provides feedback on the Job Task Analysis prior final content creation for the question's exam. Currently, JTA Survey is accepting responses until August. An email was sent to those folks who shared their interest in helping out. More details here: https://github.com/todogroup/governance/issues/322 ## April: Gathered SME to take the Survey - Next step for LF Training and Cert is to invite participants who completed the survey via email. Waiting for the marketing team to run it. - Participants include: open source developers working in organizations, OSPO managers, and legal experts working in open source. More details here: https://github.com/todogroup/governance/issues/341
Due by December 31, 2024•4/4 issues closedCo-leads: Ana, Leslie, Annania Update the way Touchpoint calls operate. Work on an improved framework to make touchpoint calls to become a space where: - [Keep Doing] Share pain points and success stories from OSPO professionals - [New] Invite C-level executives and independent practitioners to discuss strategic alignment and pain points, enriching the conversation with diverse perspectives. Introduce an approach of preparing a brief 5-minute presentation in advance of discussions to provide a structured starting point for dialogue. - [New] Create more concrete outcomes, such as insights gathered to contribute to the OSPO Book, present findings at OSPOCons, and possibly develop a whitepaper, documenting best practices and tactics for OSPO integration into business strategies. - [Keep Doing] Maintain Chatham House Rules to ensure privacy and openness in conversations. # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## Highlight 2 Brief Description OUTPUT: [Link]() ## Highlight 3 Brief Description OUTPUT: [Link]()
Due by December 31, 2024•1/1 issues closed[Related Strategic goal](https://github.com/todogroup/governance/blob/main/goals.md#%EF%B8%8F-cross-community-collaboration) Co-leads: Nik - Explore potential collaborations with existing AI SIG closer to OSPO core needs (e.g open chain AI Compliance SIG, Open Source Initiative AI definition WG, etc). - Plan and host a webinar on AI compliance best practices, inviting speakers from related communities and allowing time for open discussions. # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## Highlight 1 Brief Description OUTPUT: [Link]() ## Highlight 2 Brief Description OUTPUT: [Link]()
Due by December 31, 2024[Related Strategic goal](https://github.com/todogroup/governance/blob/main/goals.md#%EF%B8%8F-cross-community-collaboration) Co-leads: Nik - Create mechanisms for feedback between OSPOs and the project's maintainers to ensure the tool evolves in response to the changing needs of the community. # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## Highlight 1 Brief Description OUTPUT: [Link]() ## Highlight 2 Brief Description OUTPUT: [Link]()
Due by December 31, 2024View related Strategic Goal [here](https://github.com/todogroup/governance/blob/main/goals.md#%EF%B8%8F-cross-community-collaboration) Co-leads: Brittany - Facilitate the exchange of tools, best practices, and insights between the InnerSource Commons community and TODO. - Ensure we keep highlighting InnerSource Commons initiatives during OSPOlogyLive mini-summits. # Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## ISC Distribution Partners and Advisors for the OSPO Survey 2024 A key focus of ISC's involvement was to include questions specifically about the involvement in innersource best practices within OSPOs or open source management and strategy, to analyze trends and evolution over the years. OUTPUT: [Link](https://www.research.net/r/5GNDNPL) ## Multiple ISC and TODO talks at Conferences on the value of OSPOs working with ISPOs [Completed] How Should Your OSPO Work with InnerSource? - Russell Rutledge, InnerSource Commons Foundation & Ana Jiménez Santamaría, TODO Group OUTPUT: [Link](https://sched.co/1aBOc)
Due by December 31, 2024•2/2 issues closed[Related Strategic goal](https://github.com/todogroup/governance/blob/main/goals.md#%EF%B8%8F-cross-community-collaboration) Co-leads: Stephen, Georg, Brittany Examples of successful collaboration: - Share tools and best practices related to OpenSSF that an Open Source Program Office can leverage. For instance, the adoption of OpenSSF scorecards to improve security practices across a company's development processes. - Increase participation and contributions to OpenSSF and Special Interest Groups by promoting their resources and tools across various TODO Group platforms and calls. ## Highlights This section is dedicated to the Steering Committee and Project Manager to document a list of activities that have been accomplished in relation to this objective within the community: ## Invited OpenSSF to have a Q&A session in all Touchpoint calls during February and March Conversations and questions around the scorecard implementation best practices, API visualizer, monitor tools and more. OUTPUT: check summary notes [here](https://github.com/todogroup/ospology/discussions/442) ## Highlight 2 Brief Description OUTPUT: [Link]() ## Highlight 3 Brief Description OUTPUT: [Link]()
Due by December 31, 2024•2/2 issues closed**Help from:** Stephen A. **Description:** Some of the TODO communication channels are not accessible to all for several reasons: (1) Internal policies for the organizations forming TODO, (2) geographical restrictions to access tooling, or (3) incorrect team affiliation. Slack issues: * Not everyone can access it due to limitations (1) and (2) * Discussions get lost and are hard to search * Conversations are deleted after some time * Can’t create sub-threads or live discussions Mailing List issues: * Since it’s attached to google accounts, people who can’t access google are not able to see past conversations GH Discussions: * GitHub Discussions solves Slack issues but is not well adopted (needs more time and maybe educate the community to use it) **How?:** * Create onboarding guides for TODO Community and General members (DONE) * Keep reviewing GH Discussions (AKA OSPO Forum) evolution * Build a list of alternatives * Evaluate risks and constraints for each tool * Ask the community * Only in case a migration is approved, set up migration deadlines
Due by December 7, 2022•1/1 issues closed**Help from:** **Description:** Create network spaces where all the community and general members can participate without geographical limitations. Work done so far: ✅ Work Day Activity Meetings have APAC, EMEA an AMER friendly timezones ✅TODO Sync Meetings are supported for Europe and APAC chapters (EMEA and APAC friendly timezones) ✅ OSPOlogy is AMER and EMEA friendly, and sessions are recorded and uploaded on OSPOlogy youtube channel **How?:** * Define an official process via: https://github.com/todogroup/governance/issues/111: Let the community propose ideas (e.g TODO Europe chapter sync meetings)
Due by December 7, 2022•2/2 issues closed**Help from:** Stephen A. **Description:** Current TODO Website has outdated information and does not show many of the new resources initiated in TODO. Some initial contributions have been made to update existing pages (e.g Community page, about, index, etc) but the website demands a new wireframe design that contains more sections that visualize what TODO actually is + re-define content on each of the sections How?: * Create Wireframe (DONE) * Audit existing website content and search for flaws * Work with the community on the new website content * Define communication channels to sync (DONE: #project-website ) * Define a place to work on new content as a draft (DONE: g.doc) * Set up official sync meetings where people can work on this if they wish (DONE: Work Day Activity meetings) * Communicate to the website development team the desired changes/ updates (team provided by LF and having sync with TODO PM, who should act as the linchpin between the community and the dev team) * Make PRs in order to progressively make content updates
Due by December 7, 2022•1/1 issues closed**Help from:** Dawn **Description:** TODO Surveys have been sent to TODO General members on an annual basis. This year, TODO should conduct 2 surveys (1) for those orgs that support TODO as General Members and (2) for those participating in the TODO Community. **How?:** * Determine the timeline for the surveys * Work on the questionnaire for both surveys. * Set up a plan for distributing and reminders to complete the survey.
Due by December 7, 2022•3/3 issues closed**Help from:** Every Steering Committee Member **Description:**TODO is an open community of practitioners who aims to create and share knowledge about Open Source Program Offices or similar Open Source initiatives. TODO Community and its resources are open to all, and it should be clear that there are no exclusions for people or from adjacent communities willing to become part of the TODO community. **How** * Set up an entire SC meeting to discuss this topic * Audit existing documentation for OSPO Associates program and search for improvements * Decide whether or not to build a Partner program
Due by December 7, 2022•1/1 issues closed**Help from:** Shilla, SJ, Thomas S **Description:** Right now, TODO PM is the one Moderating all OSPOlogy sessions. How can the ST members become moderators for specific OSPOlogy sessions? What other actions can be implemented to add more value to the upcoming OSPOlogy sessions where SC members can work at? What other actions can be implemented to add more value to the upcoming OSPOlogy sessions for the audience? **How:** * Review existing OSPOlogy process (how the community can submit new topics and join the call), tooling (videoconference platform used), and editor/admin access. * Search for improvements and define ways to fix the presented issues
Due by December 7, 2022•1/1 issues closed**Help from:** VMB, Thomas S **Description:** In the past, there wasn’t a documented clear process to produce new TODO Group guides or OSPO use cases. Initial documentation was created and added to the todo website + GH todogroup.org repo but can be improved. **How?:** * Audit existing documentation and look for missing information (e.g set up a standard roadmap when someone creates a new use case) * Submit PR to improve existing/ new documentation * Create new documentation for other content that is missing
Due by December 7, 2022•1/1 issues closedv2.0 of the TODO Group Charter
Due by May 31, 2017