C3P0 is a PHP script for filing multiple bugs at once wih Bugzilla? by setting a parameters such as locale(language). It saves you time when filing those pesky bugs.

You can find it here,

https://github.com/milossh/bugzilla-c3po

Use the PuTTY client on Windows, or SSH on UNIX and UNIX-like systems.

Log in to your account using SSH.

Download the bugzilla tarball:

wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-STABLE.tar.gz

Change to your html directory (i.e. the directory that will store files for bugs.myOwnDomain.com) using the command

cd myOwnDomain.com/bugs

(Hint, if that directory does not exist you can make it with

mkdir $HOME/myOwnDomain.com/bugs

Untar the Bugzilla tarball into your html directory:

tar zxf ../bugzilla-STABLE.tar.gz

Change to the bugzilla directory with the command:

cd bugzilla-###

where ### is the version number on the folder that you just extracted.

Create the default localconfig file by entering the command:

nice -n 12 ./checksetup.pl

You should see output similar to the following:

* This is Bugzilla 3.0 on perl 5.8.4

* Running on Linux 2.4.29-grsec+w+fhs6b+gr0501+nfs+a32+++p4+sata+c4+gr2b-v6.189 #1 SMP Mon Feb 7 13:23:30 PST 2005

Checking perl modules…

Checking for CGI (v2.93) ok: found v3.04

Checking for TimeDate (v2.21) ok: found v2.22

Checking for DBI (v1.41) ok: found v1.46

Checking for PathTools (v0.84) ok: found v0.87

Checking for Template-Toolkit (v2.12) ok: found v2.14

Checking for Email-Send (v2.00) ok: found v2.185

Checking for Email-MIME-Modifier (any) ok: found v1.442

Checking available perl DBD modules…

Checking for DBD-Pg (v1.45) found v1.41

Checking for DBD-mysql (v2.9003) ok: found v2.9006

The following Perl modules are optional:

Checking for GD (v1.20) ok: found v2.23

Checking for Template-GD (any) ok: found v1.56

Checking for Chart (v1.0) ok: found v2.2

Checking for GDGraph (any) ok: found v1.43

Checking for GDTextUtil (any) ok: found v0.86

Checking for XML-Twig (any) ok: found v3.17

Checking for MIME-tools (v5.406) ok: found v5.417

Checking for libwww-perl (any) ok: found v2.033

Checking for PatchReader (v0.9.4) ok: found v0.9.5

Checking for PerlMagick (any) ok: found v6.0.6

Checking for perl-ldap (any) ok: found v0.32

Checking for SOAP-Lite (any) ok: found v0.66.1

Checking for HTML-Parser (v3.40) ok: found v3.45

Checking for HTML-Scrubber (any) ok: found v0.08

Checking for Email-MIME-Attachment-Stripper (any) not found

Checking for Email-Reply (any) not found

Checking for mod_perl (v1.999022) not found

Checking for CGI (v3.11) found v3.04

Checking for Apache-DBI (v0.96) not found

* NOTE: You must run any commands listed below as root.

**********************************************************************

* OPTIONAL MODULES *

**********************************************************************

* Certain Perl modules are not required by Bugzilla, but by *

* installing the latest version you gain access to additional *

* features. *

* *

* The optional modules you do not have installed are listed below, *

* with the name of the feature they enable. If you want to install *

* one of these modules, just run the appropriate command in the *

* “COMMANDS TO INSTALL” section. *

**********************************************************************

***********************************************************************

* MODULE NAME * ENABLES FEATURE(S) *

***********************************************************************

* Email-Reply * Inbound Email *

* Email-MIME-Attachment-Stripper * Inbound Email *

* mod_perl * mod_perl *

* Apache-DBI * mod_perl *

* CGI * mod_perl *

***********************************************************************

COMMANDS TO INSTALL:

Email-Reply: /usr/bin/perl -MCPAN -e ‘install Email::Reply’

Email-MIME-Attachment-Stripper: /usr/bin/perl -MCPAN -e ‘install Email::MIME::Attachment::Stripper’

mod_perl: /usr/bin/perl -MCPAN -e ‘install mod_perl2′

Apache-DBI: /usr/bin/perl -MCPAN -e ‘install Apache::DBI’

CGI: /usr/bin/perl -MCPAN -e ‘install CGI’

Reading ./localconfig…

OPTIONAL NOTE: If you want to be able to use the ‘difference between two

patches’ feature of Bugzilla (which requires the PatchReader Perl module

as well), you should install patchutils from:

http://cyberelk.net/tim/patchutils/

This version of Bugzilla contains some variables that you may want to

change and adapt to your local settings. Please edit the file

./localconfig and rerun nice -n 12 checksetup.pl.

The following variables are new to ./localconfig since you last ran

checksetup.pl: create_htaccess, webservergroup, db_driver, db_host, db_name, db_user, db_pass, db_port, db_sock, db_check, index_html, cvsbin, interdiffbin, diffpath

If any of the modules in the top section that doesn’t say “optional” are listed as missing, please see the section below for the specific version of Bugzilla you are installing to fix the version-specific issues, then return here and do this step again. It is worth using “nice” to stop the install-module.pm from being too processor intensive, as DreamHost servers will kill processes it deems as using too much of the server resources, giving install errors. For example, to add MySQL support you would run

nice -n 12 perl install-module.pl DBD::mysql

to install with a lower process priority.

Find out your primary group. On the command line, run:

groups

and make note of the group listed there. If there is more than one, you want the first one. Remember this, you’ll need it in the next step.

Edit localconfig with your favorite text editor. Make the following changes:

Change $webservergroup = “apache” to $webservergroup = “yourgroup” where yourgroup is your primary group (which you looked up in the previous step). NOTE: Previous instructions here suggested to set $webservergroup = “” — you do not want to do this as it will let anyone else hosted on the same machine with you screw with your bugzilla settings!

Change $db_host = “localhost” to $db_host = “mysql.myOwnDomain.com” (the value specified in “DB Hostname” above).

Change $db_name = “bugs” to $db_name = “userbugs” (the value specified in “DB name” above).

Change $db_user = “bugs” to $db_user = “userbugs” (the value specified in “DB Username” above).

Change $db_pass = ”; to $db_pass = ‘password’;, where password is the password you chose for “DB Password” above.

re-run checksetup.pl:

nice -n 12 ./checksetup.pl

Dreamhost uses suexec to run your CGIs. This means the CGIs run as your user and not as the webserver. As of Bugzilla 3.6, checksetup.pl will deal with this automatically Please see the section on Bugzilla 3.6 below. If you’re installing a version prior to 3.6, you’ll need to do this: After running checksetup.pl (and after every time you ever run checksetup.pl) you’ll need to run the following commands to set some additional permissions to let Bugzilla work under suexec on Dreamhost:

for i in docs graphs images js skins; do find $i -type d -exec chmod o+rx {} \; ; done

for i in jpg gif css js png html rdf xul; do find . -name \*.$i -exec chmod o+r {} \; ; done

find . -name .htaccess -exec chmod o+r {} \;

chmod o+x . data data/webdot

That should be it. Launch your web browser and point it to http://www.myOwnDomain.com/bugs/bugzilla-###. You should see the Bugzilla front page.

Configuring Bugzilla

1. Log in to your account using SSH.
2. Download the bugzilla tarball:

   wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-STABLE.tar.gz

3. Change to your html directory (i.e. the directory that will store files for bugs.myOwnDomain.com) using the command

   cd myOwnDomain.com/bugs

   (Hint, if that directory does not exist you can make it with

   mkdir $HOME/myOwnDomain.com/bugs

4. Untar the Bugzilla tarball into your html directory:

   tar zxf ../bugzilla-STABLE.tar.gz

5. Change to the bugzilla directory with the command:

   cd bugzilla-###

   where ### is the version number on the folder that you just extracted.

6. Create the default localconfig file by entering the command:

   nice -n 12 ./checksetup.pl

   You should see output similar to the following:

   * This is Bugzilla 3.0 on perl 5.8.4
   * Running on Linux 2.4.29-grsec+w+fhs6b+gr0501+nfs+a32+++p4+sata+c4+gr2b-v6.189 #1 SMP Mon Feb 7 13:23:30 PST 2005
   
   Checking perl modules...
   Checking for             CGI (v2.93)   ok: found v3.04
   Checking for        TimeDate (v2.21)   ok: found v2.22
   Checking for             DBI (v1.41)   ok: found v1.46
   Checking for       PathTools (v0.84)   ok: found v0.87
   Checking for Template-Toolkit (v2.12)   ok: found v2.14
   Checking for      Email-Send (v2.00)   ok: found v2.185
   Checking for Email-MIME-Modifier (any)     ok: found v1.442 
   
   Checking available perl DBD modules...
   Checking for          DBD-Pg (v1.45)    found v1.41
   Checking for       DBD-mysql (v2.9003) ok: found v2.9006 
   
   The following Perl modules are optional:
   Checking for              GD (v1.20)   ok: found v2.23
   Checking for     Template-GD (any)     ok: found v1.56
   Checking for           Chart (v1.0)    ok: found v2.2
   Checking for         GDGraph (any)     ok: found v1.43
   Checking for      GDTextUtil (any)     ok: found v0.86
   Checking for        XML-Twig (any)     ok: found v3.17
   Checking for      MIME-tools (v5.406)  ok: found v5.417
   Checking for     libwww-perl (any)     ok: found v2.033
   Checking for     PatchReader (v0.9.4)  ok: found v0.9.5
   Checking for      PerlMagick (any)     ok: found v6.0.6
   Checking for       perl-ldap (any)     ok: found v0.32
   Checking for       SOAP-Lite (any)     ok: found v0.66.1
   Checking for     HTML-Parser (v3.40)   ok: found v3.45
   Checking for   HTML-Scrubber (any)     ok: found v0.08
   Checking for Email-MIME-Attachment-Stripper (any)      not found
   Checking for     Email-Reply (any)      not found
   Checking for        mod_perl (v1.999022)  not found
   Checking for             CGI (v3.11)    found v3.04
   Checking for      Apache-DBI (v0.96)    not found 
   
   * NOTE: You must run any commands listed below as root.
   
   **********************************************************************
   * OPTIONAL MODULES                                                   *
   **********************************************************************
   * Certain Perl modules are not required by Bugzilla, but by          *
   * installing the latest version you gain access to additional        *
   * features.                                                          *
   *                                                                    *
   * The optional modules you do not have installed are listed below,   *
   * with the name of the feature they enable. If you want to install   *
   * one of these modules, just run the appropriate command in the      *
   * "COMMANDS TO INSTALL" section.                                     *
   **********************************************************************
   
   ***********************************************************************
   *                    MODULE NAME * ENABLES FEATURE(S)                 *
   ***********************************************************************
   *                    Email-Reply * Inbound Email                      *
   * Email-MIME-Attachment-Stripper * Inbound Email                      *
   *                       mod_perl * mod_perl                           *
   *                     Apache-DBI * mod_perl                           *
   *                            CGI * mod_perl                           *
   ***********************************************************************
   COMMANDS TO INSTALL:
   
       Email-Reply: /usr/bin/perl -MCPAN -e 'install Email::Reply'
   Email-MIME-Attachment-Stripper: /usr/bin/perl -MCPAN -e 'install Email::MIME::Attachment::Stripper'
          mod_perl: /usr/bin/perl -MCPAN -e 'install mod_perl2'
        Apache-DBI: /usr/bin/perl -MCPAN -e 'install Apache::DBI'
               CGI: /usr/bin/perl -MCPAN -e 'install CGI'
   Reading ./localconfig...
   
   OPTIONAL NOTE: If you want to be able to use the 'difference between two
   patches' feature of Bugzilla (which requires the PatchReader Perl module
   as well), you should install patchutils from:
   
   http://cyberelk.net/tim/patchutils/
   
   This version of Bugzilla contains some variables that you may want to
   change and adapt to your local settings. Please edit the file
   ./localconfig and rerun nice -n 12 checksetup.pl.
   
   The following variables are new to ./localconfig since you last ran
   checksetup.pl:  create_htaccess, webservergroup, db_driver, db_host, db_name, db_user, db_pass, db_port, db_sock, db_check, index_html, cvsbin, interdiffbin, diffpath

   If any of the modules in the top section that doesn’t say “optional” are listed as missing, please see the section below for the specific version of Bugzilla you are installing to fix the version-specific issues, then return here and do this step again. It is worth using “nice” to stop the install-module.pm from being too processor intensive, as DreamHost servers will kill processes it deems as using too much of the server resources, giving install errors. For example, to add MySQL support you would run

   nice -n 12 perl install-module.pl DBD::mysql

   to install with a lower process priority.

7. Find out your primary group. On the command line, run:

   groups

   and make note of the group listed there. If there is more than one, you want the first one. Remember this, you’ll need it in the next step.

8. Edit localconfig with your favorite text editor. Make the following changes:
   1. Change $webservergroup = "apache" to $webservergroup = "yourgroup" where yourgroup is your primary group (which you looked up in the previous step). NOTE: Previous instructions here suggested to set $webservergroup = “” — you do not want to do this as it will let anyone else hosted on the same machine with you screw with your bugzilla settings!
   2. Change $db_host = "localhost" to $db_host = "mysql.myOwnDomain.com" (the value specified in “DB Hostname” above).
   3. Change $db_name = "bugs" to $db_name = "userbugs" (the value specified in “DB name” above).
   4. Change $db_user = "bugs" to $db_user = "userbugs" (the value specified in “DB Username” above).
   5. Change $db_pass = ''; to $db_pass = 'password';, where password is the password you chose for “DB Password” above.
9. re-run checksetup.pl:

   nice -n 12 ./checksetup.pl

10. Dreamhost uses suexec to run your CGIs. This means the CGIs run as your user and not as the webserver. As of Bugzilla 3.6, checksetup.pl will deal with this automatically Please see the section on Bugzilla 3.6 below. If you’re installing a version prior to 3.6, you’ll need to do this: After running checksetup.pl (and after everytime you ever run checksetup.pl) you’ll need to run the following commands to set some additional permissions to let Bugzilla work under suexec on Dreamhost:

    for i in docs graphs images js skins; do find $i -type d -exec chmod o+rx {} \;?; done
    for i in jpg gif css js png html rdf xul; do find . -name \*.$i -exec chmod o+r {} \;?; done
    find . -name .htaccess -exec chmod o+r {} \;
    chmod o+x . data data/webdot

That should be it. Launch your web browser and point it to http://www.myOwnDomain.com/bugs/bugzilla-###. You should see the Bugzilla front page.

This post is password protected. To view it please enter your password below:

Password:

Mozilla users who enjoy a personalized skin are often quick to choose one from the many popular themes available. Most of the popular themes are dark, focusing on space, stars, or underwater colors to minimize energy use and maximize the ease of use. The new default template is designed with all kinds of users in mind, with the hope that with a somewhat neutral, but clearly Mozilla themed color scheme, wiki users will find the site easy to use as well as easy on the eyes.

Mozilla wiki users will find the new skin available online now, and users who remember the previous default skins will be pleasantly surprised with this latest change. The wiki.mozilla.org default templates of the past have also focused more on ease of use rather than flashy or stunning graphics, and the new default skin is no exception. But everyone enjoys an update, at least once in a while, and wiki.mozilla.org users will find that the new default template provides a fresh face with a sensible and thoughtful visual scheme. If you have been looking forward to a change at wiki.mozilla.org, the new default template has arrived. Take the time to check it out!

Besides the State of the Union Address, Mozilla.org has had some other news of dramatic political messages that were shared with users around the world. In solidarity with the high profile internet black-outs held by Wikipedia and others, the Mozilla Firefox start page was black and contained an important message about the SOPA/PIPA bills in Congress. The main complaint of all sites that took part in the black out is that these two bills effectively allow internet censorship. The idea was to educate users about the potential threat to usability, without reducing the access that users expect from Mozilla.

Over at wiki.mozilla.org, a new default template has been released, somewhat big news from the wiki world. Users and web designers will be excited to see the updated image, which combines usability with sleek and thematic design.

The other most recent news from Mozilla that has been exciting for everyone involved is the conclusion of the Mozilla Firefox Challenge which raised more than $680,000 from people all around the world. The donations are another example of how individual action can cause global impact, something Mozilla.org exemplifies with the free and accessible web browsing tools.

What attracted you to Mozilla and how did you get involved?

Back in 2001, when Netscape 6 seemed to be the only browser around, I stumbled on Mozilla for the first time. The product seemed so similar to Netscape, and yet they were an open source project with a pretty interested following. I became involved in the discussions and news groups, asking and answering the questions that were floating around at the time, about use, design, and the direction of the browser called Phoenix, which is now known as Firefox. I enjoy helping people, especially with things that I understand and care about. My enjoyment and involvement was clearly more than just a side hobby.

Do most people who are involved with Mozilla feel passionately about the products?

There is an inherent magic in the Mozilla product suite. Most people who get involved are drawn to the mission and believe strongly in the products. Take SUMO, for example. As a support and update mechanism it works incredibly well. Even the first crude release back in 2007 was such a significant step up from the old support system that people began to take notice. Firefox support changed dynamically and we have the input of many dedicated Mozilla fans to thank.

What is the best interview with David Tenser question you’ve been asked as Mozilla Support lead?

People like to ask about hobbies. I think that shows how strong the Mozilla community is – we do it because we love to do it and it shows. My other hobby is photography, by the way.

This post is password protected. To view it please enter your password below:

Password:

This post is password protected. To view it please enter your password below:

Password:

This post is password protected. To view it please enter your password below:

Password:

The latest State of the Union Address gave one of the best examples of how localization plays a role in everything we do these days. As software developers and engineers plan their strategies for making the most of their products, they are increasingly looking to localization to bring their ideas to the world. As the President spoke on Tuesday night, live commentary was broadcast along with instant translations from individuals around the world. Crowd sourcing combined with localization is changing the way we think of software development and communication.

The importance of localization these days is similar to the way the internet itself was important when it first became available for public use. Sharing information across the planet without the time delays of the past changed the world forever. At first, this was a revolution for people who were used to dealing with each other, and usually for dealing with each other in a common language. Today, the possibility of sharing with anyone, no matter their language, culture, or location makes software development even more exciting and meaningful than ever before.

As we develop tools that can be used across countries, providing localization and localization support becomes more and more of a priority. Software that does not offer localization will hit a dead end where competitors can tap into many other markets. With the availability of crowd sourcing and free technology, there is no excuse for neglecting the importance of localization these days.

In the long run, communication technologies are what make the world a smaller place. The fact that we can share ideas around the world in a few seconds is revolutionary, and the only tool needed these days is some form of localized communication tool. Localization is one of the most important aspects of any tool being developed today.