• Category? Tools, of course, but something more? The most similar is Tools:Package Managers but is not exactly. Tools managers? Project Managers? (the same category will apply other tools such as hdlmake, edalize, tsfpga, etc).

Nice question. I'd say those are Tools, but not Package managers (only FuseSoc is). I think that Tools:Managers might be added. @Paebbels, wdyt?

• I filled license with "GNU GPLv3". Maybe we need a list of licenses and how to be specified? Others tools have not this field. Some of them, have the license as extra info, as long description (ex: Vunit -> License: Mozilla Public License, v. 2.0. baring OSVVM components.).

I think we should use SPDX identifiers: https://spdx.org/licenses/. No need to reinvent the wheel. In fact, I didn't take much care about that field because GitHub does it for us. We should check the repos of the items/projects and ask GitHub's API about it. We should only need to specify the license when there is no API.

• What about tags? Do you see that list ok? Is huge?

Up to you, both the number of tags and how to write them (in a single row or in multiple rows). Using multiple rows is desirable for SCM, but other than that...

Let me know how can I help to define these things (add a category, a licenses list, etc).

#1 😉

Thanks!