From b1c90991b60e97de08cec7a4cfabf2e627f9819c Mon Sep 17 00:00:00 2001
From: Tim Ryan <id@timryan.org>
Date: Sun, 11 Feb 2018 16:13:51 -0500
Subject: [PATCH 1/2] Created 2018-02-12.md

---
 meetings/2018-02-12.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 meetings/2018-02-12.md

diff --git a/meetings/2018-02-12.md b/meetings/2018-02-12.md
new file mode 100644
index 0000000..f843e31
--- /dev/null
+++ b/meetings/2018-02-12.md
@@ -0,0 +1,18 @@
+
+# Meeting DATE
+
+**Moderator:** NAME  
+**Notetaker:** NAME  
+**Attending:** NAMES  
+
+## Agenda
+
+* ...
+
+## Notes
+
+* ...
+
+## Action items
+
+* ...

From 3eb261e89f9113ad54b39eb3082dd7ef643c8a75 Mon Sep 17 00:00:00 2001
From: Tim Ryan <id@timryan.org>
Date: Mon, 12 Feb 2018 15:30:14 -0500
Subject: [PATCH 2/2] Update 2018-02-12.md

---
 meetings/2018-02-12.md | 82 ++++++++++++++++++++++++++++++++++++++----
 1 file changed, 75 insertions(+), 7 deletions(-)

diff --git a/meetings/2018-02-12.md b/meetings/2018-02-12.md
index f843e31..0dfb3da 100644
--- a/meetings/2018-02-12.md
+++ b/meetings/2018-02-12.md
@@ -1,18 +1,86 @@
 
-# Meeting DATE
+# Meeting 2018-02-12
 
-**Moderator:** NAME  
-**Notetaker:** NAME  
-**Attending:** NAMES  
+**Moderator:** @frijol  
+**Notetaker:** @tcr  
+**Attending:** @hipsterbrown  
 
 ## Agenda
 
-* ...
+* [ ] Last week's action items
+* [ ] Can we set dates for Tesselcamp?
+* [ ] CodeTriage– any discussion? Please read https://github.com/tessel/t2-cli/pull/1406
+* [ ] Recap from Sunday work session
+* [ ] Infrastructure issues (Slack & Forums)– how do we fix so it's not a problem in the future?
+* [ ] Upgrading Node version
+* [ ] Status of static website for tessel.io
+* [ ] Re-label contribution-starter? See https://github.com/tessel/project/issues/371
+* [ ] Check in on current project priorities
 
 ## Notes
 
-* ...
+Emailing Boaz
+
+* Emailed Boaz and would like to do a quarterly meeting with Boaz
+* Hopefully can he can join a weekly meeting
+* Kelsey's gone stating March 5th, so 
+
+Tim work yesterday
+
+* Domains updated with `dokku network:rebuildall`
+* Forums instance not ready yet
+
+Tesselcamp
+
+* Setup a time during the week
+* Should we send out open invitation for others to the meetup?
+
+CodeTriage
+
+* Open issues for open source projects, cleverly reduces the amount if a person isn't receptive
+* You get on, on the waiting list, and we just got nominated!
+* Open PR on this—should we accept it?
+* @frijol spent her Sunday on triaging issues on the project repo and more
+* t2-cli repo has a number of open crash reports (legit vs. user error)
+* Crash reports could be good beginner issues
+* Also #371
+
+Sunday work session:
+
+* @tcr Domains working again
+* @frijol Cleanup of issues
+* @hipsterbrown Worked on now.sh deployment for tessel.io with autodeployment with now.tessel.io
+
+now.tessel.io
+* CNAMEd to the appropriate domain
+* @tcr: Will SSL continue to work?
+* Just need team@tessel.io account
+* Can use now desktop app or CLI or look at logs
+* Do we want the blog separate from the website?
+
+Static website
+* On deck for @tcr and toward our April goal
+
+Auto-compiler
+* Francis is working on this: see #ops channel
+* Paying $30 a month for our compiler process (Fargate requires a private subnet)
+* Should run in the background making builds, but also we want an on-demand endpoint
+* ECS t2-compiler task would take up more resources than we expected
+* Use SAM should be more serverless
 
 ## Action items
 
-* ...
+* @tcr Monitor dokku subdomains
+* @tcr Instantiate a forums instance
+* @tcr See if @rwaldron is available that date for TesselCamp
+* @frijol See if Jon/Jia are interested in attending TesselCamp
+* @hipsterbrown Finish autodeployment of now.sh and write up instructions
+* @frijol Retrieve all our blog posts from tumblr and put them into a blog repo (or repurpose this-week-in-tessel)
+* @frijol Do #371 for `help wanted` and `good first issue`
+
+Punt:
+* [ ] t2-cli crash reports discussion 
+* [ ] RailsGirls
+* [ ] Infrastructure issues (Slack & Forums)– how do we fix so it's not a problem in the future?
+* [ ] Check in on current project priorities
+* [ ] Upgrading Node version