Hi All,
If you're one of the unlucky ones who won't be attending Linaro Connect
Q1.12 next week, you'll be pleased to hear we're enabling remote
participation via Google Hangouts for the 5 morning Session rooms. As
Hangouts allow use of webcams, this will hopefully make it a more
interactive experience for you - for example with webcams located in the
rooms you can see who's in the room and who's talking at any particular time
(and you'll better know who to tell to speak up if they're too quiet J).
We've provided guidelines for remote participation at the bottom of the
Schedule page here:
http://connect.linaro.org/schedule
or directly here:
http://connect.linaro.org/remote
I'm conscious this is the first time we've used this facility, so do let me
know if the guidelines aren't clear. And then I'll also appreciate your
feedback during the week to help us improve next time.
Thx
Stephen Doel
Chief Operating Officer
T: +44 1223 45 00 23 │ M: +44 77 66 014 247
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro/155974581091106>
Facebook | <http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
Hi,
https://wiki.linaro.org/Platform/Android/LinaroAndroidBuildService has
been updated with these instructions about a new build option:
EXTERNAL_TARBALL
Use to request that the build system fetch an archive from the
location that you set EXTERNAL_TARBALL to and unpack it into
build/external_tarballs (build is the build root directory. This exact
path can be written as
$BUILD_SCRIPT_ROOT/../../build/external_tarballs). Multiple archives
can be requested, separated by ";", e.g.
EXTERNAL_TARBALL="http://foo.com/ball1.tar.gz;http://foo.com/ball2.tar.bz2"
There has been some discussion about if the path that is being
unpacked to is easy to use. We could modify the build scripts so we
either set an environment variable to point to where we unpack to
($EXT_TARBALL_DIR) or have a fixed path in /tmp that we soft link from
(/tmp/external_tarballs). If you have a strong opinion, please let me
know.
Thanks,
--
James Tunnicliffe
Hi guys,
As we're almost done with 12.02 planning, I'd like to share the
current blueprints we intend to work during the 12.02 cycle:
https://launchpad.net/linaro-dev-platform/+milestone/12.02
I know this is a quite short cycle, as we'll have the Linaro Connect,
Android Builders and ELC, but I really hope to get most of the
blueprints done during Connect's hacking sessions.
Some interesting topics we'll cover this month:
* Adding the USB-Host enablement test cases at LAVA
* Start testing and validating the daily Linaro Native and Cross GCC packages
* Enable ARMHF Precise based builds
* Update XBMC to the latest 11.0 Beta release (currently Beta 2)
* Sysroot build automation
* Backporting of Unity 5, bringing the latest development from the GWG
* Finalizing the Cross Buildd with Multi-Arch support
And a few other bug fixes :-)
Hope you enjoy ;-)
Cheers,
--
Ricardo Salveti de Araujo
Greeting,
Here is the postmortem and lessons learned for Linaro's first release for 2012.
https://wiki.linaro.org/Cycles/1201/Release/Review
Highlights and Key Successes
============================
The Ubuntu development platform team has delivered Ubuntu TV
fully accelerated on a PandaBoard with Ubuntu LEB and the Ubuntu
TV UI and XBMC also for PandaBoard.
http://www.youtube.com/watch?feature=player_embedded&v=uQMOETMZA5Y
The members demonstration was very successful with the graphics WG,
landing teams, verification team, platform teams and the Igloo community
all contributing some very fine achievements to the effort.
Internal communications have been getting better and there is now a
weekly sync between the platform groups and the working groups that
is similar to the platform - landing team syncs. Each team brings a high
priority issue or but to the table in order to find a plan for resolution.
Postmortem and Lessons Learned
==============================
This cycle seemed to present a challenge to most of the teams to stay
focused on the delivery, There was no release from the Power Management
group, and output was down for the Multimedia, Graphics and Platform
teams. An issue here is that some release procedures are not being
followed by some of the teams.
An important issue that came up this cycle is that platform teams are
requesting the source code for binary blobs. At integration, when an
issue has been found, the path to the person that can fix and regenerate
the binary blob is too long to actually fit the integration into one cycle.
Add to this the requirement to use kernels and toolchains that are not
aligned with the binary blobs and a conflict is created between
development and schedule.
Some of the lessons learned that came out of the cycle are:
* There needs to be offspring knowledge within the infrastructure. The
resource that had this domain knowledge is no longer with Linaro. To
be effective, this knowledge should be brought in house again.
* Listen to community users and incorporate useful information and
go to people directly to get their reviews.
* Need to become better at declaring scope which has good probability
to be delivered at the beginning of the cycle, rather than declaring all
pieces of work that we want to work upon and shed items which are
impeded on the way. Impediments should be highlighted early on to
get resolved.
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
<pfefferz> all right
so welcome to 12.02!
the goal is to mkae snowball work great
and origen
iMX53 is semi blocked
<bero> There's still stuff to try there
<pfefferz> and panda gets a lot of attention
<bero> But it would be really useful to get some more information
<pfefferz> bero, lets hold off on iMX53 until we have more info
<jackh> the three bugs assigned to me, i tried this afternoon, two of them
still there
<pfefferz> can you send the current issue set in?
jackh, cool
<jackh> the gallery one does not there
<pfefferz> did you update the thrid?
that's good
feel free to list the build where you don't see it
in the bug
everyone
we have a new team member
jackh, aka Chenglie
has joined us from IBM
<jackh> it's Chengjie He
<pfefferz> welcome Chengjie
<bero> Welcome jackh
<pabhishek> welcome jackh
<pfefferz> right ;)
<jackh> haha, just call me jacky for short...
<bhoj2> welcom jackh :)
<botao_sun> jackh: I will give you a brief later about compiling the code.
<pfefferz> its great to have you on the Android team Chengjie He
we'll do another welcome round on wednesday ;)
<jackh> pls do it face to face, zach...
haha, joking
<pfefferz> :)
so we're gonna focus on getting our tests all green
its a big job
as usuual
:)
we've had some good pickup by the member companies of our concerns
so we shouldn't be as blocked as we were
we also have connect abs and elc
as a reminder all presentations for elc and abs have to be submitted a
week before the event
also
for everyone doing a session
please have a rough agenda listed
something like
here's where we are
here's where we need to be
I'm going to take a more passive role during other people's sessions this
time
:)
any questions or comments?
<mansson__> Prepare a "lightning talk" version of your session (5 min.)
good to have.
<pfefferz> good point mansson__
<pfefferz> the highest prio thing we have right now
is the demo at connect
most everyone is involoved in getting it to happen
I suspect we'll be spending a bunch of time in the hacking sessions making
it work
I have to get a poster together
so one more thing
people arte really starting to use our builds
1. because they're easy to use
2. they work
3. they can talk to us on irc
this means they're looking at our BPs to see how our work is progressing
so that's all I had
thanks for setting the meeting up Tony
anyone have anything else?
<mansson__> I think everything is pretty clear. We continue to make a
lasting impression on human evolution. Making ARM Linux history.
<pfefferz> exactly!
<mansson__> 15 out of 50 talks at ELC are by Linaro people.
<pfefferz> hehe
not bad for a non-sponser
seriously guys
we're changing the world
every little thing we get working
has a giant impact
okay
<pfefferz> mansson__, would you send this transcript out to everyone?
<mansson__> Yes.
<pfefferz> thanks!