Update mailing list info #340
Conversation
| @@ -37,9 +37,17 @@ Current information can always be found at the NIPY website:: | |||
| Mailing Lists | |||
| ============= | |||
|
|
|||
| Please see the developer's list:: | |||
| For questions on how to use nipy, please see NeuroStars: | |||
There was a problem hiding this comment.
I don't actually use neurostars. I'm not sure about Alexis or Bertrand, but I can't see them mentioned on neurostars at a quick search. I personally don't like the idea of splitting user and developer questions. So, I think we should continue to recommend the (new) mailing list for user questions.
There was a problem hiding this comment.
Sorry, my mistake--I thought this had been agreed on. Here's not the place for such a discussion, I just wanted to update things ASAP.
@matthew-brett how about using github issues? or should everything go through the mailing list?
There was a problem hiding this comment.
Sure - github issues if it may be a bug, mailing list for general questions or advice about raising an issue.
|
Ben - would you mind finishing up this one? I think we're nearly ready to go for a release. |
|
@matthew-brett how's this latest change work for you? |
|
How about |
|
good call. Fixed. |
| http://projects.scipy.org/mailman/listinfo/nipy-devel | ||
| https://mail.python.org/mailman/listinfo/neuroimaging | ||
|
|
||
| For new bug reports, a list of current bugs and planned changes, or to make code contributions, please see the Github issues: |
There was a problem hiding this comment.
Oops - sorry - way of rephrasing here so that people don't think they have to go to github issues in order to make code contributions?
There was a problem hiding this comment.
What about:
Github issues may also be used to report bugs, contribute code, or see a list of known bugs and planned changes:
|
@effigies @matthew-brett how's the latest? I even squashed the commits... embarrassing. :) |
|
What, you don't want 6 commits for a +6/-2? LGTM. |
| http://projects.scipy.org/mailman/listinfo/nipy-devel | ||
| https://mail.python.org/mailman/listinfo/neuroimaging | ||
|
|
||
| Github issues may also be used to report bugs or to see a list of known bugs and planned changes: |
There was a problem hiding this comment.
I know this is getting a bit embarrassing, but how about:
Please report bugs at github issues:
https://github.com/nipy/nipy/issues
You can see the list of current proposed changes at:
https://github.com/nipy/nipy/pulls
|
@matthew-brett made the changes you requested. |
|
Sorry to be so boring about it - thanks for keeping going. |
MRG: Update mailing list info Update information about where to get help.
We got an email to nipy-devel this morning. I thought I'd update the mailing list metadata to what I believe is the current recommendations.