The UP Computer Science Network : Alliance of Computer Science Students

By Jeffrey Louie Quiambao (http://jefspeaks.i.ph), taken from the June-August 2005 Issue of The UP Parser

Terms usually are vulnerable to misconceptions. It is for that very reason why the term “CS Network” accidentally misleads many people, especially those who are not well informed. Only through transparency can we effectively inform people with utmost truth and clarity. What is this CS Network, then?

Let’s take note of this one fact first: things change. That is why it’s being said that it’s the only thing which remains constant. And with change, adaptation must proceed with it. The CS Network that exists today is just another prodigy of change. It was first conceptualized by the former Computer Science Representatives (AY 2004-2005) to be almost the department equivalent of the Engineering Alliance of Student Leaders (EASL) where different organization heads/representatives were called to be the audience of the incumbent Engineering Student Council for their presentation of their projects and plans for the college. It was aimed for faster and better information dissemination. Now, the present Computer Science Representatives with their primary goal for their term of a homogenous Computer Science community, together with the CS department realized the potential of the CS Network to suffice what is being required.

The CS Network is now an avenue for anybody, may it be a CS organization or a CS student alone, who is willing to help for the betterment of the department and as well as the college. It also acts as a unified body aiming towards a harmonious CS community (i.e. every activity/project is a product of having the benefit of the many as its primary goal). And with the coming of the Engineering League of Excellence (ELE), the CS Network now stands as the local council of the CS Department.

Currently, it is composed of the incumbent CS Representatives as coordinators, faculty advisers (of the student body and as well as of the different CS organizations) and representatives from the different CS organizations and service arms.

DCS BATCH REPRESENTATIVES
Freshmen Reps
1) Antonio Mari San Miguel
2) Joan Cantillas
3) Jim Lerry Guiyab
4) Manica Dimaiwat
Sophomore Reps
1) Ma. Elena Bacay
2) Roger John Ragasa
3) John Michael Tolentino
Junior Reps
1) Joebet Isaac Del Rosario
2) Tristan Jed Roque

CS NETWORK GUIDELINES
Description
The CS Network serves as an intermediate level between the department and the organizations/students, and a venue to convene and share ideas among organizations. It gives support to activities if what is asked will not exceed the capabilities/limitations of the department. It is open to any organization/student that/who is willing to help the Department and/or College in any way.

Objectives

• To coordinate and mediate the activities of the students or organizations.
• To improve information dissemination.
• To ensure a systematic scheduling delegation of similar activities for department-related events.
• To promote harmonious working relationship.
• To support activities that promotes the well-roundedness of the students.
• To document every activity made.

Guidelines

1. All projects of the Department and the ESC shall go through the CS Network if the CS students are the stakeholders.
2. An organization is required to present their department-related activities to the CS Network. An activity is department-related if the name “Department of Computer Science” is mentioned in the event or it supports the initiatives of the department.
3. An organization is not required to present their non-Department-related activities to the CS Network. However, they are requested to submit a post-documentation of their project for the Engineering League of Excellence Merits (ELEM).
4. When two (2) or more NEW and same activities are presented in the Network, a First-Come-First-Served Basis is implemented. Established events are considered PROTECTED and are not subject to this rule.
5. All activities that will go through the CS Network must submit a pre-documentation and post-documentation. The template for the documentations is uploaded in the CS Network mailing list.
6. All minutes of the meeting must be forwarded to each organization’s mailing list unless specified otherwise.