OK so this burns my ass as well.
Some ground rules
Library scripts should be hosted on GitHub
Library script should have a support thread on the forum and a general instruction readme on GitHub.
Library scripts should have links to the support thread and GitHub in header comments.

Do at least this and i will set a cron job to use a page just like https://github.com/ahkscript/awesome-AutoHotkey except as a JSON page with GITHUB ZIP file download links with a server cron job to pull these packages to the server daily and set a download from the forum next to the download link above

Yes, but I prefer actual code collection rather than just a 'bookmark'.

guest3456 wrote:unless of course youre expecting all the actual CODE of the libraries to all be in one place. but that is just absurd. each library should be in its own repo so that issues and bugs can be contained and maintained by the individual authors.

What will happen if the author is not active anymore, the Pull Requests won't get reviewed or even merged.
Yes, anyone else can still take over the development of that code by Forking from the original repo.

But if the author accidentally deleted the repository, we will have another missing resource(s) just like autohotkey(dot)net.
Nowadays in the cryptocurrency craze, everyone talks about 'decentralization is much better', but in this case what we actually need is 'centralization' indeed.

elmo wrote:@tomoe_uehara seems to be talking about (b) and, in the examples from other major platforms cited by @iseahound, they return code.

Yes elmo is correct, what I'm talking about is the actual code itself, not just a link to webpage or somewhere else.

tank wrote:Do at least this and i will set a cron job ... to pull these packages to the server daily

Unfortunately I think blindly uploading codes to the repository will make it bloated and the filesize will be very large to download, thus it will defeat the purpose of making a compact library itself.
We need a categorization in form of Git Branch, so anyone don't have to download whole repository just to parse JSON for example.
Git can utilize something like "selective download" by using Git Checkout.

Imagine a git repo that has multiple branches like https://crates.io/categories, those categories will be the branches.
Inside of the branch (for example 'Parser' branch), there will be another folder: JSON, YAML, etc.
Inside that JSON folder, there will be actual code itself, along with working example inside another subfolder.

We don't need a sophisticated system like yum, dpkg, apt, pacman, etc. What we need is a system that works, even a simple github repository is fine too.
To make it work, we need a collaboration from the Autohotkey Community users
More feedback is welcomed

As i see it Tomoe and I want 2 different solutions. Her suggestion i believe looks exactly like Awesome-AutoHotkey. I want to provide a centralized download no matter which repository it is in. And you seem to be suggesting a single repo for just ahkv2 scripts which might be a good idea if we can get adoption

Right, As i said this repo would be nothing more than a JSON file referring to approved and documented libraries. a server application would download and pack each approved library to a zip file. I would add a download button for it next to the ahk download. In this way we get a single download for all approved library files and a single JSON file to maintain for it

lexikos wrote:If the download or update of the "standard Lib" can be easily automated and "the community" wants it included with the installer, that is fine with me. I just want no part in maintaining it.

Thats great to hear - I always thought the same as the others. Seems we misunderstood you.
That means that we can create an entire library manager similar to pip or other related ones.