← Back to team overview

linaro-infrastructure-stakeholders team mailing list archive

Agenda for Infrastructure Stakeholders meeting Sept 1, 2011

 

Greetings.

Going forward I will be chairing the stakeholders meeting to take some load
off James. Please bear with me as I ramp up for this task.

David Zinman
Linaro Release Manager | Platform Project Manager
Linaro.org | Open source software for ARM SoCs

---

 Stakeholders Meeting Agenda September 1, 2011

Actions from last meeting:

* james_w to work with mounir and michaelh to split up the ToolchainBuilds
spec to be more manageable: still TODO

Report on current projects:

* Patch Tracking – Done, one small item outstanding. No high priority bugs.
This project will move to maintenance this week.

* TestDrive – Improved UI planned at Connect and implemented, released as
part of 2011.08. No high priority bugs outstanding. This project will move
to maintenance this week. Platforms will continue to drive adoption of the
project.

* HardwarePacksv2 – Implementation available now. Dev Platform will drive
the transition, doing the testing and switchover. This project will move to
maintenance this week.

* CI with LAVA – several trees and defconfigs building and tested in LAVA
daily. Work will continue as discussed on the techleads list currently, with
Alexander owning the cross-team effort.

* Configure Gerrit - Android team has deployed the tool and is using it.
Work on AOSP mirroring, and bringing up target specific kernel trees are
ongoing.

* Next projects

- Private Hardware Pack Builds – work starting on that this week.

- Improvements to status.linaro.org – work starting on that this week.

* IS Queue

https://portal.admin.canonical.com/q/linaro

Proposed changes to the queues

* There are two free slots on the next projects queue.

* We propose adding "summit.linaro.org enhancements for Connect" to the next
projects queue

* https://wiki.linaro.org/Platform/Infrastructure/Specs/SummitEnhancements

* suggestions for second slot

* I don't think there is anything more urgent that the current

projects and next projects that would warrant dropping anything in progress.

* The IS Queue is still small, and nothing in there is very high priority

that I know of, so I don't think we need to re-prioritize there.

Possible upcoming projects

* Discussion of any projects that people want to propose in the near

future.

Follow ups