Closed gully closed 2 years ago
@astrocaroline recommends pursuing this AAS publication and review by JOSS path. This seems like a sweetspot in getting the JOSS review and the AAS audience.
Ok, the paper is ready for approval and edits from co-authors.
Our tentative goal is to submit it next Friday, February 25, 2022.
Here is the current draft: muler_JOSS_20220218.pdf
This paper is submitted but the review hasn't started.
The time has come.
muler
appears to have reached some threshold level of maturity. It has a feature set that can accomplish the key tasks it was built for. It has months worth of user testing under a range of scenarios, and while it is not perfect, it's pretty good! It is relied upon for projects that are, themselves, destined for publication, and so a citeable reference is due. Also, its API has more-or-less stabilized to a point that it's not likely to have major breaking changes in the future.So with all that said, let's submit a paper. We will plan to submit to JOSS, because they offer excellent two-reviewer reviews of the actual GitHub-based code. I don't believe it's possible to group
muler
with its sibling packagegollum
, but that's OK--- they'll each get their own standalone review.What we mean by research software
muler
is in-scope for JOSS because it meets these criteria:Substantial scholarly effort
muler
has taken months of work, with many contributors, commits, issues, pull requests, and considerable on-line and off-line discussions put into its software architecture. It meets these requirements:Here are the numbers at-a-glance for
muler
:1 year, 2 months
254
8
1888
in the key source code, much more in docs and tutorialsyes