Meeting notes for Sep 2016.

[koba04]

This meeting notes haven't been updated since August. Will you update meeting notes in the future? Or weren't there any meetings?

[outdooricon]

Also wondering, especially since @gaearon got back from vacation on sept 20 according to the final meeting notes :)

[browniefed]

https://twitter.com/dan_abramov/status/787636786013044736 there is your answer

[gaearon]

Yea, sorry about this. I remember about the notes.

We had different people go on vacations during August and September so the meetings were much shorter and often included two or three people.

Even so, most of them were concerned with React usage internally at Facebook, and associated work. As you might know, React team is not just responsible for developing React, but also for helping the product teams that use React (both for publicly known products and products we can’t talk about).

A summary to the best of my knowledge:

• Paul @zpao is transitioning out of the team (he’s been on it for a long time, and looks forward to working on something new).
• Christopher @vjeux has also left the team and switched to working on Nuclide.
• Ben @spicyj has been working on different issues related to React in Facebook products and reviewing Sebastian's Fiber pull requests.
• Kevin @lacker leads the new documentation effort.
• Sebastian @sebmarkbage has been busy with TC39, later returned to work on Fiber and spent a bulk of these two months fixing subtle issues and implementing child reconciliation.
• Andrew @acdlite has contributed to Fiber and new documentation. He's new to the team, but he's still in Bootcamp so he can't dedicate full time to it yet.
• I was on vacation, then working on Create React App, then working on new React docs (including new "Contributing" section and a bunch of new guides), then working on better support for error boundaries.

We also spent a bit of time debating what to focus on, as the team is pulled in many different directions. We decided to focus on shipping Fiber, and indeed there is a lot of work to do there and not as much to discuss.

I'll publish the next meeting note as soon as we have something reasonable to share.

[outdooricon]

Thanks for the update @gaearon!

[koba04]

@gaearon Thank you for your response!

Christopher @vjeux has also left the team and switched to working on Nuclide.

@vjeux was working on to add Flow types into React. Does anyone take over it?

We also spent a bit of time debating what to focus on, as the team is pulled in many different directions. We decided to focus on shipping Fiber, and indeed there is a lot of work to do there and not as much to discuss.

Awesome! I'm very excited about Fiber!

[aweary]

Best of luck @vjeux with Nuclide and @zpao with whatever you end up doing 😄

[borisyankov]

@gaeron Do you think community contributions to the work on Fiber are realistic at this early stage? Anything an ambitious contributor could take on?

[gaearon]

@vjeux was working on to add Flow types into React. Does anyone take over it?

We use Flow types in all Fiber code, and we accept contributions (like this one by @flarnie!) that Flow-ify other places in the codebase.

Flow-ifying the old reconciler is not as important because we want to eventually throw it away.

Do you think community contributions to the work on Fiber are realistic at this early stage? Anything an ambitious contributor could take on?

It’s hard to say. I consider myself an ambitious contributor and I’m still struggling quite a bit. I am building React Fiber Debugger (temporary URL) for myself to better understand how Fiber works—I’ll try to check it in soon for other folks.

We collected all work on Fiber in https://github.com/facebook/react/issues/7925. Some of the "Low Pri" issues at the bottom should be doable but might take a lot of work. Others are important too but it’s likely we might get to some of them first. In general, we encourage you to look at those issues and give them a try, but unfortunately this time we can’t give you any guarantees that we would wait for you because time is absolutely essential and we can’t afford to wait for anyone. Still, feel free to take anything from #7925 that doesn’t have somebody’s name on it, and submit a PR, although again, if we don’t agree with the approach, we likely won’t be able to spend a lot of time helping you get on track. Sorry about this!

[koba04]

Thanks! I'll close this.

[gaearon]

Let's keep it open for visibility until I publish new notes.

[gaearon]

Added notes for October. Closing.

[koba04]

Thank you for your hard work!! It's very helpful for React community!!