https://todogroup.org/faq/

I am an open source software enthusiast, I wanted to create a similar site was joined by friends around me, but unlike member of the TODO, they are ordinary developers, can I use the website source code and name of the TODO ？

We have to add a cookie banner to customize user consent for TODO website.

To make things easier, we might want to use https://www.cookiebot.com ?

Action Items

• Decide whether or not use cookiebot
• Create account
• Add code snippet into website

Hey @anajsana can you do a blog post announcing the first OSPOLogy series?

Thanks :)

Even if it means putting a free CloudFlare account in front of things and not having it be encrypted end-to-end.

TODO Group represents a bunch of forward thinking companies who do open source, and is angling to play a leadership role in the open source community. When community leaders use HTTPS, it sends a message to the web community.

Create a checklist that summarizes the main activities any organization should work on when starting an OSPO for the first time.

Action items

• Validate with the TODO Community and find potential contributors
• Start a draft on g.doc
• Open a PR

It would be great to have an rss feed for members of the TODO group who have blogs that we can all read especially when they have topics that are centered around OSPO. Would love to see that and published on the website.

One of the TODO Goals for 2022 is to revamp TODO Website. The TODO Community is welcome to participate in the Content Creation for the New Website.

💬 Working Group Sync

We will be using the #project-website channel in the TODO Slack, and meet during the monthly Work Days.

📝 Workspace

To work on content, we will be using this g.Doc. Please join the Slack channel and ask @anajsana to give you access to the file

🖌 Wireframe

pdf version

Please ping @anajsana if you have any wireframe change suggestions to sync with the Web Development Team.

The initial draft can be found here: https://docs.google.com/document/d/1PjIaHnAylGO87KD4wmzZsw5J8787YMXBL9eMcUT5BmI/edit?usp=sharing

Closing conditions

• Create PR

Tools for managing open source programs whitepaper refers to a "Open Source Program Office in A Box" without providing any link.

Right now, footer.html is showing the todogroup.org menu. The menu should be showing at header.html and appear at the top of the page (IMHO, that can improve UX)

The footer should contain the webpage structure and the social media links, at least.

Action Items

• Open a PR with requested changes
• Review PR and merge changes

Page up/down seems to move viewport by its height, including the sticky footer, overshooting by height of the footer, so to not miss text, one must go up or down a few lines after using page down and up respectively.

This does not occur on Firefox. Even then, I dislike needing to page more frequently due to the sticky footer occupying vertical space. 😄

For folk new to TODO Group, having a simple pitchdeck that we maintainer via gslides would be useful!

It would

• brief intro to LF and benefits
• intro on what TODO is, benefits
• intro to TODO guides + OSPO 101 + OSPOCon

We used to have different versions of this but they are old and need to be rebuilt, you can see some other examples here to pull ideas from: https://docs.google.com/presentation/d/1TOBX_Mb-jCz_9TBs-NFmA35PoUiQs6Ob14c9FbbBomM/edit

The following sentence has the word help you repeating twice. Suggest to remove the duplicate.

Partner with other organizations. They can help you help you choose the best projects to get involved with and identify what projects they are reaping benefits from.

I will proceed to open a PR to fix this in compliance to the contribution guide.

TODO website can be improved to make more visible all the resources and upcoming events.

Creating a wireframe to see how do we want the new website to be can be a good starting point.

• Wireframe created

We can add a new OSPO case study to share GitLab's story: https://github.com/todogroup/todogroup.org/tree/main/content/en/guides/casestudies

Action items

• Work on interview questions
• Schedule interview
• Create case study draft
• Create PR

We had a public TODO Group list for awhile that hasn't been utilized, we kill off the google group one and move it to

We should probably just have one public email list here, "todogroup-discuss" or "ospo-discuss"

add a users.md document , which links to the companies/open source projects , who use this template of open code of conduct

They may or "may not" be a member of this group, but still they use this template and acknowledge also. List and links of such projects/organizations will be good and positive.

Hi there,

I'm with Intuit, and we are starting a process of Internal Open-source, which I hope to become more public in the next couple of months... Is there any maturity process that we need to comply so that we can be in the members list?

thanks
Marcello

The FAQ question:

What can deliverables can we expect to see from the group?

contains a more "can" word.

Create a new doc where we can show TODO brand guidelines:

• Visual identity
• Background colors
• Colour Palette
• Typography

• Document created
• pdf version added at todogroup.org

The transparent logo against the light background means the contrast is too low for accessibility purposes.

https://todogroup.org/community/

Join us on Slack to chat open source program management:

Can we create something like https://github.com/todogroup/presentations that will host reusable presentations?

Inspiration: https://github.com/cncf/presentations

We can add a new OSPO case study to share RIT's story: https://github.com/todogroup/todogroup.org/tree/main/content/en/guides/casestudies

Action items

• Work on interview questions
• Schedule interview
• Create case study draft
• Create PR

The first quote in the Uber use case has issues with URLs.

I searched for the file that has this content, but didn't see anything wrong with it:
https://github.com/todogroup/todogroup.github.io/edit/master/content/en/blog/open-source-case-studies-uber.md

Hi all, I was going through the Guides on the TODO website recently, they are really well organized and they are super helpful.

I wonder if we have an archived version of those pages so that people can read locally or even print it as a book?

Thanks!

I want to contribute on translation

GitHub has made this transition process much simpler now: https://github.com/github/renaming#rename-existing. If you're curious why renaming the branch is worthwhile: https://boleary.dev/blog/2020-06-10-i-was-wrong-about-git-master.html. I don't have the necessary access in this repo to make these changes, so I'm hoping a maintainer will agree with this recommendation and take the action as linked by GitHub in my first link above... thanks!

Uber's OSPO case study was published as a blog format. Please add the case study to the TODO guides under Open Source Program Case Studies.

Thanks.

Some SVG images are very damaged in IE:

and Google's is squashed in Firefox:

RIT would like to have Primary Logo (3 big Orange letters) top row left here https://www.rit.edu/brandportal/our-identity-and-logos

Right now OSPO Landscape shows a different logo design

Closing conditions

• PR with changes made

The 2021 Open Source Program Office Survey results have been preliminarily published.

During the August 20, 2021 TODO Group Touchpoint, we ended up discovering a few things that we'd like to take action on in order to improve the survey for next year, and possible help with the published report this year.

This issue is meant for us to gather input on the survey and create actionable next steps.

Current Action Steps

The following are items that generated a discussion. These points include suggested actions.

• Open Source Program Evolution. We should explore adding some questions in the 2022 survey to help us understand the evolution of open source programs into OSPOs. Slides 33-35 in the current survey touch upon where OSPOs are currently located within orgs that already have them. The survey is missing the insight of where programs start and if they end up moving elsewhere. Example: an open source program starts in Marketing and moves to Engineering when it's become an OSPO.
• Buyer Decisions. We discovered that there was some confusion around how to interpret the question on Slide 66: "To what degree does a company’s participation in, and contributions to, the open source community influence your organization’s buying decisions?" The intent was to figure out if the following statement was true: When an organization starts to participate in open source, they are more likely to expect that from other companies they do business with (that the vendor be a good OSS citizen). We should make this questions clearer in future years and we may want to publish a note in the 2021 survey report letting people know of the point of confusion.

This came from TODO Group EU

https://docs.google.com/document/d/1c91nDKueuOH_SFYXQceMkRDsomFesW1GILohJCKQCv4/edit#heading=h.sl8gbpgq9req

Once the wireframe and content are defined, we should check if the current HUGO template can be used to create the new website resources.

If not, we should search for HUGO templates to be added. (i.e https://jamstackthemes.dev/ssg/hugo/ )

• Decide best HUGO Template
• PR Created

We can add a new OSPO case study to share US Bank's story: https://github.com/todogroup/todogroup.org/tree/main/content/en/guides/casestudies

Action items

• Work on interview questions
• Schedule interview
• Create case study draft
• Create PR

All the OSLS 2017 links are broken.

Page: TODO OSLS

Add "community" page that features link to public mailing list + Slack

If I understood correctly all the guides were moved to this repo already.
The https://github.com/todogroup/guides repo should be archived or it should have some pointer to here for potential contributors.

https://landscape.todogroup.org

The Future of Open Source survey link on the Strategy Guide is a dead link and should be updated with a relevant link.

The document https://todogroup.org/guides/create-program/ in its Policies for compliance refers to a "Open Source Compliance in the Enterprise" what is not linked to the document.

Also I could not find it in the TODO pages.

Creating this issue to track ideas for future TODO Group guides.

A collection of tools integrated together should be created and maintained.
This starter package would give companies the ability to launch their open source efforts with a cohesive, pre-assembled kit of tools.

https://l.todogroup.org

maybe add it on the main page, under the "slack" button

Maybe we can have some basic swag items such as TODO stickers and T-Shirts for the upcoming OSPOCon events. I would suggest using the "Talk Openly, Develop Openly" as the main topic.

Closing conditions

• Work on OSPOCon Design
• Order swag

Some things to discuss on the guide "How to create an open source program".

• In "Policies for compliance" there seems to be a published internal comment: "For example [I think we need to mention SPDX and OpenChain tools from The Linux Foundation, along with help from your and working with internal supply chain teams, will internally to ensure that code brought in by third parties is also compliant.]

• "Policies for accepting contributions" seems to be published like this:
  Unless your open source projects are housed at a neutral foundation, you’ll want to […] Rules that set out procedures for your company to receive contributions to your own open source projects from external developers are particularly important.

You'll want to do what?

• Looks like the github. structure is capable of hosting translations. Are translations to other languages accepted? We did this before for the "Open Organization Definition" (https://github.com/open-organization-ambassadors/open-org-definition/tree/master/Translations/Dutch because we're using these definitions in our business.

• Are all the guides still licensed as CCA 4.0 and reusable?