NDCLab / pepper-pipeline

tool | Python Easy Pre-Processing EEG Reproducible Pipeline
GNU Affero General Public License v3.0
3 stars 3 forks source link

Propose rough draft on governance #358

Open F-said opened 3 years ago

F-said commented 3 years ago

What needs documentation and what will each item entail?

F-said commented 3 years ago

Frederick P. Brooks Jr. Architecture, Democracy, and System Design. The Mythical Man-Month, 1995, pp. 41 - 50

Challenges

Proposed Solution

Separation of architecture (research, syntax, documentation) from implementation (coding) ensures conceptual integrity on a large scale.

Questions to Solution

  1. This can be thought of as an "aristocracy" where the meticulous planning is reserved for a section of the members, and the developers being the cogs.
  2. Specification may be "too rich in function" and fail to reflect practical development outcomes.
  3. What is left for the implementers to do if the generation of "thought-stuff" behind the software is out of their decision?

Answers

  1. In return, the integrity of the project is maintained. Good ideas that sprout from this project, but do not fit in its design principles can be branched off to separate software, but must be omitted from the project itself.
    • W/o architectural constraints, implementers will have to act as architects for the underlying principle of the software while they develop, resulting in "uncertain" software.
  2. Consistent discussion between architects and implementers will allow a possible reframing of spec.
  3. Development requires its own creative effort to implement the outlined concepts, "form is liberating."

Form of this solution in PEPPER

F-said commented 3 years ago

Questions

Next Actions