linaro-infrastructure-stakeholders team mailing list archive

[James Westby <james.westby@xxxxxxxxxx>]

Hi,

1. Report on the current status

   https://wiki.linaro.org/Platform/Infrastructure/CurrentProjects
 
   * 2 projects moved to maintainence
     - Initial work on https://android-build.linaro.org/
       - Moving to more carefully defined chunks of work on this service
       now.
     - Initial work on continuous integration.
       - Aligning work with validation efforts to get testing on real
         hardware.
   * 3 projects started
     - The android-build.linaro.org and continuous integration work
       mentioned above.
     - https://wiki.linaro.org/Platform/Specs/11.11/HardwarePacksV2
       from the "Next" queue to improve hardware packs.
     - All of these are in the early stages.
   * The other projects progressing
     - offspring.linaro.org is available and we are about to start
       testing the results before switching to it for 11.06.
     - PatchTracking has good development progress, and deployment is in
       progress.
     - TestDrive should have a version that can be tested within Linaro
       very soon.

   * The current IS RT queue is as follows:

     * Please set up a patchwork instance for Linaro
       - In Progress
     * script up the sync of moin ACLs and LP teams
       - Will fix a number of problems with access to private areas of
         the wiki.
     * Private hosting area for hwpacks
       - Needed for the LTs to be able to easily share hwpacks within
         the team that they can't share with the rest of Linaro or the
         world.
     * Deployment scenario for dashboard.linaro.org
       - Getting updated code on dashboard.linaro.org
     * Please help run a script to add Linaro tweets to the Linaro wiki
       - Give a sense of the life on Linaro to the wiki.
     * Please provide an instance of gerrit for Linaro
       - Code review for the Android team.
     * Please install a logbot on linaro* irc channels
       - Logging of the channels for ease of searching, as well as
         making it easier to generate statistics.
     * And more that is lower priority currently...

2. Proposal for changes to the current state

  * We have one free slot on the next queue. These are the current
    proposals that I have for what could fill that slot:

    * ImageBuildPolish
      - Rsyncable images, one-click releases
    * BetterBugtrackerReports
      - A more powerful interface to produce reports on the status of
        the bug database, for instance better searching, sorting or
        grouping.
    * BuildLogScanning
      - Scanning of Ubuntu package build logs to look for potential
        problems. This could also be used to e.g. extract binary sizes
        if we changed package builds to report them.
    * BugMetrics
      - Reports over time of state of the bug database. Capturing things
        like number of open bugs, and age of bugs in different states.
    * ImageLicenseAnalysis
      - Automated checking of the licenses that make up our images to
        produce reports that can be used to evaluate the suitability of
        those images for various tasks.
    * StatusDashboard
      - Pulling in more information to status.linaro.org to provide a
        dashboard of operational status. This would cover things like build
        health, bug tracker health, as well as the workitem tracking.
    * StatusTrackingEnhancements
      - A grab-bag of improvements to the status.linaro.org tracker.
    * SummitEnhancements
      - Improvements to summit.linaro.org to allow us to better organise
        LDS.
    * PrivateHardwarePackBuilds
      - LTs need to be able to build hwpacks without exposing them to
        the world.

Based on this I propose that we add PrivateHardwarePackBuilds to the
"Next" queue to be started on when someone has finished their current
project. This is something that is very important for the landing teams
to add, and there aren't satisfactory workarounds that they can use
otherwise.

In addition I propose that we increase the priority of Gerrit in the IS
queue to be after the private hosting area for hwpacks.

3. Discussion and decision on the proposal
4. Discussion about any upcoming topics that will be proposed.
5. AOB


Thanks,

James