-
Notifications
You must be signed in to change notification settings - Fork 628
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
Official status of metalsmith? #327
Comments
Hi Webketje, Thanks! As a longtime user of metalsmith and maintainer of a couple of metalsmith plugins I can say that there's plenty of active maintenance. As the ecosystem of metalsmith plugins isn't controlled by us the maintainers are in charge of the plugins. So for questions about individual plugins it's best to ask their maintainers directly. For some modules we're waiting on npm publishing rights from segment, which is why certain things haven't been released yet. So in general: yes, it's an actively maintained project. Help is always welcome of course, so if you see anything that you think should be improved feel free to open issues & pr's! I'll close this issue as I hope this answers your question, if not feel free to ask! |
I'm not sure if @woodyrew has publishing rights for the core package already. I think that that's the main holdup. |
Personally I think that metalsmith as a project would also look better if segment's metalsmith related packages were transferred to the metalsmith org. We've been maintaining them diligently so it's not like we'd have anything but the best intentions for the project. But it seems segment does not share that sentiment. |
Hi,
Enjoying the simplicity/ ease of use of this project. But what is its official status?
The 18 open pull requests and 39 issues as well as multiple npm "vulnerabilities" in metalsmith plugins doesn't give a great impression. Is it being maintained at all? I still see value in this project and find it the simplest of all static site builders (in fact I just migrated my Jekyll gh-pages to metalsmith).
See also #243 & #288
The text was updated successfully, but these errors were encountered: