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

Future of Less Hat #162

Open
petrbrzek opened this issue Jul 20, 2015 · 3 comments
Open

Future of Less Hat #162

petrbrzek opened this issue Jul 20, 2015 · 3 comments

Comments

@petrbrzek
Copy link
Member

Hello everyone,

It’s fantastic that a lot of dev people like and use LessHat in their projects. When I developed this library three years ago, there wasn't any universal Less mixin library, autoprefixer didn’t exist yet, so I created Less Hat to solve the pain with vendor prefixes. But the time has changed and now there are better solutions in my opinion. There is autoprefixer plugin for less (https://github.com/less/less-plugin-autoprefix), PostCSS (https://github.com/postcss/postcss) and others..

I’m now focusing my effort on developing Avocode (http://avocode.com/), so I don’t have enough time to continue developing Less Hat. I can fix some of the reported bugs, merge pull requests, but then I won’t develop Less Hat further. I’m open to hand Less Hat to the new maintainer. So if anyone is interested in developing Less Hat just send a message here.

@bennycode
Copy link
Contributor

Hey Petr,

Thank you for your feedback and clarification. I used Less Hat in a couple of web projects (most recently for developing Wire for Web) and it has always been a good companion. Therefore I would like to thank you. As a developer I can understand very well that you have to focus and I will definitely have a look at Avocode. 😃 As a Less Hat successor PostCSS seems to be a good choice but time will tell...

So Long, and Thanks For All the Fish

Benny

@MarkRabey
Copy link

While I haven't used Lesshat for a project yet, it looks great, and I came here with the intention of both using it, and contributing to it. I'm uncertain of the time commitment required to maintain such a project, so I may not be the best choice, however I am willing to consider it. Or, at the very least, work with whoever does take it on.

I can certainly try maintaining it though!

@mboudreau
Copy link
Collaborator

I wouldn't mind contributing/taking it over. I think there's a lot of community involvement and all that's needed is a better automated system release new versions. I already have that working with travis, but it would need some update on the dev stack dependency. I've already been added as a contributor, so I'm hoping I can start pulling some of these changes people has contributed and release them straight away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants