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
Specialized Accounts: netobserv #521
Comments
(PS: I created the |
We agree to the Specialized Account Expectations |
👋 You've been added to the approval page. Please follow the instructions on the Account Verification page to add |
Hello @jotak ! Did you have a chance to do this yet? |
sorry, was on holidays ... checking that right now, thanks! :-) |
done, thank you! |
Which type of specialized account are creating? If more than one apply, please select the primary type.
Corporate Account (must have already gone through email invite process)
How do you fit in with the community?
NetObserv is an open-source project that certainly falls under the definition of hachyderm's corporate accounts given that maintainers are currently all Red Hat / IBM people and the project being "productized" by Red Hat.
NetObserv is a network observability tool for Kubernetes.
We plan to use this account for sharing news about NetObserv to the tech community, such as release announcements and walk-through, technical blogs, presence in conferences, etc. This account may also be advertised as a conversation channel for the community to engage with the team and have Q&A. We are definitely not going to push repetitive content or anything close to spam. This isn't a marketing account.
How will you ensure the community is protected?
NetObserv is maintained by people at Red Hat with a long tradition of involvement in open-source, respectful with the community and other players in the field, and welcoming diversity. We will of course follow the community rules and specialized accounts expectations.
(Accounts with Automated Posting/Bot Accounts Only)
What method are you using to validate your bots code to ensure that any future updates don't disrupt the community?
No response
The text was updated successfully, but these errors were encountered: