[NOTES] 2011-03-11 Engineering Resources weekly meeting
Matt Waddel
matt.waddel at canonical.com
Fri Mar 11 23:27:14 UTC 2011
Hi,
The minutes from the Engineering Resources team meeting can be found
here:
https://wiki.linaro.org/Mentoring/Status/WeeklyMeeting/2011-03-11
Summary below.
--Matt
=== Action Items from This Meeting ===
* AddNewHardware/HardwarePack pages need to explain kernel packages
as Steve noted below
* HardwarePacks page refers to Maverick instead of Natty
* Mentoring section needs to be renamed and back links should be fixed
* A better header for wiki that includes things like a "Resources"
link in banner/header
* Toolchain documentation improvement
=== Minutes ===
==== Feedback from Steve L ====
* No super hot button issues with team
* come up with clearer idea of what goes in hwpacks and policies
around them
* snag with v310 hwpack. needed u-boot not built by John R
* missing linux-meta package in their hwpack. package name changes
each time ABI is bumped. (Scott has had people confused by
Meta-Packages)
* Do we need new "types/names" of hwpacks for situations like this
* Maybe ER team needs to add some to HWPACK documentation to mention
these things.
* Scott B - ask Andy Green for feedback on documentation changes
* HardwarePacks page refers to Maverick. Should be Natty and probably
say "CURRENT RELEASE"
* documentation under mentoring. needs to be promoted
* rename to how-to
* put something on main page and list latest updates
* suggestions for front page:
* change the way the header looks so that people will actually start
to notice it again. Put some main links in this new header
* joey links:
https://wiki.canonical.com/OEMServices
https://wiki.linaro.org/LinaroHeader
==== Feedback from Scott B ====
* cross-compiler documentation is still confusing
* break up page by 4.4/4.5 versions into 2 pages. and then versions.
* we shouldn't even suggest 4.4. 4.5 is what should be used
* explain why you do a add-apt-repository
* Cross-development Environment for userspace. There's nothing. We
don't have a good story on this. Steve says we're improving so not
spend much time trying to explain
==== Feedback from Kiko ====
* echo steve's comments on hwpacks
* (scott) naming convention for community/landing team to indicate
what is supported
==== Discussion after leads ====
* RequirementsProcessHowto - should be per release for as things change
* ProductRequirement is a little off. Its not needed
* Joey to ask if 1111 release will just use TechnicalTopics or still
do a TechnicalRequirements page
More information about the linaro-dev
mailing list