Re: Ruby Hydra client group

>
> - Where should the development happen? Do we want to get a repository
>   under the HydraCG organization on GitHub?
>

If it's agreeable to the group release any work into the public domain
(Unlicense [0]), I'd suggest creating a team within the RDF.rb GitHub
organization [1].

That would be:

  - an ideal long-term home for software output (if Hydra achieves
significant uptake and/or moves to the standards track, RDF.rb would want
to support a public domain implementation);
  - the best way to achieve visibility to other potentially interested
Rubyists who might not already be following the Hydra work closely.

- Tom

[0] http://unlicense.org/
[1] https://github.com/ruby-rdf

On Sat, Jun 18, 2016 at 10:56 AM, Markus Lanthaler <markus.lanthaler@gmx.net
> wrote:

> Hi,
>
> If you find your name in the following list, you stated in the survey that
> you would be interested and willing to contribute to the development of a
> Hydra client in Ruby.Please use this mail thread to bootstrap the group to
> get it up and running. How you do that it's completely up to you. Here are
> some questions that you might wanna answer as group to get started:
>
> - Where should the development happen? Do we want to get a repository
>   under the HydraCG organization on GitHub?
> - How should we structure the group? Should assign different roles
>   to people?
> - Should there be 1-2 persons that are responsible to lead the group
>   and drive the effort? Who should that be?
> - What will be our primary communication medium? How do we ensure it
>   is properly archived?
> - How do we make decisions as a group?
> - How do we plan the development? How do we track progress?
> - How and how often do we report back to the Hydra W3C Community Group
>   in case most of our communication/collaborations happens off the Hydra
>   mailing list?
>
>
> Here's the list of people that expressed interest in Ruby. People marked
> with an asterisk named Ruby as their preferred language.
>
> - Gregg Kellogg *
> - Sadauskas Paul *
> - Kiril Tonev
> - Pablo Ccori
> - Paul Beaudoin
>
>
> Cheers,
> Markus
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>