Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created 2018-02-12.md #373

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
82 changes: 75 additions & 7 deletions meetings/2018-02-12.md
Original file line number Diff line number Diff line change
@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: starting


Tim work yesterday

* Domains updated with `dokku network:rebuildall`
* Forums instance not ready yet

Tesselcamp

* Setup a time during the week
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: set up

* 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