W3C home > Mailing lists > Public > public-rdf-ruby@w3.org > May 2012

Re: New github organization: ruby-rdf

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Wed, 16 May 2012 14:07:53 -0400
To: "public-rdf-ruby@w3.org" <public-rdf-ruby@w3.org>
CC: Arto Bendiken <arto.bendiken@gmail.com>, Gabriel Horner <gabriel.horner@gmail.com>, Ben Lavender <blavender@gmail.com>, Nicholas Humfrey <nicholas.humfrey@bbc.co.uk>, Pius Uzamere <pius@alum.mit.edu>
Message-ID: <631EE54F-72E7-4FF1-8526-26570CB0B973@greggkellogg.net>
I've moved my forks of the remaining repos to http://github.com/ruby-rdf. Ben has kindly updated the note at the top of his repos to redirect people here, and where I can, I've updated the rubygems.org links to refer here as well.

This now includes the following gems:


in addition to those previously mentioned.

Any issues for the base RDF gem (http://github.com/ruby-rdf/rdf) or any other rdf-based gems located in that organization should be directed to the appropriate project under ruby-rdf.

Also, note that the rubygems documentation link for linkeddata points to http://rdf.greggkellogg.net/yard/index.html, which contains combined documentation for all gems referenced from linkeddata, updated when I refresh the RDF distiller.

On May 15, 2012, at 10:32 AM, Gregg Kellogg wrote:

> On May 15, 2012, at 5:46 AM, Gabriel Horner wrote:
>> On Mon, May 14, 2012 at 12:34 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>>> I just set up ruby-rdf as an organization on GitHub at http://github.com/ruby-rdf. I've also transferred most of the RDF gems for which I was the owner to this org. This includes the following:
>>> https://github.com/ruby-rdf/rdf-rdfxml
>>> https://github.com/ruby-rdf/rdf-rdfa
>>> https://github.com/ruby-rdf/rdf-turtle
>>> https://github.com/ruby-rdf/rdf-trig
>>> https://github.com/ruby-rdf/rdf-microdata
>>> https://github.com/ruby-rdf/rdf-n3
>>> https://github.com/ruby-rdf/rdf-xsd
>>> https://github.com/ruby-rdf/sparql
>>> (others will go there when they're more stable).
>> For all the gems that you have push access, you could just fork over
>> to ruby-rdf. That way you're still giving credit to the original
>> owner. You could explain in the README that the repository has moved
>> over to the organization. It would help if datagraph, bendinken and
>> bhuga updated their repository descriptions to point to ruby-rdf as
>> the canonical ones.
> Yes, in the absence of action by Arto and Ben, my plan is to move my own repos over, and then fork those back to my own account. Of course, this means a fork of a fork, so it would be better to have the original root repos moved.
> Alternatively, my repos, which are the most up-to-date at least for rdf and rdf-spec, could break the fork and become primary repos, which is probably less confusing.
> Best would be for Arto and Ben to take action.
>>> I encourage owners of other RDF repos to join the organization and move their repos over as well.
>>> Next step will be to re-release these gems with updated gemspec information so that the home pages show up properly on http://rubygems.org.
>>> Also, I'll look into creating GitHub Pages for the generated Yard documentation. This should replace the Ruby Forge docs, which are way out of date.
>> You could just use http://rdoc.info/gems/GEM i.e.
>> http://rdoc.info/gems/rdf . The site is maintained by the Yard author.
> The READMEs already reference http://rubydoc.info/gems/GEM (which is the same thing, really). However, I think that http://ruby-rdf.gitub.com and sub-URLs should probably at least contain the READMEs themselves. For http://ruby-rdf.github.com, the linkeddata README might be most comprehensive.
> With rubydoc.info, it definitely favors the root repository, for example http:;rdoc.info/gems/linkeddata reference's datagraph's gem, while my own requires more detail: http://rdoc.info/github/gkellogg/linkeddata/frames
> Gregg
>>> Gregg
Received on Wednesday, 16 May 2012 18:08:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:15 UTC