Hi folks
Multimedia has now its own project group. The linaro-multimedia-wg which
used to be a project is now a project group:
https://launchpad.net/linaro-multimedia-wg
As such it can be used as an "umbrella" for all multimedia projects. For
now there is a general project registered
https://launchpad.net/linaro-multimedia-project. This generic project
can be used to track milestones which do not necessarily release
binaries to our LEBs or upstream.
I have associated this generic project and libjpeg-turbo with
linaro-multimedia-wg project group. Also I will go on creating any
projects which will be releasing binaries for the future releases - the
current understanding is to create the following projects
- x264-arm-optimizations (yang zhang)
- speech-codec-arm-optimizations (rony nandy)
- ucm-audio-integration (wei feng)
One thing to consider is whether we want to merge the first two in 1
project codec-arm-optimizations in order to simplify the discovery of
binary tarball releases through 1 project rather than many - I leave
this decision to you and Kurt. We can take the decision in the meeting
today.
A couple of details to note about the milestones
1. they are marked as YYYY.mm instead of YY.mm (for example 2011.09
instead of 11.09). This is following suite with other projects and
milestones in other WGs.
2. the milestones dates must be exactly 1 week BEFORE the official
release deadline (you can see the official release deadlines in
https://launchpad.net/linaro/11.11), so that we are releasing in time
for the release candidate and the testing process to go ahead prior to
the official release.
Please ask away any questions you may have or voice your concerns.
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Hi folks
Next week (01 September) I'd like to run a retrospective session
looking at August's release, and in particularly discussing
- what went well and we should do again
- what was counter-productive and we should stop doing
- what are the impediments for 1109
- any ideas for improvement of how things get done in Multimedia
I have set up a space in our wiki to gather any comments:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Status/Retrospect…
If we all add feedback in the wiki before the meeting then the
retrospective can be faster and smoother.
If you have suggestions as to how to improve the retrospectives, you can
also forward those to me.
BR,
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-08-23
Please fill in your status - in particular
what has been done (special attention - release 1108. List your
blueprints which have work items targeting 11.08)
what will you work on next
issues/impediments stopping you
Please do that before the meeting so that we do not spend much of the
time chatting over progress - we can use the time to go through issues
really and try to get an action plan to fix them. Pay special attention
to issues related to 1108 release.
thanks,
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-08-16
Folks please go to the page above and update your status for this week.
In a very simple way:
- what is done
- what will be done next (especially anything to release/highlight for
11.08)
- what are the issues you have
Your info should be in place before the weekly meeting tomorrow,
otherwise we will be doing progress reporting through IRC, and that
topic leads to lengthy chats usually.
Many thanks,
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Folks
as part of the effort to improve the way we communicate, and work with
the team colleagues and others, I believe we need to have 1 session each
month looking back at what went right and we should keep doing, what
went wrong and we should get rid of, and what needs tweaking for the
next period.
These retrospectives should not take more time in separate meetings. I
propose we use the team meeting on first Thursday of each month for our
retrospective of the work done in the last month. This way it will not
interfere with the release, and should provide an opportunity to capture
gripes and suggestions which are still relatively fresh in the mind.
If none disagree then we could start with this in the first week of
September? I can also arrange for the discussion to be on IRC or call
whatever you find best.
What do you think?
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Hi folks
following the monthly releases 11.08 is in sight target date is the
25.August. This means
- Time : remember that the RC will be created on the 18th August. That
is almost 1 week away, so flag any issues which may stop you from
releasing. We could ask for a release later, than the 18th but this
could hamper the efforts of the Platform team to test and fix issues so
avoid delays if possible
- any blueprints which will be releasing tarballs as part of the LEBs
should be targeting a project milestone for 2011.08. So far the
following project is shortlisted for a release to our LEBs this month:
MULTIMEDIA: libjpeg-turbo
Each of the blueprints for the libjpeg-turbo 2011.08 milestone needs to
have a headline and acceptance criteria. Check the links below for
examples of what headline/acceptance entries look like:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-upgrad…https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-upgrad…
- any other work which does not release into our official LEBs but
should be highlighted (as a major improvement or achievement), needs to
provide a suitable highlight in the whiteboard for 11.08. Just adding a
sentence with the title "headline" under the 11.08 section of the work
items in the whiteboard would be sufficient. The headline should point
out to a concrete result that the readers can try out (binary, test
result, documentation)
The test content, neon forum seeds and wiki, and openMAX recommendation
are in my opinion not part of the official LEB, so they need to be
highlighted separately in the release announcement. I would then need
the headline for the blueprints associated with these deliverables, to
communicate to the release management.
Let me know if you have any concerns or questions.
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Hi,
We(Linaro) are evaluating to optimize speex using ARM NEON as an open
source NEON optimized version is not available. Please let us know if
someone is already working on it or if some version exists in the open
source community which we might have missed.
Secondly,I want to know if bit exactness is mandatory for the NEON
optimized version with the C only version? and if a lsb mismatch once
in a while is acceptable?
--
Rony Nandy
Multimdedia Working Group,
www.linaro.org │ Open source software for ARM SoCs
Hi,
We(Linaro) are evaluating to optimize speex using ARM NEON as an open
source NEON optimized version
is not available. Please let us know if someone is already working on it
or if some version exists
in the open source community which we might have missed.
Secondly,I want to know if bit exactness is mandatory for the NEON
optimized version with the
C only version? and if a lsb mismatch once in a while is acceptable?
--
Rony Nandy
Multimdedia Working Group,
www.linaro.org │ Open source software for ARM SoCs
