Bullshit Issues

[kenwheeler]

This isn't an issue, it's a PSA.

This library has become wildly popular. It is in use on many high profile sites, as well as countless medium and smaller size sites.

That said, I take my responsibility to keep it stable very seriously. People are literally depending on it.

Very recently, I've been having a problem. People aren't taking the time to file proper issue reports and/or using the issues as a support forum.

You guys might be thinking, hey why is Ken being a dick lately? My intention isn't to be a dick at all, but I am missing important bugs and wasting time sorting through support requests and invalid/incomplete issue reports. And that's time I could be spending making Slick better.

I recently implemented a set of guidelines in the Contributing.markdown file. People need to follow them. If you are asking yourself, "why a JSFiddle demo?" Here's why:

• English isn't your strong point, and I can fully understand what you mean if I can see the code. Code is separate from language, and I can literally see what you mean.
• Your site's demo page isn't helpful. Most of the time it is something external causing the problem. On a JSFiddle demo, the issue can be isolated
• It saves me time. I don't have a lot of time. If you won't spend 5 minutes making a demo, how do you expect me to take an hour to try and fix it?

So please. Pretty fucking please with a cherry on top. File valid issues. If you see someone filing bullshit, call them on it.

[EnigmaSolved]

Very reasonable.

For others' reference, here's the Contributing page:
https://github.com/kenwheeler/slick/blob/master/CONTRIBUTING.markdown

One thought for consideration: I think that Feature Requests, if they're documented well (ie, not simply a request to "make Slick more awesome"), can often make sense to have as Github Issues because then you can easily tie them to Milestones. Additionally, sometimes there is an overlap of Feature Requests and Bug Reports, and it is nice to have the automatic cross-referencing of those two when everything is posted within Github. You lose some of that by moving Feature Requests to the subreddit. Those are just my thoughts though. This is your project, so I respect however you prefer to organize it. :)

[kenwheeler]

If a feature request has technical details and proposed implementation, it can absolutely live as an issue. But no "why doesn't slick do this" bugs.

[EnigmaSolved]

Great clarification!

[graphicgeek]

I've never wished Github had a thumbs up button until now.

[EnigmaSolved]

@graphicgeek Github actually does! Just type : and then you should see a list of several options. The thumbs up (or +1) is :+1: and looks like 👍. I discovered it ages ago because I like to do sideways smileys (which begin with a colon). :)

[deefour]

@kenwheeler I think you're doing a spectacular job sorting through the trash. You shouldn't have your time wasted with nonsense like #681.

I think strictness (closing out issues that don't conform to the contribution guidelines, maybe with some generic "thanks, but please read submission guidelines" message attached) is key to keeping your sanity.

For what it's worth, you come across genuinely interested in helping the users of your lib more than other maintainers of popular projects.

[MikeMcNuke]

Keep up the good work and if we have an issue > follow THIS guidelines! Thanks!

[influxweb]

👍