JOSS paper on v3

[kartographer]

Description

As mentioned on a few telecons, now that we finally got v3 out the door, I'd like to get a brief updated JOSS paper out about the new version.

I pulled the author list from the updated maintainers an authors list, putting maintainers + authors first and then authors only second. Obviously this is a first pass (and as such, institutions, names, OCRID IDs will need to get confirmed).

Comments welcome! I kept the update relatively short -- I thought about adding a section on major changes since v2, but decided against it for the moment (though I'd happy to discuss that or any other additions).

Motivation and Context

Types of changes

• Documentation change (documentation changes only)

Checklist:

• I have read the contribution guide.
• My code follows the code style of this project.

Documentation change checklist:

• Any updated docstrings use the numpy docstring format.
• If this is a significant change to the readme or other docs, I have checked that they are rendered properly on ReadTheDocs. (you may need help to get this branch to build on RTD, just ask!)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.92%. Comparing base (283dda3) to head (b6b2f3b).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1461   +/-   ##
=======================================
  Coverage   99.92%   99.92%           
=======================================
  Files          61       61           
  Lines       21337    21337           
=======================================
  Hits        21322    21322           
  Misses         15       15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bhazelton]

Looking very good, just a few comments

[kartographer]

Alright, moving this out of draft status and into "ready" status, just to mark my intention to start wrapping this up.

@bhazelton @mkolopanis @steven-murray @adampbeardsley @dannyjacobs @nkern @aelanman @plaplant @jpober @PyxieLouStar -- can you check your author information (name, affiliation, and ORCID ID) and confirm that you are interested in being listed as a co-author? (I'm assuming as much for the current regulars on the weekly call, but want to try to touch base w/ everyone before submission). I'm hoping to get this out the door by Aug 20, so a response sooner rather than later would be appreciated!

[aelanman]

Looks good to me!

[steven-murray]

One comment on my affiliation, otherwise all good. Thanks @kartographer!

[kartographer]

Noting that on the telecon we discussed adding a "what's new" section to the paper, so I'm going to work on adding that...

[dannyjacobs]

Looks good to me too. Thanks for pushing this through Karto.

[plaplant]

Looks good to me, thanks @kartographer!

[adampbeardsley]

Looks good to me!

[kartographer]

@nkern @PyxieLouStar: I'm going to try and get this sent out, so I wanted to send one more ping -- can you confirm if you'd like to be on the paper (otherwise I'll assuming I should take you off). Thanks!

[nkern]

Hi @kartographer--sorry for the late response, i don't have github notifications on.. anyways, yes I'd be happy to be on the author list. Both my orcid and my affil are correct! lmk if anything else comes up. :)
thanks!

[PyxieLouStar]

@kartographer my affiliation should be 3 rather than 2. Thank you!