Changes

Jump to: navigation, search

Powered by Mozilla:Survey

278 bytes added, 18:21, 19 December 2008
A rearrangement - still far from perfect
==Questions==
Which Mozilla===Application-based applications have you been involved with?Specific===
Please fill out this part of the survey once for each Mozilla-based application you have been involved in developing. What is the name and purpose of the application? Please give a URL if the application is publicly available. Which Mozilla technologies have you worked with beforedoes the application use?
* Gecko
* Necko
* XPCOM
* XULRunner
* XUL
* XBL
* Other: ____
Have you ever contributed a patch to the Mozilla codebase?* Yes* No If What did you have contributed a patchuse these technologies for, was that patch accepted and checked-in?* Yes* NoWhat were some of the pain points during the patch submission processwhy did you choose them?
If you haven't contributed a patch, could you provide some information about why you haven't or what could be done to make the contribution process easier for you or your organization?====XUL====
What are some frustrations or barriers you've encountered with Mozilla technologies?* The patch review process* A lack of developer tools* Incomplete documentation* Please complete the following section if your application uses XUL...* Other: ____
Why did you choose XUL?
* Native Look and Feel
How do you control the version of Mozilla your users view your app with?  Do you have concerns about the future stability of XUL?
Do you use XBL?====XULRunner====
What technology is Please complete the majority following section if your application logic developed in?* XPCOM: C/C++* XPCOM: JavaScript* JavaScript Modules* JavaScript XUL script includes* Otheruses XULRunner.
If you use XULRunner, do you build it yourself, or use existing binaries?
If you build it yourself, do you patch it locally?
* Yes
** How many patches do you apply? If they haven't been upstreamed yet, what is stopping you?
* No
 
If you patch it, how many patches do you apply? If they haven't been submitted upstream yet, what is stopping you?
 
===Community Involvement===
 
Have you ever submitted a patch to the Mozilla codebase?
* Yes
* No
 
If you have submitted a patch, was that patch accepted and checked in?
* Yes
* No
 
What parts of the patch submission process did you find difficult or lengthy?
 
If you haven't contributed a patch, why is that? What could be done to make the contribution process easier for you or your organization?
 
What are some frustrations or barriers you've encountered with Mozilla technologies?
 
* The patch review process
* A lack of developer tools
* Incomplete documentation
* ...
* Other: ____
Accountapprovers, antispam, confirm, emeritus
4,925
edits

Navigation menu