@hiro I do not agree, good organization allow to better solve the problems, let's take a stupid example (also valid to answer bmarkus):
Every time we update the kernel there is the usual problem with programs that lose compatibility (and this round it is exacerbated by the loss of scm).
This is normal administration, but if we had a unified management of the scripts we could better handle the issue.
Let's take a packet at random from aur: https://aur.archlinux.org/packages/vboxgtk/
People can easily vote for it, comment on it, observe the code, download the source, Read the comments, you'll notice several reports.
Simplify access to this information could mean increasing the participation of people.
Also maintain a repository of scripts is to have few limitations of space (and I remember we had this problem in the past) and would also increase the safety of the packages (since the compilation would be just in time, with the code under the eyes).
If we wanted to exaggerate, we could even think to automate the reconstruction of critical packages every time we update a kernel or when a new dependency is updated.
We could make sure that meo have the latest minor version of firefox in complete autonomy, the minute after its release (just kidding but it is a plausible perspective, I hope that meo do not get angry
However, these are not things that I claim, but I'm still stuck to the fourth version of tinycore for missing application and I do not have the ability to solve alone.
Do not take it as a protest, I still consider tinycore as a great gift to the community, and just know that I am sorry to observe the presence of these problems.