[PRE REVIEW]: mei-friend: An Interactive Web-based Editor for Digital Music Encodings

[editorialbot]

Submitting author: @wergo (Werner Goebl)
Repository: https://github.com/mei-friend/mei-friend
Branch with paper.md (empty if default branch): joss2023
Version: v1.0.0
Editor: @faroit
Reviewers: @stefan-balke, @rlskoeser
Managing EiC: Olivia Guest

Status

Status badge code:

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

Author instructions

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

@wergo 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 JOSS 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]

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]

Software report:

github.com/AlDanial/cloc v 1.88  T=0.84 s (115.6 files/s, 277668.8 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
JavaScript                      46           8272          11594         194080
XML                              2              0              0           7561
SVG                             20              5              9           6325
CSS                             13            379            135           2013
HTML                             2             31             40           1411
Markdown                         7             78              0            514
TeX                              1             20              0            194
JSON                             2             11              0            182
Python                           4             16              1             77
-------------------------------------------------------------------------------
SUM:                            97           8812          11779         212357
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

[editorialbot]

Wordcount for paper.md is 1276

[editorialbot]

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

OK DOIs

- 10.17613/fc1c-mx52 is OK
- 10.18061/emr.v16i1.7643 is OK
- 10.14361/9783839451458-015 is OK
- 10.1145/3543882.3543892 is OK
- 10.1525/JAMS.2016.69.1.273 is OK
- 10.1145/3243907.3243911 is OK
- 10.1007/s00799-018-0262-x is OK
- 10.1145/3543882.3543891 is OK
- 10.1145/2872518.2890529 is OK
- 10.18716/ride.a.15.2 is OK

MISSING DOIs

- None

INVALID DOIs

- https://doi.org/10.1145/3358664.3358666 is INVALID because of 'https://doi.org/' prefix

[editorialbot]

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

[wergo]

Thank you for your messages.

As potential reviewers from the Music Encoding community, we would like to recommend Perry Roland (pe-ro) or Craig Sapp (craigsapp), however, both of them are not on the list you recommended.

Of the reviewers from your list, Adam Michael Wood (adammichaelwood), Sam Hames (SamHames) or Rebecca Sutton Koeser (rlskoeser) would be a good fit based on the keywords Digital Humanities, Web applications, or Music provided on their profiles.

[arfon]

@editorialbot generate pdf

[editorialbot]

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

[editorialbot]

Five most similar historical JOSS papers:

py2lispIDyOM: A Python package for the information dynamics of music (IDyOM) model
Submitting author: @xinyiguan
Handling editor: @faroit (Active)
Reviewers: @AoifeHughes, @hayesall
Similarity score: 0.7961

libfmp: A Python Package for Fundamentals of Music Processing
Submitting author: @fzalkow
Handling editor: @arfon (Active)
Reviewers: @brunaw, @expectopatronum
Similarity score: 0.7940

A flexible search system for high-accuracy identification of biological entities and molecules
Submitting author: @maxkfranz
Handling editor: @galessiorob (Active)
Reviewers: @AlexanderPico, @rabdill, @apcamargo
Similarity score: 0.7888

GIMS: Graphical Interface for Materials Simulations
Submitting author: @kokookster
Handling editor: @jgostick (Active)
Reviewers: @marshallmcdonnell, @jgostick
Similarity score: 0.7875

Open-Unmix - A Reference Implementation for Music Source Separation
Submitting author: @faroit
Handling editor: @arokem (Retired)
Reviewers: @bmcfee, @hagenw
Similarity score: 0.7846

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before before considering asking the reviewers of these papers to review again for JOSS.

[arfon]

@editorialbot invite @faroit as editor

👋 @faroit – would you be willing to edit this submission for JOSS?

[editorialbot]

Invitation to edit this submission sent!

[faroit]

@editorialbot assign @faroit as editor

[editorialbot]

Assigned! @faroit is now the editor

[faroit]

👋 Hi @wergo, thanks for your submission to JOSS! I will be serving as the editor for this. We'll use this issue to identify reviewers and resolve technical issues.

Thank you already for providing a list of reviewers with domain knowledge. I would also like to ask Stefan Balke (@ stefan-balke). Can you please check if this would be fine wrt to the JOSS COI policy?

[wergo]

Dear @faroit, sorry for the late response. While I was reading your message, I was under the impression that you ask Stefan Balke whether he has a COI. But probably you addressed this question to us.

I can declare no conflict of interest with Stefan Balke. Both authors (David Weigl and me) do not know Stefan Balke in person and have not collaborated with him.

[faroit]

👋 @pe-ro @craigsapp @adammichaelwood @SamHames @rlskoeser - would any of you be willing to review this submission for JOSS? The JOSS review process takes place on GitHub and focuses on the software and a short paper. We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html

The software under review is https://github.com/mei-friend/mei-friend

This issue is a "pre-review" issue in which reviewers are assigned. Once sufficient reviewers are recruited we will open a dedicated review issue where the review will take place.

[faroit]

@editorialbot add @stefan-balke as reviewer

[editorialbot]

@stefan-balke added to the reviewers list!

[rlskoeser]

@faroit I'm willing to review.

[faroit]

@editorialbot add @rlskoeser as reviewer

[editorialbot]

@rlskoeser added to the reviewers list!

[faroit]

@rlskoeser thank you for helping out!

[faroit]

@editorialbot start review

[editorialbot]

OK, I've started the review over in #6002.