tag:help.rubygems.org,2010-01-19:/discussions/suggestions/8-programmatic-access-to-edit-those-new-gem-hyperlinksRubyGems.org: Discussion 2011-04-07T20:59:26Ztag:help.rubygems.org,2010-01-19:Comment/13414602010-03-30T15:17:32Z2010-03-30T15:17:47ZProgrammatic access to edit those new gem hyperlinks<div><p>Okay, just searched the gemcutter mailinglist but couldnt find
anything about this. So it seems valid. Perhaps this discussion is
more appropriate for the mailinglist?</p>
<p>On another point, can we stat how many people are actually using
the Wiki Link field? It just seems so similar in purpose to the
Documentation hyperlink, and therefore may be unnecessary /
deprecapable.</p></div>dreamcat4tag:help.rubygems.org,2010-01-19:Comment/13414602010-03-30T15:25:46Z2010-03-30T15:25:46ZProgrammatic access to edit those new gem hyperlinks<div><p>We've talked a bit off-list about adding arbitrary simple
metadata to the gemspec, which would allow for information like
this. Adding stuff to the gemspec isn't a simple change, as it
involves significant amounts of compatibility work.</p>
<p>I've taken a few stabs at this on a branch, but nothing worth
sharing yet.</p></div>John Barnettetag:help.rubygems.org,2010-01-19:Comment/13414602010-11-17T07:25:12Z2010-11-17T07:25:12ZProgrammatic access to edit those new gem hyperlinks<div><p>Closing this out for the moment, it's stale and we can revisit metadata handling after <code>Gem::Specification#metadata</code> lands. On your point about wiki vs. docs, dreamcat4, it's pretty frequent that one points to RDoc or YARD API docs and one (the wiki) points to more long-form stuff.</p></div>John Barnette