Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2006 2006-05-11 Project-wide

2006-05-11 Project-wide

Attending: Brian, Chris, Donald, Harry, Jason, Jeremy, Jean-Marie, Josh, Sheldon, Stefan

Agenda

  • Review of last project-wide meeting notes/issues
  • Summary of Dundee get-together
    • M1 Done.
    • Dev-Process
      • Very, very brief overview. For more see ConferenceCall 2006-05-04 and Trac
    • Security
      • Can now move forward. Still a few open issues (in ConferenceCall 2006-05-04 last week's action points.
    • HD trip? Donald to EMBL for user interviews.
    • Testing (junit4/testng)
  • Week-in-review
    • Baltimore
    • Boston
    • Dundee
      • Java1.4 Snafu. Basically, doesn't work as expected. Needs time investment. Options? Priorities? (Josh)
  • Week-to-come
    • Roi5d : plan?
    • APIs/Rendering/Pojos (see https://trac.openmicroscopy.org.uk/ticket/2). Can someone explain? (Josh)
    • Resurrect
      • Annotation hierarchies and permissions (Chris & Brian)
      • PDI hierarchies and permissions (Chris & Brian)
  • And as always, WhoNeedsWhatFromWhomByWhen
    • Quick poll: More informal meeting in August? Half work, half vacation in Edinburgh? Good, Bad, Maybe. "The Children of OME"


Review of last project-wide meeting


  • The Java 1.4 implementation has proven to be more difficult then anticipated and requires a detailed discussion to decide which direction to head and how to get the problem fixed.
    • The question was raised on whether we need to support 1.4 (primarily for Macintosh machines running the 10.3 operating system).
    • The suggestion is that we stick with a Java 1.5 requirement.
    • The upcoming cross-language remoting infrastructure can equally support 1.4.
    • ticket:32 then is essentially closed, and work on the Java5 model will begin shortly.

Week-to-come


  • ROIs: To get consensus on a model, the suggestion is that each team bring a representative to a skype group and approve a universal model (via the evaluation models already suggested).
  • There are new methods needed in the IPojos interface to support viewing. More to come.

Summary of Dundee get-together


  • Milestone 1 was completed. A fully installable version of OMERO is now available for download. You'll need to get a database dump from the importer team, and checkout shoola-omero as well.
  • Shoola is ready to be tagged, but needs a quick check against a full database with images
  • There was a discussion of how to release tag Shoola. The suggestion has been made that we tag Shoola, the question is when or how. One suggestion is that it should be tagged several weeks after the server, so there is time to review the original OMERO release first. The other suggestion is that like releases (for example the "M1" releases) be compatible with each other (M1 Shoola and M1 OMERO work together).
  • After a short review of Trac, the Dundee team has decided to use this tool for OMERO and Shoola development. Over the next six weeks they will be trying this tool to see if it needs their needs. There is some concern over its lack of hierarchy, and this is one area that should be worked on in the near future (hopefully be Catriona's group).
  • During the recent Dundee developer's meeting, we solidified a security model to use for OMERO. There are still some points to be decided (such as the bits in the permission field, etc.)
  • There was a discussion about import/export limitations and our current use of single user datagraphs. For now these issues in Resurrect will be handled by only importing an individuals data and not any other user's data that may be linked to it. There is some discussion that needs to happen about annotations, and this has been scheduled in the action items.


Action Items


  • Harry: Please contact Josiah for information for the ROI gathering (pass off to Josh)
  • Josh: please spearhead the ROI gathering, in order to get the concrete models done so we can come to a decision.
  • Jason: Please figure out the next meeting time (if August/EDI is good, etc.)
  • Jean-Marie: A discussion about the roadmap of Shoola needs to be set up once Jason is back in Dundee.
    • Includes: letting Josh know what needs to be added for rendering from Shoola.
  • Jason: Details about the release process for Shoola/Omero needs to be discussed and put up on the Wiki.
  • Chris: Have a meeting with Jason about the security model to discuss the few remaining caveats that could cause issues (applying permission changes to hierarchies, etc.), and outline what permissions (READ/WRITE/ATTACH) we want to support.
  • Jason and Donald: Have a discussion about cell tracking
  • Chris/Josh/Brian: Have a discussion about multi-user import/export handling ticket:50 for cycle 1 iteration 2.
  • After evaluating trac for a while, discuss keeping and discuss adding hierarchy features a la 1.0 or via Catriona.

Document Actions