Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mailing list info #340

Merged
merged 1 commit into from Aug 29, 2015

Conversation

Projects
None yet
3 participants
@bcipolli
Copy link
Contributor

commented Aug 25, 2015

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.

README.rst Outdated
@@ -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:

This comment has been minimized.

Copy link
@matthew-brett

matthew-brett Aug 25, 2015

Member

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.

This comment has been minimized.

Copy link
@bcipolli

bcipolli Aug 25, 2015

Author Contributor

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?

This comment has been minimized.

Copy link
@matthew-brett

matthew-brett Aug 25, 2015

Member

Sure - github issues if it may be a bug, mailing list for general questions or advice about raising an issue.

@matthew-brett

This comment has been minimized.

Copy link
Member

commented Aug 28, 2015

Ben - would you mind finishing up this one? I think we're nearly ready to go for a release.

@bcipolli

This comment has been minimized.

Copy link
Contributor Author

commented Aug 28, 2015

@matthew-brett how's this latest change work for you?

@matthew-brett

This comment has been minimized.

Copy link
Member

commented Aug 28, 2015

How about

please see the ``neuroimaging`` mailing list
@bcipolli

This comment has been minimized.

Copy link
Contributor Author

commented Aug 28, 2015

good call. Fixed.

README.rst Outdated
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:

This comment has been minimized.

Copy link
@matthew-brett

matthew-brett Aug 28, 2015

Member

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?

This comment has been minimized.

Copy link
@effigies

effigies Aug 28, 2015

Member

What about:

Github issues may also be used to report bugs, contribute code, or see a list of known bugs and planned changes:
README.rst Outdated
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:

This comment has been minimized.

Copy link
@effigies

effigies Aug 28, 2015

Member

Sorry, grammar tweak: No comma, since the last part wouldn't be a full sentence on its own, and the list is now two items long.

@bcipolli

This comment has been minimized.

Copy link
Contributor Author

commented Aug 28, 2015

@effigies @matthew-brett how's the latest? I even squashed the commits... embarrassing. :)

@effigies

This comment has been minimized.

Copy link
Member

commented Aug 28, 2015

What, you don't want 6 commits for a +6/-2?

LGTM.

README.rst Outdated
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:

This comment has been minimized.

Copy link
@matthew-brett

matthew-brett Aug 28, 2015

Member

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
@bcipolli

This comment has been minimized.

Copy link
Contributor Author

commented Aug 29, 2015

@matthew-brett made the changes you requested.

@matthew-brett

This comment has been minimized.

Copy link
Member

commented Aug 29, 2015

Sorry to be so boring about it - thanks for keeping going.

matthew-brett added a commit that referenced this pull request Aug 29, 2015

Merge pull request #340 from bcipolli/update_mailing_lists
MRG: Update mailing list info

Update information about where to get help.

@matthew-brett matthew-brett merged commit 6259598 into nipy:master Aug 29, 2015

0 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
coverage/coveralls Coverage pending from Coveralls.io
Details

@bcipolli bcipolli deleted the bcipolli:update_mailing_lists branch Aug 31, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.