57237 - Outside developers need more documentation

Status: RESOLVED WORKSFORME

(Developer Documentation Graveyard :: General, defect, P3)

Description

[Aaron Leventhal]

From what I hear, now is a good time to propose some work on the developer 
docs. Can we have a discussion about what holes need to be filled, and what 
needs updating? My concern is that Mozilla development is going to belong to 
an 'exclusive club'. Let's spread the religion.

Here are some things we could use:
- we could use a good overview of the architecture. 
- a section from the point of view of a web developer who just knows HTML and 
javascript, and they want to start coding their own chrome. They don't need to 
go through building from source, they can just develop using a release build 
with mozilla -console. A tutorial with examples would be good - a lot of these 
guys are more right brained.
- A reference for the Mozilla API, listing the important objects and methods 
available to Javascript developers.
- In general I think a lot of the developers could spend a day or two updating 
documentation relevant to their area. Some things are out of date or should 
eventually be consolodated and cleaned up.

Comment 1

[Brian 'netdragon' Bober]

Turning this into a META bug. Please add META keyword.

Comment 2

[James Cox]

accepting QA for mozilla developer docs.

some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.

I will do a full review of all bugs not touched in one week (8th April). 

Thanks.

</spam>

Comment 3

[Daniel Wang]

103361, 61025

Comment 4

[Phil Ringnalda (:philor)]

So, this is an abandoned meta bug for abandoned documentation bugs in products where they'll never be noticed, or changed when they get documented? Bet it will work just as well with a closed resolution, then.