-
Notifications
You must be signed in to change notification settings - Fork 118
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
Create Slack workspace for Athena++ #61
Comments
I'm interested. |
Same here!
…On Thu, Jan 25, 2018 at 4:23 PM, Matt Coleman ***@***.***> wrote:
I'm interested.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbN-6BFZM55WzB7XnfnwPKZ_ze_nLY6Hks5tOQ0OgaJpZM4RtoP2>
.
|
This seems helpful. I would be interested. |
This is a great idea.
Daniel
…Sent from my iPhone
On Jan 25, 2018, at 3:38 PM, Jonah Miller ***@***.***> wrote:
This seems helpful. I would be interested.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I will sign up. Kyle is dragging me kicking and screaming into the modern world. ;-)
… On Jan 25, 2018, at 6:08 PM, Kyle Gerard Felker ***@***.***> wrote:
Would anyone be interested / would try Slack as a platform for discussion of Athena++ development? Issues and pull requests on the GitHub repository would still be the main forum to discuss development details, but Slack could be a useful centralized place to share early results, ask general questions, and learn what others are working on and developing.
I think it would be much better than point-to-point email discussions for many topics. The Free Slack plan stores 10,000 messages of searchable history. Those who already use Slack (which I suspect is many of you) know that it is a very simple but flexible chat platform. You can easily attach plots, files, and inline code in your messages.
I have a private workspace setup under athena-pp.slack.com <x-msg://46/athena-pp.slack.com> that I have been using to monitor the commit activity and test results of my forked repository, but this content is in a separate channel. The workspace could be easily extended to serve a more general role.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#61>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEO7zuBNKubvZ1PavYvEHEEaR9zBj2W3ks5tOQlQgaJpZM4RtoP2>.
|
I have configured the workspace such that anyone with a I setup a few channels to compartmentalize the initial discussions of feature branches and other topics, e.g. |
Hi Kyle,
Although I still have a princeton email account, it is easier to use my UNLV account.
My UNLV account is zhaohuan.zhu@unlv.edu <mailto:zhaohuan.zhu@unlv.edu>
Thanks,
Zhaohuan
-----------------------------
Zhaohuan Zhu
Assistant Professor, Physics & Astronomy
University of Nevada - Las Vegas
Email: zhzhu@physics.unlv.edu
Homepage: www.physics.unlv.edu/~zhzhu
… On Jan 29, 2018, at 11:15 AM, Kyle Gerard Felker ***@***.***> wrote:
I have configured the workspace such that anyone with a @princeton.edu email can join automatically at https://join.slack.com/t/athena-pp/signup <https://join.slack.com/t/athena-pp/signup>. Otherwise, you can send me your email address ***@***.*** ***@***.***>) and I will send you an invite.
I setup a few channels to compartmentalize the initial discussions of feature branches and other topics, e.g. #particles, #radiation, #performance, but we can add or remove these as needed. It is probably best to use the default#general channel to start (please ignore the commit and Travis CI testing history, which was moved to a separate channel).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIO4vulGxRvUdy0V1Z-qqeum_kjFU_Kaks5tPhjSgaJpZM4RtoP2>.
|
Hi Kyle,
Can you add my email: yanfei@kitp.ucsb.edu
Thanks.
…On 2018-01-29 11:15, Kyle Gerard Felker wrote:
I have configured the workspace such that anyone with a @princeton.edu
email can join automatically at
https://join.slack.com/t/athena-pp/signup. Otherwise, you can send me
your email address ***@***.***) and I will send you an
invite.
I setup a few channels to compartmentalize the initial discussions of
feature branches and other topics, e.g. #particles, #radiation,
#performance, but we can add or remove these as needed. It is probably
best to use the default#general channel to start (please ignore the
commit and Travis CI testing history, which was moved to a separate
channel).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
*
Links:
------
[1]
#61 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/AIViJ29TK1CBZ3nj5819sUKqmpEmo4Emks5tPhjSgaJpZM4RtoP2
--
Yan-Fei Jiang
KITP Fellow
Kohn Hall,
University of California at Santa Barbara,
Santa Barbara, CA 93106
|
Hi Kyle,
Thanks for setting this u! My slack account name is ecostriker. I’m not completely sure which email I used to set it up (and I’d like to be consistent with my other projects) so if you can add me via username that’s best.
Thanks!
Eve
On Jan 26, 2018, at 12:08 AM, Kyle Gerard Felker ***@***.***> wrote:
Would anyone be interested / would try Slack as a platform for discussion of Athena++ development? Issues and pull requests on the GitHub repository would still be the main forum to discuss development details, but Slack could be a useful centralized place to share early results, ask general questions, and learn what others are working on and developing.
I think it would be much better than point-to-point email discussions for many topics. The Free Slack plan stores 10,000 messages of searchable history. Those who already use Slack (which I suspect is many of you) know that it is a very simple but flexible chat platform. You can easily attach plots, files, and inline code in your messages.
I have a private workspace setup under athena-pp.slack.com <x-msg://361/athena-pp.slack.com> that I have been using to monitor the commit activity and test results of my forked repository, but this content is in a separate channel. The workspace could be easily extended to serve a more general role.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#61>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFP8vabTTDKQ6XWcemhmbU8W2vnm8yWvks5tOQlQgaJpZM4RtoP2>.
============================================================================
============================================================================
Eve C. Ostriker
Professor of Astrophysical Sciences
email: eco@astro.princeton.edu Peyton Hall, 4 Ivy Lane
phone: 609-258-7240 Princeton University
FAX: 609-258-8226 Princeton, NJ 08544
|
@ecostriker, as far as I am aware, there is no such thing as a centralized Slack account--- your usernames/profiles for each workspace are completely independent. I don't think I can look up your account for other Slack workspaces, so let me know which email address you prefer to receive the invite |
Okay, I figured out that I am eco@astro.princeton.edu <mailto:eco@astro.princeton.edu>, so please add me as that to athena-pp.
I am able to switch from one workspace to another within slack, although I bet you’re right that it keeps track of what I’ve logged into and my identity may be different (even if I entered the same profile info).
Eve
On Jan 29, 2018, at 8:48 PM, Kyle Gerard Felker ***@***.***> wrote:
@ecostriker <https://github.com/ecostriker>, as far as I am aware, there is no such thing as a centralized Slack account--- your usernames/profiles for each workspace are completely independent. I don't think I can look up your account for other Slack workspaces, so let me know which email address you prefer to receive the invite
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFP8vT7L9GfNlcnk8q3qw-CQH-4vTCTFks5tPiCHgaJpZM4RtoP2>.
============================================================================
============================================================================
Eve C. Ostriker
Professor of Astrophysical Sciences
email: eco@astro.princeton.edu Peyton Hall, 4 Ivy Lane
phone: 609-258-7240 Princeton University
FAX: 609-258-8226 Princeton, NJ 08544
|
Hi Kyle, Could you also send me an invitation: xbai@tsinghua.edu.cn Thanks! |
Hi Kyle, Could you send me an invitation: pmullen2@illinois.edu Best, |
I will close this issue now that the Slack workspace is set up. |
Operator split cooling solver with subcycling
Would anyone be interested / would try Slack as a platform for discussion of Athena++ development? Issues and pull requests on the GitHub repository would still be the main forum to discuss development details, but Slack could be a useful centralized place to share early results, ask general questions, and learn what others are working on and developing.
I think it would be much better than point-to-point email discussions for many topics. The Free Slack plan stores 10,000 messages of searchable history. Those who already use Slack (which I suspect is many of you) know that it is a very simple but flexible chat platform. You can easily attach plots, files, and inline code in your messages.
I have a private workspace setup under athena-pp.slack.com that I have been using to monitor the commit activity and test results of my forked repository, but this content is in a separate channel. The workspace could be easily extended to serve a more general role.
The text was updated successfully, but these errors were encountered: