ServerJS/Process: Difference between revisions
< ServerJS
Jump to navigation
Jump to search
m (fix broken link) |
(Add link to Proposal Process proposal) |
||
| Line 8: | Line 8: | ||
Number 1 is how things get done. Number 2 is how we ensure that number 1 is able to continue in face of inevitable disagreements. | Number 1 is how things get done. Number 2 is how we ensure that number 1 is able to continue in face of inevitable disagreements. | ||
* [[ServerJS/ProposalProcess|CommonJS Proposal Process]] | |||
(to be continued...) | (to be continued...) | ||
Revision as of 00:23, 4 September 2009
The goal of this project is to have something that people can run and build web frameworks and applications on.
The process needs to support that goal, plus the goal of having a specification that allows people to make other JS interpreters/platforms compatible.
There are two parts to the process:
- Creating the specs and code
- Handling disagreements
Number 1 is how things get done. Number 2 is how we ensure that number 1 is able to continue in face of inevitable disagreements.
(to be continued...)
Prior Art
- Python Enhancement Proposal (PEP). This process is not completely applicable, because Python has a dictator that keeps things from spiraling out of control.
- Scheme Requests For Implementation
- Request for Comments (RFC)
- Apache Voting