<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WordPressMy.com</title>
	<atom:link href="http://wordpressmy.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpressmy.com</link>
	<description>Just another  weblog</description>
	<lastBuildDate>Sat, 28 Jan 2012 16:28:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Year of the Meetup</title>
		<link>http://wordpressmy.com/2012/01/28/year-of-the-meetup/</link>
		<comments>http://wordpressmy.com/2012/01/28/year-of-the-meetup/#comments</comments>
		<pubDate>Sat, 28 Jan 2012 16:28:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/28/year-of-the-meetup/</guid>
		<description><![CDATA[We hereby declare 2012 as the Year of the WordPress Meetup. You&#8217;ll want to get in on this action. meet·up mēt-əp noun A meeting, especially a regular meeting of people who share a particular interest and have connected with each other through a social-networking Web site: a meetup for new moms in the neighborhood; a meetup to plan the trip; a meetup for WordPress users.1 So what is a WordPress Meetup? Basically, it&#8217;s people in a community getting together &#8212; meeting up &#8212; who share an interest in WordPress, whether [...]]]></description>
			<content:encoded><![CDATA[<p>We hereby declare 2012 as the Year of the WordPress Meetup. You&#8217;ll want to get in on this action.</p>
<blockquote><p><strong>meet·up</strong> <strong>mēt</strong>-əp <em>noun</em><br />
A meeting, especially a regular meeting of people who share a particular interest and have connected with each other through a social-networking Web site: <em>a meetup for new moms in the neighborhood; a meetup to plan the trip; a meetup for WordPress users.</em><sup>1</sup></p>
</blockquote>
<p>So what is a <em>WordPress Meetup</em>? Basically, it&#8217;s people in a community getting together &#8212; meeting up &#8212; who share an interest in WordPress, whether they be bloggers, business users, developers, consultants, or any other category of person able to say, &#8220;I use WordPress in some way and I like it, and I want to meet other people who can say the same.&#8221; Meetups come in different shapes and sizes, but they all carry the benefit of connecting you with potential collaborators and friends, and helping you learn more about what you can do with WordPress. Here are some of the common types of WordPress meetups:</p>
<ul>
<li>Hang out and work on your WordPress sites together</li>
<li>Social/happy hour type gatherings</li>
<li>Mini-lectures/presentations</li>
<li>Developer hacking meetups</li>
<li>Show &amp; tell of how group members are using WordPress</li>
<li>Formal instruction on how to use WordPress</li>
<li>Lecture series (possibly with visiting speakers)</li>
<li>Genius bar/help desk</li>
</ul>
<p>There&#8217;s no prescribed format, as each local group can decide for itself what they want to do. Some groups mix it up from month to month, while others have multiple events each month to satisfy the needs of their community.</p>
<p>The tough part? Running a popular group takes time and money. Just as we worked last year to remove the financial burden for <a href="http://wordcamp.org">WordCamp</a> organizers and provide logistical support so they could focus more on their event content and experience, we want to start extending that kind of support to meetup groups as well. We don&#8217;t want it to cost anything for someone to run a WordPress meetup, or to attend one &#8212; building local communities should be as free as WordPress itself!</p>
<p>Since there are so many more meetups than there are WordCamps, we&#8217;re going to start with the cost that is the same for every group: meetup.com organizer dues. We&#8217;re setting up an official WordPress account on <a href="http://meetup.com">Meetup.com</a> right now, and over the next couple of weeks will be working with existing meetup group organizers, people who want to start a new meetup group, and the helpful folks at Meetup.com to put this program in place. WordPress meetup groups that choose to have their group become part of the WordPress account will no longer pay organizer dues for that group, as the <a href="http://wordpressfoundation.org">WordPress Foundation</a> will be footing the bill.</p>
<p>This is exciting for several reasons. First, it means local organizers who are giving something back to the project by way of their time won&#8217;t also have shell out $12-19/month for the privilege. That alone is a big step. Second, it will open the door to more events and leaders within a community, since leadership and event planning won&#8217;t need to be tied to &#8220;owning&#8221; the meetup group. Third, more active meetup groups means more WordCamps, yay!</p>
<p>In addition to the financial aspects, we&#8217;ll be working on ways to improve social recognition of meetup activity by incorporating feeds from the official meetup groups into the WordPress.org site, and including meetup group participation in the activity stream on your <a href="http://profiles.wordpress.org/">WordPress.org profile</a>.<sup>2</sup> I&#8217;m also hoping we can do something around providing video equipment to meetup groups (like we already do for WordCamps) to record presentations and tutorials that can be posted to <a href="http://wordpress.tv">WordPress.tv</a>, helping meetup groups offer WordPress classes in their community, and getting involved with mentoring WordPress clubs at local schools and universities. Oh, and we&#8217;ll send out some WordPress buttons and stickers to the groups that join in, because everyone loves buttons and stickers.</p>
<p>We&#8217;re also putting together some cool resources for people who want to start a new meetup group. There will be a field guide to getting started and some supplies to help you get your group going, and a forum for organizers to talk to and learn from each other.</p>
<p>Over time, we&#8217;ll be talking to organizers and looking at what other expenses we can absorb and what other support we can provide to local groups. For now, we&#8217;re starting with the organizer dues. If you currently run a WordPress meetup group (whether you are using Meetup.com or not) or would like to start a WordPress meetup group in your area, please fill out our <a href="http://wordpressdotorg.polldaddy.com/s/wordpress-meetup-groups">WordPress Meetup Groups survey</a>. Filling in the survey doesn&#8217;t obligate you to join the official group, it just gives us a starting point to a) find out what groups are around/interested, and b) get some information on existing groups and their expenses and needs. Meetup.com will contact the group organizers who&#8217;ve said they&#8217;d like to join the new program, and will walk them through the logistics of the change and answer questions before helping them to opt-in officially.</p>
<p>So, if you currently run a WordPress meetup group, or you would like to start one, please  fill out our <a href="http://wordpressdotorg.polldaddy.com/s/wordpress-meetup-groups">WordPress Meetup Groups survey</a>. I can&#8217;t wait to see more meetups!</p>
<p><strong>1</strong> &#8211; Adapted from <a href="http://dictionary.reference.com/browse/meetup">&#8220;meetup&#8221; definition at dictionary.com</a>.<br />
<strong>2</strong> &#8211; Didn&#8217;t know about profiles? Check out http://profiles.wordpress.org/users/yourwordpressdotorgusernamehere (put in the username you use in the WordPress.org forums) to see yours!</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/28/year-of-the-meetup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internet Blackout Day on January 18</title>
		<link>http://wordpressmy.com/2012/01/18/internet-blackout-day-on-january-18/</link>
		<comments>http://wordpressmy.com/2012/01/18/internet-blackout-day-on-january-18/#comments</comments>
		<pubDate>Wed, 18 Jan 2012 00:55:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/18/internet-blackout-day-on-january-18/</guid>
		<description><![CDATA[WordPress.org is officially joining the protest against Senate Bill 968: the Protect IP Act that is coming before the U.S. Senate next week. As I wrote in my post a week ago, if this bill is passed it will jeopardize internet freedom and shift the power of the independent web into the hands of corporations. [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress.org is officially joining the <a href="http://sopastrike.com/">protest against Senate Bill 968: the Protect IP Act</a> that is coming before the U.S. Senate next week. As I wrote in <a title="Help Stop SOPA/PIPA" href="http://wordpress.org/news/2012/01/help-stop-sopa-pipa/">my post a week ago</a>, if this bill is passed it will jeopardize internet freedom and shift the power of the independent web into the hands of corporations. We must stop it.</p>
<p>On January 18, 2012 many sites around the web &#8212; from small personal blogs to internet institutions like <a href="http://mozilla.org">Mozilla</a>, <a href="http://en.wikipedia.org/wiki/Wikipedia%3ASOPA_initiative/Action">Wikipedia</a>, <a href="http://blog.reddit.com/2012/01/stopped-they-must-be-on-this-all.html">reddit</a>, and <a href="https://twitter.com/#!/benhuh/status/157538541155516416">I Can Has Cheezburger?</a> &#8211; will be going dark in protest and to drive their visitors to sites like <a href="http://americancensorship.org">americancensorship.org</a> to take action and help fight the passage of the Protect IP Act. So will WordPress.org.</p>
<p>If you want to join the protest by blacking out your WordPress site or applying a ribbon, there is now a variety of <a href="http://wordpress.org/extend/plugins/tags/sopa">blackout plugins in the WordPress.org plugins directory</a>. While joining the protest in this manner is laudable, please don&#8217;t forget to also make those phone calls to U.S. Senators &#8212; they&#8217;re the ones with the voting power.</p>
<ul>
<li><a href="http://wordpress.org/extend/plugins/tags/sopa">Get a protest plugin</a></li>
<li><a href="http://americancensorship.org">Take action at americancensorship.org</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/18/internet-blackout-day-on-january-18/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Help Stop SOPA/PIPA</title>
		<link>http://wordpressmy.com/2012/01/11/help-stop-sopapipa/</link>
		<comments>http://wordpressmy.com/2012/01/11/help-stop-sopapipa/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 11:45:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/11/help-stop-sopapipa/</guid>
		<description><![CDATA[You are an agent of change. Has anyone ever told you that? Well, I just did, and I meant it. Normally we stay away from from politics here at the official WordPress project &#8212; having users from all over the globe that span the political spectrum is evidence that we are doing our job and [...]]]></description>
			<content:encoded><![CDATA[<p>You are an agent of change. Has anyone ever told you that? Well, I just did, and I meant it.</p>
<p>Normally we stay away from from politics here at the official WordPress project &#8212; having users from all over the globe that span the political spectrum is evidence that we are doing our job and democratizing publishing, and we don&#8217;t want to alienate any of our users no matter how much some of us may disagree with some of them personally. Today, I&#8217;m breaking our no-politics rule, because <a href="http://americancensorship.org/">there&#8217;s something going on</a> in U.S. politics right now that we need to make sure you know about and understand, because it affects us all.</p>
<p>Using WordPress to blog, to publish, to communicate things online that once upon a time would have been relegated to an unread private journal (or simply remained unspoken, uncreated, unshared) makes <strong>you</strong> a part of one of the biggest changes in modern history: the democratization of publishing and the independent web. Every time you click Publish, you are a part of that change, whether you are posting canny political insight or a cat that makes you LOL. How would you feel if the web stopped being so free and independent? I&#8217;m <del>concerned</del> freaked right the heck out about the bills that threaten to do this, and as a participant in one of the biggest changes in modern history, you should be, too.</p>
<p>You may have heard people talking/blogging/twittering about SOPA &#8212; the Stop Online Piracy Act. The recent <a href="http://godaddyboycott.org/">SOPA-related boycott of GoDaddy</a> was all over the news, with many people expressing their outrage over the possibilities of SOPA, but when I ask people about SOPA and its sister bill in the Senate, PIPA (Protect IP Act), many don&#8217;t really know what the bills propose, or what we stand to lose. If you are not freaked out by SOPA/PIPA, please: for the next four minutes, instead of checking Facebook statuses, seeing who mentioned you on Twitter, or watching the latest episode of Sherlock*, watch this video (by <a href="http://fightforthefuture.org/">Fight for the Future</a>).</p>
</p>
<p>Some thoughts:</p>
<ul>
<li>In the U.S. our legal system maintains that the burden of proof is on the accuser, and that people are innocent until proven guilty. This tenet seems to be on the chopping block when it comes to the web if these bills pass, as companies could shut down sites based on accusation alone.</li>
<li>Laws are not like lines of PHP; they are not easily reverted if someone wakes up and realizes there is a better way to do things. We should not be so quick to codify something this far-reaching.</li>
<li>The people writing these laws are not the people writing the independent web, and they are not out to protect it. We have to stand up for it ourselves.</li>
</ul>
<p>Blogging is a form of activism. You can be an agent of change. Some people will tell you that taking action is useless, that online petitions, phone calls to representatives, and other actions won&#8217;t change a single mind, especially one that&#8217;s been convinced of something by lobbyist dollars. To those people, I repeat the words of Margaret Mead:</p>
<blockquote><p>Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it is the only thing that ever has.</p>
</blockquote>
<p>We are not a small group. More than 60 million people use WordPress &#8212; it&#8217;s said to power <a href="http://w3techs.com/technologies/overview/content_management/all">about 15% of the web</a>. We can make an impact, and you can be an agent of change. Go to <a href="http://americancensorship.org/">Stop American Censorship</a> for more information and a bunch of ways you can take action quickly, easily, and painlessly. The Senate votes in two weeks, and we need to help at least 41 more senators see reason before then. Please. <a href="http://americancensorship.org/">Make your voice heard</a>.</p>
<p><em>*Yes, the latest episode of Sherlock is good. Stephen Moffatt + Russell Tovey = always good</em></p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/11/help-stop-sopapipa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.3.1 Security and Maintenance Release</title>
		<link>http://wordpressmy.com/2012/01/04/wordpress-3-3-1-security-and-maintenance-release/</link>
		<comments>http://wordpressmy.com/2012/01/04/wordpress-3-3-1-security-and-maintenance-release/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 04:49:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/04/wordpress-3-3-1-security-and-maintenance-release/</guid>
		<description><![CDATA[WordPress 3.3.1 is now available. This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K. and the Go Daddy security team for responsibly disclosing the bug to our security team. Download 3.3.1 or visit [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress 3.3.1 is now available. This maintenance release fixes <a href="http://core.trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=3.3.1&amp;group=resolution&amp;order=priority">15 issues</a> with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K. and the Go Daddy security team for responsibly disclosing the bug to our security team.</p>
<p><a href="http://wordpress.org/download/">Download 3.3.1</a> or visit Dashboard &rarr; Updates in your site admin.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/04/wordpress-3-3-1-security-and-maintenance-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.3 Beta 2</title>
		<link>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-2/</link>
		<comments>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-2/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-2/</guid>
		<description><![CDATA[Changes since Beta 1: Updated the Blue theme Fixed IE7 and RTL support Improved flyout menu styling and fixed several glitches Finished the Pointers implementation Landed the dashboard Welcome box for new installs Improved contextual help styling Tweaked the admin bar a little more Fixed a bunch of bugs Consult the full change log  for [...]]]></description>
			<content:encoded><![CDATA[<p>Changes since Beta 1:</p>
<ul>
<li>Updated the Blue theme</li>
<li>Fixed IE7 and RTL support</li>
<li>Improved flyout menu styling and fixed several glitches</li>
<li>Finished the Pointers implementation</li>
<li>Landed the dashboard Welcome box for new installs</li>
<li>Improved contextual help styling</li>
<li>Tweaked the admin bar a little more</li>
<li>Fixed a bunch of bugs</li>
</ul>
<p>Consult the <a href="http://core.trac.wordpress.org/log/trunk/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=&amp;stop_rev=18939&amp;limit=100">full change log</a>  for details, and see the <a href="http://wordpress.org/news/2011/10/wordpress-3-3-beta-1/">Beta 1 announcement</a> for information on how to help test Beta 2.</p>
<blockquote><p>Welcome for the new –<br />
3.3 at beta 2.<br />
(IE7, woo!)</p></blockquote>
<p>Download <a href="http://wordpress.org/wordpress-3.3-beta2.zip">3.3 Beta 2</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.3 Beta 3 Available</title>
		<link>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-3-available/</link>
		<comments>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-3-available/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-3-available/</guid>
		<description><![CDATA[Testers, Beta 3 is now available! You know the drill: use a test install, see what you can break, and report any bugs you find. There have been 200 commits since Beta 2, but at this point, betas are not adding new features — it’s all about fixing bugs, making things a little prettier, and [...]]]></description>
			<content:encoded><![CDATA[<p>Testers, Beta 3 is now available! You know the drill: use a test install, see what you can break, and report any bugs you find. There have been 200 commits since Beta 2, but at this point, betas are not adding new features — it’s all about fixing bugs, making things a little prettier, and editing text strings.</p>
<p>As always, plugin and theme authors, PLEASE test your code against the beta so you can catch any incompatibilities now rather than after your users update their WordPress installation and find bugs for you. <strong>This time we really mean it, especially if your plugin uses jQuery.</strong> We’ve now updated to jQuery 1.7 in core, so please please pretty please check your plugins and themes against beta 3.</p>
<p>These silly haikus –<br />
With so many releases,<br />
I run out of words.</p>
<p>Download <a href="http://wordpress.org/wordpress-3.3-beta3.zip">WordPress 3.3 Beta 3</a> now.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-3-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Taking WordPress to War</title>
		<link>http://wordpressmy.com/2012/01/02/taking-wordpress-to-war/</link>
		<comments>http://wordpressmy.com/2012/01/02/taking-wordpress-to-war/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/taking-wordpress-to-war/</guid>
		<description><![CDATA[Today is the eleventh day of the eleventh month of the (20)eleventh year, and in several parts of the world, it is a holiday related to war. In the U.S., where I live, it is Veterans Day, which honors military veterans. In much of Europe, today is Armistice Day or Remembrance Day, commemorating the armistice signed at [...]]]></description>
			<content:encoded><![CDATA[<p>Today is the eleventh day of the eleventh month of the (20)eleventh year, and in several parts of the world, it is a holiday related to war. In the U.S., where I live, it is Veterans Day, which honors military veterans. In much of Europe, today is Armistice Day or Remembrance Day, commemorating the armistice signed at the “eleventh hour of the eleventh day of the eleventh month” of 1918 that ended the fighting on the Western Front in World War I.</p>
<p>Whether serving in the military, living in an area of unrest or attack, having friends or family in the fray, or just being human enough to think war sucks (there’s really no gentler way to say that, is there?), war impacts most people in the world today.</p>
<p>The mission of WordPress is to democratize publishing. Sometimes we’re fortunate enough for that to mean providing a platform for communication that helps people work toward peace in their communities and around the world. Sometimes it means providing a platform for keeping people informed and aware of the other things that are happening around the world, including the horror of wars and revolutions.</p>
<p>At WordCamp San Francisco in August, one of the most popular and well-respected sessions was led by Teru Kuwayama of <a href="http://basetrack.org/">Basetrack.org</a>. On this day of remembrance, I thought it would be good to share the video of his presentation. Not only is it a very cool example of how WordPress can be used in unexpected ways (this is not your <del datetime="2011-11-11T14:23:43+00:00">father’s Oldsmobile</del> usual blog), it’s a reminder of how much work still needs to be done to move from war to peace. So here is <em>Taking WordPress to War: Basetrack.org</em>. Peace out, yo.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/taking-wordpress-to-war/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wherefore Art Thou, Widgets?</title>
		<link>http://wordpressmy.com/2012/01/02/wherefore-art-thou-widgets/</link>
		<comments>http://wordpressmy.com/2012/01/02/wherefore-art-thou-widgets/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/wherefore-art-thou-widgets/</guid>
		<description><![CDATA[We need your opinion! One of the features we&#8217;re adding to WordPress 3.3 (currently in beta 3) is intended to reduce widget pain. Say you&#8217;re using Theme A and you have a handful of widgets set up. You switch to Theme B, and it has different widget areas, so you add/remove/edit your widgets. Then you [...]]]></description>
			<content:encoded><![CDATA[<p>We need your opinion! One of the features we&#8217;re adding to WordPress 3.3 (currently in beta 3) is intended to reduce widget pain. Say you&#8217;re using Theme A and you have a handful of widgets set up. You switch to Theme B, and it has different widget areas, so you add/remove/edit your widgets. Then you realize that you hate Theme B. &#8220;This theme doesn&#8217;t represent my innermost soul!&#8221; you cry to the heavens. You switch back to Theme A, but because it had different widget areas, now your widgets are messed up. Argh, right? Not for long!</p>
<p>Imagine being able to change themes and modify widgets as needed, and if you decided to go back to your old theme, it would return your widgets to how they were the last time you had that theme activated.  Sounds good, yeah? The problem we&#8217;re facing is deciding how long to save the old widget configuration, since there are so many potential workflows. If you changed From Theme A to Theme B and added more widgets over the next few weeks, if you switched back to Theme A after a month, would you still expect it to go back to the widgets from a month ago? At what point does it go from handy timesaver to unexpected widget mangler?  What do you think?</p>
<p><a href="http://polldaddy.com/poll/5686875/">View This Poll</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/wherefore-art-thou-widgets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.3 Beta 4 Available Now</title>
		<link>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-4-available-now/</link>
		<comments>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-4-available-now/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-4-available-now/</guid>
		<description><![CDATA[The march toward 3.3 continues! With all our major tickets closed, we are very close to a release candidate. In Beta 4 we&#8217;ve fixed a bunch of bugs, cleaned up the UI, added real text in some of the screens that still had placeholder text in Beta 3 (post-update screen, the Dashboard welcome area, new [...]]]></description>
			<content:encoded><![CDATA[<p>The march toward 3.3 continues!</p>
<p>With all our major tickets closed, we are very close to a release candidate. In Beta 4 we&#8217;ve fixed a bunch of bugs, cleaned up the UI, added real text in some of the screens that still had placeholder text in Beta 3 (post-update screen, the Dashboard welcome area, new feature pointers), and generally tightened things up. We updated to jQuery 1.7.1 and addressed a LOT of bugs.</p>
<p>If you are a plugin or theme developer (or distributor), please test against Beta 4 to ensure there are no issues.</p>
<p>If you find any problems, please report them as usual. Many thanks!</p>
<p>Thought 3 was the last?<br />
Ha ha! Beta 4 is here &#8211;<br />
Better get testing!</p>
<p><a href="http://wordpress.org/wordpress-3.3-beta4.zip">Download WordPress 3.3 Beta 4</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/wordpress-3-3-beta-4-available-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.3 Release Candidate 1</title>
		<link>http://wordpressmy.com/2012/01/02/wordpress-3-3-release-candidate-1/</link>
		<comments>http://wordpressmy.com/2012/01/02/wordpress-3-3-release-candidate-1/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 03:14:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress.org]]></category>

		<guid isPermaLink="false">http://wordpressmy.com/2012/01/02/wordpress-3-3-release-candidate-1/</guid>
		<description><![CDATA[Release Candidate stage means we think we&#8217;re done and are about ready to launch this version, but are doing one last check before we officially call it. So take a look, and as always, please check your themes and plugins for compatibility if you&#8217;re a developer. Stayed up late tonight, Hammering toward RC1. Now with [...]]]></description>
			<content:encoded><![CDATA[<p>Release Candidate stage means we think we&#8217;re done and are about ready to launch this version, but are doing one last check before we officially call it. So take a look, and as always, please check your themes and plugins for compatibility if you&#8217;re a developer.</p>
<p>Stayed up late tonight,<br />
Hammering toward RC1.<br />
Now with more icons!</p>
<p><a href="http://wordpress.org/wordpress-3.3-RC1.zip">Download WordPress 3.3 Release Candidate 1</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpressmy.com/2012/01/02/wordpress-3-3-release-candidate-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

