🚀 go-pugleaf

In article <8114@ecs.soton.ac.uk> tjc@ecs.soton.ac.uk (Tim Chown) writes:
>error of some sort.  It's quite rare but as our postmaster I
>redirect failed headers to me so I can attempt to prevent
>
>Anyway, as a result I saw a message between two students that
>was clearly showing them to be cheating in an assigment by exchanging
>pieces of code.  I only saw the subject line, but it was enough.
>Do you turn a blind eye?  Do you let the offenders gain an unfair

 If something like that happens here, I send a message to the author of the
message, reminding him of his responsibilities.  I otherwise ignore it as
information I use.

 Users of this system are warned that email is not 100% private, and that
in particular the Postmaster may see all failed mail.

>advantage?  It's not at all clear cut.  We have correlation software
>written as the basis as a PhD that checks for collaboration on the
>structure of code, but when you have the extra "proof" should you

  The real question here, I believe, is not related to email.  It is the
question of whether collaboration should be considered cheating.  This is
probably the wrong news group.  We are supposedly preparing students to be
able to function in a real programming job where the ability to successfully
collaborate with colleagues is an essential requirement of the position.

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940