On 7/17/23 07:07, Tomaz Canabrava wrote:
"if we are too strict about following all the rules we will let go people that would be a good fit for the project, for the sake of folloing the process correctly", but processes also are a thing that should evolve.
I don't think it's too strict to say "Before you maintain packages, officially, you should show an interest in maintaining packages, unofficially, and since GPG is a requirement for packaging, you should show us you can do that too" I agree that processes are a thing that should evolve and change but that is something that also has a process. The TU bylaws explain how to apply, and the bylaws can be changed. Case and point, TU has been replaced with Package Maintainer, an entirely new job with different responsibilities. If you disagree with the application process, absolutely open a dialogue and invite discussion.
I fix bugs upstream, work on opensource on my day to day life and on my vacations I travel to teach programming to students with low income. We all work for the common goal, and while the list of things that are not time consuming, they will add and will be time consuming in the end.
Being a package maintainer is more responsibility and work than the things I described. If you're too busy to say Hi in IRC, how will you find time to properly maintain packages?
I guess my overall point is.. WHY do you want to be a Package Maintainer for Archlinux?
To improve the relationship between KDE & Archlinux, having more people that are on those two communities at the same time, to move things faster and help decrease the maintenance burden of a single person taking care of around ~400 pieces of software.
I use KDE/Plasma as my daily driver and I can respect this. I think if you picked any one way to interact more directly with the Archlinux Community, you'd get plenty of YES votes. Despite being a little meh about the application process, your experience is great and your motivation is respectable.