Our advice (and reviewer checklist) asks for the code of conduct to be linked and suggests using the usethis function, https://devguide.ropensci.org/collaboration.html#friendlyfiles. This means that most developers will use the default usethis code of conduct. Two questions:

1. Wouldn't it be better for us to tell authors to add a link to ropensci's code of conduct at https://ropensci.org

This blog post by C. Titus Brown might make a useful cc article. Relatively simple. Targeted at people who run a lot of data through scripts and tools more than people developing software per se.

http://ivory.idyll.org/blog/2020-software-and-workflow-dev-practices.html

In Settingsconfiguration.java we create directories using mkdirs(). We should check the return type and print an error message to the log, if the directory could not be created

Findbugs output:

Exceptional return value of java.io.File.mkdirs() ignored in org.getaviz.generator.SettingsConfiguration.loadConfig(String)

Exceptional return value of java.io.File.mkdirs() ignored in org.getav

Sometimes, developers write useless javadocs such as the example below

/**
 * Some Foo Method.
 * @param id the id
 * @return 
*/
int someFooMethod(int id){ return 0; }

The plugin should spot this kind of "documentation" and present them into the report.
A common pattern to detect such useless javadocs are:

• the method documentation includes only the name of the method,

Tip to further improve the wiki:

Extend the "getting started" section with requirements regarding tools and platform needed to install/use HQ :

• Jenkins/Bamboo or other build tool including plugin x and y
• docker pull or native installation
• Server or VM with unrestricted internetaccess
• Python
• VCS
• etc

Various indicators need to be worked out more thoroughly. Some comments we got:

• a lot of questions could be merged and also made more qualitative - more descriptions
• De volgende items moeten denk ik nog wat uitgewerkt worden en concreter worden. Nu zou ik niet weten hoe ik software kan schrijven die eraan voldoet: D4 PF1 PF2 PF3 CH1

Labels showing the commitId should be changed so that they also show the date and time of the according commit. So the user can remember what commit he chose.

Examples:

• ComparisonContainer => Headlines in the table should be added with date
• Tooltips
• tbc

The develop role should be allowed to ignore issues. The quality manager can edit report configurations. Open issue: rights per report?

Sentry Issue: THOTH-3Y3

An unhandled error occurred during extraction of image "quay.io/thoth-station/image-store:cuda-44324038910ae778b3d15bd2ea80148c8ddcb95f310ccabe6f0499003c0425bd": time="2020-02-19T23:16:47Z" level=fatal msg="Error determining repository tags: Invalid status code returned when 

In Guided Notebooks, there is a link to Example sections in a Google Doc. The document does not seem to contain those referenced sections.