News for hackers. Stuff that matters.
Re:State of React Native 2018 by shaneos on Friday June 15, 2018 @01:51AM (#17317776)
The response that I've gotten, after complaining repeatedly, is that the team simply has no time to look at any externally reported issues, and that it's essentially a waste of time opening an issue.

This makes me very sad (as an ex-FBer especially), I wish that FB would just add another 3 or 4 engineers to the team with the explicit goal of giving them the bandwidth to be good open source stewards. I'm sure the FB engineers don't like having to ignore the community, but they do as a matter of policy.

Re:State of React Native 2018 by ascorbic on Friday June 15, 2018 @03:34PM (#17322810)
They could learn a lot from Microsoft. VS Code, Typescript and related projects are a shining example of how to handle issues on open source projects. In fact, considering what heavy users they are of React Native, maybe Microsoft could be taking a more active role in the core project.
Re:State of React Native 2018 by olfactory on Friday June 15, 2018 @11:39AM (#17320544)
This is a great point. There have been a few issues that I've followed only to find that eventually the entire thread on Github with tons of example cases of the bug gets "closed for inactivity" because nobody from Facebook would respond to it.
Re:State of React Native 2018 by ricardobeat on Friday June 15, 2018 @02:40PM (#17322351)
They don't need to add more engineers - as an open-source project, all they should have to do is put one person to manage the community, encourage and vet new contributors. But that would mean losing some control.