Hello everyone, My name is Peter and I'm 26 years old. I work as a test and quality engineer and I'm from Augsburg, in Bavaria Germany. In my day-to-day job, I'm working together with car OEMs, Android devices, and their tools, like CANoe, CARMEN, Ellisys, ADB, and others. In the last months, I have seen Christian "gromit" Heusel in several upstream discussions and issues, and we got in contact with each other. We talked about getting more involved in Arch Linux, and this awakened my interest in becoming a package maintainer. My Linux journey started in 2018, beginning with a small project with a Raspberry Pi for my training as an environmental protection technician. I created a project with the "Enviro+ environmental monitoring station", which monitors temperature, pressure, humidity sensors, and others. This was then put together with Prometheus and Grafana into a graphical application, which visualized the values and changes of these. At this time, I also started using Arch Linux distribution on my desktop and learned more and more about Linux. In the meantime, I have learned to work with PKGBUILDs, learned bash, and started to maintain a custom kernel, together with some custom schedulers. In 2021, there was an RFC[1] posted on Arch Linux for the x86-64-v3 micro-architecture port. This got me very interested, and I started the "CachyOS"[2] project with Hamad Marri and Vladislav Nepogodin, which was intended as a learning and enthusiasts project. Over the years, we have integrated the x86-64-v3 and x86-64-v4 integration into this project. Additionally, I have further maintained the custom kernel "linux-cachyos"[3], and also started working together with upstream kernel developers as well as reporting bugs in the kernel community. Currently, in my spare time, I'm mainly maintaining the CachyOS project but also contribute a lot to the sched-ext project, while integrating this into CachyOS as well as doing the testing for the scx-scheds[4] schedulers. I will also be at the Linux Plumbers Conference in Vienna[5] and will give a talk about the integration and benefits of using sched-ext for distributions. I'm also currently maintaing the infrastructure of CachyOS, which includes services like mailserver, mirrors syncing, administration and others. Most of these servers are running on Arch Linux, therefore I have also gained experience in maintaining and managing these. In general, you may know me better by the name "ptr1337". I have reported bugs and suggestions to Arch Linux, as well as helping the Arch Linux-based community. Since the GitLab migration by Arch Linux, I have made a bunch of contributions to packages as well as helping the overall Arch Linux-based community. To further bring more involvement to the upstream Arch Linux project, I am applying as a package maintainer. Also, I could further bring my experience with the x86-64-v3 integration for Arch Linux as well as bringing up discussions from "downstream" distributions. Following packages from the AUR, I would like to maintain in the Arch Linux repository: - scx-scheds (as soon as the sched-ext framework is merged in the mainline kernel) - libpfm (this needs to be discussed with the linux-tools maintainer) - contour - libunicode (dependecy for contour) - boxed-cpp (dependecy for contour) - virtme-ng - llvm-bolt - ananicy-cpp For most of the above packages, I'm directly in contact with the developers as well as contributing and providing testing for these. Following packages in the Arch Linux repository, I could possibly (Co-)Maintain: - bpftop - cosmic group - dkms - wine-staging If there are any other packages that currently lack maintenance and need some help, I'm open to maintaining these. My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other. Best regards, Peter "ptr1337" Jung References ---------- [1] https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0002-march.rs... [2] https://cachyos.org [3] https://github.com/cachyos/linux-cachyos [4] https://github.com/sched-ext/scx/ [5] https://lpc.events/event/18/sessions/192/#20240918 Other Links --------------- Gitlab Arch Linux: https://gitlab.archlinux.org/ptr1337 Github: https://github.com/ptr1337 PKGBUILDs: https://github.com/CachyOS/CachyOS-PKGBUILDS AUR Packages: https://aur.archlinux.org/packages?SeB=m&K=ptr1337
On Mon, 2024-09-02 at 19:07 +0200, Peter Jung wrote:
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
I hereby confirm my sponsorship. Good luck, Peter! Bert.
On 24/09/02 07:07PM, Peter Jung wrote:
Hello everyone,
Hello hello 👋
In the last months, I have seen Christian "gromit" Heusel in several upstream discussions and issues, and we got in contact with each other. We talked about getting more involved in Arch Linux, and this awakened my interest in becoming a package maintainer.
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
I confirm my sponsorship of Peter as I think he is a cool guy and would be a great addition to our team! Good luck in the process and thanks for the detailed application 🤗
Best regards, Peter "ptr1337" Jung
Cheers, Christian
On Mon, 2024-09-02 at 21:59 +0200, Christian Heusel wrote:
I confirm my sponsorship of Peter as I think he is a cool guy and would be a great addition to our team!
Good luck in the process and thanks for the detailed application 🤗
Best regards, Peter "ptr1337" Jung
Cheers, Christian
This marks the start of the discussion period, which will last for two weeks until September 17th. The voting period will start immediately after and will last for seven days. Please use the time to ask anything you'd like to know of Peter, which may or may not be in his application. Also do take a look at his PKGBUILDS. Best, Bert.
On Tue, 2024-09-03 at 07:53 +0200, Bert Peters wrote:
This marks the start of the discussion period, which will last for two weeks until September 17th. The voting period will start immediately after and will last for seven days.
Please use the time to ask anything you'd like to know of Peter, which may or may not be in his application. Also do take a look at his PKGBUILDS.
Best,
Bert.
Reminder, just a few more days of discussion period. Do take the opportunity to ask any questions you might want to have answered. Bert
On 9/2/24 12:07 PM, Peter Jung wrote:
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
I don't know you personally, but as long as you are not named "Jia" and you have Christian and Bert's support - Welcome Aboard! (good luck!) -- David C. Rankin, J.D.,P.E.
Hi, On 03/09/2024 04:23, David C. Rankin wrote:
On 9/2/24 12:07 PM, Peter Jung wrote:
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
I don't know you personally, but as long as you are not named "Jia"
These "jokes" are unwelcome on this mailing list.
On 9/3/24 3:56 AM, Jelle van der Waa wrote:
I don't know you personally, but as long as you are not named "Jia"
These "jokes" are unwelcome on this mailing list.
Jelle, It wasn't a joke -- it was an ice-breaker. Perhaps different in your culture, but not intended as a joke. -- David C. Rankin, J.D.,P.E.
So, if my name would be "Jia" it would be an issue? This joke is really questionable On Tue, 3 Sept 2024, 11:12 David C. Rankin, <drankinatty@gmail.com> wrote:
On 9/3/24 3:56 AM, Jelle van der Waa wrote:
I don't know you personally, but as long as you are not named "Jia"
These "jokes" are unwelcome on this mailing list.
Jelle,
It wasn't a joke -- it was an ice-breaker. Perhaps different in your culture, but not intended as a joke.
-- David C. Rankin, J.D.,P.E.
Don't want to spam the mailing list, but I asked chatgpt [ugjka@ugjka ~]$ sgpt "what is a jia joke" A "jia joke" is a term used to describe a joke that is so bad or poorly constructed that it becomes funny in an ironic way. The humor often comes from the joke's lack of wit, cleverness, or coherence. The term "jia" itself doesn't have a specific meaning in this context; it's just part of the phrase. These jokes are often shared for their sheer absurdity and the amusement that comes from their failure to be traditionally funny.
So, if my name would be "Jia" it would be an issue? This joke is really questionable
On Tue, 3 Sept 2024, 11:12 David C. Rankin, <drankinatty@gmail.com> wrote:
On 9/3/24 3:56 AM, Jelle van der Waa wrote:
I don't know you personally, but as long as you are not named "Jia"
These "jokes" are unwelcome on this mailing list.
Jelle,
It wasn't a joke -- it was an ice-breaker. Perhaps different in your
culture, but not intended as a joke.
-- David C. Rankin, J.D.,P.E.
Uģis Ģērmanis schreef op 2024-09-03 11:30:
Don't want to spam the mailing list, but I asked chatgpt
[ugjka@ugjka ~]$ sgpt "what is a jia joke" A "jia joke" is a term used to describe a joke that is so bad or poorly constructed that it becomes funny in an ironic way. The humor often comes from the joke's lack of wit, cleverness, or coherence. The term "jia" itself doesn't have a specific meaning in this context; it's just part of the phrase. These jokes are often shared for their sheer absurdity and the amusement that comes from their failure to be traditionally funny.
ChatGPT is completely wrong; It's a reference to the XZ backdoor incident, implying he might be a malicious entity trying to be accepted. I don't think that is respectful to the applicant, nor to gromit and myself who vouched for him. Let's stop this discussion. Please focus on Peter's application. Constructive comments welcome.
Hi Peter, On Mon, Sep 02, 2024 at 07:07:00PM +0200, Peter Jung wrote: [...]
In 2021, there was an RFC[1] posted on Arch Linux for the x86-64-v3 micro-architecture port. This got me very interested, and I started the "CachyOS"[2] project with Hamad Marri and Vladislav Nepogodin, which was intended as a learning and enthusiasts project.
Over the years, we have integrated the x86-64-v3 and x86-64-v4 integration into this project. Additionally, I have further maintained the custom kernel "linux-cachyos"[3], and also started working together with upstream kernel developers as well as reporting bugs in the kernel community.
If you're accepted as a package maintainer, will there be any new efforts to bring official x86-64-v3 builds to Arch? This is something that's been stuck in limbo. I'd be very inclined to vote in favor of you joining if you plan to assist with moving us closer to that goal.
Hi T.J., On 03.09.24 16:10, T.J. Townsend wrote:
If you're accepted as a package maintainer, will there be any new efforts to bring official x86-64-v3 builds to Arch? This is something that's been stuck in limbo. I'd be very inclined to vote in favor of you joining if you plan to assist with moving us closer to that goal.
As I wrote in the application, I would welcome to work on this, too. Personally, I really want to see that Arch gets more "modernized" in this topic. I don't know the current state of the integration om archlinux and what you have done internally so far, but im open to work into this and help archlinux getting this goal done.
On Mon Sep 2, 2024 at 7:07 PM CEST, Peter Jung wrote:
Hello everyone,
My name is Peter and I'm 26 years old. I work as a test and quality engineer and I'm from Augsburg, in Bavaria Germany. In my day-to-day job, I'm working together with car OEMs, Android devices, and their tools, like CANoe, CARMEN, Ellisys, ADB, and others.
Servus Peter! 👋
Following packages from the AUR, I would like to maintain in the Arch Linux repository: - scx-scheds (as soon as the sched-ext framework is merged in the mainline kernel) - libpfm (this needs to be discussed with the linux-tools maintainer) - contour - libunicode (dependecy for contour) - boxed-cpp (dependecy for contour) - virtme-ng - llvm-bolt - ananicy-cpp
PKGBUILDs generally look good and according to the guidelines. One thing I noticed was that you still source explicit commits for VCS packages instead of pkgver-tags, e.g. in libpfm: _commit='3d77461cb966259c51f3b3e322564187f4bef7fb' source=("$pkgname::git+https://git.code.sf.net/p/perfmon2/libpfm4#commit=$_commit") b2sums=('4380f73..') This is no longer required since support for VCS checksums was added to pacman - the above can be replaced with: source=("$pkgname::git+https://git.code.sf.net/p/perfmon2/libpfm4#tag=v$pkgver") b2sums=('otherchecksum..')
If there are any other packages that currently lack maintenance and need some help, I'm open to maintaining these.
There sure are, but they're not always so easy to identify, the following pages might give you some ideas of where there is opportunity help out: - Orphaned packages [0]. - Open todos [1]. - Long-out-of-date packages [2].
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
Best regards,
Peter "ptr1337" Jung
All in all, congratulations on a very well-written application. I think you have an impressive track-record and will make a addition to our distribution. Wish you all the best in the application process, good luck! :) [0]: https://archlinux.org/packages/?sort=&repo=Extra&q=&maintainer=orphan&flagged[1]: https://archlinux.org/todo/ [2]: https://archlinux.org/devel/reports/long-out-of-date/ -- Sincerely, Carl Smedstad PGP: 3D309011083BA25E
Servus Peter! 👋 Servus!
Following packages from the AUR, I would like to maintain in the Arch Linux repository: - scx-scheds (as soon as the sched-ext framework is merged in the mainline kernel) - libpfm (this needs to be discussed with the linux-tools maintainer) - contour - libunicode (dependecy for contour) - boxed-cpp (dependecy for contour) - virtme-ng - llvm-bolt - ananicy-cpp PKGBUILDs generally look good and according to the guidelines. One thing I noticed was that you still source explicit commits for VCS packages instead of pkgver-tags, e.g. in libpfm:
_commit=d77461cb966259c51f3b3e322564187f4bef7fb' source=$pkgname::git+https://git.code.sf.net/p/perfmon2/libpfm4#commit=$_commit") b2sums=4380f73..')
This is no longer required since support for VCS checksums was added to pacman - the above can be replaced with:
source=$pkgname::git+https://git.code.sf.net/p/perfmon2/libpfm4#tag=v$pkgver") b2sums=otherchecksum..') Thank you for your review. I will look into these and will adjust the
If there are any other packages that currently lack maintenance and need some help, I'm open to maintaining these. There sure are, but they're not always so easy to identify, the following pages might give you some ideas of where there is opportunity help out:
- Orphaned packages [0]. - Open todos [1]. - Long-out-of-date packages [2]. Thanks, 'll look into these, when the time comes. :)
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
Best regards,
Peter "ptr1337" Jung All in all, congratulations on a very well-written application. I think you have an impressive track-record and will make a addition to our distribution.
Wish you all the best in the application process, good luck! :)
On 07.09.24 12:33, Carl Smedstad wrote: libpfm package. thank you for taking the time to review my application/AUR PKGBUILDs and for your thoughtful response.
[0]: https://archlinux.org/packages/?sort=epo=Extra&q=&maintainer=orphan&flagged[1]: https://archlinux.org/todo/ [2]: https://archlinux.org/devel/reports/long-out-of-date/
Best regards, Peter (ptr1337) Jung
On 9/2/24 7:07 PM, Peter Jung wrote:
Hello everyone,
Hey Peter, Thanks for your application & good luck!
My name is Peter and I'm 26 years old. I work as a test and quality engineer and I'm from Augsburg, in Bavaria Germany. In my day-to-day job, I'm working together with car OEMs, Android devices, and their tools, like CANoe, CARMEN, Ellisys, ADB, and others.
In the last months, I have seen Christian "gromit" Heusel in several upstream discussions and issues, and we got in contact with each other. We talked about getting more involved in Arch Linux, and this awakened my interest in becoming a package maintainer.
My Linux journey started in 2018, beginning with a small project with a Raspberry Pi for my training as an environmental protection technician. I created a project with the "Enviro+ environmental monitoring station", which monitors temperature, pressure, humidity sensors, and others. This was then put together with Prometheus and Grafana into a graphical application, which visualized the values and changes of these.
At this time, I also started using Arch Linux distribution on my desktop and learned more and more about Linux. In the meantime, I have learned to work with PKGBUILDs, learned bash, and started to maintain a custom kernel, together with some custom schedulers.
Nice journey, congrats :)
In 2021, there was an RFC[1] posted on Arch Linux for the x86-64-v3 micro-architecture port. This got me very interested, and I started the "CachyOS"[2] project with Hamad Marri and Vladislav Nepogodin, which was intended as a learning and enthusiasts project.
Over the years, we have integrated the x86-64-v3 and x86-64-v4 integration into this project. Additionally, I have further maintained the custom kernel "linux-cachyos"[3], and also started working together with upstream kernel developers as well as reporting bugs in the kernel community.
Really cool to see people from CachyOS willing to contribute to "upstream"!
Currently, in my spare time, I'm mainly maintaining the CachyOS project but also contribute a lot to the sched-ext project, while integrating this into CachyOS as well as doing the testing for the scx-scheds[4] schedulers. I will also be at the Linux Plumbers Conference in Vienna[5] and will give a talk about the integration and benefits of using sched-ext for distributions.
Interesting, I will definitely watch a replay (if there's one?).
I'm also currently maintaing the infrastructure of CachyOS, which includes services like mailserver, mirrors syncing, administration and others. Most of these servers are running on Arch Linux, therefore I have also gained experience in maintaining and managing these.
In general, you may know me better by the name "ptr1337". I have reported bugs and suggestions to Arch Linux, as well as helping the Arch Linux-based community. Since the GitLab migration by Arch Linux, I have made a bunch of contributions to packages as well as helping the overall Arch Linux-based community.
I confirm I came accros "ptr1337" multiple time in our GitLab issues/MR, providing good quality contributions.
To further bring more involvement to the upstream Arch Linux project, I am applying as a package maintainer. Also, I could further bring my experience with the x86-64-v3 integration for Arch Linux as well as bringing up discussions from "downstream" distributions.
That's definitely something a lot of people (both from staff and users) are looking for, so no doubt that any help/feedback on that matter would be greatly appreciated.
Following packages from the AUR, I would like to maintain in the Arch Linux repository: - scx-scheds (as soon as the sched-ext framework is merged in the mainline kernel) - libpfm (this needs to be discussed with the linux-tools maintainer) - contour - libunicode (dependecy for contour) - boxed-cpp (dependecy for contour) - virtme-ng - llvm-bolt - ananicy-cpp
For most of the above packages, I'm directly in contact with the developers as well as contributing and providing testing for these.
Following packages in the Arch Linux repository, I could possibly (Co-)Maintain: - bpftop - cosmic group - dkms - wine-staging
If there are any other packages that currently lack maintenance and need some help, I'm open to maintaining these.
Your AUR PKGBUILDs all generally look good! Here are a few (definitely non-critical) details I could raise: - forkgram doesn't need to provides nor conflicts its -bin variant [1]. It's up to "derivatives" packages to provide/conflict the "regular" one. - linux-cachyos-lts, linux-cachyos, linux-cachyos-rc, linux-cachyos-bore, linux-cachyos-server shouldn't declare `gcc`, `make` & `patch` as make dependencies [2][3][4][5][6][7][8][9] as they are already provided by the `base-devel` meta package (which is assumed installed when building packages with `makepkg` [10]) - linux-sched-ext-git and linux-tip-git licenses array refer to `GPL2` which is not a valid SPDX license identifier [11][12] (which we are now using in our PKGBUILDs [13]). - scx-scheds-git being licensed under GPL-2.0, there's no need to install the license file on end users' machine [14]. This is a common license is already delivered by the `licenses` package [13]. - The `url` variable should point to the official site of the software being packaged [15], and fallback to the upstream repo only if such official site doesn't exists. For instance, the url for contour [16] should be a link to its official website [17] rather than the GitHub repo (that would imply updating the source array accordingly). - In lapce-git, the source renaming to $_pkgbase [18] is useless as the source is already named that way. - As already raised by Carl, makepkg now supports generating checksums for git sources [19]. That means that you could now points to tags instead of commits in the source array, which should ease the maintenance for libpfm [20]. Again, those are really non-critical details! As said earlier, you PKGBUILDs all look good! :)
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
Best regards,
Peter "ptr1337" Jung
Based on the few times I came accros Peter's name (whether it was directly Arch related or not), he always seemed like a nice, passionate and helpful person; providing good and relevant input & contributions. I think he would be a great addition to the team!
References ---------- [1] https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0002-march.rs... [2] https://cachyos.org [3] https://github.com/cachyos/linux-cachyos [4] https://github.com/sched-ext/scx/ [5] https://lpc.events/event/18/sessions/192/#20240918
Other Links --------------- Gitlab Arch Linux: https://gitlab.archlinux.org/ptr1337 Github: https://github.com/ptr1337 PKGBUILDs: https://github.com/CachyOS/CachyOS-PKGBUILDS AUR Packages: https://aur.archlinux.org/packages?SeB=m&K=ptr1337
[1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=forkgram#n64 [2] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-lts#n20... [3] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos#n182 [4] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-rc#n182 [5] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-bore#n1... [6] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-server#... [7] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-rt#n178 [8] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-hardene... [9] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-echo#n1... [10] https://wiki.archlinux.org/title/PKGBUILD#makedepends [11] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-sched-ext-git#n... [12] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-tip-git#n58 [13] https://wiki.archlinux.org/title/PKGBUILD#license [14] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=scx-scheds-git#n80 [15] https://wiki.archlinux.org/title/PKGBUILD#url [16] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=contour#n9 [17] http://contour-terminal.org/ [18] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=lapce-git#n32 [19] https://gitlab.archlinux.org/pacman/pacman/-/releases/v6.1.0 [20] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libpfm#n17 -- Regards, Robin Candau / Antiz
On 07.09.24 15:19, Robin Candau wrote:
On 9/2/24 7:07 PM, Peter Jung wrote:
Hello everyone,
Hey Peter,
Thanks for your application & good luck!
My name is Peter and I'm 26 years old. I work as a test and quality engineer and I'm from Augsburg, in Bavaria Germany. In my day-to-day job, I'm working together with car OEMs, Android devices, and their tools, like CANoe, CARMEN, Ellisys, ADB, and others.
In the last months, I have seen Christian "gromit" Heusel in several upstream discussions and issues, and we got in contact with each other. We talked about getting more involved in Arch Linux, and this awakened my interest in becoming a package maintainer.
My Linux journey started in 2018, beginning with a small project with a Raspberry Pi for my training as an environmental protection technician. I created a project with the "Enviro+ environmental monitoring station", which monitors temperature, pressure, humidity sensors, and others. This was then put together with Prometheus and Grafana into a graphical application, which visualized the values and changes of these.
At this time, I also started using Arch Linux distribution on my desktop and learned more and more about Linux. In the meantime, I have learned to work with PKGBUILDs, learned bash, and started to maintain a custom kernel, together with some custom schedulers.
Nice journey, congrats :)
In 2021, there was an RFC[1] posted on Arch Linux for the x86-64-v3 micro-architecture port. This got me very interested, and I started the "CachyOS"[2] project with Hamad Marri and Vladislav Nepogodin, which was intended as a learning and enthusiasts project.
Over the years, we have integrated the x86-64-v3 and x86-64-v4 integration into this project. Additionally, I have further maintained the custom kernel "linux-cachyos"[3], and also started working together with upstream kernel developers as well as reporting bugs in the kernel community.
Really cool to see people from CachyOS willing to contribute to "upstream", either if its the kernel, archlinux or others.
Yes, its a really important point for me, trying to contribute and help as much as possible to projects. :)
Currently, in my spare time, I'm mainly maintaining the CachyOS project but also contribute a lot to the sched-ext project, while integrating this into CachyOS as well as doing the testing for the scx-scheds[4] schedulers. I will also be at the Linux Plumbers Conference in Vienna[5] and will give a talk about the integration and benefits of using sched-ext for distributions.
Interesting, I will definitely watch a replay (if there's one?).
Yes, there will be a replay on youtube and also a livestream (but this costs 50€ i guess). Sadly, the time is pretty limited (10min each person), so it will be not too detailed, but we will see how it goes. :)
I'm also currently maintaing the infrastructure of CachyOS, which includes services like mailserver, mirrors syncing, administration and others. Most of these servers are running on Arch Linux, therefore I have also gained experience in maintaining and managing these.
In general, you may know me better by the name "ptr1337". I have reported bugs and suggestions to Arch Linux, as well as helping the Arch Linux-based community. Since the GitLab migration by Arch Linux, I have made a bunch of contributions to packages as well as helping the overall Arch Linux-based community.
I confirm I came accros "ptr1337" multiple time in our GitLab issues/MR, providing good quality contributions.
To further bring more involvement to the upstream Arch Linux project, I am applying as a package maintainer. Also, I could further bring my experience with the x86-64-v3 integration for Arch Linux as well as bringing up discussions from "downstream" distributions.
That's definitely something a lot of people (both from staff and users) are looking for, so no doubt that any help/feedback on that matter would be greatly appreciated.
Following packages from the AUR, I would like to maintain in the Arch Linux repository: - scx-scheds (as soon as the sched-ext framework is merged in the mainline kernel) - libpfm (this needs to be discussed with the linux-tools maintainer) - contour - libunicode (dependecy for contour) - boxed-cpp (dependecy for contour) - virtme-ng - llvm-bolt - ananicy-cpp
For most of the above packages, I'm directly in contact with the developers as well as contributing and providing testing for these.
Following packages in the Arch Linux repository, I could possibly (Co-)Maintain: - bpftop - cosmic group - dkms - wine-staging
If there are any other packages that currently lack maintenance and need some help, I'm open to maintaining these.
Your AUR PKGBUILDs all generally look good!
Here are a few (definitely non-critical) details I could raise:
- forkgram doesn't need to provides nor conflicts its -bin variant [1]. It's up to "derivatives" packages to provide/conflict the "regular" one.
- linux-cachyos-lts, linux-cachyos, linux-cachyos-rc, linux-cachyos-bore, linux-cachyos-server shouldn't declare `gcc`, `make` & `patch` as make dependencies [2][3][4][5][6][7][8][9] as they are already provided by the `base-devel` meta package (which is assumed installed when building packages with `makepkg` [10])
- linux-sched-ext-git and linux-tip-git licenses array refer to `GPL2` which is not a valid SPDX license identifier [11][12] (which we are now using in our PKGBUILDs [13]).
- scx-scheds-git being licensed under GPL-2.0, there's no need to install the license file on end users' machine [14]. This is a common license is already delivered by the `licenses` package [13].
- The `url` variable should point to the official site of the software being packaged [15], and fallback to the upstream repo only if such official site doesn't exists. For instance, the url for contour [16] should be a link to its official website [17] rather than the GitHub repo (that would imply updating the source array accordingly).
- In lapce-git, the source renaming to $_pkgbase [18] is useless as the source is already named that way.
- As already raised by Carl, makepkg now supports generating checksums for git sources [19]. That means that you could now points to tags instead of commits in the source array, which should ease the maintenance for libpfm [20].
Again, those are really non-critical details! As said earlier, you PKGBUILDs all look good! :)
Wow, thank you very much for your detailed review! I will fix these in the next week!
My sponsors are Christian "gromit" Heusel and Bert "bertptrs" Peters. Thanks for guiding me through the application process as well as the nice talk with each other.
Best regards,
Peter "ptr1337" Jung
Based on the few times I came accros Peter's name (whether it was directly Arch related or not), he always seemed like a nice, passionate and helpful person; providing good and relevant input & contributions. I think he would be a great addition to the team!
Thanks for your nice words and i',m looking forward for the votings. :)
References ---------- [1] https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0002-march.rs... [2] https://cachyos.org [3] https://github.com/cachyos/linux-cachyos [4] https://github.com/sched-ext/scx/ [5] https://lpc.events/event/18/sessions/192/#20240918
Other Links --------------- Gitlab Arch Linux: https://gitlab.archlinux.org/ptr1337 Github: https://github.com/ptr1337 PKGBUILDs: https://github.com/CachyOS/CachyOS-PKGBUILDS AUR Packages: https://aur.archlinux.org/packages?SeB=m&K=ptr1337
[1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=forkgram#n64 [2] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-lts#n20... [3] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos#n182 [4] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-rc#n182 [5] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-bore#n1... [6] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-server#... [7] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-rt#n178 [8] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-hardene... [9] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-cachyos-echo#n1... [10] https://wiki.archlinux.org/title/PKGBUILD#makedepends [11] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-sched-ext-git#n... [12] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-tip-git#n58 [13] https://wiki.archlinux.org/title/PKGBUILD#license [14] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=scx-scheds-git#n80 [15] https://wiki.archlinux.org/title/PKGBUILD#url [16] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=contour#n9 [17] http://contour-terminal.org/ [18] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=lapce-git#n32 [19] https://gitlab.archlinux.org/pacman/pacman/-/releases/v6.1.0 [20] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libpfm#n17
Best regards, Peter "ptr1337" Jung
On Mon, Sep 02, 2024 at 07:07:00PM GMT, Peter Jung wrote:
Hello everyone,
Yo! And good luck with your application :)
I will also be at the Linux Plumbers Conference in Vienna[5] and will give a talk about the integration and benefits of using sched-ext for distributions.
I'll be there as well with some people. Got your talk in my calendar and we can grab a beer if you are up for that :) -- Morten Linderud PGP: 9C02FF419FECBE16
On 08.09.24 20:04, Morten Linderud wrote:
On Mon, Sep 02, 2024 at 07:07:00PM GMT, Peter Jung wrote:
Hello everyone, Yo!
And good luck with your application :)
Hi Morten, :)
I will also be at the Linux Plumbers Conference in Vienna[5] and will give a talk about the integration and benefits of using sched-ext for distributions. I'll be there as well with some people. Got your talk in my calendar and we can grab a beer if you are up for that :)
Sure, that sounds good! Lets meet each other. :) See you soon!
participants (11)
-
Bert Peters
-
Carl Smedstad
-
Christian Heusel
-
David C. Rankin
-
Jelle van der Waa
-
Morten Linderud
-
Pasha Finkelshtein
-
Peter Jung
-
Robin Candau
-
T.J. Townsend
-
Uģis Ģērmanis