-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PROJECT ONBOARDING] OpenEBS #299
Comments
Thanks @Cmierly . Since OpenEBS has been previously in Sandbox, majority of the items in the checklist can be marked as completed. Shall I do that with supporting evidence in the quote-reply? |
@avishnu yes, please do (for the full visibility). |
Review and understand
Thanks for sharing. The links provide very useful insights and have been reviewed. Contribute and transfer
Believe this is completed. Exists at https://github.com/openebs
Believe this is completed. thelinuxfoundation is an organization owner for openebs.
Believe this is completed. There are 2 channels 'openebs' (for community users) and 'openebs-dev' (for community developers) in Kubernetes slack workspace. There is also an 'openebs' channel in CNCF slack workspace. |
OpenEBS is currently existing in the Cloud Native Landscape as a cloud-native storage project. |
Since OpenEBS was previously in Sandbox, the domain, trademark and logo assets are already with CNCF. Can you help us find this information? |
|
OpenEBS website (https://openebs.io) is integrated with Google Analytics 4 engine. Will reach out to [email protected] for help with transferring. |
Hi Vishnu, I've marked off the domain name item as I confirmed we have openebs.io and openebs.org in the LF's records. We do not seem to have the trademark document. We have a new process for that so I will share new documents when they've been generated. For analytics, you can open a Service Desk ticket to take care of that. Patrice on our team will handle it. But, in order to get access to Service Desk, we'll also need you to provide your maintainer email addresses. You can send those to [email protected]. |
https://github.com/organizations/openebs/settings/installations/7220130
Thanks @krook . I've emailed [email protected] with the maintainer details. Will wait for the new process of trademark transfer and documents to be shared with us. |
@avishnu Thank you for submitting the maintainer details @krook @Cmierly I have added the maintainer details to our internal records. Now that I have those details, I can invite you to join the CNCF instances of either FOSSA OR Snyk. Please let me know which scanning service the OpenEBS project would prefer to use to monitor compliance with the license allow list Many thanks again. |
Update and document
GitHub app for DCO is installed in OpenEBS GitHub org and enabled for all the repositories. Refer: https://github.com/organizations/openebs/settings/installations/7220130
Every repository in the project has a reference to CNCF code of conduct (https://github.com/openebs/community/blob/HEAD/CODE_OF_CONDUCT.md). Have raised this PR as well.
OpenEBS website (https://openebs.io) has the LF footer and trademark usage guideline sentence. We will make changes for "Sandbox-level projects should include the sentence “We are a Cloud Native Computing Foundation sandbox project.” and the CNCF logo." soon.
Raised the PR: cncf/foundation#878 for the aggregated CNCF maintainer list.
The maintainer details have been emailed to [email protected].
The current project governance is penned here: https://github.com/openebs/community/blob/develop/GOVERNANCE.md. The maintainers will engage with CNCF on improving this and reaching the open governance benchmarks.
OK. |
@Cmierly what does explicit mean here? We usually point to https://github.com/openebs/community/blob/HEAD/CODE_OF_CONDUCT.md which in turns point to the CNCF Code of Conduct.
Guess we ought to modify both the org .github/README and the main repo/README? |
Thanks @avishnu
|
Thanks @RobertKielty . I believe we are already part of a FOSSA 'team' called 'OpenEBS' which has access to 43 repos today. So, we could continue with FOSSA. |
@RobertKielty
|
I've added myself to the #maintainers-circle Slack channel. Thanks @krook . |
I have confirmed OpenEBS team is there. https://app.fossa.com/account/settings/organization/teams/485 I have upgraded the permissions of @tiagolobocastro and @avishnu so that you both have Team Admin permissions. Those permissions mean that you should be able to interact repos (Projects in FOSSA) that have been added to the Team, |
Hi @RobertKielty, I do see that I am now a team admin but I still seem to have issues when trying to use the github action or the cli tool:
|
@krook concerning the OpenEBS trademark:
I believe LFX already owns the trademark for OpenEBS (its listed on https://www.linuxfoundation.org/legal/trademarks). |
@tiagolobocastro, it was nice meeting you yesterday. Thank you for your time and effort in completing this task. @krook, Tiagao added 29 OpenEBS repos to the OpenEBS team on CNCF FOSSA
Some of the repos have a large number of license issues reported. FOSSA is reporting on all transitive RubyGem dependencies because of Ruby licensing @tiagolobocastro you and the OpenEBS project team can confer with @jeefy and @krook both here and on the onboarding meeting on how to act on the license issues found. |
Project has been added to CLOMonitor |
Need help on transferring the website analytics. |
OpenEBS DevStats instance unarchived. |
Project was added to All CNCF DevStats instance (backfilled data when OpenEBS was archived and fully regenerated all dashboards). |
Welcome to CNCF Project Onboarding
This is an issue created to help onboard your project into the CNCF after the TOC has voted to accept your project.
We would like your project to complete onboarding within one month of acceptance.
Please track your progress by using "Quote reply" to create your own copy of this checklist in an issue, so that you can update the status as you finish items.
Review and understand
Contribute and transfer
thelinuxfoundation
as an organization owner to ensure neutral hosting of your project.Update and document
README
on GitHub.README
file).CNCF staff tasks
The text was updated successfully, but these errors were encountered: