Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2011 2011-11-01 Tuesday Meeting

2011-11-01 Tuesday Meeting

Attending: Josh (notes), Carlos, Simon (presenting), Elwood (presenting), Chris, Jason (notes), Mark, Colin, Melissa, Will, Curtis, Emma, Andrew, Jean-Marie (notes), Scott

Agenda

Remember: Agenda must be complete (with estimated times) on the day before the meeting. Any additions after that must go at the bottom (AOCB)

  1. Accepting minutes from last meeting

  2. Matters Arising (2 mins)

    • Reminder - ALL: Could everyone have short personal presentation for developers meeting
  3. Satellite Dev Meeting - draft programme https://docs.google.com/document/d/1FnyW97C-eFq-W1dyOnB1NUJ7cK3Vvy3rI1INLjRIZnY/edit?hl=en_US (5 mins)

  4. UsingGit review (15 mins)

    • Read Using Git
    • Be ready for making suggestions on readability/usability
  5. OMERO/HIC: Simon/Elwood (30 mins)

  6. Any other business (<5 mins)

    • Scott:Confirmation of a free place on the ImageJ course at Leicester University 19th - 20th Dec.

Attending

* Josh (notes), Carlos, Simon (presenting), Elwood (presenting), Chris, Jason (notes), Mark, Colin, Melissa, Will, Curtis, Emma, Andrew, Jean-Marie (notes), Scott

Notes

  1. Accepting minutes from last meeting

    • Elwood: note about web meeting moving to Mondays
      • Chris: Moved to have the ability to be prepared for Tuesday
      • Especially if we move to one meeting (on Tuesdays?)
      • Elwood: will be getting involved with that.
  2. Matters Arising (2 mins) Started at 14:30 UK

    • Reminder - ALL: Could everyone have short personal presentation for developers meeting
      • Colin: What is it?
        • Emma: One slide each 2-3 min max. Brief intro on what you do, want to do etc. All satellites will give one slide as well.
        • 25 people giving the presentations; critical to stay short
        • Josh: example slide to devteam
    • Jean-Marie: Branches
      • For any one who missed the meeting, be sure to clean up your branches.
    • Jean-Marie: renaming trac
      • Not a good time to bookmark the pages.
  3. Satellite Dev Meeting - draft programme (https://docs.google.com/document/d/1FnyW97C-eFq-W1dyOnB1NUJ7cK3Vvy3rI1INLjRIZnY/edit?hl=en_US) (5 mins) * Feedback welcome. * Dinner-- tell Emma if NOT coming

  4. UsingGit review (15 mins) Started at 14:34 UK

    • Read Using Git
    • Be ready for making suggestions on readability/usability
    • Will:
      • Fine. Mentioned a few things several times. “git graph”
    • Simon: Gitflow? Using it or not?
      • Chris: discussed last week to see who was using it.
      • Most are using it, but no ones pushing to develop directly.
      • Can use, up to individuals
      • Revise Git page, linking to GitFlow page
      • Requires cleaning up your branches
    • Elwood:
      • Is everyone working same way?
      • Chris: Web team: completion of the feature is when it’s merged to develop
      • Remember to manage your branches
    • Josh: Ready to release to others?
      • Andrew: only test what you expect to be using
      • Fix gitflow, then release.
      • Curtis: could have more of a summary, etc.
      • Josh: cool. Will fix and hopefully everyone will feel free to update. i.e. on stop for our git info.
    • Jason:
      • Does anyone wake up and think “I have to use git today! :(“
      • Carlos: in the end, once we cross the omigod bit
        • the first thing we think is “I’m going to put it in my git”
      • Simon: Really it’s how could we use git more?
  5. OMERO/HIC: Simon/Elwood (30 mins) Started at 14:45 UK

    • [google presentation](https://docs.google.com/present/edit?id=0ARIdpFACdpc4ZGZxOGhybmhfMjdmcDQ4azZnNg&hl=en_US

    • Summary of OMERO/HIC

    • Jason: looking at feedback/communication from satellites

      • often feeling “just drop it into tables” but with client, etc.
      • but that’s a template that can be used again.
    • Chris: cF. people touching the DB

    • Elwood suggestions:

      • non-devteam group jabber chat
      • bin/omero update requirements
    • Simon: using a hic group jabber

      • Jean-Marie: not sure that is the right approach.
      • Want people to be aware of it.
      • Minigroup meeting is one thing.
      • But constant conversations prevents others from getting involved.
      • Elwood: may not scale.
      • Andrew: everyone on nitpick?
      • Jason: hard for you to follow or worried to distract others?
        • Simon: both.
      • Chris: real problem. devteam is now at 13 people. When it’s 30?
        • expectation changes significantly. along with dynamic
        • Is the expectation that a conversation in devteam will be participated in?
        • One thing for asking questions.
        • Decision making is something else, more difficult.
      • Jean-Marie: Need ground rules, use devteam as a root, then go off on alternative channel. Having many chats interferes with what we need.
      • Andrew: but if we have it used so much then we’re going to need to have permanent archives. Chris: probably true, have the full text indexed.
      • Jean-Marie: at the end of the conversation should have a report from the minigroup.
      • Andrew: conversations in devteam often don’t have an end. Unlike the end of meeting.
      • Jason: advancing the requirements of devteam.
        • Discuss it next week.
      • Elwood: you’re not going to know until you try it.
      • Andrew: Need archiving and index
      • Emma:
      • Jean-Marie:
      • Jason: caution you guys to put everybody together and then we said core team is going elsewhere.
        • Use next weeks meeting to get etiquette worked out.
      • Chris: will need some etiquette policies.
        • On IRC they’d kick you in the shin.
      • Andrew: now and again, we have 2 or so conversations at once. The more people we have, the worse that’s going to get.
    • Other questions?

      • Andrew: bringing the HIC folks by to see faces
      • Jean-Marie: What are the data volumes?
        • Simon: 0.5 - 1M rows for Tayside
        • Jason: some data like 22M. rows
        • Josh: For each user, we need to track each data use (cF. clicks).
      • Scott: user feedback? How’s that defined at the moment?
        • Simon: current plan is Alison/Keith sit down with us for a demo
        • At the moment, the only users are ~4 people at HIC.
      • Jason:
        • original problem is: data in system, we can get it out
        • new problem: get data and audit usage.
      • Chris: not a new problem. Very large commercial packages.
    • Next presentation: Colin in 3 weeks (when in Dundee)

  6. Project Update: Jason (15 mins) Started at 15:38 UK

    • Jason: summary, some idea of the scale of what we’ll be operating on; plus staffing, etc
    • See paper/grant reviews (Alfresco); generally impressive accomplishments
    • Lot of decisions to be made about our strategic conversations
      • incl. documentation, who’s it for? where to publish?
      • who do we hire? etc.
    • Process:
      • have some in place but need to evolve that.
      • have been working with Jean-Marie, Josh, Chris, and Emma for monitoring
      • Example: 4.4 process. Some other milestones were easier e.g. Permissions, Big images.
      • 4.4 needs more thought.
      • At the same time, none of us want a senior team that’s giving orders.
      • But use these positions for feedback. cF. If there’s a problem going “From zero to hero” then bring it up.
      • 5 of us meet Monday mornings. (Jason counts)
    • Important part: minigroups
      • Model every other week, web weekly, HIC every 2 weeks.
      • Make sure they appear on the calendar. Use agenda & minutes. (Jason reads them)
      • No way anyone can participate in everything.
      • Shouldn’t hear things for the first time at Paris meetings
    • Hiring
      • Ads going out thanks to Emma. Still in HR process
      • Andrew: can we put ads on nitpick? Sure.
      • Still won’t have enough people, but we have a lot.
      • Any strong feelings then speak up
    • Personnel discussion
      • Renewal of positions
      • Funding periods
    • Satellites
      • Things could get complicated
      • Hopefully github etc will help
      • Goal is to make all OME products more useful to science
      • Scaling will be very difficult
      • OME-ification. Training, development. Knowledge transfer.
      • Use next couple of weeks to evaluate how we could make things better.
    • Feedback
      • Carlos: comfortable with Glencoe position, but thank you Jason for personnel explanation (awkward)
      • Melissa: what do we do about importer tickets?
        • Assign them to Chris. After planning out web, then will try to review those.
        • Donald’s went to Jean-Marie.
        • Chris: We’ll also reduce the number of components on trac.
      • Colin: in a nice position, gladly Jason’s the one organizing it
      • Jason: this OMERO paper goes out; we’re going to get hammered.
        • 3k installs → whole bunch of people installing
        • think seriously about how to respond & react.
        • e.g. respond to every email?
        • Simon: would be good if we could get more community responses.
        • Chris: perhaps we respond too quickly.
      • Meeting
        • Elwood: how many people? Emma: 25 people. Pushing 30.
        • Jason: that’s not the complete set.
        • Chris: in a year, should be about 50 people
  7. Any other business (<5 mins) Started at 16:09 UK

    • Curtis: any meeting next week? No.
    • Scott: Confirmation of a free place on the ImageJ course at Leicester University 19th - 20th Dec.

Actions

* Josh: refactor gitflow out.
* Jason: send GS ads to nitpick
* Everyone: feedback on scaling, etc.
Document Actions