[arch-dev-public] Looking for an Arch ISO maintainer
Hi all, Gerardo has stepped down as Arch ISO maintainer, which makes archiso unmaintained. I've asked Pierres if he was interested in maintaining the project and he is willing to do bug fixes when required but no major maintenance. Which means that we are looking for a new maintainer :-) To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see: - Proper CI / automated testing of the archiso - Reproducible archiso (patches on the mailing list) [1] - Support secure boot [2] - Accessibility improvements (patches available on the mailing list) [3] Please reply if you are interested in becoming an archiso maintainer, so far Alad has shown interested. [1] https://bugs.archlinux.org/task/63683?project=6 [2] https://bugs.archlinux.org/task/53864?project=6 [3] https://bugs.archlinux.org/task/63166?project=6 -- Jelle van der Waa
On 2019-11-08 10:22, Jelle van der Waa wrote:
To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see: [...] - Support secure boot [2] [...] [2] https://bugs.archlinux.org/task/53864?project=6
I am interested in working on Secure Boot, though I think that is more of an administrative rather than a technical challenge, cf. [1], Section "Suggested Action". Daniel Bermond has expressed interest in adopting the necessary shim-efi package [2] to the repositories since he is its current AUR maintainer, I am also happy to co-maintain that package. Best, Jonas [1] https://lists.archlinux.org/pipermail/arch-releng/2019-January/003891.html [2] https://aur.archlinux.org/packages/shim-efi/
On Fri, Nov 08, 2019 at 10:22:44AM +0100, Jelle van der Waa wrote:
Hi all,
Gerardo has stepped down as Arch ISO maintainer, which makes archiso unmaintained. I've asked Pierres if he was interested in maintaining the project and he is willing to do bug fixes when required but no major maintenance. Which means that we are looking for a new maintainer :-)
To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see:
- Proper CI / automated testing of the archiso - Reproducible archiso (patches on the mailing list) [1]
I'm interested on this.
- Accessibility improvements (patches available on the mailing list) [3]
And this. I wonder if me and diabonas could step in and help with all of these issues. Thanks! -Santiago.
On Fri, Nov 08, 2019 at 10:22:44AM +0100, Jelle van der Waa wrote:
Hi all,
Gerardo has stepped down as Arch ISO maintainer, which makes archiso unmaintained. I've asked Pierres if he was interested in maintaining the project and he is willing to do bug fixes when required but no major maintenance. Which means that we are looking for a new maintainer :-)
To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see:
- Proper CI / automated testing of the archiso - Reproducible archiso (patches on the mailing list) [1] - Support secure boot [2] - Accessibility improvements (patches available on the mailing list) [3]
Please reply if you are interested in becoming an archiso maintainer, so far Alad has shown interested.
[1] https://bugs.archlinux.org/task/63683?project=6 [2] https://bugs.archlinux.org/task/53864?project=6 [3] https://bugs.archlinux.org/task/63166?project=6
-- Jelle van der Waa
Hi, Arch-boxes and cloud images rely on the ISO. So I would be interested as well and would definitely help out with automating/testing. chris
On 2019-11-08 10:22:44 (+0100), Jelle van der Waa wrote:
To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see:
- Proper CI / automated testing of the archiso
I agree and was surprised to see, that we don't really have that yet. Automated testing of archiso actually sounds pretty interesting, albeit challenging.
- Reproducible archiso (patches on the mailing list) [1] - Support secure boot [2] - Accessibility improvements (patches available on the mailing list) [3]
I worked on a blocker around this topic (i.e. brltty).
Please reply if you are interested in becoming an archiso maintainer, so far Alad has shown interested.
I'm not exactly blessed with plenty of free time, but I'd be interested in giving it a go. Best, David -- https://sleepmap.de
Em novembro 9, 2019 8:03 David Runge escreveu:
On 2019-11-08 10:22:44 (+0100), Jelle van der Waa wrote:
To be completely honest, I am not sure what maintenance archiso requires but there are a few things I would love to see:
- Proper CI / automated testing of the archiso
I agree and was surprised to see, that we don't really have that yet. Automated testing of archiso actually sounds pretty interesting, albeit challenging.
- Reproducible archiso (patches on the mailing list) [1] - Support secure boot [2] - Accessibility improvements (patches available on the mailing list) [3]
I worked on a blocker around this topic (i.e. brltty).
Please reply if you are interested in becoming an archiso maintainer, so far Alad has shown interested.
I'm not exactly blessed with plenty of free time, but I'd be interested in giving it a go.
Hi All, Love to see a lot of people stepping up to help with archiso. Perhaps we should do feature hunts more often, even for projects that have maintainers. But, we still don't have anyone wanting to become the actual maintainer of archiso to help implement these changes. I don't really see archiso being a handful as it is now. But, that might change with these features being introduced. Whomever takes it, should be able to cope with that. Regards, Giancarlo Razzolini
On 2019-11-11 09:40:14 (-0300), Giancarlo Razzolini via arch-dev-public wrote:
But, we still don't have anyone wanting to become the actual maintainer of archiso to help implement these changes.
I'd be up for it. I have some ideas around certain possible test scenarios in regards to packer and ansible already. What is currently still unclear to me is how the archiso and bootstrap images on our download page are exactly generated from archiso (the actual specific calls) and whether a semi-automated way of doing that exists (I guess this question is aimed towards Pierre). I would like to automate this as far as possible and make this more transparent when maintaining archiso. How do we go on from here? Best, David -- https://sleepmap.de
On Sat, Mar 28, 2020 at 02:11:02PM +0100, David Runge wrote:
On 2019-11-11 09:40:14 (-0300), Giancarlo Razzolini via arch-dev-public wrote:
But, we still don't have anyone wanting to become the actual maintainer of archiso to help implement these changes.
I'd be up for it. I have some ideas around certain possible test scenarios in regards to packer and ansible already.
What is currently still unclear to me is how the archiso and bootstrap images on our download page are exactly generated from archiso (the actual specific calls) and whether a semi-automated way of doing that exists (I guess this question is aimed towards Pierre).
I would like to automate this as far as possible and make this more transparent when maintaining archiso.
How do we go on from here?
Best, David
Hi, just a general idea, but wouldn't it make sense to revive the arch-releng mailing list a bit + found a release engineering team? We got a few additions to our monthly releases: * Arch Linux Docker * Arch Linux Vagrant Boxes * Arch Linux Cloud Images (soon) * Arch Linux Tarball Would be cool, if we could manage to revive the #archlinux-releng channel on freenode, revive the mailing list and maybe even have weekly meetings, like the devops team has. Just my 2 cents, chris
On 2020-03-28 22:33:01 (+0100), Christian Rebischke via arch-dev-public wrote:
just a general idea, but wouldn't it make sense to revive the arch-releng mailing list a bit + found a release engineering team?
We got a few additions to our monthly releases:
* Arch Linux Docker * Arch Linux Vagrant Boxes * Arch Linux Cloud Images (soon) * Arch Linux Tarball
Would be cool, if we could manage to revive the #archlinux-releng channel on freenode, revive the mailing list and maybe even have weekly meetings, like the devops team has.
That sounds like a good idea actually. IMHO the effort to streamline this further is a team effort. A lot of work in the container direction has already been done by you, which is great! The arch-releng mailing list is not dead though. Contributions are happening, but unfortunately there's noone to merge them after review currently. I didn't even know #arch-releng existed. Idling there now! :) Also, I got an offlist offer for help from someone who has seemingly been working towards build automation of sorts. I guess someone needs to add my SSH key to the repo for things to progress further. Best, David -- https://sleepmap.de
Em março 28, 2020 10:11 David Runge escreveu:
On 2019-11-11 09:40:14 (-0300), Giancarlo Razzolini via arch-dev-public wrote:
But, we still don't have anyone wanting to become the actual maintainer of archiso to help implement these changes.
I'd be up for it. I have some ideas around certain possible test scenarios in regards to packer and ansible already.
What is currently still unclear to me is how the archiso and bootstrap images on our download page are exactly generated from archiso (the actual specific calls) and whether a semi-automated way of doing that exists (I guess this question is aimed towards Pierre).
I would like to automate this as far as possible and make this more transparent when maintaining archiso.
How do we go on from here?
Best, David
Hi David, Thanks for coming forward to handle this. I'm going to set your write access to the git repository for Archiso. Regards, Giancarlo Razzolini
participants (6)
-
Christian Rebischke
-
David Runge
-
Giancarlo Razzolini
-
Jelle van der Waa
-
Jonas Witschel
-
Santiago Torres-Arias