Been hanging out with a few WordPress.org hackers — Scott, Nacin, and Otto — the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they’re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here’s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:

Our first focus was around improving the discussion and support around plugins.

You’ll now notice that threads about a plugin are pulled directly into a “support” tab on the plugin page — each plugin has its own forum. We’ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you’re using. And finally to show how active and well-supported a plugin is, you can see  ”16 of 75 support threads in the last two weeks have been resolved.” Finally, if you’re logged in you get access to the new “favorites” feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!

If you’re a plugin author, we’ve started with a short threshold (2 weeks) for the resolved stats so it’s easy to catch up and stay on top of it. (It’ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.

We’ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:

• “Plugin headers” or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.
• You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn’t yours. There is no better way to follow the development of your favorite plugins. There’s nothing like the smell of fresh changesets in the morning.
• Behind the scenes, we’ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.

All of this will continue to evolve as we get feedback and see usage, but we’re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ — it imparts magical coding powers.)

More: Plugin Directory Refreshed

LASER Vision Correction Surgery

Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it’s easily my favorite. Don’t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I’m aiming a little higher and shooting for a full-on contributor/community summit.

Core code isn’t the only way to contribute to the WordPress project. We have an active theme review team, support forum volunteers, people writing documentation, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we’ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.

In addition to bringing together the active contributor team reps to work together, I think it’s important to include community members who don’t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!

Taking a cue from events with limited availability like AdaCamp (attendance) and the jQuery conference (speaker roster), I want you to nominate people and/or WordPress-based businesses to participate in the summit. Yes, you can nominate yourself.* You can nominate up to 10 additional people — be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there’s a theme or hosting company (for example) that you think should be there, you don’t need to go looking for employee names. This nomination process will hopefully ensure that we don’t overlook someone who is making a difference in our community when it comes time to issue invitations.

Nominations will be open for a week, after which the survey will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at WordPress.tv. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you’re thinking to yourself that maybe now’s the perfect time to start contributing time to the WordPress project, good thinking! In the meantime, if you want to weigh in, fill in the community summit nomination form. Thanks, and wish us luck!

* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.

** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.

See original here: Calling All Contributors: Community Summit 2012

buy green coffee beans online

The latest and greatest version of the WordPress software — 3.3, named “Sonny” in honor of the great jazz saxophonist Sonny Stitt — is immediately available for download or update inside your WordPress dashboard.

WordPress has had over 65 million downloads since version 3.0 was released, and in this third major iteration we’ve added significant polish around the new user experience, navigation, uploading, and imports. Check out this short video that summarizes the things we think you’ll find are the cat’s pajamas:

For Users

Experienced users will appreciate the new drag-and-drop uploader, hover menus for the navigation, the new toolbar, improved co-editing support, and the new Tumblr importer. We’ve also been thinking a ton about what the WordPress experience is like for people completely new to the software. Version 3.3 has significant improvements there with pointer tips for new features included in each update, a friendly welcome message for first-time users, and revamped help tabs throughout the interface. Finally we’ve improved the dashboard experience on the iPad and other tablets with better touch support.

For Developers

There is a ton of candy for developers as well. I’d recommend starting your exploration with the new editor API, new jQuery version, better ways to hook into the help screens, more performant post-slug-only permalinks, and of course the entire list of improvements on the Codex and in Trac.

Roll the Credits

The Credits tab on the new About WordPress screen in the WordPress dashboard provides recognition for contributors to each release, but we like to thank them here as well.

Aaron D. Campbell, Aaron Jorbin, Adam Backstrom, Adam Harley, Alex Concha, Alex King, Alex Mills (Viper007Bond), amereservant, ampt, Andrei Freeman, Andre Renaut, andrewfrazier, Andrew Nacin, Andrew Ozz, Andrew Ryno, Andy Skelton, Anthony Atkinson, Austin Matzko, Bartosz Kaszubowski, Benjamin J. Balter, Brandon Dove, carlospaulino, Caspie, cebradesign, Chelsea Otakan, Chip Bennett, Chris Jean, Coen Jacobs, Curtiss Grymala, Daniel Bachhuber, Daryl Koopersmith, Daryl L. L. Houston, David, David Cowgill, David Gwyer, Da^MsT, deltafactory, demetris, Derek Herman, Devin Reams, Digital Raindrops, Dion Hulse (@dd32), Dominik Schilling (ocean90), Doug Provencio, dragoonis, DrewAPicture, Dylan Kuhn, eduplessis, Eightamrock, eko-fr, Elpie, elyobo, Empireoflight, Erick Hitter, Eric Mann, Evan Anderson, Evan Solomon, fonglh, garyc40, Gary Jones, Gaurav Aggarwal, George Stephanis, goldenapples, goto10, hakre, Helen Hou-Sandi, Ian Stewart, Ipstenu, Jackson, Jacob Gillespie, Jake Goldman, James Collins, Jane Wells, jeremyclarke, Jesper Johansen (Jayjdk), jgadbois, Jick, Joe Hoyle, John Blackbourn, John Hawkins, John James Jacoby, JohnONolan, John P. Bloch, Jon Cave, Jorge Bernal, Joseph Scott, jtclarke, Jurica Zuanovic, Justin Givens, Justin Sainton, Kailey Lampert (trepmal), kevinB, kitchin, Konstantin Kovshenin, Kuraishi, Kurt Payne, Lance Willett, Latz, linuxologos, Lloyd Budd, Luc De Brouwer, lukeschlather, Mako, Mantas Malcius, MarcusPope, mark-k, Mark Jaquith, Mark McWilliams, Marko Heijnen, Martin Lormes, masonjames, Matias Ventura, Matt Mullenweg, Matt Thomas, Matt Wiebe, MattyRob, Mert Yazicioglu, Michael Adams (mdawaffe), Michael Fields, Michal “Mau” Pliska, Mike Bijon, Mike Schroder, Milan Dinic, mitchoyoshitaka, Mohammad Jangda, Morten Hauan, Mr Papa, mrtorrent, Naoko McCracken, natebedortha, Nikolay Bachiyski, olivM, olleicua, Otto, pagesimplify, paulhastings0, pavelevap, pete.mall, Peter Westwood, peterwilsoncc, ppaire, Ptah Dunbar, r-a-y, Rami Y, Rasheed Bydousi, Robert Chapin (miqrogroove), Ron Rennick, Ross Hanney, ruslany, Ryan Boren, ryanhellyer, Ryan Imel, Safirul Alredha, Samir Shah, Sam Margulies, saracannon, Scott Basgaard, Scott Bressler, Scott Cariss, scottconnerly, Scott Reilly, Scott Taylor, scribu, Sergey Biryukov, Sheri Bigelow, Simon Wheatley, sirzooro, Stephanie Leary, tech163, TheDeadMedic, Tim Moore, Tom Auger, Travis Ballard, Ulrich Sossou, vnsavage, wpweaver, WraithKenny, Yoav Farhi, and Ze Fontainhas.

As well, we’d like to give a shout out to these users who have been particularly active on the support forums since the release of 3.2:

alchymyth, Andrea_r, ClaytonJames, cubecolour, Eran Miller, esmi, Frederick Townes, govpatel, Ipstenu, keesiemeijer, kmessinger, Marcus, Otto, peredur, Rev. Voodoo, Samuel B, Tobias, vtxyzzy, and zoonini.

Link: WordPress 3.3 “Sonny”

green coffee beans free shipping

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 Dashboard → Updates in your site admin.

Read more from the original source: WordPress 3.3.1 Security and Maintenance Release

cheap green coffee beans

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 — 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’t want to alienate any of our users no matter how much some of us may disagree with some of them personally. Today, I’m breaking our no-politics rule, because there’s something going on in U.S. politics right now that we need to make sure you know about and understand, because it affects us all.

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 you 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’m concerned 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.

You may have heard people talking/blogging/twittering about SOPA — the Stop Online Piracy Act. The recent SOPA-related boycott of GoDaddy 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’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 Fight for the Future).

Some thoughts:

• 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.
• 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.
• 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.

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’t change a single mind, especially one that’s been convinced of something by lobbyist dollars. To those people, I repeat the words of Margaret Mead:

Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it is the only thing that ever has.

We are not a small group. More than 60 million people use WordPress — it’s said to power about 15% of the web. We can make an impact, and you can be an agent of change. Go to Stop American Censorship 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. Make your voice heard.

*Yes, the latest episode of Sherlock is good. Stephen Moffatt + Russell Tovey = always good

Excerpt from: Help Stop SOPA/PIPA

green coffee 800 malaysia

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. We must stop it.

On January 18, 2012 many sites around the web — from small personal blogs to internet institutions like Mozilla, Wikipedia, reddit, and I Can Has Cheezburger? – will be going dark in protest and to drive their visitors to sites like americancensorship.org to take action and help fight the passage of the Protect IP Act. So will WordPress.org.

If you want to join the protest by blacking out your WordPress site or applying a ribbon, there is now a variety of blackout plugins in the WordPress.org plugins directory. While joining the protest in this manner is laudable, please don’t forget to also make those phone calls to U.S. Senators — they’re the ones with the voting power.

• Get a protest plugin
• Take action at americancensorship.org

Read more: Internet Blackout Day on January 18

green coffee

WordPress 3.3.2 is available now and is a security update for all previous versions.

Three external libraries included in WordPress received security updates:

• Plupload (version 1.5.4), which WordPress uses for uploading media.
• SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.
• SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.

Thanks to Neal Poole and Nathan Partlan for responsibly disclosing the bugs in Plupload and SWFUpload, and Szymon Gruszecki for a separate bug in SWFUpload.

WordPress 3.3.2 also addresses:

• Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by Jon Cave of our WordPress core security team, and Adam Backstrom.
• Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.
• Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to Mauro Gentile for responsibly disclosing these issues to the security team.

These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the change log for more details.

Download WordPress 3.3.2 or update now from the Dashboard → Updates menu in your site’s admin area.

WordPress 3.4 Beta 3 also available

Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. Nearly 90 changes have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)

This is still beta software, so we don’t recommend that you use it on production sites. But if you’re a plugin developer, a theme developer, or a site administrator, you should be running this on your test environments and reporting any bugs you find. (See the known issues here.) If you’re a WordPress user who wants to open your presents early, take advantage of WordPress’s famous 5-minute install and spin up a secondary test site. Let us know what you think!

Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. Download WordPress 3.4 Beta 3 or use the WordPress Beta Tester plugin.

See the article here: WordPress 3.3.2 (and WordPress 3.4 Beta 3)

HGH

Howdy, folks! Another week, another beta. Since we released Beta 1 last week, we’ve committed more than 60 bug fixes and feature adjustments based on testing and feedback. If you’ve been testing Beta 1, please update to Beta 2 to make sure things are still working for you. If you are a theme or plugin author and have not yet started testing your code against the 3.4 beta, now’s the perfect time to start. And as always, if you find any bugs, let us know! Full details on testing and bug reporting can be found in last week’s Beta 1 post.

Download WordPress 3.4 Beta 2

See the article here: WordPress 3.4 Beta 2

Wrinkle Cream

It’s almost that time again, when the WordPress core development team gets together in person to review the year’s progress and talk about priorities for the coming year. Next week Matt Mullenweg, Mark Jaquith, Peter Westwood, Andrew Ozz, Andrew Nacin, Dion Hulse, Daryl Koopersmith, Jon Cave, and I will meet at Tybee Island, GA, the same location as the last meetup.

Last year we wanted to do a video town hall, but ran into technical and scheduling difficulties. This year we’re planning ahead, and will definitely make it happen. We’re currently taking questions, and will record a series of town hall-style videos where we answer your questions. Ask about the roadmap, code, community, contributing, WordCamps, meetups, themes, plugins, features, you name it. No topic (as long as it is about WordPress) is off limits, and we’ll do our best to answer as many questions as we can while we are together. The videos will be posted to this blog and archived at WordPress.tv.

Last year the people who were in attendance also posted pictures and updates to Twitter using the #wptybee tag. We’ll use the same tag this year, so if you’re interested in following along, add it to your Twitter client as a search.

What do you want to know from us? Ask away!

Read more: Core Team Meetup Time

Autoblogging Software

We hereby declare 2012 as the Year of the WordPress Meetup. You’ll want to get in on this action.

meet

• Blog this!
• Bookmark on Delicious
• Digg this post
• Recommend on Facebook
• Share via MySpace
• share via Reddit
• Share with Stumblers
• Share on technorati
• Tumblr it
• Tweet about it
• Subscribe to the comments on this post
• Bookmark in Browser