These are chat archives for fiji/fiji

11th
Apr 2016
Ignacio Arganda-Carreras
@iarganda
Apr 11 2016 09:45
I just found out that we can make our repositories citable via Zenodo and GitHub: https://guides.github.com/activities/citable-code/
What do you think about it @ctrueden?
Richard Domander
@rimadoma
Apr 11 2016 10:00
@iarganda Citing software (by assigning DOIs) is in interesting topic, one we could perhaps discuss on the forum
I think it'd be good to set up a Jenkins job, which acquires a DOI when you publish a release, but then the question remains what the DOI would actually point to
I think it'd be important to include the POM into the cited artefact, because it's an important part of reproducibility
on the other hand at the Software Sustainability Institute's conference at Edinburgh it was suggested that one should include a CITATION file to their repository, like LICENSE or README
John Bogovic
@bogovicj
Apr 11 2016 13:00
@tpietzsch I would like ARGBARGBColorConverter to stay in bdv-core. I'll remove it from bigwarp
@ctrueden I'll also look into why bigwarp_fiji won't build with pom-fiji 22.0.0.
tpietzsch
@tpietzsch
Apr 11 2016 13:21
@bogovicj ok, cool, no work for me :+1:
:-)
Curtis Rueden
@ctrueden
Apr 11 2016 14:52
@iarganda There is a guide for Zenodo somewhere on the wiki.
Oh, I guess it's not really a "guide." Someone (probably Mark) just added a note about it.
This was after Thorsten Wagner did it for his plugins.
@iarganda I think in a perfect world, we would automatically create a new DOI (because you need a new one for every version, right?) for every release. But that might be a bit excessive. And it would make it more complex to analyze your project's citations—just as multiple GitHub repos also makes it more complex.
@rimadoma I like the idea of a CITATION file, in cases where a publication already exists.
We have something like that on the ImageJ wiki: each plugin that is citable has [[Category:Citable]] at the bottom, as well as a == Publication == header followed by {{Publication | My Project}}.
Curtis Rueden
@ctrueden
Apr 11 2016 14:57
@kmader FYI, the latest ImageJ2 release includes the Scala script engine now, but it isn't fully working. The unit tests worked, so I released it, but it seems there are problems with it in both the Script Editor and Script Interpreter at the moment. Will investigate as time allows.
Richard Domander
@rimadoma
Apr 11 2016 14:57
@ctrueden Hmm, I think that's a good way to inform the public on how to cite the plugins. But I wonder if that information should also be included into the help / about dialogs of the plugins one develops... Naturally this would be the responsibility of the individual developer
Curtis Rueden
@ctrueden
Apr 11 2016 14:58
@rimadoma We can make it really easy for them though by providing a framework. At the moment, I think only @StephanPreibisch does this with his plugins. At most 1-2 other devs.
@tpietzsch @bogovicj Thank you for resolving the ARGBARGBColorConverter!
Richard Domander
@rimadoma
Apr 11 2016 14:59
@ctrueden Cool. I'll check how he's doing it
Ignacio Arganda-Carreras
@iarganda
Apr 11 2016 16:04
@rimadoma and @ctrueden I just discovered the "citable" category on the wiki :D
Curtis Rueden
@ctrueden
Apr 11 2016 17:12
@iarganda It is a work in progress. I eventually want to convert EVERY citation on the wiki to use the Publication template, but there is a long way to go. Feel free to help out if you notice pages that need to be changed over, and/or pages missing the Citable category.
@rimadoma The way Preibisch is doing it is almost certainly Swing/AWT-specific. We would need to concoct a more general way in the SciJava Common UI framework.
Richard Domander
@rimadoma
Apr 11 2016 18:12
@ctrueden Oh, I see. Well, in any case I think the citation info should be per plugin, and I guess that would be the right level of granularity to implement this framework. I believe a (superficial) collection of plugins should work this way too, or at least BoneJ, because it borrows its plugins from many authors, and the credit should go where it's due.