Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
  • 2 commits
  • 8 files changed
  • 0 comments
  • 1 contributor
Sep 03, 2012
Roger Que query Merge static assets into content directory a70112e
Roger Que query SBP forum archive changes
Create an sbp-forum/ directory for the verdict files.

Add the 2011 forum notes, which were previously hosted elsewhere.
769cedb
10 README.markdown
Source Rendered
... ... @@ -1,10 +1,8 @@
1   -This is the [nanoc](http://nanoc.stoneship.org/) tree used to generate the [UNC
2   -Computer Science Club Web site](http://csclub.cs.unc.edu/). In order to build
3   -successfully, the following additional Ruby packages are required:
  1 +This is the [nanoc](http://nanoc.stoneship.org/) tree used to generate the [UNC Computer Science Club Web site](http://csclub.cs.unc.edu/).
  2 +In order to build successfully, the following additional Ruby packages are required:
4 3
5 4 * [Haml](http://haml-lang.com/) and [Sass](http://sass-lang.com/) 3.1 or later
6 5 * [kramdown](http://kramdown.rubyforge.org/)
7 6
8   -To build, use `rake`; the generated output will be placed in a new directory
9   -named `output`. Note that pushes to the main GitHub repository will trigger a
10   -server-side pull and rebuild of the site!
  7 +To build, use `nanoc co`; the generated output will be placed in a new directory named `output`.
  8 +Note that pushes to the main GitHub repository trigger a server-side pull and rebuild of the site!
7 Rakefile
... ... @@ -1,7 +0,0 @@
1   -require 'nanoc3/tasks'
2   -
3   -desc "Compile site, adding static assets"
4   -task :default do
5   - system 'nanoc3 compile'
6   - cp_r 'assets/.', 'output'
7   -end
0  assets/cowlogo.png → content/cowlogo.png
File renamed without changes
0  assets/favicon.ico → content/favicon.ico
File renamed without changes
16 content/index.markdown
Source Rendered
... ... @@ -1,12 +1,12 @@
1   -The UNC Computer Science Club puts together social gatherings, peer education,
2   -seminars, and job recruitment events for undergraduates in [the Department of
  1 +The UNC Computer Science Club puts together social gatherings, peer education,
  2 +seminars, and job recruitment events for undergraduates in [the Department of
3 3 Computer Science](http://www.cs.unc.edu/).
4 4
5 5 Need to contact somebody?
6 6
7   -* If you'd like to hold an on-campus recruiting event, contact events
  7 +* If you'd like to hold an on-campus recruiting event, contact events
8 8 coordinator Katie Hawthorne at <kathryne@email.unc.edu>.
9   -* Internship or job opening advertisements should be sent to Kevin Jeffay at
  9 +* Internship or job opening advertisements should be sent to Kevin Jeffay at
10 10 <jeffay@cs.unc.edu>.
11 11 * All other inquiries or feedback can go to <cs-club@cs.unc.edu>.
12 12
@@ -15,8 +15,8 @@ Some things you may find useful:
15 15 * [Key-based authentication with OpenSSH](help/openssh-keygen/)
16 16 * [Slides for Chris Davis’ CrackChats](crackchat/)
17 17 * CS Club SBP forum results:
18   - [2011](http://www.unc.edu/~zhoum/csclub_sbpforum_2011.html),
19   - [2010](forum-2010.txt)
  18 + [2011](sbp-forum/2011.html),
  19 + [2010](sbp-forum/2010.txt)
20 20
21 21 Subscribe to the CSC mailing list:
22 22
@@ -31,6 +31,6 @@ Subscribe to the CSC mailing list:
31 31 </p>
32 32 </form>
33 33
34   -The [source code for this Web site](https://github.com/unc-csclub/csclub-web)
35   -is available on GitHub. The cow image in the header was generated with Tony
  34 +The [source code for this Web site](https://github.com/unc-csclub/csclub-web)
  35 +is available on GitHub. The cow image in the header was generated with Tony
36 36 Monroe’s [cowsay](http://www.nog.net/~tony/warez/cowsay.shtml).
0  assets/robots.txt → content/robots.txt
File renamed without changes
0  content/forum-2010.txt → content/sbp-forum/2010.txt
File renamed without changes
76 content/sbp-forum/2011.html
... ... @@ -0,0 +1,76 @@
  1 +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
  2 +<html>
  3 +<head>
  4 + <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  5 + <meta http-equiv="Content-Style-Type" content="text/css">
  6 + <title></title>
  7 + <meta name="Generator" content="Cocoa HTML Writer">
  8 + <meta name="CocoaVersion" content="1038.35">
  9 + <style type="text/css">
  10 + p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
  11 + p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
  12 + span.s1 {text-decoration: underline}
  13 + </style>
  14 +</head>
  15 +<body>
  16 +<p class="p1">This year the Computer Science Club endorses Ian Lee for Student Body President based on his Technology platform and presentation at the Tech forum.</p>
  17 +<p class="p2"><br></p>
  18 +<p class="p1">For more details about the Tech forum, please continue reading. If you have any questions (including if you're one of the candidates!), our contact information is at the bottom of this write-up.</p>
  19 +<p class="p2"><br></p>
  20 +<p class="p1">The platform score is 40% of the total score. The other 60% is based on the presentation that was given at the forum. In evaluating the presentation score, the club gave consideration to overall knowledge of UNC's IT (both breadth and depth), feasibility of their implementations, and their coherence to their written platform.</p>
  21 +<p class="p2"><br></p>
  22 +<p class="p1">In order to determine our rating of your platform, first, we as a group determined what we thought the important tech. issues campus faced going into next year and the foreseeable future. We then rated the candidates based on how many of these issues were addressed, as well as giving minimal points for other issues brought up by the candidates.<span class="Apple-converted-space"> </span></p>
  23 +<p class="p2"><br></p>
  24 +<p class="p1"><span class="s1">Our list of issues includes:</span></p>
  25 +<p class="p1"><b>Connect Carolina</b> -- Student Government serves as a key point for addressing student grievances. Considering the grumbling about CC this year--how will your administration address that?</p>
  26 +<p class="p1"><b>Student organization websites</b> -- changes have been made to how student orgs address webspace. How will you deal with publicizing this / making sure each group has easy access to publicize their group? Is this even SG's job?</p>
  27 +<p class="p1"><b>Publicizing existing tech. resources on campus<span class="Apple-converted-space"> </span></b></p>
  28 +<p class="p2"><br></p>
  29 +<p class="p2"><br></p>
  30 +<p class="p1">Following is a break-down of each of the candidates.</p>
  31 +<p class="p2"><br></p>
  32 +<p class="p1"><b>Ian</b></p>
  33 +<p class="p1">We thought it was really important that Ian addressed that ConnectCarolina is an important tech concern facing the university in the near and far future. We thought that it was commendable that he pointed out specifics in ConnectCarolina that needed to be improved, but the few things he pointed out in his online platform (i.e. new grads system) are in place to happen next year anyway. We wish that he expressed more desire to find out from the student body what they wanted to see from Connect Carolina.</p>
  34 +<p class="p2"><br></p>
  35 +<p class="p1">Even though one of Ian's largest points was ubiquitous wi-fi, which is something that been considered and contentious in the past, we felt like he defended his point very well. Ian explained at the forum, that he felt like wi-fi in the dorms and other places on campus, was more than a technical issue, but actually a signal of the university's technical prominence and in short: a good advertising measure for the university. We also liked that he emphasized that it was a long term goal and not something that he necessarily expected to accomplish in the next year.</p>
  36 +<p class="p2"><br></p>
  37 +<p class="p1">TL;DR</p>
  38 +<p class="p2"><br></p>
  39 +<p class="p1">As a club, we thought that Ian had the best vision for technology issues on campus that face students and also has the technical know-how to face new challenges that could crop up.<span class="Apple-converted-space"> </span></p>
  40 +<p class="p2"><b></b><br></p>
  41 +<p class="p1"><b>Brooklyn</b></p>
  42 +<p class="p1">Brooklyn has built her campaign around being a connector, and one concrete way she showed that this would be useful as SBP is in pointing out that ConnectCarolina needs to conform to the policies of various administrative communities on campus, from Admissions to Advising.</p>
  43 +<p class="p2"><b></b><br></p>
  44 +<p class="p1">We appreciate Brooklyn's admission of not having personal technical know-how that Ian does. And we do appreciate that she believes strongly in connecting and finding people with expertise in specific issues, including technology. However, we were not convinced that she has the direction and the overall vision in order to take other people's experiential input and turn it into directed, specific goals. Brooklyn could do well, but she would take a long time to ramp up to speed: time that a 1-year SBP does not have.</p>
  45 +<p class="p2"><b></b><br></p>
  46 +<p class="p1"><b>Mary</b></p>
  47 +<p class="p1">We appreciated Mary's breadth of knowledge and numerous tech issues on campus her platform addressed. We commend her ability to talk on all these disparate points at the forum. We especially like that she believes strongly in publicizing the already available resources on campus.</p>
  48 +<p class="p2"><br></p>
  49 +<p class="p1">However, we felt that despite the many great tech points she had, there was no coherent vision driving her technical platform. Even in her written five-year plans and ten-year plans, there is very little coherency. Nor, did she bring up her ideas for Carolina being a technical innovator at the forum.<span class="Apple-converted-space"> </span></p>
  50 +<p class="p2"><br></p>
  51 +<p class="p1">We really liked Mary as a candidate, both generally and as from a tech point of view, but Ian pulled through because of our sense that he had a stronger vision.<span class="Apple-converted-space"> </span></p>
  52 +<p class="p2"><b></b><br></p>
  53 +<p class="p1"><b>Rick</b></p>
  54 +<p class="p1">Unfortunately, Rick cited other commitments this evening and could not attend our forum. Based on his written platform, we appreciated that Rick thought that ConnectCarolina was an important issue (duh, we agree), however he didn't state any specific plans regarding ConnectCarolina.<span class="Apple-converted-space"> </span></p>
  55 +<p class="p2"><b></b><br></p>
  56 +<p class="p2"><br></p>
  57 +<p class="p2"><br></p>
  58 +<p class="p2"><br></p>
  59 +<p class="p1">Max Beckman-Harned</p>
  60 +<p class="p1">macmaxbh@email.unc.edu</p>
  61 +<p class="p1">Tech&amp;Web Co-chair, Medlin &amp; Jones administration</p>
  62 +<p class="p2"><br></p>
  63 +<p class="p1">Maggie Zhou</p>
  64 +<p class="p1">mz@unc.edu</p>
  65 +<p class="p1">CS Club President, 2008-2011</p>
  66 +<p class="p2"><br></p>
  67 +<p class="p1">Roger Que</p>
  68 +<p class="p1">query@unc.edu</p>
  69 +<p class="p1">Class of 2012 (aka. will still be around)</p>
  70 +<p class="p2"><br></p>
  71 +<p class="p1">Aditya Anand</p>
  72 +<p class="p1">adityaa@email.unc.edu</p>
  73 +<p class="p1">Class of 2014<span class="Apple-converted-space"> </span></p>
  74 +<p class="p2"><br></p>
  75 +</body>
  76 +</html>

No commit comments for this range

Something went wrong with that request. Please try again.