Skip to content
Maarten Koopmans edited this page Nov 9, 2020 · 1 revision

WIP - DO NOT SPEND TIME READING OR COMMNENING YET.

The goal of this page is to list and describe the people, processes, assets and services we use. We want to make these resilient, as currently most things are in silos. We'll also have to add some organizational structure.

- feature, process, .... buddy for resilience

The feature buddy process is designed as followed. On any given resource two people are responsible: the owner and the buddy. The owner knows all inside-out. THe buddy knows the larger picture and is involved in any major change. That way, when the owner is gone (holiday, hit by a bus, off-boarded suddenly) the feature buddy can quickly determine the problem area and zoon, pulling in resources as needed. The goal of this process is a) resiliency b) as light a load as possible for the feature buddy.

We may want to version assets if possible as well.

assets

What is the difference between these two?

  • asset site design
  • all things describing the overall design of the site, including it growth path.

What is the difference between these two?

  • asset shop architecture
  • all things payment flow on our site/end

Ah, I think the first of each "two" is supposed to be a sub-header.

  • asset code

  • All code relating to DiaGrammar. We may split this into "modules", like parse area, input, canvas, menu, export etc.

  • asset docker dev images

  • for the website flow we are using docker images via docker-compose. Hard part because we are doing some clever DNS work and the docker-compose YAML have the website's cert in it

  • asset static site

  • all things Hugo

services used (SaaS)

  • paddle
  • who manages the contacts about the services with Paddle.
  • Paddle backup (2checkout?)
  • mailgun
  • G Suite
  • Telegram -- Backup tool in case of service disruption or similar issues? So the team van always communicate.
  • Notion (EOL, need replacement)

processes

  • deployment process
  • how do we deploy various parts of the site, where to, etc
  • EV code signing EXEs
  • process updates
  • time/financial management
  • security processes (web certs, ssh keys etc)
  • customer support
  • license recovery support

people assets

  • who is part of the team, what is our churn?
  • onboarding for (part) of the project.
  • offboarding (limiting access).
  • people leave fairly suddenly. How to deal with that?

Clone this wiki locally