Hi Matt.

I would definitely go to a little west coast meetup.

- Casey


On Thu, Oct 11, 2012 at 8:14 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi all,

Okay, what about the second set of dates?  March 4-8?

Although, to be perfectly honest, after how active the list has been
and how many things there have been discussed that would benefit from
-- or may even *require* -- in person contact, I am a bit bummed that
we can't get together sooner, to do things like talk about testing,
release schedules, better SPH/particle support, codifying analysis
modules and figuring out some packaging issues.

In December there's a scientific software workshop at TACC:

http://scisoftdays.org/meetings/2012/

Is anyone interested in going, and if so, perhaps having an in-person
meeting in the area held in conjunction with this?  Or, if not, then
maybe triyng to have a west coast meeting in December?  By then I
think the job scramble should have subsided considerably (certainly I
am counting on it for myself!) even if it picks up again a bit later.

-Matt

On Wed, Sep 19, 2012 at 8:04 PM, Britton Smith <brittonsmith@gmail.com> wrote:
> Hi all,
>
> I would prefer not the first set of dates.  I have a thing in Austin, TX on
> February 17.
>
> Britton
>
>
> On Wed, Sep 19, 2012 at 5:06 PM, Matthew Turk <matthewturk@gmail.com> wrote:
>>
>> Hi everyone,
>>
>> Okay, after a week or so we've had 13 positive responses.  January is
>> the worst month, so I'd like to suggest we investigate either February
>> or March.  California is the clear winner for locations, which I think
>> will also help out a lot with funding and with overall atmosphere.
>>
>> I'd like to propose we start talking about one of the following three
>> weeks -- we should then narrow down to a subset of days in the week.
>> Can anyone think of existing conflicts for, or obvious preferences
>> among:
>>
>> 1) February 18-22
>> 2) March 4-8
>> 3) March 25-29
>>
>> (An advantage of this time frame is that the elephant seals will be at
>> Año Nuevo, if we end up spending time at Santa Cruz.)  Once we have
>> narrowed down the week, we can write a proposal to HIPACC as Chris
>> suggested, and proceed from there.
>>
>> I think this could be a very, very successful meeting for our community.
>>
>> -Matt
>>
>> On Thu, Sep 13, 2012 at 1:22 PM, Christopher Moody <cemoody@ucsc.edu>
>> wrote:
>> > Hi everyone,
>> > Sorry to join this conversation late. I've talked about this (very
>> > briefly!)
>> > with Joel Primack for HIPACC funding, and he was very supportive that
>> > this
>> > we should write up a proposal. He comes back from China next week, so I
>> > can
>> > bring it up again then.
>> >
>> > Santa Cruz is a bit warmer than Chicago in January...
>> >
>> > chris
>> >
>> >
>> > On Thu, Sep 13, 2012 at 6:21 AM, Matthew Turk <matthewturk@gmail.com>
>> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >> We've had a good number of responses so far, all of them "Yes!".  If
>> >> you're a regular contributor to either the mailing list or the code
>> >> base, it would be really beneficial to submit a "Nope" response if you
>> >> know you wouldn't be able to attend.
>> >>
>> >>
>> >>
>> >> https://docs.google.com/spreadsheet/viewform?formkey=dHpZMjc4czJMQ2MtWERReVdiT0IxaFE6MQ#gid=0
>> >>
>> >> -Matt
>> >>
>> >> On Tue, Sep 11, 2012 at 11:34 AM, Matthew Turk <matthewturk@gmail.com>
>> >> wrote:
>> >> > Hi everyone,
>> >> >
>> >> > I like this idea a lot.  We had a really good success with this
>> >> > year's
>> >> > workshop, and I think we can build on that with a development-focused
>> >> > workshop sometime early next year.  I particularly like the way
>> >> > Nathan
>> >> > posed it:
>> >> >
>> >> > "...to have a group of us in a room together for a few days to hash
>> >> > out new features, discuss where the code is going, hear about the
>> >> > science yt is enabling, and make some solid progress on improving the
>> >> > code."
>> >> >
>> >> > My life is going to be a little bit complicated for a couple months,
>> >> > but I think aiming for a Winter quarter workshop would be best, as I
>> >> > think that will minimize conflicts with the usual fall
>> >> > obligations/cycle.  Unless there are strong arguments to hold the
>> >> > workshop in New York / Boulder, we should probably look into hosting
>> >> > in California somewhere.  (One respondent to the usage workshop we
>> >> > had
>> >> > this year was, "Chicago in January?  Really?")  I think we should
>> >> > certainly investigate HIPACC as an opportunity for funding, as well
>> >> > as
>> >> > the NSF; once we have figured out if we're going to hold it and
>> >> > where,
>> >> > we can begin those processes.
>> >> >
>> >> > Before we start digging in to properly planning something, we should
>> >> > definitely get a better idea of who would be interested in attending.
>> >> > I've set up a little survey here:
>> >> >
>> >> >
>> >> >
>> >> > https://docs.google.com/spreadsheet/viewform?formkey=dHpZMjc4czJMQ2MtWERReVdiT0IxaFE6MQ#gid=0
>> >> >
>> >> > Responses both for and against are useful information.  In a few days
>> >> > we'll see how things have turned out and we can take it from there.
>> >> >
>> >> > -Matt
>> >> >
>> >> > On Mon, Sep 10, 2012 at 3:45 PM, Anthony Scopatz <scopatz@gmail.com>
>> >> > wrote:
>> >> >> Matt and I talked about doing a yt-dev workshop at some point in the
>> >> >> near-ish future.  I am definitely +1 to this idea.
>> >> >>
>> >> >> Be Well
>> >> >> Anthony
>> >> >>
>> >> >>
>> >> >> On Mon, Sep 10, 2012 at 2:40 PM, Nathan Goldbaum
>> >> >> <nathan12343@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi Kacper,
>> >> >>>
>> >> >>> Right now there are no official plans for a yt workshop.  However,
>> >> >>> a
>> >> >>> few
>> >> >>> of us have discussed the possibility of having a
>> >> >>> development-focused
>> >> >>> workshop for ~20 people at UC Santa Cruz for 3-4 days sometime in
>> >> >>> the
>> >> >>> Winter
>> >> >>> quarter (Jan - Mar 2013).  I put forward UCSC as a possible
>> >> >>> location
>> >> >>> since
>> >> >>> there are a decent number of active users/developers here and in
>> >> >>> the
>> >> >>> Bay
>> >> >>> area, however I think a meeting in Boulder or NYC probably makes
>> >> >>> just
>> >> >>> as
>> >> >>> much sense.  For any of the options, we will need to look into
>> >> >>> funding
>> >> >>> for
>> >> >>> travel, hotels, etc for the participants.  I know that we applied
>> >> >>> for
>> >> >>> an NSF
>> >> >>> grant for the users workshop, is that still possible this time
>> >> >>> around?
>> >> >>> If
>> >> >>> it's going to be in California and we can make a case that there
>> >> >>> will
>> >> >>> be a
>> >> >>> good number of participants from UCs, we can probably apply for
>> >> >>> funding from
>> >> >>> HIPACC, although we need to discuss this possibility further with
>> >> >>> Joel
>> >> >>> Primack.
>> >> >>>
>> >> >>> I guess this is as good a time as any to ask: how do people feel
>> >> >>> about
>> >> >>> having a dev workshop sometime in the Winter quarter?  If you're
>> >> >>> supportive,
>> >> >>> do you have any preference for a location?  Personally I think it
>> >> >>> will
>> >> >>> be
>> >> >>> very productive to have a group of us in a room together for a few
>> >> >>> days to
>> >> >>> hash out new features, discuss where the code is going, hear about
>> >> >>> the
>> >> >>> science yt is enabling, and make some solid progress on improving
>> >> >>> the
>> >> >>> code.
>> >> >>>
>> >> >>> Cheers,
>> >> >>>
>> >> >>> Nathan
>> >> >>>
>> >> >>> On Sep 10, 2012, at 12:30 PM, Kacper Kowalik wrote:
>> >> >>>
>> >> >>> > Hi all,
>> >> >>> > I'd like to ask if there are any plans on organizing 2nd yt
>> >> >>> > workshop?
>> >> >>> > It's this time of the year when I need to apply for grants at my
>> >> >>> > university and I'd very much like to include such event in the
>> >> >>> > application :)
>> >> >>> > Cheers,
>> >> >>> > Kacper
>> >> >>> >
>> >> >>> > _______________________________________________
>> >> >>> > yt-dev mailing list
>> >> >>> > yt-dev@lists.spacepope.org
>> >> >>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >> >>>
>> >> >>> _______________________________________________
>> >> >>> yt-dev mailing list
>> >> >>> yt-dev@lists.spacepope.org
>> >> >>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> yt-dev mailing list
>> >> >> yt-dev@lists.spacepope.org
>> >> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >> >>
>> >> _______________________________________________
>> >> yt-dev mailing list
>> >> yt-dev@lists.spacepope.org
>> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> >
>> >
>> > _______________________________________________
>> > yt-dev mailing list
>> > yt-dev@lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev@lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org