3 ms·
This. I see that the repo is under the developer’s account so clearly this is not Facebook’s actions. If the developer worked at a random unknown company nobod
by whoisjuan 6y ago
This. I see that the repo is under the developer’s account so clearly this is not Facebook’s actions.
If the developer worked at a random unknown company nobody would be paying attention to this. Perhaps the original author wouldn’t have posted his (rightful) claim.
- dessant 6y agoThe app was swapped during an internal review process at Facebook. https://github.com/facebook/react-native/commit/f9c2157141b8fcddcb2d2c576c952f2ce7daedda https://github.com/facebook/react-native/commit/f9c2157141b8...
- whoisjuan 6y agoSwapped by the author himself. This is definitely a gray area. How much does a reviewer need to dig into the license implications of swapping a dependency? You’re totally in your right to demand license compliance of course. I’m just saying that is hard to blame it as a concerted effort by several individuals. Doesn’t seem to be the case here.
- thih9 6y agoHow is that any different from a regular github fork? Note that the repo name also stays the same when a github project is forked. True, github repos are namespaced and github marketplace isn’t. Perhaps this is the core of the issue. Then again, this looks like an issue of github marketplace. In this light FB’s actions seem unrelated.