This repository is designed to assist students of Royal Holloway Computer Science Department who wish to publish, open source or otherwise distribute work they have completed as part of their course. It is designed to be read alongside the Student Handbook and the College Regulations on Academic Misconduct.
Students put a lot of work into designing creative assignment submissions and producing interesting and original work. When looking to further their academic career or apply for jobs, it is important they are able to showcase the work they have done. Equally, it is important for the Department and College to protect the integrity of the degree and to ensure a level playing field for all.
The College does not claim ownership of, or any rights to non-assesed work product produced by the student as part of their degree. The Student retains full ownership and rights to the work they produce outside of assignments.
This repository contains several template licences, which are explained later on. The README includes general advice and best practices to avoid allegations of Academic Misconduct. It is important to note that information contained within this repository is unofficial and provides no guarantee against and should not be used as a defence for allegations of Academic Misconduct.
- Do not publish assesed work unless this has been agreed with the department.
- If publishing work connected to, but not directly associated with, assesments you should only publish after grades for that asssesment have been returned.
- Ensure you do not publish code skeletons, documentation or any material provided directly to you by the course leader. This remains the Copyright of the College and a licence to reproduce it should be sort if you wish to do so.
- Always publish work with a specific licence. Although no licence technically indicates no rights to the reader it is better to state this explicitly for the avoidence of doubt.
- If you are publishing "solutions" to an assignment or labsheet, it is adviseable to include the below disclaimer.
- When publishing group work, you must have the consent of all parties and they should be named on the licence.
- If you use Git remotes as a back up tool, ensure you understand whether the remote is set as public or private.
The following is a general disclaimer that may be used appended to standard licences for use on repositories that contain work produced as part of a Royal Holloway degree. Please see the Licencing Conditions below.
The Software was produced in conjunction with a degree at Royal Holloway, University of London. Current students are reminded that although referenced use of external materials is permitted in assessed coursework submissions, this should be done in a way that:
a) obeys the conditions of the licence
b) attributes the Copyright Holder and source
c) does not misrepresent ownership of The Software
Submission of work that has been plagiarised or otherwise misrepresented is treated as Academic Misconduct. Submissions are routinely checked for this.
Several standard open source licences are included as part of the repository, and, for your convenience they include the above disclaimer. Please see the Licencing Conditions below.
You may reproduce the disclaimer and any template licences included in the repository without carrying forward the full repository licence. You must include the following in the README of any repository that uses either of the aforementioned:
This repository carries a Royal Holloway, University of London specific licence. Please see here for more information.
A link back to this repository should be included.