search

bazelruby / rules_ruby

Formerly canonical rules for ruby, that are about 2-3 years behind current Bazel. If they work for you great, but if not — please try the new rules ruby by Alex Radionov: https://github.com/bazel-contrib/rules_ruby
Apache License 2.0
99 stars 37 forks source link

State of this project #139

Open graywolf-at-work opened 1 year ago

graywolf-at-work commented 1 year ago

Hello,

I would like to inquire about the state of this project. Last release was in the fall of last year, and even current master does not seem to support ruby 3.1.2 released in April of this year. Please don't take this in a pushy way, I'm just curious before I import this into our workspace.

Thanks

kigster commented 1 year ago

Please check out the README. We are desperately looking for more maintainers. Want to help? Go for it.

kigster commented 1 year ago

As I have a regular job, my time for this project is now very sporadic. We very much welcome more contributors.

graywolf-at-work commented 1 year ago

Please check out the README.

I must admit I've overlooked it since it is right below table of content. And even reading it now it does not exactly sounds like "We are desperately looking for more maintainers".

Want to help? Go for it.

Yeah, will try. We have a lot of ruby code and it hardly makes sense to re-invent all that was already done here. I see this is licensed under Apache 2, which, while not my license of choice, I can live with.

I guess I will send few cleanup patches and then ask you to consider a new release (both to signal that this is alive and to get support for 3.1 into a release).

Is some contributor license agreement required for this project or submitting code under current license is enough? If yes, where could I find it (to get it cleared by our legal)?

Final question I have is regarding a code of conduct. Questions about it should be send to bazel-ruby@reinvent.one? Or is that address supposed to be used only for reporting violations? If yes, where would the appropriate venue be?

kigster commented 1 year ago

How about the discussions on GitHub?

kigster commented 1 year ago

Note: Apache 2 license was chosen I believe to match the Bazels license.

If Bazel changes theirs so will we.

I guess I will send few cleanup patches and then ask you to consider a new release (both to signal that this is alive and to get support for 3.1 into a release).

Once it's ready, of course.

Is some contributor license agreement required for this project or submitting code under current license is enough? If yes, where could I find it (to get it cleared by our legal)?

I'll look into adding that. Thanks for bringing it to my attention. You could help by letting us know what your legal considers a red flag vs not.

Final question I have is regarding a code of conduct. Questions about it should

be send to bazel-ruby@reinvent.one? Or is that address supposed to be used only for reporting violations? If yes, where would the appropriate venue be?

You can send it directly to me at kigster AT gmail.com.

Thanks.

kigster commented 1 year ago

https://github.com/bazelruby/rules_ruby/discussions/146