Student Committee Representatives

Members present: Joanne, Manny, Mary, Nik, Leslie, Eli, Zach K, Matt, Lindsay, Brad, Zack C, Jeff

• Matt: DNS sometimes gets messed up. Manny: I think we've resolved the issue, but if the issue still comes up, we'll look into it. Matt: Packets get out once a connection has been established (to SSH), but DNS doesn't work.
• Pizza arrives.
• Manny: Next year, we want to have the group even more involved with the community.
• Mary: IT NINJAs next year.
• Jeff: Nick Tatar said he would keep days open for NINJA sessions for freshmen.
• Mary: How many recurring members should we have? How big should the group be?
• Leslie: I think we need more visibility.
• Mary: IT headbands? Arm bands?
• Manny: ByteHoard is almost ready.
• Manny: We'll do an Outlook 2007 upgrade this summer. Brad: Will we have more mailbox space? Manny: No, but we can forward to your Gmail.
• Joanne: At the IT meetings, we were thinking about giving you more things to do. For example, we thought about encouraging a student group to work on the archiving issue.
• Leslie: The committee would be willing, as long as we have the option to say no.
• Jeff: Over the summer, a group of students should write some documentation for the IT Web site.
• Mary: There will be new printers in the fall. Interesting fact: the most printing happens in West Hall. We have decided to replace the two printers in each dorm with single multicopy units.
• Lindsay: Is there documentation for installing printers on Fedora? Manny: There should be, but we'll check.
• Zach: With the most printing happening in the dorms, won't they fail more often? Mary: When we do request a quote from the vendor, we specify volume of printing, so they should be reliable.
• Mary: We are also going to add another color printer to the Academic Center.
• Leslie: I am bothered by the number of documents that are printed and never retrieved.
• Mary: With leased printers, we pay for every printed side of every document.
• Eli: That may have to do with printers failing.
• Nik: We could look at printer queues and send angry emails.
• Brad: In my Tech New Ventures class, we talked about having every printer prepared to print every job, and a card swipe would initiate the printing. It solves the printer jam issue and it could be more convenient.
• Manny: Faculty printing may also be a problem. Brad: I had to print 1000 pages for one class. Manny: We should encourage faculty to be more green. Leslie: We do have some professors that are more traditional.
• Manny: There should be a study next semester about printing habits and costs. The fundamental issue is awareness. Mary: I think it would be nice to have students give their peers perspective on the issue.
• With the printing accounting software, we can tell people what print jobs cost. There are lots of units we could use: trees killed, students who couldn't come to Olin, etc.
• Leslie: It's important to tell people that Gmail isn't as secure as Outlook because it has a Web-based login.
• Brad: I used to fire up my Dell to delete email and change my password every six months.
• Brad: What is going on with the VMWare? Manny: It's on the backburner. We didn't get a lot of feedback. At the moment, we're still looking at Fedora 9 for the fall. Talk to Dave Carver if you want to try it.
• Registration went fairly well.
• Mike and Javier have been working on the portal. We're on the right track. Hopefully the portal will be the only option in the fall, so people aren't running scripts on SIS.
• Meeting adjourned.

• Members present: Brad Powers, Manny, Zach Kratzer, Matt Crawford, Nik Wittenstein, Leslie Gerhat, Eli Sheldon, Javier Zapanta, Zack Coburn.
• Manny: We're working on the registration system. It will hopefully be ready by April, but it's delayed by the vendor (Jenzabar).
• Manny: Printing in the residence halls is currently stable. We are looking at the possibility of replacing the printers with one multi-function copy unit per residence hall.
• Matt: What is wrong with the AC third floor printer?
• Manny: The AC third floor printer has a part on order.
• Nik: A technician came and cleaned the AC third floor printer and now it works better.
• Manny: If people are having trouble updating Olinux, they should check the IT Web site. Dave will be sending an email to students about the pilot VMWare Windows/Linux system.
• Leslie: I had a conversation about My.olin.edu and Launchpad. The students would like a portal, but they want it to be more like Launchpad.
• Javier: I talked to Greg Marra, and we agreed that we're going to combine our efforts. We are planning to convert the main page of My.olin.edu into Launchpad.
• Manny: We want the portal to be the one stop shop.
• Manny: We're trying to figure out our spam problem. We are looking for feedback about how students are dealing with spam. Yesterday, our gateway processed 130,000 messages. 93% of them were spam.
• Meeting adjourned.

HB COUP – February 5, 2008 Present: Jeff Moore, Jeff DeCew, Evan Morikawa, Alyssa Levitz Details Day! 0. Someone screws up 1. Aggrieved submits “report” – will need to make this – make sure that the form is clear on lack of anonymity, lack of individual sanctions, etc. – “if unsure, please submit regular report” 2. HB Chair forms an IT – perhaps instead of OSL and two students, have Chair and two students *Don’t want this to be a part of it – Chair, Vice Chair and OSL representative decide if the HB is the right group of people to be dealing with that situation – in the future, hope to remove this from the single student process, as well Notes on flow chart Normal report • Chair/Vice Chair/Nick – decide if HB is right place for the grievance – in future, want to skip this and go straight to an IT o If the regular report was filed, but it ought to have been organizational – Still make IT complete work before moving it over to COUP side of things to err on the side of protecting students’ anonymity • The way normal IT currently works: as long as the IT can get everyone to agree, they can do anything. Hearing panel is for when people don’t accept responsibility or can’t get everyone to agree on a solution. Also, finding out who is actually involved. COUP report • Chair/Vice Chair/Nick decide if it is actually a COUP report – talk to aggrieved, make sure aggrieved knows what’s involved – this stage wouldn’t go in the rules, but it would occur • Need to define what COUP IT is (also, we need a new name. Really, Jeff? Really?? Never would’ve guessed) o Comprised of Chair or Vice Chair and two other HB members o Powers of investigation – figuring out what happened, making sure the HB knows the entire story/there are no surprises o Power to dismiss (case/organizations) o No power to resolve (fully) • Black Box –work through using a test case o Is the honor code a valid metric to judge organizations? In some cases, yes – in other cases, the HB would be reviewing organizations against their charters or constitutions General Notes • Fair for either IT to send something to the other side – a case could also potentially go to both at once, if there’s a personal issue at hand as well as an organizational factor o What is your desired outcome? Things to do for future • Make COUP Report form o Could have extra field for charter/constitutional violations in addition to clause of HC violated – or just say “what are your concerns” so as not to pigeon hole people into a certain thing o “Please list concerns, and site specific clauses when necessary” perhaps instead of “What violations of the honor code or the governing document are you citing?” o Don’t want it to be difficult for the aggrieved – put the burden on the people who know it (Chair/Vice Chair) and think about it • Continue working through black box

HB COUP Meeting – January 29, 2008

Present: Jeff Moore, Jeff DeCew, Alyssa Levitz, Nancy Doremus, Evan Morikawa, Jessie Sullivan

Looking to the Future
For next week: Start thinking about details – thinking about how you want this to look
The two weeks after that: how to implement details, and executing them

Important Aspects of Solutions

• General enough to use for more than just CORe (including actions of other organizations)
  • Don’t want to put an amendment in the HC that is that specific
    
• Simple (Removed)
  
  • Don’t want to give up important aspects just to be simple
    
• Efficient (Removed)
  
  • Not an issue as long as there is transparency
    
• No faculty/staff involvement (unless relevant to particular case)
  
• Transparency
  
  • Honor board can have discussions about anything without having a case
    Status updates, invitations?
    
• No spectators (aim for a private, non-confidential meeting)
  
  • Do we still want student input?
    
  • Discussion ~= spectators
    
  • Amicus briefs (perhaps as a result of a discussion)
    
• Threshold
   Difference between a regular Honor Board case and this new situation
   “Because you can’t hide something once it’s transparent.” – Jeff DeCew
   After the IT: the IT can diverge things – may need to reverse a club action while HB deals with the individual who caused that
  • Not a small group that decides (not a subsection of the honor board). Note: HC says that all Honor Board decisions (cases, approving abstracts, etc.) must be dealt with by consensus
  • Non-individualized sanctions (or, at least, not directed at the individual)
  • Result: formal announcement to the student body
  Priorities
  1. Transparency (with discretion)
  2. 0% faculty/staff involvement
  3. Generalized enough to use for more than CORe
  4. That’s π. But seriously, non-individualized sanctions
  10. No spectators (still allowing for discussion)
  11. Threshold: after the IT
  12. Formal written statement: closure for the student body (part of transparency)
  
  Other comments
  Which cases go to what process?
  o Intent of reporting violation – one is about “hammer of justice,” the other about fixing the problem
  o Using CORe funds to do something (while an individual purchases it, the club had to endorse it)
  What if someone submits a case as a vote of no-confidence sort of thing?
  Jeff Moore and Jessie like Halle Berry
  Jeff Moore kept us late!

Intercollegiate Relations Committee (IRC)

Responsibilities of the IRC
To advise the faculty and administration on matters related to establishing, maintaining and improving relationships with local partner institutions, with special attention given to the free exchange of students between partner campuses. To accomplish this function, the committee will regularly:
! consult with students, faculty, staff at Olin and at area institutions;
! evaluate the effectiveness of intercollegiate partnerships, programs and procedures;
! identify curricular and operational needs and opportunities with respect to partner institutions;
! make recommendations regarding partnerships, programs and procedures to improve intercollegiate relations;
! work with the ARB and corresponding committees at partner schools to facilitate course scheduling and improve other opportunities; and
! promote experiences developed or delivered by Olin community members to local partner institutions.

Membership of the IRC
The voting membership shall consist of 3 faculty members, 1 staff member and 2 students. Ex officio members include the Dean of Faculty and the Registrar.

IRC Chair
The chair of the ICRC Committee is selected by the current members with DoF approval from those faculty members that have already served one year.

Policy for appointments and rotation to the IRC
Faculty members are selected by ballot and serve two to three years on rotating terms.
Student representatives serve a one year term.

Authority of the IRC
The committee’s authority follows the general outline of Section 3.


[It should be noted that changes have been submitted to change the charge to reflect actual student membership, which include the CORe BaBAOW Ambassadors (Ex Officio) and up to one student representative from each of the partnet institutions).]

Class of 2007 Senior Gift
June 27, 2007

The members of the Class of 2007 present this endowment to fund green initiatives at Olin College. To ensure that the initiatives undertaken yield measurable results, the class has set the following guidelines for distributing the endowment funds administered by the Olin College Dean of Faculty Office.

I. Project Selection Process
a. A year long committee will be formed during CORe’s Fall Committee Selection Process, consisting of two students, selected by the CORe Executive Board through the CORe committee selection process, and one faculty member, selected by the Dean of Faculty when prompted by the CORe Vice President of Student Initiatives.
i. Charge:
1. The Committee’s first task will be to send out a request for proposals within 48 hours of formation.
2. The committee will evaluate green initiative project proposals submitted by members of the community and decide which project(s) will receive funding for that semester.
b. If there are not enough applicants to fill the committee spots, the funding for the semester will be returned back to the endowment.
c. One student, chosen by consensus by the committee, will be in charge of scheduling meetings, advertising project proposal submission deadlines, and performing general administration for the committee, including running the meetings.
d. All project proposals will be due once per semester one week after the committee is formed in the fall and at the end of Add Period in the spring. Funds will be assigned at a single meeting no later than one week after the submission deadline.
e. The committee is not required to approve a project every semester. If there are no applicants, or if none of the project proposals are feasible or appropriate, the money that would have been spent that semester can be re-entered into the endowment.
f. On the last day of classes each semester, the committee will publish a list summarizing all of the projects funded to date. This list will be publicly available and sent to the Class of 2007 yearly from the Development Office.

II. Funding
a. The committee will fund projects with up to 5% of the endowment earnings, distributed in equal amounts for each semester.
i. Until the Class of 2007 collects enough money to establish the endowment fund, $2,500 of the already collected gift money may be used to fund projects each year.
b. The recipients of the grant must only use the money for supplies that will contribute to the progress of their project.
c. The endowment will be open to donations from individuals or groups outside of the Class of 2007.
d. If no money is spent over a period of 10 years after the endowment has been established, the Class of 2007 gift funds will be returned to the Olin College endowment.

III. Project Selection Guidelines
a. The green initiatives project must have a tangible, measurable outcome that promotes sustainability and environmental awareness.
b. The project must benefit Olin College in some way. However, the project need not be limited to improving the college campus. Initiatives that improve the college’s relationship with the greater community are also encouraged.
c. Results of the project must be reported to the Olin Community and made available in a publicly accessible forum.

IV. If a situation should arise not explicitly covered by the document, the committee should interpret the intent of the document and act accordingly.

V. In the year 2012, the Class of 2007, coordinated by the alumni representatives review the progress of the green initiatives program and re-evaluate the intent and execution of the endowment.

Registration

• Manny: We are looking into registration problems, engaging the vendor, looking to improve performance. We will possibly test the system.
• Joanne: The vendor will be here over the holiday break.

Linux

• Manny: We have only had three students (and no faculty) respond to the new Olinux Fedora Core 7 release. We may survey the population and see if it's worth continuing with Olinux.
• Nik: I'm using it for Computer Architecture, running Windows in VMWare player inside of Linux, and it's working well, except I can't access the Internet through the VMWare player.
• Crawford: I had to switch from bridged mode to net mode for it to work.
• Manny: Next semester, we might offer a loaner so you can try Olinux if you already use another distribution.

Wireless

• Manny: Mike Horne has been working on it.
• Mike: Access Points have been crashing here and there, so Nortel has been giving us custom software to run on the master switch to collect more data. Other institutions have been having similar situations, but our situation appears to be unique. People haven't been complaining, though.

Printing

• Manny: We've been having some printing problems. Since our Ricoh contracts end in about a year, we're thinking of replacing the HP printers in the residence halls with one Ricoh printer per dorm.
• Students: It would also be nice to have copiers in the residence halls.

Winter break

• Manny: We'll be sending a note to students about computers and being away from Olin. Don't remove your system from the domain. Remember you can use VPN. It will probably be in the CORe Digest.

Expo

• Manny: There will be chaos in the computer lab. Mike fixed the paper cutter. We've ordered paper and ink cartridges, so we should survive. People need to clean up after themselves. Remember to print in draft mode and avoid colored backgrounds.

Random extras

• Jeff: Should students be able to send to the working group list?
• Manny: We want to get feedback from students. It can come from the student working group list, but for day to day things, students should contact the help desk.
• Mike: A good example is the dining hall wireless. I haven't gotten any feedback yet as to whether the changes have made a difference.
• Manny: Send feedback through the help desk. We want to know and we will fix things. We can't police all the rooms and make sure things are still there and working. We have to rely on people to contact us when technology stops working or disappears.
• Mike: The access points can read RFID if we buy additional software.

Minutes taken by Zack Coburn (2010)

Manny: recent issues
- Firewall issue is being resolved.
- Access points appear to be bouncing. Students haven't noticed. May have impact this weekend.
- Outlook 2007 is having disconnecting issues. Disconnecting calendar shares seems to help sometimes.

Mary: AV update
- We now have two cameras available.
- We purchased a few tripods.
- We purchased a Sony camera on eBay!
- We will update the students on cameras.

Javier: the portal
- Trying to gather feedback to make the portal a more effective experience.
- Manny: We are looking at other schools that use Jenzabar.
- Jeff: There are a couple one-stop shops, such as mrwiki.olin.edu/mrwiki, launchpad.core.olin.edu.
- Joanne: We are looking at getting cross-registration and some other forms online to make things easier for students, Linda Canavan. The portal is already tied in to all the backend systems.

Manny
- The recent VPN outage is being resolved with an upgrade.
- We are looking at integrating VPN with ActiveDirectory.

Jeff: SIS
- Speaking of downtime, in about two to three weeks, there's going to be some downtime on SIS. Should we all use the Portal since it buffers, whereas SIS does not?
- Most students SIS? Yes.
- Recommendation: Prevent people from using SIS.
- Joanne: The real problem with SIS is that there are cron jobs running in the background.

Manny: Linux
- How many people use Olinux?
- Dave Carver spends a lot of time keeping Olinux up to date. We are trying to assess whether students use it.
- We are looking at a pilot program involving VMWare. We are essentially ready to launch.

Manny: OlinCards
- We will be slowly rolling out a new interface for putting money on cards. There will be new features, like email notifications.
- Nik: Will it be tied in with ActiveDirectory?
- Manny: Yes. And you'll be able to have guest accounts so your parents can log in.

Manny: Software upgrades
- We have posted a lot of them. Many people haven't been upgrading applications. Should we issue reminders?
- FYI: If you get the Symantec LiveUpdate warning, it means it isn't running correctly.

Manny: File transfer
- We are looking for some simple file transfer solutions to let people transfer data in and out of Olin.

Manny: Public and Sandbox
- We need a good way to approach the student body about how they should be using network storage.
- Sharing copyrighted material is illegal.
- Big files are sometimes a problem.
- Joanne: Publish a list of top users?
- Brad: Yes!
- Nik: We need a script that tells each user where all of their files are. We could have an Olin-wide Public purging day.
- Leslie: We can't just purge Public. Faculty uses it, there are important files on it.
- Manny: Copyrighted stuff?
- Jeff: Delete it.
- Nik: You can't write a script to determine if something is copyrighted.
- Manny: But some files are obvious.
- Leslie: The Honor Board is also a resource. It would be legitimate to Honor Board people who repeatedly share copyrighted information.
- Brad: Is it reasonable for me to store backup copies of my media on the network?
- Manny: Yes, unless it's on a shared folder like Public.

Mary: Lights
- The computer lab has automatic lights now!

Manny: AV issues
- Some of the rooms in the AC are having AV issues. We are troubleshooting.
- Mary: You can always call the help desk.

Jeff: Public and Sandbox
- If you're going to get tough on Public and Sandbox, inform the students that you're going to get tough.
- Mary: Is an email the best way?
- Jeff: Probably.
- Javier: Send statistics about what we know.
- Leslie: The students don't know that IT knows.

Tenth body
- Leslie: IT understaffed still?
- Manny: We are working on getting a tenth body.

OS X
- Nik: Is ProTools Upgraded?
- Yes
- Nik: Can we get FinalCut Pro?
- IT doesn't own it. There would need to be a curricular need for it.

Meeting adjourned at 7:01pm

Minutes taken by Jeffrey Stanton (2010)

Attendance:
Brad Powers '10
Eli Sheldon '11
Jeff Stanton '10
Joanne Kosuth 'IT
Lindsay Kaye '11
Leslie Gerhat '10
Manny Aramal 'IT
Mary Fitzpatrick 'IT
Matt Crawford '09
Nik Wittenstein '09
Zach Coburn '10
Zach Kratzer '10

Full disclosure: Leslie, Nik, Zach K work in IT

IT Experience - the Good, the Bad & the Ugly
Turnaround time slow
Understaffed - student view
Questions like "Where is my laptop"

More IT/student training
Shorten first IT orientation
Several sessions later, before first weekend?
Student-run is better (Straight talk)
Students develop with IT before the fact
Laptops not on first day here == BAD (frosh, IT, etc say so)
On other hand, can be distracting in orientation

Curriculum decides software/features
More student feedback?

Support for academic tech is good, student life/social tech not perceived as well

Camcorders not available to students
Not IT's fault
Been brought to proper places
Cameras were bought for HDK's class (HDK was on sabbatical)
Wellesley video course students couldn't get cameras

Responsibility for equipment

Is equipment for academic use?
Where in learning continuum is the line?
Is there even a line?
General use / wear and tear lowers availability for academic use

Continue to email students about outages
Reasonable notice, students can't complain
IT Notifies everybody on system outages
Also check out indicators on it.olin.edu
Coburn: IT Emails on weekend are reminders of dedication