Spin Maintainers, may I please have your attention.
To be included in the Fedora 10 release cycle, you'll need a Feature page in category ProposedFeature (and change that to the ProposedFeatureF10 category when you feel the Spin Concept is ready for actual inclusion). This page should be ready (eg. prepared) before the Alpha freeze.
The Feature Page for that spin should have a short description of the spin concept, it's target audience, any notes you want to write down on why it is you do foo or bar. It should also contain a link to the kickstart, but since a mailing list is still pending, I suggest you email it to fedora-livecd-list@redhat.com. The Spin SIG picks it up, does a technical review, and sends you the OK or comments. If the Spin SIG approves, your kickstart will be added to the GIT repository for the appropriate branch(es). At this point, it'll be forced to use "generic-logos", still. The Spin SIG will work with you to fit in the kickstart into the pool, get some things right or more right, and while you -by then at least-, should also have commit "access to the GIT repository"[1], the spin concept will continue it's path to the Board for trademark approval. Make sure that before this happens, you have some kind of strong argument in favor of the spin so they just can't say no. It makes all our lives easier ;-) Once you're kickstart (spin concept) has the almighty Board trademark approval stamp, we change "generic-logos" back to "fedora-logos".
The kickstart should be built upon fedora-live-base.ks in the spin-kickstarts repository at:
http://git.fedorahosted.org/git/?p=spin-kickstarts.git
This GIT repository has several branches: master, and a very distinctive branch for each live release of Fedora out there. Naturally, the master branch is where development goes against rawhide, and the release specific branches is where you have a chance to maintain your spin concept for the duration of the lifecycle of that release.
Basing on fedora-live-base.ks may be deferred from such as with the Electronic Lab DVD spin: it bases itself on the KDE CD spin so that minimal overhead in duplicate configuration and scripts is accomplished. You may do the same; as long as you make sure you tell us in your Feature page or technical review request. And if you don't tell us in your Feature page, I'll read it from the kickstart anyway.
For now, you are requested to start filling out your spin's Feature page, get them to the Spin SIG (members are on [2]), request access to the gitspin-kickstarts group[1] in FAS, and start composing every two weeks or so, to verify rawhide hasn't changed too much.
To watch commits to the spin-kickstarts GIT repository, subscribe to the spin-kickstarts-commits list[3]
I'd love to see you all come back to me in the next week or so ;-)
Thanks in advance,
Kind regards,
Jeroen van Meeuwen -kanarip
[1] https://admin.fedoraproject.org/accounts/group/view/gitspin-kickstarts
[2] http://fedoraproject.org/wiki/SIGs/Spins (members, guidelines, DOs and DONTs)
[3] https://fedorahosted.org/mailman/listinfo/spin-kickstarts-commits
Jeroen van Meeuwen wrote:
Spin Maintainers, may I please have your attention.
To be included in the Fedora 10 release cycle, you'll need a Feature page in category ProposedFeature (and change that to the ProposedFeatureF10 category when you feel the Spin Concept is ready for actual inclusion). This page should be ready (eg. prepared) before the Alpha freeze.
All or just new spins (ie, where to Desktop, KDE, and other existing ones fall)?
-- Rex
Rex Dieter (rdieter@math.unl.edu) said:
Jeroen van Meeuwen wrote:
Spin Maintainers, may I please have your attention.
To be included in the Fedora 10 release cycle, you'll need a Feature page in category ProposedFeature (and change that to the ProposedFeatureF10 category when you feel the Spin Concept is ready for actual inclusion). This page should be ready (eg. prepared) before the Alpha freeze.
All or just new spins (ie, where to Desktop, KDE, and other existing ones fall)?
From talking to people, this is 'all spins which are not part of the
'normal' set (i.e., Fedora install set, Desktop live, KDE live.)
Bill
Bill Nottingham wrote:
Rex Dieter (rdieter@math.unl.edu) said:
Jeroen van Meeuwen wrote:
Spin Maintainers, may I please have your attention.
To be included in the Fedora 10 release cycle, you'll need a Feature page in category ProposedFeature (and change that to the ProposedFeatureF10 category when you feel the Spin Concept is ready for actual inclusion). This page should be ready (eg. prepared) before the Alpha freeze.
All or just new spins (ie, where to Desktop, KDE, and other existing ones fall)?
From talking to people, this is 'all spins which are not part of the
'normal' set (i.e., Fedora install set, Desktop live, KDE live.)
Should I submit feature pages for games and xfce spin and does it have to be done for each release? I am not sure I understand the purpose.
Rahul
Rahul Sundaram wrote:
Bill Nottingham wrote:
Rex Dieter (rdieter@math.unl.edu) said:
Jeroen van Meeuwen wrote:
Snip...
I just have to say this thread somewhat continued on fedora-devel instead... Sorry for the inconvenience of everyone following the thread here... If you want to read the answers to some of the questions asked, here's the archive link to this thread:
https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00686.html
Kind regards,
Jeroen van Meeuwen -kanarip
Jareon et al,
I am interested in creating a sping that is designed for accessibility (includes brltty, emacspeak, orca etc).
I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd.
When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems.
The steps I took were:
$ livecd-creator -c fedora-live-base.ks -f base the base.iso was created. wodim -dao dev=0,0,0 base.iso
The cd was burned without errors.
reboot
after teh timeout from isolinux, I get a ton of errors.
Since I am blind, it is difficult for me to debug the startup process without sighted assistance, and I wish there were a way to use qemu to test the iso before burning it to a cd, but as far as I can tell qemu is not accessible :)
Any suggestions would be appreciated.
-----Original Message----- From: Jeroen van Meeuwen [mailto:kanarip@kanarip.com] Sent: Sunday, July 13, 2008 7:20 AM To: fedora-livecd-list@redhat.com Subject: Re: [Fedora-livecd-list] Re: Attention Spin Maintainers
Rahul Sundaram wrote:
Bill Nottingham wrote:
Rex Dieter (rdieter@math.unl.edu) said:
Jeroen van Meeuwen wrote:
Snip...
I just have to say this thread somewhat continued on fedora-devel instead... Sorry for the inconvenience of everyone following the thread here... If you want to read the answers to some of the questions asked, here's the archive link to this thread:
https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00686.html
Kind regards,
Jeroen van Meeuwen -kanarip
-- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
On Sun, 2008-07-13 at 15:25 -0700, DON.RAIKES@ORACLE.COM wrote:
I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd.
When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems.
Errors there tend to indicate either 1) Burn problems 2) Problems in the created initrd. The latter could be that you're using a distro which doesn't have the right mkinitrd bits or some other mismatch. It's hard to say without knowing what the actual errors are
Jeremy
Hi Jeremy,
I just installed fedora 9 over the weekend (and again this morning had some issues with it).
I am hoping hte issues I ran into yesterday were causing hte problems. I suspected the burning process originally since when I tried ot burn a dvd on my dvdrw drive wodim said it couldn't handle it at all.
I'll try the base kickstart again tonight or tomorrow and see what happens now.
-----Original Message----- From: Jeremy Katz [mailto:katzj@redhat.com] Sent: Monday, July 14, 2008 12:17 PM To: fedora-livecd-list@redhat.com Subject: RE: [Fedora-livecd-list] Re: Attention Spin Maintainers
On Sun, 2008-07-13 at 15:25 -0700, DON.RAIKES@ORACLE.COM wrote:
I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd.
When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems.
Errors there tend to indicate either 1) Burn problems 2) Problems in the created initrd. The latter could be that you're using a distro which doesn't have the right mkinitrd bits or some other mismatch. It's hard to say without knowing what the actual errors are
Jeremy
-- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Hello,
I am trying to create a livecd based on the fedora spins project's fedora-live-base.ks file. My livecd is going to be a console-only cd (no gui).
My problem is that I cannot get sound working on the cd. I have added the alsa-lib and alsa-utils packages but no success so far.
I am not finding an alsa-drivers rpm anywhere that I can add to the cd.
Any suggestions would be appreciated.
On Mon, 2008-08-11 at 12:31 -0700, DON.RAIKES@oracle.com wrote:
I am trying to create a livecd based on the fedora spins project's fedora-live-base.ks file. My livecd is going to be a console-only cd (no gui).
My problem is that I cannot get sound working on the cd. I have added the alsa-lib and alsa-utils packages but no success so far.
I am not finding an alsa-drivers rpm anywhere that I can add to the cd.
The alsa drivers are included in the kernel. You shouldn't need any other packages
Jeremy
livecd@lists.fedoraproject.org