Skip to content

2025-03-20.md

Latest commit

 

History

History
62 lines (54 loc) · 2.96 KB

2025-03-20.md

File metadata and controls

62 lines (54 loc) · 2.96 KB

Open Sustain Technology

2025 March 20

Participants:

  • Andrew Nesbitt
  • Richard Littauer
  • Tobias Augspurger
  • Michael
  • Pierre Vogler-Finck
  • Josh Hopkins

Secretary: ?

Agenda and Notes

  • Check-in
  • GitHub and climate triage
    • Tobi in Lead
    • Relaunch climate triage, update logos with companies and people involved in the relaunch
    • Adding additional Analytics
      • should cover how many issues are closed and how many are closed (e.g. per month)
      • Excerpt from Tobis mail to michael (from github)
Here some more ideas how to increase and measure impact: 
1. We should motivate the open source community in this area to add Good First Issue labels to their issues.
2. We should use a consistent hashtag in our post and motivate people to use the hashtag if they talk about the project or closed an issue. The hashtag could be measured across GitHub but also social media platforms. We could use #climatetriage but also some other GitHub hashtag. 
3. I will write a blog post draft for OpenSource.org that we can sign and share together. OpenSource.org helped a lot in the past in doing marketing for the project.
4. We should try to motivate some Open Source "Influence" people to share our content. 
5. We should set up a chat room or something similar where we guide people and match them according to their skills to some open source project. The OpenSustain.tech community can help this people to find good project to participate. 

- How do we ensure githubs 'important' considered OS projects align with the ones from OST
    - Github has some OKR's developed with https://speedandscale.com/

  • redoing the plots from the old report with new backend data

    • Michael takes lead
      • Do appointment with Josh and Tobi
    • Will be used for the github climate week in SF
    • What plots do we need?

  • 2025 report?

  • Governance doc

  • Issue about that we need a process to enable humans to update metadata -> Pierre creates Issue

  • Andrew

    • Took over numfocus hackathon (innovation sprint) -> trying to get some machine learning people to use ost data as training data and to classify new entries
    • Where is any additional data about OST projects stored? What is the central data store?

  • Tobi

    • Names for people working on ost
      • Head of Investigation
      • Head of Data Mining
      • Head of Ecosystem Study
      • Head of Analysics
      • Head of Community Growth
      • Head of Ecosystem Support
      • Head of Advocacy
      • We should be aware of the signaling of the names
    • OST projects are 90% for developers, and ~10% with a nice frontend which also ca
    • We can not show historical data/data growth at the moment because we do not have any historical data