-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exam Format Idea #246
Comments
I welcome any idea and here are the requirements:
|
Interesting idea
|
Quite an interesting idea I think, but I'm more for a multiple groups scheme (Maybe 4-5 people). From experience when a group is too large usually a few people end up speaking most of the time. I think it could be interesting to meet by groups talking about Open Source stuff. @ploum could participate in these conversations and give grades. Of course, if someone is too shy or intimidated by a group discussion I guess he could still get a one-on-one with the teacher if he wants to. |
It is a very good idea but we have to think about the fact that for shy people it is very difficult to interrupt a conversation to give their idea. For this reason we could give a time limit to each person to speak, but the inconvenience is that the time of the examination would be very long. I think the best solution would be to do small groups. But will we have to work together before the exam, prepare a topic? Another question to raise would be the language in which the exam can be taken, if an Erasmus student for example does not understand the person in front of him it can cause problems. |
Hi everyone,
I would like to suggest an idea for the evaluation of this course. Could we imagine to pass the exam collectively, as a main focus of this course is the community and the collaboration around an open source project?
However, it is not yet clear in my mind how it could be organized practically (with the whole class? in small groups of 5-6?), but if you agree with this general idea, we could define it more precisely later.
The text was updated successfully, but these errors were encountered: