You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2018. It is now read-only.
Hi Adam, I asked the EmojiOne folk to take ownership of the project, we'll all stay on as contributors but I think it's a better home for the project :)
Wouldn't it be better to have an organization account then? 😄
What does this mean for the roadmap though? For example, the plan to support multiple emoji sets. I'm happy if only EmojiOne was supported because we planned to move to it anyway, but it would be good to know what the plan is.
The repo will be moved to the Ranks org, I believe, this is just temporary.
EmojiOne won't be changing much in terms of code, they don't have enough time to do it themselves. Any issues/features/bugfixes can still go ahead 😄
Hey @adam-lynch, we have no plans to change anything about emojify.js. I agree it would be nice to add support for Emojione (when/if we have time) but besides that we plan to let the contributors decide the best direction for it. 😄
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What's up with that? Why? How does it effect the module? Are there plans for changes to come?
The text was updated successfully, but these errors were encountered: