Difference between revisions of "Firebug "linting" for portability problems"
(→Project Description) |
(→Project Leader(s)) |
||
Line 12: | Line 12: | ||
== Project Leader(s) == | == Project Leader(s) == | ||
− | + | [[user: ptmahent | Piratheep Mahenthiran]] | |
− | + | Resources: mfinkle, robcee | |
== Project Contributor(s) == | == Project Contributor(s) == |
Revision as of 13:35, 19 September 2008
Contents
Firebug "linting" for portability problems
Firebug "linting" for portability problems
Project Description
DLots of web developers use Firebug and Firefox for building their applications, but we want those apps to work well in other browsers as well. If Firebug knew about JS or CSS patterns that could cause problems in other browsers, it would make it much easier to have those applications work in all browsers.
Resources: mfinkle, robcee
http://groups.google.com/group/firebug/topics
Project Leader(s)
Piratheep Mahenthiran Resources: mfinkle, robcee
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
Provides more depth than the Project Description. This 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.
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.