On 4/17/23 01:07, Polarian wrote:
Other maintainers have different situations and requirements. This finally is my main point: There is no simple "this is the right way to do it, and everything else is wrong". Rather, a lot of those decisions are situative and subjective. I don't believe in simple answers and "one size fits all" solutions in software engineering. There's just various degrees of broken-ness 😄
Although the point is valid, there is no one correct way, we have guidelines, and they should be adhered to.
A disordered community is a useless community, I will quote Erus here as I liked it :P
"Arch is a small community, we all must pull the carpet in the same direction" ~ Erus (this was paraphrased from memory)
It makes a valid point, if we are all writing packages in different ways, we are pulling the carpet in complete other directions and we get nowhere, we must keep going in the same direction, this is the exact reason why Anthraxx is the elected leader of Arch Linux, they decide the path moving forward, and they ruled.
No TUs seem to want Anthraxx toppled from power, as no vote to remove Anthraxx has been conducted, as far as I am aware at least.
Which therefore means, what Anthraxx says goes, they made the official call so we must follow!
I completely agree with the first part of your response, but I wanted to clarify a possible misconception in the latter part. As the project leader, I do have additional responsibilities, tasks, and duties, and try to drive our priorities inside a certain direction. But that doesn't mean my opinions and feedback should hold more weight than any other staff member associated with Arch Linux. It's crucial to me that we all operate on a level playing field and that my role doesn't affect the collaborative nature of our team. I may speak on behalf of our AUR maintenance team, but I do so as an equal member, not as a leader who rules on their sole opinion. Sincerely, Levente (while leaving the leadership hat inside the wardrobe)