current circlemarker	zeplin circlemarker

as a:
user

when I:
select a tree

I want to

We're using console.log calls to debug server-side code. These calls should be made via a logging system that allows the developer to specify the log level (debug, error, warn, log, etc). We should be able to specify to our app via a config file which levels to output and where to stream output (file, stdout, etc)

This is somewhat dependent on determining the brand tone (see Issue #102).

So far our list of emails to draft is as follows:

Candidate Invitations:

• Initial Contact
• Invitation Follow-up
• Last Chance to Participate

Recording Responses:

• Thank You for Recording
• Notification of Opponent Participation

Please see the relevant file in the “[Email Templ

Overview

We need to update the description for the HfLA Website team on the project card and project page to reflect our newest mission and objectives.

Action Items

Product

• Sign off on copy (recommended copy below)

Development

• Update the copy reflected on site (both on project card and project page)

Current copy:

_The hackforla.org website is our organizatio

Overview

We need to update our team roster in order to update:

1. the Hack for LA Project Overview --> MVP
2. the "Project Background" static page on the FOLA site --> V2

Action Items

• Compile a list of team members (past & present) in a new Google Sheet or in framework doc created by Bonnie (if already created)
• Save

Overview

In order to allow for internal hand off between LADOT users, we should have a walk through going over setting up admin roles, as well as anything else unclear

Action Items

• Determine best way to write walk through
• possibly PDF with screenshots
• Write walkthrough
• Share with LADOT

Resources/Instructions

Overview

Meeting time is currently 2PM Saturdays, however Yamato and Henry Marks cannot make it.

Action Items

• Discuss new meeting times and come to consensus about team availability
• Slack Bonnie to get her weekend availability

Please comment progress on this issue

Overview

The majority of VRMS users are returning, so the returning user button should be above the new user button

Acceptance criteria

• All functionality maintained
• Invert position of buttons

Background

<img width="609" alt="Screen Shot 2020-08-31 at 7 24 33 PM" src="https://user-images.githubusercontent.com/19891365/91787884-e70be080-ebd8-11ea-92ac-6cb565c328a9

Overview

Reserve the name "NotToday: Self-Defense Against Suicidal Thoughts" or closest permissible variant in iOS and Android stores.

Action Items

Research how to do this.

Resources/Instructions

• App name reservation in app store through itunes connect
• [Two differe

Overview

Revisit Spacial Joint by Hour of a day to Get Street Sweeping Regulations

Action Items

Try below but not limited to:

• investigate how lines are joined?
• explore different ways of joining?
• using hour of a day as segment
• research other approaches

Resources/Instructions

• consult Regan to look into

Overview

We need to build each part of the website and connect it with the menu (header and footer). This issue is for the donation page

Action Items

• Build the Donate page
• Integrate it into the footer and link it to the Radical Collaboration drop down menu item in header.
• Put screen shots in issue to show completion. and @ message experimentinhonesty
• show th

Overview

We need to have a working READme file or WIKI to easily on-board new team members.

Action Items

• Add the following information as a comments to this issue:
  • Identify what information needs to be collected.
  • Identify who holds each piece of information.
  • Collect information.

Resources/Instructions

[Current Readme](https://github.com/hack

Overview

Add all team members to roster, G-drive & Github

Action Items

Update the list:

• Roster/Roles
• G-drive
• Github

Resources/Instructions

Roster & Roles
Google Drive access
[Git

Overview

Provide collateral for the OpenSourceAutomations.org website

Action Items

• Gather items
  • 600 x 400 image
    • Alt image text
  • Name of automation
  • A blurb about the automation
  • Links (github, slack channel url, Testing Site, Live Site, etc.)
  • Healthy project files (see resources for instructions)
    • Readme.md