{"action":"opened","issue":{"url":"https://api.github.com/repos/codemeta/codemetar/issues/22","repository_url":"https://api.github.com/repos/codemeta/codemetar","labels_url":"https://api.github.com/repos/codemeta/codemetar/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/codemeta/codemetar/issues/22/comments","events_url":"https://api.github.com/repos/codemeta/codemetar/issues/22/events","html_url":"https://github.com/codemeta/codemetar/issues/22","id":243524331,"number":22,"title":"Should we be using a Non-DESCRIPTION home for additional metadata fields?","user":{"login":"cboettig","id":222586,"avatar_url":"https://avatars3.githubusercontent.com/u/222586?v=4","gravatar_id":"","url":"https://api.github.com/users/cboettig","html_url":"https://github.com/cboettig","followers_url":"https://api.github.com/users/cboettig/followers","following_url":"https://api.github.com/users/cboettig/following{/other_user}","gists_url":"https://api.github.com/users/cboettig/gists{/gist_id}","starred_url":"https://api.github.com/users/cboettig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cboettig/subscriptions","organizations_url":"https://api.github.com/users/cboettig/orgs","repos_url":"https://api.github.com/users/cboettig/repos","events_url":"https://api.github.com/users/cboettig/events{/privacy}","received_events_url":"https://api.github.com/users/cboettig/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-17T20:53:54Z","updated_at":"2017-07-17T20:53:54Z","closed_at":null,"body":"CRAN's [_Writing R Extensions_](https://cran.r-project.org/doc/manuals/r-release/R-exts.html#The-DESCRIPTION-file) clearly states that we *can* add additional fields:\r\n\r\n> There is no restriction on the use of other fields not mentioned here (but using other capitalizations of these field names would cause confusion). Fields Note, Contact (for contacting the authors/developers9) and MailingList are in common use. Some repositories (including CRAN and R-forge) add their own fields.\r\n\r\nAnd from [_CRAN Policies_](https://cran.r-project.org/web/packages/policies.html)\r\n\r\n> Additional DESCRIPTION fields could be used for providing email addresses for contacting the package authors/developers (e.g., ‘Contact’), or a URL for submitting bug reports (e.g., ‘BugReports’).\r\n\r\nHowever, using an unrecognized field does throw a NOTE (though you'll need to be using `devtools::check(check_version=TRUE)` or `devtools::release()` to see it)\r\n\r\n```\r\nchecking CRAN incoming feasibility ... NOTE\r\nMaintainer: ‘Carl Boettiger <cboettig@gmail.com>’\r\n\r\nUnknown, possibly mis-spelled, fields in DESCRIPTION:\r\n  ‘keywords’\r\n```\r\n\r\nThe list of recognized terms appears in the ``tools:::.get_standard_DESCRIPTION_fields()`, see source:  https://github.com/wch/r-source/blob/trunk/src/library/tools/R/utils.R#L1179.  (Thanks @kevinushey).  \r\n\r\n\r\nGiven the policies above, and as the NOTE suggests, this CRAN check may only be as a hack to check spelling in the DESCRIPTION file, so it's not clear whether or not CRAN would object to the term above.  OTOH, it would certainly give us pause to start all rOpenSci packages throwing an extraneous note to indicate `provider: https://rOpenSci.org` or something similar.  \r\n\r\n\r\nAlternatively, `codemetar` users could just enter additional fields manually into the `codemeta.json` or through dedicated R functions, but this does seem a bit clunky.  \r\n"}}
{"actor":{"display_login":"cboettig"}}