WordPress 3.0 Thelonious passed 3 million downloads yesterday, and today the plugin directory followed suit with a milestone of its own: 100 million downloads.
The WordPress community’s growth over the years has been tremendous, and we want to reinvest in it. So we’re taking the next two months to concentrate on improving WordPress.org. A major part of that will be improving the infrastructure of the plugins directory. More than 10,000 plugins are in the directory, every one of them GPL compatible and free as in both beer and speech. Here’s what we have in mind:
We want to provide developers the tools they need to build the best possible plugins. We’re going to provide better integration with the forums so you can support your users. We’ll make more statistics available to you so you can analyze your user base, and over time we hope to make it easier for you to manage, build, and release localized plugins.
We want to improve how the core software works with your plugin and the plugin directory. We’re going to focus on ensuring seamless upgrades by making the best possible determinations about compatibility, and offer continual improvements to the plugin installer. And we also want to give you a better developer tool set like SVN notifications and improvements to the bug tracker.
We’re also going to experiment with other great ideas to help the community help plugin authors. We want it to be easy for you to offer comments to plugin authors and the community, including user reviews and better feedback. We may experiment with an adoption process for abandoned plugins as a way to revitalize hidden gems in the directory. I’m not sure there is a better way to show how extendable WordPress is and how awesome this community is at the same time.
As Matt said in the 3.0 release announcement, our goal isn’t to make everything perfect all at once. But we think incremental improvements can provide us with a great base for 3.1 and beyond, and for the tens of millions of users, and hundreds of millions of plugin downloads to come.
It’s been summer for about a week now. Whether you’re on vacation or burning the midnight oil, attending a local/nearby WordCamp is a great way to spend a weekend. Meet other WordPress users, developers, designers & consultants, learn a little something, maybe share a little of your own experience and knowledge, and break bread (or raise a toast) with new friends and collaborators. Here are the WordCamps scheduled for this summer, along with what I know about them.
July 3: WordCamp Germany – Berlin, Germany. I love it that they’re using BuddyPress for their event site. They have multiple tracks, and what looks to be a nice variety of sessions. It’s only a few days away, so if you’re thinking of going, get your tickets now!
July 10: WordCamp Boulder – Boulder, Colorado, USA. This was WordCamp Denver last year, but the organizers have decided to mix it up and go back and forth between Denver and Boulder, which also has a thriving tech community. This year the venue is the Boulder Theater (so pretty!), and there will sessions for bloggers and devs alike, plus a Genius Bar to help people get their WordPress sites all fixed up. The speaker lineup looks good, and I hear they’re pumping up the wifi this year. I’ll be there, likely hunched over a notebook with Lisa Sabin-Wilson (author of WordPress for Dummies and BuddyPress for Dummies) to talk about the WordPress User Handbook project, and/or hunched over a sketchbook with Kevin Conboy (designed the new lighter “on” state for admin menus in WordPress 3.0) to work out a new default WordCamp.org theme (using BuddyPress). You can still get tickets!
July 17–18: WordCamp UK- Manchester, England, UK. The roving WordCamp UK will be in Manchester this year, and is probably the closest to BarCamp style of all the WordCamps, using a wiki to plan some speakers/sessions and organizing the rest ad-hoc on the first day of the event. I’ll be attending this one as well, and am looking forward to seeing WordPress lead developer Peter Westwood again. I’m also looking forward to meeting some core contributors for the first time in person, like Simon Wheatley and John O’Nolan. Mike Little, co-founder of WordPress, is on the organizing team of WordCamp UK. Tickets on sale now!
July 24: WordCamp Nigeria – Lagos, Nigeria. Their site seems to have a virus, so no link from here, but if you’re in Nigeria and interested in attending/getting involved, a quick Google search will get you to the organizers.
August 7: WordCamp Houston – Houston, TX, USA. Houston, Texas, birthplace of WordPress! Fittingly, Matt Mullenweg will be there to give the keynote. WordCamp Houston is running three tracks — Business, Blogger and Developer — in recognition of the fact that people who are interested in using WordPress for their business may not actually be bloggers or developers themselves. This used to get labeled as a “CMS” track at previous WordCamps (including NYC 2009), but with WordPress 3.0 supporting CMS functionality out of the box, “Business” is a much more appropriate label. Who wants to bet on if there will be BBQ for lunch?
August 7 : WordCamp Iowa – Des Moines, Iowa, USA. Another placeholder page. Happening, not happening? I’ve emailed the organizer and will update this post once I know more.
August 7–8: WordCamp New Zealand – Auckland, New Zealand. They haven’t announced this year’s speakers or topics, but they’ve been running polls to get community input into the program. Of note: in 2011 WordCamp New Zealand will be shifting seasons and will be in February instead, when the weather is nicer.
August 20–22: WordCamp Savannah – Savannah, Georgia, USA. Disclaimer: I am completely biased about Savannah, since I’m one of the organizers. This will be the first WordCamp in Savannah, and it’s being held at the Savannah College of Art and Design River Club, an awesome venue that used to be a cotton warehouse or something like that. Since Savannah doesn’t really have a cohesive WordPress community yet (though a fair number of people from Savannah attended WordCamp Atlanta earlier this year), this WordCamp is aimed squarely at building a local community. We’ll have a local meet-and-greet, regular sessions with visiting speakers (lots of core contributors coming to this one, plus Matt), and on Sunday it will be combination unconference/genius bar/collaborative workspace. Oh, and a potluck! We’ll also be running a pre-WordCamp workshop for people who have never used WordPress but want to get started, so that they’ll be able to follow the presentations and conversations littered with WordPress-specific vocabulary over the weekend. Ticket sales just opened, so get your tickets now.
Arm your vuvuzelas: WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new lighter interface, the contextual help on every screen, the 1,217 bug fixes and feature enhancements, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video. (In HD, if you can, so you can catch the Easter eggs.)
If you’d like to embed the WordPress 3.0 video tour in your blog, copy and paste this code for the high quality version:
For a more comprehensive look at everything that has improved in 3.0 check out 3.0′s Codex page or the long list of issues in Trac. (We’re trying to keep these announcement posts shorter.) Whew! That’s a lot packed into one release. I can’t think of a better way to kick off the 3.X cycle we’ll be in for the next two and a half years.
The Future
Normally this is where I’d say we’re about to start work on 3.1, but we’re actually not. We’re going to take a release cycle off to focus on all of the things around WordPress. The growth of the community has been breathtaking, including over 10.3 million downloads of version 2.9, but so much of our effort has been focused on the core software it hasn’t left much time for anything else. Over the next three months we’re going to split into ninja/pirate teams focused on different areas of the around-WordPress experience, including the showcase, Codex, forums, profiles, update and compatibility APIs, theme directory, plugin directory, mailing lists, core plugins, wordcamp.org… the possibilities are endless. The goal of the teams isn’t going to be to make things perfect all at once, just better than they are today. We think this investment of time will give us a much stronger infrastructure to grow WordPress.org for the many tens of millions of users that will join us during the 3.X release cycle.
It Takes a Village
I’m proud to acknowledge the contributions of the following 218 people to the 3.0 release cycle. These are the folks that make WordPress what it is, whose collaboration and hard work enable us to build something greater than the sum of our parts. In alphabetical order, of course.
If you’ve made it this far, check out my 2010 State of the Word speech at WordCamp San Francisco, it’s jam-packed with information on the growth of WordPress, 3.0, what we’re planning for the future, and the philosophy of WordPress.
When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase:
Now is the time for all good men to come to the aid of their country.
For some reason that has stuck with me all these years. Today I’m going to rephrase and re-purpose that line:
Now is the time for great theme developers to come to the aid of their community.
The theme directory has been chugging along for more than a year now. During that time we’ve tinkered with the review process and some of the management tools, but haven’t really opened it up as much as we’d like. It’s time to rip off the band-aid and take some action; to that end, we’re looking for community members to help with the process of reviewing themes for the directory.
Right now this is a bit like a New Year’s resolution to exercise every day: it’s what we need to do, but we’re still figuring out exactly how it will all work. That’s part of the community involvement as well — we expect that those who pitch in will also help shape the process.
What’s involved in reviewing themes for the directory? There are some obvious things, such as being familiar with PHP and WordPress theme code (and the theme development checklist), with an eye for security issues. You would also need to have the ability to set up a separate install of the latest version of WordPress for testing theme submissions.
Hopefully a few talented theme developers are reading this right now and saying to themselves, “I’d love to help! How do I get started?” Just join the new theme reviewers mailing list and we’ll get you up to speed on this new opportunity to come to the aid of your community.
As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What’s an RC? An RC comes after beta and before the final launch. It means we think we’ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using WordPress with a wide variety of configurations and hosting setups, it’s entirely possible that we’ve missed something. So! For the brave of heart, please download the RC and test it out (but not on your live site unless you’re extra adventurous). Some things to know:
Custom menus are finished! Yay!
Multi-site is all set.
The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.
There are a ton of changes, so plugin authors, please test your plugins now, so that if there is a compatibility issue, we can figure it out before the final release.
Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
Has it really been seven years since the first release of WordPress? It seems like just yesterday we were fresh to the world, a new entrant to a market everyone said was already saturated. (As a side note, if the common perception is that a market is finished and that everything interesting has been done already, it’s probably a really good time to enter it.)
The growth over the past year has blown me away. Since our last birthday we’ve doubled theme downloads to over 10 million, and doubled plugin downloads to 60 million. Most importantly, we continued to grow the development community to 1,528 people active on Trac and 13 committers, both numbers the highest in the history of WordPress.
That’s 1,528 people pouring their hearts and souls into GPL software we all own, we all build on, we can use as we please, we can all make better. We’ve evolved from a simple script to a web platform.
We’re on the cusp of version 3.0, with a release candidate coming out any minute now.
If you’d like to celebrate WordPress’s birthday with us — tell a friend! Help them upgrade their blog or find the perfect theme. Talk about how WordPress is built by and for a community. Drop in to help test 3.0, including all the plugins you use. Write something to take advantage of the new 3.0 features, or teach your friends how to. If you buy any themes or plugins, make sure they’re GPL or compatible just like WordPress. We’ve got a long road ahead of us, it’s important that we not forget that Open Source got us this far, and is the only way we’re going to get to the next level. The whole of what we can build together is far greater than the sum of our parts. Spread the good word.
A week from today on May 1, hundreds of WordPress users, developers, designers and general enthusiasts will descend upon San Francisco for the 4th annual WordCamp SF. Since that first WordCamp in 2006, back when WordPress was on version 2.0 (Duke), the number of people using WordPress to power their web publishing — from personal blogs to large-scale commercial sites — has grown by millions. It’s no wonder this year’s event is going to be so great.
If you’re unfamiliar with WordCamps, here’s the skinny: the San Francisco event is the flagship, put together each year under the direction of WordPress co-founder and lead developer Matt Mullenweg, who traditionally reports on the “State of the Word” and assembles a lineup of speakers that have inspired him over the past year. This year’s lineup includes luminaries such as Richard Stallman, the father of Free Software, best-selling author Scott Berkun, and Salon.com co-founder Scott Rosenberg. As the final speaker list is finalized, the remaining speakers will be added to the WordCamp SF website, but a surprise or two is still possible.
Though the main event is on Saturday, May 1, there are additional days of WordPress goodness in store. Saturday, May 1 will be the main conference with scheduled speakers. There will be keynotes, session tracks for both bloggers/end-users and developers, and lightning talks to provide a broad mix of content, followed by a raging afterparty. Sunday, May 2 will shift location and tone, with a low-key developers’ unconference for the super-code-focused attendees. May 3 and 4 are conference-free, but a WordPress core contributor in-person code sprint will span those two days, bringing together core contributors old and new from around the globe for two days of intense hacking (and let’s face it, 3.0 bug fixes).
It’s definitely WordCamp season; just check out the growing list of upcoming WordCamps over the next couple of months! If you don’t see a WordCamp near you listed here, check the rest of the schedule at WordCamp.org. In the meantime, don’t forget that many WordCamps post video of their presentations on WordPress.tv.
Early next week, we’re hoping to release the 2nd beta release of WordPress 3.0 on our journey toward the final version. There are still over 200 bugs in the 3.0 milestone, and we can use all the help we can get on fixing these problems. If you’re a developer, take a look at the list of bugs that still need fixing in 3.0. Write a patch, or test and give feedback on someone else’s. The tickets around custom post types and taxonomies are especially in need of help. Every little bit helps, so if you’re a developer who’s never contributed to core before, maybe now is the right time! Check out our information on contributing to WordPress core, and head over to Trac to see if there’s a problem you might know how to fix. If you get stuck, need collaborators, or have a question about the best way to approach a fix, hop into the dev channel on IRC at irc.freenode.net, channel #wordpress-dev. Core developers will be around over the weekend working on bugs themselves, so if you’re trying to help, don’t be afraid to ask questions. With your help, maybe by Monday we can knock the bug count down to half of what it is right now. How great would that be? (Answer: pretty great)
The sprint will go full force until Monday afternoon, when the lead developers and core committers will all stop to take a breath and look at the remaining bug reports to see how we did over the weekend, so don’t wait! And thanks!
Summary: A web host had a crappy server configuration that allowed people on the same box to read each others’ configuration files, and some members of the “security” press have tried to turn this into a “WordPress vulnerability” story.
WordPress, like all other web applications, must store database connection info in clear text. Encrypting credentials doesn’t matter because the keys have to be stored where the web server can read them in order to decrypt the data. If a malicious user has access to the file system — like they appeared to have in this case — it is trivial to obtain the keys and decrypt the information. When you leave the keys to the door in the lock, does it help to lock the door?
A properly configured web server will not allow users to access the files of another user, regardless of file permissions. The web server is the responsibility of the hosting provider. The methods for doing this (suexec, et al) have been around for 5+ years.
I’m not even going to link any of the articles because they have so many inaccuracies you become stupider by reading them.
If you’re a web host and you turn a bad file permissions story into a WordPress story, you’re doing something wrong.
P.S. Network Solutions, it’s “WordPress” not “Word Press.”
The deadline for students applying for Google Summer of Code this year is today, at 19:00 UTC. That’s about 3 hours from now. Still working on your application? Double check your time zone here. No late applications will be accepted.
There are a lot of potential projects on our Ideas list, so if you’ve been hemming and hawing over whether or not to apply, this is your last chance for this year. We have great people lined up to mentor the students, including most of the WordPress lead developers, some dedicated core contributors, plugin developers, the BuddyPress lead developers, etc. Google is providing a great opportunity for both students and the open source projects that act as mentoring organizations (like WordPress), so don’t pass it up if you’re an eligible student.
You can’t win if you don’t play, right? Five thousand bucks for two months of coding over the summer with WordPress hotshots. I know a lot of people that would love that deal. Oh, and hey, student girl wonders of WordPress-land: why haven’t you applied yet?
Remember when I posted earlier about the Twitter account, and I said that hopefully you’d find out later today what has been keeping us all so busy? Beta testers, this is your moment: the WordPress 3.0 Beta 1 has arrived!
This is an early beta. This means there are a few things we’re still finishing. We wanted to get people testing it this weekend, so we’re releasing it now rather than waiting another week until everything is finalized and polished. There’s a ton of stuff going on in 3.0, so this time we’re giving you a list of things to check out, so that we can make sure people are testing all the things that need it.
You Should Know:
The custom menus system (Appearance > Menus) is not quite finished. In Beta 2, the layout will be different and a bunch of the functionality will be improved, but we didn’t want to hold things up for this one screen. You can play with making custom menus, and report bugs if you find them, but this is not how the final screen will look/work, so don’t get attached to it.
The merge! Yes, WordPress and WordPress MU have merged. This does not mean that you can suddenly start adding a bunch of new blogs from within your regular WordPress Dashboard. If you’re interested in testing the Super Admin stuff associated with multiple sites, you’ll need some simple directions to get started.
We’re still fiddling with a few small things in the UI, as we were focused on getting the more function-oriented code finished first. For example, we’re getting a new icon for the Super Admin section.
Things to test:
Play with the new default theme, Twenty Ten, including the custom background and header options.
Custom Post Type functionality has been beefed up. It’s really easy to add new types, so do that and see how it looks!
WordPress MU users should test the multiple sites functionality to make sure nothing broke during the merge.
Already have a test install that you want to switch over to the beta? Try the beta tester plugin.
This post is about the @WordPress Twitter account, so if you don’t use Twitter, or don’t care about Twitter, then feel free to take the time you might have spent reading this post to go play outside (or an equivalent) instead.
Okay, so, Twitter! When all those apps started popping up using the Twitter API, things like automatically following anyone who followed you and sending an automatic Direct Message seemed like good ideas. We’re all friends, right? Wrong. That auto-follow bit us hard, and the huge amount of spam the account gets means that it’s been nearly impossible to monitor legitimate messages from WordPress users and developers who need to be pointed to a help resource. We’re sorry! Just as we needed to get the Ideas Forum under control* so that it could become a more useful resource for the community, we needed to get rid of the spam clogging our Twitter arteries. Except there was no easy way to do it.
We had wound up following over 50,000 people. If someone went to the @WordPress profile page on Twitter to see the stream of updates from people we followed, almost none of it had anything to do with WordPress or the community. Diet pills, Twitter scams, and multi-posted spam messages were the norm. Yuck! Who else wishes there was Akismet for Twitter? Unfortunately, there’s no easy way to clear this stuff out quickly (mass unfollows trigger their TOS alert, so it’s not surprising). I even contacted Twitter directly to see what the options might be, and it was suggested we use a script to clear the account. To be clear: Twitter flagged our account so that when the script was run they wouldn’t mark us as spammers for violating the TOS with a mass unfollow. We communicated with them beforehand, and the use of scripts to do this is not encouraged. Twitter was doing us a nice favor to help us get our house in order. Thanks, Twitter! Last night I ran the script and removed everyone. Extreme, but in good cause, right?
We’re now starting to re-follow real people from the WordPress community. There will be no more auto-follow. If you are a WordPress developer, designer, blogger, fan site, whatever — and think your tweets should appear in the @WordPress updates stream, then send an @ reply to us and we can add you to the new list (assuming you’re not hawking diet pills, free iPads or ways to get a million followers). This way, people who are new to WordPress and go to check us out on Twitter will (hopefully) get a sense of the vibrant community that we have. People who send @ messages to us won’t (hopefully) wonder indefinitely why they were ignored, because without all the spam, maybe we can use Twitter as it was intended to be used, as another channel of communication.
And for anyone who uses Qwitter and thinks @WordPress stopped loving them because of the last tweet they posted before the script ran… sorry! It wasn’t like that, we swear! It would be nice if the script could have done a bulk DM before the removal, but nope (otherwise we’d have included a message about this). So trust us, we still like you! And if you haven’t already been re-followed, please don’t take it personally… just send an @reply to @WordPress (tell us how you use WordPress!) and we’ll try to get you re-added soon. Later today (hopefully) you’ll find out what’s been keeping us so busy!
*Have you noticed? We cleared out thousands of old threads, added categorization, and will try to keep it to under a hundred open idea threads at a time so that they can be managed in a timely fashion. Check it out and rate some of the new ideas today!
Professor: So. Out of the 20 students in the class, half wrote WordPress Summer of Code proposals good enough to receive an A. How many of you are planning to apply for the program?
Jack, a student: I am. They opened applications today.
Sophie, a student: I am. And that sentence was grammatically terrible.
Jack: Shut up.
Chris, a student: I’m not applying.
Jack (to Chris): Chicken?
Sophie: You’re such a jerk! Maybe he has a job lined up or something, did you ever think of that?
Professor: Whoa -
Chris: Actually, I’m going backpacking in Australia with my Dad. No internet for about half the time, and when I emailed the people at WordPress they said I should probably wait until next year to apply and make sure I’d be able to be online through the whole summer.
Professor: Fair enough. The application period opens today at 19:00 UTC and goes through April 9th, so let’s hear from the people who are applying.
Jack: I’m submitting mine today.
Sophie: That’s just stupid.
Andrea, a teacher’s assistant: Hey, that’s not necessary.
Jack: Yeah! The early bird gets the worm, or hadn’t you heard?
Sophie: What I heard was that the WordPress mentors are holding open IRC chats this week to talk to prospective students and give them feedback on proposals and ideas, and that talking directly to the mentors ups your chances of being selected. But I guess you don’t think you need the people who are actually choosing the students to know your name because your proposal is so brilliant?
Jack’s jaw drops.
Jack: Where did you hear that? It wasn’t on the GSoC mailing list.
Sophie: I joined the wp-hackers list and asked all the core contributors for feedback on my idea, and then I emailed 3 potential mentors to see what they thought of it personally. By the time applications are due, I’ll have revised it based on community and mentor feedback, and enough people will know who I am — and that I’m full of initiative — that my chances of being accepted will be much better.
Jack: You think you’re all Felicia Day with your MW2 level 70, but you’re just a computer nerd.
Sophie: Um, duh. We’re in an advanced computer programming class. We’re all computer nerds.
Professor: Now, now. Sophie’s correct; talking to community members and mentors will improve her chances. But, Jack, there’s no reason you can’t join the IRC chats and the mailing list to get your name out there, too, even if you submit your application today. Most proposals get tweaked a bit after the students are chosen anyway.
Here’s the deal. The application period opens today. Early applications will likely get a bit more attention up front, but it’s also important that your ideas and approach are vetted by the community and the mentors. If you haven’t already, you should join the wp-hackers mailing list and send your proposal to the list for feedback. We’ll also be doing a few IRC chats during the application period to give students a chance to talk directly with the mentors. Note that not every mentor will attend all three chats, so if you want to talk to a specific person, you might want to email them. Please arrive on time to the chats, as they will be scheduled for an hour, and will have to accommodate multiple students. IRC chats will be held at irc.freenode.net in room #wordpress-gsoc.
Wednesday, March March 31 at 20:30 UTC (4:30pm eastern)
Saturday, April 3 at 21:30 UTC (5:30pm eastern)
Wednesday, April 7 at 20:30 UTC (4:30pm eastern)
This chat room will remain open during the application period, and various mentors and community members may be there and able to answer questions, but the scheduled chats are the only official times at which they are scheduled to do so.
Oh, and if you want to help publicize the WordPress summer of code, grab a flyer and post it somewhere on a bulletin board at your local college campus. Professors, don’t forget to encourage your brightest students to apply!
Professor: Is anyone here applying for Google Summer of Code this year? If so, see me after class to discuss getting independent study credit toward your degree.
Jack, a student: Isn’t that a really hard program to get into? Like, hard like getting to level 70 in Modern Warfare 2?
Sophie, a student: I went past 70, I prestiged.
Jack (turning to Sophie): Shut up, you did not!
Sophie: I did, too!
Professor: Not the point, kids. So who’s going to try for a GSoC spot?
Andrea, a teacher’s assistant: There are some great open source projects participating this year. I’d love to see someone from this class get in on the WordPress project.
Jack: WordPress is awesome, but my friend Billy didn’t get chosen by them last year.
Sophie: Billy’s not as smart as he thinks he is.
Jack: You think you could do better?!
Sophie: Of course I do! Any primate could do better than Billy! Or you, for that matter!
Jack: What? I would so beat you out in a coding competition!
Andrea: Sounds like we have the makings of a friendly classroom competition, Prof.
Professor: I think you’re right, Andrea. Tell you kids what. They announce the students who’ve been accepted on April 26th, which is before the semester ends. Let’s turn this into a class project.
Jack (raising a suspicious eyebrow): How do you mean?
Professor: As a class assignment, everyone has one week to write a project proposal for the Google Summer of Code, specific to the WordPress project. The proposals will be graded like a regular assignment. Anyone who gets an A on the proposal can use me as a reference if they apply with the proposal to WordPress and Google for the program. The application deadline is April 9, so you’ll have time to revise your application after it’s been graded.
Sophie: What’s in it for us?
Andrea: If you’re successful in GSoC you earn $5000 for the summer.
Sophie (smirking, to Jack): That’s more than you’ll make working the hot dog cart by City Hall.
Jack: You wish. I’m totally getting in, and you’ll be on the hot dog cart this year.
Professor: And as I was starting to say in the first place, a GSoC project would qualify for independent study credit. Tell you what, as an added bonus, anyone who actually gets accepted into the WordPress GSoC program will get extra credit points on their year end average.
Sophie (perking up): Really? I’m in!
Jack: No way, they’ll choose me first!
Stay tuned for the continuing adventures of Jack and Sophie as they navigate the course of applying to Google Summer of Code to work with WordPress.
That’s right, WordPress is honored to be among the 150 open source organizations chosen to participate in Google Summer of Code this year. Students work on WordPress projects over the summer under the guidance of mentors from among the WordPress core developers, and if they complete their projects successfully Google pays them $5000! Talk about a win-win. Last year’s projects led to some very cool code being created, like the new search API targeted for version 3.0 and the Elastic theme generator.
Professors: Help us and your students by telling them about GSoC and encouraging them to apply. Consider having them write a WordPress plugin or core patch as a class assignment so they can get to know the codebase. Offer to sign on as an adviser for a summer independent study so they can get credit for their work with GSoC.
Students: Check out our Ideas page, and start thinking about projects you’d like to propose. Watch this space for an announcement of some live chat information sessions where you can ask potential mentors questions and get feedback on your pre-proposal ideas. This program is competitive, but is one of the best opportunities out there when it comes to programming. You get real-world experience as a member of an open source community, you make decent money, you make connections with industry leaders, and you get the attention of Google. Not to mention some serious bragging rights. What are you waiting for? Applications will be accepted from March 29-April 9, so start thinking about a project now!
This weekend, thousands of WordPress users and developers are among the people attending the South by Southwest (SxSW) Interactive conference in Austin, TX. To celebrate this, we’re throwing a WordPress BBQ at SxSW tomorrow so that there’s a place for us all to get together.
If you’re a WordPress fan attending SxSW (or you just happen to be in Austin), please join us for lunch after 12pm* tomorrow, Sunday March 14. We’re getting the BBQ from Rudy’s and the red velvet cake from Central Market. Yum! Come, eat, talk about the cool things you’re doing with WordPress, let us know what we can do better, gossip about Mark Jaquith’s new hairstyle, whatever. Think of it like a WordCamp without presentations. I’ll be there, lead developers Mark Jaquith and Ryan Boren will be there, core contributors will be there, plugin and theme developers will be there, and basically all the most intelligent and attractive people from SxSW will be there. You should be, too!
Location: Conjunctured coworking space, 1309 East 7th St., Austin, TX 78702. From the convention center, walk up to 7th Street, hang a right, and walk until you get to #1309. If you’re tired of walking, taking a cab is a decent option. Note that this is on the other side of I-35 from the convention center.
* We’ll keep serving until we run out of food, so probably until around 2 or 3? We’ll have a hundred pounds of bbq meat, a bunch of sides, and dozens of gallons of iced tea, so come hungry.
Cum modific meta ca sa scap de rss si wordpress.com sa ramana doar inregistrare autentificare si ce mai vreau eu am modificat din tema si a mers dar dupa ce am modificat ordinea din dashboard de la widgets nu le mai incarca de unde am modificat prima data si nustu unde trebe sa modific iarasi ca sa scap de ce nu vreau
Dupa download, extrage din arhiva fisierul trilulilu_plugin.php. Copiaza-l pe server in directorul /wp-content/plugins. Apoi activeaza-l din sectiunea “Plugin-uri” in consola de administrare a blog-ului tau.
Utilizarea plugin-ului:
La scrierea unui nou articol, introdu codul cum este descris mai jos, in sectiunea “HTML” (nu “Visual”) a articolului:
[trilu-video] link permanent video Trilulilu [/trilu-video]
[trilu-audio] link permanent audio Trilulilu [/trilu-audio]
[trilu-imagine] link permanent imagine Trilulilu [/trilu-imagi
vreau sa schimb si eu versiunea 2.07 cu versiunea 1.01 daca merge
sau mai simplu incercati sa vedeti daca merge acel plugin la toate versiunile wordpress si dupaia imi spuneti ce ati facut voi
si inca o problema care o am!!!!!!
mie mea disparut de la
articol-Articol New Post sectiunele “HTML & Visual”
De curand mi-am facut si eu blog(de 3 zile). Blogul este gazduit de wordpress.com. In primul rand doresc sa stiu daca pot cumva sa fac panoul de control sa fie in limba romana. In al doilea rand: astazi m-am chinuit la un post, am scris ceva pe acolo si apoi am pus un link care sa directioneze cititorulla alta pagina, nu am putut sa fac asta.
(In HD, if you can, so you can catch the Easter eggs.)
This weekend, thousands of WordPress users and developers are among the people attending the South by Southwest (SxSW) Interactive conference in Austin, TX. To celebrate this, we’re throwing a WordPress BBQ at SxSW tomorrow so that there’s a place for us all to get together.
