tag:help.rubygems.org,2010-01-19:/discussions/problems/34812-reporting-abuse-on-prometheus-client-modelRubyGems.org: Discussion 2019-01-25T16:37:28Ztag:help.rubygems.org,2010-01-19:Comment/468195812019-01-19T19:51:47Z2019-01-19T19:51:47ZReporting Abuse on prometheus-client-model<div><p>Thank you for writing in. It is the policy of RubyGems.org that we refrain from making judgements about the content of a gem, as we have little to no insight into what development a user might be doing out of the public eye, or what their eventual plans are. We know this can be frustrating, especially in the case of popular or common names, but we would rather err on the side of protecting creators than accidentally removing someone’s work.</p>
<p>If you haven't already, I would attempt to contact the author and see if they'll add you as an owner of the gem. Instructions on how they can do that can be found here:</p>
<p><a href="http://guides.rubygems.org/command-reference/#gem-owner">http://guides.rubygems.org/command-reference/#gem-owner</a></p>
<p>I've taken the liberty of cc'ing the gem author; hopefully a simple request to them will sort this out :)</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/468195812019-01-21T16:25:16Z2019-01-21T16:25:17ZReporting Abuse on prometheus-client-model<div><p>Hi Kerrizor and Andrew</p>
<p>First of all apologies for the late reply and the hassle.</p>
<p>I was investigating a bug bounty program when I found an unclaimed gem, so<br>
I squatted this name in order to report this to the company.<br>
However upon re-investigating I now have noticed that this gem does not<br>
belong to the bug bounty program, it was used as a library rather than a<br>
self developed gem.</p>
<p>I will release this gem name by adding you as owner and remove myself as<br>
owner of the gem.<br>
Could you give me an email address so I can transfer the gem name?</p>
<p>My sincere apologies.</p>
<p>Kind regards<br>
Preben</p></div>Preben Ver Eecketag:help.rubygems.org,2010-01-19:Comment/468195812019-01-21T16:57:46Z2019-01-21T16:57:47ZReporting Abuse on prometheus-client-model<div><p>Hi Preben,</p>
<p>You can reach out to the actual owners by re-opening <a href="https://github.com/prometheus/client_model/issues/29">https://github.com/prometheus/client_model/issues/29</a> and letting the maintainers know about this so they can work with you to transfer the ownership.</p>
<p>From the maintainer's github profile (<a href="https://github.com/beorn7">https://github.com/beorn7</a>): <a href="mailto:beorn@soundcloud.com">beorn@soundcloud.com</a></p>
<p>Sorry about how the topic came about.</p>
<p>Thanks,<br>
Andrew</p></div>Andrew Sutag:help.rubygems.org,2010-01-19:Comment/468195812019-01-21T17:48:54Z2019-01-21T17:48:56ZReporting Abuse on prometheus-client-model<div><p>As the maintainer of the <a href="https://github.com/prometheus/client_model">https://github.com/prometheus/client_model</a> repo, I would actually prefer not to have this gem at all (or at least I don't want to maintain it). The usage of the Prometheus protobufs in Ruby is almost non existing at the moment, and there are no plans to revive it. In fact, the upcoming standard for metrics exposition is OpenMetrics, which might then also provide a platform for protobuf support again, but that would be separate from the <a href="https://github.com/prometheus/client_model">https://github.com/prometheus/client_model</a> repo.</p>
<p>IMHO offering this Gem is more confusing than helpful.</p></div>Björn Rabensteintag:help.rubygems.org,2010-01-19:Comment/468195812019-01-25T16:37:27Z2019-01-25T16:37:27ZReporting Abuse on prometheus-client-model<div><p>I'm going to go ahead and close this ticket, if you folks don't mind. I'm glad we could connect you all to sort this out!</p></div>kerrizor