Grab important info to one way links – welcome to your personal guide.

Dimensions and design
BlackBerry Storm is smaller vs iPhone but somehow thicker. iPhone looks IMHO more stylish.
+1 for iPhone

Screen
Like iPhone BlackBerry Storm has a bright and clear touch screen, but has a click-push button effect that brings a new tactile experience to a Gadget and Gizmos world.
+1 for BlackBerry Storm

Interface
Both iPhone and BlackBerry Storm have touch screen user interfaces with horizontal and portrait views (both auto rotating), scrolling, pan and zoom options. iPhone’s interface looks somehow clear and better.
+1 for iPhone

Dialing
Similar to iPhone dialing screen with quick contacts dialing, BlackBerry Storm has a voice dialing option.
+1 for BlackBerry Storm

Messaging
As iPhone BlackBerry Storm has a full bunch of messaging options, but has no iPhone’s biggest gaps – it has Copy-Paste option, message forwarding and delivery confirmation reports with no additional manipulations needed.
+2 for BlackBerry Storm

Browser
BlackBerry Storm is equipped with a real-HTML browser quite similar iPhones. It has zooming options and page cashing. Actually at the moment there is no information if Storm’s browser is Flash capable while iPhone is known as none.

Media
Both BlackBerry Storm and iPhone have music and video players, BlackBerry Storm is a little more useful while allows you to upload you MP3 stuff with no need to have iTunes or smht on the PC you are downloading from that makes the process easier. Actually, if you are iTunes fan – it’s a bug +Plus for buying iPhone decision, but if you aren’t – ability to get stuff not only by “iTuned” PC or Mac will make you choose BlackBerry Storm.

Apps
BlackBerry Storm comes with a lot of preinstalled stuff. Well, it can be quite enough for you and you’ll never need for smth else. iPhone’s big +Plus it’s, sure, AppStore. BlackBerry-lovers will argue that it has a lot of applications for BlackBerry available, but friendly speaking, it is incomparable with Apple’s AppStore.
+2 for iPhone

Camera
BlackBerry Storm allows to make 3.2MPx vs iPhone out-of-date 2.0 MPx pictures and it records video. I should mention that BlackBerry Storm has built-in flash that makes this gadget’s camera much more useful.
+2 for BlackBerry Storm

Maps
Both devices has maps using built-in Gps.

Interfaces
Both devices has mini-jack phones connector, BlackBerry Storm has microSD(TM)/SDHDA slot that gives you ability not just to increase available memory capacity (iPhone is 16Gb maximum), but use your computer card reader to simply download / upload all your stuff. And, sure, you can have more than one card (it’s 16Gb cards available in the market, but, hope, it will take not much time for 32 and more).
+1 for BlackBerry Storm

Availability and Prices
Both gadgets are about $200 with all-that d**n plans, but BlackBerry Storm gives you ability to use any other 3G network – if its actually critical for you.

The Conclusion
Well, simply counting we’ll get +4 for iPhone vs +7 for BlacvBerry Storm. But… what are these “pluses” equal? iPhone pluses for design, user interface, iTunes and AppStore vs BlackBerry Storm – for camera, copy-paste, messaging and flash card. It’s up to you what do you need more.

Read handy recommendations about cara membuat website – study hyperlinked page.

This (long) weekend, many WordPress users and developers (including half the core team) will be in Austin, TX for South by Southwest. Matt Mullenweg, Ryan Boren, Mark Jaquith and I will all be there, so say hello if you’re there, too. In the spirit of all this WordPress community connecting, I’ll be posting here every day during SxSW with information about the new contribution opportunities we’re creating. Each post will cover one or more of the following:

• Development (of course)
• QA
• Documentation
• Ideas and Opinions
• User Experience
• Graphic Design
• Accessibility
• Usability Testing
• WordPress.tv
• Community Organizing

Since the first thing people think of when they think of contributing to WordPress is PHP development, we’ll start there.

The code (which is poetry) is the meat of the application, so it makes sense that the most opportunities to contribute will continue to fall in this area. Trac is always filled with tickets that need patches, patches that need testing, and issues that need some creative developer thinking/collaboration to find the right solution to a problem that has us going in circles.

If you are proficient in PHP, consider looking through the tickets (especially the ones marked “bug,” since they should get higher priority) and writing a patch for one of them. If you’ve got more advanced skills, consider writing a patch for one of the more complex tickets, or offering corrections to a patch submitted by someone else (if needed). If you don’t trust your coding skills but know your way around the application files, look for tickets tagged has-patch and test the patches in as many browsers as you can, posting your results afterward in the ticket thread.

If you find a bug in the course of your daily use of WordPress, report it. First, check Trac to see if the issue already has a ticket. You could also scan the archives of the wp-testers list to see if people have been talking about the bug, or email the list yourself to see if anyone has any information on the problem. If these actions don’t bear fruit, start a new ticket in Trac (you’ll need to create a login to do this). Be as detailed as you can about the issue, and don’t forget to make the proper selections from the metadata dropdown menus. Just in case anyone is unsure of how to make these selections…

Use the severity field with caution. Most bugs will be of normal severity. Marking a bug as high severity will not necessarily speed up development, and if it turns out that you’ve marked a bug’s severity incorrectly it may even slow down development.

Priority will usually be normal. Leave it to the more senior developers to change the status to a higher priority, as they are familiar with all the tickets and Trac and will be better able to assess the priority in relation to other tickets.

Ticket type. This is one of most misused fields, with many people marking tickets as defects that should not be. To address this, here’s a reminder of the ticket types and their intended uses. Your choices are: defect (bug), enhancement, feature request, and task (blessed).

• Defect (bug). Something is broken. You know how the feature is supposed to work (if you’re unsure, check the Codex or ask in the dev channel), but something has gone awry that needs to be fixed.
• Enhancement. Something is awkward or slow and could be designed or coded better without overhauling the function or screen design. Please don’t mark something as a defect (bug) if it is really an enhancement.
• Feature request. If there’s something that could be improved that would require significant restructuring of code or screen design, it should be marked as feature request rather than enhancement. Please note: this is not really the place to request features that are not currently in WordPress. Please continue to use the Ideas forum to suggest new features. The core developers will add new feature requests to Trac as they review the Ideas forum with each release cycle.
• Task (blessed). This type indicates approval from the core development team. Only core developers should use this selection. If you mark something as Task (blessed) yourself, you will have bad karma.

Bug Hunts*! If you have checked the Codex page for bug hunts lately, you’ll notice it’s been awhile since there was one. No more! Official bug hunts, sprints for finding and fixing bugs, will be brought back on a regular basis. The first one will be announced soon, possibly next week, to try and tackle the bug tickets related to widgets. (No need to wait, though, there are hundreds of open tickets in the 2.8 milestone just waiting for a kind developer to pay them some attention.)

As always, contributing developers can communicate with each other and with the core team in the #wordpress-dev IRC channel at irc.freenode.net, on the wp-hackers list, and in the ticket threads on Trac. Regular developer chats in IRC will be returning to Wednesdays at noon (Pacific time) starting next week.

[* - I used to love the bug hunt challenge in Space Cadet 3D Pinball back in the days of Windows 95]

I hope i can continue to create as interesting posts as the previous owner did.

I am going to have some great new free wrodpress themes available really soon.

Thanks everyone

Basically, the contest is to create a plugin, widget, mash up, hack, or other variety of web application that helps people find and share opportunities to take action. The grand prize is 50 benjis, and the best WordPress plugin will also be featured in the Plugin Directory. But the real prize is spreading a little more love in the world.

Click here for all the details.

“Writing a Plugin” in the WordPress Codex is where I got started when I needed to get hooked in to WordPress. Others might like to grab one of the over 4,000 open source WordPress plugins and tweak the source. If in need of a little help, the Plugins and Hacks forum is full of friends to assist you wrap your head around the code or debug a problem. Social Actions also has provided some developer resources.

Let’s show them how we change the web the WordPress way!

No longer. We’re now using Sphinx (a “free open-source SQL full-text search engine”) to power search on the Plugins Directory both from the website and from within your blog’s admin (Plugins → Add New).

It works much better. There are a few oddities floating around (our fault not sphinx’s) that we’ll be cleaning up shortly, but we’re happy enough with it on the whole to start letting everyone else use it

Currently, the search only indexes the plugin’s title and description/installation/FAQ/etc. (from the plugin’s readme.txt file), but we’ll be adding things like authors and tags soon.

You may have noticed that we went much longer than usual to release this .1 update. We’re very proud of this fact because it’s a testament to the testing all of you contributed prior to the release of 2.7 which helped make it the most bug-free release we’ve had.

Consult the list of fixed tickets and the full set of changes between 2.7 and 2.7.1 for details.

Finally partly due to the stability of the 2.7 we’ve decided to push back 2.8 a few more weeks so we can bring in a few more speed optimizations, taxonomy enhancements, and new theme features. We also need to figure out which jazz musician to name the release after.

Right now, the lead developers are thinking the top priorities for 2.8 will be widget management, theme browser/installer and performance upgrades. The rest of the development time will be taken up with bug tickets and additional features/enhancements from a prioritized list. To that end, we’ve posted a new survey for you to help us prioritize features for 2.8. The list pulls from the developers’ “2.7 leftovers” list as well as the most popular features from the Ideas forum. Just rank each feature and tell us your top pick (up to three). You also have the option of adding comments or additional suggestions, but this is not mandatory. For your response to count, you must rank all of the features in the list. The survey has only one page.

Note that media features are not included in this list as we will be posting a separate survey for media-specific features soon.

Cast your votes any time this week, but as always the sooner the better. This survey will close at noon on December 31, 2008 UTC.

In the new year, we will be reviving scheduled IRC developer chats, where the lead developers will discuss the week’s progress on feature development, providing opportunities for people to ask questions or make suggestions. These will be held early in the day on Wednesdays (U.S. Wednesday), and the specific time will be posted here on the development blog once it’s been finalized.

As a related aside, we spent a significant amount of time during 2.7 development sifting through Trac tickets that really shouldn’t have been there. Feature ideas and requests do not belong in Trac, they belong in the Ideas forum. Please reserve Trac for reporting bugs and things that need fixing (typos, code enhancements, etc.). If you are asking for a new UI, a new feature, or a new approach to coding something, that’s not an enhancement, it’s a new feature. New features will be entered into Trac by developers once it has been determined that the feature should be included in core. To help speed up development, moving forward we will close Trac tickets that are actually feature requests, with the comment that they should be posted in the Ideas forum instead. Please help the developers maximize their time by following this guideline.

Thanks for your help!

It’s not quite that time yet, but we’re as close as we’ve ever been, hence the immediate availability of 2.7 Release Candidate 2, or RC2 for short.

Of course if you were already testing 2.7, you can just use the built-in core updater (Tools > Upgrade) to download and install RC2 for you (and later upgrade you to the final release when it’s available) but if not you can use the download link above.

We feel this release is pretty much exactly what we’re going to ship as 2.7, barring any final bugs or polish tweaks that you report or we find.