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

Should the Ruby bindings live in an external repo? #1200

Open
bendk opened this issue Mar 31, 2022 · 2 comments
Open

Should the Ruby bindings live in an external repo? #1200

bendk opened this issue Mar 31, 2022 · 2 comments

Comments

@bendk
Copy link
Contributor

bendk commented Mar 31, 2022

If/when the separate bindings PR lands, we should consider moving uniffi-bindgen-ruby to a separate repo. Reasons for this:

  • We're not really supporting it as an organization and we don't want to imply that we will
  • The docs make a distinction between "standard" bindings generators and "external" ones. It feels right to me that the standard languages are Kotlin, Swift, and Python.

┆Issue is synchronized with this Jira Task
┆friendlyId: UNIFFI-149

@mhammond
Copy link
Member

It's worth noting that Mozilla is also looking at having gecko-js bindings live externally, and as soon as it is possible, we will probably reject requests to add more bindings to this repo should someone come along and ask - so Ruby isn't being singled out here. @saks, and the author of the Ruby bindings, how would you feel about this?

@saks
Copy link
Contributor

saks commented Mar 31, 2022

I'm certainly OK with it 🙂 I'm grateful for making a compromise and adding ruby while external bindings weren't possible. Please let me know if you need my help externalizing ruby bindings @mhammond

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

3 participants