Sorry to bring this topic back, I would like to throw some ideas out. As it has been said, no AUR alike. One of the advantages that void presents is the fact that packages are reviewed by maintainers, keeping the quality of the repos high, which is a great thing and rather tiring job, but precious tho the community!
However, I see there is a big problem, specially in the long run. Everything needs to be done by the maintainers, their time and their resources. Requests are piling up and the hardware is not free, old packages are barely keep due to space limitations, which isn’t great; x86, arm, arm64, x86_64 (an mips?) need to be stored and compiled, generating costs. And Void will only continue to grow, making this worse and worse.
Another issue is that reviewing a package is sometimes not enough. Knowing which make flags should be used or not, special compiling options, etc (specially when having a musl branch). A build may work in a machine, but may not in others, and it may set some settings that the majority may not want (example: requiring Java for a minor feature). But if the package is approved then any issue it causes, even if it wasn’t created by the user (an update), then needs to be fixed by them, the maintainers.
My last concern is wether the smallest and strangest packages will need to have support. There are little utils that some people may use, but throwing them into the official repos may be too… extreme. AUR solves this problem (one of the few things that it does right), it allows user to share automatic installation instructions (PKGBUILDs). Void could take advantage of that.
I would like to throw some proposals out:
Accepting any package (after being approved), but without building it: users can continue to contribute to void-packages, but flaging it as a no build package by the continuous building system, but still letting the user to clone it and build it from source if needed. This way a bit of resources are saved.
Separate repository for the community: similar to the idea of AUR, like a VUR. but packages need to pass the maintainers and packagers approval, and is treated like the current void-packages. Users will need to clone it and build their extra packages from there, without an easy manager like Pacaur or yaourt.
The main difference between the two is that the second would be closer to the community. There will be filtering, but a package creator could directly modify their own package, like AUR. But the maintainers would still have the right to deny someone from uploading or modifying anything.
The advantages this method presents is a faster growing package number. But I am more interested in testing. This way we could have automated *-git packages ready to be build, clean and easy (take dolphin’s emulator as an example, 3 years passed from stable to stable release, but the development branch was miles ahead after some time passed, and people used the -git branch).
All feedback is welcome.