<div dir="ltr"><div><div>It looks like we need someone with high (> 1500 reputation) to create the new [yt] tag on StackOverflow.<br><br></div>I'll try asking and then immediately answer a few yt questions next weekend and just tag it with [python], [visualization], and [scientific-computing].<br>
<br></div>-Nathan<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 18, 2013 at 10:46 AM, Britton Smith <span dir="ltr"><<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This all sounds fine to me. I'm cool with giving SO a try. It would definitely be nice to have stock answers to common questions in a more easily searchable place.<div>
<br></div><div>If this starts happening, someone please report back here and let others know what we have to do to get involved.</div><span class="HOEnZb"><font color="#888888">
<div><br></div><div>Britton</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 18, 2013 at 3:49 AM, Sam Skillman <span dir="ltr"><<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Okay so I think I've switched my opinion on using scicomp here, primarily based on the discussion here: <a href="http://meta.scicomp.stackexchange.com/questions/338/can-scicomp-stackexchange-be-used-for-project-specific-questions/339#339" target="_blank">http://meta.scicomp.stackexchange.com/questions/338/can-scicomp-stackexchange-be-used-for-project-specific-questions/339#339</a></div>
<div><br></div><div>The main point is -- if the questions are general in nature, i.e. "what would be a good way to visualize/analyze this data in this way" would be great, but questions of "i'm having a problem using feature X in frontend Y" would not be appropriate. Personally, I can imagine many more very yt-specific questions being asked as opposed to big picture, but maybe i'm wrong. I'd say we just start using stack overflow and see how it shakes out.</div>
<div><br></div><div>If we're game, I'd say we ask a few planted questions and answer them ourselves, and if a question comes up on a mailing list that is answered on SO, then point to it. </div><span><font color="#888888"><div>
<br></div><div>
Sam</div></font></span></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 17, 2013 at 12:27 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alright, so I guess we're in sort-of agreement? What's next? Do we<br>
want to just skip the main site, try for SciComp, encourage people<br>
(and even ask/answer questions ourselves) and start following the tag?<br>
<div><div><br>
On Sun, Nov 17, 2013 at 12:17 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>> wrote:<br>
> I'd be happy to reach out to the sci comp folks. They field questions for a<br>
> few other codes so it may be a good fit.<br>
><br>
> I'm a +1 on trying it out. It also has the added benefit of a rewards<br>
> structure.<br>
><br>
> Sam<br>
><br>
> On Nov 17, 2013 11:11 AM, "Nathan Goldbaum" <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>> wrote:<br>
>><br>
>> Didn't realize one needs very high reputation to create a new tag - I<br>
>> guess that makes sense though.<br>
>><br>
>> While fragmentation is bad, I'd argue that StackOverflow's high google<br>
>> ranking negates that somewhat.<br>
>><br>
>> Are there any SO users with high reputations who might be interested in<br>
>> creating the tag?<br>
>><br>
>> Barring that, the scicomp beta exchange is also probably a good fit.<br>
>><br>
>> On Sunday, November 17, 2013, Matthew Turk wrote:<br>
>>><br>
>>> Hi Nathan,<br>
>>><br>
>>> On Sun, Nov 17, 2013 at 12:01 AM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>><br>
>>> wrote:<br>
>>> > Hi all,<br>
>>> ><br>
>>> > I recently subscribed to the [yt] tag on StackExchange. Now, whenever<br>
>>> > a<br>
>>> > question is asked using this tag on any StackExchange site, I will get<br>
>>> > an<br>
>>> > e-mail about it, just like if a question is asked on the users or dev<br>
>>> > list.<br>
>>> > Currently (as far as I can tell) zero questions have been asked using<br>
>>> > this<br>
>>> > tag...<br>
>>> ><br>
>>> > If there are a few others who are interested in subscribing to the tag,<br>
>>> > I<br>
>>> > think it might be worthwhile to add StackOverflow to the website and<br>
>>> > docs<br>
>>> > where we describe how to get help and also announce on the user’s list<br>
>>> > that<br>
>>> > StackOverflow is an alternate place to ask questions.<br>
>>> ><br>
>>> > While this might split the community somewhat - not everyone will be<br>
>>> > subscribed to StackOverflow and thus might miss useful info - I think<br>
>>> > moving<br>
>>> > some helpful suggestions to StackOverflow will massively improve<br>
>>> > googleability of common yt issues, allowing us to avoid answering the<br>
>>> > same<br>
>>> > questions over and over again.<br>
>>> ><br>
>>> > It might also be worthwhile to ask and answer some common yt questions.<br>
>>> > Off<br>
>>> > the top of my head, I think we could at least answer how to load<br>
>>> > various<br>
>>> > types of datasets into yt.<br>
>>><br>
>>> In principle, I'm okay with this. But I have a few concerns --<br>
>>><br>
>>> 1) I don't think the tag "yt" can be created unless someone with high<br>
>>> reputation does so. (<br>
>>> <a href="http://stackoverflow.com/help/privileges/create-tags" target="_blank">http://stackoverflow.com/help/privileges/create-tags</a> )<br>
>>> 2) We have well-defined usage metrics that we can quantify based on<br>
>>> mailing list activity, so this may fragment that.<br>
>>> 3) Many of the existing contributors and users don't want another inbox.<br>
>>><br>
>>> *However*. SO is really quite good for evolving questions and for an<br>
>>> updateable reference. I do really like that aspect. But I think we<br>
>>> may find ourselves getting a bit fragmented -- in fact, what I see as<br>
>>> being a possible outcome is that if yt does end up growing into an<br>
>>> interdisciplinary space, we'd see people from non-Astro disciplines<br>
>>> using it, but retaining our original core audience here. All your<br>
>>> points really are good ones.<br>
>>><br>
>>> I don't know. Could be awesome. And, I'd like to see us embrace more<br>
>>> modern and useful methods of communication and outreach. So ... I<br>
>>> guess the experiment could be a good one!<br>
>>><br>
>>> -Matt<br>
>>><br>
>>> ><br>
>>> > -Nathan<br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > yt-dev mailing list<br>
>>> > <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> ><br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>