From c17bcf3c402112d1c81da28567b7c40fd1addb22 Mon Sep 17 00:00:00 2001
From: Oskar Thoren <ot@oskarthoren.com>
Date: Wed, 28 Mar 2018 10:29:46 +0800
Subject: [PATCH] Remove noisy comments

---
 83-energy-efficient.md | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/83-energy-efficient.md b/83-energy-efficient.md
index 48d47a9..165a4ed 100644
--- a/83-energy-efficient.md
+++ b/83-energy-efficient.md
@@ -1,6 +1,3 @@
-<!-- Please Review https://docs.google.com/document/d/1CaFM2ZXGOKf05_LXMPJeNNy5qJOdAq91EF2Gn2QUBFI/edit# for more details -->
-<!-- in PR the document should be named as`DEV#1-title.md` -->
-
 ## Preamble
 
     Idea: 83
@@ -14,18 +11,9 @@ A specific issue about the energy efficiency of different parts of Status (`stat
 
 
 ## Swarm Participants
-<!-- Each contributor pledges to the idea with their FOCUS value. (hours per week) -->
-<!-- Here all roles in swarm are defined and filled, one of the contributors should responsibility of the Idea as Lead. -->
-
-<!-- Testing/Evaluation support role is also mandatory to check in on specified Goal dates or earlier. -->
-
-<!-- Lead Contributor is the Owner of the Idea. If required, they can get support from a PM, but should be responsible for end to end execution of the Idea. This includes ensuring appropriate resources are allocated, setting realistic timelines and milestones, and any post-launch metrics or bug fixes that are attributed to the Idea -->
-<!-- A swarm requires at minimum 3 contributors and 1 evaluator/tester -->
-<!-- 'Contributor' should be replaced with a descriptive role type. -->
 - Lead Contributor: @mandrigin (~25h)
 - Contributor (Go): @feuGeneA 
 - Contributor (QA): @lukaszfryc (~10h/week)
-<!-- - Contributor: @username -->
 
 ## Product Overview
 Energy consumption is a crucial part of the mobile experience, and even though it is related to performance, it is worth having a separate.
@@ -63,7 +51,6 @@ MVP2 (development): Create a low-power background mode for status-go (date: *Mar
 
 
 ## Supporting Role Communication
-<!-- Once Requirements and Goals are fleshed out, then it should be communicated to supporting organelles if required -->
 
 ## Useful Links
 https://github.com/dgryski/go-perfbook