Sugar on a Stick v3 "how did we do?" release review meeting
by Mel Chua
How did the Mirabelle release cycle go? We're gearing up for making
v4, and want to know what went well and what could have been better -
everything from technical to deployment to documentation to process
sustainability to... well, really, everything!
Our next weekly meeting (Monday May 31, 1900 UTC in #sugar-meeting on
irc.freenode.net) will be about exactly that. We announced this date
several weeks back, but now that the release is out and the meeting
date near, it's time for a reminder.
If you can't make the meeting, no worries (especially since Monday is
a holiday in the US). This meeting is intended to get as much feedback
out at one time as possible; release planning for v4 is a separate
meeting (June 7th, again at 1900 UTC) that will take the feedback from
this release review into account." Anything sent in before that
meeting will be considered during the initial v4 planning session.
if you can't make the meeting (or even if you can) and have thoughts
or suggestions you'd like to share, please send them to
soas(a)lists.sugarlabs.org or add them directly to the agenda,
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_meetings#Agenda (which
includes links to the email feedback I've seen so far). Note that you
need to be a member of the soas list to post to it, so if you aren't
subscribed, feel free to email it just to me with a request to forward
to the list, and I'll do so. I'm only gathering feedback that appears
on the soas list, though, in order to preserve my sanity - so if you
reply to any of the other lists, we may not see it in time.
The three questions to answer:
1. What went well with Mirabelle?
2. What didn't?
3. How would you change things?
And then, of course, whatever else you'd like to write.
--Mel, who was somehow inadvertently persuaded by Peter and Sebastian
to chair this meeting
13 years, 10 months
who is being shown in Neighborhood View
by Mikus Grinbergs
Been trying out os240py. My current setup is an ethernet LAN, with *no*
DHCP server. It was interesting to note (just by changing the
/etc/resolv.conf content, plus clicking on an AP icon) that when I do
not have a valid /etc/resolv.conf file, Neighborhood View shows the XOs
on my local LAN; whereas when I do have a valid /etc/resolv.conf file,
Neighborhood View shows the XOs connected to the "My Settings" specified
Jabber server (on the internet).
mikus
13 years, 11 months
[OT] Does ad-hoc network depend on "security through obscurity ?"
by Mikus Grinbergs
OFF TOPIC
I've been currently using an Ad-Hoc wireless network (set up by clicking
in an XO's palette at the gray icon in Frame) for testing collaboration.
That network is performing well, and has been reliable.
But this was on channel 1. Can neighbors (or drive-bys) connect to it?
And what is my legal liability if they do?
[In the news there has been a story about a German court holding someone
responsible for having an "unprotected" home wifi, to which someone else
connected, and used to download copyrighted material without permission.
Also a story about the vehicles Google used to capture images for its
"StreetView" mapping service -- apparently they in addition recorded the
locations of the "wifi hotspots" they encountered.]
mikus
13 years, 11 months
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
http://spins.fedoraproject.org/soas/.
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
http://wiki.sugarlabs.org/go/0.88/Notes.
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
http://download.sugarlabs.org/soas/docs/customization-guide/.
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!
Sebastian Dziallas
Sugar on a Stick Project Lead
13 years, 11 months
kernel modules question
by Joshua Daniel Franklin
Is there a special advantage to using "make xo_1_defconfig" instead of
just copying over a stock Fedora 11 .config file?
I've compiled a module but it looks like I need a couple dependencies
so I'm wondering if just compiling the kitchen sink would be easier
than searching through "make menuconfig".
I'm running the latest XO-1 kernel from
http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/
I did basically this on a CentOS 5 machine:
lsb_release -d
# Description: CentOS release 5.5 (Final)
yum -y install gcc make ncurses ncurses-devel glibc glibc-devel
glibc-headers rpmdevtools rpm-build
adduser olpcdev
su - olpcdev
rpmdev-setuptree
# look for the latest 60M src rpm here:
# http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/?C=M;O=D
wget http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/kernel-2.6.31_xo1-20100505...
rpm --nomd5 -i kernel-2.6.31_xo1-20100505.1835.1.olpc.b072a92.src.rpm
cd ~/rpmbuild/SOURCES/
tar jxf olpc-2.6.tar.bz2
cd linux-2.6.31
make clean distclean
make ARCH=i386 INSTALL_MOD_STRIP=1 xo_1_defconfig
make ARCH=i386 INSTALL_MOD_STRIP=1 menuconfig
# activate bluetooth or whatever
make ARCH=i386 INSTALL_MOD_STRIP=1 modules
13 years, 11 months
New XO-1.5 10.2.0 build 125
by Chris Ball
http://wiki.laptop.org/go/F11_for_1.5
http://build.laptop.org/10.2.0/os125
Compressed image size: 677.88mb (+0.77mb since build 124)
Description of changes in this build:
* Record: Another attempt to fix Record sync, this time by writing
intermediate files to a tmpfs, to avoid jitter due to slow SD writes.
* powerd: inhibit idle suspend for 1 min after waking from sleep
* usb_modeswitch, tcl: include for GSM modem support (#9684)
* Pull F11 updates.
Package changes since build 124:
+NetworkManager-0.7.2.996-1.fc11.i586
-NetworkManager-0.7.2.997-1.fc11.i586
+NetworkManager-glib-0.7.2.996-1.fc11.i586
-NetworkManager-glib-0.7.2.997-1.fc11.i586
+NetworkManager-gnome-0.7.2.996-1.fc11.i586
-NetworkManager-gnome-0.7.2.997-1.fc11.i586
+elfutils-libelf-0.145-1.fc11.i586
-elfutils-libelf-0.147-1.fc11.i586
-olpc-powerd-21-1.fc11.i586
+olpc-powerd-22-1.fc11.i586
+tcl-8.5.6-6.fc11.i586
+usb_modeswitch-1.1.2-3.fc11.i586
+usb_modeswitch-data-20100418-2.fc11.noarch
13 years, 11 months
Re: [support-gang] XO 1.5 troubles: Touchpad has become non-responsive after an update
by Mikus Grinbergs
Kevin wrote
>> [ If the mouse was not working, how did you get from Sugar to GNOME ? ]
>
> 1. Ctrl-Alt-Neighborhood (a.k.a. Ctrl-Alt-F1) gets me to the shell as root.
> 2. "nano -bkw /home/olpc/.olpc-active-desktop"
> 3. Change "sugar" to "gnome"
> 4. Save and reboot
>
> Non-shell-users: Note the period at the start of .olpc-active-desktop.
Interesting. There is no such file on my XO-1.5 (nor on any XO-1).
Is that because I normally never switch between Sugar and GNOME ?
mikus (XO-1.5 B2, q3a39b, os125)
13 years, 11 months
Record-77 in os125
by Mikus Grinbergs
Disclaimer: I am not asking for help; I am sharing my experience.
Ran Record-77 with os125. In general, I'm satisfied with how it works
(but with 'high' quality I did experience the ticket #10165 problem).
Etoys still has a problem playing the recorded video (and with audio,
only one of the three options Etoys offered me would work).
It was interesting that JukeBox-19 correctly played back both the video
clip made by Record and the audio clip made by Record. [As did Browse.]
[Note: on F11-on-XO1, Record-77 shows black where the image should be.]
mikus
13 years, 11 months
Re: [Sugar-devel] Sugar 0.88 packages
by Bernie Innocenti
El Fri, 14-05-2010 a las 08:59 +0200, Tomeu Vizoso escribió:
> I'm just asking for someone to propose a set of concrete and coherent
> changes to the current process, is it really asking too much?
>
> I'm sorry but I cannot go through the old threads, ask individuals for
> clarifications, then draft that new process myself.
Do you want the proposal posted to the wiki?
We could basically take Sasha's original plan and copy it to the wiki. I
think it was quite well thought:
http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023410.html
I propose the following amendments:
1) Scrap the paragraph saying that any sugar developer can approve
changes, because it turned out to be a controversial point. The "who"
and the "where" of reviews are orthogonal topics that can be discussed
independently.
2) Also scrap the part where Sascha proposes ways to track patches in
the list, since we can now use Patchwork for this.
3) Add all the clarifications in my follow-up to Sascha's proposal:
http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023468.html
4) The existing conventions still apply for referencing tickets in the
commit logs
5) When a corresponding ticket exists, the committer should add a link
to the patch discussion in Patchwork before committing the patch.
Does this sound good enough for an initial iteration? If so, I could
take care of transcribing it into the wiki. Then, we can further refine
the process as we go.
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
13 years, 11 months
