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

Add bundle report-issue #5

Closed

Conversation

colby-swandale
Copy link
Member

This is a copy of @indirect's proposal from bundler/bunder#4925

@colby-swandale colby-swandale changed the title Create 0002-bundler-report-issue.md bundler report-issue Mar 4, 2017
@hmistry
Copy link
Contributor

hmistry commented Mar 10, 2017

@hmistry
Copy link
Contributor

hmistry commented Mar 10, 2017

I really like the overall concept. There's a lot of info collected. A couple of knee-jerk reactions are:

  1. Since we know the type of error, can we only collect what's necessary? In other words, don't collect anything that's not remotely needed at all.
  2. I presume there can be privacy and security concerns of the user. For example: the user paths in the shell can give out more clues about a github user, i.e. a different internet username. For companies, this can be a potential leak of their entire stack for outsiders to see - thinking of Gemfile.lock.
  3. Will there be an interface for a user to preview and edit/approve before submission? As a user, I want this control.

@colby-swandale
Copy link
Member Author

colby-swandale commented Mar 12, 2017

@indirect, quick thought, don't use Gists, unlike issues, gists can be deleted by the user as well when the user deletes their account.

@indirect
Copy link
Member

indirect commented Jul 1, 2018

Final comment period starts here! Please give us your feedback by July 7.

@indirect indirect changed the title bundler report-issue Add bundle report-issue Jul 1, 2018
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.

3 participants