moba
commented
6 years ago My proposed actions towards a release, and a possible path towards attracting node operators:
- we need instructions not only about how to set up a node, but also how to maintain it. this could be as simple as Yawning's suggestion of tagged releases in git, for now, and respective notes, or as complex as automated builds for various distributions. i hear that there are toolkits that make this fairly easy these days, and can even produce pre-built virtual machine images. the existing nix files can serve as a potential starting point here.
- we need a documented way for users to register client keys on our testbed. this testbed could be run on a single machine to reduce complexity.
- we should release our clients (cli, mailproxy, android) with a preconfigured set of testbed nodes in their config. again, these nodes can all run on one machine of ours; in the release notes, we ask for operators to join us for a proper testbed. we can request certain features, for example: only dedicated machines on >= 1 gbit/s connections with more than 5TB of monthly traffic allowance (or something similarly powerful)
Without a release (strategy), I don't currently see how and why we should hunt down potential operators just yet.
david415
our volunteer run mix network needs a set of provider and mix operators. the provider ops will have to deal with users and mix ops will not.