astropy
Better plan presence/talks at conferences
Could you pls be specific about what conferences you're thinking of here? Also, what do you see as the goals of the presence?
What I mean specifically is that we should make sure that we always apply for talks at relevant conferences/workshops - what this would take the form of is a table of upcoming conferences with someone assigned to apply for a talk, and if none of us can do it, we could approach others in the collaboration.
Sorry to nag on this a bit but this is important and I want us to have as a clear focus as possible.
I assume you’re talking about things like SciPy. What other conferences are there? (There’s the Astro one..ADASS, right?) DotAstro? PyAstro? What communities do we target by being visible at these conferences (e.g., Research software dev, open source, etc)?
And for each of these conferences, what’s the goal of having an Astropy presence?
(I know there are lots of good answers to these questions, I just want to hear them, especially from y’alls perspective. I want to make sure we do things with strategy and purpose.)
On Tue, Sep 27, 2016 at 4:03 AM, Thomas Robitaille <[email protected]
wrote:
What I mean specifically is that we should make sure that we always apply for talks at relevant conferences/workshops - what this would take the form of is a table of upcoming conferences with someone assigned to apply for a talk, and if none of us can do it, we could approach others in the collaboration.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/astropy/coordination/issues/77#issuecomment-249794347, or mute the thread https://github.com/notifications/unsubscribe-auth/ABYJma64gml7NMEnPq1L7FHIU3wp9oFuks5quM3IgaJpZM4Jzk03 .
Kelle Cruz, PhD — http://kellecruz.com/ 917.725.1334 — Hunter: x16486 — AMNH: x3404
Having gone to my first ADASS this year, I want to bring this back up. I think our project presence at ADASS should be significant and coordinated. Right now, we don't really have anyone taking on this role with the gusto it deserves.
This is part of the Learn Team stuff now. No need to keep such an old issue open? Individual conference can have their own issue.
This is actually separate from Learn but yes, it is a designated role so fine to close.