4 ms·

Another unfortunate example of the necessities of contributor agreements.

• ansible 13y ago
  Another unfortunate example of the necessities of contributor agreements. Uh, no. This is an example of needing to take care, and fully understand what is going into each commit. The OP got a little sloppy (which happens), and is now praying the price for it. Hopefully it can all get resolved soon and everyone can get back to work.
  • jthol 13y ago
    Whoever gave him the file might also share some of the blame.
    • PeterisP 13y ago
      There is a big difference in submitting an example that provokes a bug, and publishing that example. If an audio player crashes when opening a file with the latest Miley Cyrus hit, then that specific file is useful to reproduce the bug, but it doesn't mean that it can be redistributed further. The same is with any personally identifiable information - if you have obtained a list of people names/emails/adresses, it doesn't automatically mean that it's okay for you to publish that list.
  • StavrosK 13y ago
    > Hopefully it can all get resolved soon and everyone can get back to work. If we wanted everyone to get back to work, we wouldn't be browsing HN.
• nness 13y ago
  I would assume contributor agreements would be very important for issues like this if they were ever to go to court. But I doubt it would have been acknowledged by GitHub in their response to the complaint.