Proposal: Contributor Experience SIG #2162
Conversation
Signed-off-by: svrnm <neumanns@cisco.com>
Signed-off-by: svrnm <neumanns@cisco.com>
Signed-off-by: svrnm <neumanns@cisco.com>
Signed-off-by: svrnm <neumanns@cisco.com>
svrnm
requested review from
alolita,
austinlparker,
danielgblanco,
dyladan,
jpkrohling,
mtwo,
tedsuo and
trask
as code owners
Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
Co-authored-by: Jamie Danielson <jamieedanielson@gmail.com>
| * Surveys by the End User SIG that aim towards contributor experience | ||
| * _add more_ | ||
|
|
||
| Also related to this initiative is the [Check-In process of the Governance Committee](https://github.com/open-telemetry/community/blob/main/gc-check-ins.md) |
There was a problem hiding this comment.
Another related resource is the CNCF's cross-cutting Contributor Experience SIG. https://github.com/kubernetes/community/tree/master/sig-contributor-experience
Feels like one of the things this group might do is maintain a relationship with them and consult them for best practices and resources where that makes sense, as well as upstream our governance resources into their repos for other projects when that makes sense.
There was a problem hiding this comment.
How do we feel all this fits with the current role of the "community manager"? Maybe that was an interim solution and we need a ContribEx SIG, not a single community manager, but if we're going to continue that role we should address the relationship. cc @austinlparker
There was a problem hiding this comment.
Feels like one of the things this group might do is maintain a relationship with them and consult them for best practices and resources where that makes sense, as well as upstream our governance resources into their repos for other projects when that makes sense.
Ah, let me another item for that :-)
Good point around the Community Manager role, @austinlparker wdyt?
|
@open-telemetry/governance-committee please take a look and review |
| * SIGs are short of contributors and require some help to advertise their need | ||
| (blog post, social posts, etc) and to lower the barrier of entry into their | ||
| sub-project. | ||
| * _add more_ |
There was a problem hiding this comment.
This may not be the way to write it, but I'd like to be able to focus on this issue. and also not dismiss it as a problem of the people on that side for not showing up on occasions a secondary timezone meeting was attempted. The root of the issue is we need to refocus on building with conscious and active involvement in making other timezones work. We don't want to accidentally treat one side of the earth as folks who are relegated to watching the others lead, or force them to interrupt their sleep or family duties.
| * _add more_ | |
| * implicit bias towards founding members timezones, such the majority of SIG meetings occurring at 11pm or midnight UTC+8. |
There was a problem hiding this comment.
Thanks for adding this, as someone who is semi-affected by that as well, I fully agree. A layer that adds to the problem is that an answer people often get is "if you want your issue to make progress, please come to the SIG meeting". I understand why we say that and I said (and say) the same thing myself. In a broader sense, there is also an implicit bias that people share a work culture, e.g. they know periods of time where most people are off (e.g. last and first week of the year), they understand certain terminology and to be fluent enough in English to participate in a SIG meeting.
I tried to broaden your suggestion to include that:
| * _add more_ | |
| * Implicit bias towards US (and EU) working hours, rituals and modes of operation. Majority of SIG meetings occurring from early PST onward. |
This PR proposes the establishment of a "Contributor Experience SIG". While this is "yet another SIG" initiative, not establishing such a SIG is not an option: the problems outlined in this document will get bigger not smaller and while the final ownership of the health of the project is with the @open-telemetry/governance-committee this requires a coordinated effort and more hands across the project to be addressed successfully.