Incorrect information about hymps

[forart]

Just cut'n'pasted your correction.

(curiosity: can't GH users post changes directly to our "code" ?)

[forart]

note: Discussions are active, if you have any suggestion (about categorizations too)...

Let's keep in touch !

[andrepxx]

Well yes, I could fork the repo and submit a pull request. But I didn't wanna fork it and I saw that, so far, all commits in this repo were from you and I didn't wanna "break" that "row" by submitting my own commit. ;-)

[forart]

Well yes, I could fork the repo and submit a pull request. But I didn't wanna fork it and I saw that, so far, all commits in this repo were from you and I didn't wanna "break" that "row" by submitting my own commit. ;-)

Yep, GH is a bit "strange"... we happened to unintentionally fork some repos (RealBasicVSR, YAMS ? Of course we have doxed them, but never - intentionally - forked).

We do also noticed some "caching effect" by badges generation services, anyway - except for some (inevitable, sigh!) human error and some limit (it would be great to let visitors to dinamically apply table sorting) - we are quite happy of "our" markdown-tables format.

Anyway we would like to focus on categorizations (softwares are not lacking) 'cause there's some mess...
...example: under H_AUDIO could be more useful to have more macro-categories (eg. INSTRUMENTS -> Voice, Guitar, Bass, Drums...) even for GH-page readability, anyway the project goal is to build a platform-indipendent open source "libraries-distro" for (artistic) multimedia content creation.

We do need a dev-oriented categorization, but we - actually - don't have any "embedded" dev in our organization (as we also told to @jcelerier here)...

...so suggestions are welcomed.

;)