It is not a secret that Prolog community is quite small. Thus, improving the availability of the resources if very important. For example, there is an Awesome Prolog GitHub repo, but it wasn’t updated for a while. I suggest to look at the OCaml community example, and create a “community” GitHub organization to manage important Prolog projects:
Building a better community is always good. Resources are indeed quite spread. Sites like Awesome Prolog already try to make material accessible from one place. Anyone can (I guess) try to get involved in Awesome Prolog, no? Next we can make a better connection from the SWI-Prolog site.
For SWI-Prolog we have GitHUb, the add-ons (packs) and this forum, The forum seems to work really well thanks to Discourse. The add-ons have been discussed and can and should be improved.
What is really needed are of course volunteers to help moving these things forward. Here it doesn’t help that the small Prolog community is also distributed both over distributions and with totally different ideas were things should move to.
I think that The Awesome Prolog repository is a good idea to add links to systems, code, libraries, examples, tutorials, etc. Specially for three reasons: there exists an explicit code of conduct, it is system agnostic, and contributions via pull requests are easy.
I think the first step should be to figure out why Klaus is not merging these PRs. If he doesn’t like them we get the discussion between quantity vs. quality and who decides on what. If he lost interest or time, maybe someone else wants to take over? If there is something functional with a good reputation I think it is better to strengthen that than to start something new.