Explain the firefox source code to people already programmers

Status

Team

Open issues/risks

`

Stage 1: Definition

1. Feature overview

I read somewhere that Mozilla:

- wants 1 million programmers to edit the firefox source code

- knows that editing the firefox source code is hard

I want Mozilla to:

- mention in bold that nobody needs to read all the firefox source code to edit it

- have a list of requirements with links to learn them or to buy books to learn them

- requirements can't teach variables and other common programming concepts again

- requirements must be concise

- even though we don't need to know all the code, give us a firefox source code overview

- write where the code documentation is as a code comment

- e-mail where the code documentation is to add-on authors

- write code edit examples

- finally explain a part of the firefox code, the part that matters to the example

Mozilla already wants this, so I moved it to draft.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes