Using "Github Issues" for NCEAS working group communication

[cboettig]

Hi folks,

Just a few quick notes on using these issues for working group communication:

• If you aren't interested in any getting any emails related to new issues, you can just unsubscribe from all notifications by going to the repository home page and clicking the button that says "unwatch"
• If you want to get notifications but do not want to follow certain threads (issues) that aren't relevant to you, you can go to the github page for that issue and click the "unsubscribe" button that appears on the left sidebar (under the word "Notifications").
• If you reply to an issue using your email client, a copy will still appear in the online thread and still be forwarded to anyone watching the issue.
• If you've turned off any notifications, you can still see the discussions by visiting the Github repo online. You can also choose which issues you do want to follow. When you create or comment on an issue, you are automatically subscribed.
• Issues written in the online editor use Github markdown syntax to add formatting like links, bullets, or images. Mentioning a user like @mbjones creates a link to their profile and sends them a notification. Replies via email are shown as plain-text and won't use these formatting tricks.
• You can mention an issue in a commit message just by using it's number, such as #1. This is a good way to connect what changes you actually made to the discussion.
• Issues can be labeled, assigned to individual users, and grouped into milestones. We can use these features as we see fit. (the default labels may not be useful, feel free to remove them and add others). When issues are resolved they can be marked "closed".

Sorry for the inbox clutter and hope this helps!

@cboettig

p.s. @davharris @emchristensen @julieripplinger it appears your issue #1 was lost when issues were toggled off and toggled back on. Not sure about the details, but it does seem your email thread is still active. Others might have a better idea what happened there.

[davharris]

Thanks @cboettig!

The email discussion actually wasn't focused on an issue, it stemmed from a comment on some code for the rodents data set.