Re: Planning to close Hydra Community Group due to inactivity unless we hear from you

I have an interesting proof of concept project, though it is closed 
source. What I do is automating HTML generation based on the REST API 
response. For example a hyperlink can be turned into a form or an anchor 
depending on its properties. The result is an automatically generated 
web application which can be even customized if I add custom rules to 
the generator. Not sure if the same concept is applicable to a different 
context, but I guess it could be used for translation between APIs too.

I think what is needed at this point is a bigger community, and to reach 
a bigger community we need people willing to play with the technology 
and write about it. To convince someone to use Hydra in a professional 
project it requires a lot more popularity and to increase popularity we 
need a lot more blog posts, tutorials, etc. about it, not to mention 
comparisons with other REST technologies, advantages/disadvantages, etc.

On 2024. 05. 18. 19:04, Andrii Berezovskyi wrote:
> Dear Hydra community,
>
> May I ask if someone could point out any products using Hydra or 
> services providing a Hydra-based API, please?
>
> I was involved in OSLC [1] for quite a few years, which builds on top 
> of LDP (sort of) to enable hypermedia-driven linked data APIs for 
> engineering tools (these declared OSLC support [2]). I've been keeping 
> an eye on Hydra since it's an effort in an adjacent space but never 
> got an excuse to work with it since I have not encountered a 
> tool/platform exposing a Hydra endpoint. I would love to have an 
> excuse to play with some Hydra APIs, even better if one is in the 
> engineering tooling domain!
>
> Also, may I ask if there has been any synergy between Hydra and LDP?
>
> Thanks,
> Andrew
>
> [1]: https://open-services.net/
> [2]: https://open-services.net/resources/tools-survey-2020/
>
>> On 6 May 2024, at 17:17, Karol Szczepański 
>> <karol.szczepanski@gmail.com> wrote:
>>
>> Dear Hydra Community members
>>
>> In response to your objections I've contacted CG/BG System asking not
>> to close the group yet.
>>
>> I'm not sure I agree with Asbjørn about being in deep hibernation -
>> I'd call that state a "clinical death", but this turmoil the notice
>> caused might bring some good.
>>
>> Indeed I failed to push some new energy to the community after taking
>> over from Markus, but there was still some activity going on on GitHub
>> (which was also announced on the group), including a release candidate
>> pull request [1].
>>
>> While the end of the road is close for the specification, there is
>> still some room for discussion about the final shape.
>>
>> The notice itself is also a mark for me to take the final step with
>> publishing the spec.
>>
>> Regards
>>
>> Karol Szczepański
>>
>> [1] https://github.com/HydraCG/Specifications/pull/243
>>