Whedon the Bot

ropensci requirements : https://hackmd.io/KxM9HK-eSo-x2nkTOSBeow

• whedon is not currently generatized

• whedon can assign the reviewer to issues, decide what to respond to, who to ping

• Complexity – has to do with the journal – cross ref, compiling papers, etc//

• Arfon is willing to help us to "patch up" whedon to work for us … and wants to build it out

• current written in ruby

• helps with assigning reviewers, responding to issues

  • editors – defined as a github team (we should do that!)
  • editors have priceledges

Could whedon help us track packages and submittors and reviewers in a document somwehre or database??

• ropensci – has a good practice report, set of conventions that they want the community to follow – look into what this is.
• Whendon only looks at the issue – doesn't write out somewhere to help track items over time
• do donations wrok for organizations???

The joss website – is backed by a database
we could consider a separate script to generate a report from the github issue itself and track that over time

• reminders –
• only happens if their checklist isn't complete
• looks for string Review checklist for @reviewer…
• whedon assumes that the review comment has been started
  • might be able to refine this a bit to look for a comment or something that suggests that the review has been submitted
  • the one difference with joss is they have a website submission and we (and ropensci) have the users create an issue
  • Arfon might try to write a proposal around this
  • arfon might try to work on some code rewrites over the next few weeks…