ServerJS/Process: Difference between revisions
< ServerJS
mNo edit summary |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
There are two parts to the process: | 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. | 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...) | ||
| Line 21: | Line 24: | ||
== Related Discussions == | == Related Discussions == | ||
* [http://groups.google.com/group/ | * [http://groups.google.com/group/commonjs/browse_thread/thread/280c8b0375783604 Organisation and Making Decisions] | ||
Latest revision as of 07:32, 5 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