beanvalidation.org is no longer maintained

[yrodiere]

There is a website for "bean validation" out there: https://beanvalidation.org/

However:

1. The news section hasn't been updated in years.
2. The website doesn't mention Jakarta Validation 3.1 -- and is probably outdated in other areas.
3. The website is hosted on Red Hat infrastructure, and maintained by the Hibernate team, with no involvement or control from the Eclipse foundation.
4. Jakarta Validation already has a website: https://jakarta.ee/specifications/bean-validation/

I wouldn't be able to tell you who has ownership of the DNS records, but I can try to find out, and I suspect the Eclipse Foundation would want to own it.

What should we do with this website?

1. Keep things as they are, with outdated information.
2. Transfer ownership (push access) to people working on Jakarta Validation.
3. Re-host it somewhere on Eclipse infrastructure, and keep it up to date.
4. Re-host it somewhere on Eclipse infrastructure, for archive purposes, with some added banner to mention the content is obsolete.
5. Completely lose the content and change the DNS to redirect to some other Eclipse website (https://jakarta.ee/specifications/bean-validation/ or this GitHub repo).
6. Something else?

The Hibernate team can help with the transfer of hosting/ownership, but I don't think we will be able to keep the website up to date.

cc @starksm64

[yrodiere]

BTW there is even a whole GitHub organization: https://github.com/beanvalidation
The website source is there: https://github.com/beanvalidation/beanvalidation.org

[gsmet]

The website was maintained by us. I think it still has value for the old specs. I suppose that it doesn't make a lot of sense to push the new specs there... even if I would argue that the website is a lot better than the home at Jakarta (but maybe this can be improved).

Maybe we just need to add a banner explaining the situation and point to the new home?

Also Bean Validation has been renamed Jakarta Validation if I followed things correctly so beanvalidation.org doesn't make a lot of sense for the future.

[emmanuelbernard]

I own and control the DNS for beanvalidation.org, feel free to ask me of tasks (outside my PTO time ahah)

I would really love to keep the website alive because it is much nicer for a beanvalidation user and contributor than the https://jakarta.ee/specifications/bean-validation/ page.
In fact the jakarta ee page does point to this website.

The website is hosted by GitHub Pages, but the CI and staging is indeed a Red Hat Hibernate team owned infra.

I like your solution 2 (give push access to Jakarta Validation contributors), which hopefully would solve the outdated news problem.

I almost pushed to fix it all in rage (naive time evaluation on my side) but I discovered that it's using awestruct and is at an old Ruby version unfortunately and it's a pain to set it up on macOS. So a refresh, or a Docker based "dev" environment or a rebase off Jekyll would make sense to reboot the effort. Each comes with gradually increasing time to spend on it.

[yrodiere]

a Docker based "dev" environment [...] would make sense to reboot the effort

Way ahead of you: https://github.com/hibernate/awestruct-build-env

Though the beanvalidation.org readme is indeed outdated... It should look more like this: https://github.com/hibernate/hibernate.org?tab=readme-ov-file#set-up-the-build-environmentthe-easy-way

[emmanuelbernard]

This fails for me on arm64. The fedora base image seems to be aarch64

[emmanuelbernard]

ok no it's not quite that, it fails on macOS when the podman VM is run through their Rosetta abstraction. It might be fixed in the next major OS version but I'm not running that.