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

Abandoned? #321

Closed
vinnyrose opened this issue Sep 23, 2016 · 5 comments
Closed

Abandoned? #321

vinnyrose opened this issue Sep 23, 2016 · 5 comments

Comments

@vinnyrose
Copy link

@kaizau @endtwist,

This library appears to be abandoned. Can you confirm if you are no longer maintaining this library? Is there a possibility of handing over to new maintainers?

Best

@kaizau
Copy link
Member

kaizau commented Sep 26, 2016

Sadly accurate. Can't speak for @endtwist but it's not a personal priority at the moment. Considering the sheer number of PRs and forks here, that's not an ideal state of affairs.

@endtwist How's your bandwidth these days? Perhaps we draft up a transition plan?

@kaizau
Copy link
Member

kaizau commented Sep 26, 2016

The state of frontend tooling has changed quite a bit since we started. Even in 2013, we considered making a Node conversion. And if we started fresh in 2016, there's no chance this wouldn't be a npm module.

So my inclination would actually be to rapidly sunset the current version of FontCustom and replace it with a rewrite. A final PR / bugfixes release would be ideal for those who are committed to ruby.

@endtwist
Copy link
Member

endtwist commented Sep 27, 2016

@kaizau Yes, same here. It's not been a priority and I've begun to stray away from using fonts as a storage/display method for icons (switching over to, often, SVG's use).

That being said, it's clear that Font Custom is still valued greatly (with 20 PRs and 82 issues open).

@kaizau I think it would be worthwhile to draft up a plan to add some core contributors, sunset the gem, and make a plan for a Node-based implementation. I can make some time for us to figure this out.

@jpotterm
Copy link

jpotterm commented Sep 27, 2016

In case it helps, there is a Node project grunt-webfont that looks like it may have a similar implementation to FontCustom (it has a FontForge backend). Maybe you could combine forces with them?

Personally I think it'd be better to have one NPM module with all the business logic and then have other NPM modules that are thin wrappers for command line, Grunt, Gulp, etc.

@JakeBeresford
Copy link
Collaborator

I will be working on resolving open issues & merging PRs, then releasing a new major in the coming weeks.

Ongoing support will be limited, and I would recommend using SVG rather than icon fonts if possible. I understand that others may have similar constraints as I do, which is my motivation to release an update to this project.

Thanks for your patience.

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

No branches or pull requests

5 participants