[PRE REVIEW]: RangeEnclosures.jl: A framework to bound function ranges

[whedon]

Submitting author: @lucaferranti (Luca Ferranti) Repository: https://github.com/JuliaReach/RangeEnclosures.jl Version: Editor: @odow Reviewers: @dpsanders, @blegat Managing EiC: Mathieu Besançon

Author instructions

Thanks for submitting your paper to JCON @lucaferranti. Currently, there isn't an JCON editor assigned to your paper.

The author's suggestion for the handling editor is @carstenbauer.

@lucaferranti if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JCON and may be suitable for this submission (please start at the bottom of the list).

Editor instructions

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

@whedon commands

[whedon]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[lucaferranti]

@whedon check references

[whedon]

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

OK DOIs

- 10.29007/zzc7 is OK
- 10.1146/annurev-control-071420-081941 is OK
- 10.1137/141000671 is OK
- 10.1023/A:1021368627321 is OK
- 10.1023/B:NUMA.0000049462.70970.b6 is OK
- 10.1137/1.9780898717716 is OK
- 10.21105/jcon.00097 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[blegat]

@odow Happy to

[schillic]

@whedon generate pdf

[whedon]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[schillic]

(This was a minor change - see https://github.com/JuliaReach/RangeEnclosures.jl/pull/114)

[carstenbauer]

@whedon remove @odow as editor

[whedon]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@whedon commands

[carstenbauer]

@whedon assign @carstenbauer as editor

[whedon]

OK, the editor is @carstenbauer

[carstenbauer]

@whedon assign @odow as editor

[odow]

@whedon add @dpsanders as reviewer

[whedon]

I'm sorry @odow, I'm afraid I can't do that. That's something only editors are allowed to do.

[carstenbauer]

@whedon add @dpsanders as reviewer

[whedon]

OK, @dpsanders is now a reviewer

[odow]

@whedon add @blegat as reviewer

[whedon]

I'm sorry @odow, I'm afraid I can't do that. That's something only editors are allowed to do.

[carstenbauer]

@whedon add @blegat as reviewer

[whedon]

OK, @blegat is now a reviewer

[carstenbauer]

@whedon assign @carstenbauer as editor

[whedon]

OK, the editor is @carstenbauer

[carstenbauer]

@whedon assign @odow as editor

[carstenbauer]

@whedon assign @odow as editor

[carstenbauer]

First of all, sorry for this noise everyone, we are having some Whedon issues.

@odow: I hope that things work now (I've added you to the "editor" sub-team of the GitHub organization). Would be great if you could try with @whedon start review (given that you're ready to go to the review stage with this submission).

[lucaferranti]

@carstenbauer I am not sure if JCON whedon has some tweaks compared to the original one. At least in JOSS the bot has had some updates (including renaming to @editorial-bot), if you dont have any extra features maybe updating with upstream could help the workflow? (you maybe already thought about it and there are good reasons / issues for not switching)

[carstenbauer]

@lucaferranti Yes, we are already upgrading in the background to the new GitHub-action based workflow but decided, for various reasons, to still go with good-old Whedon for this round of submissions. We hope to use the new system for JuliaCon2023.

Anyways, thanks for pointing it out.

[odow]

@whedon start review

[whedon]

I'm sorry @odow, I'm afraid I can't do that. That's something only editors are allowed to do.

[arfon]

@whedon list editors

[whedon]

Current editors:

@arfon
@carstenbauer
@matbesancon
@ranjanan
@vchuravy

[arfon]

@whedon list editors

[whedon]

Current editors:

@arfon
@carstenbauer
@matbesancon
@ranjanan
@vchuravy

[odow]

@whedon list editors

[whedon]

Current editors:

@arfon
@carstenbauer
@matbesancon
@odow
@ranjanan
@vchuravy

[odow]

@whedon start review

[odow]

@whedon start review

[matbesancon]

@whedon start review

[matbesancon]

@whedon begin review

[whedon]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@whedon commands

[matbesancon]

@whedon commands

[whedon]

Here are some things you can ask me to do:

# List all of Whedon's capabilities
@whedon commands

# Assign a GitHub user as the sole reviewer of this submission
@whedon assign @username as reviewer

# Add a GitHub user to the reviewers of this submission
@whedon add @username as reviewer

# Re-invite a reviewer (if they can't update checklists)
@whedon re-invite @username as reviewer

# Remove a GitHub user from the reviewers of this submission
@whedon remove @username as reviewer

# List of editor GitHub usernames
@whedon list editors

# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers

# Change editorial assignment
@whedon assign @username as editor

# Set the software archive DOI at the top of the issue e.g.
@whedon set 10.0000/zenodo.00000 as archive

# Set the software version at the top of the issue e.g.
@whedon set v1.0.1 as version

# Open the review issue
@whedon start review

EDITORIAL TASKS

# All commands can be run on a non-default branch, to do this pass a custom 
# branch name by following the command with `from branch custom-branch-name`.
# For example:

# Compile the paper
@whedon generate pdf

# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name

# Remind an author or reviewer to return to a review after a
# certain period of time (supported units days and weeks)
@whedon remind @reviewer in 2 weeks

# Ask Whedon to do a dry run of accepting the paper and depositing with Crossref
@whedon recommend-accept

# Ask Whedon to check the references for missing DOIs
@whedon check references

# Ask Whedon to check repository statistics for the submitted software
@whedon check repository

EiC TASKS

# Invite an editor to edit a submission (sending them an email)
@whedon invite @editor as editor

# Reject a paper
@whedon reject

# Withdraw a paper
@whedon withdraw

# Ask Whedon to actually accept the paper and deposit with Crossref
@whedon accept deposit=true

[matbesancon]

@whedon list editors

[whedon]

Current editors:

@arfon
@carstenbauer
@matbesancon
@odow
@ranjanan
@vchuravy

[matbesancon]

@whedon list reviewers

[whedon]

Here's the current list of reviewers: http://bit.ly/2V9GSFq

[matbesancon]

@whedon start review

[matbesancon]

@whedon maybe consider engaging a review

[whedon]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@whedon commands

[matbesancon]

@whedon start review