Team Feedback/Transparency #9104
Replies: 2 comments 1 reply
-
|
Hi @eddiemonge, I am an very occasional maintainer of CRA so my answer only represents my view but there's my two cents: The CRA core team is really small, basically @iansu / @ianschmitz / @mrmckeb, who do all of the heavy lifting along with the few other current and past maintainers and large amounts of community members (many of whom work on other large projects like Jest, Babel, TypeScript and service workers). It should be noted that none of them work at Facebook or work on Create-React-App full time so I wouldn't consider CRA being a "very much Facebook project". The CRA team meets every other wednesday, which is an open call and the meeting notes and decisions are visible in https://github.com/iansu/create-react-app-meta/issues. We also have a Dischord server for discussion at https://discord.gg/9zN9uY. I agree that the governance model could be outlined better in our CONTRIBUTING document. That said, we are still amid of a global COVID-19 pandemic and in the middle of an important fight against inequality not only in the US, but across the world so we can only ask for patience for receiving new features and bug fixes and suggest to #TakeAction instead, joining forces for justice. #blacklivesmatter |
Beta Was this translation helpful? Give feedback.
-
|
I must say that I do a lot less than some of the other contributors to Create React App, and I wish I could do more - but as @petetnt says, we're volunteers and the time I spend on Create React App is 100% my own time. I'm also a maintainer of Storybook, and as part of my work there I try to ensure great out-of-the-box experiences with Create React App. Open source can in some cases literally just mean that the source code is open to the public, but that's not what's happening here. We listen to the community, and very regularly discuss what we can do to meet community needs and wants. We also revisit those decisions regularly. Again, as @petetnt points out, our decisions often come down to what we can support... not what we want to support. |
Beta Was this translation helpful? Give feedback.
-
Feedback
Those things should be moved here to make it more transparent. Other than getting posted here, how would anyone have known about the meetings or the resulting notes? When are the next ones scheduled as a I would like and didn't get to for the last one. As for the review notes, have those been turned into issues so people in the community can help with them?
Can that be moved here to discussions? (also the link expired and thats one of the problems with Discord). Other things that could be improved:
I am highly appreciative of all the work that has been done here. Having been part of a number of OSS projects in the past (jQuery, Yeoman, UI-Router, ...), I know how difficult doing volunteer work is. Between the day job, family life and other hobbies and projects, finding time to devote to one project is a challenge. I've been trying to help with the issues but its hard without having the power to close issues or tag them or anything else. I will continue to do my best to help the project as I have gotten so much value from it. TL;DR:I would like to volunteer to help and I feel other people may as well but there doesn't seem to be a good path to do so. How can we help? |
Beta Was this translation helpful? Give feedback.
-
From the community perspective, its been going on almost 3 months with out a release and without feedback as to why. I think having a blog at https://create-react-app.dev/ with some updates would be beneficial.
Another thing is Issues and Pull Requests seem out of control. Perhaps asking for community volunteers to help triage would be good but I don't know how that would work since this is still very much a Facebook project and not really an OSS community project.
I think that last point is my current issue, the lack of transparency on who this project is supposed to be for and how controls it.
Beta Was this translation helpful? Give feedback.
All reactions