[TASK] MetaMask Project Redesign (void)

[ghost]

[2018-07-15: recreated issue-text, mainly for task-documentation purposes. The project redesign was not applied]

---

- ! IMMEDIATE PROJECT REDESIGN NECESSARY, STARTING WITH A CODE FREEZE  ! -

---

Continuation of #3427 and #3631

Goals

• Drastically reduce teach-in time for new participants (team, contributors, visitors)
• Allow participants to focus on specific subsystems (core, ui, translation etc.)
• Keep all happy: managers, casual devs, core devs, agiles, phasic-workers, "lab-rats" (...)

Main Process

During the redesign of https://github.com/lazaridiscom/mm-vault (which includes the task to provide hw-wallet support for ledger), any upcoming barriers will be processed, for example: test-system, ci, code-documentation, collaboration-workflow, etc.

This is a "Zero Theory", "Full Practical" Approach which is only documented in-source-code / in-repository. Issues are usually not filed or discussed, but immediately solved (or at least started to work on).

Current BARRIER

The MetaMask Project.

Note: this is (mostly) a sequence. Breaking the sequence introduces problems. Additionally, the execution must be directed, thus adjustments can be made whenever necessary.

• Use an external entity to assess everything (SURPRISE: doing this already since months)
• Freeze the Code (for a minimum of 2 weeks)
• Freeze Issues (no new Issues filed from team)
• Clarify who works (or wants to) on something different than main MM code...
• ...and clarify the remaining responsibilities (to team-mates, users) of those
• Document/Refine Test-System
• Document/Refine Build-System
• Document Code (without any changes)
• Delete redundant information
• Move more and more information directly into the repository
• Use an external entity to revise/provide procedures & processes.
• Isolate subsystems, split out main subsystems
• New long-term oriented hires get to claim central subsystems (e.g. mm-vault)
• (still fuzzy): Existent External ui-team is given more autonomy (based on rules/guidelines)
• Restart the project: Asynchronous, Event-Driven, Standard-Procedures based

The "external entity" would be me (even if a project-manager is hired, he should not start with such heavy task without a teach-in. I had a 2 months teach-in (one voluntarily, one more due to the delays).

Overall Duration

• 1 month teach-in (already done)
• limited to 3 months (avoid burnout)
• Apr, May, Jun 2018

Important Note

At this point (after loosing excessive amounts of progress, due to the dysfunctional main project), I move all my effort out and away of the main repository. Without access-rights (even not for the issue-tracker) I cannot do much (at least not without ruining my stomach...).

I will fulfill my main task (mm-vault) anyway (e.g. whilst working with a mm fork which I stabilize myself). What happens in the mm-main project depends on the team, the lead and the upper management (if existent, I have not yet understood the "organism").

I'm calling (partially shouting) since around 2 months that "things are bad". But without any authority, those calls are like a cats meow.

Wanted:

a Lion to ROAR: FREEZE IT, NOW!!!

---

follow-up: #4060