Officers

Minutes for 2012-06-01

  1. Call to Order 06-01-2012 13:11

    1. Roll Call
      1. Administrative Cabinet
        1. President - David Nuon: Present
        2. Vice-President - Ian Goegobuer: Present
        3. Treasurer - Christopher Gomez: Present, came in 06-01-2012 13:13
        4. Secretary - Shane Satterfield: Present
      2. Appointed Positions
        1. AESB Representative - Victoria Hatfield:Not Present
        2. Publicity and Recruitment Chair - Leo Tronolone:Present
        3. Market Manager - James Coolidge: Not Present
        4. Event Coordinator - Diana Ignacio Present
        5. Webmaster - John-Jimi Kathleen Som: Present
        6. Office Technician - Johnny Patterson: Present, came in 06-01-2012 13:37
        7. Historian - Orion Sakorn: Present
        8. Librarian - Anthony Gialcalone: Not Present
      3. Project Managers:
        1. Socie-D: Ben Chang Not Present
      4. Approval of Agenda: [PASS]
        1. First: Ian [PASS]
        2. Second: Diana [PASS]
        3. Discussion: None
      5. Approval of Minutes: [PASS]
        1. First: Diana [PASS]
        2. Second: Ian [PASS]
        3. Discussion: None
    2. Announcements
      1. Guest Introductions
    3. Business
      1. Officer Reports
        1. Faculty Advisor: Not Present
          1. Have to talk to Murgolo because he is not an ACM National member.
        2. President:
          1. Availability over summer:
            1. David is available over the summer nearly everyday.
        3. Vice-President:
          1. Ian: Ian is here over the summer as well.
          2. Ian: If you want access to the twitter, contact Ian.
          3. Ian: If you are interested in getting started on a project over the summer, contact Ian, or post something on the ACM facebook page.
        4. Treasurer:
          1. Chris: We need to do some fundraisers, especially if we are going to have to pay for the faculty advisor. We should also restock. We need the funds for a costco run.
          2. Sal: when is the costco run scheduled?
            1. Nathan: Whenever I can get James to do so.
          3. Sal & Orion: Water, Water, Water!
        5. Secretary:
          1. Working on a new system for the minutes.
        6. AESB Representative:
          1. Year-in review
            1. Sal: I talked with the incoming AESB president. There is a good chance that rooms will be lost. Every year there is a year in review to show that orgs deserve their rooms. Historian, take pictures. Make things that you can show off on your resume.
            2. Orion: How are we going to take pictures of programming projects?
              1. Sal: You can take pictures of the Programming team, and events like the robot battles. You want to make things that will make the college look good. You can just take some screen shots for the programming projects.
        7. Publicity and Recruitment Chair:
          1. Sal: I will be coaching Leo from now on.
          2. Design assets and documents.
            1. Sal: Talked with Nathan about this. Has a lot of these. I just have random files, and we need to organize them. The best publicity is just talking to people. I can meet with Leo next Friday.
          3. Event Fliers/Board
            1. Sal: I just want to print out some 4x6 and get them all over the place because they're cheap.
              1. Orion: Where would we post them?
                1. Sal: In the office, and maybe in the labs.
            2. Sal: We have a big board. I just want to create a generic board that we can just post on new 4x6's and update them frequently.
          4. Beginning of the year recruitment.
            1. A lot of students are coming in and we want to scout them. We want people that already know how to program and are bored out of their mind. The best publicity is going into classes and talking to people. The publicity chair should arrange and schedule it so that you can go into classes and talk to people. The main classes to hit are CECS 100 and 174. In the 200 lvl get the students that now know how to code and get them to start projects. That is our strategy on sophomores. For Juniors and Seniors, scare them.
            2. David: Everyone, try to get people involved. People that aren't involved tend not to do so well. Emphasize that connections are important.
            3. Sal: Don't email people. Email doesn't work. Talk to people. Start coordinating people and see who can talk to people.
        8. Market Manager:
          1. We need to restock soon.
            1. David: We need water.
        9. Webmaster:
          1. Accounts
            1. David: I am training the webmaster and helping him get familiar with the website. Mainly, he must help the secretary proofread the minutes.
            2. Sal: Don't treat your accounts like your facebook; keep them generic.
            3. David: Make sure you check the forwarding when you get your accounts. Also, the double login.
            4. Sal: Do you know what AESB is Jimmi? We have a page on there and you should make sure it's up to date. And wiki wiki wiki.
        10. Office Technician:
          1. Surveillance Boost
            1. Sal: We need to make sure the surveillance system is safe. We need to mount one more camera. If you can't secure it, obscure it.
        11. Historian:
          1. Franks videos of robot competition.
            1. David: Frank still needs to get us these videos. He should be back soon and living locally. Once he's finished moving, ask him for the videos.
        12. Librarian:
          1. David: I haven't heard from him in a while. From what we last talked about, he wants to have a library check-out system.
            1. Sal: If we are going to have a check-out system, it should be only for members.
          2. Tony still needs to see Steve Gold about his book collection.
        13. Event Coordinator
          1. Diana: I still need access to the email. I am planning lots of social events. Also, I am working on recruiting.
          2. Sal: How much did the ACM BBQ make?
            1. Diana: I am not sure.
            2. David: I don't think that there was enough money made.
          3. Motion to give all of the money made by ACM from the ACM-W BBQ to ACM-W: [PASS]
            1. First: Ian: Oky doky, more money for them.
            2. Second: Orion [PASS]
            3. Discussion: None
          4. ACM meetings are Tuesdays at 1pm, ACM-W meetings are Thursdays at 1pm
      2. Project Committee Reports
        1. By-laws Comittee: July 11th 2012
          1. Sal: Our next meeting is going to be the bylaws meeting. It is going to be a very long meeting. Pay close attention. Let there be praise for the bylaws. Money is a very sensitive issue. Not only will you learn a lot about the bylaws, but you will learn a lot about ACM history. We are going to do the same thing as SOAR. We are going to go out to lunch, them talk about the bylaws, and then go do something afterwards.
          2. Proposed Ammendments:
            1. Sal: I want AESB Representative and Event coordinator to become executive board members. Weird connections are important.
            2. Sal: Secretary should look into the USU mailbox.
              1. Sal: If anything would be mailed to us, it would be put into this mailbox.
            3. Librarian will be in charge of keeping the office open as much as possible.
            4. Bump up transitions. Start them earlier.
            5. There are two days out of the year that we have no board members. We are going to close that loophole.
            6. For ACM-W we will open up presidency to EE, Math, and applied math.
    4. Old Business
      1. Sal: We have a tendency to put off things we need to do. When we say that we need to do something, the secretary should put it in old business. This will make it a system of accountability. It will be an action list. Also, proofread the notes.
    5. New Business

      1. ACM
        1. National Student Accounts
          1. David: Who has a national student account?
            1. Sal: Every officer needs to have a national student account.
          2. David: I need to get the credentials for the ACM national chapter on the website.
        2. Report to ACM
          1. Due by the end Q3, July 30.
          2. David: I want to get this done as soon as possible. We need an ID number from our faculty advisor. We need to figure out how we are going to do this. Shane, can you meet with me on Sunday about this?
            1. Shane: Yes.
      2. T3

        1. When?
          1. Sal: We don't know when. In early to mid August, registration opens. Who do we have to monitor that?
            1. David: I will.
        2. Sal: Event, fiscal, and campus policy certifications are the three that we need. We should have multiples of these. Sign up for redundancy, everyone. If something goes wrong, make sure someone else can do it. Have back ups. Management strategy should be placed on the wiki.
        3. Sal: You have to pay in person. You show up, it's on a Saturday, early in the morning. You go through a guest speaker, then go to some lessons. Then lunch, and repeat. Treasurer should do fundraising, and just look into things that are interesting.
      3. SOAR

        1. When? July 11th 2012
        2. When to register?
          1. Sal: You don't register, you just show up. First come first serve.
        3. Who is going?
          1. We will be meeting at 11 ish. We will have a bylaws meeting that day. People who show up for that can show up for SOAR.
        4. Recruitment strategy
          1. Sal: ACM and ACM-W booths will be right next to each other. Snag the people walking by. Make it so that they have to walk through us to get by. Ask them what their major is. Try and get CECS majors, and for other majors, persuade them into a CS minor.
            1. David: Express how computation heavy the other engineering majors are.
            2. Ian: I don't remember the ACM table at SOAR when I entered.
          2. Sal: Instead of talking about ourselves, we should interogate the students and make it all about them. The biggest mistake ACM made when I entered was that we measured our success on how many people showed up to our meetings. But they didn't do anything. We want active and valuable members.
      4. Summer Shenanigans
        1. Code Jams
          1. David: Code jams are hilarious. I want this to be a bunch of people in the lab coding. I don't want people playing video games in there. I don't want the freshman who don't know anything to be intimidated.
          2. Sal: We have an issue with recruitment. People that enter, don't often stay. Our goal with this is to make the freshman not suck. Anyone who goes into the code jam has to be working on something; no messing around. If they don't know what to do, give them something to do.
            1. Nathan: If all else fails, advise them.
        2. Archiving
          1. David: We have lots of documents that I don't want to lose. I want many things to be documented on the wiki for transitions of future boards.
      5. Keys
        1. David: Thank you all for sending your signatures for the form. We're pretty much done. We just need the advisor's signture.
      6. ACM Git Hub
        1. Sal: Apparently, non-profit organizations get free git hub.
        2. David: Git hub has made very awesome clients for Mac and Windows.
      7. Programming team
        1. Sal: I should run the programming team. I will see if I can get the charter ready by August. If you want to get started, work on the warm-up problems. I will get the junior varsity teams to do this. People should get started as early as their freshman year.
          1. Nathan: There is an IBM representative at the programming team competition every time and he recruits.
        2. Sal: Alumni are very important for networking. Keep in contact with your alumni.
      8. Hack-a-thons
        1. Sal: You just plot people in a room and they just start coding. We need to talk to an industry to cook up one, maybe some prizes. Maybe we could have the EA contact sponser the hack-a-thon over spring break.
      9. Meeting with Dr. James
        1. Sal: We are going down to ECS 316. We want to talk about code jams. This will be our big thing next year.
          1. Code Jams
          2. Programming team and junior varsity.
          3. Dr. James said he wanted a local competition. He wants more of that.
          4. ACM-W outreach.
          5. Helping motivate faculty and showing student projects
          6. Getting funding from the industry.
          7. More industry contacts.
          8. The techs would like some feedback on problems with the lab computers.
          9. Manage MSDNAA for the department.
  2. Adjournment 06-01-2012 14:59