|
|
|
|
@ -9,8 +9,9 @@ that enables anyone to self-host a specific set of apps.
|
|
|
|
|
** A worker's co-operative
|
|
|
|
|
|
|
|
|
|
I want to build a workplace where the goals are differently aligned
|
|
|
|
|
from that of a more common tech workplace. The goals of the worker's
|
|
|
|
|
co-op:
|
|
|
|
|
from that of a more common tech workplace.
|
|
|
|
|
|
|
|
|
|
*** Goals
|
|
|
|
|
|
|
|
|
|
- worker control: 1 worker = 1 vote
|
|
|
|
|
- long-term, stable sustainable job's for members
|
|
|
|
|
@ -40,13 +41,24 @@ co-op:
|
|
|
|
|
- actively manage environmental impacts
|
|
|
|
|
- seek out, involve, and learn from diverse groups
|
|
|
|
|
|
|
|
|
|
** Product
|
|
|
|
|
*** Bylaws
|
|
|
|
|
|
|
|
|
|
- Impactful decisions and bylaws can only be made by a vote of all
|
|
|
|
|
members (consensus)
|
|
|
|
|
|
|
|
|
|
- Hiring and firing of a member can only be made by a consensus vote
|
|
|
|
|
of all members
|
|
|
|
|
|
|
|
|
|
- The co-op and its members may not enter into any agreements that
|
|
|
|
|
would cause the change of worker control
|
|
|
|
|
|
|
|
|
|
* Product
|
|
|
|
|
|
|
|
|
|
The goal is to produce a product that enables less-technical people
|
|
|
|
|
the ability to self-host applications in a secure and auto-updating
|
|
|
|
|
manner. Self-hosting for anyone!
|
|
|
|
|
|
|
|
|
|
*** Potential Qualities
|
|
|
|
|
** Potential Qualities
|
|
|
|
|
|
|
|
|
|
- secure
|
|
|
|
|
- auto-updates
|
|
|
|
|
@ -64,7 +76,7 @@ manner. Self-hosting for anyone!
|
|
|
|
|
- updates are run through CI before being made available
|
|
|
|
|
- can be moved between providers (no vendor lock-in)
|
|
|
|
|
|
|
|
|
|
*** Potential Tech For Self-Hosted Cloud Infra
|
|
|
|
|
** Potential Tech For Self-Hosted Cloud Infra
|
|
|
|
|
|
|
|
|
|
- DNS Registration
|
|
|
|
|
- Terraform via supported registry
|
|
|
|
|
@ -81,7 +93,7 @@ manner. Self-hosting for anyone!
|
|
|
|
|
- OS
|
|
|
|
|
- flatcar linux
|
|
|
|
|
|
|
|
|
|
*** Potential Tech for Deployment and Config Node
|
|
|
|
|
** Potential Tech for Deployment and Config Node
|
|
|
|
|
|
|
|
|
|
Can be run locally or as a SaaS
|
|
|
|
|
|
|
|
|
|
@ -95,4 +107,35 @@ Can be run locally or as a SaaS
|
|
|
|
|
- can be used to:
|
|
|
|
|
- select apps
|
|
|
|
|
- resources (manage)
|
|
|
|
|
- view logs (stored on self-hosted infra)
|
|
|
|
|
- view logs (stored on self-hosted infra)
|
|
|
|
|
|
|
|
|
|
** Potential Revenue Model
|
|
|
|
|
|
|
|
|
|
- End users pay for:
|
|
|
|
|
- a one-off version
|
|
|
|
|
|
|
|
|
|
This would enable using the product to create a self-hosted
|
|
|
|
|
instance with the apps of the users choosing. It would still
|
|
|
|
|
include automatic bi-weekly OS updates (via flatcar OS) but
|
|
|
|
|
otherwise may not include automatic updates for the platform.
|
|
|
|
|
- a monthly subscription
|
|
|
|
|
|
|
|
|
|
This would enable full automatic updates for the product, the
|
|
|
|
|
self-hosted instance, all apps running on the self-hosted
|
|
|
|
|
instance.
|
|
|
|
|
|
|
|
|
|
- Open source?
|
|
|
|
|
|
|
|
|
|
Likely the product itself can be open sourced (AGPL) and made freely
|
|
|
|
|
available. The target end user is not someone that would be likely
|
|
|
|
|
to setup and run it on their own anyways but it would be an option
|
|
|
|
|
if they didn't like changes made to the product in the future and
|
|
|
|
|
they gained technical experience or hired someone to manage their
|
|
|
|
|
own control node themselves.
|
|
|
|
|
|
|
|
|
|
- Target end user:
|
|
|
|
|
|
|
|
|
|
Companies or individuals that would like to have more control or
|
|
|
|
|
save on costs relative to pure SaaS solutions but do not have the
|
|
|
|
|
technical knowledge, time, or appetite for risk that would lead them
|
|
|
|
|
to run their own self-hosted infrastructure.
|
|
|
|
|
|
