Present: Frank, Roland, Ian, Gabrielle Allen, Vassili, Steve
ET website: * online at http://einsteintoolkit.org/new/ * can be edited via git repo at https://bitbucket.org/einsteintoolkit/www/src which all maintainers should be able to edit * sub-menu button in About maybe too small, better to have a landing like page as for "Documentation" * find a middle ground between all on one page and very many tiny pages * needs to be tested on more common browsers, suggest at least Safari/OSX, Firefox, Chrome, Edge/Internet Explorer, mobile broswers on both IOS and Android both phone and tablets * contact someone with design experience about colour scheme
Read/write driven SYNC: * Steve worked on this and has sent out a link: https://github.com/stevenrbrandt/PresyncWave * works for a wavetoy, not yet clear if prolongation would work or if works for production code * the README file should contain usage instructions * feedback would be appreciated
Simfactory machine files/options/submit/run scripts * treat as documentation, ie no review is required but use your own good judgement
Yours, Roland
On 30 Jan 2017, at 17:12, Roland Haas rhaas@illinois.edu wrote:
Simfactory machine files/options/submit/run scripts
- treat as documentation, ie no review is required but use your own
good judgement
Possibly, but what I meant to say on the call was that it shouldn't need review if the machine is obviously currently broken due to a system update or similar, or the machine is new. Whether other changes should need review should be discussed more widely, e.g. with Erik as well, as the author of simfactory.
-- Ian Hinder http://members.aei.mpg.de/ianhin
Hello all,
Simfactory machine files/options/submit/run scripts
- treat as documentation, ie no review is required but use your own
good judgement
Possibly, but what I meant to say on the call was that it shouldn't need review if the machine is obviously currently broken due to a system update or similar, or the machine is new. Whether other changes should need review should be discussed more widely, e.g. with Erik as well, as the author of simfactory.
True.
I was thinking that for the machine-files / option-files / submit-scripts / run-scripts the original author of the file in question should be consulted (since there may well be reasons for why things were done the way they were done) which is not necessarily Erik. Eg for a machine that one has no access to, one would usually not be able to comment anyway.
For simfactory's *source code*, review is required and the original author (or official maintainer) would have final say.
If we end up with people breaking machines too often, then we have to revise this of course.
Yours, Roland
users@lists.einsteintoolkit.org