I can do thursdat at 6. Where are we going to meet? --Evan ----- Original Message ----- From: "Sean T. Brady" <sean@xxxxxxxxxxxxxx> Date: Monday, July 28, 2003 5:08 pm Subject: IEEE Exec: Re: Date for Mid-Summer Meeting! > All, > > Looks like Deep is the only one coming to this meeting. I'd like to > reschedule for next week. Please email me by noon on Wednesday > with any > evenings that you are available. Sorry people! > > Sean > > On 07/28/2003 1:01 PM, "Deepanjan De" <deepanjan.de@xxxxxxxxxxxxx> > wrote: > > Hey guys, > > Sorry I'm an hour off, but I can attend the meeting on > Thursday at > > 6. See ya. > > > > Deep > > > > ----- Original Message ----- > > From: "Sean T. Brady" <sean@xxxxxxxxxxxxxx> > > Date: Monday, July 21, 2003 6:56 pm > > Subject: IEEE Exec: Re: Date for Mid-Summer Meeting! > > > >> Hi All, > >> > >> I'd like to postpone this Thursday's meeting by one week since > >> Evan is the > >> only one that can make it this week. Please let me know by noon > >> on Monday, > >> July 28 if you can be there. > >> > >> Sean > >> > >> On 07/20/2003 2:19 PM, "Deepanjan De" <deepanjan.de@xxxxxxxxxxxxx> > >> wrote: > >>> Hey guys, > >>> Unfortunately Thursday, July 24 at 6pm is not good for me. If > >>> my plans change I'll let everyone know. Since our College of > >>> Engineering budget is at $0 and our University account does not > >> allow> us to use the money for group dinners, we cannot have > anything>>> reimbursed until our new account comes in during the > fall semester. > >>> In terms of items for discussion, I have expressed a lot of > >>> interest in the Philanthropic Committee @ VU and I'd like to see > >> that> get underway during the Fall Semester. I volunteered awhile > >> back to > >>> initiate this committee and I think it's a great idea, so that is > >>> something that I feel should be established. > >>> I also was trying to think of ways to get general body > >>> involved. I think one way to get people involved is if they > >> feel like > >>> they are apart of some kind of decision making process. That way > >>> people begin to get the feeling that their input matters and it > >> is not > >>> the executive board serving the IEEE, but it?s the IEEE serving > > each > >>> other and reaching out to the entire ECE department. I realize > > that > >>> our executive board meetings are an open forum for any members to > >>> attend, but maybe we should approach it differently. Maybe we > >> should> have a general body meeting that is held only to hear what > >> people want > >>> to see from the IEEE. I think too many people get turned off when > >>> they see "Exec board meeting, other members welcome". (Not that > >>> people don't get turned off from general body meetings either). > >> This> kind of meeting would need some creative advertising > >> techniques but I > >>> think it's worth a shot. Anyway, if I come up with anything > >> else, and > >>> if Thursday afternoon clears up for me I'll let you all know. > >> See ya. > >>> > >>> Deep > >>> > >>> > >>> ----- Original Message ----- > >>> From: "Sean T. Brady" <sean@xxxxxxxxxxxxxx> > >>> Date: Monday, July 14, 2003 7:42 pm > >>> Subject: IEEE Exec: Date for Mid-Summer Meeting! > >>> > >>>> Hi All, > >>>> > >>>> Let's meet at Villanova (room TBD) on Thursday, July 24 at 6pm. > >>>> Deep, since > >>>> you're working at 'Nova, can you see what we can do about > >>>> reimbursement for > >>>> dinner given that our budget isn't yet effective? > >>>> > >>>> Everyone should expect a tentative agenda by next Tuesday. By > >>>> close of > >>>> business on Monday, July 21, please advise per your availability > >>>> and let me > >>>> know if you have any topics/ideas you'd like to have discussed > >>>> (even if you > >>>> cannot attend). > >>>> > >>>> FYI, these agendas aren't meant to be stuffy or constricting > >> like our > >>>> meetings last Fall... I just think that they will help to guide > > our > >>>> conversations and allow for more people than just me to prepare > >> their>> thoughts! :-) > >>>> > >>>> Sean > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > > > > > > >