oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheryl John <shery...@gmail.com>
Subject Re: OODT SoCal Meetup/Hackathon
Date Fri, 25 May 2012 17:40:12 GMT
Out of town on the 9th weekend.

On Fri, May 25, 2012 at 8:28 AM, Paul Vee <paul.vee@gmail.com> wrote:

> Can't do 9th
>
> Sent from my iPhone
>
> On May 25, 2012, at 8:21 AM, "Ramirez, Paul M (388J)" <
> paul.m.ramirez@jpl.nasa.gov> wrote:
>
> > Hey Guys,
> >
> > So thoughts on June 16th or June 9th? Chris the prospect is your house so
> > either of those days work for you?
> >
> > --Paul
> >
> > On 5/21/12 10:03 AM, "Mattmann, Chris A (388J)"
> > <chris.a.mattmann@jpl.nasa.gov> wrote:
> >
> >> Hey Tom,
> >>
> >> Awesome, well we will plan on having an OODT meetup in Novemeber that's
> >> for sure
> >> and I again volunteer my house :)
> >>
> >> Cheers,
> >> Chris
> >>
> >> On May 21, 2012, at 6:27 AM, Thomas Bennett wrote:
> >>
> >>> Hey,
> >>>
> >>> Totally awesome idea. Wish I could be there to join in ;). If this
> >>> becomes
> >>> a more regular event - keep me posted. I'll be in the US in November -
> >>> it
> >>> would be great way to meet the team.
> >>>
> >>> Cheers,
> >>> Tom
> >>>
> >>> On 18 May 2012 07:16, Cameron Goodale <goodale@apache.org> wrote:
> >>>
> >>>> I think the pool/house idea sounds great.  If we start early enough,
> >>>> then
> >>>> we can hack for like 4 - 6 hours, then use the pool as a reward for
a
> >>>> job
> >>>> well done.
> >>>>
> >>>> My hope is that we can get some long stretches of time to work on
> OODT,
> >>>> without email, twitter, IM, or facebook distractions...well the
> >>>> exception
> >>>> being the Google Hangout (of course).
> >>>>
> >>>> -Cam
> >>>>
> >>>> On Thu, May 17, 2012 at 7:06 PM, Ramirez, Paul M (388J) <
> >>>> paul.m.ramirez@jpl.nasa.gov> wrote:
> >>>>
> >>>>> Your place sounds good to me. Now we just need to lock down a date.
> >>>>> 1st
> >>>> or
> >>>>>  2nd Saturday of June work?
> >>>>>
> >>>>> +1 to Google hangout.
> >>>>>
> >>>>> Probably best if people do a SVN checkout before we meetup.
> >>>>>
> >>>>> --Paul
> >>>>>
> >>>>> On May 17, 2012, at 10:45 AM, "Mattmann, Chris A (388J)" <
> >>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
> >>>>>
> >>>>>> Now *that* is a great idea bfost. We can set up a Google Hangout
for
> >>>>> this.
> >>>>>>
> >>>>>> OK, then I am going to throw out my pool/house for the meetup
> >>>>>> location,
> >>>>>> depending on what people think!
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Chris
> >>>>>>
> >>>>>> On May 16, 2012, at 11:32 PM, Brian Foster wrote:
> >>>>>>
> >>>>>>> google+ hangout 4 those out of state!
> >>>>>>>
> >>>>>>> On May 16, 2012, at 11:54 AM, "Mattmann, Chris A (388J)"
<
> >>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
> >>>>>>>
> >>>>>>>> Hey Paul,
> >>>>>>>>
> >>>>>>>> This sounds like a great idea and I'm in (of course!)
> >>>>>>>>
> >>>>>>>> One thing we'll need to do is make sure that we do a
really good
> >>>>>>>> job
> >>>>> of trying
> >>>>>>>> to include everyone, even folks that are not in the
SoCal area.
> >>>>>>>> That
> >>>>> means
> >>>>>>>> potentially using the Wiki, and other forms of communication
> (JIRA,
> >>>>> ReviewBoard, etc.)
> >>>>>>>> to make sure everyone (including those not able to attend)
feels
> >>>>> included.
> >>>>>>>>
> >>>>>>>> Great idea!
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Chris
> >>>>>>>>
> >>>>>>>> On May 15, 2012, at 2:21 PM, Ramirez, Paul M (388J)
wrote:
> >>>>>>>>
> >>>>>>>>> Hi All,
> >>>>>>>>>
> >>>>>>>>> Anyone interested in doing a meetup/hackathon at
the beginning of
> >>>>> June. The goal would be to get some updates to our code base but
> >>>>> really
> >>>>> focused on getting 0.4 out the door. If there is enough interest
we
> >>>>> would
> >>>>> need a place to host it. Anyone and everyone would be welcome as
it
> >>>>> would
> >>>>> be a good way to understand the ways to contribute which go well
> >>>>> beyond
> >>>>> just code. If enough people seem interested  I will work out the
> >>>>> details.
> >>>>> My initial thought is this would be on a weekend.
> >>>>>>>>>
> >>>>>>>>> --Paul
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>> Chris Mattmann, Ph.D.
> >>>>>>>> Senior Computer Scientist
> >>>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>>>>>>> Office: 171-266B, Mailstop: 171-246
> >>>>>>>> Email: chris.a.mattmann@nasa.gov
> >>>>>>>> WWW:   http://sunset.usc.edu/~mattmann/
> >>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>> Adjunct Assistant Professor, Computer Science Department
> >>>>>>>> University of Southern California, Los Angeles, CA 90089
USA
> >>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>> Chris Mattmann, Ph.D.
> >>>>>> Senior Computer Scientist
> >>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>>>>> Office: 171-266B, Mailstop: 171-246
> >>>>>> Email: chris.a.mattmann@nasa.gov
> >>>>>> WWW:   http://sunset.usc.edu/~mattmann/
> >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>> Adjunct Assistant Professor, Computer Science Department
> >>>>>> University of Southern California, Los Angeles, CA 90089 USA
> >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Chris Mattmann, Ph.D.
> >> Senior Computer Scientist
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 171-266B, Mailstop: 171-246
> >> Email: chris.a.mattmann@nasa.gov
> >> WWW:   http://sunset.usc.edu/~mattmann/
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Adjunct Assistant Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >
>



-- 
-Sheryl

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message