Timeframe: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Kurzgesagt says the exponential phase of mirror deployment can be accomplished over a ten year period, so. Let's work backwards. *2040 deployment complete, mirror swarm onlin...") |
No edit summary |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Kurzgesagt says the exponential phase of mirror deployment can be accomplished over a ten year period, so. Let's work backwards. | Kurzgesagt says the exponential phase of mirror deployment can be accomplished over a ten year period, so. Let's work backwards. | ||
*2040 deployment complete, | *2040 deployment complete, dyson swarm online and sending at full power. | ||
*2030 deployment started, deployment test phase begins. | *2030 deployment started, deployment test phase begins. | ||
*2029 sponsored launch. | *2029 sponsored launch. | ||
| Line 12: | Line 12: | ||
*2021 management structure in place, team structures tested | *2021 management structure in place, team structures tested | ||
*2020 mirrorswarm.com registered, planning starts. | *2020 mirrorswarm.com registered, planning starts. | ||
== Strategy == | |||
An emergent team structure driven by | started [[User:John|John]] ([[User talk:John|talk]]) 11:59, 3 January 2020 (UTC) | ||
A long-term management structure aimed at retaining | *An emergent team structure driven by progressive analysis of the requirement. | ||
*A long-term management structure aimed at retaining control of the swarm to oversee compliance with the constraints, initially achieved by Jowan's voting control. This start-up direction model is [https://en.wikipedia.org/wiki/Benevolent_dictator_for_life BDFL (Benevolent dictator for life)]. | |||
*Make it work on paper before anyone takes out a screwdriver. | |||
*Small project teams | |||
*Rapid prototyping | |||
*High transparency | |||
*Asynchronous cooperation | |||
*Webinar meetings and conferences for documentation and open access | |||
*Actively avoid back channels, leave a documentation trail | |||
*Avoid proprietary or patented technology where it is applicable. | |||
*Early access to spin-off open source technology will attract business participants | |||
Latest revision as of 09:17, 23 July 2020
Kurzgesagt says the exponential phase of mirror deployment can be accomplished over a ten year period, so. Let's work backwards.
- 2040 deployment complete, dyson swarm online and sending at full power.
- 2030 deployment started, deployment test phase begins.
- 2029 sponsored launch.
- 2027 plans finalized, sponsors in place, product assembly begins.
- 2026
- 2025 unit testing started
- 2024
- 2023
- 2022
- 2021 management structure in place, team structures tested
- 2020 mirrorswarm.com registered, planning starts.
Strategy
started John (talk) 11:59, 3 January 2020 (UTC)
- An emergent team structure driven by progressive analysis of the requirement.
- A long-term management structure aimed at retaining control of the swarm to oversee compliance with the constraints, initially achieved by Jowan's voting control. This start-up direction model is BDFL (Benevolent dictator for life).
- Make it work on paper before anyone takes out a screwdriver.
- Small project teams
- Rapid prototyping
- High transparency
- Asynchronous cooperation
- Webinar meetings and conferences for documentation and open access
- Actively avoid back channels, leave a documentation trail
- Avoid proprietary or patented technology where it is applicable.
- Early access to spin-off open source technology will attract business participants