From be31fc382ec315c6e69a66959cd1e410983c8395 Mon Sep 17 00:00:00 2001 From: Stephen O'Neill Date: Wed, 15 Nov 2017 08:32:57 +0000 Subject: [PATCH 1/2] Add notes about the deliverable format. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index ffcb86e..b52ec13 100644 --- a/README.md +++ b/README.md @@ -19,19 +19,19 @@ We leave it to you to decide how to transmit the data between the client and the You should use engineering best practices where appropriate. Principles we value include: security, performance, readability, testability, scalability, simplicity. You should also aim to achieve a clean separation of concerns between components of your solution; using the MVC pattern, for example. +## The Markup + +An example of the initial HTML form is [provided in this repository](markup.html). + ## The Deliverable -* A bundled/archived repository showing your commit history or a link to an accessible private repository with your work in (Github can host private repositories at a cost; there is no charge for doing so with Bitbucket). You could fork this repo in git, but any VCS is fine. Git example for sending us a standalone bundle: +* A git bundled repository showing your commit history: git bundle create .bundle --all --branches * A covering note explaining the technology choices you have made. * Any instructions required to run your solution and tests in a Linux environment. -## The Markup - -An example of the initial HTML form is [provided in this repository](markup.html). - ## Assessment Policy We consider all candidates equally, fairly and without bias. To that end, we ask that you do not leave any personally identifying information in your submission (such as your name within an author field or file, or in use as test data). We run all VCS-based submissions through an anonymiser before assessment, so that there is no identifying information in the commit history, but this will only remove references in the committing author and email address, not deep in the code submitted. From 0234ecf06c57afcc277bb9a3406cae432547f08b Mon Sep 17 00:00:00 2001 From: Stephen O'Neill Date: Wed, 15 Nov 2017 11:28:02 +0000 Subject: [PATCH 2/2] Standardized the deliverable / assessment policy to require a README, git bundle & anonymizable submission for equality & diversity --- README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index b52ec13..320ecf9 100644 --- a/README.md +++ b/README.md @@ -19,19 +19,21 @@ We leave it to you to decide how to transmit the data between the client and the You should use engineering best practices where appropriate. Principles we value include: security, performance, readability, testability, scalability, simplicity. You should also aim to achieve a clean separation of concerns between components of your solution; using the MVC pattern, for example. -## The Markup +### The Markup An example of the initial HTML form is [provided in this repository](markup.html). ## The Deliverable -* A git bundled repository showing your commit history: +Replace the contents of this README.md with: - git bundle create .bundle --all --branches + 1. A covering note explaining the technology choices you have made. + 1. Any instructions required to run your solution and tests in a Linux environment. -* A covering note explaining the technology choices you have made. -* Any instructions required to run your solution and tests in a Linux environment. +Email as an attachment or a link the git bundled repository showing your commit history with all your commits on the master branch: -## Assessment Policy + git bundle create .bundle --all --branches + +## Equality & Diversity We consider all candidates equally, fairly and without bias. To that end, we ask that you do not leave any personally identifying information in your submission (such as your name within an author field or file, or in use as test data). We run all VCS-based submissions through an anonymiser before assessment, so that there is no identifying information in the commit history, but this will only remove references in the committing author and email address, not deep in the code submitted.