Overtake the curation of WebVOWL, or use an own fork

[Zack-83]

Is your feature request related to a problem? Please describe.
The project which developed WebVOWL seems abandoned. The service is offline, the repository has not been updatet for almost three years and the developers do not react to users' requests.

Describe the solution you'd like
Since Widoco relies heavily on WebVOWL, maybe it would be helpful to fork it, either as standalone, or as a part of the Widoco project.

The advantage would be that some minor adjustments may be added more quickly, e.g. VisualDataWeb/WebVOWL#205

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
There are already some WebVOWL forks, but none is particularly updated

• pmundt: 2 branches, 0 issues, 0 PR; last commit 2024-09-06
  • Rework Dockerfile for multi-arch builds; drop re-run of release script

Nonactive forks with significant contributions in the past

• DrSnowbird: 2 branches, 0 issues, 0 PR; last commit 2022-08-04

  • added automation scripts to ease the common use run, build, stop, she…; updated/fixed download errors; updated docker-compose port

• Lembutt: 1 branch, 0 issues, 0 PR; last commit 2023-01-26

  • Create docker-image.yml; added timeout; url as env var; Update Dockerfile

• Vansnoden: 1 branch, 0 issues, 0 PR; last commit 2022-09-26

  • matcher menu added with a temporary action onclick; base ontology interface set up; salvador atagong committed Sep 23, 2022; matcher architecture defined; datalist added for input search purposes

• dati-semantic-WebVOWL: 1 branch, 0+3 issues, 0+8 PR; last commit 2023-02-10

  • Include Owl2Vowl converter in repository; Configured Github Actions; added https to google fonts url + added publiccode.yml; update docker container image and removed logs file; fix versioning webVol; Fix first load resources; add workflow_dispatch to publish

• Original: 2 branches, 61+118 issues, 4+23 PR; last commit 2022-05-11

Recent forks with no significant contribution

• tziegler-tud: 1 branch, 0 issues, 0 PR; last commit 2024-07-18
  • Create docker-image.yml

Nonactive forks

• L4B0MB4: 1 branch, 0 issues, 0 PR; last commit 2023-01-04

  • working but imperfect resizing for text; fixing radius adjustments based on text size and position

• mosfet80: 1 branch, 0 issues, 0 PR; last commit 2023-07-29

  • remove old unused jar

• BeameryEdge: 1 branch, 0 issues, 0 PR; last commit 2023-04-19

  • remove CI link

• bohuizhang: 2 branches, 0 issues, 0 PR; last commit 2023-09-11

  • Implement OntoGPT mode

• kevfocke: 2 branches, 0 issues, 0 PR; up to date

• sarvex: 2 branches, 0 issues, 0 PR; up to date

• ibinsu: 3 branches, 0 issues, 0 PR; up to date

[dgarijo]

Thanks @Zack-83.
I do not have the bandwidth to maintain WebVOWL. However, having a static version to support PRs from users would be nice. Is there a preferred fork you think we should consider? You list a lot of possibilities :)

[Zack-83]

Many thanks @dgarijo !
I restructured a little the list.

Most forks made progress on the Docker embedding. I cannot judge how relevant this can be for our usage.

I would try with one of these two:

• https://github.com/pmundt/WebVOWL/tree/docker-minimization --> the most recent one;
• https://github.com/VisualDataWeb/WebVOWL/tree/vowl_editor --> "editor" sounds good but I cannot judge how far they are.

[dgarijo]

Thanks. The editor is not something I want to include in the doc, as it's for a different purpose. The first one seems the one to go.