Project proposal: bootstrap Zig SIG

[inge4pres]

Related to #2514

Propose a new project to form a Zig Special Interest Group.

There is growing interest in Zig, and while there is a working SDK, it would be great to have it officially supported by the OpenTelemetry community.

[austinlparker]

Heya - thanks for this! Do you have any more people who would be interested in maintaining/contributing to this effort? If so could you get them to approve this when it moves from draft?

[inge4pres]

Hello @austinlparker 👋🏻 are you referring to existing OTel community members or other peers in general?

The current un-official SDK for Zig has 3 active maintainers (@kmos, @hendriknielaender, myself) and we will keep working on it.

We'd love to have more people onboard!

[jaronoff97]

@austinlparker i've been speaking with @inge4pres and would be happy to sponsor this and make sure they're off to a good start here. I've been involved with the injector project which is a zig project, i'm going to ask in our injector group if anyone else wants to help out here.

[trask]

Thanks @jaronoff97! I think having someone who's been a maintainer in another OpenTelemetry SIG as (at least) an initial maintainer here would be really helpful here.

@kmos @hndrk - are you able to commit to the time needed to be a maintainer within the OpenTelemetry org? (see https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#maintainer)

@inge4pres can you list company names of the individuals in the proposal? it helps us to ensure that a SIG isn't dominated by any single company, thanks!

The next step after the above is for the GC to vote on approving the new SIG, at which point we would assign a GC liaison and reach out to the TC to request assignment of a TC liaison.

[kakkoyun]

Hey @trask👋 I'm a maintainer of Go Compile-time instrumentation SIG and I can help here as well. I was involved at the creation of this effort but I couldn't dedicate time after that, however now I can so please count me in.

cc @inge4pres

[kmos]

Hi @trask, I’m aligned with @inge4pres and available to contribute and maintain the project. Happy to help wherever needed.

[inge4pres]

can you list company names of the individuals in the proposal? it helps us to ensure that a SIG isn't dominated by any single company, thanks!

@trask affiliation as follows:

@inge4pres: Elastic
@kmos: Red Hat
@hendriknielaender: TaxDoo gmbh
@kakkoyun: DataDog

I realized now that I misspelled Hendrik's GitHub handle in the proposal, now corrected.

The next step after the above is for the GC to vote on approving the new SIG, at which point we would assign a GC liaison and reach out to the TC to request assignment of a TC liaison.

Awesome thanks!
Is the PR good to be undrafted if I'm adding @jaronoff97 as TC sponsor?
Apologies for the seemingly dumb questions but I'm new to the whole process.

[trask]

this looks great! go ahead and undraft it. we'll still need a GC and TC sponsor (@jaronoff97 isn't a TC member), but that will happen after the GC votes on the project.

[jmacd]

I am willing to sponsor this SIG. I know a little about Zig and I want to know learn more.

[trask]

hi @inge4pres! we discussed in the Governance Committee meeting today and would love to see the Zig SIG move forward.

@alolita has volunteered to be GC liaison for the SIG.

our recommendation is to treat the donation as a follow-up to the SIG creation, following the donation process at https://github.com/open-telemetry/community/blob/main/guides/contributor/donations.md

if this makes sense to you, can you update the project proposal to reflect that? thanks!

[inge4pres]

Thanks a lot folks ❤️
I have updated the proposal with the aforementioned people to help bootstrap the SIG.

LGTM donating the project after the SIG is formed and we get more familiar with the rest of the community.

[hendriknielaender]

Thanks a lot folks ❤️ I have updated the proposal with the aforementioned people to help bootstrap the SIG.

LGTM donating the project after the SIG is formed and we get more familiar with the rest of the community.

@inge4pres could you do a small update, and can you remove taxdoo. Since this year iam no longer working there. Thank you.

[inge4pres]

CI failure does not seem related to this PR, i'll try rebasing

Issues found in 2 inputs. Find details below.

[home/repo/projects/resources-and-entities.md]:
[404] https://docs.google.com/document/d/1VUdBRInLEhO_0ABAoiLEssB1CQO_IcD5zDnaMEha42w/edit | Rejected status code (this depends on your "accept" configuration): Not Found

[home/repo/README.md]:
[404] https://docs.google.com/presentation/d/1Neab3OZ3c-m5kOE37iZXEVpK4Pjj6xGTJEUuUzLQJvk/edit?usp=sharing | Rejected status code (this depends on your "accept" configuration): Not Found

[mx-psi]

CI failure does not seem related to this PR, i'll try rebasing

[...]

This is a known issue, see #3300. Feel free to ignore.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: hendriknielaender / name: hndrk (251e175)
• ✅ login: inge4pres / name: Francesco Gualazzi (213f6ca, 21d923f, 4348e0d, cdc5935, d956cf3, df7dd40, e1c2765, f322312, f496f21, 251e175)

[kakkoyun]

LGTM 🚀

[inge4pres]

• ❌ - login: @hendriknielaender / name: hndrk. The commit (251e175) is not authorized under a signed CLA.

@hendriknielaender you should sign the CLA to make this work, that's also going to be needed for the donation process anyway.

[jmacd]

This looks great. I have no reservations and am ready to participate.

[inge4pres]

Thanks everybody for getting this through!

@dmathieu suggested that the next step is to open an issue of type "SIG Onboarding" (thanks Damien 🙏🏼), so I'll do that

[alolita]

Excited to get the Zig SIG started and looking forward to participating in some excellent SIG discussions and OTel features.