opensutd / community

OpenSUTD's DNA

OpenSUTD/course-materials

17/01/19 - This repository has officially moved under the OpenSUTD organization, and will host academic materials. Please do not submit personal projects here - existing ones will eventually be reallocated to other spaces.

Hello there, welcome to OpenSUTD! We believe knowledge should be available for everyone who wants to access it. MIT set up OpenCourseWare in the spirit of sharing knowledge with everybody - this is our take on it, and it'll be interesting to see what this evolves into!

Important note The endgame for this project is simply to be a platform to share information. If you are the creator or owner of any of the materials on this repository and would not like it to be here, we will take it down.

What is this repository for?

This should be a space to encourage self-improvement and share knowledge, not spoon-feed it. What's fair game for contribution:

• Past lecture materials
• Past quiz, assignment, and homework questions
• Posters
• Project reports
• Personal notes

What shouldn't be here:

• Personal projects, quiz, examination, and homework answers (Tips and notes are fine)

Contributing to OpenSUTD

Anyone can contribute material by submitting a issue or pull request! This prototype is still in its infancy, so we're looking for collaborators to act as content curators, who help to manage what's in the repository. In the case of legacy course materials, curators should have taken the course before.

Repository Structure

As the repository grows, optimizing its structure lets people find what they want easily. An example would be:

/Courses
	/10.001 Advanced Math I
		/Summer 2017
		/Projects
		...
	...
	/50.002 Computation Structures
		/Fall 2017
		/Projects
		...
	...

File naming should be consistent across the repository. In general, stuff should be organized and easy to find:

• Courses with their code and canonical name, e.g. 10.001 Advanced Math I
• Lecture slides should have the week number and a descriptive filename, e.g. Week 10 - James Scott - Commentary on Jacob's work.pdf
• Subdirectories as needed, e.g. /Additional Readings or /src

community's Issues

Mission Statement

I realise the community repo doesn't have the mission statement which can be found on the github.io.

Should we be fixing this.

Contribution Guidelines

As an example: https://gist.github.com/PurpleBooth/b24679402957c63ec426

I'm thinking a separate code of conduct document is still a good idea though. In which case:

• CONTRIBUTING: Guides for Project Submission, or contributing to current OpenSUTD projects. Include some git usage tips and guide, and the typical disclaimers what NOT to contribute. This page will be highlighted by GitHub automaticallly.
• CONDUCT: Code of conduct document, mostly common sense. Assume that people are generally nice and should be following it even if they did not explicitly read it, so we don't need to serve it in people's face except if there is a "problem" somewhere.

Let's get this worked out ASAP.

Proper Description of OpenSUTD

We need:

• clear statement showing what OpenSUTD is
• clear statement showing what OpenSUTD is not
• Mission statement #4
• logo #5

And then we need to reconcile this with the website

Unable to upload

Edits can be made to submit pull requests, inclusive of changing file content, file name, etc.

However, uploads are disabled in all repositories. I tried uploading in community and in fifth-row guides, its disabled. Pls fix thanks!

Onboarding guide

We need an onboarding guide so that we can make new contributors' experience more friction-less.

Something worth exploring: OpenBadges

Open Badges are verifiable, portable digital badges with embedded metadata about skills and achievements. They comply with the Open Badges Specification and are shareable across the web.

Each Open Badge is associated with an image and information about the badge, its recipient, the issuer, and any supporting evidence. All this information may be packaged within a badge image file that can be displayed via online CVs and social networks. Thousands of organizations across the world issue badges in accordance with the Open Badges Specification, from non-profits to major employers to educational institutions at all levels.

Badges may represent many different types of achievements and claims.

https://openbadges.org/

Logo Change

Issue thread for contributions for a new logo design

Files go to https://github.com/OpenSUTD/community/tree/master/branding

OpenSUTD Visual Identity

Open call for OpenSUTD logo - April '19

Calling for designers and contributors - like all things OpenSUTD, our visual identity is up for co-creation! This includes our logo, our palette, and visual design principles. After all, the community should be the one to design its identity, right?

Get started by looking at Issue #5: Logo Change.

Assets required

References

• How to create and deliver the correct logo files to your client
• A designers guide to creating logo files

Start with a vector .ai file

Optimize for screens (RGB). OpenSUTD is currently very much an internet community, and we don't expect to be printing (yet!).

Raster copies in .png and .jpg

Export small file sizes for web display, etc. Common sizes are square 200px, 500px and 1000px.

Different variants

A lockup is simply a different layout configuration.

For example, if your logo is made up of both typography and an icon, you might have 2 layout variants such as; a long/thin version with the icon to the left of the text, and another with the icon above the text. Here’s an example from logogeek.uk:

get smashed get smart: a continuation of the OpenSUTD spirit

get smashed get smart

This idea was stolen from fishbiscuit, because I'm a bad guy that way. Thanks QZ!

Motivations

Knowing that the OpenSUTD framework has been validated through the execution of DiscoverSUTD;

Recognizing that momentum from the successful execution of DiscoverSUTD will decay with time;

Further acknowledging that consistent output further reinforces the legitimacy and efficacy of the organization;

Recalling that the spirit of OpenSUTD is one of sharing;

Wat dis?

I propose we run a session for lightning talks (aka data blitz) open to all members of the SUTD community, but done with presenters (and possibly audience) being somewhat inebriated. See "Drunk Powerpoint Presentations" for a similar concept.

Why dis?

Experiences from DiscoverSUTD point to there being a persistent need for experience/knowledge sharing from the senior students and/or researchers to the younger batches. Styling them in a shortened, bite-sized format and placing these interactions in a casual context allows us to catalyze this information sharing with minimal time/resource investment.

How dis?

A possible way of doing this would be:

When: Start of Term 6 (Fall Term), 9 - 11pm
Where: Mont Calzone
What: Internship Experiences and How to not Get Snek'd by Corporate
Who: Returning Seniors and Curious Freshies

Marketing Efforts: Word of Mouth, Telegram Groups, Some sort of alcohol deal to lure in dem alcoholisms.
Presentation Format: Ignite Lightning Talk format (20 slides x 15 seconds) for 5 minutes each.

Call to Action

This is an easy-to-organize, low investment way to keep the momentum going from the DiscoverSUTD suppers. Do share any feedback you have on the viability of this idea. Thanks.