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 Contributors #140

Open
wbuchwalter opened this issue Jul 20, 2017 · 12 comments
Open

Looking for Contributors #140

wbuchwalter opened this issue Jul 20, 2017 · 12 comments

Comments

@wbuchwalter
Copy link
Member

As you may have noticed, this repo is not maintained since a while.
Since I am not using Angular nor Redux anymore, and as I am working on other stuffs I don't have the time/capacity to maintain it anymore.

If you are interested in being a contributor of ng-redux, please let me know!

@AntJanus
Copy link
Collaborator

I'm definitely interested in helping out! I'm using this lib in production at my company. We're still using AngularJS day-to-day and Redux as well so I've got a pretty good handle on both sides.

I wouldn't mind taking over and spearheading the project.

@wbuchwalter
Copy link
Member Author

Awesome :)
I have added you as a contributor.
What's your npm username?

@AntJanus
Copy link
Collaborator

same as here: antjanus

Thanks!

@wbuchwalter
Copy link
Member Author

You're good to go!
Leaving this issue open as having 1 our 2 more contributors wouldn't hurt.

@AntJanus
Copy link
Collaborator

Awesome! Let me run a few things by you real quick before I take over:

  1. Are you cool with me adding new contributors?
  2. I'm considering dropping bower support in the next major release since bower is officially closing down.
  3. I'd like to create a 4.0.0 version and add proper changelog/release cycle using standard-version, clean up a few things, and drop that bower support.
  4. and I'd like to redo the logic so that an instance of a Redux store can be passed into ng-redux at config time (whilst still keeping the createStoreWith functionality).

I'm going to open up issues for 2-4, open it up for brief discussion, and keep going.

@wbuchwalter
Copy link
Member Author

👍
You can add contributor yes.
All your other point sounds good to me as long as everything is done following SemVer.

@deini
Copy link
Collaborator

deini commented Jul 26, 2017

Also using this in prod, would love to help out!

@AntJanus
Copy link
Collaborator

Hey, just wanted to update. I created an issue #142 with my plan for the future of ng-redux. It's mostly just bunch of cleanups, testing PRs and merging them in, and finally, adding provideStore functionality.

@HunterEl
Copy link
Collaborator

I am gearing up to use this in production as well and would love to help out where I can!

@AustinMCrane
Copy link

I would like to contribute as well.

@AntJanus
Copy link
Collaborator

AntJanus commented Jan 4, 2018

@AustinMCrane awesome! You're welcome to pick up any of the bugs or check out our "roadmap"-ish issue here: #164

If you have any ideas on future features, you can post them there. There's also a feature that no one has tackled yet that's slated for 4.1.0 release: #136

@BrkCoder
Copy link

I would like to contribute too, although I am using ngrx for most of my work and projects.

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

6 participants