Displaying 1 To 16 Of 16 Comments I would argue that it’s not Jane that’s bad, but that the policies she publicizes rub the community in several wrong ways. I hadn’t heard the “Jane should resign” lines; had I noticed them, I would have redirected people towards focusing less on the person (she’s just doing her job) and more on what’s truly bugging them (they just don’t like what she has to say). » Posted By Spamboy On May 29, 2010 @ 10:35 AM Classic And Kubrick Have Left The Building Definitely celebration. It’s like trying to get a kid to give up their special binky — they’re terribly attached to it, may bitch when you yank it away cold-turkey, but then they grow up completely well-adjusted with no ill effects. Removing these tried-but-true themes will be the same for WordPress. » Posted By Spamboy On March 29, 2010 @ 1:42 PM How many people were in attendance? Did all events occur in the same room, or were they spread throughout the NERD center? » Posted By Spamboy On January 26, 2010 @ 10:11 PM Should WordPress Change The Blog Nomenclature Within The Backend? For a user to be serious enough to utilize any CMS, they should also intelligent enough to understand the CMS capabilities of WordPress without being confused by blog-centric terminology. » Posted By Spamboy On November 3, 2009 @ 7:01 PM Supported Legacy Branches For WordPress.org? @Chris: I think a legacy branch would be intended for users who desire to run stable software — you could infer that such individuals would be *more likely* to upgrade because of that vested interest. @Dougal The longer period of time a legacy branch is supported, the better — for both the individual/business running WP, and the team maintaining that branch. A 3-4 month window is too short for companies that use WordPress publicly. Personal bloggers have a much-easier time upgrading their installations than businesses. Time spent trying to always be on the most-current version = time *not* spent doing other things, like running a business. @Randy You make excellent points about how feature-rich WordPress has become, especially when describing 2.6.x. By the time of that branch, WP had gained enough useful, regularly-usable features that there wasn’t a huge push to upgrade. This is what kept me on WordPress 2.6.x for the longest time (that, and my breakable custom theme). I don’t know about your idea that more people would adopt WordPress due to the existence of a legacy branch. And if this did increase adoption, it would surely be just businesses who are currently weary of running the latest version of any open-source software. I think in general, I support this idea, but I also know I would never use it (my own blog ventures are not highly impacted by upgrades). » Posted By Spamboy On September 29, 2009 @ 10:55 PM Screencast: Basic Image Editing In WordPress 2.9 The main advantage I see of this is leveraging the delivered functionality to automatically resize your entire library at once. One limitation of the media library now is that you’re stuck with your image sizes as they were uploaded, and there’s no easy way to redo sizes without alot of backend, manual work. » Posted By Spamboy On September 11, 2009 @ 6:21 PM WordPress Dev Chat For 9-10-09 it looks like it is possible to show a link in the backend of WordPress during an upgrade which will contain a zipfile of just the changed files for that version.
This solves my concern that we discussed on Twitter, which means that there won’t be overt promotion of multiple upgrade methods. Having just a link within the administration panel is rather minor. Auto upgrade should be the primary upgrade method with uploading only the changed files coming in second. Last would be replacing all of the files. It was always my assumption that auto-upgrade was replacing all of the files. If it’s not, does what occurs during an auto-upgrade equate to what occurs with “uploading only the changed files”? » Posted By Spamboy On September 12, 2009 @ 10:09 PM What does it matter if I get your blog post an hour after it was published as opposed to 5 minutes? This matters alot for certain types of feeds. The best example I can think of is post comments feeds — the quicker you get updates for new replies, the faster you can add your two cents. I’ve sometimes lost traction in comments conversations because I didn’t know someone had posted a particular reply until an hour later. » Posted By Spamboy On September 12, 2009 @ 10:06 PM @Chris Jean I work in a corporate environment and promote the use of WordPress within said environment. Frequent software updates which are not scheduled/expected does nothing to increase their confidence in any software suite, where having a dependable product — or the fallback of immediate, tremendous support — is of utmost importance. As I mentioned before, I know that WordPress is well-crafted and all known scenarios are tested; my corporate overlords are not as easily convinced. Hence, why frequent updates are “scary”, at least to them. » Posted By Spamboy On August 17, 2009 @ 11:14 AM @Chris Thanks for the additional information from the hackers list (which I do not particpate in, and hence wasn’t privy to). I do assume everyone knew from Matt’s comments — “been there for years, it’s just no one has noticed it until now” sounds at first read that it wasn’t addressed until someone outside of development brought it up. @Joss See above reply. I see what you are talking about now. @Ben The only downside is two minor release updates within almost one week of one another. It doesn’t inspire confidence in the general public, although those experienced with WP know things are perfectly fine. » Posted By Spamboy On August 12, 2009 @ 1:48 PM @Matt if this bug has been around since 2.7, then one must assume that WP development considered the issue to be minor, in order to have not been fixed quite some time ago. Which leads to questions like: why is it considered serious enough now to warrant a fix with a new 2.8.x release? And if it warrants a new release now vs. just rolling it into a future major release, it makes it look like something more serious had been “back-burnered” when it shouldn’t have been? » Posted By Spamboy On August 12, 2009 @ 7:31 AM Listener Poll: What Day Of The Week Should I Record WordPress Weekly? My vote is actually for “Any day BUT Friday.” After a long week at work, and having to get up early every Saturday morning, I can never make the Friday live shows and would have a better chance of doing so if they were recorded other days of the week (except Saturday). » Posted By Spamboy On August 3, 2009 @ 3:39 PM This whole subject could have been communicated clearer from the get-go. Then again, part of the confusion is keeping WP.org and WPMU separate in people’s minds — we’re techy/bloggy/WordPressy enough to know what exactly is meant when someone utters the phrase “WP.org”, but a greater public might not. » Posted By Spamboy On June 2, 2009 @ 3:27 PM Review Of Eventina 2.0 – jQuery Strikes Again Good review — learned something new (JQuery compatability issues between themes and plugins). Please keep up your work with these reviews. » Posted By Spamboy On May 22, 2009 @ 9:54 AM Compilation Of Theme Frameworks Thanks for the tip. BTW, to say that the “usual suspects show up near the top of the list” suggests they were ranked, which Dainis himself did not imply in his post. » Posted By Spamboy On April 29, 2009 @ 12:27 AM WPWeekly Episode 47 – Interview With Vladimir Prelovac In the podcast, you referred to using Flickr instead of the built-in WordPress gallery because the former offers better features. While that might be the case, you should consider the latter because of search. At WordCamp Dallas 2008, John Pozadzides explained in his presentation that it’s better to host the files on your site. Otherwise, when users perform Google searches against your photos, they will be directed to the static Flickr page link instead of the page on your blog which might be using the picture. » Posted By Spamboy On April 23, 2009 @ 3:16 PMComments Posted By Spamboy
«« Back To Stats Page