Hi all, If I might intervene, I have something to add. I'm not TU, but I maintain several packages in AUR. It's not too difficult. But the most challenging part of this task is dealing with user requests: if it's just an update request, it's more or less straightforward. But in all other cases, I find the most productive way for users to file a request for something AND mail me a description of what's going wrong. This way, I can discuss the issue and find (or decline to find) the best possible solution. So, as a package maintainer, I don't appreciate sending vague requests without a clear description of what's done wrong. Thank you for understanding and being ready to hear the POV of a mere mortal maintainer, Best wishes, Pasha Finkelshteyn Developer Advocate for Data Engineering JetBrains Pasha Finkelshteyn Developer Advocate for Data Engineering JetBrains asm0dey@jetbrains.com https://linktr.ee/asm0dey Find out more On Wed, Mar 1, 2023 at 2:03 PM Markus Schaaf <markuschaaf@gmail.com> wrote:
Am 28.02.23 um 23:51 schrieb irecca.kun@gmail.com:
Or there are no rules and TUs actually do what they want?
Simply put, yes. Actually the project is run by a club of people, called Arch-devs. It is their project, not yours. Although they admit new members, and work partially in public, they make the rules and interpret them. Or the TUs on behalf of the devs, pertaining to the community repo and AUR.
TU's aren't judges, as you said, but I definitely want some justice here.
While the project members made rules, these rules guide the inner workings of the project, and do not grant enforceable rights to outsiders. Run your own repo and be the ruler of your own little kingdom. :-)
Also, you could have come here and asked for explanation and guidance, instead of acting childish.
Just my 2¢. I am a user like you.
BR