Inconsistent config filename, param names and default values

The loaded config and named parameters are inconsistent over all projects.
Shouldn't they be standardised 🤔? If so, what's the right filename and params?

• ~/.openml/config (file) and ~/.openml/cache(directory)?
• apikey, server=https://www.openml.org/api, cachedir=~/.openml/cache?

What do you think?

R
Path (saveOMLConfig.R#L18): ~/.openml/config
Params (config_helpers.R#L20-L25):

server = "http://www.openml.org/api/v1",
cachedir = file.path(tempdir(), "cache"),
verbosity = 1L,
arff.reader = "farff",
apikey = "",
confirm.upload = TRUE

Python
Path (config.py#L26): ~/.openml/config
Params (config.py#L19-L23):

'apikey': None,
'server': "https://www.openml.org/api/v1/xml",
'verbosity': 0,
'cachedir': os.path.expanduser('~/.openml/cache'),
'avoid_duplicate_runs': 'True',

Java
Path (saveOMLConfig.R#L18): ~/.openml/openml.conf
Params:

• cache_allowed Config.java#L74
• cache_directory Config.java#L79
• api_key Config.java#L120
• server Config.java#L127
• tags Config.java#L131

The following projects doesn't support a config file:

• .NET (OpenMlConnector.cs#L33 (OpenMlConnector constructor))
• Weka (pom.xml#L106-L110, (OpenmlConnector constructor))

Start by comparing R/saveOMLConfig.R and R/config_helpers.R, Python's openml/config.py, Java's Config.java, and the OpenMlConnector constructors in .NET and Weka. Define the cross-client filename, parameter names, defaults, and support expectations, then verify that the affected projects follow the agreed convention.