Forward Guidance: Reason Apollo Continued Development?

[Phylodome]

Does the Apollo team still plan to support ReasonML with a meaningful degree of resources moving forward?

I ask because it seems as if many of the issues are lying fallow, with little interaction and few updates on behalf of the maintainer, as well as the fact that reason-apollo increasingly lags behind react-apollo, and has still not formally incorporated support for hooks.

If reason-apollo was an experiment that the team does not plan to support moving forward, it would be helpful to know asap.

If it will be supported moving forward, it would be helpful to have some insight into the team's plan to track key updates, or perhaps to put out a request for help maintaining the project.

[MargaretKrutikova]

I was also curious about the future plans of reason-apollo. But if you want to use hooks, they are available in reason-apollo-hooks, with constant development and new features being added at least every week 😄

[Phylodome]

Thanks @MargaretKrutikova. I'm aware of the project, though I'm hesitant to add additional third party dependencies to supplement core features of the react spec. I think most would agree that support for such features belongs within the reason-apollo codebase, especially given ReasonReact's component-level adoption of the hooks paradigm.

Fundamentally, though, I'd just like an honest / realistic answer as to whether this project will receive development resources moving forward such that it makes sense to continue using Apollo in my ReasonML project / attempting to contribute fixes etc.

[Phylodome]

Would very much appreciate any thoughts / insights you might provide, @Gregoirevda.

[Gregoirevda]

Hi @Phylodome, that flat graph is when I got my first child. I'm currently working on another opensource project which takes much more time than expected. I am planning to implement hooks in reason-apollo, but not immediately...

[Phylodome]

Hey @Gregoirevda. First off, congrats on becoming a father!

Totally understand the time constraints. Perhaps you could clarify a few questions for us?

• Is this library formally part of Apollo? As in, are there any economic incentives aligned w/ the project's management? Asking because I'm curious if there are any metrics that the org uses to justify allocation of more resources to the project.

• Is there anything we can do to help move the project forward while you're focused elsewhere? Would anything make your work easier when you return? Are there specific challenges to the migration that you'd like the community to take a stab at? Low-hanging fruit those of us who aren't quite masters of Reason could help with?

I know that it's a bit of work to go through these questions and perhaps even more to begin formally bringing others into the fold of maintenance and development, but it seems like there are at least a few of us who'd be willing to help carry some of the load in service of making progress here.

If that sounds good to you, I'd love to take whatever first steps you feel are appropriate. If not, I also understand.

Congrats again.

[Gregoirevda]

Thank you @Phylodome!

It is formally part of Apollo. I created this project and asked Apollo employees to add it in their github org so we can have an official repo and it could get more traction for opensource development.

Everyone should be able to contribute, that's also the purpose of it being under Apollo org. Would be nice if @fakenickels could be granted access here to push things forward while I'm working on something else. If reason-apollo-hooks are merged here it be a good progress already

[Phylodome]

Wonderful. Who would we need to ask about adding @fakenickels as a project admin? I 100% agree that incorporating reason-apollo-hooks into reason-apollo would be a great first step.

@fakenickels, is that something you'd be willing to entertain?