Difference between revisions of "Updating JS guide and JS reference"

From CDOT Wiki
Jump to: navigation, search
(Project Description)
m (Reverted edits by Avol (Talk); changed back to last version by JesseRuderman)
 
(5 intermediate revisions by 3 users not shown)
Line 21: Line 21:
 
== Project Details ==
 
== Project Details ==
  
Provides more depth than the Project DescriptionThis is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.
+
* Good people to talk to about this on irc are: '''dria''' (who owns MDC) and '''sheppy''' (technical writer/dev for Mozilla)You should also join '''#devmo''' in irc to get connected to the rest of the technical writers.
 +
* You might also hang out with people who maintain and test the JavaScript engine, such as '''brendan''' and '''Jesse''', in '''#jslang'''.
  
 
== Project News ==
 
== Project News ==

Latest revision as of 08:30, 17 January 2007

Project Name

Updating JS guide and JS reference

Project Description

The current JavaScript guide and reference are valuable, but in serious need of updating in both structure and content (new language features, more relevant compatibility information, improved examples).

Related tech and skills: documentation, JavaScript

Project Leader(s)

Colin Guy

Project Contributor(s)

Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki

NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.

Project Details

  • Good people to talk to about this on irc are: dria (who owns MDC) and sheppy (technical writer/dev for Mozilla). You should also join #devmo in irc to get connected to the rest of the technical writers.
  • You might also hang out with people who maintain and test the JavaScript engine, such as brendan and Jesse, in #jslang.

Project News

This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.

Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.