Present: Bhavesh, Peter, Sam, Roland, Steve, Yosef, Zach, Qian
* planning for next ET release (due in June or August) ** August is next possible date ** collect milestones for ET release: https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&a...
* Giraffe tests ** Zach is working on this ** will be couple of weeks
* status of NSNS gallery example: http://einsteintoolkit.org/mp.html Peter will try and get this done this week.
* status of download page for ET MHD paper: http://einsteintoolkit.org/mp.html Roland to look into this. Roland to update page.
* server status ** ssl on trac and wiki sites ** captchas on trac and wiki sites Steve is in contact with IT at CCT about sites. Captchas rely on mod_php which has been deprecated. For now, disable catpchas in trac and hope for the best as far as receiving spam goes.
* standing item: unanswered / ongoing questions on mailing list No open emails.
ET workshops: * Bhavesh has sent out a reminder about registration
* how to review codes On wiki: https://docs.einsteintoolkit.org/et-docs/How_to_Review_a_Patch Guidelines or code contributions http://einsteintoolkit.org/contribute.html * Components should be of sufficient quality to be used for peer-reviewed and published science. This includes a basic standard of software engineering, documentation of the software including algorithms and methods, tutorials and examples, and self-tests to demonstrate that the software works correctly. * To focus development and support, optimize resources, and provide best practises, the Einstein Toolkit components should be of current interest to the community. * All components must be distributed under an open source licence so that others can use these components without restrictions (except as mandated by scientific integrity), can modify and improve them as necessary, and can pass on these modifications to their collaborators as they see fit.
* ET call attendance fluctuates significantly suggestion to base skipping on number of agenda items having the regular meeting once a week makes scheduling easier and harder to forget tentative agreement is to keep the weekly meeting
Yours, Roland