-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Community (TDC) Meeting, Thursday 13 March 2025 #4410
Comments
Undo changes in Once the above PR is merged, the automatically generated sync PR should be mergeable without conflicts |
Fix typo in echoed text: |
Try to sort out the strange issues we saw on our traffic graphs Merging the above PR will refresh which then needs to be merged into The changes this will introduce are similar (ideally: identical) to these changes in my fork: 6f95e6b Main point is to remove lines like these from the respec-rendered HTML: <script type="text/javascript" async="" src="https://www.google-analytics.com/analytics.js"></script>
<script type="text/javascript" async="" src="https://www.googletagmanager.com/gtag/js?id=G-JR4K3ZJLPH&l=dataLayer&cx=c&gtm=457e5350za200&tag_exp=102015666~102067808~102482433~102539968~102558064~102587591~102605417~102640600~102717422~102732003~102788824"></script> |
Discuss future of old schemas on Note: we need to decide and execute this before we can publish v3.2.0 or v3.1.2. |
Weekly meetings happen on Thursdays at 9am - 10am Pacific
This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics.
Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals.
Meetings take place over Zoom: https://zoom.us/j/975841675, dial-in passcode: 763054
Accessibility & Etiquette
Participants must abide by our Code-of-Conduct.
Meetings are recorded for future reference, and for those who are not able to attend in-person.
We invite you to feel comfortable to challenge any language or behaviour that is harmful or not inclusive during this meeting.
We look forward to your participation, but please consider these acts of etiquette:
Agenda Structure
/cc @OAI/tsc please suggest items for inclusion.
The text was updated successfully, but these errors were encountered: