[Obcommunity] will evolve into a real community repository. Any valid Obarun GitLab instance account will have the ability to maintain their packages, and these packages will be directly accessible through the [Obcommunity] repository.
This is an excellent idea, and I have a use case for this. We just need to be careful about edge cases. Here are two potentially problematic ones right of the top of my head:
- how to handle package name collisions (assuming obcommunity remains a single repository);
- how to prevent abuse of the build services, Obarun doesn't have a lot of active users now which makes it a non-issue, but the number of users could increase over time, increasing the chances that someone without good intentions shows up.
This last point is important because you're not just providing a means to share PKGBUILDs like the AUR does, but also infrastructure to build the resulting packages (which the AUR doesn't and thus is not vulnerable to these types of problems).