Personal tools
  • We're Hiring!

You are here: Home → Community → Minutes → Conference Calls → 2011 → 2011-01-18 Tuesday Meeting
« April 2024 »
April
MoTuWeThFrSaSu
1234567
891011121314
15161718192021
22232425262728
2930
 

2011-01-18 Tuesday Meeting

Attending: Brian, Ola, Will, Scott, Chris, Donald, Jean-Marie, Andrew, Josh, Jason, Melissa, Curtis, Carlos

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 (<10 mins)

    • Josh: Review community about Ice 3.4. Where do we stand?
    • Josh: Send email to ome-devel about git
    • Josh (Discussion): Chgrp & designing new model object converters (See notes from last Thursday)
    • Josh (Discussion): Acquisition date nullability issue (See notes from last Thursday)
    • Josh (Discussion): search bridge for protocols (See notes from last Thursday)
    • Jean-Marie: renumber sprints.
    • Ola: create a QA account for Scott
    • Review Tuesday trac policies and then write them on process list
    • Web: discuss big images on Monday
    • Josh: talk to Christopher Wood re: OME to OMERO
    • Melissa/Will: follow up on import colors (see ticket #3668). Update forum with ticket number
    • Josh: Update docs on bridging issue for querying external xml forum issue
    • Brian: go through all import QAs
    • Brian: For QA testing, if a fail happens should be added to test_images_qa

  3. GIT (30 mins)

    • C) To find out our timeline...
      • How (and by when) do we decide if we are moving?
      • How (and by when) do we decide when we are moving?
      • When do we contact the lists? How long do they need to have?
      • Do we turn off svn and test first? When?
    • D) To define how we work...
      • See http://users.openmicroscopy.org.uk/~jmoore/git/workfows.html
      • Do we allow/encourage/force use of github? gitweb? (i.e. how do we share with other developers?)
      • Do we have one central repository? Handle merges yourself.
      • Do we have an integration manager who handles merges?
      • Does something like "dictator & lieutenants" make sense (perhaps later)?
      • Do we use git-flow? Something more or less strict? Build/extend our own?
      • Do we need to buy any GUI tools?
      • Do we mirror git to svn? (Added after meeting)

  4. Feedback on Scott's document (15 mins)

  5. Any other business (<5 mins)

In Attendance

  • Brian, Ola, Will, Scott, Chris, Donald, Jean-Marie, Andrew, Josh, Jason, Melissa, Curtis, Carlos

Notes

  1. Minutes & last week

    • Discussed ticket/trac usage
      • Tickets shouldn't be longer than 2 days of work
      • Any activity should be in a ticket, so everyone (e.g. like Scott) knows what coming
      • When in-progress, move tickets to the middle column
      • Put estimate where possible, especially bugs.
      • Forum policy is response within 24 hours
      • Similarly, bug should be done similarly quickly (as long
      • If its longer then 2 days of work, should probalby be moved to a story with detailed sub-tickets
      • Do not leave tickets in progress if you are away from work for a few days
      • Commits should have a ticket
      • Jason:
        • What should we do with the spring summary script?
        • JMB: Just to get a better idea of estimates vs. reality
      • We are also now keeping 2 iterations going at the same time now (current + 1)
        • This is so you can plan ahead without having to drag tickets
      • Andrew: Suggests we get the trac report email each week and then review in a month or so if we want to continue

  2. Matters Arising

    • Josh: Review community about Ice 3.4. Where do we stand?
      • Waiting for Feedback
      • May need to send out another email to Nitpick
    • Josh: Send email to ome-devel about git
      • Was on hold for feedback
    • Josh (Discussion): Chgrp & designing new model object converters (See notes from last Thursday)
    • Josh (Discussion): Acquisition date nullability issue (See notes from last Thursday)
    • Josh (Discussion): search bridge for protocols (See notes from last Thursday) (three above go together)
      • Josh: Still left, not sure where to go
      • Jason: First on this list above is most important, second second, third last
      • JMB: We need to have collaborators try first before we help out - let collaborators know this
      • Will: Couple people on the forums asking for this.
        • Jason: As an example, Martin has a workflow that makes perfect sense
      • Jason: Also, alot of people want big images
      • JMB: Probably a 45 days for work for chgrp, moving a lot of other tasks till after the summer
      • Donald: have to keep collaborators like Jos in mind or they may move on to their own thing
      • Jason: have to be aware that others are building their own when we can't provide a feature
      • Jason: could we use the public link functionality rather than chgrp
      • JMB: Not going to make a decision on this right now, but we need to decide soon
        • Josh: Need to decide soon as my work depends on this decision
        • Josh: If this is going to take time, will move forward on Big Images
    • Jean-Marie: renumber sprints. (DONE)
    • Ola: create a QA account for Scott (DONE)
      • Chris needs to add scott to omeroteam email
    • Review Tuesday trac policies and then write them on process list (DONE)
    • Web: discuss big images on Monday (DONE)
      • Carlos is looking at the API
    • Josh: talk to Christopher Wood re: OME to OMERO (DONE)
    • Melissa/Will: follow up on import colors (see ticket #3668). Update forum with ticket number (DONE)
    • Josh: Update docs on bridging issue for querying external xml forum issue (PENDING)
    • Brian: go through all import QAs (DONE)
    • Brian: For QA testing, if a fail happens should be added to test_images_qa (DONE)

  3. GIT (30 mins)

    • C) To find out our timeline...
      • How (and by when) do we decide if we are moving?
      • How (and by when) do we decide when we are moving?
      • When do we contact the lists? How long do they need to have?
      • Do we turn off svn and test first? When?
    • D) To define how we work...
      • See http://users.openmicroscopy.org.uk/~jmoore/git/workfows.html
      • Do we allow/encourage/force use of github? gitweb? (i.e. how do we share with other developers?)
      • Do we have one central repository? Handle merges yourself
      • Do we have an integration manager who handles merges?
      • Does something like "dictator & lieutenants" make sense (perhaps later)?
      • Do we use git-flow? Something more or less strict? Build/extend our own?
      • Do we need to buy any GUI tools?
      • Do we mirror git to svn? (Added after meeting)
    • Notes
      • Impressions from last week
        • Will: Impression I got was that you can do a lot with GIT, we will need a work flow to keep everyone in sync
        • Josh: Whoever is doing the release has to make sure its all sync'd upon release
        • Will: Are we aiming to commit to 'trunk' as often as we are now? How often?
        • Josh: Pushing up to main trunk less frequently if needed, more often to 'personal' trunk
        • JMB: How does this sync with closing tickets?
        • Josh: We can have tickets closed from someone's personal branch
        • Donald: possibly move for big images sooner
      • Transition timeline
        • Jason: how does this affect public access to our resources?
          • Chris: ffmpeg moved to git 1st of January
            • keeping git around with nightly export to svn/trunk (read-only)
            • also nightly source builds
            • trac shows a schism between svn and git (old commits)
            • There are things we can do to make it easier, but there will be some disconnect
          • People looking at our grants, bad-time to destabilize
        • Ola
          • How does GIT counter work? Chris: No such thing. Have to use SHA1 for that commit
          • Examples
            • http://trac.openmicroscopy.org.uk/agilo/ticket/173
            • http://trac.openmicroscopy.org.uk/agilo/log/spec/Schemas?rev=88a37d2662684a80bce0371467d455452892790d
        • Time choices:
          • After big images?
            • Chris: don't have a lot of code on laptops at the moment. More research/design
            • Perhaps end of this iteration; otherwise wait
          • Seems we agree on Thursday morning this week
      • Workflow
        • Master on necromancer with any number of branches as desired (folks will be able to branch as needed)

  4. Feedback on Scott's document (15 mins)

    • Re eclipse
    • Jean-Marie: column "do you have time to be a beta tester?"
    • Jason: "how would you like to communicate with us?" EMAIL, BLOG, PRIVATE, ...
    • Jason: "Volume of data / How much imaging do you do?"
    • Jason: "What's your research question?"
    • Chris: "Main acquisition system? Which instruments?"
    • Jason: (for devs) "How important is OMERO to your activities?" PRIME EFFORT, INVESTIGATING, ...
      • "How much priority does OMERO have in providing resources to your users?"
    • Ola: "Which language do you use?"
    • Script for general feedback ("Advanced user feedback")
      • Andrew: Question on upgrade?
      • Chris: bin/omero admin feedback
      • Chris: also a big problem that people aren't upgrading there stuff
        • Integrate that with the feedback box, so we know what's old, etc.
    • Jean-Marie: "Are we responding quickly enough?"

  5. Any other business (<5 mins)

    • 4.3 bugs
      • Large backlog of bugs. Everyone look at them and clean up.
    • Proposed "Deprecated" CSS example
      • Brian: On releated. Everyone please update google documentation spreadsheet with status of your pages
    • Chris: OME-XML wiki pages moved?
      • Only moved tickets
      • Same for Shoola trac
    • March 2&3 Knime.
    • Jason: strong feedback from usersabout writing OME-TIFF HCS format
      • All images from well in a single TIFF
      • That's the granularity they're interested in.
      • cF. number of files on file system
    • Jason: projects to think about / keep an eye on

Action Items

 * Everyone: evaluate git-flow for next Tuesday
 * Everyone: Review Scott's google docs, provide feedback on quick questions to ask users
 * Everyone: Large backlog of bugs. Look at them and clean up.
 * Everyone: please update google documentation spreadsheet with status of your pages
 * Andrew: document (under /team?) of how to mark "deprecated"
 * Carlos: looking at big images in Web
 * Chris: Add Scott to omero-team email
 * Chris & Josh: start migration to git
 * Josh: update docs on bridges
 * Josh: send out git announcment/feedback email
Document Actions
Left arrow Previous: 2011-01-13 Thursday Meeting Next: 2011-01-20 Thursday Meeting Right arrow