667
edits
Changes
no edit summary
==== Documentation ====
Many different types of documentation would be included in the kit, some of which existand some which would need to be created. Wherever possible, the documentation in the kit would refer to things in the kit--the kit should be self-contained as much as possible. * Documentation on using each of the tools included in the kit * Reference and other Documentation (much from [http://developer.mozilla.org MDC]) * Learning materials (much from [http://zenit.senecac.on.ca/wiki Seneca courses])** Labs and Walkthroughs** Presentations/Lectures (from Seneca and Mozilla)** Tutorials** Video/Audio content (guest lectures, conference talks, etc.) * Books** [http://developer.mozilla.org/en/docs/Creating_XPCOM_Components Creating XPCOM Components]** [http://books.mozdev.org/chapters/index.html Creating Applications with Mozilla] * Interviews, articles, substantial blog posts, etc. from Mozilla Developers * Bibliography/Lists of non-free books of interest to Mozilla Developers * Glossary of Terms
==== Questions/Issues ====
* What's the best way to use MDC and other Mozilla documentation in this such that future releases don't need a lot of manual work to pull in new material?
* Should source code for popular extensions be included and indexed? This might be nice in terms of providing learning/teaching materials for extension developers.
* Need to clear copyright and licensing on all materials to be used.
* Should there be more than one? For example, Academic version, Developer version? I lean toward 'no', but perhaps some types of content could be put on a separate disc?
* There should also be an Enterprise Deployment version (NOTE: trying to get a student to do this with mkaply)
* Is it worth mining the newsgroups for info?
* What about Mac OS X?