from the that-may-be-difficult dept
At the end of the post, I noted that I was a bit surprised that a separate issue hadn't come up. The entire discussion had been about school policy, and not about copyright. Yet, many schools these days now try to claim the copyright on code written by students. Perhaps I spoke too soon.
Kyle alerts us that, with the new school year beginning, the same professor has added a new copyright policy to his assignments. Thankfully, it doesn't sound like he's claiming copyright over the code, but over the assignments themselves. You can see the policy for yourself, where it states:
The homework assignments in this class are copyrighted by Dr. Beeson, including the names of the assignments, and the names of all the required classes and methods, all the examples that are posted with the assignment, and the problem descriptions and programming hints that are posted. Your solutions are your own, but if you want to post them publicly, you must change the names of the classes and methods, and you cannot post the problem descriptions. This should enable you to show your work to a prospective employer, and possibly allow me to re-use the assignments without future students being able to Google your solutions.Now, to give Dr. Beeson credit, he appears to be trying to come up with a reasonable compromise here, allowing Kyle to do the sorts of things he wanted to do, without making it so that he would have to come up with new assignments every semester. So, I can respect that. But, I'm not sure that he's got a legal right for all of that. It's not entirely clear if the names of the assignments are enough "creative expression" to warrant a copyright. Ditto for the names of required classes and methods. Even if they were, I would imagine any student would have a pretty strong fair use argument in reposting them.
I think it's fair for Dr. Beeson to request students not post info that makes it so easy for future students to Google the answers from former students (though, let's face it, students will always find ways to get similar info anyway), but claiming it's due to copyright seems like a stretch.