Open hythloda opened 6 months ago
@hythloda adding Dick's linkedin profile here for people who are interested in knowing more about his contribution and impact to OSS work (ActiveState) and identity work (OpenID Foundation, OAuth 2.0)
https://www.linkedin.com/in/dickhardt/
I support this. Looking forward to seeing how Hello Identity Coop's identity contributions are brought forward within our TIs. Please encourage TAC engagement if needed while getting alignment and integrated with TIs.
@sevansdell Do you know if there is a way to do the voting on Hello's associate membership sooner rather than later? Are things like this able to get voted on asynchronously. I'm asking because if the GC does not vote until May 30th this means they will likely miss the next Associate Member Town Hall. I see that the next Associate member Town Hall is also May 30th and then the next one is not until July. I'm just thinking about the member experience of being on hold for such a long time. Will they still be motivated to contribute after this amount of time? I would think the May 30th Associate Town Hall would be an opportune time for them to introduce themselves as new Associate members, assuming all goes well with the approval process. Unsure about this but just flagging for consideration.
Dana this is the first time GC has used an asynchronous process to vote and we didn’t have advance notice this was coming. To expedite I’d recommend reaching out to GC voting members individually and amplifying your ask and the timeline. Good luck!!
Get Outlook for iOShttps://aka.ms/o0ukef
Internal Use - Confidential
From: Dana Wang @.> Sent: Wednesday, May 22, 2024 5:59:13 PM To: ossf/Governance-Committee @.> Cc: Evans, Sarah @.>; Mention @.> Subject: Re: [ossf/Governance-Committee] New Associate Member Application: Hello Identity Co-op (Issue #29)
[EXTERNAL EMAIL]
@sevansdell [github.com]https://urldefense.com/v3/__https://github.com/sevansdell__;!!LpKI!nDY5HwmC2v-DPezk76-dUHnxlD84THeeAUNRHeVJJWVCb5hFvKNS9Q5HKjkT1szm5u_d0voF1FkkMxDenv9128IL$ Do you know if there is a way to do the voting on Hello's associate membership sooner rather than later? Are things like this able to get voted on asynchronously. I'm asking because if the GC does not vote until May 30th this means they will likely miss the next Associate Member Town Hall. I see that the next Associate member Town Hall is also May 30th and then the next one is not until July. I'm just thinking about the member experience of being on hold for such a long time. Will they still be motivated to contribute after this amount of time? I would think the May 30th Associate Town Hall would be an opportune time for them to introduce themselves as new Associate members, assuming all goes well with the approval process. Unsure about this but just flagging for consideration.
— Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/ossf/Governance-Committee/issues/29*issuecomment-2125961975__;Iw!!LpKI!nDY5HwmC2v-DPezk76-dUHnxlD84THeeAUNRHeVJJWVCb5hFvKNS9Q5HKjkT1szm5u_d0voF1FkkMxDenpIDkgnK$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BBMFTE3H6T62Q75Q7FLP7CDZDUWNDAVCNFSM6AAAAABH3DRANOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVHE3DCOJXGU__;!!LpKI!nDY5HwmC2v-DPezk76-dUHnxlD84THeeAUNRHeVJJWVCb5hFvKNS9Q5HKjkT1szm5u_d0voF1FkkMxDenpHprDTP$. You are receiving this because you were mentioned.Message ID: @.***>
This is an interesting application. I'm curious what groups Dick & Hello would see themselves participating in amongst our TIs?
What is your name? Dick Hardt
What is your email? dick.hardt@hello.coop
What is your member company? Hello Identity Co-op
Identify which category their organization falls under: Non-profit
Link to your website: https://hello.coop/
What is your organizational mission statement: Give users control over their identity
What drives your interest in joining the OpenSSF? Give OSS developers control over their identity
What are your organization’s aspirations for contributing to the OpenSSF, and how do you anticipate that your membership will bolster the OpenSSF's growth and support? We hope to share our insights regarding identity and security, to improve the trust amongst OSS developers, and to improve the trust in OSS by others.
Could you summarize your organization’s contributions to OpenSSF? We are offering a free identity provider for OSS developers to use with Sigstore, and to the Linux Foundation.
Please include any contributions made to OpenSSF or other OpenSSF projects and open-source projects developed using any OpenSSF dependencies. We have added the OpenID Connect device flow to the Hellō Wallet, and have added the Sigstore as an application with the default 'sigstore' identifier. The Hellō Wallet is ready to be used with cosign once https://issuer.hello.coop is added as a provider.
How many developers do you expect to have contribute to OpenSSF projects in the next 6-12 months? Are there other roles such as researchers, analysts or any other positions that you plan on contributing? We are offering to operate a developer identity provider, and to add identity provider features as needed for the Sigstore project.
How do you currently leverage any OpenSSF resources in your organization? We plan on using Sigstore in our OSS projects.
Do you have signing authority for your entire institution? If no, who does? Yes
Do you agree to follow the OpenSSF Code of Conduct Yes
1. Organizational Information/Alignment:
Organizational Mission Alignment:
Non-Profit, Government, or Academic Status:
Brand Alignment and Reputation:
2. Commitment to Open Source Security and Contribution:
Commitment to Contribution:
Commitment to Open Source Security:
Commitment to Open Source Security:
Utilization of OpenSSF Resources:
Educational and Community Engagement:
3. Compliance and Ethics:
Open Source Licensing and Compliance:
No Conflict of Interest: