Technology Team Charter

Values

• Openness – When possible, we will choose the solution that allows the most people to engage meaningfully with the project. (Example: private vs public github: unless it’s not feasible, we would try to do a public repo and accept pull requests).

• Engagement – When possible, we will try to fork off tasks that other people could do, and only if we can’t find someone to do it, will we take on the task ourselves. (Example: If we need to make a tweak to the site, we could create a good Github issue, announce it in #technology, then if nobody has claimed it in 30 min we should just do it).

• Endurance – While each of us are committing to work on this for the foreseeable future, when possible we will encourage each other to take breaks, be healthy, and enjoy life. This is where volunteer engagement will pay off. We do not want to burn out and shut down the site in 2019.

• Discussion – When possible, we will speak up when we’re offended, when we have a need that isn’t being met, or when something is wrong. This is not an excuse for rudeness.

Where to find us

• On Slack in #technology, #hosting, #python, #docs, #front-end, #database
• On Hangout at https://hangouts.google.com/hangouts/_/ineffable.co.za/mltshp
• In our code at https://github.com/MLTSHP or https://gitlab.com/MLTSHP

Who we are

The people listed below are committed to spending their free time working on mltshp for the foreseeable future while striving to respect the values listed above. We believe that we have the time as well as the enduring interest to do this for years.

Leadership

First Contact –

“I need a technical thing, how do I submit an issue?”

• Chuck Lauer Vose / @vosechu / vosechu[at]gmail.com
• Matthew McLeod / @vai / m[at]wurk.io

Planning, resource allocation, technical tie-breaker –

• Patrick Thomson / @importantshock / patrick.thomson[at]reconfigure.io

Design, assets, swag –

• Al Rotches / @heyitsal / mltshp[at]aldesigns.com

Front-end –

• Scott Vandehey / @spaceninja / scott[at]spaceninja.com

Steering committee rep., Legal & Money concerns –

• Jessamyn West / @jessamyn

Community Moderators / Helpers –

• Angela Woosley / @tweedlydo / tweedlydo[at]gmail.com
• The Incomparable / @tonyb

Team members and specialties:

• Chuck Lauer Vose / @vosechu / vosechu[at]gmail.com —
  Web dev (Ruby), Performance optimizations, HTML5/CSS3, JS
• Taylor Simpson ^{[no relation]} / @ilama / tjsimpson[at]gmail.com —
  Web dev (full stack)
• Jason Simpson ^{[no relation]} / @jxyzn/@xiojason —
  mlkshk.jx.io, image & video transcoding, perl
• Shane Doucette @shaniber / shaniber[at]gmail.com —
  System Administration / Server Wizardry - AWS / Digitalocean, Linux, Apache, Nginx, Varnish, MySQL, scripting, perl Developer support - Vagrant, Virtualbox, git, capistrano, Jenkins / Travis / CI. Technical user communication / documentation.
• Travis Hardiman / @travis [twitter + slack + mlkshk] / @dieseltravis [github] —
  Web dev (.Net, static), CSS, HTML, javascript, git, SQL
• Jim Ashman @jim-ashman (slack) - (Web Dev, PM, biz/process analysis). backend: php, mysql, frontend: css/html/javascript.
• Chris Cotter / @soupkills
• Jeff Remer / @jeffremer —
  iOS/Objective-C, frontend web, a little backend web
• Bill Turner / @billturner —
  web dev (ruby, angular, react), backend (postgres, mysql, linux - aws, digitalocean, etc)
• Matthew McLeod / @vai / m[at]wurk.io —
  Systems architect, bespoke dev, web anything, and apps; desktop or otherwise, megacorp consulting etc.
• Patrick Thomson / @importantshock / patrick.thomson[at]reconfigure.io —
  web dev (Ruby, Haskell, Python), iOS (ObjC), git, PostgreSQL, backend (Linux, BSD, Solaris)
• Ziad Wakim / @motdiem / ziad.wakim[at]gmail.com —
  server side stuff, configuration, documentation, bug finding, fixing and “fixing”, iOS testing
• Bill Connell / @wjcstp —
  HTML/CSS, some PHP and SQL, Linux, also happy to do writing/editing, documentation, communications, testing
• Jason Pettis / @jazon —
  HTML, SQL and some MySQL, css/html, systems admin (mostly Microsoft Servers), happy to help with writing, documentation, testing, general admin duties
• Jim Jazwiecki / @jzw / jim.jazwiecki[at]gmail.com —
  Python, linux sysadmin, AWS, SQL, HTML
• Jesse Burgheimer / @down10 / down10[at]gmail.com —
  HTML/CSS/JS, Wordpress-level PHP, and graphic dz9n sk1llz
• Jordan Brock / @jordanbrock / jordan[at]brock.id.au —
  Ruby, Rails, mySQL, AWS, HTML, CSS, HAML, SASS, jQuery, CoffeeScript
• Ethan Marcotte / @beep [Twitter + GitHub + GitLab] / public[at]ethanmarcotte.com —
  design, HTML/CSS/JS
• Eric Johnson / @lostbear —
  backend, .net, java, go, AWS, unit and integration testing, test coverage
• Michael Ivey / @ivey —
  Go, Ruby (Rails), dabble in most other languages and can learn whatever, UNIX sysadmin, AWS, React (a little), HTML/CSS (no designer but I can fumble around to success), Git, chatbots
• Nick / nick[at]curiola.com —
  Go, Python, Angular, Linux, AWS, terraform, docker, SQL, Nginx, Jenkins CI. Totally Web scalez!
• Trey Piepmeier / @trey [Twitter + GitHub + mlkshk] / @treypiepmeier [GitLab] —
  HTML/CSS/JS, Git, maybe React, maybe some easy Python.
• Josh Lee / @joshleejosh [mlkshk + Twitter + Facebook + Github] —
  html/css, js (jquery, d3), python, git
• Chris Bodenlos / @cb [mlkshk] / chris[at]ohm.io —
  Web development, design and related concerns - js/node, html/css, mysql/mssql, php/cf, linux/iis, typing/conference calls, ui/ux
• Scott Vandehey / @spaceninja [Twitter + Github + mlkshk —
  CSS specialist, some vanilla JS experience, technical documentation
• Björn Lijnema / @bjrn [mlkshk] / @bjxrn [Github] —
  web & dev master of none. HTML&CSS, also JS, PHP, SQL, server ops. Various other languages. Data wrangling. Happy to brush up on whatever is needed.