-
Notifications
You must be signed in to change notification settings - Fork 442
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
A call for maintainers #353
Comments
To be honest, my plans consisted mostly of bug fixes and updating to jquery 2. I did want to look into possibly showing the images in a more general way. I noticed from my last experience with superslides that images with a particular resolution will be cut off around the borders which is unwanted when displaying images of webpages for example (toolbars and sidebars get cut off). Other than that, I'd like to see if the other guys have more vision for this library than I do. If so, I'm happy to be a contributor than a maintainer :) |
considering this has been used in a wordpress plugin it's very important this is maintained and continued to have contributions too as the plugin is quite popular. The sad thing is the maintainer of the plugin for wordpress that has leveraged this code base has also gone MIA. |
I'm happy to be part of beta testing branches and generally chat & contribute to the community - not sure if my skill set is up to the full rewrite but am happy to be a contributor to sections of the code. I'm quite invested into SS slider. I think abandoning support for legacy browsers or at least versioning the development to mark the end of support for these should be the first project. I don't think feature additions should be part of this phase of transiting to a new community of support ~ until it's clear that the maintainers are capable and present with developing features PLUS I think that with 20 or so other sliders in open source with their different takes on "slider" - it may be counter-productive to drift from the clear and simple purpose of a lean full screen slider. After closing legacy support . I'm pitching for full mobile compatibility ... |
Hi ... can we schedule a todo list with some responsibilities? |
I am used this plugin on all most each my website. so sadly, it stop updated from last 3 years. |
None of you actually been set as a maintainer yet by @nicinabox ? Also I'd rather like to join. |
What's the current state of this issue and repo? |
@CatinhoCR It's dead. Quality project for the time at which it was created, but one should look elsewhere for a proper solution now. Many thanks to the creator for putting this out here for the community and maintaining it for as long as he did though:) |
@nicinabox - any chance of mentioning that the project is currently unmaintained here: http://archive.nicinabox.com/superslides/#1 The page above is indexed high on google search and I spent quite a lot of time on it before realising it is now unmaintained. |
@isedwards Sorry for the confusion, I didn't even realize it was well indexed. I've added a prominent message there now. |
A few lovely folks from the community (@jamesalbert, @nmai, @ianhobbs) have contacted me to offer their help in taking over this project. I realized that these discussions were difficult to have on their own and in silos. Instead, I wanted to bring these discussions forward publicly (this is an OSS project after all) so anyone can offer input and assistance.
When superslides was created back in 2012 (4 years ago!) there was a very different browser and device landscape. Superslides was designed to bring a performant, fullscreen carousel to IE7 and many of the decisions that were made were based on that support floor. The mobile web wasn't taken as seriously then.
In 2016 things are a bit different. Microsoft has sunset nearly all IE versions. Mobile and touch-enabled devices are more prominent than they ever have been. And while the internet has continued to rapidly change, superslides was neglected as I moved into other jobs and focused on different problems. Superslides hasn't seen an update in 2 years yet continues to gain stars daily while falling sadly behind in compatibility.
I often think about the future of this project. I'd like to see it carry on with future-facing features, but I no longer have time to maintain it and its current feature set is minimally relevant to problems we have today.
So, future maintainers and users of the world:
The text was updated successfully, but these errors were encountered: