Closed smrgeoinfo closed 10 years ago
@smrazgs thanks. Comments:
target_property
to keep consistent with the other field names?I agree the pull requests would technically fill the bill, but the pull request might be considered the first step to get a proposal on the board (the repository owner would be expected to filter out junk requests, but nothing else). For GitHub Newbies, it might not be obvious how to look at pull request to see what’s been proposed—having it explicit in the register would avoid that. I suppose this would mean a process in which there is a thread in the issue tracker for each proposed term that would be closed with a pull request to change proposed to adopted. Initially the process could be some sort of time-limited comment period.
The ‘_’ vs. ‘-‘ vs CamelCase thing… I agree they should all be one way or the other. I prefer lowerCamelCase for property names, but I’m not religious about it.
steve
Stephen M Richard Arizona Geological Survey 416 W. Congress #100 Tucson, AZ AZGS: 520-770-3500 Office: 520-209-4127 FAX: 520-770-3505
From: Tom Kralidis [mailto:notifications@github.com] Sent: Thursday, March 06, 2014 7:48 AM To: OSGeo/Cat-Interop Cc: Steve Richard Subject: Re: [Cat-Interop] add status, targetProperty, and submitter fields (#7)
@smrazgshttps://github.com/smrazgs thanks. Comments:
— Reply to this email directly or view it on GitHubhttps://github.com/OSGeo/Cat-Interop/pull/7#issuecomment-36894305.
for better registry operation. example content in new fields