[bsidesclt] Re: Meeting (sorry for sending this twice)

  • From: Tom Moore <c0ncealedx64@xxxxxxxxx>
  • To: bsidesclt@xxxxxxxxxxxxx
  • Date: Thu, 20 Sep 2012 19:31:43 -0400

I will be available in the evenings Mon-Tue of next week, but this week I
had prior obligations.
My apologies for not responding previously.
Bryan, K.C. and myself will be leaving for DerbyCon on Wed afternoon.

Tom

On Thu, Sep 20, 2012 at 7:17 PM, Chris Teodorski
<chris.teodorski@xxxxxxxxx>wrote:

> Unfortunately i am going to be out of town.  Monday night could work.
> On Sep 20, 2012 4:30 PM, "Jon Molesa" <rjmolesa@xxxxxxxxxxxxx> wrote:
>
>> I believe that is what the point of sending it to the list was. How
>> about tomorrow night at 6:00 PM?
>>
>> On 9/20/12 3:56 PM, Hpilking wrote:
>> > Try proposing a day/time/methodology?
>> >
>> >
>> >
>> > On Sep 20, 2012, at 2:43 PM, Jon Molesa <rjmolesa@xxxxxxxxxxxxx> wrote:
>> >
>> >> On 9/17/12 10:03 PM, Jon Molesa wrote:
>> >>> On 17.09.2012 16:38, Chris Teodorski wrote:
>> >>>> Resending as a few people have just joined the list.
>> >>>>
>> >>>> I'd like to suggest a meeting sometime either this week or early next
>> >>>> week.  I think we need to start nailing some things down.   I'm not
>> >>>> opposed to a google hangout, etc for people who can't physically
>> meet,
>> >>>> but I think in order to get this rolling we need to start making some
>> >>>> decisions -- most importantly a date.  Additionally BSides Raleigh is
>> >>>> planning to host a BSides event this spring as well -- so we will
>> need
>> >>>> to plan our event in a timeframe that doesn't conflict with theirs.
>> >>>>
>> >>>> How does this sound to everyone?     Jon -- might we be able to meet
>> >>>> at your office?
>> >>>
>> >>> Absolutely! Next week I leave for DerbyCon. So let's try to meet this
>> >>> week if possible.
>> >>>
>> >>>>
>> >>>> Chris
>> >>>
>> >>
>> >> I know folks are busy, but does no one want to meet and go over a few
>> >> key decisions as a group? If no then Chris and I will proceed.
>> >>
>> >> --
>> >> Jon Molesa
>> >> rjmolesa@xxxxxxxxxxxxx
>> >>
>> >
>>
>>
>> --
>> Jon Molesa
>> rjmolesa@xxxxxxxxxxxxx
>>
>>

Other related posts: