tag:help.rubygems.org,2010-01-19:/discussions/problems/130-observational-gem-ownershipRubyGems.org: Discussion 2018-10-18T19:50:54Ztag:help.rubygems.org,2010-01-19:Comment/14681722010-04-16T02:31:08Z2010-04-16T02:31:08Zobservational gem ownership<div><p>Hi there,</p>
<p>I've added the current gem owner to this thread. We have a
policy of not going in and revoking ownership without giving the
original owner some time to adjust. You can use the <code>gem
owner</code> command to give James ownership of the gem:</p>
<p><a href=
"http://rubygems.org/pages/gem_docs#owner">http://rubygems.org/pages/gem_docs#owner</a></p>
<p>After that, you can push a forked gem simply by naming the
gemspec "yourusername-observational", rebuilding, and pushing.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/14681722010-04-16T02:53:10Z2010-04-16T02:53:10Zobservational gem ownership<div><p>Sorry for the trouble James. I didn't really know what I was
doing... What<br>
email address should I give ownership to?</p>
<p>Great gem, by the way :) I hope my bug fixes got in ;)</p></div>Brian Terlsontag:help.rubygems.org,2010-01-19:Comment/14681722010-04-16T03:07:48Z2010-04-16T03:07:50Zobservational gem ownership<div><p>No worries at all. My gemcutter email is <a href=
"mailto:jamesgolick@gmail.com">jamesgolick@gmail.com</a></p></div>James Golicktag:help.rubygems.org,2010-01-19:Comment/14681722010-04-17T20:11:56Z2010-04-17T20:11:56Zobservational gem ownership<div><p>The gem should be entirely in your hands now!</p>
<p>Thanks.</p></div>Brian Terlson