search

rubygems / rfcs

RubyGems + Bundler RFCs
45 stars 40 forks source link

Add `bundle report-issue` #5

Closed colby-swandale closed 5 years ago

colby-swandale commented 7 years ago

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

hmistry commented 7 years ago

Nice rendered view of above RFC

hmistry commented 7 years ago

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 commented 7 years ago

@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 commented 6 years ago

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