From 4b55778773727a9e6df0a6d59208709ca39be4d9 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Mon, 4 Nov 2019 12:15:26 +0000 Subject: [PATCH 01/27] add brain-dump.md file with inital contents for https://github.com/dwyl/product-roadmap/issues/12 --- brain-dump.md | 85 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 brain-dump.md diff --git a/brain-dump.md b/brain-dump.md new file mode 100644 index 0000000..953fc05 --- /dev/null +++ b/brain-dump.md @@ -0,0 +1,85 @@ +# Brain Dump + +The _first_ step in creating a systematic list of any kind +(_and thus a process for accomplishing the things on the list_) +is to empty one's mind (_specifically working memory_) +of everything that is occupying space and processing power. +This step is often referred to as a brain dump. + +![brain-dump-before-after](https://user-images.githubusercontent.com/194400/68108635-3497be00-fee0-11e9-83f0-6a56ecc99623.jpg "Brain Dump Diagram - Credit: Annie Mueller") + + + +> A brain dump is the act of writing down everything +that is on your mind so that you don't forget it +and to clear your brain to **focus** on **one thing** +instead of being distracted by many things. +https://anniemueller.com/brain-dump-noun-1 + +The first feature we need to build +is a way of capturing all thoughts +on one's mind. +Thankfully this is just a matter +of capturing free text (_using a **`textarea`** element_) +and safely storing it as **`text`** in Postgres. + + + +## Existing (_Incomplete_) Approaches + +There are several tools that can be used for an _initial_ brain dump. +They each have their strengths and weaknesses. + ++ Basic notes app on phone/PC - good for initial capture, useless for follow up. ++ Google Docs - quite good for collaborative capture, useless for next steps. ++ Evernote - powerful yet incomplete, over-complicated and expensive. ++ Trello - trello is great for capturing and OK for categorising +but _useless_ for completion. + + +Our MVP _could_ be achieved +simply by using one of these +_existing_ Apps +and then focussing on the _next_ step +in the + +### Can't We Just Use Sticky Notes? + +Capturing a brain dump +on paper or sticky notes +_can_ feel like a good step in the moment. + +![colorful-sticky-notes](https://user-images.githubusercontent.com/194400/68108210-1ed5c900-fedf-11e9-829b-27f84889e311.jpg) + +But unless those notes +are _immediately_ transferred +to a system and categorised, +most of the information is lost. +We've all been there +in the brain-storming / idea generating +session where everyone shares their thoughts. +Everyone feels great for a few moments, +like _real progress_ has been made, +but in reality walls full of _unorganised_ sticky notes +is where ideas and information go to _die_. +(_sorry if that feels overly dramatic, + but we have felt the frustration + of both **losing** the **individual** sticky notes + and the **entire session** + due to a lack of a systematic process for storing the information_) + +A further downside of sticky notes +is that while they are OK for colocated teams, +they are ***useless*** for **_remote_ collaboration**. + +People often _attempt_ to resolve +this by taking a photo of the board full of sticky notes, +naively thinking that they have "captured" +the information. +While the photo is better than nothing +it creates a false sense of security +because most of the time +the single word on the sticky note +does not capture the whole idea. From d1c63d5a80809e24f260f91433345b234ee83b47 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Mon, 4 Nov 2019 12:17:16 +0000 Subject: [PATCH 02/27] [WiP] start extending "What?" section for #9 > "Capture, Categorise, Complete" --- README.md | 58 +++++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 48 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 3857585..9dcd557 100644 --- a/README.md +++ b/README.md @@ -5,25 +5,25 @@ ## _Why_? -Having a **_clear_ Product Roadmap** is ***essential*** for -ensuring ***everyone*** is ***focussed*** -on working towards the collective ***goal***. +Having a _clear_ **Product Roadmap** is ***essential*** +to help ***everyone*** _focus_ +on our collective **goal**. ### _Public_? From a "commercial" perspective making our Product Roadmap `public` _can_ be viewed as "_**giving away** all our **secrets**_" by those who follow -_traditional_ (_competition-focussed_) "_capitalism_". +_traditional_ (_competition-focussed_) _capitalism_. We don't think we are "_competing_" with anyone, rather we are trying to _serve_ the people using our app and listen to their feedback. If there are other people/teams/companies -trying to solve the same problem as us +trying to solve the same challenge as us and they are _not_ open-sourcing their code and/or guarding the user-feedback, -they are _stuck_ in the _old_ mindset. +they are _stuck_ in a _fixed_ mindset. We believe that _radical_ transparency and openness both in _what_ we do and _how_ we do it @@ -86,12 +86,50 @@ we may end up only having time/resources to solve **one** of these challenges. This list is intended as a guide not a "gospel"._ + Our immediate plan is to build a **_single_ app** that satisfies _several_ human needs -by focussing on "personal effectiveness". -We will build simple UI/UX that helps people -achieve _all_ of their personal goals: Checklists. -GOTO: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) +by focussing on "***personal effectiveness***". + +The App will be a "_hybrid_" +and contain several features +that together help the individual achieve _all_ of their personal goals. +In some cases the features and UX we are building +may appear _familiar_ +because several other people/teams/companies +have _attempted_ to solve this challenge before. + +### USP: What is _different_ about the @dwyl App? + +A valid/relevant **question** is: what makes the @dwyl App unique?
+The **answer** is: _initially_ it may _appear_ that our App +does not have much different +from existing apps that _partially_ solve the personal effectiveness challenge. +The _major_ differences will become apparent in due course: +1. We are an + + +The @dwyl App Will have the following workflow: + +1. ***Capture*** - capture everything that is on your mind in a "brain dump". +2. ***Categorise*** - split out the text + into distinct items and _categorise_ them. + a) What type of info/item is it? + e.g: Todo Item, Reading list item, shopping list, random thought, bucket list? + b) Do you have an _existing_ category/tag for the item or is it **`new`** + c) Add any additional detail you can think of at the time. +3. Complete + a) Add any relevant detail required to complete the task. + e.g: acceptance criteria, deadline, dependencies + b) Delegate if necessary/possible + c) Track progress of the task + d) ***Confirm*** it was completed to expected standard. + e) ***Reflect*** on + + We will build simple UI/UX that helps people + achieve _all_ of their personal goals: + Checklists. + GOTO: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) ## _Who_? From c42a1775b6ff938831558fb711c5f66c8ce00f42 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Tue, 5 Nov 2019 20:46:25 +0000 Subject: [PATCH 03/27] add background detail for "Brain Dump" issue https://github.com/dwyl/product-roadmap/issues/12 --- brain-dump.md | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/brain-dump.md b/brain-dump.md index 953fc05..d38035d 100644 --- a/brain-dump.md +++ b/brain-dump.md @@ -1,11 +1,16 @@ # Brain Dump -The _first_ step in creating a systematic list of any kind -(_and thus a process for accomplishing the things on the list_) -is to empty one's mind (_specifically working memory_) -of everything that is occupying space and processing power. +The **_first_ step** in creating +a **systematic list** of _any_ kind +(_and thus a process for completing the things on the list_) +is to create a means to help people +input _everything_ on their mind. +Emptying one's mind (_specifically working memory_) +of everything that is occupying space and processing power +is essential for allowing a person to focus. This step is often referred to as a brain dump. + ![brain-dump-before-after](https://user-images.githubusercontent.com/194400/68108635-3497be00-fee0-11e9-83f0-6a56ecc99623.jpg "Brain Dump Diagram - Credit: Annie Mueller") Our immediate plan is to build a **_single_ app** that satisfies _several_ human needs -while focussing on "***personal effectiveness***". +while focussing on the theme of "***personal effectiveness***". The App will be a "_hybrid_" and contain several features -that together help the individual achieve _all_ of their personal goals. +that together help the individual +achieve _all_ of their personal goals. In some cases the features and UX we are building may appear _familiar_ because several other people/teams/companies have _attempted_ to solve this challenge before. -If you are well-versed in _existing_ software/apps, -you might recognise features as being "_note input similar to Evernote_", -"_collaborative editing like Google Docs_" or "_offline reading like Pocket_". -In _most_ cases the app(s) that _already_ has/have a certain feature(s) -(_e.g. Photo text OCR. collaborative editing +If you are well-versed in _existing_ software/apps +or curious about UI/Design in general, +you _might_ find certain features familiar. +You may think: +"_note-taking similar to Evernote_", +"_collaborative editing like Google Docs_" +or "_offline reading like Pocket_". +In _most_ cases the app(s) +that _already_ has/have a certain feature(s) +(_e.g. nested note-taking, collaborative editing or offline distraction-free reading_) did not _invent_ the feature, they merely have a memorable _implementation_ of it. Our intention is _never_ to "copy" -the feature/UX of another App. +the feature/UX of another App, +but we will draw inspiration from _many_ sources. @@ -148,10 +160,12 @@ to allow a person to input palintext and save it to a backend as `text`. - +For details, please see: +[`brain-dump.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) Once the text input is working, we will iterate and improve it +in several interesting and innovative ways. Further down the line we will add additional methods @@ -168,16 +182,18 @@ So in order to make progress with them, we will need to _significantly_ leverage the Open Source work of many brilliant people. - +But we are getting ahead of ourselves; +we need to _first_ focus +on creating "MVP" versions +of each step in the workflow. For the _second_ step (***Categorise***), we will need a tagging system that allows people to apply textual labels to items. -We will build simple UI/UX that helps people -achieve _all_ of their personal goals: -Checklists. -GOTO: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) +And finally for the MVP of the _third_ step, +we will build a simply checklist system. +See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) diff --git a/brain-dump.md b/brain-dump.md index d38035d..1c0ea4a 100644 --- a/brain-dump.md +++ b/brain-dump.md @@ -2,12 +2,14 @@ The **_first_ step** in creating a **systematic list** of _any_ kind -(_and thus a process for completing the things on the list_) +(_and thus a process for completing + the items on the list_) is to create a means to help people input _everything_ on their mind. Emptying one's mind (_specifically working memory_) of everything that is occupying space and processing power -is essential for allowing a person to focus. +is _essential_ for allowing a person to focus +on their _one_ most important priority. This step is often referred to as a brain dump. @@ -38,6 +40,7 @@ Figma wireframe: https://www.figma.com/proto/WrpkKGJNYZbeCzMRDVtvQLbC/dwyl-app We can/will evolve this text input to have autocompletion and natural language processing (_to detect the kinds of items being typed_). +First we need to have an ultra-basic MVP working. Please see: https://github.com/dwyl/product-roadmap/issues/12 From 68094b929a7a2c77fca66d779795cd7c51365c66 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Fri, 8 Nov 2019 18:28:21 +0000 Subject: [PATCH 07/27] add link to "Categorise" issue https://github.com/dwyl/product-roadmap/issues/15 --- README.md | 91 +++++++++++++++++++++++++++++-------------------------- 1 file changed, 48 insertions(+), 43 deletions(-) diff --git a/README.md b/README.md index 438f2d2..4e8f010 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,6 @@ trying to solve the same challenge as us and they are _not_ open-sourcing their code and/or guarding the user-feedback, they are _stuck_ in a _fixed_ mindset. - We believe that _radical_ transparency and openness both in _what_ we do and _how_ we do it is _essential_ for succeeding in our _mission_. @@ -52,15 +51,16 @@ is easy to replicate and difficult to differentiate.
However we **hypothesize** that being **open** and **transparent** with our roadmap will foster -a more **collaborative culture**_) +a more **collaborative culture**_. + _**Fear** that members of their **own team** will leave -and "**steal**" their **secrets**; this happens more -[often](http://mashable.com/2017/05/20/uber-vs-google-waymo-self-driving-car-wars-get-nasty) -people realise_. +and "**steal**" their **secrets**;
+this does +[happen](http://mashable.com/2017/05/20/uber-vs-google-waymo-self-driving-car-wars-get-nasty) +but only because the knowledge is **not** shared openly_. -+ _**Uncertainty** about the **future** of their **product/industry**_ -(_committing to a long-range map implies a fixed/inflexible destination_) ++ _**Uncertainty** about the **future** of their **product/industry**._
+_Committing to a long-range map implies a fixed/inflexible destination._ + _**Doubt** in their **own ability** to **deliver** the plan_. @@ -97,39 +97,17 @@ Our immediate plan is to build a **_single_ app** that satisfies _several_ human needs while focussing on the theme of "***personal effectiveness***". -The App will be a "_hybrid_" -and contain several features +The @dwyl App will be a "_hybrid_" +containing several features that together help the individual -achieve _all_ of their personal goals. -In some cases the features and UX we are building -may appear _familiar_ -because several other people/teams/companies -have _attempted_ to solve this challenge before. -If you are well-versed in _existing_ software/apps -or curious about UI/Design in general, -you _might_ find certain features familiar. -You may think: -"_note-taking similar to Evernote_", -"_collaborative editing like Google Docs_" -or "_offline reading like Pocket_". -In _most_ cases the app(s) -that _already_ has/have a certain feature(s) -(_e.g. nested note-taking, collaborative editing - or offline distraction-free reading_) -did not _invent_ the feature, -they merely have a memorable _implementation_ of it. -Our intention is _never_ to "copy" -the feature/UX of another App, -but we will draw inspiration from _many_ sources. - - - +achieve _all_ of their personal goals +through a systematic workflow. The @dwyl App Will have the following basic workflow: ***Capture, Categorise Complete***. 1. ***Capture*** - capture everything that is on your mind in a "brain dump". -2. ***Categorise*** - split out the text +2. ***Categorise*** - split out blocks of text into distinct items and _categorise_ them.
**a)** What type of info/item is it? e.g: Todo Item, Reading list item, shopping list, @@ -159,17 +137,16 @@ we will build an ultra-simple interface to allow a person to input palintext and save it to a backend as `text`. - For details, please see: [`brain-dump.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) Once the text input is working, we will iterate and improve it -in several interesting and innovative ways. - -Further down the line -we will add additional methods -to help people "capture" information: +in several interesting and innovative ways.
+We will add additional methods +to help people "capture" information. +e.g: ++ Linking to external sources of information. + Photo/image uploads + Optical Character Recognition (OCR) + Image/object recognition @@ -181,7 +158,6 @@ that have formed the basis for entire companies. So in order to make progress with them, we will need to _significantly_ leverage the Open Source work of many brilliant people. - But we are getting ahead of ourselves; we need to _first_ focus on creating "MVP" versions @@ -190,9 +166,13 @@ of each step in the workflow. For the _second_ step (***Categorise***), we will need a tagging system that allows people to apply textual labels to items. +The UX for this is still "TBD". +We will need to sketch it out ahead of sprint planning. +See: https://github.com/dwyl/product-roadmap/issues/15 + -And finally for the MVP of the _third_ step, -we will build a simply checklist system. +And finally for the _third_ step, +we will build a simple checklist system. See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) @@ -239,6 +219,31 @@ There shouldn't be any surprises or inconsistent UX (_bugs_), and if there are, they can be reported and fixed _fast_. +#### Familiar UX? + +In some cases the features and UX we are building +may appear _familiar_ +because several other people/teams/companies +have _attempted_ to solve this challenge before. +If you are well-versed in _existing_ software/apps +or curious about UI/Design in general, +you _might_ find certain features familiar. +You may think: +"_note-taking similar to Evernote_", +"_collaborative editing like Google Docs_" +or "_offline reading like Pocket_". +In _most_ cases the app(s) +that _already_ has/have a certain feature(s) +(_e.g. nested note-taking, collaborative editing + or offline distraction-free reading_) +did not _invent_ the feature, +they merely have a memorable _implementation_ of it. +Our intention is _never_ to "copy" +the feature/UX of another App, +but we will draw inspiration from _many_ sources. + + + ## _Who_? Who is this product roadmap intended for? From b54501e1b06ca711392fc8ab3cd41fcccfe65828 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Fri, 8 Nov 2019 18:51:07 +0000 Subject: [PATCH 08/27] rename brain-dump.md to capture.md consistent with the "Workflow" #9 --- brain-dump.md => capture.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) rename brain-dump.md => capture.md (88%) diff --git a/brain-dump.md b/capture.md similarity index 88% rename from brain-dump.md rename to capture.md index 1c0ea4a..67ecc40 100644 --- a/brain-dump.md +++ b/capture.md @@ -1,16 +1,14 @@ -# Brain Dump +# _Capture_ The **_first_ step** in creating -a **systematic list** of _any_ kind -(_and thus a process for completing - the items on the list_) -is to create a means to help people -input _everything_ on their mind. +a **system** of for personal effectiveness +is to help people ***capture*** +_everything_ on their mind. Emptying one's mind (_specifically working memory_) of everything that is occupying space and processing power -is _essential_ for allowing a person to focus -on their _one_ most important priority. -This step is often referred to as a brain dump. +is _essential_ for gaining focus +on the _one_ most important priority. +This step is often referred to as a "brain dump". ![brain-dump-before-after](https://user-images.githubusercontent.com/194400/68108635-3497be00-fee0-11e9-83f0-6a56ecc99623.jpg "Brain Dump Diagram - Credit: Annie Mueller") @@ -35,7 +33,8 @@ of capturing free text (_using a **`textarea`** element_) and safely storing it as **`text`** in Postgres. Figma wireframe: https://www.figma.com/proto/WrpkKGJNYZbeCzMRDVtvQLbC/dwyl-app -![image](https://user-images.githubusercontent.com/194400/68241788-3c05b700-0007-11ea-941b-0fd58962ad03.png) + +![capture-plaintext](https://user-images.githubusercontent.com/194400/68241788-3c05b700-0007-11ea-941b-0fd58962ad03.png) We can/will evolve this text input to have autocompletion and natural language processing @@ -44,7 +43,7 @@ First we need to have an ultra-basic MVP working. Please see: https://github.com/dwyl/product-roadmap/issues/12 -for Acceptance Criteria +for detail and acceptance criteria. ## Existing (_Incomplete_) Tech-based Approaches From 70e565d7ea7d22c63dae6513a424d4ae3b221db9 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Fri, 8 Nov 2019 18:55:52 +0000 Subject: [PATCH 09/27] reduce size of brain dump image #12 --- capture.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/capture.md b/capture.md index 67ecc40..2f793e2 100644 --- a/capture.md +++ b/capture.md @@ -3,15 +3,18 @@ The **_first_ step** in creating a **system** of for personal effectiveness is to help people ***capture*** -_everything_ on their mind. +_everything_ on their mind.
Emptying one's mind (_specifically working memory_) of everything that is occupying space and processing power is _essential_ for gaining focus on the _one_ most important priority. This step is often referred to as a "brain dump". - -![brain-dump-before-after](https://user-images.githubusercontent.com/194400/68108635-3497be00-fee0-11e9-83f0-6a56ecc99623.jpg "Brain Dump Diagram - Credit: Annie Mueller") + From b1a365ab4483dda8c892c57afb2e1a21a8a0e6c3 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Fri, 8 Nov 2019 19:31:49 +0000 Subject: [PATCH 10/27] update "USP" section of README.md for #9 --- README.md | 52 ++++++++++++++++++++++++++++++++++------------------ 1 file changed, 34 insertions(+), 18 deletions(-) diff --git a/README.md b/README.md index 4e8f010..2e4a756 100644 --- a/README.md +++ b/README.md @@ -134,15 +134,16 @@ The @dwyl App Will have the following basic workflow: For the first step (***Capture***), we will build an ultra-simple interface -to allow a person to -input palintext -and save it to a backend as `text`. +to allow people to +input **`palintext`** +and save it to a backend as **`text`**. For details, please see: [`brain-dump.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) Once the text input is working, we will iterate and improve it -in several interesting and innovative ways.
+in several interesting and innovative ways +in response to feedback from people _using_ the MVP.
We will add additional methods to help people "capture" information. e.g: @@ -163,7 +164,7 @@ we need to _first_ focus on creating "MVP" versions of each step in the workflow. -For the _second_ step (***Categorise***), +For the _second_ step, ***Categorise***, we will need a tagging system that allows people to apply textual labels to items. The UX for this is still "TBD". @@ -171,7 +172,7 @@ We will need to sketch it out ahead of sprint planning. See: https://github.com/dwyl/product-roadmap/issues/15 -And finally for the _third_ step, +And finally for the _third_ step, ***Complete***, we will build a simple checklist system. See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md) @@ -181,24 +182,26 @@ See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/check ### USP: What is _different_ about the @dwyl App? -A valid/relevant **question** is: what makes the @dwyl App unique?
+A valid/relevant **question** is: what makes the @dwyl App unique? +i.e. What is our +["unique selling point"](https://en.wikipedia.org/wiki/Unique_selling_proposition)?
The **answer** is: _initially_ it may _appear_ that our App does not have much different from existing apps that _partially_ solve the personal effectiveness challenge. The _major_ differences will become apparent in due course: -1. We are playing an +1. **People Not _Profits_** - We are playing an ["***infinite game***"](https://github.com/dwyl/start-here/issues/190) -to help people -"_maximise their personal effectiveness, creativity and happiness_." +where our _mission_ is to +"_Empower people to maximise effectiveness, creativity and happiness_." See: -[What is dwyl's mission?](https://github.com/dwyl/start-here/blob/master/mission.md#what-is-dwyls-mission)
+[What is dwyl's mission?](https://github.com/dwyl/start-here/blob/master/mission.md#what-is-dwyls-mission) We will not _rest_ until we have created a system/app that is _universally accessible_ to every human being that allows _everyone_ a fair opportunity to live their best life. -Our goal is to _cooperate_ with many people/organisations +We will _cooperate_ with _many_ people/organisations to build a comprehensive solution that _anyone_ can use. -2. All of our code will _always_ be ***Open Source***. -That means anyone is free to modify/extend/improve it. +2. ***Open Source*** - All of our code will _always_ be ***Open Source***. +That means anyone can modify/extend/improve it. And if people feel we are not doing a good enough job of stewarding the App/community, they can _tell_ us! Of the _many_ "productivity" apps out there, @@ -209,12 +212,25 @@ Your data is bound by their "terms and conditions" i.e. Google_) and you are a _hostage_ to their whims. If they decide to have a UI re-write -that _completely_ changes how you interact with the App, +that +[_completely_ changes](https://github.com/dwyl/product-roadmap/issues/14) +how you interact with the App, you have _no control_ and are _forced_ to use the "new version"; their way or the highway. -2. **Progressive UI** - -1. We are building a robust and reliable app with a focus end-to-end testing -to ensure a consistent UX. +We are going to _eliminate forced updates_ +by implementing a UX/UI innovation we call Progressive UI. +3. **Progressive UX/UI** - the UX/UI for _each_ person using the app, +will be _personalised_ to the individual +based on the features they (_most_) _use_. +If the person does not _use_ a particular function, they won't _see_ it. +> Note: This is might not feel relevant during "MVP", +but it will be an _amazing_ feature once our app has _lots_ of functionality. +4. **Best-in-Class Engineering Practices** - +Focus on high quality software product +with best-in-class engineering practices. +We are building a robust and reliable app +with a focus end-to-end testing to ensure a consistent UX +on as many devices as possible. There shouldn't be any surprises or inconsistent UX (_bugs_), and if there are, they can be reported and fixed _fast_. From e03f0b65c3255321ebc8dd1e6ed69c69529c5945 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Fri, 8 Nov 2019 19:44:12 +0000 Subject: [PATCH 11/27] add "How you can help" section to README.md --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 2e4a756..58dc4e7 100644 --- a/README.md +++ b/README.md @@ -302,6 +302,23 @@ This list _will_ evolve over time.
We will insert links to specific features and check them off this list as we go. +If you want to get involved in helping us with the App, +there are 4 ways to help: + +1. **Use** the **_Beta_ App**! +`[insert app link here!]` +2. Give us ***feedback*** on the **_existing_ UX** +`[insert feedback link here!]` +3. **Read** the +[issues](https://github.com/dwyl/time/issues?q=label%3A%22help+wanted%22+is%3Aissue+is%3Aopen) +and help us answer questions if you can. +4. Write some **`code`**! +See: https://github.com/dwyl/technology-stack + +## Brain Dump of Features + +The following list needs to be _organised_: + + [ ] Security First - ensuring the security of both the people using the Application(s) and the (_personal_) Data in the system is a ["hygiene factor"](https://en.wikipedia.org/wiki/Two-factor_theory) From 3f7cd7a528d44aeb6c736bee93c13576c740cfe0 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Sat, 9 Nov 2019 21:32:42 +0000 Subject: [PATCH 12/27] simplify "How?" section #16 --- README.md | 42 +++++++++++++++++++++++++++++++++++------- 1 file changed, 35 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 58dc4e7..c84226f 100644 --- a/README.md +++ b/README.md @@ -298,10 +298,6 @@ which **features** get built **next**_! ## How? -This list _will_ evolve over time.
-We will insert links to specific features -and check them off this list as we go. - If you want to get involved in helping us with the App, there are 4 ways to help: @@ -315,6 +311,38 @@ and help us answer questions if you can. 4. Write some **`code`**! See: https://github.com/dwyl/technology-stack + +### Tech & Features Roadmap + + +This list _will_ evolve over time.
+We will insert links to specific features +and check them off this list as we go. + +#### MVP Basic Workflow + ++ [ ] Mobile First UI/UX to **Capture** **`plaintex`** ++ [ ] Save **`plaintex`** data to Phoenix backend ++ [ ] Simple UX to **Categorise** (Transform) +the **`plaintex`** into actionable items.
+UI/UX **`help wanted`**: https://github.com/dwyl/product-roadmap/issues/15 ++ [ ] Start working on task (_start timer_) ++ [ ] Check a task off as done. + +After the MVP workflow is complete, +we will hold a sprint demo to showcase the state of the App. +The sprint demo will be recorded on our Zoom call. +Following the sprint demo call +we will do a backlog grooming session to discuss the features/ideas list: + +#### Offline Support + ++ [ ] Create Progressive Web App ++ [ ] Save data on device if offline. + + + + ## Further Reading From a2d16a92db9ab7591d592f8b9f171014de85c773 Mon Sep 17 00:00:00 2001 From: nelsonic Date: Sat, 9 Nov 2019 21:43:11 +0000 Subject: [PATCH 13/27] add enough to product roadmap to get started working on the app! #16 --- README.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c84226f..8ce70a8 100644 --- a/README.md +++ b/README.md @@ -326,7 +326,8 @@ and check them off this list as we go. + [ ] Simple UX to **Categorise** (Transform) the **`plaintex`** into actionable items.
UI/UX **`help wanted`**: https://github.com/dwyl/product-roadmap/issues/15 -+ [ ] Start working on task (_start timer_) ++ [ ] Start working on task (_start timer for item_) +see: https://github.com/nelsonic/time-mvp-phoenix#create-schemas + [ ] Check a task off as done. After the MVP workflow is complete, @@ -337,9 +338,22 @@ we will do a backlog grooming session to discuss the features/ideas list: #### Offline Support -+ [ ] Create Progressive Web App ++ [ ] Create Progressive Web App using Elm. +see: + [ ] Save data on device if offline. +#### Image Capture + ++ [ ] Capture (_upload_) images from mobile. ++ [ ] Categorise (_tag_) the images for findability. + +#### Authentication + ++ [ ] Create accounts to allow people to own their content/items. ++ [ ] Authenticate with GitHub OAuth + + [ ] Associate person record with GitHub username + token. ++ [ ] Associate **`items`** with **`person`** +