Skip to content

Instantly share code, notes, and snippets.

@jdangerx
Last active August 29, 2015 14:21
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jdangerx/a538aca072852edbc707 to your computer and use it in GitHub Desktop.
Save jdangerx/a538aca072852edbc707 to your computer and use it in GitHub Desktop.
some thoughts about scav townhall

Overarching points

  • we need captains by the end of this year, and house reps would be great also. I think we're all agreed on this.
  • continuing workshops / build nights next year is very important to me personally and I think would do wonders for recruitment, sense of community, and skill training. To make sure this happens, we need a point person, since I won't be around physically. Whoever does this will have my full remote support.
  • in my opinion, team organization doesn't make a huge difference in performance - as long as we are organized enough to present most of our items at Judgment, I think the number of people scavving is a bigger factor
    • in light of that, consider optimizing our organization for ease of judgment and lower average stress.
    • additionally, coercing people into administrative roles doesn't work great - high dropout rates and bad vibes - so consider seeing who wants to do leadership stuff, and then building organization around the talent we have.

##Play-by-play

3:11 - Safety discussion re: Cartier’s thumb, we need better clamps and gloves apparently. 3:13 - Safety rules on the wall got broken, weather was a problem

We have gloves and safety glasses, in the safety box. Not well-distributed/available though, as we can see from nobody using them. We should encourage people to wear gloves, maybe by example during Scav, maybe by training pre-Scav.

3:14 - Clark moves to the organization. Wants 6 Secretaries in charge of sections of the list. Also wants a mentor under them. Nicholas says that the last time it happened was a disaster, corrected by Clark.

It was an organizational disaster in that one person dropped out, and nobody really knew where the items were.

Would be better if we:

  1. made sure nobody was gonna drop out, or everyone doing it really wants to
  2. had page boxes/bags (I'm really big on the idea of using those big ikea bags for pages but that's a real minor detail)

Cartier response that it would dilute the pool of competent people too much. Dido supports the co-captaining of pages. Ben speaks up against this idea. Wants to educate the page captains better so they know what they’re getting into. Clark wants more meetings in advance to train people. Clark wants more one on one page captain connections. Dido saw people being untrained and confused after list release.

Having a team of people work on a page is really great for stress levels, imo, and also increases participation. Educating the page captains, about both how Scav/our team works and about skills, is a great idea. We just have to have our shit together to do it.

Discussion of parsing the LateK.

Improvements/suggestions welcome. The LaTeX comes out at like 3 or 4 so the delay isn't huge.

Page captains typing their pages? Roger is okay with having it on the walls is fine. Cartier wants more contact with the page captains themselves. Ben wants phone numbers from the page captains on the wall. Basically need to put them in closer touch with scavvies.

Yes. Make it easier for scavvies to talk to whoever is keeping track of their work.

Matthew and Matthew talk about page captaining. Matthew G wants categorization of the items less than 10 points to be split by category not page. Matthew C thinks it’s too complex. Dido wants page captains to categorize the items themselves. Could use lists to generate interest. Clark wants to add complexity to the spreadsheet. Will Shore speaks in support of categorization. Further discussion of page captains tagging the list. Keeps the system of page captains but adds a category classification to the items.

If we go with the website that I'm working on we'll have a tag system, so we can organize the items in flexible ways.

Ben makes the argument that we should collect information on people’s skill and interests. Matthew G advocates a google form sort of approach where you would sign up to be contacted based on categories. Will advocates for using the miscellaneous list to interest people.

Matthew G wants an unclaimed item captain for Saturday.

Interesting. In the past we've had people go hard on "The Shit List" on Saturday, which is just items that people have dropped. This also already kind of happens early Sunday morning, when we are just like "hmm what items do we have left to do."

Roger thinks at some point that we need the manpower over administration. Matthew tries to summarize the positions. Ben corrects and says we should categorize regardless. Question boiled down to page captains versus lieutenants for organization. Categorization is like a tag on tumblr.

May not be a bad idea to have many secretaries/lieutenants but also allow groups to take a whole page. Kind of what we did with Phoenix Shack.

3:42 That paragraph was getting long. Further discussion of how the category system would work. Roger wants stuff other than the lieutenants vs. page captains before we go into the main debate about lieutenants. Will Shore says the decision might have to happen closer to scav. Ben talks about the possibility of a website that’s not a google doc. Problems of claiming and contributing and the difference between the two. Forum with every item as a thread? Rouse talks about a historical example. Dido says worst case scenario is a facebook page. Matthew G - Done, unclaimed, claimed, and assistance requested. Ben thinks we should reach out to other scav teams. Ben tentatively signals he might be able to do it.

Hacked out a bit of a website yesterday. Happy to talk to people about it.

3:51 Moving into the primary question of page captains versus lieutenants. Ben wants to possibly put good page captains over two pages. Rouse says lieutenants could probably be named today and that can determine whether we should do lieutenants this year or not.

In that lieutenants are unlikely to be first years, yes, we can gauge the feasibility of lieutenants before school's out.

Potential names? Not right now. Dido wants to send that email about interest. Presentation at judgment is a possibility of failure in the lieutenant system. Scott makes the point that it may cost us points. Brief digression on the organization of the items when they’re done. The presentation makes it special. It’s harder to get that if you’re in charge of more items. Okay this was a huge mistake we’re digressing sooooo hard right now Jesus take the wheel. They are coming, we cannot get out. BACK TO REALITY Drop out rate among page captains is really high/bad.

High dropout rate is probably due to coercing people into being page captains, without telling them what it entails. Honestly having lieutenants might have lower dropout rate since we don't have to have as many people. Or maybe even lieutenant teams to reduce stress? 1 group per 3-5 pages, depending on group size? Just spitballing here. Seems tough to organize and there is certainly an organizational benefit to having a few people have an idea of how the whole list is going. OTOH a lot of that "keep track of the whole list" burden can be shouldered by the website.

Question is that can we raise judgment participation by using the lieutenant system.

Digression: Lunch at Judgment?

Would be DOPE but also most people are so busy at Judgment. After the showcase we might have someone go grab a ton of food from Noodles or something? I'd be happy to.

Okay, that seems to have been tabled. Moving towards how we recruit and stuff.

Stuff during O-Week to sell scav. Do we have a mini scav? Discussion of programming for the O-Week scavving. Show the Scavengers movie?

All good ideas. Also, build nights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment