- From: Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>
- Date: Wed, 22 Jun 2016 19:38:15 +0200
- To: Lorenzo Moriondo <tunedconsulting@gmail.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Hydra <public-hydra@w3.org>
- Message-ID: <CA+OuRR-A9m8i0sEah_LXFrFCOs9CO3PvTo709uPTUxH_tuhOfA@mail.gmail.com>
Hi all, first of all, although I am very interested in Hydra (and a big fan of Python), I can not take the lead of this activity, having already too many responsibilities on my plate :-/ But I will gladly give a hand if needed. I did hack a small hydra client in Python ( https://github.com/pchampin/hydra-py) mostly for 2 reaons: * I wanted to get a concrete feeling of how much intelligence Hydra allowed to put in the client, and * I needed a Python TPF client. The README and the scripts in the `examples` directory should give you an idea of how it works, until I find some time to write a proper documentation. If any one feels to comment and/or contribute, feel free to do so. FInally, to reply to Lorenzo, I dare say that I have some expertise on RDF, having been a member of the RDF 1.1 working group :) So I can help on this side. best On 19 June 2016 at 12:16, Lorenzo Moriondo <tunedconsulting@gmail.com> wrote: > Hi Python fans (; > > I can definetly help with Python development and anything Python-related. > I am actively volunteering for Python Software Foundation and I am a great > fan of Github; I think that small groups can leverage consistently the > repository plus issues plus the wiki there, I usually go with Google Docs > for resources collection and more design-intensive tasks to be documented. > Lately is really common to open a Slack group to have chats and docs going > on in the same place, and also publish the commits via channels using Slack > bots. Obviously in the end everything has to be rolled out in the official > mailing list to keep track of progress. > > Briefly, I am not a great expert of RDF or other W3C standards for data; > if there is somebody that knows perfectly the spec and basic principles of > the client and can write down with me a design document, we can do all the > software engineering and development part with anybody willing to help. > > Best, > > PS. I did actually started a small research for a metadata-rich server in > the past but didn't had the time to follow: > https://github.com/Mec-iS/mild-QL > > Lorenzo Moriondo, from mobile > https://it.linkedin.com/in/lorenzomoriondo > On Jun 18, 2016 7:57 PM, "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 Python.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 Python. People marked >> with an asterisk named Python as their preferred language. >> >> - Charles Vardeman * >> - Lorenzo Moriondo * >> - Pablo Ccori * >> - Pierre-Antoine Champin * >> - Adam Christie >> - Tomaszuk Dominik >> - Wasin Passornpakorn >> >> >> Cheers, >> Markus >> >> >> -- >> Markus Lanthaler >> @markuslanthaler >> >> >>
Received on Wednesday, 22 June 2016 17:39:06 UTC