Collaborative Coordinate System: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
People can work on distinct modules, or even generate the same modules in parallel. | People can work on distinct modules, or even generate the same modules in parallel. | ||
Unique modules should be prioritized. If common modules are a bottleneck, additional players can work on other | Unique modules should be prioritized. If common modules are a bottleneck, additional players can work on other steps of the [[Development Template]]. | ||
Latest revision as of 04:52, 21 June 2025
Working with numerous people, we can work on collaborative design using a Merge Workflow. To do this, we need to define a collaborative coordinate system with the requirement that everyone (1) understands this system readily, and (2) that they can orient their contribution with respect to this system, and that (3) an unlimited number of people can be allocated to this system.
Participants coordinate based on availability of prior part libraries. If these don't exist, they are created and placed into a repository readily.
People can work on distinct modules, or even generate the same modules in parallel.
Unique modules should be prioritized. If common modules are a bottleneck, additional players can work on other steps of the Development Template.