- From: Asbjørn Ulsberg <asbjorn@ulsberg.no>
- Date: Thu, 26 May 2016 15:56:27 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: Hydra <public-hydra@w3.org>
2016-05-25 22:48 GMT+02:00 Markus Lanthaler <markus.lanthaler@gmx.net>: > I don't think we have a tooling or process issue. In my opinion the biggest > issues is we have are missing commitment and contribution... and, probably > most importantly, lack of code that is driving and informing the discussions. I'd say that those are symptoms of a tooling and process issue. But since I agree with what you write later, that's not very important. > So, my proposal is comparatively simple: we start creating a Hydra client (or > a couple of them) and use it to drive the further development of Hydra. Excellent idea! The reason I like this idea, is that it means the development of Hydra turns in to actual *development*, and the most natural way to do that is on GitHub with issues, pull requests, etc., just like Tomasz suggested. However, it's even better to contribute actual code to a working implementation than (just) text to a specification. It's secondary, but in order to get more contributions to the specification, I would strongly urge you to consider changing the format from HTML to Markdown. > As soon as we are happy with the implementation of a feature, we will update > the specification (at which point, we will already have examples). +1. > So, to start gauging the interest, I created a survey: > > https://www.w3.org/2002/09/wbs/64267/hydra-client-collaboration/ Answered. 2016-05-26 0:01 GMT+02:00 Paul Sadauskas <paul@sadauskas.com>: > I found the easiest approach for me would be to write a test suite that would > exercise the Hydra example server and my code, and highlight the differences. I think the test suite should be a part of the scope of the project. Implementers of both servers and clients should be able to exercise their implementation by a standard test suite that should be easy to improve through pull requests and which should provide good feedback to the implementer when something is wrong in his or her implementation. -- Asbjørn Ulsberg -=|=- asbjorn@ulsberg.no «He's a loathsome offensive brute, yet I can't look away»
Received on Thursday, 26 May 2016 13:56:57 UTC