Open kenwheeler opened 8 years ago
I am open to culling the issues, etc... I am currently using slick in a project, and I have encountered some of the complexity issues, as well as needs that I have hacked a solution for. So it behooves me to pay attention to the project.
@Mcashley email me at ken@outlook.com
I'm down to help. Profoundly appreciate your efforts along with @simeydotme and @ahmadalfy over the years (also emailed).
@mcashley @leggomuhgreggo :+1:
I'll be available to help clean up any issues with this project. Whether it's cleaning up the issue list, or knocking out some of the issues themselves. I can be contacted at slickcontribute@konigsmark.us
firstly, thanks for the work you guys've done so far. use this on a personal project & have since introduced it to a project at work. so definitely up for helping you out with issues. will drop an email.
At work I use your awesome slider on now 9 sides in many different situations. Maybe you have noticed that I try to give you a little bit back. You've got an email :smile:
@kenwheeler dropped you email but didn't have response - do you still need contributors?
How's this closed? o.0... I'm seeing 332 issues opened and 115 PRs... that's A LOT... =/ is this project discontinued? If it is, please, someone must warn it somewhere...
This issue isn't closed.
@leggomuhgreggo I may have seen it closed, seriously. Is it possible that it got opened after I've commented? =P Anyway, it's open now, thanks.
We are in year 2018 now. Is this project still maintained by anybody? It feels like nobody is looking into the issues and pull requests. I see a lot of pull requests that could easily be answered or merged.
@kenwheeler I sent you an email. I would be happy to help you.
Probably not much. I was also interest in to be a more active contributor in the past, I've also got in touch with @kenwheeler but later on things have happened and I couldn't assume this. I'm still unavailable right now, if something changes, I'll got in touch with you guys again. Please keep the project, slick is still one of the best carousels out there. I'm unsubscribing this issue.
CALL FOR CONTRIBUTORS
I'm reaching out because I want to fix Slick. I mean, generally speaking, the happy path of slick is stable, and has been. However, there are indeed some bugs when getting fancy with the options, and that shouldn't be the case.
So I show up to github issues in the morning, and say "Hey man, what can I fix today?". I look around and I have a real hard time determining:
I have super limited time to work on this, and I want to make the time I do have count. I'm reaching out because I need some help with issue management. Are there any fine folks who would like to go through the current issues list and do the following:
If anyone is up for the task, it would be amazing. People often ask if they can donate, and no I don't want money. Instead, help me make slick continue to be the best carousel out there.
I have a working 2.0 branch here https://github.com/kenwheeler/slick/tree/2.0 if anyone hasn't seen it, where I'm introducing some really cool stuff that will make slick more reliable. I'm setting the stage for CI integration to make pull requests easily verifiable, and adding modern tooling that brings this project up to current standards.
Also, as an aside, when I wrote this plugin I was writing carousels from scratch all the time. I haven't even implemented a carousel in over a year. I've been in React-land and more recently writing native applications in React Native full time. This puts me a bit out of touch with modern carousel needs. Please comment and let me know if I'm overlooking some cool new thing that I should be supporting but I'm not.
As always, thank you rascals so much for using this plugin, and I deeply apologize if I haven't responded to a PR or issue in a timely fashion. There are a ton of them and I just don't have the bandwidth and I feel terrible. Lets fix that.
Big shout out to @simeydotme and @ahmadalfy for helping me so far, you should all buy them a beer for being amazing.