Skip to content
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

PROCESS CHANGE: Add "Are you using Knative?" issue to Community, link to it, maintain an ADOPTERS.MD in community #648

Closed
omerbensaadon opened this issue Jun 14, 2021 · 9 comments

Comments

@omerbensaadon
Copy link
Contributor

omerbensaadon commented Jun 14, 2021

Proposal: Create a "Are you using Knative?" issue in Community similar to dapr/dapr#3169, pin it.

Create a similar issue in each of our main repos (serving, eventing, docs), pin it, links to this issue in Community.

See the proposed text:

# Are you using Knative?

If you are using Knative, we would love to know!

## Why?
Tracking usage in OSS is hard, if you leave a comment on this issue we can better understand who our users are and deliver a better experience for YOU!

- We'd like to give your organization the opportunity to collaborate more closely with contributors (if you want to)
- We want to help promote your organization 
- We want to show off all the awesome stuff our users are doing 

## How you can help
Submit a comment in this issue to include the following information, which would then also get included into the [ADOPTERS.md]($//TODO LINK) file and (if applicable) on the Knative homepage: 

Organization/Company: 
Website: 
Country: 
Contact: (email or Twitter at least one please!)
Usage scenario: e.g. We use Knative for XYZ
Status: Development?/Production?
  • Expected benefits. Who gains the benefits? Why will they benefit?

We get a better understanding of who our users are, more logos for the website, more reference implementations etc. etc.

  • Expected costs. Who bears the costs? How heavy are they?

Next to nothing

  • Timeframe for implementation / rollout.

As soon as it is approved

  • Are you willing to drive the process, or is this a request for help?

Yes, I need someone to pin the issue in each Repo though (I believe)

@evankanderson
Copy link
Member

/assign @pmorie @bsnchan

@omerbensaadon
Copy link
Contributor Author

I won't be able to attend the next 2 Steering Meetings :(

@xtreme-sameer-vohra
Copy link
Contributor

Related - knative/docs#3246

@bsnchan
Copy link
Contributor

bsnchan commented Jun 21, 2021

cc @knative/steering-committee

I love this idea! I can bring it up at the next steering meeting if you can't make it :)

@bsnchan
Copy link
Contributor

bsnchan commented Jul 8, 2021

Steering loves this idea :) let's do it

/assign @bsnchan

@bsnchan
Copy link
Contributor

bsnchan commented Jul 14, 2021

Main issue created here (#688), will update the issue once I have the ADOPTERS.MD file merged in.

@bsnchan
Copy link
Contributor

bsnchan commented Jul 19, 2021

Issue has been created -- I pinned it at the top of of knative/community. @omerbensaadon - were you thinking to create an issue in serving/eventing/docs as well? I'm worried that the comments may end up in different places if we were to do that. What do you think?

@vaikas
Copy link
Contributor

vaikas commented Jul 22, 2021

/close

We decided to just have one instead of spreading this throughout the various repos.

@knative-prow-robot
Copy link
Contributor

@vaikas: Closing this issue.

In response to this:

/close

We decided to just have one instead of spreading this throughout the various repos.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Steering Committee backlog automation moved this from In progress to Complete Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

7 participants