On 7/17/23 04:27, Tomaz Canabrava wrote:
>
>
> On Mon, 17 Jul 2023 at 11:18 Jonathan Steel <jsteel@archlinux.org
> <mailto:jsteel@archlinux.org>> wrote:
>
> On Mon 17 Jul 2023 at 10:44, Tomaz Canabrava wrote:
> > Because I don’t have a gpg key, and when the dkim features on the
> email
> > already are enough to validate that the email I send is from me.
>
> You will need a GPG key to package. Arch has rules about applying
> and you are
> openly not following them.
>
>
> I’ll create a gpg key when/if I need, to sign the packages, if arch
> Linux votes for me.
>
>
> > i won’t re-apply because that’s a waste of everyone’s time just
> for the sake
> > of ticking boxes.
>
> I consider an application that does not meet the requirements and
> has had very
> little effort put in to be a waste of time.
>
>
> That’s true, and I guess I already have your -1 on the votes. Great
> meeting you :)
>
> Besides not following rules, I help to maintain with patches upstream as
> a maintainer, co-maintainer or just a random person sending patches
> fixing bugs the following software set:
So which is it, (co/)maintainer or random person sending patches?
Both, but, let me clarify:
- I am a KDE developer, you can check my credentials and my name is on the KDE ev Members list here:
I'm one of the most active developers on Konsole, and one of the core deelopers of Plasma Firewall.
I also worked with Subsurface for many years porting the software from Gtk to Qt - and I'm one of the top 5 developers there.
The other softwares in the list that *are not* from kde software I'm just a random person contributing on my spare time because I like it.
I have never - on my 18 years of coding - worked with opensource because it was paid, and I contribute since my university days because I *sincerely* like it.
I've
sent patches for Pacman and other Arch Projects but that does not make
me an Archlinux Developer. (I mean, I can call myself whatever I want so
I suppose it does but that is irrelevant.)
> - kde plasma
> - plasma firewall
> - dolphin
> - ark
> - kde system settings
> - Konsole
> - qgroundcontrol
> - konversation
> - kio
> - kde partition manager
> - subsurface
> - kde frameworks
> - codevis
> - kconfigxt
>
> But in the end it’s the maintainers role to see if someone from upstream
> would be useful for arch as a packager, or if he just wants to waste
> more time of a non-paid position for no glory just for the sake of
> helping a distro he uses daily.
I'll gladly waste time on a non-paid position for no glory for the sake
of helping the distro I use daily. It's called "contributing".
That's what I do for more than 18 years. We know that written text lacks tone, so I'll clarify that thing too:
"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.
https://wiki.archlinux.org/title/Getting_involved
I maintain AUR packages, troll #aot on IRC, report bugs and try to help
track them down, use the testing repos and sign off on newly updated
packages.. None of these things is difficult or overly time consuming
and making yourself known by doing any one of them will have a
significant positive impact on your application.
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.
> Today I’ll create an aur component for Codevis, a software to
> visualize large architectures Im developing for the past three years
> (that just got opensourced)
>
> And I’ll also create a GPG key, and sign some email on this thread with it.
I like seeing new stuff going into the AUR. I forgot to mention the
handful of packages i found on github just to put in the AUR. For
nothing more than funsies, but they're being used by people which is
awesome. (And entirely the point.)
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.