Present: Andrea, Ben, Dario, Hadrien, Michel, Pere, Benedikt, Torre, Liz
Pere - Belle II presentation was well received. They recognize they need to participate and will be doing so, are already in some areas (e.g. conditions).
Agreed that the dates are set: Mon May 2 - Wed May 4.
Will probably have the plenaries in the afternoon on Mon to allow travellers to come in on Mon morning, but could potentially use Mon morning for smaller sessions. Wed is the day before a European holiday, so we may lose people Wed afternoon, but there too could perhaps use it for smaller sessions after having the closeout in the morning. To be firmed up as we firm up content and how full the agenda is.
Michel - we have full LAL conference support. Perhaps a small fee for coffee breaks. Will contact the person doing this sort of support and get things going. Will create an Indico page promptly.
Thoughts on sessions:
Packaging hackathon: will soon (pre-workshop) winnow the candidate list down to a small number. Could use the hackathon to work hands-on with the best/chosen candidates for solving particular problems. Determine successful/unsuccessful evaluations of the tools.
Training: could have a session on transforming training material into WikiToLearn. An intro/tutorial on WikiToLearn. Would be good to have a hackathon element also if we can identify particular things that a hackathon group could work on, bootstrapping content.
Knowledge base: an intro/tutorial and a blitz on entering content, in a hackathon session and/or between sessions. Predefine objectives well, and test scaling when many people are editing.
Concurrency/new architectures: define program and objectives.
Should we have parallel sessions? Hackathons? Tutorials? Talk sessions beyond the opening plenaries? Depends on the content we come up with.
We agreed we should (as part of soliciting participation) poll people on
So request out of this meeting is for people with session ideas, to write a paragraph selling the session first to this group and ultimately to prospective participants in the poll.
Then ultimately we can doodle the session times to come to the optimal schedule.
Michel - no problem for several parallel rooms if needed, up to 20-30 people each.
Many HSF mentions in the workshop. Lively discussion. General expression was interest in HSF, making use of it. Experiments indicated appreciation for what HSF is doing.
Much interest in technology evaluation and HSF role. Deserves follow-up. At CERN, this means engaging with TechLab. They are ready to open up to interested people. Set up another round of technology demonstrator projects. Involve other labs also, round up interested users.
Liz - Fermilab very interested as well. Converging on an OpenLab framework agreement. Fermilab will become one of the logos on the OpenLab page, part of the framework. OpenLab way ahead in this, a long standing tradition, the legalisms all worked out. First project identified, on Big Data, Siemens as the industry partner, will invite other participants at CERN. Will advertise when ready.
Updates from Andrew:
On Monday I assigned the number for the licensing TN (not hard: HSF-TN-2016-01), updated the GitHub directory and mailed Michel (I’ve updated the document now too, please let me know if there’s any problem: pdflatex ran ok and the PDF looks fine.)
I’ve agreed with the WLCG ops chairs to submit the Machine/Job Features technical note, and I’ve uploaded that as a draft in the consultation stage, running until 19th Feb (i.e. after the next WLCG ops coodination meeting where it will also be presented.) I’m next going to mail hsf-sf-forum to announce the consultation stage.
Please see http://hepsoftwarefoundation.org/technical_notes.html for the updated state of both documents.
Two topics for coming newsletters: explaining TNs, and the licensing. Will get these out ASAP.
Andrea - asked Tim Smith to comment on licensing note. Appropriate license depends on the software above and the software below. Perhaps add this point.
Liz - FNAL lawyer was complimentary on the note. Suggested adding more about ‘class path exception’. Perhaps reference it.
Agreement that if TN note additions are quickly proposed and agreed, they can go in. We don’t want to re-open discussion on what’s in there already. We need to get the note out asap.
Torre summarized recent hepsoftware.org additions and updates:
Startup team meeting notes were hard to find on the website; moved to front page.