Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2016 2016-09-06 Tuesday Team Meeting

2016-09-06 Tuesday Team Meeting

Dundee: Gus, Roger, Mark, Ola, Simone, Jean-Marie, Will, Kenny, Petr, Dominik, Balaji,

Remote: Sebastien, Josh, Colin, Eleanor, Emil, David, Chris,

Agenda - 2:00pm Start

  1. Accepting minutes from last meeting

  2. Project Timelines (2-3 minutes each)

    1. Spaces

      1. Files/Formats/OME Files (Sebastien)
        • 2 releases next week.
        • Freeze this week Thursday & Friday
        • OME files support all modalities of C++
        • Roger Proposal to shelve 5.1 jobs (see standupx notes)
        • Scoping meetings since last Wednesday. (see notes)
        • Model diagrams etc
        • More discussions tomorrow - feedback welcome
        • External people contacting us - Reader patches etc
        • May need to relax access to test repo
        • KLB file format from Janelia. Need place to test
      2. Metadata (Josh)
        • Demo3 with mapr UI
        • New menu bars for listing Phenotypes, Genes etc.
        • Hope to get into production for demos etc. but needs more annotation fixes
        • Needs more testing from Jason & team
        • Big Data conf 25th September
        • Poster
          • PDF on gdrive under IDR folder
          • Comments welcome
      3. OMERO 5.3.0
        • LUT followup & web api for 5.3.0
        • Grid-view for SPW Well data start in ~2 weeks
        • Potential 5.2.6 release
          • Ice 3.5 fix
          • Apache deprecation?
          • 1 or 2 PRs may be included
      4. Outreach (Colin)
        • Petr: Graeme coming to give IJ talk
        • Preparing Fiji scripting workflow
        • Berlin mid November Jason presenting
    2. Other releases/upgrades:

      1. Figure
        • Pip installable (Ola’s PR)
      2. ImageJ
      3. Learning
        • Meeting Paul re: mapr bulk annotations from csv
        • On hold until mapr more stable
      4. Sysadmin
        • Seabass & Octopus storage issues
      5. Website redevelopment/redesign (Helen)
        • reviewing About pages while Liza is away
        • if anyone on Dundee team wants to update their bio and/or photo, please let me know
      6. Smuggler (Montpellier)
    3. Glencoe Update (Chris)

      • Legacy cleanup, testing.
      • CellProfiler fixes.
      • Some new PRs to come
      • Old DB update fixes. Maybe in to 5.2.6 release
  3. AOB (5 mins max - technical discussions should be highlighted to relevant people and rescheduled)

    1. Dundee: mandatory IT security survey
      • Deadline 10th September.
  4. 5.3.0-m4 report

    • Web should be deployed separately using zip and virtualenv
    • Webapps pip installed into virtualenv
    • All versions should be defined in requirements file
    • Ola: TRIAL tested via breaking. Quite stable now.
    • For m4 we just need webapps pip installable
    • Josh: need to update release boards etc. Not ready for m4
    • Chris: Might be easier to work with pre-compiled archives, ship these around etc. without using Pypy
    • Josh: ci could generate egg from merge jobs, put on github/snoopy
    • Jobs named web-dev-*
    • Testing. Omeroweb-install scripts with Ansible driver
    • Josh: is Ansible a barrier for all team getting started?
    • JM: don’t think this is a problem
    • New install docs page - need to be tested
    • Webapp naming: github: /ome/omero-*
    • Chris: bigger issue is root dir name for package. E.g. ‘figure’
    • Ola: omego isn’t known/used by the team much.
    • Josh: omego knows how to download and install server.
    • Should do the same for OMERO.web
    • Jean-Marie. Expose and document omego more as it becomes more stable
    • Josh: would be nice to have “requirements.txt” type file for omego so we know versions of everything installed
    • Josh: what is release job for m4? (Seabass release jobs dead)
    • Josh: What else for 5.3.0? Is ‘trial’ approved?
    • Will: pip install webapp doesn’t do omero config?
    • Josh: no, teach Ansible role how to build/install/config web apps?
    • Ola: this is just internal (ansible not used externally)?
    • Josh: IDR playbooks could use this. Keep improving - maybe release docs and tell external users to start using ansible in > a year.
    • Chris: asking a lot to have our users install & use Ansible etc.
    • Josh: config for installing webapps can be very complex. E.g. top-links, public urls, etc.
    • Chris: can add config to in each webapp.
    • Chat after standup tomorrow
Document Actions