Skip to content

Japanese survey - #273

Draft
AndrejKiri wants to merge 3 commits into
mainfrom
japanese-survey
Draft

Japanese survey#273
AndrejKiri wants to merge 3 commits into
mainfrom
japanese-survey

Conversation

@AndrejKiri

@AndrejKiri AndrejKiri commented Feb 16, 2026

Copy link
Copy Markdown
Contributor

Adding a new survey to the repo. Please review. So far it is just a README file and csv with data. We will add analysis later, once it is ready.

@AndrejKiri AndrejKiri self-assigned this Feb 16, 2026
@AndrejKiri
AndrejKiri requested a review from a team as a code owner February 16, 2026 17:37
@AndrejKiri

Copy link
Copy Markdown
Contributor Author

FYI @E-STAT @ymotongpoo @austinlparker

@E-STAT

E-STAT commented Feb 17, 2026

Copy link
Copy Markdown
Contributor

Thanks so much for doing this @AndrejKiri

@ymotongpoo

ymotongpoo commented Feb 17, 2026

Copy link
Copy Markdown

@AndrejKiri @E-STAT We didn't ask for the user consent to share the answer publicly. Given that, the raw data should not be publicly shared.
ref: https://docs.google.com/forms/d/14-392OfyoCezrDQKyO5LhCQGyBhTSJvR-9MLgPQ0maU/edit

@AndrejKiri

Copy link
Copy Markdown
Contributor Author

@ymotongpoo Fair point. Thanks for raising it.

In the past, we shared data for all surveys that SIG End-user conducted in our repo by default. I don't think we asked for consent for any of them. But that doesn't mean it wasn't a mistake. We should start doing that for sure. Here is an issue to make sure we do it in the future.

For this particular case, I am wondering if there is anything we can do to still publish the data. 🤔 I think the data is pretty anonymous already. We can make potential identification of individual respondents even harder by breaking the data set into multiple .csv files—e.g., having demographic questions separate, open-ended questions separate, and the rest of the questions separate. That way there is IMO no way to identify who responded what. Would it be sufficient, or do you think we shouldn't publish the data anyway?

@avillela @danielgblanco @reese-lee What do you think about it? Did we get similar feedback in the past?

## Resources
<!-- Add links to the resources you created -->
- [CSV survey data](/end-user-surveys/japanese-community-survey/japanese-community-survey.csv)
- Survey report in `.pdf`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the PDF missing?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danielgblanco Yes, the analysis is not finished yet. I would add it later on. My intention here was to share out the data so if folks in the community are curious, they can do their own analysis.

However, before merging, we should for sure address Yoshi's comment above. I shared my perspective there. I would love to hear what you think about it.

@danielgblanco

Copy link
Copy Markdown
Contributor

I'm not a lawyer, but does any of the questions (or combination of them) fall under the regulation for PII? Just reading https://www.security.org/identity-theft/what-is-pii/ it doesn't seem like there is.

One thing we could do is ask for CNCF's opinion, as they have a service to run specific CNCF surveys (see https://contribute.cncf.io/resources/services/marketing#surveys) and could shed some light?

@danielgblanco

Copy link
Copy Markdown
Contributor

Maybe in the future what we could do is a have a disclaimer around the information collected, how it's not PII, and how we use the data.

@AndrejKiri

Copy link
Copy Markdown
Contributor Author

Just an update here: We discussed this multiple times at the SIG meetings. I will split the data into several smaller csv and will open a new PR where I will follow the convention to submit PRs from a fork rather than submitting directly to the source repository. 💪 Will close this PR once the new PR is openned.

@AndrejKiri
AndrejKiri marked this pull request as draft July 13, 2026 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants