Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LOOKING FOR A NEW TEAM TO LEAD CRACO #415

Closed
patricklafrance opened this issue Apr 25, 2022 · 11 comments
Closed

LOOKING FOR A NEW TEAM TO LEAD CRACO #415

patricklafrance opened this issue Apr 25, 2022 · 11 comments

Comments

@patricklafrance
Copy link
Contributor

After a few years, GSoft decided to stop maintaining CRACO. I personnally have a new role and I don't have the time (or motivation) to contribute anymore. Since we are short staff, the management at GSoft won't assign anyone on this project.

Instead of killing the project, I would prefer to transfer the ownership to a new team since it's still widely used and the CRA 5 support is almost done.

If you are interested, manifest yourself in this issue.

@patricklafrance patricklafrance pinned this issue Apr 25, 2022
@Codex-
Copy link
Contributor

Codex- commented Apr 27, 2022

It's always hard when life and priorities change tracks, thanks for all the contributions!

Would you be looking for a group specifically or motivated individuals?

@patricklafrance
Copy link
Contributor Author

I am fine with both @Codex-

A team or a motivated individual who will be the new owner of the repo and take the lead.

@akachicon
Copy link

@patricklafrance
First of all, thanks for the great job during all these years! Can you please describe the scope of work you see necessary to release cra5 support?

@patricklafrance
Copy link
Contributor Author

patricklafrance commented Apr 27, 2022

Hey @akachicon

The utility functions have to be adapted to work with Webpack 5. I think it requires a full redesign.

Otherwise it's mostly about testing different use cases. I haven't test much CRACO with CRA5 so there might be other things that are broken like lesser used features.

From the comments in the issues there doesn't seem to have many problems thought.

@patricklafrance
Copy link
Contributor Author

@XzaR90 @mattsputnikdigital please create a new issue to talk about matters not related to finding new maintainers for craco.

Thank you

@dilanx
Copy link
Owner

dilanx commented May 30, 2022

Has a new maintainer been found, or not yet? If not, I would be interested in completing the upgrade to CRA5 and conducting internal testing throughout my team.

@patricklafrance
Copy link
Contributor Author

Hey @dilanx

Still no maintainers! Thanks for your interest in completing the upgrade to CRA5. Feel free to message me if you need me to add additional contributors of your team.

@dilanx
Copy link
Owner

dilanx commented May 31, 2022

Thanks for your response @patricklafrance

Is there a good method I could use to contact you directly? I would like to message you more about the possibility of maintaining this project.

@patricklafrance
Copy link
Contributor Author

@dilanx yes you can DM me on Twitter.

@dilanx
Copy link
Owner

dilanx commented May 31, 2022

Thanks, @patricklafrance. Unfortunately, it says that you have incoming DMs from anyone disabled, so it doesn't let me message you. You can message me on Twitter if you'd like.

@dilanx
Copy link
Owner

dilanx commented Jun 27, 2022

😄

@dilanx dilanx closed this as completed Jun 27, 2022
@dilanx dilanx unpinned this issue Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants