About half the classes listed on the homepage do not yet have pages created for them. We need to get these pages made and older pages updated to continue to be a relevant source of information for CS students at Cornell.

Might be able to help out here, so a quick question: is this more of the required classes such as MATH 1920/2210 kind of classes, classes that are of interest such as MATH 4710/4740, or both types?

Some of the sections seem to be somewhat redundant (e.g., general advice / testimonials). Also, some of the information becomes outdated very quick (e.g., past offerings). Suggestions on how to improve the structure?

Random thought -- it would be pretty cool if the list of courses on the homepage of the Wiki could be automatically generated from the list of .md files in the classes folder. This would reduce the amount of manual work involved in adding and removing classes, and it would ensure that new pages for classes aren't accidentally ignored and not featured on the homepage.

I edited the repo recently, and I noticed that the changes weren't updating on the actual website. Then I noticed that the list of contributors, which was updated in January 2019, was also not up to date, which indicates that the website has been out of sync with the repo since at least then.

Look at contributing.md for a good example of the issue. The markdown syntax isn't working properly, and as a result, the page is very cluttered and difficult to read.

The primary function of the CS Wiki is to be a resource for learning about CS classes offered at Cornell. There exists other content as well, but the vast majority of the content is class specific.

Most of the class pages have more-or-less the following structure:

• General Information
• Prerequisites
• Topics Covered
• Workload
• Testimonials
• Past Offerings

General Information, Prerequisites, and Topics Covered contain information that is largely just ported over from publicly available course websites.

The remaining sections cover the workload of the class, general opinions, advice, and feedback related to the class, professor name, semester taken, and median of the course. With the exception of the median, all of this information would be included in a course review site like CU Reviews (managed by Cornell DTI).

The years of content we have are certainly valuable, but what reason is there to encourage students to provide new information here rather than on CU Reviews? On that site, they would not need to deal with the hassle of creating PRs and could easily contribute anonymously. Possible fixes to those problems are discussed in #80, but the solution is already implemented on CU Reviews.

If the only new information the Cornell CS Wiki is providing is course medians, perhaps it would be better for the Wiki to go into a conservation/archive mode, where we retain all the existing information and continue to host the site, but encourage users to contribute to CU Reviews instead of adding info here. It will also be useful to students if course information is consolidated in one place, so they do not have to peruse multiple sources.

(side note -- a project dedicated to just collecting the medians of courses at Cornell would be pretty interesting)

Thoughts on this proposal? I've been thinking about it on and off for some time, and continuing to 'compete' with CU Reviews and similar sites doesn't seem practical or helpful to the community overall.

It looks like Github has updated their web editor a bit (based on what I saw in CS 5152) - might want to update that just to keep up to date.

See any class page. Kramdown parses other Markdown in tables just fine, but for some reason links are not linkified unless explicitly linked (which is annoying).

Add pages on how to get involved with open source on campus

The required math classes page is missing information on the linear algebra requirement, and could use some revision in general. There is probably enough information on the intro math classes at Cornell that we don't need this page, but if someone wants to update it, go ahead.

I thought maybe we could add @dragon-girl88 's design (the current favicon) to the front page of the Wiki as a logo as well. Anyone have any strong opinions on this? We could place it next to the title.

This is probably a little minor, but I think labeling CS major core classes (111x, 211x, 3110, 3410/20, 4410, 4820) will make it easier for people to spot them if they want info about them

Thoughts? It'd make it easier to cross-reference too

Adding a favicon to the wiki would definitely make it look more aesthetically appealing :)

What's the best way to encourage participation in contributing to the wiki? Having to commit PRs, etc. seems to be a somewhat high barrier to entry. I think another big reason is the desire for anonymity. Perhaps we could set up some sort of anonymous form where people can add their feedback? Thoughts?

If anyone is familiar with Ruby, it would be helpful to have comments explaining the logic in the Wikilink matcher implementation just in case any changes are ever necessary.

Hey @rishi1999, I notice you're quite active in the repo. Would you like to be added to the CornellCSWiki org to effectively gain full permissions around the wiki?

I graduated in 2017 so getting a new maintainer is probably a good idea. I'm unsure if Open Source Cornell still promotes this wiki. It'd be good to post about it again in groups and such, or to reach out to URMC, WICC, or ACSU to raise awareness about it as both a resource to learn about courses and contribute information.

I like the collaborative nature of having this information on Github, and back when I was still at Cornell it was a good resource for "Intro to git/Github/open source contributing" type workshops too. I know student groups are sometimes in the lookout for opportunities to host teaching events.

In any case, let me know.