maybe somebody else can keep it in better shape.
Dieter Plaetinck dieter@plaetinck.be writes:
maybe somebody else can keep it in better shape.
I'd certainly like to. I'll absolutely be continuing to do some maintenance work on it in the near future regardless.
Hi,
I'm also interested. I would focus on making relatively minor changes to AIF over time, while developing a new installation system in parallel. The new installation system could be made available for testing early on, to gather feedback, but should not replace the old AIF until it was good enough (for some definition of good enough).
If you don't think this is a horrible plan and, after having discussed with me here, don't think I'm a horrible person, then I'm willing to put in some effort.
Jeremiah also seem like a fine gentleman, and I wouldn't mind the slightest if he were elected.
Alexander Rødseth rodseth@gmail.com writes:
Hi,
I'm also interested. I would focus on making relatively minor changes to AIF over time, while developing a new installation system in parallel.
The new installation system could be made available for testing early on, to gather feedback, but should not replace the old AIF until it was good enough (for some definition of good enough).
I would think "working" would suffice :P
If you don't think this is a horrible plan and, after having discussed with me here, don't think I'm a horrible person, then I'm willing to put in some effort.
Jeremiah also seem like a fine gentleman, and I wouldn't mind the slightest if he were elected.
I say if you feel like developing a new installer do it, and talk about it. If you want to help with AIF, do so -- you might also want to take a look at some of the other efforts that are going on at the moment, like archboot[1] .
I'd definitely appreciate it if you either ping me via github or this list wrt AIF work, if only to reduce duplication of effort (and for collaboration), and I'd be more than glad to lend at least an eye to a new install tool effort if it was a promising one.
Reading and modifying AIF's codebase has so far been pretty enlightening in various ways, I'm still working out how to best go about the type of restructuring it seems to be in need of -- one of the major difficulties is that it's hard to test, at least with the resources I have on hand.
Footnotes: [1] https://wiki.archlinux.org/index.php/Archboot
On Tue, 07 Aug 2012 02:26:39 -0400 Jeremiah Dodds jeremiah.dodds@gmail.com wrote:
Reading and modifying AIF's codebase has so far been pretty enlightening in various ways, I'm still working out how to best go about the type of restructuring it seems to be in need of -- one of the major difficulties is that it's hard to test, at least with the resources I have on hand.
it's very useful to have a computer that has hardware virtualisation support, so you can test in virtualbox or qemu-kvm.
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Dieter
On Tue, Aug 7, 2012 at 4:48 AM, Dieter Plaetinck dieter@plaetinck.be wrote:
On Tue, 07 Aug 2012 02:26:39 -0400 Jeremiah Dodds jeremiah.dodds@gmail.com wrote:
Reading and modifying AIF's codebase has so far been pretty enlightening in various ways, I'm still working out how to best go about the type of restructuring it seems to be in need of -- one of the major difficulties is that it's hard to test, at least with the resources I have on hand.
it's very useful to have a computer that has hardware virtualisation support, so you can test in virtualbox or qemu-kvm.
I was using virtualbox, and actually just switched over to qemu-kvm just last night. It's still what I would call "hard" to test, partially from the length of time it takes to run an install, and partially due to me being spoiled by automatic testing tools :P
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
-- Jeremiah
On Tue, 7 Aug 2012 08:21:45 -0400 Jeremiah Dodds jeremiah.dodds@gmail.com wrote:
On Tue, Aug 7, 2012 at 4:48 AM, Dieter Plaetinck dieter@plaetinck.be wrote:
On Tue, 07 Aug 2012 02:26:39 -0400 Jeremiah Dodds jeremiah.dodds@gmail.com wrote:
Reading and modifying AIF's codebase has so far been pretty enlightening in various ways, I'm still working out how to best go about the type of restructuring it seems to be in need of -- one of the major difficulties is that it's hard to test, at least with the resources I have on hand.
it's very useful to have a computer that has hardware virtualisation support, so you can test in virtualbox or qemu-kvm.
I was using virtualbox, and actually just switched over to qemu-kvm just last night. It's still what I would call "hard" to test, partially from the length of time it takes to run an install, and partially due to me being spoiled by automatic testing tools :P
welcome to my world. although for some things you can just run aif on your regular computer; and/or source its libraries (from an interactive bash shell) to check for syntax errors or try out functions.
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
i requested the transfer with github. good luck, and if you have any questions, don't hesitate to get in touch, i'll try to provide feedback where I can (but you can take it in the direction you want)
Dieter
Am 07.08.2012 17:45, schrieb Dieter Plaetinck:
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
i requested the transfer with github. good luck, and if you have any questions, don't hesitate to get in touch, i'll try to provide feedback where I can (but you can take it in the direction you want)
At some point, I'd like to transfer the permissions to the official AIF repo on archlinux.org. I won't do that until I see some work done though. Until then, ask an Arch developer to pull your github.
On Tue, 07 Aug 2012 18:01:43 +0200 Thomas Bächler thomas@archlinux.org wrote:
Am 07.08.2012 17:45, schrieb Dieter Plaetinck:
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
i requested the transfer with github. good luck, and if you have any questions, don't hesitate to get in touch, i'll try to provide feedback where I can (but you can take it in the direction you want)
At some point, I'd like to transfer the permissions to the official AIF repo on archlinux.org. I won't do that until I see some work done though. Until then, ask an Arch developer to pull your github.
the way I saw it, Jeremiah would become the primary maintainer (in his github repo) and we remove http://projects.archlinux.org/aif.git/ quite frankly, that repo has done nothing but causing confusion. I've always preferred github.
now you're basically saying "arch linux developers" are the new aif maintainer. that's fine by me too. I didn't expect any arch devs to be interested in the burden of maintaining aif.
Dieter
On 08/07/2012 07:10 PM, Dieter Plaetinck wrote:
On Tue, 07 Aug 2012 18:01:43 +0200 Thomas Bächler thomas@archlinux.org wrote:
Am 07.08.2012 17:45, schrieb Dieter Plaetinck:
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
i requested the transfer with github. good luck, and if you have any questions, don't hesitate to get in touch, i'll try to provide feedback where I can (but you can take it in the direction you want)
At some point, I'd like to transfer the permissions to the official AIF repo on archlinux.org. I won't do that until I see some work done though. Until then, ask an Arch developer to pull your github.
the way I saw it, Jeremiah would become the primary maintainer (in his github repo) and we remove http://projects.archlinux.org/aif.git/ quite frankly, that repo has done nothing but causing confusion. I've always preferred github.
now you're basically saying "arch linux developers" are the new aif maintainer. that's fine by me too. I didn't expect any arch devs to be interested in the burden of maintaining aif.
Dieter
In my opinion, I see this confusion the primary reason nobody contributes to AIF.
Is AIF an arch project or not?
If is in arch project, then our users should use our bugtracker to report bugs, use arch-releng to send patches.
If not, then why we are discussion this here?
On Tue, 07 Aug 2012 22:20:02 +0300 Ionut Biru ibiru@archlinux.org wrote:
On 08/07/2012 07:10 PM, Dieter Plaetinck wrote:
On Tue, 07 Aug 2012 18:01:43 +0200 Thomas Bächler thomas@archlinux.org wrote:
Am 07.08.2012 17:45, schrieb Dieter Plaetinck:
anyway, i wanted to do "transfer ownership" in github, but it complains because "jdodds/aif already exists" so i'ld suggest you remove your aif repo on github (of course keep your commits locally so you don't loose anything), then i'll transfer ownership.
Done. I'll do my best to take good care of AIF.
i requested the transfer with github. good luck, and if you have any questions, don't hesitate to get in touch, i'll try to provide feedback where I can (but you can take it in the direction you want)
At some point, I'd like to transfer the permissions to the official AIF repo on archlinux.org. I won't do that until I see some work done though. Until then, ask an Arch developer to pull your github.
the way I saw it, Jeremiah would become the primary maintainer (in his github repo) and we remove http://projects.archlinux.org/aif.git/ quite frankly, that repo has done nothing but causing confusion. I've always preferred github.
now you're basically saying "arch linux developers" are the new aif maintainer. that's fine by me too. I didn't expect any arch devs to be interested in the burden of maintaining aif.
Dieter
In my opinion, I see this confusion the primary reason nobody contributes to AIF.
Is AIF an arch project or not?
If is in arch project, then our users should use our bugtracker to report bugs, use arch-releng to send patches.
If not, then why we are discussion this here?
it was. now it's not anymore. because i was the only dev who worked on it and i resigned.
So, AIF is not an Arch Linux project, is not included on the ISO, is not developed by an Arch developer and there may be several competing installers, what will be the criteria for one (or several installers) to be included on the ISO? By package vote, or up to Gerardo Pozzi?
- Alexander
On Wed, Aug 8, 2012 at 12:55 PM, Alexander Rødseth rodseth@gmail.com wrote:
So, AIF is not an Arch Linux project, is not included on the ISO, is not developed by an Arch developer and there may be several competing installers, what will be the criteria for one (or several installers) to be included on the ISO? By package vote, or up to Gerardo Pozzi?
Probably the latter...
arch-releng@lists.archlinux.org