3 ms·

It's easily agreeable that attribution should have been given before publishing, but the level of hysteria in this post is excessive. The author of the fork im

by tomxor 5y ago

It's easily agreeable that attribution should have been given before publishing, but the level of hysteria in this post is excessive. The author of the fork immediately complied and had likely just made a mistake in a hastily published fork. I suspect the original author was more frustrated with the fork existing.

ctvo 5y ago
The original author mentioned reaching out privately. https://twitter.com/DerianAndre/status/1441851684095811585 https://twitter.com/DerianAndre/status/1441851684095811585 As a "prolific and known" open source personality you'd think they'd be more careful? Their attitude since then has left a lot to be desired.
- tomxor 5y ago
  > Did you talk with him before all of this? > Yes This is a pretty terse reply, talk with him when... a month ago, or yesterday. I don't care for either side but I'm suspicious when people reach for twitter shame - it's more plausible that insta-pressure just forced him to drop his daily activities and immediately make changes to save face in public. > Their attitude since then has left a lot to be desired. What are you referring to? (not rhetoric)
  - jorgebucaran 5y ago
    I reached out to him when I could've filed a takedown notice instead. Later, after the tweets, I even asked him to shake hands on the whole thing[1][2][3], but he was already sunk-cost-mode on and determined to die on a stupid hill. Only because I called him out is that we were able to had my git history restored and copyright attributed. > Their attitude since then has left a lot to be desired. That refers to the forker's attitude following the tweets[4][5]. [1]: https://github.com/ai/nanocolors/pull/14#issuecomment-927757741 https://github.com/ai/nanocolors/pull/14#issuecomment-927757... [2]: https://user-images.githubusercontent.com/56996/135221889-529be6d3-066e-46db-b890-43c9b1423baf.jpg https://user-images.githubusercontent.com/56996/135221889-52... [3]: https://twitter.com/jorgebucaran/status/1442055448899641348 https://twitter.com/jorgebucaran/status/1442055448899641348 [4]: https://news.ycombinator.com/item?id=28661094 https://news.ycombinator.com/item?id=28661094 [5]: https://github.com/jorgebucaran/colorette/issues/78 https://github.com/jorgebucaran/colorette/issues/78

by tomxor 5y ago

ctvo 5y ago

The original author mentioned reaching out privately. https://twitter.com/DerianAndre/status/1441851684095811585 https://twitter.com/DerianAndre/status/1441851684095811585 As a "prolific and known" open source personality you'd think they'd be more careful? Their attitude since then has left a lot to be desired.

tomxor 5y ago
> Did you talk with him before all of this? > Yes This is a pretty terse reply, talk with him when... a month ago, or yesterday. I don't care for either side but I'm suspicious when people reach for twitter shame - it's more plausible that insta-pressure just forced him to drop his daily activities and immediately make changes to save face in public. > Their attitude since then has left a lot to be desired. What are you referring to? (not rhetoric)
- jorgebucaran 5y ago
  I reached out to him when I could've filed a takedown notice instead. Later, after the tweets, I even asked him to shake hands on the whole thing[1][2][3], but he was already sunk-cost-mode on and determined to die on a stupid hill. Only because I called him out is that we were able to had my git history restored and copyright attributed. > Their attitude since then has left a lot to be desired. That refers to the forker's attitude following the tweets[4][5]. [1]: https://github.com/ai/nanocolors/pull/14#issuecomment-927757741 https://github.com/ai/nanocolors/pull/14#issuecomment-927757... [2]: https://user-images.githubusercontent.com/56996/135221889-529be6d3-066e-46db-b890-43c9b1423baf.jpg https://user-images.githubusercontent.com/56996/135221889-52... [3]: https://twitter.com/jorgebucaran/status/1442055448899641348 https://twitter.com/jorgebucaran/status/1442055448899641348 [4]: https://news.ycombinator.com/item?id=28661094 https://news.ycombinator.com/item?id=28661094 [5]: https://github.com/jorgebucaran/colorette/issues/78 https://github.com/jorgebucaran/colorette/issues/78