Closed tarebyte closed 9 years ago
So - I'm not longer using it since I've left academics, but I can tell you how I used the original version when I wrote it.
2 scenarios - students work in teams and students work individually. Really those are the same things. For students working individual, they are on a team by themselves, and the team has the same name as the username for the student.
I had access to an on-site github enterprise, so I didn't have any quota issues to worry about, that was nice.
1) bootstrap course - create organization, create teams
2) create a private (to me) repository for an assignment, populate with starter files
3) create a repository for each team completing the assignment.
4) From the local clone of my starter repository, push the files to each team's repo
5) When done - run a clone of all the repositories.
I've been monitoring the change made since then, but that was the basic workflow that I used. It worked well in CS 2 (individual assignments) and a graduate software architecture course I taught where they worked in teams.
Thanks @mikehelmick!
I want to find some related materials for I am starting to use it in class.
Can you give an example of materials you would like to see?
@tarebyte Like how could teachers make reasonable evaluation, especially when facing collaborative situations? And also, how could a teacher makes an effective collaborative programme, and what is the good workflow?
@eduOS That sounds like content that could possibly be added to https://education.github.com/guide. Or a discussion that could be started in https://github.com/education/teachers.
To me, your question doesn't really relate to this particular issue.
If you raise an issue in education/teachers or in education/guide, I'd be more than happy to discuss ways of putting up new information that could help teachers.
OK. Thank you very much for your suggestion.
@eduOS For team assignments, the commit history and contribute graphs in the github you are outstanding in informing you as to who did what. It requires some clicking around, but the data is great.
@mikehelmick Yeah, thank you very much for your time.
I don't think that the number of commits, the only consideration of both commit history and contribute graphs, is the all-sided way to show the teacher who did what.
@EduOS The "blame" function in GitHub can show you who did what.
@terabyte and others; I too agree that we could provide some pedagogical resources somewhere in education.github.com. I'm not sure exactly what it would look like, but I am interested in contributing my experience as a high school teacher.
@kelleydv Awesome! I am majoring in education technology, hoping to make GitHub, an awesome tool, to be used in classroom in an efficient way.
I plan on using the private repos / "Sandboxing" approach in my intro Java programming course.
For teachers_pet, I had a rough time getting ruby 1.9.3 working on Windows 8.1 x64, more success with Ruby 2.1.5, FWIW.
I was getting certificate errors, which I fixed by following: https://gist.github.com/fnichol/867550
Once I got through that problem, its been good.
Any ideas / advice for how to give feedback to the student? I was planning on simply commenting their code, committing it as "graded" and pushing it back to their repository. That way they can see my comments highlighted in the diffs. Is there a better way?
I plan on using Sandboxing for a "C++ for Java Programmers" sophomore-level university course. I am still getting things set up, but I had the same difficulty with SSL certificate errors that @mafudge had. His advice solved my issue.
@mafudge I either comment on their code, or I open an issue on the repository with feedback for them so that it's an open conversation if they have questions.
Hi Everyone,
I'm trying to get a more in depth understanding of how people are using this gem, what their pain points are, or if they aren't using the gem anymore what caused them to.
If you are interested in talking to email me at github@marktareshawty.com and we can work out a time, or feel free to comment on this issue!
Thanks!