Still active? #3
Comments
|
I have no idea if anyone is using this gem. https://rubygems.org/gems/method_object doesn't seem to say. I'm not actively developing it anymore. I'm also not sure how to give you ownership of the gem name. Happy to give it up. |
|
Hi Jared! Super, thank you! I took over and gave away a few gems before, it's quite simple. First, you use the following command to add our team as co-owner of your gem:
That gives us the right to remove your ownership of the gem. (You could remove yourself, too, but I don't recommend that to avoid mistakes). For whomever was using We can, however, publish new releases with our code. That would be version Again, thank you very much! PS: I will redact this public Github post so that it does not contain our email address any more. I assume you will receive an email notification of this post, there you can see the email address. |
|
can you please give me the link to the github repo you intend to publish
from so I might update the README on this repo?
thanks
…On Tue, Sep 3, 2019 at 11:53 PM mmzoo ***@***.***> wrote:
Hi Jared! Super, thank you!
I took over and gave away a few gems before, it's quite simple. First, you
use the following command to add our team as co-owner of your gem:
gem owner --add ***@***.*** method_object
That gives us the right to remove your ownership of the gem. (You could
remove yourself, too, but I don't recommend that to avoid mistakes).
For whomever was using method_object up to this day, versions 0.0.1 to
0.1.1 will continue to be served by rubygems indefinitely as is. Nobody
can change any code which has been published through rubygems.
We can, however, publish new releases with our code. That would be version
1.0.0 and everything above that.
Again, thank you very much!
PS: I will redact this public Github post so that it does not contain our
email address any more. I assume you will receive an email notification of
this post, there you can see the email address.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAACBQO73XBUKTDTJESZGTLQH5LOXANCNFSM4IS5TDQA>
.
--
Jared
|
|
Yes! This is the repo: https://github.com/bukowskis/method_object We're in the process of preparing it for release in this PR: bukowskis/method_object#2 |
|
not sure it worked since you're blank
[image: image.png]
can you check?
…On Thu, Sep 5, 2019 at 4:24 AM mmzoo ***@***.***> wrote:
Yes! This is the repo: https://github.com/bukowskis/method_object
We're in the process of preparing it for release in this PR:
bukowskis/method_object#2
<bukowskis/method_object#2>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAACBQKOVKCJV43EQMQSDK3QIDT6JANCNFSM4IS5TDQA>
.
--
Jared
|
|
Yes, it worked just splenditly! I recently changed the email address that was associated with our rubygems company account and didn't update the gravatar yet. We can now remove you from the gem and are looking forward to releasing shortly. Cool, thank you! |
Hi!
We're actively developing a gem with the same name. I'm not sure your gem is still active or not? If it is not really used, we would like to take over the name on rubygems and publish it for everyone to use. It's been used internally for some time now, but we believe it's useful for a larger audience.
Our functionality is similar to the one you propose, only that the arguments need to be specified beforehand much l like keyword arguments (as opposed to your
*argssplat). That's basically implemented using dry-initializer.EDIT: And use
include MethodObjectso you don't have to inherit.Let me know your thoughts.
Thanks!
The text was updated successfully, but these errors were encountered: