federico-razzoli
commented
1 month ago About 1:
Separating the audiences was a basic idea of this list. We can change it, but should be give up usability to be in that list?
Another option could be to split this list into 3 different depositories. In theory, each of them might have the criteria to be listed. I'm not sure if this is a good thing for usability or not.
I'd like to hear other people opinions.
About 2: I tried this pull request, let's see if it's approved.
About 3: I don't have an answer, but I have a general feeling that GitHub search is far from perfect.
Github has a lot of awesome lists. A search for awesome in:name forks:false gives 101 k hits. Which ones should awesome-mariadb be included on? I tried searching, e.g. "awesome-mysql" in:readme which gives 412 hits, and awesome AND mysql in:README which gives 25.5 k hits. I started looking through the top starred in the latter, and found out:
1. sindresorhus/awesome (312k stars) - my PR to add MariaDB was not eligible. Their long list of criterias requires the awesome list to be a flat list instead of a list divided into sub-pages (like awesome-mariadb is now), see the PR for the rest of the criterias. 2. awesome-python (213k stars) - has a list of Database Drivers with awesome-mysql as an item with sub-items. MariaDB could be included as a separate item here too. Anybody want to give a go? 3. awesome-selfhosted/awesome-selfhosted (188k stars ) - this one and following one in the search results does not mention awesome-mysql in the readme. Is there something wrong with the github search critieras I used?
I ended my evaluation here and decided to share my observations so far. Maybe somebody wants to comment on this so far?