Microsoft and Open Source?????

Have you heard this news yet??? Changes seem to be happening in the Windows arena as curtains seem to be falling. Microsoft finally are ok with lets say, “peeping inside the Window”! (People familiar with open source will get this one!). I don’t need to say much to explain whats happening , but if you’ve clicked on that link already you’ve got my point.

Microsoft is embracing open source finally and Windows compatible open source software is ready to hit the market. While Microsoft has joined hands with open source, their diplomatic perspective on open source kind of puzzles me… While according to Microsoft, “Open source is neither an industry fad, nor a magic bullet. Rather, the development methods commonly encompassed by the term open source have provided customers and developers with additional options among many in the technology ecosystem.“(read more here) the fact that they have opened doors (or rather say opened Windows!) is alarming!

I think this is a big step for open source that it will finally be able to reach a lot more people through the Windows platform. Though the focus maybe more towards business and enterprise solutions today, I don’t see it far away when a layman will be open to Open Office! However the other side of the coin strikes a little harder in my mind as I wonder if this is a game played by Microsoft to actually monopolize the open source market too, for all you know we might have a Microsoft Office for Linux very soon.

But against all odds I think its a big step taken for open source specially with the announcement of the Spike Ignited Drupal Stack for Windows . Being an employee of SpikeSource, I am very proud today!

Quick Bugzilla Tutorial

Bugzilla is a “Bug Tracking System” that can efficiently keep track of outstanding bugs in a product. Multiple users can access this database and query, add and manage these bugs. Bugzilla essentially comes to the rescue of a group of people working together on a product as it enables them to view current bugs and make contributions to resolve issues.

 

Its basic repository nature works out better than the mailing list concept and an organized database is always easier to work with.

 

The bugzilla utility basically allows you to do the following:

• Add a bug into the database

• Review existing bug reports

• Manage the content

 

Bugzilla is organised in the form of bug reports that give all the information you need about a particular bug. A bug report would consist of the following fields.

 

• Product–>Component

• Assigned to

• Status (New, Assigned, Fixed etc)

• Summary

• Bug priority

• Bug severity (blocker, trivial etc)

• Bug reporter

 

A Bug’s Life:

 

Once a new bug is entered, it goes through a number of states before the issue is resolved. A bug’s life as we term it has the following states an transitions:

 

1. unconfirmed

2. new (this state is acquired once the bug is confirmed)

3. assigned (once a developer takes possession of the bug)

4. resolved (when the development with the bug is finished)

5. reopen (when the solution is not satisfactory)

6. verified (once the solution is verified and satisfactory)

7. closed

For a better understanding view: http://www.bugzilla.org/docs/2.18/images/bzLifecycle.png

 

Bugzilla Query Page:

 

The Bugzilla search page allows you to search for a particular bug. The search can be based on the product, status or description. To refine your search an advanced search option is available.

 

The result page lists the bugs based on relevance to the search.

 

Adding a new bug:

 

In order to add a new bug, or even query, you need to have an account which you log into.

 

• Click on “Enter New Bug”. This takes you to a page containing the list of products.

• Select the relevant product.

• Now you can make your report more specific by selecting the component, target etc. At this point you are the “reporter” of that bug and the status of that bug is set to NEW.

• You can assign the bug to a particular person and provide his email id in the “Assign to” field. Appropriately you can add people in CC also. Alternatively, you can use it as a reporting mechanism where you don’t assign the bug to anyone but just add the right people who could solve your problem in the CC list. Anybody who wishes to take it up can re-assign it to himself later.

• Give a one-line summary and a short description of the bug.

• It is a good practice to use the keywords listed.

• Once finished, click on “commit” to file your report.

 

Managing your bug report:

 

• If you want to resolve a bug that is assigned to, you need to first accept the bug and change its state to ASSIGNED. Then you can resolve it.

• Commenting option is also available where you can make suggestions, if any.

• If you want to resolve bugs not assigned to you, re-assign it to yourself and do so.

   

For a complete Bugzilla tutorial use this link:

http://www.bugzilla.org/docs/2.14/html/index.html

 

 

Case-sensitivity in Google

Recently i was searching for some stuff on the net and I happened to realize this… The Google search engine, awesome tool and probably the most useful thing made since the bulb was invented had something missing!

I was looking for some stuff, lets assume, “Helloworld” and google gave me results for “helloworld” and “HelloWorld” and “Helloworld”… So i guess the Google Search Engine is not case-sensitive… I think if the engine provides case-sensitivity, the results could be more relevant to the user’s needs.

As far as i tried, i could only conclude that this kinda search cannot be done with google, however i’m not sure, but i’d love to know…

Does anybody know how case-sensitive strings can be searched with google?