Re: C# Hydra client group

>- Where should the development happen? Do we want to get a repository
  under the HydraCG organization on GitHub?
I don't mind of having it in the HydraCG space.

>- How should we structure the group? Should assign different roles
>  to people?
Roles are useful at the beginning - later on it may become more fuzzy.
I'd try to gather some details on strong/weak points, experiences just to 
figure it out.

>- Should there be 1-2 persons that are responsible to lead the group
>  and drive the effort? Who should that be?
Leader is "a must" - otherwise we'll loose the target.
I'm considering to volounteer - unfortunately JavaScript client is also a 
good piece of work ahead I'd like to contribute :).
The only issue with that is I run URSA on my own which is a C# sever/client 
with Hydra on board and it would make me biased and contaminated with 
approaches/decisions I made in that project.

>- What will be our primary communication medium? How do we ensure it
>  is properly archived?
As it was stated several times, GitHub issues would be a good choice. Maybe 
random calls/emails/

>- How do we make decisions as a group?
Community feedback, leader's call?

>- How do we plan the development? How do we track progress?
Good point - some kind of issue tracker? I'd start with base list of 
features for all the platform clients.

For starters - I'd consider using RomanticWeb.net for modelling RDF. It's 
ORM like solution that allows to map strongly typed interfaces over RDF 
graphs with LINQ to SPARQL translator. I never liked pure RDF 
handling/querying i.e. with dotNetRDF.

Best
Karol

Received on Saturday, 18 June 2016 19:23:59 UTC