From 5221eeaa54e5e23445763586ca9496f36e1f94ba Mon Sep 17 00:00:00 2001
From: Tails developers <amnesia@boum.org>
Date: Sat, 20 Jul 2013 10:16:09 +0200
Subject: [PATCH] Criteria for easy tasks

---
 .../working_together/criteria_for_easy_tasks.mdwn  | 87 ++++++++++++++++++++++
 1 file changed, 87 insertions(+)
 create mode 100644 wiki/src/contribute/working_together/criteria_for_easy_tasks.mdwn

diff --git a/wiki/src/contribute/working_together/criteria_for_easy_tasks.mdwn b/wiki/src/contribute/working_together/criteria_for_easy_tasks.mdwn
new file mode 100644
index 000000000..1bacd8c58
--- /dev/null
+++ b/wiki/src/contribute/working_together/criteria_for_easy_tasks.mdwn
@@ -0,0 +1,87 @@
+[[!meta title="Criteria for easy tasks"]]
+
+We think that having issues flagged as *easy* on Redmine is a great tool
+to help new contributors getting into Tails. Here are a few criteria to
+help us determine which issues to put in this category.
+
+We want to allow people with very different skills to contribute to
+Tails for the first time. Programmers, web designers, documentation writers, or
+translators should be able to find tasks that they can complete without
+having to acquire a deep knowledge of Tails or to learn how to use tools
+that are outside of their field of expertise.
+
+General
+=======
+
+- Not easy:
+  - Has subtasks or is blocked by other issues.
+  - Needs to be split to be actionable.
+
+Audit & Research
+================
+
+- Not easy:
+  - Interacts with several subsystems of Tails.
+
+Code
+====
+
+- Easy:
+  - Write a patch that doesn't need to rebuild Tails.
+- Not easy:
+  - The first solution that comes to your mind is not the right one.
+  - Interact with several subsystems of Tails.
+  - Rework on a first attempt to code that failed because things were
+    more difficult that they seemed at first glance.
+  - Have specific hardware for the task.
+
+Discuss
+=======
+
+- Not applicable.
+
+Documentation
+=============
+
+- Easy:
+  - Write user documentation.
+- Not easy:
+  - Use Git or send patches.
+
+Promote
+=======
+
+- Easy:
+  - Explain how to use Tails as described in the documentation.
+- Not easy:
+  - Explain how Tails work based on the design document.
+  - Speak on behalf of Tails.
+
+Sysadmin
+========
+
+- Not easy:
+  - Have privileges on Tails infrastructure.
+- Easy:
+  - Work that can be tested locally, for example using a virtual
+    machine.
+
+Test
+====
+
+- Easy:
+  - Test behaviour of Tails using the GUI.
+- Not easy:
+  - Code or build a dedicated testing infrastructure.
+
+Translate & Website
+===================
+
+- Not easy:
+  - Use Git or send patches.
+
+Wait & Communicate
+==================
+
+- Easy:
+  - Send nice emails to ask for updates.
-- 
2.11.4.GIT