Old CoRE Constitution
CoRE Living Contract
CoRE is an acronym that stands for COmputers, Robotics and Engineering. Located in O'Connor hall in the Dickinson Community at SUNY-Binghamton, we are a Special Interest Housing (S.I.H.) group dedicated to learning and sharing knowledge in these subjects.
CoRE has several projects under it's belt, including the semi-annual Maximum Overkill competition, where CoRE sets up the lecture halls for 3D-gaming. We also make our own print, radio and TV ads for the event and run them on campus. We also currently in the planning stages of a project with the Kopernik space center, as well as a project involving a Blimp-Cam!
CoRE is one of the longest-lived S.I.H. groups on campus, with a rich history spanning back to 1991. Indeed, many of the CoRE alumni still visit often to relive their CoRE days, and offer advice (and sometimes jobs!) to current members of the module. CoRE history is handed down in the form of CoRE-Lore stories that are told every year at the CoRE-Lore dinner. The CoRE-Lore dinner is open to all current and former CoRE members, and provides a chance for all to speak, mingle and eat good food.
If you are interested in learning more about CoRE, please click the other tabs located above this text. If you still have questions, feel free to contact any member of the C-Board for an answer. Adios!" You have to be a Binghamton University student if you want to form part of the CoRE special interest housing. (SIH) Binghamton attracts intelligent, talented, motivated students. Admission standards are high, and the Committee on Admissions evaluates each application for evidence of academic and non-academic strengths. Overall, school average, cumulative rank in class, trend and distribution of grades, courses selected, and SAT or ACT scores are taken into account. Though not required, achievement test scores are reviewed if submitted. The committee also looks closely for evidence of extracurricular and community involvement, special talents, leadership ability, intellectual curiosity and other positive qualities. Personal statements from applicants are welcome, and help the committee learn more about the person behind the application.
Offered on a first-come, first-served basis, allows you to enrich your Binghamton experience by learning more about a particular interest and living with others who share it. The SIH environment is conducive to forming relationships and fostering a lively exchange of knowledge apart from the traditional classroom setting. You and the other residents work closely with a faculty adviser and residence staff to coordinate projects and plan activities.
Participant Requirements
Participants must have a genuine interest in exploring the world of technology, including much more than a passing interest in computers, engineering, or robotics. Applicants must be willing to work to achieve the positive environment, which will best facilitate module goals. A strong interest in learning, however, is the most critical quality, along with a willingness to devote a good deal of effort to module endeavors. SHI applications can be found in the residential life office.
For more information visit the Residential Life web page or contact mcarra@binghamton.edu.
I. Introduction
As members of the Computers, Robotics, and Engineering Special Interest Housing Module (CoRE), we are committed to an active living environment, promoting education and awareness in computers, robotics and engineering related topics, and advancing spirit within the Module, and throughout the community at large.
II. Goals and Objectives
It is the goal of this Module to promote members' knowledge in areas of interest.
It is the goal of this Module to create community spirit amongst its members.
It is the goal of this Module to help provide support for the University Community, and in particular Dickinson Community, in computer related areas.
It is the goal of this Module to promote the advancement of computer literacy on campus.
It is the goal of this Module to promote the availability of computing services on campus.
Programs which have already been or are being planned or conducted include:
Conducting presentations involving demonstrations of Module work and/or computer related topics at Parent's Weekend and other occasions
Computer tournaments and \"Boffers\" at the Dickinson Days as part of the \"Battle-a-thon\"
\"Maximum Overkill\" - computer gaming on the big screens of the Lecture Hall
Maximizing productive use of networking connectivity between Module members and others.
The Module is responsible for maintaining and staffing the Pseudopod, a small computer center in O'Connor Hall. Pseudopod administration is among the most important of CoRE projects. It is coordinated by the Pseudopod Manager, whose duties and position are defined below.
There are eight elected positions and an optional number of appointed positions within the Module.
The E-Board is defined as the eight elected positions. It exists to handle Module crises and to decide how to present issues to the Module. It should be noted that the E-Board has no more power than its individual members' powers, as described below. Further more, the E-Board must maintain open communications with Module members. Any E-Board decision may be overturned by a majority vote of Module members at a Module meeting.
The C-Board is defined as the eight elected positions, all appointed positions, and the CoRE RA's. It exists to accelerate the decision making process. A C-Board meeting shall be held each week as a preparatory meeting for the general CoRE meeting. At CBoard meetings, it may be requested that only C-Board members talk, for the purpose of efficiency. The C-Board may discuss issues to be brought up at the CoRE meeting for a vote by acclimation. However, any module member may request that such an issue be brought to a general vote. Any C-Board decision may be overturned by a majority vote of Module members at a Module meeting.
CoRE meetings exist to keep members informed of Module business, and to discuss issues with long-term effects on the Module, i.e. large purchases. The CoRE meeting is also the arena where any Module member may raise concerns about Module issues, i.e. C-Board decisions.
A. E-Board Positions
The President is responsible for representing the Module to the general public, speaking on behalf of the Module, coordinating programs (i.e. making sure that things happen -- final responsibility), validating project proposals, running CoRE meetings, and seeing that required tasks of other positions are fulfilled when the actual position holder is unavailable. The President may act reasonably as any other E-Board member, provided that the member in question is kept informed of all issues. The President dent is the only CoRE member with the authority to represent CoRE to the public, save the Vice President in certain circumstances (See Vice President Below), but he may designate this authority to other CoRE members for specific occasions. The President may, with the approval of the Treasurer, make necessary \"small\" purchases (as defined in section V. Funds Allocation) in the course of performing his duties, as long as the rest of the Module is kept informed of these purchases. The president has the authority, and responsibility to deal with any situation not outlined here as a responsibility of another E-Board member. Where at all possible, the Module President should be a returning member.
* Note: All interactions with the Computer Center are the responsibility of the Network Coordinator.
The Treasurer is responsible for overseeing Module and Pseudopod finances, including keeping records of Module and Pseudopod expenditures, receipts, and available funds. The Treasurer is also in charge of coordinating fund raising activities. The Treasurer must agree to any minor financial decisions made by the President, Pseudopod Manager, System Administrator, or Resource Room Manager without the express permission of CoRE before that E-Board member may use their \"small purchases\" privilege. The Treasurer is also responsible for executing these purchases in the best interests of CoRE. The Treasurer alone may not make any purchasing decisions for CoRE or the Pseudopod. The entire module must be informed of all purchases made by the Treasurer.
The Pseudopod Manager is responsible for maintaining the good working order of the Pseudopod's equipment, supervising the presentability and cleanliness of the Pseudopod, maintaining the proper staffing of the Pseudopod, and keeping the module and community apprised of its status. In regards to proper staffing, the Pseudopod Manager is responsible for making sure that an empty shift is filled, whether by him-/herself or by another Module member. It is the duty of the Pseudopod Manger to educate CoRE members as to the proper use and function of all Pseudopod equipment (e.g. Pseudopod orientations). The Pseudopod Manager has the authority to deal with any situation related to CoRE equipment located in the Pseudopod and not related to computer hardware or software. The Pseudopod Manager may, with the approval of the Treasurer, make necessary \"small\" purchases (as defined in section V. Funds Allocation) in the course of performing his duties, as long as the rest of the Module is kept informed o f these purchases. The Pseudopod manager is also the chairman of the Pseudopod DTC committee.
The System Administrator is responsible for maintaining all CoRE computers' hardware and software (including the Pseudopod), as well as communicating with all CoRE Members to keep them apprised of the current status of CoRE machines (i.e. working o order, upgrades, as well as any other changes). The System Administrator has the authority to deal with any situation related to CoRE computer hardware and software. The system administrator must have all administrative passwords to all CoRE systems, and is the only one who may change these passwords. The System Administrator is also required to make sure that the knowledge needed to administer CoRE's systems is taught to as many interested CoRE members as possible. The System Administrator may, with the a approval of the Treasurer, make necessary \"small\" purchases (as defined in section V. Funds Allocation) in the course of performing his duties, as long as the rest of the Module is kept informed of these purchases.
* Note: All interactions with the Computer Center, and all network address management issues are the responsibility of the Network Coordinator.
The Resource Room Manager is responsible for maintaining the CoRE resource room, as well as enforcing quiet hours and any other regulations imposed upon the room by the University, the Module, or both. S/he is responsible for keeping track of all of CoRE's property kept in the resource room (e.g. the CoRE library), as well as maintaining the proper order of the room. If the resource room is misused it is the responsibility of the Resource Room Manger to deal with the situation in whatever manner is deemed most appropriate and fair by him/her. This includes but is not limited to the revoking of Resource Room privileges and closing the room to all CoRE members for a period of time determined by the Resource Room Manager in conjunction with the President t and the RA's. The Resource Room Manager has the authority to deal with any situation related to CoRE equipment located in the CoRE Resource Room and not related to computer hardware or software. The Resource Room Manager may, with the approval of the Treasurer, make necessary \"small\" purchases (as defined in section V. Funds Allocation) in the course of performing his duties, as long as the rest of the Module is kept informed of these purchases. Where at all possible, the Resource Room Manager should be a new CoRE member who expects to be returning to the module the following semester.
The Network Coordinator is the liaison between the Computer Center and the Module. S/he is responsible for reporting network related problems to the Computer Center and keeping Module members informed of the status of network related issues. The Network Coordinator is responsible for the CoRE computer network, both module-owned and member-owned, and should work with the System Administrator to determine how that network is to be used. The Network Coordinator is also required to assist CoRE members in setting up and maintaining their own network connections. The Network Coordinator should endeavor to keep an open dialogue between the Computer Center and the Module.
The Secretary is an elected official responsible for keeping attendance at Module meetings, maintaining Module records other than finance records, assisting the E-Board members with the execution of their duties, and interpreting the Lifestyle Agreement within its literal confines.
The Vice President is an elected official nominated by the Module President within 3 weeks after the general elections. The Vice President is responsible for assisting the President in his/her duties, as well as coordinating and presiding over C-Board meetings. The Vice President may act reasonably as the President in situations where the President is unavailable, providing that the President is kept informed. This position does not guarantee the holder a future position as President of the Module, but is intended solely to aid the President in the running of the Module. Where at all possible, the Vice President should be a new Module member who expects to return to the Module the following semester.
All elected officials must keep the President informed of all pertinent Module issues.
The elected officials are empowered to act in their duties without consulting the Module, if necessary, as long as the Module is kept informed of all significant activities.
It is the obligation of each of the above positions, upon deciding to resign or not to run again, to train any individuals interested in taking over in that position.
Most importantly, all E-Board members have a responsibility to provide learning opportunities for Module members, whenever possible.
Should an elected official decide to resign, CoRE must be given at least one (1) week of notice.
B. Appointed Positions
The President, Secretary, Treasurer, Pseudopod Manager, Resource Room Manager, and System Administrator may appoint assistant positions as needed. All assistant positions are to be filled by way of a nomination from the primary position holder, and a simple majority of the E-Board. Assistant positions may be removed at the discretion of the appointing member. No person may hold more than one elected position at a time, and assistant positions may be combined with other assistant positions or elected positions by general discretion and common sense. In general, the positions of President, Treasurer, Secretary, System Administrator, and Pseudopod Manager should not hold an additional appointed position. Should the assistant decide to resign, the primary posit ion holder must be given at least two (2) days notice.
C. Elections
E-Board members (with the exceptions of the Vice President and Resource Room Manager) will be elected for a given semester at the last CoRE meeting of the preceding semester. The Vice President and Resource Room Manager will be elected for a given semester no later than the third CoRE meeting of that semester. There will be a letter of intent period of at least one week before all elections.
D. Vacancies
Should an E-Board position become vacant, the President must act as that position, or may appoint a temporary replacement, until an election is held. This election must be held as soon as is reasonably possible, allowing for a one (1) week letter of intent period after its announcement at a regular CoRE meeting.
V. Funds Allocation
The Module receives funds from a number of sources. These funds are to be allocated according to the needs and wishes of the Module as a whole, and the purpose for which they were designated by the funding source. As detailed above, some E-Board members may allocate money for \"small\" purchases without formal Module approval. These purchases are limited to 5% of the total amount currently in the appropriate fund per week. This may only be done if it is clear that such a purchase is important, and the time remaining before the next floor meeting is such that it is not convenient to seek formal approval at that forum. \"Large\" (those not \"small\" as defined above) purchases must be authorized by the Module by consensus or, if necessary, by a simple majority vote, at a Module meeting.
VI. Member Responsibilities
1. Members are responsible for faithfully executing the duties of Module positions to which they have been elected or appointed, for as long as they hold those positions. If a Module member intends to resign from a position, s/he must give at least 7 days advance notice.
2. Members have a responsibility to the Pseudopod as designated by the Pseudopod manager, the consensus of the Module, and the Pseudopod Rules. Module members may miss their Pseudopod duty only if another Module member has committed to covering their scheduled hour or been granted authorization by the Pseudopod Manager. Pseudopod members may exchange shifts by mutual consent.
3. Each Module member is responsible for being a major participant in at least one project each semester, beyond those projects conducted as a part of regular Module activity. The President will determine whether a project satisfies this. In extreme cases, the Module may vote to override, with a simple majority, the President's rejection of a project. A project, by definition, will not count for the above unless it has been written up in the proper manner and handed in to the President.
4. Members are expected to attend weekly Module meetings, at a regular time and place established by consensus at a previous Module meeting. Members may miss a meeting only if they have been authorized to do so by the President or Secretary. In that all votes will be held at the Module meetings, voting privileges extend only to present members or those properly excused.
5. Module members are required to respect Module and Pseudopod equipment and resources. They must use them according to guidelines and regulations developed by the Module. They must not intentionally damage them or intentionally promote their decay . Refer to Rules for Proper Use of the Pseudopod and Proper Use of the Network.
6. Module Members are expected to do their best to maintain cordial relations with each other.
7. It is the responsibility of the individual Module member to receive a Pseudopod orientation prior to the opening of the Pseudopod for general hours. A member cannot receive his key to the Pseudopod/Resource Room without previously having an orientation.
8. Every Module member is required to have an account on the Module's system(s), and is required to have some form of a Web page, and read a required e-mail list (core-announce). Failure to fulfill these responsibilities is grounds for consideration of revocation of Module privileges.
VII. Disciplinary Action
The Module does not have the ability to remove any member. It may however remove all privileges granted by the Module. The E-Board must decide on a case by case, privilege by privilege basis what removal possibilities to bring to the voting attention of t he Module at a Module meeting. A Module member may bring up another member for removal by bringing it to the attention of the E-Board. A Module member may bring an E-Board member for removal as below.
An E-Board member may be brought up for removal from E-Board by a unanimous vote of the rest of the E-Board, or by a Module member, and receiving a simple majority vote at a Module meeting.
VIII. Lifestyle Agreement Amendments
Any CoRE member may propose an amendment to this document at a regular CoRE meeting provided s/he has the proposed change in writing with her/him, and s/he proposed this amendment at the previous C-Board meeting. S/he must read the changes in their entirety, and field any relevant questions. A 2/3-majority vote of those CoRE members present results in that amendment's incorporation into this document immediately.
";