opensource-observer / oso

Measuring the impact of open source software
https://opensource.observer
Apache License 2.0
74 stars 16 forks source link

Design workshop to capture initial metrics feedback from OP community #1194

Closed ccerv1 closed 7 months ago

ccerv1 commented 7 months ago

What is it?

See here for RF4 Gov Design Experiments and here for Impact Metrics GMT

Goal: Identify what impact badgeholders care about and identify appropriate metrics

Notes from Carl: I would love to jam on how we can make this happen and who the appropriate resource might be. Ultimately, we want some way of learning what forms of impact people care about and then using that to identify appropriate metrics. There are various ways to frame this exercise. Some ideas:

Filter Criteria

In order to have comparable metrics, there need to be some initial filtering criteria. These can be used both for determining eligible projects as well as creating time buckets for comparing projects’ impact.

For example, project must have deployed something on the Superchain before April 1 to be eligible. Then, we care about all sequencer fees generated between Nov 1 (~R3) and Apr 30, ie, over a 6 month period.

ccerv1 commented 7 months ago

Meetings note from call with Simona here

Next actions: