search

samvera-deprecated / rdf-vocab

Shared RDF Vocabularies (rdf-vocab <= v0.7.0)
https://github.com/ruby-rdf/rdf-vocab
Apache License 2.0
4 stars 2 forks source link

Should rdf-vocab be offered to ruby-rdf? #20

Closed dchandekstark closed 9 years ago

dchandekstark commented 9 years ago

In #19, @gkellogg mentioned this as a possibility, so I wanted to get ProjectHydra community feedback. As pointed out in #19, it would require a license change.

/cc @no-reply @jeremyf @jcoyne @mjgiarlo @jpstroop @acoburn @awead

dchandekstark commented 9 years ago

My initial reaction is that both projects might benefit from such a move. RDF.rb could offload some its historical baggage, and rdf-vocab might gain better support and integration with RDF.rb over the long term. Personally I don't see the license change as a blocker (see also #6).

dchandekstark commented 9 years ago

Closing with no action. Please re-open to re-raise question.

gkellogg commented 9 years ago

When we last looked at this, we were waiting for a license change to UNLICENSE. There are also a couple of technical changes needed, mostly to lazy-load the vocabulary, rather than do a require of each one when this gem is loaded; that could be quite costly as the number of vocabularies is added.

RDF.rb does this by creating an autoload for each vocabulary, and a hard load if Vocabulary.each is called.

If the license on the gem is changed to UNLICENSE, this would require a dedication for any significant change or portion of this (trivial changes aren't necessary); see https://github.com/ruby-rdf/rdf/blob/develop/README.md#contributing.

To do this, we'd like to see the license terms changed, the repo moved to http://github.com/ruby-rdf/rdf-vocab, and push rights to rubygems.org updated to allow selected core-committers to release new versions of the gem; of course, original members of the gem retain all administrative rights.

/cd @bendiken

dchandekstark commented 9 years ago

@gkellogg Thanks for revisiting this issue. I will spin off an issue to do the lazy-loading. As to the question of license change and move to ruby-rdf, I need to consult the Hydra community and current project contributors. Stay tuned.

/cc @acoburn @mjgiarlo

acoburn commented 9 years ago

@dchandekstark regarding a possible license and org change, that sounds like a great item for next week's hydra-tech call.

dchandekstark commented 9 years ago

Decision made in the affirmative. See https://wiki.duraspace.org/display/hydra/Hydra+Tech+Call+2015-03-18.