-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JOSS review thread #154
Comments
Super minor thing (and I can't find the LaTeX file that generates the paper in this repo—it likely lives elsewhere): Figures 1 and 2 in the paper aren't vector based. This is fine for Figure 1 since it uses a high enough resolution that it looks okay, but Figure 2 appears quite pixelated (almost unreadable) when printed. Including SVGs or PDFs in the paper manuscript (or higher resolution PNGs) would be helpful. |
Everything installed just fine for me both via pip and through I did get an error initially, since my system python is 3.13.1, and the project settings look for less than 3.13: Line 9 in 1d739fe
…but poetry ended up automatically installing a 3.9 virtualenv for me. Perhaps allowing >3.13 could be helpful |
The current repo uses Sphinx to build https://votekit.readthedocs.io/en/latest/, which seems to be the actual documentation. It uses the comprehensive ipynbs in https://github.com/mggg/VoteKit/tree/main/notebooks to provide a helpful tutorial, and for my part, running those notebooks interactively on my own was the best way for me to get familiar with the package and its functionality and output. These are great and should be kept as the main documentation tutorial. There's a link to an older, less-organized and less-polished version of the documentation (https://mggg.github.io/VoteKit/) that I accidentally used as my initial entry to the documentation and it took a while to figure out why it didn't match what was in the current repo: Line 22 in 1d739fe
|
JOSS recommends having clear contributor guidelines:
The project currently has a code of conduct, and the README states that "bug reports and feature requests, as well as contributions, are welcome", but it doesn't provide guidelines for how to do that (like issue templates, recommendations for contributors, style preferences, etc.) It might be helpful to include a CONTRIBUTING.md file—see https://github.com/jessesquires/.github/blob/main/CONTRIBUTING.md for a good generic one that I've adapted from several times, or this shorter R-specific one, or GitHub's official example guide for examples. |
Thank you for the super detailed feedback! We really appreciate it. |
Hello! I'm reviewing this package/paper for JOSS (openjournals/joss-reviews#7477), and following their recommendation, I'll leave comments and suggestions as comments here.
The text was updated successfully, but these errors were encountered: