Skip to content
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

[PRE REVIEW]: Research Software Engineering Skills #264

Open
editorialbot opened this issue Oct 10, 2024 · 11 comments
Open

[PRE REVIEW]: Research Software Engineering Skills #264

editorialbot opened this issue Oct 10, 2024 · 11 comments

Comments

@editorialbot
Copy link
Collaborator

Submitting author: @jatkinson1000 (Jack Atkinson)
Repository: https://github.com/jatkinson1000/rse-skills-workshop
Branch with paper.md (empty if default branch):
Version: v1.0.0
Editor: Pending
Reviewers: Pending
Managing EiC: Lorena Barba

Status

status

Status badge code:

HTML: <a href="https://jose.theoj.org/papers/7924393a31a981fcf46156111dcc0079"><img src="https://jose.theoj.org/papers/7924393a31a981fcf46156111dcc0079/status.svg"></a>
Markdown: [![status](https://jose.theoj.org/papers/7924393a31a981fcf46156111dcc0079/status.svg)](https://jose.theoj.org/papers/7924393a31a981fcf46156111dcc0079)

Author instructions

Thanks for submitting your paper to JOSE @jatkinson1000. Currently, there isn't a JOSE editor assigned to your paper.

@jatkinson1000 if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

The JOSE submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:

@editorialbot commands
@editorialbot
Copy link
Collaborator Author

Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.90  T=0.04 s (959.4 files/s, 315875.1 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
CSS                              3           2487              9           5383
Python                          10            410            584           1065
Markdown                         9            193              0            516
TeX                              2             17              0            146
Lua                              1              9              2             73
YAML                             4             13              9             69
Sass                             1             22             12             64
JavaScript                       1             15             20             40
JSON                             1              0              0             14
Bourne Shell                     2              2              8             12
-------------------------------------------------------------------------------
SUM:                            34           3168            644           7382
-------------------------------------------------------------------------------

Commit count by author:

    41	Jack Atkinson
     4	jatkinson1000

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

✅ OK DOIs

- 10.6084/m9.figshare.19608801.v1 is OK
- 10.1038/s41597-022-01710-x is OK
- 10.21105/jose.00037 is OK
- 10.5281/zenodo.5960048 is OK
- 10.1145/2445196.2445388 is OK
- 10.5281/zenodo.10783026 is OK
- 10.1371/journal.pbio.1001745 is OK
- 10.1371/journal.pcbi.1005510 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Black: The uncompromising Python code formatter
- No DOI given, and none found for title: Pylint

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

Paper file info:

📄 Wordcount for paper.md is 1952

✅ The paper includes a Statement of need section

@editorialbot
Copy link
Collaborator Author

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@jatkinson1000
Copy link

Thanks for opening the pre-review JOSE.

For potential reviewers we can suggest janash, suchow, danielskatz, adeepak7.
Let us know if you need further suggestions.

@MarionBWeinzierl
Copy link

More potential reviewers from your list: dpshelio, lechten, krother

@jatkinson1000
Copy link

Hi @labarba @acocac just wondered if there is anything we can/need to to to progress this further.
Please do let us know if we have missed something that triggers the next steps.
Thanks!

@labarba
Copy link
Member

labarba commented Nov 5, 2024

No editor has been assigned yet to handle your submission. We have a backlog and a small, volunteer-only team. Thank you for your patience.

@acocac
Copy link

acocac commented Nov 5, 2024

Hi @labarba @acocac just wondered if there is anything we can/need to to to progress this further. Please do let us know if we have missed something that triggers the next steps. Thanks!

@jatkinson1000, thanks for reaching out.

@labarba this is to raise a conflict of interest regarding my role as a potential editor. I'm currently collaborating with one of the submission's authors. Fingers crossed to find someone else!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants