Undergraduate BE Board:Agendas - 1/22/08 Agenda: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
(New page: Meeting: Tuesday January 22nd, 7:30pm 3rd floor building 56 (Mike buy food) #Welcome back kickoff #*Date -- Tuesday Feb 12th? #*Location -- #**Dan couldn't find any place in SS #**Reserve...)
 
No edit summary
Line 1: Line 1:
{{Template:Undergrad BE Board}}
<div style="padding: 10px; width: 720px; border: 5px solid #2D9258;">
Meeting: Tuesday January 22nd, 7:30pm 3rd floor building 56 (Mike buy food)
Meeting: Tuesday January 22nd, 7:30pm 3rd floor building 56 (Mike buy food)


Line 14: Line 17:
#**Hand out T-shirts?
#**Hand out T-shirts?
#Senior Dinner
#Senior Dinner
#*-Who: students, faculty, event coordinators?, be elected officials?
#*Style: cocktail? formal sit-down? (cocktail sounds fun to me)
#*Extras: slideshow/pictures? -- during dinner or separate time before/after?
#*Awards:
#**Formal: from advisors? faculty?
#**Nonformal: "fun awards" -> How many: 5-10?
#**Method of selection of award choices: 1) preset, 2) seniors choose, 3) seniors vote from list, 4) people are nominated for specific awards
#***Voting system (if we have one?): 1) vote on choices (online?), 2) nominate
#*Attire: Formal? Semi-formal?
#*Are there themes/decoration for senior dinners? I'm not very familiar with them. Do we want one?
#*In the future we might have to do this differently
#*Do we want to start any traditions?
#BE Tshirts
#BE Tshirts
#Mission Statement
#Mission Statement
#UG on curriculum board (so not hosed, no units hiding, etc)
#UG on curriculum board (so not hosed, no units hiding, etc)
#BE UG Board ASA recognized? Do we want? Maybe beneficial for continuity reasons
#BE UG Board ASA recognized? Do we want? Maybe beneficial for continuity reasons

Revision as of 14:54, 20 January 2008

<html> <td><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,29,0" width="750" height="180">

       <param name="movie" value="http://mit.edu/be/images/mitbe.swf">
       <param name="quality" value="high">
       <embed src="http://mit.edu/be/images/mitbe.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="750" height="180"></embed></object></td>

</html>

Home              UG Program Info              Members              Meetings              Pictures       Curriculum       Links              Contact us      


Meeting: Tuesday January 22nd, 7:30pm 3rd floor building 56 (Mike buy food)

  1. Welcome back kickoff
    • Date -- Tuesday Feb 12th?
    • Location --
      • Dan couldn't find any place in SS
      • Reserved 56-614 Feb 12th 7-9pm (tentative, can be changed)
      • Currently requesting 56-114
    • Food -- Subway, Finale's cake (Dan is trying to get approved. Mike must cut)
    • What to do --
      • Hand out newsletter (Neha and Bernice will work on it and anyone else willing)
      • Speak about upcoming events
      • Talk about elections
      • Hand out T-shirts?
  2. Senior Dinner
    • -Who: students, faculty, event coordinators?, be elected officials?
    • Style: cocktail? formal sit-down? (cocktail sounds fun to me)
    • Extras: slideshow/pictures? -- during dinner or separate time before/after?
    • Awards:
      • Formal: from advisors? faculty?
      • Nonformal: "fun awards" -> How many: 5-10?
      • Method of selection of award choices: 1) preset, 2) seniors choose, 3) seniors vote from list, 4) people are nominated for specific awards
        • Voting system (if we have one?): 1) vote on choices (online?), 2) nominate
    • Attire: Formal? Semi-formal?
    • Are there themes/decoration for senior dinners? I'm not very familiar with them. Do we want one?
    • In the future we might have to do this differently
    • Do we want to start any traditions?
  3. BE Tshirts
  4. Mission Statement
  5. UG on curriculum board (so not hosed, no units hiding, etc)
  6. BE UG Board ASA recognized? Do we want? Maybe beneficial for continuity reasons