[WIP] initial commit of NumPy-based CoC and reporting manual #1062
Conversation
|
Addresses #1053 |
CODE_OF_CONDUCT.md
Outdated
| considering your report. Alternatively, if for any reason you feel | ||
| uncomfortable making a report to the committee, then you can also contact: | ||
|
|
||
| - ***somebody other than pysaler 1, 2, or James*** |
There was a problem hiding this comment.
tough one... I'd be tempted to say that you can always go to @sjsrey, but that's not quite in the spirit of the original document. We might need to think about a good external.
There was a problem hiding this comment.
I thought this article on designing a code of conduct was informative. It is not clear if these policies require an "outside" person. It would be great to have numfocus as an outside participant in pysal's CoC. However, pysal's size and numfocus's other duties may not necessitate/allow for this. I think listing @sjsrey as the committee backup is reasonable, I would also be happy to take this role.
|
Looks good to me! Thank you for preparing this, @jGaboardi! It will probably be reasonable to move this to pysal.org similar to scipy. |
|
@weikang9009 that's a good idea. @dfolch you had mentioned a few ideas last week at NARSC. Would you be able to put them in here? |
|
potential external participant (once we get our issues sorted):
we could also ask Numfocus if they would be interested to do external conflict resolution (they already do it for SciPy and NumPy):
|
|
@weikang9009 Should this issue/PR be migrated to the |
|
@slumnitz Following @weikang9009 's suggestion do you agree that we should close the PR here and open in back up in pysal.site? Does anyone else have comments/thoughts/suggestions? |
|
Migrating to pysal/pysal.github.io#76 |
This is an initial Code of Conduct document which is based on the Numpy CoC. I volunteer to be on the CoC committee.
To Do:
Create new pysal-conduct@googlegroups.com for reporting?Find two other
pysalersto volunteers.Need a non-
pysalerfor reports involving committee.