[17423] in APO News
Minutes for the Second Summer Meeting
daemon@ATHENA.MIT.EDU (Michael A Feffer)
Mon Jul 10 20:45:48 2017
From: Michael A Feffer <mfeffer@mit.edu>
To: apo-minutes <apo-minutes@mit.edu>
Date: Tue, 11 Jul 2017 00:45:36 +0000
--_000_2CE835C9E79A754CB701E0E3F0B2651C9AB8C538OC11EXPO25excha_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Meeting minutes 7/10
Attendance: Nina, Michael, Will, Lori, Kyra, Amanda, Ellen, Claire, Nathan
Advisor: Ellen
Treasury issues (sort of missed since I was late, sorry...)
Officer Role Definitions:
- Went over President role, no real disagreements here
- Pub Dir, also not much to change here (gendered language)
- AC: short discussion about wording over officer list maintaining; ended u=
p not changing anything
(aside: should talk about Officer Portal later in the semester)
- FVP: changing to keep track of fellowship hours; also thinking of changin=
g wording for "membership retention program"
- Treasurer: mainly just need to fix gendered language; also goal to file r=
eimbursements weekly; must have bylaws
to exist (as a club) and also must have Treasurer to exist as a club; will =
share standing policies later
- SVP: need to keep track of hours; coordinate with PCs;
what do we want SVP to do vs PC?
driving idea: SVP in charge; PC just needs to handle things day-of; PC can =
take on more responsibilities if they desire
(made minor revisions to the definition of SVP accordingly)
want to define somewhere that not only SVP plans and runs event
result: PC definition should be very clear; have standing policy for saying=
that any brother can run service events and help SVP
(move that SVP should be organizer but can delegate to standing policy rule=
)
Action plan for hosedness:
- Changing 2 weeks to 1 week of MIA before contacting them (just a low-key =
checkin)(help them get stuff out of the way for the week)
(help figure out if they're hosed or if just a 1-off sort of thing)
- Action plan can go into standing policies
(skipping bylaws for now)
Big Projects:
- BookEx: just changing day to accomodate sororities
- MBU: NOT HOSTING; maybe go to Harvard/WPI to help with their MBU (would b=
e much happier going to Harvard's)
idea: teach a number of badges; many are tech related; can help fill in kno=
wledge for boy scouts
alternatively brothers can just be runners on day-of/herd scouts (lots of s=
couts on campus that day)
dates: November 4th, December 2nd
would likely fall under SVP
- Talent Show Fate/Poetry Slam: went over ideas for Open Mic;
note that if this is our big event, not many people likely needed; may need=
to think about getting more involved
with setup being more low-key, we can determine theme and ambiance; doesn't=
require entire chapter to work on it
(need to figure out what we want from this event)(thinking about figuring t=
his out in September)
- LD Day: Nina will get things rolling; Michael will also need to start res=
erving some things; August 1st will have concrete info
Thoughts about structure of meetings:
- check-in will become very unwieldy if we get very large (even though it's=
nice to have...)
- review "HP House System"; may be able to do check-ins on house basis
- have funny slide themes (Will will find sample slide decks)
- APO Online should be maintained a bit better
Rush planning and Rush chair:
- Rush chair would be de facto PC for some Rush events; one of public faces=
for prospectives; someone else who has
- Rush at the front of their mind besides Will...
- (Will also need a new PVP; opportunity for Rush chair to learn what this =
position would entail)
- Timeline for Rush: Thurs before end of BookEx to end of the next week (TB=
D)(may be changed)
First year summer mailing list: materials due July 22nd (should be samples =
in Google Drive from past years)
Will is going to email out about Rush stuff after the weekend
action item for all members: Add bylaw and standing policy stuff
Nina will help Michael with Officer Portal stuff
--_000_2CE835C9E79A754CB701E0E3F0B2651C9AB8C538OC11EXPO25excha_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" id=3D"owaParaStyle"></style>
</head>
<body fpstyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<div>Meeting minutes 7/10</div>
<div><br>
</div>
<div>Attendance: Nina, Michael, Will, Lori, Kyra, Amanda, Ellen, Claire, Na=
than</div>
<div>Advisor: Ellen</div>
<div><br>
</div>
<div>Treasury issues (sort of missed since I was late, sorry...)</div>
<div><br>
</div>
<div>Officer Role Definitions:</div>
<div>- Went over President role, no real disagreements here</div>
<div>- Pub Dir, also not much to change here (gendered language)</div>
<div>- AC: short discussion about wording over officer list maintaining; en=
ded up not changing anything</div>
<div>(aside: should talk about Officer Portal later in the semester)</div>
<div>- FVP: changing to keep track of fellowship hours; also thinking of ch=
anging wording for "membership retention program"</div>
<div>- Treasurer: mainly just need to fix gendered language; also goal to f=
ile reimbursements weekly; must have bylaws</div>
<div>to exist (as a club) and also must have Treasurer to exist as a club; =
will share standing policies later</div>
<div>- SVP: need to keep track of hours; coordinate with PCs; </div>
<div><span style=3D"white-space:pre"></span>what do we want SVP to do vs PC=
?</div>
<div><span style=3D"white-space:pre"></span>driving idea: SVP in charge; PC=
just needs to handle things day-of; PC can take on more responsibilities i=
f they desire</div>
<div><span style=3D"white-space:pre"></span>(made minor revisions to the de=
finition of SVP accordingly)</div>
<div><span style=3D"white-space:pre"></span>want to define somewhere that n=
ot only SVP plans and runs event</div>
<div><span style=3D"white-space:pre"></span>result: PC definition should be=
very clear; have standing policy for saying that any brother can run servi=
ce events and help SVP</div>
<div><span style=3D"white-space:pre"></span>(move that SVP should be organi=
zer but can delegate to standing policy rule)</div>
<div><br>
</div>
<div>Action plan for hosedness:</div>
<div>- Changing 2 weeks to 1 week of MIA before contacting them (just a low=
-key checkin)(help them get stuff out of the way for the week)</div>
<div>(help figure out if they're hosed or if just a 1-off sort of thing)</d=
iv>
<div>- Action plan can go into standing policies</div>
<div><br>
</div>
<div>(skipping bylaws for now)</div>
<div><br>
</div>
<div>Big Projects:</div>
<div>- BookEx: just changing day to accomodate sororities</div>
<div>- MBU: NOT HOSTING; maybe go to Harvard/WPI to help with their MBU (wo=
uld be much happier going to Harvard's)</div>
<div><span style=3D"white-space:pre"></span>idea: teach a number of badges;=
many are tech related; can help fill in knowledge for boy scouts</div>
<div><span style=3D"white-space:pre"></span>alternatively brothers can just=
be runners on day-of/herd scouts (lots of scouts on campus that day)</div>
<div><span style=3D"white-space:pre"></span>dates: November 4th, December 2=
nd</div>
<div><span style=3D"white-space:pre"></span>would likely fall under SVP</di=
v>
<div>- Talent Show Fate/Poetry Slam: went over ideas for Open Mic;</div>
<div><span style=3D"white-space:pre"></span>note that if this is our big ev=
ent, not many people likely needed; may need to think about getting more in=
volved</div>
<div><span style=3D"white-space:pre"></span>with setup being more low-key, =
we can determine theme and ambiance; doesn't require entire chapter to work=
on it</div>
<div><span style=3D"white-space:pre"></span>(need to figure out what we wan=
t from this event)(thinking about figuring this out in September)</div>
<div>- LD Day: Nina will get things rolling; Michael will also need to star=
t reserving some things; August 1st will have concrete info</div>
<div><br>
</div>
<div>Thoughts about structure of meetings:</div>
<div>- check-in will become very unwieldy if we get very large (even though=
it's nice to have...)</div>
<div>- review "HP House System"; may be able to do check-ins on h=
ouse basis</div>
<div>- have funny slide themes (Will will find sample slide decks)</div>
<div>- APO Online should be maintained a bit better</div>
<div><br>
</div>
<div>Rush planning and Rush chair:</div>
<div>- Rush chair would be de facto PC for some Rush events; one of public =
faces for prospectives; someone else who has</div>
<div>- Rush at the front of their mind besides Will...</div>
<div>- (Will also need a new PVP; opportunity for Rush chair to learn what =
this position would entail)</div>
<div>- Timeline for Rush: Thurs before end of BookEx to end of the next wee=
k (TBD)(may be changed)</div>
<div><br>
</div>
<div>First year summer mailing list: materials due July 22nd (should be sam=
ples in Google Drive from past years)</div>
<div><br>
</div>
<div>Will is going to email out about Rush stuff after the weekend</div>
<div><br>
</div>
<div>action item for all members: Add bylaw and standing policy stuff =
</div>
<div>Nina will help Michael with Officer Portal stuff</div>
</div>
</body>
</html>
--_000_2CE835C9E79A754CB701E0E3F0B2651C9AB8C538OC11EXPO25excha_--
