On Saturday, May 10th, we held our twenty-seventh Open Source Comes to Campus event at the University of California-Davis. The event was organized by the Davis Computer Science Club and sponsored by Rackspace. Many thanks to our amazing mentors: Thomas Kluyver, Britta Gustafson, Charlyn Gonda, Conrad Fay, Kevin Liu, Michael Seydel, Jackie Zhang, Timothy Tong, Alex Mandel, Mike Covington and Asheesh Laroia.
At the event, we used the Software Carpentry sticky-note method for gathering feedback. We asked students to tell us one thing they learned and/or enjoyed, and one thing we could improve on.
What Students Learned
Many students talked about the open source tools they used at the workshop:
* How to use git; Install IRC; Learn some commands
* GitHub. How to pick a project.
* Learned more git!
* I learned how to use IRC chat.
* I learned that you can tag git commits and use them to reference commits.
* IRC. Never used it before, and it looks like there are awesome channels for webdev.
* I learned about git revert, and how totally kick ass it is.
* I learned how to use git better.
* Learned how to navigate git.
* What branching in git actually is.
* How to collaborate using git.
* How to use git; how open source software works.
* I learned how to set up git, and get little familiar of open source project.
* Git commands.
* Awesome way of interacting with tools while listening to lecture.
A couple of students mentioned types of open source projects they were excited to learn about:
* Open source possibilities for designers.
* Open source can be used for good (humanitarian projects)!
* Learned: how to get involved with open source projects by Googling information about the project and lurking the repository for information.
* How to properly find open source projects.
* I learned how to find projects to work on.
* I learned a process to start on open source projects.
* How easy it is to search for projects and find important contacts.
* Learned how to gain credibility.
* Learned how to gain exposure in open source projects.
* Found some cool open source projects that relate to my interests.
* I get to know more about open source projects! Found some cool projects and want to try to explore them. 🙂 Thank you!
* How many open source projects are out there.
* How open source projects work.
* Open source is actually a big thing.
* Open source/free software doesn’t necessarily mean free as in $0.00, but it means that the source code is freely available to the public & changes can be made.
Things To Improve
* I only learned about the /me command in IRC. Too easy. 🙁
* Too easy. 🙁 Since this was tailored to CS students, the materials should be a little more intermediate.
* Learning the basics of git beforehand!
* run through an example open source project we edit.
* Thanks for holding this workshop. If you could have a project demonstration set up and we can see how it is edited, that would be great.
* Maybe explain how this is important in today’s world. Make this event accessible to everyone on campus.* Question: How has open source been profitable to developers when people are able to download it?* Maybe give some extra info about why open source is good, why we should open source code.
* Sound system for louder speaker.
* Have donuts and coffee at the time mentioned.
* Organization of the event should be better. We had no schedule. We did not know what to expect, when the breaks are, are there breaks? Lunch at 1 pm is too late.
* Want to learn about how people contribute to Python.
* Workflow to using git and GitHub
* Like to learn more about popular tools.
* Suggestion: during the git portion, explain what each command is for more thoroughly.
* OpenHatch: who are you? You never explained! How to get involved in projects other than finding bugs? What was the point of git exercise? It did not make sense. Also without looking at the hint, it was not clear at all.
We highly recommend the sticky note method! We’ve had very little luck getting students to fill out exit surveys. Writing some short, anonymous notes seems like a much better way of learning how your event went and what you can do better. Thanks, Davis attendees!