Add default files for new development of Mozilla JSON files.

3 files changed, 205 insertions, 0 deletions

diff --git a/jsons/BugZappers_data.json b/jsons/BugZappers_data-prototype.json
index d76aaef..d76aaef 100644
--- a/jsons/BugZappers_data.json
+++ b/jsons/BugZappers_data-prototype.json
diff --git a/jsons/Config_mozilla.json b/jsons/Config_mozilla.json
new file mode 100644
index 0000000..2b9e957
--- /dev/null
+++ b/jsons/Config_mozilla.json
@@ -0,0 +1,117 @@
+{
+    "commentPackages": {
+        "rh-common": {
+            "markTriaged": {
+                "position": "-commit_middle",
+                "name": "Mark Triaged",
+                "markTriaged": true,
+                "assignee": null
+            },
+            "addnoresponse": {
+                "name": "NoRespns",
+                "position": "topRow",
+                "commentIdx": "noResponseString",
+                "status": "CLOSED",
+                "resolution": "INSUFFICIENT_DATA"
+            },
+            "moveyourbutt": {
+                "name": "InfRemind",
+                "position": "topRow",
+                "commentIdx": "moveYourButString",
+                "setNeedinfo": true
+            },
+            "needinforbtn": {
+                "name": "NEEDINFO",
+                "position": "bottomRow",
+                "setNeedinfo": true
+            },
+            "notriagebtn": {
+                "name": "noTriage",
+                "position": "bottomRow",
+                "comment": "This bug has been triaged",
+                "status": "ASSIGNED",
+                "addCC": "self"
+            },
+            "nodebugsymbols": {
+                "name": "noDbg",
+                "position": "bottomRow",
+                "commentIdx": "noDebugSymbols",
+                "status": "CLOSED",
+                "resolution": "INSUFFICIENT_DATA"
+            },
+            "closeOnRetest": {
+                "position": "bottomRow",
+                "name": "Retest",
+                "commentIdx": "thankLettingUsKnow",
+                "status": "CLOSED",
+                "computeResolution": true
+            }
+        },
+        "rh-gecko": {
+            "addgetffrepro": {
+                "name": "Repro",
+                "position": "topRow",
+                "commentIdx": "getAbrtReproInfo",
+                "setNeedinfo": true
+            },
+            "webfailure": {
+                "name": "Bad site",
+                "position": "topRow",
+                "commentIdx": "websiteFailure",
+                "status": "CLOSED",
+                "resolution": "NOTABUG"
+            },
+            "crashInFlash": {
+                "name": "flashCrash",
+                "position": "topRow",
+                "commentIdx": "flashCrashString",
+                "status": "CLOSED",
+                "resolution": "CANTFIX"
+            }
+        },
+        "rh-xorg": {
+            "addgetlogstext": {
+                "name": "X logs",
+                "position": "topRow",
+                "commentIdx": "getLogsString",
+                "setNeedinfo": true
+            }
+        }
+    },
+    "commentStrings": {
+        "thankLettingUsKnow": "Thank you for letting us know.",
+        "noDebugSymbols": "Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).\n\nUnfortunately, we cannot use this backtrace.\n\nClosing as INSUFFICIENT_DATA.",
+        "noTriageString": "There is nothing to triage here.\n\nSwitching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.",
+        "getAbrtReproInfo": "Reporter, could you please describe us what you have done to get to this point, and how we can reproduce this issue here? Is there anything special about your system, network, configuration which we need to replicate here in order to reproduce your problem please?",
+        "getLogsString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.\n\nPlease add drm.debug=0x04 to the kernel command line, restart computer, and attach\n\n* your X server config file (/etc/X11/xorg.conf, if available),\n* X server log file (/var/log/Xorg.*.log)\n* output of the dmesg command, and\n* system log (/var/log/messages)\n\nto the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThanks in advance.",
+        "getLogsLiveCDString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue.\n\nIf the anaconda crashes during the switching to the graphic mode, most likely the problem lies in Xorg support for your graphics chip. There are couple of options how we can obtain information necessary for resolving the issue.\n\nIf the computer is not completely frozen when installation fails, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, somewhere on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.\n\nIf the computer is completely useless after installation fails, you can also install Fedora with a VESA mode driver (see http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/\nfor more information on that). Then after successful installation you can collect /var/log/anaconda.xlog, /var/log/Xorg.0.log, and the output of the program dmesg instead.\n\nOr you can install Fedora in a text mode completely, and then start X after that. If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThank you very much in advance.",
+        "noResponseString": "Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.\n\nUsers who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.\n\nClosing as INSUFFICIENT_DATA.",
+        "websiteFailure": "To report a broken website, first please make sure that you are running the latest release of Firefox (i.e., updated from updates-testing repository for your distribution or Rawhide).\n\nThen, if you can still reproduce the issue, pull down the 'Help' menu and select 'Report Broken Web Site'. This will start a wizard which will prompt you for the information required (privacy policy). This information is sent to a database and aggregated, so we have a good idea of which sites the most people are having problems with.\n\nIf you are interested, you can search the database of reports (http://reporter.mozilla.org/).\n\nClosing this bug as NOTABUG, if you don't agree with this resolution, please, reopen this bug and attach any relevant information to this bug.",
+        "sentUpstreamString": "We filed this bug in the upstream database (§§§) and believe that it is more appropriate to let it be resolved upstream.\n\nWe will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.\n\nThank you for the bug report.",
+        "moveYourButString": "Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.",
+        "cantfixNvidiaString": "Thanks for the report. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. If you would be able to reproduce this issue using only open source software, please, reopen this bug with the additional information, but in meantime I have no choice than to close this bug as CANTFIX (because we really cannot fix it).\n\nThe open source 'nouveau' driver (in package xorg-x11-drv-nouveau) is the recommended alternative for users of Nvidia graphic chips.  It is used by default in Fedora 11 and later if you remove any customizations that explicitly set the video driver.  The older \"nv\" driver may be needed in some cases.  It is also available in older Fedora releases.  Install the packages xorg-x11-drv-nouveau or xorg-x11-drv-nv and override the X server's default choice if necessary.  See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information.\n\nIf you used a non-packaged version of the driver from the Nvidia website please clean your system from additional libraries and software it installed. For users who are experiencing problems installing, configuring, or using the unsupported 3rd party proprietary \"nvidia\" video driver, Nvidia provides indirect customer support via an online web based support forum.  Nvidia monitors these web forums for commonly reported problems and passes them on to Nvidia engineers for investigation.  Once they've isolated a particular problem, it is often fixed in a future video driver update.\n\nThe NVNews Nvidia Linux driver forum is located at:\n\n\u0009http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14\n\nOnce you have reported this issue in the Nvidia web forums, others who may have experienced the particular problem may be able to assist.  If there is a real bug occuring, Nvidia will be able to determine this, and will likely resolve the issue in a future driver update for the operating system releases that they officially support.\n\nWhile we does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat/Fedora mailing lists helpful in finding assistance:\n\nX.Org mailing lists:\n\u0009http://www.freedesktop.org/XOrg/XorgMailingLists\n\nXFree86 mailing lists:\n\u0009http://www.xfree86.org/sos/lists.html\n\nRed Hat/Fedora mailing lists:\n\u0009https://listman.redhat.com/mailman/listinfo",
+        "flashCrashString": "Unfortunately, crash here happened in the binary-only flash player for which we don't have any source code, so unfortunately we cannot help you with it.\n\nClosing as CANTFIX (because that's our situation)",
+        "getEOL": "Thank you for your bug report.\nWe are sorry, but the Fedora Project no longer maintains this version of Fedora. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.\nAs a result we are setting this bug to CLOSED:WONTFIX"
+    },
+    "configData": {
+        "queryButton": true,
+        "upstreamButton": false,
+        "parseAbrtBacktraces": true,
+        "submitsLogging": false,
+        "suspiciousComponents": [
+
+        ],
+        "downloadJSON": [
+
+        ],
+        "objectStyle": "RH",
+        "matches": [
+            "https://bugzilla.redhat.com/show_bug.cgi.*",
+            "https://bugzilla.mozilla.org/show_bug.cgi.*"
+        ],
+        "signature": "\n\n-- \nFedora Bugzappers volunteer triage team\nhttps://fedoraproject.org/wiki/BugZappers"
+    },
+    "constantData": {
+
+    }
+}
diff --git a/jsons/bugzilla-comments-json.js b/jsons/bugzilla-comments-json.js
new file mode 100644
index 0000000..5707940
--- /dev/null
+++ b/jsons/bugzilla-comments-json.js
@@ -0,0 +1,88 @@
+{
+  "commentPackages": {
+    "test": {
+      "test-all": {
+        "name": "Test lots of things",
+        "product": "Thunderbird",
+        "component": "Internal Components",
+        "priority": "P1",
+        "severity": "major",
+        "assignee": "mschroeder",
+        "qacontact": "foobar",
+        "url": "http://example.com",
+        "addDependsOn": "123",
+        "removeDependsOn": "456",
+        "addBlocks": "789",
+        "removeBlocks": "101112",
+        "addWhiteboard": ["a","b","c"],
+        "removeWhiteboard": ["a","b"],
+        "addKeyword": ["d", "e"],
+        "removeKeyword": "e",
+        "url": "http://example.com",
+        "status": "RESOLVED",
+        "resolution": "INCOMPLETE",
+        "version": "Lightning 0.3",
+        "os": "All",
+        "platform": "All",
+        "prefixTitle": "pre-title:",
+        "suffixTitle": ":post-title"
+      }
+    },
+    "mozilla": {
+      "safe-mode": {
+        "name": "Safe Mode Question",
+        "comment": "Have you tried safe mode? (see https://support.mozillamessaging.com/en-US/kb/Safe+Mode for more information)"
+      },
+      "extension-issue": {
+        "name": "Response: Invalid due to extension issue",
+        "comment": "Sorry, your issue is to do with an extension and we are unable to support it here. Please raise the issue direct with the extension author or on their site.\n\nYou may find details of how to do this here:\n\n******* INSERT LINK TO EXTENSION SITE *******",
+        "status": "RESOLVED",
+        "resolution": "INVALID"
+      },
+      "profile-location": {
+        "name": "Profile Location text and link",
+        "comment": "To locate your profile, see this page for more information: https://support.mozillamessaging.com/en-US/kb/Profiles"
+      },
+
+      "no-response": {
+        "name": "INCOMPLETE (No Response from Reporter)",
+        "comment": "No response for a while now, closing INCOMPLETE. Please reopen if you can reproduce or answer any unanswered questions.",
+        "status": "RESOLVED",
+        "resolution": "INCOMPLETE"
+      }
+    },
+    "thunderbird": {
+    },
+
+    "calendar": {
+      "console-log": {
+        "name": "Calendar Console Log",
+        "comment": "Please enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor (Options > Advanced > General > Config Editor) and check your error console for messages."
+      },
+      "prepare-checkin": {
+        "name": "prepare for checkin",
+        "target": "1.0b2",
+        "removeKeyword": "checkin-needed",
+        "status": "RESOLVED",
+        "resolution": "FIXED",
+        "comment": "Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/INSERT_REV_HERE>\n\n-> FIXED"
+      },
+      "what-version": {
+        "name": "Using what version?",
+        "comment": "Please tell us what version you are using:\n\n* Thunderbird\n* Lightning\n* Provider for Google Calendar"
+      },
+      "retest-nightly": {
+        "name": "Retest with nightly",
+        "comment": "Does this still happen with the latest 1.0b2pre nightlies?"
+      },
+      "extension-fodder": {
+        "name": "Extension Fodder",
+        "addWhiteboard": "extension fodder",
+        "prefixSummary": "[extension fodder]",
+        "status": "RESOLVED",
+        "resolution": "WONTFIX",
+        "comment": "This sounds like a good idea, but I think it makes more sense as an extension. Marking WONTFIX for core calendar."
+      }
+    }
+  }
+}