by Paul W. Frields
Despite a posting to the lists earlier in the month to check our
spin content, apparently no one caught the fact that there was no
Moblin spin among the release candidates. At this point, we're going
to have to wait for mirrors to die down before we can consider
shipping a late copy.
I went to the Spins process page to see where things might have gone
off track, and found that the page stated that after acceptance the
following step occurs:
"Spin added to a wiki page containing a table listing all of the spins
for Fedora X (very similar to
Note that no one is responsible or accountable for it happening
according to the spin page, nor is the proper page listed. I made
a change, so now the step reads:
"The Spins Wrangler adds the Spin to a wiki page containing a table
listing all of the spins for Fedora 14
This change is not a decree by any means, but it seemed like the most
effective way to ensure entries get made.
I can't help but think we would have caught this problem if there were
regular Spins meetings, or at least schedule items that indicate the
SIG should carry out a task like checking the list of Spins before RC
phase. Earlier, I brought up the idea of entering a set of schedule
items. Ideally, someone on the SIG will step up to gather that list
of dates for Fedora 14, and talk to John Poelstra to make sure the
dates get on the release schedule. I'd also like to make sure we have
a clear spins wrangler who knows the responsibilities that come with
that role. That person should check over the spins process page
and find any places where it's not clear what the task is, and who is
responsible for doing it.
So -- who wants to gather the schedule and report it to John Poelstra
by around June 1?
Who is the current spins wrangler, and can that person go over the
page by around the same time, and bring questions to the list?
* * *
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
12 years, 8 months
Re: [Fedora-spins] MIA spins
by Peter Robinson
On Thu, May 27, 2010 at 7:50 AM, Rahul Sundaram <metherid(a)gmail.com> wrote:
> On 05/27/2010 12:15 PM, Bruno Wolff III wrote:
>> On Thu, May 27, 2010 at 07:37:48 +0100,
>> Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>> WooHoo... nearly 2 days after the release and there's still no signs
>>> of the Moblin spin. I'm not going to yell and scream like some would
>>> about their spin but it would be nice to see some kind of update as to
>>> why its still missing? I don't see that request as being unreasonable
>>> after all I feel I put as much work into my spin and it can't help to
>>> feel to me a little unfair and disappointed. If it was some other spin
>>> all hell would have broken lose.
>> I think that would depend on which spin. This isn't the first time something
>> bad has happened with a spin. I don't remember hell breaking loose in the
>> Certainly it is unfortunate and disappointing that it happened.
> I have long since advocated that spin owners be granted access in Fedora
> infrastructure to compose their own spins and release engineering not
> take this role. The current method is simply not scaling well and we
> have seen enough proof of that by now.
I'm not sure the pros and cons to the above, or whether there's
something as basic as access to signing keys that might restrict that.
I'm quite happy for the infra team to deal with it, generally they've
done a sterling job and I hope to see Moblin spin shortly, pity its
well behind the watershed and the MeeGo 1 release will no doubt dampen
down the effect but that is life.
What I would like is a much better defined spin process. I've been
involved in the spin process for 2 releases now, managed to miss the
boat with F-12 because there was no where on the spin process and no
prior announcements to cut off dates. I actually made it in with 2
spins this process (maintain moblin, co-maintain sugar on a stick) but
it was certainly not without issues.
Announcing Sugar on a Stick v.3 (Mirabelle)
by Sebastian Dziallas
Mirabelles have arrived! (http://www.flickr.com/photos/enil/3892066169/)
I am proud to announce the availability of Sugar on a Stick v.3,
code-named Mirabelle. More information about Sugar on a Stick,
including download and installation details, are available at
Changes in Sugar on a Stick since the last release (v.2 Blueberry):
Sugar version 0.88. The most recent release of the Sugar Learning
Platform features support for 3G connections, increased accessibility,
and better integration with our Activity Portal
(http://activities.sugarlabs.org) allowing students and teachers to
update their sticks with additional Activities. More information about
the 0.88 release of Sugar is available at
Customize your own remix of Sugar on a Stick. You'll notice that v.3
Mirabelle has a smaller Activity selection than its predecessors,
Blueberry and Strawberry. We realized we'll never be able to create an
Activity selection suitable for all deployments - instead, we've
chosen to include and support a core set of basic, teacher-tested
Activities in the default image, and invite deployments to use this as
a base on which to build a customized Activity selection for their
classrooms. Instructions on how to do this are available at
Sugar on a Stick is now a Fedora Spin. After two prior releases of
being based on the Fedora distribution, Sugar on a Stick has
recognized by the Fedora Project as an official Spin. This ties us
more closely to Fedora's release cycle and gives us resources from
their engineering and marketing teams, which extends the reach of
Sugar on a Stick and makes the project itself more sustainable. In
exchange, users of Fedora have access to an easily deployable
implementation of the Sugar Platform; it's a great example of a
mutually beneficial upstream - downstream relationship.
The biggest difference in v.3 of Sugar on a Stick has been in its
release processes and engineering sustainability; it's now much easier
for new contributors to get involved. We continue to move towards our
long-term vision of bringing stability and deployability to Sugar's
personalized learning environment, and invite all interested parties
to join us.
If you'd like to contribute to the next version, due for release in
early November, join us at our Contributors Portal at
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick. All types of
contributions are welcome, from the technical to the pedagogical, and
we're happy to teach what we know and learn what you have to share.
Thank you especially to the Sugar on a Stick team and all the people
involved for their awesome work on this release!
Sugar on a Stick Project Lead
-kdebluetooth still valid when creating spin
by Shakthi Kannan
1. Does the option -kdebluetooth in a kickstart file still remove KDE
from a custom spin? I get the message:
No such package kdebluetooth to remove
when building a spin.
2. To create a LiveDVD, I require the following .ks files apart from
the custom spin .ks file?