Dundee: Simon, Balaji, Petr, Mark, Dominik, Helen, J-M, June, Jason, Roger, Riad
Remote: Seb, Wilma, Eleanor, Liza, Melissa
Start: 2:00 pm
(2-3 minutes each)
sooner if needed). Includes some support for Java 9 (runtime). Will require some testing/coordination with upstream project releases (ImageJ/Fij).
in the community?
(currently). Launcher having issues. Will look into the launcher, if it requires a cursory tweak.
API to write OME-TIFF. Starting to look into low-level components release while we extend the Python bindings. Need rationalization in terms of documentation/website.
the new website.
Hopefully something by the end of the month.
consume IDR-PY the last step for completing phase1 of the Gene-Ontology notebooks.
interested in adopting BioSchemas mark up. Aim to make datasets more findable by search engines using json-ld. Looking at implementing for data resource and datasets in IDR
5.4.0 Out Thanks.
Training for the coming weeks
on the same.
targeted towards the cambridge training. Will have to consider the Bio-Formats release cycle as well, for 5.4.1
Concentrating on the training sheet.
Start prep for Cambridge in coming weeks
Advertise the cambridge workshops again, in social media.
Seeing is Believing: Good discussions, lots of microscopy.
Should try to attend in future as well.
3.1.2 out today. Compatible with 5.3.x
Compliments from Oxford, have some issues with IE. Have some
Design issue, towards multi-view. (Comments welcome).
Load testing (ongoing process)
(creates dependency on OMERO 5.4)
and nitpicks like CSS styling and further linkages
Riad still needs to supply a photo and bio
downloads - OME Files page and decision on whether we have versioned OMERO download pages on the website since there are no index pages on downloads.openmicroscopy.org since we changed the release process
Trello card in the website board(inbox): comments welcome.
versions of OMERO downloads in our downloads pages.
(5 min. max; tech. Discussion should be highlighted to relevant people and rescheduled)
Scc 0.8.0: changes for developers
scc. (one-time notification instead of daily notifications).
process, passing on the knowledge to the core team.
Calls after standup every day to discuss status.
tagged as “discussion”
Will help in scheduling.
(20-25 minutes plus 15 minutes questions max)