PR policy about data-and-utilities

[dericed]

I assembled a collection of resources that may offer clarity on this topic. See http://bfy.tw/3aZm.

[mdlincoln]

@dericed I think my question is not about "how pull requests work" per se, but about how the NYPL team would handle them for this particular repo. e.g. if I see a data formatting change I'd like done, is it worth me making the changes myself and submitting a PR, or would it be more efficient to submit an issue, assuming NYPL would have to replicate the scripted changes within their own data export workflow?

[dericed]

I don't at all speak for the project, but unless there is some documentation within the repo to indicate an exception to the expected use of GitHub, I'd suggest the following defaults:

• a new pull request be initiated by sending a new pull request
• a new issue be initiated by creating a new issue

[saverkamp]

@mdlincoln Thanks for the feedback! We've updated our documentation to include a pull request policy and to clarify our preferences for data correction suggestions. In short, we would love your pull requests for code examples, but we are not accepting pull requests for our datasets. You can send us metadata corrections through our Digital Collections feedback form or through email to [email protected]. If you have other suggestions for improving this repository, this is the place to do it.

Hope this helps,
Shawn

[mdlincoln]

Brilliant! 👍