Hi @cyclejs-community/contributors 😄
I hope y'all are doing well. It's been a while since we've had any community-wide communication go out, but in the meantime things have been ticking along.
I'm reaching out to you because we're looking for someone to step up as a maintainer for redux-cycles.
For those who aren't familiar, redux-cycles is a cool piece of technology that acts as a bridge between redux and cycle, and in my opinion is one of the most elegant solutions for managing asynchronous effects for apps that use redux. It's also one of the most starred pieces of tech in the Cycle.js ecosystem!
redux-cycles was originally created by @nickbalestra and @lmatteis, who did a fantastic job launching the project, but it currently has nobody actively working on it.
A major part of the reason @TylorS and I created this community is because we believe that contributors should be able to work on a project without feeling an obligation to stick around forever, or guilt if they need to walk away. We want working on open source Cycle projects to be a great experience, and in order to do that we need to have each others backs.
To that end, I'm hoping to find one or several people who are interested in doing a bit of maintenance work on redux-cycles. There are several low hanging fruit issues that would go a long way, like updating the dependencies, updating the README and triaging the existing issues.
If you want to be more involved in open source or the Cycle.js community, this is a great opportunity. By putting your hand up, there's no obligation to have a long term commitment to working on the project. Any work that you can find time to do is greatly valued.
I hope that someone is willing to step up and do a little bit of work here, as it would be a shame for such a great project to be deprecated when it just needs a little bit of love.
I'm happy to provide guidance and support for anyone who wants to do some maintenance. I'll give you push access to the repo, arrange for you to have publish access on npm, and field any questions you have. If you're keen, please comment in here or get in touch with me on Gitter. Also feel free to post any questions you have in here!
Hi @cyclejs-community/contributors 😄
I hope y'all are doing well. It's been a while since we've had any community-wide communication go out, but in the meantime things have been ticking along.
I'm reaching out to you because we're looking for someone to step up as a maintainer for redux-cycles.
For those who aren't familiar,
redux-cyclesis a cool piece of technology that acts as a bridge betweenreduxandcycle, and in my opinion is one of the most elegant solutions for managing asynchronous effects for apps that useredux. It's also one of the most starred pieces of tech in the Cycle.js ecosystem!redux-cycleswas originally created by @nickbalestra and @lmatteis, who did a fantastic job launching the project, but it currently has nobody actively working on it.A major part of the reason @TylorS and I created this community is because we believe that contributors should be able to work on a project without feeling an obligation to stick around forever, or guilt if they need to walk away. We want working on open source Cycle projects to be a great experience, and in order to do that we need to have each others backs.
To that end, I'm hoping to find one or several people who are interested in doing a bit of maintenance work on
redux-cycles. There are several low hanging fruit issues that would go a long way, like updating the dependencies, updating the README and triaging the existing issues.If you want to be more involved in open source or the Cycle.js community, this is a great opportunity. By putting your hand up, there's no obligation to have a long term commitment to working on the project. Any work that you can find time to do is greatly valued.
I hope that someone is willing to step up and do a little bit of work here, as it would be a shame for such a great project to be deprecated when it just needs a little bit of love.
I'm happy to provide guidance and support for anyone who wants to do some maintenance. I'll give you push access to the repo, arrange for you to have publish access on npm, and field any questions you have. If you're keen, please comment in here or get in touch with me on Gitter. Also feel free to post any questions you have in here!