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

Who has access to the rbtree gem on RubyGems? #2

Open
kyrylo opened this issue Jan 12, 2022 · 3 comments
Open

Who has access to the rbtree gem on RubyGems? #2

kyrylo opened this issue Jan 12, 2022 · 3 comments

Comments

@kyrylo
Copy link

kyrylo commented Jan 12, 2022

Hi there @zzak!

I saw that someone pushed a new version of rbtree (v0.4.4) on January 1, 2021.
Was it you? If so, how did you get access/rights to push the gem under the name rbtree?

The owner of the gem is this profile: https://rubygems.org/profiles/lvfl98xod5hkd1mczt9yiuyoulblcy5z
Which, I believe, belongs to Ozawa Takuma.

Three years ago I made a fork of rbtree and released it as rbtree3 because I couldn't just push to rbtree.

I still maintain it but I am not sure who uses that besides me. It also includes some of the fixes you did here. Not sure if you saw my fork or https://github.com/skade/rbtree, where I was able to obtain the source code. @skade let me know that he also doesn't have access to the rbtree gem on RubyGems.

@dentarg
Copy link

dentarg commented May 14, 2024

Looks like @mame is the one pushing rbtree to RubyGems.org? https://github.com/mame/rbtree

@kyrylo
Copy link
Author

kyrylo commented May 14, 2024

Oh wow, so now we have one more rbtree fork, which leads to more confusion.

Great find, @dentarg 😁🤝

@mame
Copy link

mame commented May 14, 2024

Yes, I pushed rbtree 0.4.5 and 0.4.6. Ozawa Takuma gave me a push privilege when I sent him a couple of patches to fix some build errors.

Note that the owner of rbtree gem is still Ozawa-san. When I need to make changes to rbtree, I email the patch to him for review before committing.

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