Last Wednesday, the core development team and a number of contributing developers met in the IRC #wordpress-dev channel to talk about which features should be included in version 2.9, which is now entering the development phase. We’ve been planning to focus on media features in 2.9 for some time, and unsurprisingly, it was media features that dominated the discussion.* A large percentage of the requests we get from users are for more/better media features, so we’ve decided to focus 2.9 on building an infrastructure for improved media handling that we can continue to build on in versions to come. In that vein, we need your input to determine which features to prioritize and build sooner rather than later.
These are the features that we’re asking people to vote on (in alphabetical, not prioritized, order):
Additional Media Filters: In the uploader, you can currently upload an image from your hard drive, link to an image from a URL, or select an image from the Media Library. This proposed feature would add links in the Media Library pane that would allow you to filter images to those that had been used most recently, used most often, and/or marked as a favorite. These filters would be available on the Media Library screen as well.
Basic Image Editing: Enable cropping, resizing and 90-degree rotation of uploaded images.
Better Media Settings: Enable the creation of more default media settings controlled in the Settings section, and allow settings to be overridden during the individual media upload process as needed.
Bulk Media Import API: Develop an API to allow for bulk media importing by plugins or importers.
Custom Image Sizes: Instead of hardcoded thumbnail, medium, large, etc. image sizes, custom image sizes would allow you to configure the maximum dimensions for each of the sizes.
Easier Embeds: Make it easier to embed third-party content such as YouTube videos, etc. Similar to Viper’s Video Quicktags plugin.
Media Albums: Ability to create and edit photo albums that can stand alone (as opposed to galleries being tied only to a post), including photostream functionality.
Media Metadata: Enable the use of categories and tags on media files.
Photostream: Create a Flickr-style photostream that simply displays images in a chronological stream (as opposed to grouping in galleries).
Post thumbnails: Choose an image to appear as a thumbnail with your post/article/excerpt.
Revised Media UI: Redesign the uploader UI to make uploading and editing media files a simpler, more user-friendly process.
These descriptions are repeated in the beginning of the voting survey, so if you forget what something means you’ll be able to scroll up to remind yourself. Only the first question (pick your top choice) is mandatory. This survey isn’t very long. Question two lets you assign a general high/low priority to each of the 11 feature suggestions, while question 3 asks you to rank the 11 features in order of priority from 1-11. A text box or two allow you to make additional suggestions, and that’s it. The survey is anonymous, and will be open all week, until Friday, July 10, 2009 at 11:59 PM UTC.
Results of the survey will be used to help developers decide which features to focus on for version 2.9. The 2.9 anticipated feature list will be posted here later in July, after the priority has been determined. How many contributing developers are available to code various features will play a large part in the decision-making process, so if you’ve ever thought of contributing code to WordPress development, now’s a great time to get involved. Developer chats are held each Wednesday in the IRC channel (irc.freenode.com #wordpress-dev) at 9 PM UTC (5pm Eastern, 2pm Pacific).
* – Other non-media features that were discussed either were determined to be better held for a future version for technical reasons, or were so widely desired that they were accepted for the 2.9 roadmap without requiring a vote.
A game programming language has been added to the Free Educational Programming Languages
page. If you have been dreaming of writing your own computer game, this free package, GameKit, may be just what you need to learn how to. It's also useful if you want to teach older children (minimum age: teens) or adults how to program. Check it out.
To avoid misunderstanding: if you're looking for game engines for use with the usual programming languages like C/C++,
Pascal/Delphi, BASIC, etc,
please see the Free Games Engines page instead. GameKit is a programming language on its own, for
writing games, and in spite of its name, is not a general game engine for use with other programming languages.
If WordPress were a country, our Bill of Rights would be the GPL because it protects our core freedoms. We’ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress’s license. There have been some questions in the community about whether the GPL applies to themes like we’ve always assumed. To help clarify this point, I reached out to the Software Freedom Law Center, the world’s preeminent experts on the GPL, which spent time with WordPress’s code, community, and provided us with an official legal opinion. One sentence summary: PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.
Matt,
You asked the Software Freedom Law Center to clarify the status of themes as derivative works of WordPress, a content management software package written in PHP and licensed under version 2 of the GNU General Public License.
We examined release candidate 1 of WordPress 2.8, which you provided to us at http://wordpress.org/wordpress-2.8-RC1.tar.gz. The “classic” and “default” themes included in that release candidate comprise various PHP and CSS files along with an optional directory of images. The PHP files contain a mix of HTML markup and PHP calls to
WordPress functions. There is some programmatic logic in the PHP code, including loops and conditionals.
When WordPress is started, it executes various routines that prepare information for use by themes. In normal use, control is then transferred via PHP’s include() function to HTML and PHP templates found in theme package files. The PHP code in those template files relies on the earlier-prepared information to fill the templates for serving to the client.
On the basis of that version of WordPress, and considering those themes as if they had been added to WordPress by a third party, it is our opinion that the themes presented, and any that are substantially similar, contain elements that are derivative works of the WordPress software as well as elements that are potentially separate works. Specifically, the CSS files and material contained in the images directory of the “default” theme are works separate from the WordPress code. On the other hand, the PHP and HTML code that is intermingled with and operated on by PHP the code derives from the WordPress code.
In the WordPress themes, CSS files and images exist purely as data to be served by a web server. WordPress itself ignores these files[1]. The CSS and image files are simply read by the server as data and delivered verbatim to the user, avoiding the WordPress instance altogether. The CSS and images could easily be used with a range of HTML documents and read and displayed by a variety of software having no relation to WordPress. As such, these files are separate works from the WordPress code itself.
The PHP elements, taken together, are clearly derivative of WordPress code. The template is loaded via the include() function. Its contents are combined with the WordPress code in memory to be processed by PHP along with (and completely indistinguishable from) the rest of WordPress. The PHP code consists largely of calls to WordPress functions and sparse, minimal logic to control which WordPress functions are accessed and how many times they will be called. They are derivative of WordPress because every part of them is determined by the content of the WordPress functions they call. As works of authorship, they are designed only to be combined with WordPress into a larger work.
HTML elements are intermingled with PHP in the two themes presented. These snippets of HTML interspersed with PHP throughout the theme PHP files together form a work whose form is highly dependent on the PHP and thus derivative of it.
In conclusion, the WordPress themes supplied contain elements that are derivative of WordPress’s copyrighted code. These themes, being collections of distinct works (images, CSS files, PHP files), need not be GPL-licensed as a whole. Rather, the PHP files are subject to the requirements of the GPL while the images and CSS are not. Third-party developers of such themes may apply restrictive copyrights to these elements if they wish.
Finally, we note that it might be possible to design a valid WordPress theme that avoids the factors that subject it to WordPress’s copyright, but such a theme would have to forgo almost all the WordPress functionality that makes the software useful.
Sincerely,
James Vasile
Software Freedom Law Center
[1] There is one exception. WordPress does reads CSS and image files to create previews of templates for the template selection portion of the administrative interface. Even in that case, though, nothing in those files calls any WordPress functions, is treated as a command by PHP, or alters any other WordPress data structure. These files are read as data and used to create an image and display a miniaturized version of a webpage to the user.
Even though graphics and CSS aren’t required to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or javascript? So as before, we will only promote and host things on WordPress.org that are 100% GPL or compatible. To celebrate a few folks creating 100% GPL themes and providing support and other services around them, we have a new page listing GPL commercially supported themes.
Two new free online C# tutorials have been added to the Free Online C# Tutorials, References and Documentation
page. One is from the horse's mouth itself (Microsoft) and the other is from a tutorial delivered at a Microsoft .NET Crash Course in Cambridge. If you're hankering to write programs using C#, check these out.
Fancy creating your own cartoon (animation), with or without sound? Pencil lets you create your cartoons as a Flash file, a QuickTime movie file
or as a series of PNG images. For lack of a better category page to list this interesting open source program, I've provisionally added it to the
Free Drawing and Painting Software page. Since it can produce Flash files, you can even exhibit your cartoons on
your own website. (QuickTime movies should work too, but not everyone has the QuickTime plugin.)
Over the last couple months I had a chance to help create a great new product for Stumbleupon. Su.pr lets create short urls, publish directly to Facebook and Twitter and gives you great tracking and statistics around them. Su.pr also helps you get more traffic by making it easy to get your content in front of the Stumbleupon community.
Last week we launched our API which lets you integrate shorten and post functionality into any site or application. Today we are adding the ability to use your own domain for shortening. This lets you have urls like http://joshuaeichorn.com/9OPL so your readers can know what domain they are going too before they click on the link.
Now down to the fun part installation.
Step 1, Sign up for Su.pr
Just go to the su.pr homepage and sign up using suprjosh for the invite code (The code is good for 500 sign ups).
Step 2, install and configure the PHP re-director
I’m not going go over this in detail since instructions are already available from su.pr.
Note: when installing the rewrite rule you’ll want to make sure its not catching any of your other pages, I put mine after all my custom rules and added a condition to check the given url wasn’t the name of a file or directory.
If your doing your URL rewriting in PHP you might want to handle the link detection there instead, but 4 character words with no extension aren’t too common.
Step 3, Test is out
Now that you are up and running any short url created on Su.pr for your domain will be use your domain instead of su.pr for the shortening. If you ran into any problems let me know, I will see what I can do to help.
Details on how things work
The settings on your server tell Su.pr if it has a redirector
If the redirector is enable all new Su.pr urls for the matching domain are made with your domain
Requests go to your server and are picked up by the rewrite rule
The redirector on your server makes a call to the Su.pr API which returns a domain redirection url, something like http://su.pr/d/joshuaeichorn.com/abcd
The user is redirected back to su.pr and then forwarded to the correct page on your server
The double redirection at the end lets us collect stats and do the required setup for showing the Javascript version of the Stumbleupon toolbar.
Two new free tools, an icon editor and a cursor editor, have been added to the
Free Resource Editors, Compilers and Icon Editors page.
The icon editor, IcoFX, lets you create icons, such as the "favicon" icon
that is used by websites or the icons that appear on your computer desktop. The cursor editor, AniFX, can be used to create cursors, even
animated cursors, that you can integrate into your programs or substitute for existing ones to customize your computer. Check them out.
2.8.1 Beta 2 is ready for testing. Download it, check out the changes since beta 1, and review all tickets fixed in 2.8.1. We especially suggest, recommend, and beg that plugin developers test their plugins against beta 2 and let us know of any issues. Notable fixes in beta 2:
Translation of role names fixed
wp_page_menu() defaults to sorting by the user specified menu order rather than the page title
Upload error messages are now correctly reported
Autosave error experienced by some IE users is fixed
Styling glitch in the plugin editor fixed
SSH2 filesystem requirements updated
Switched back to curl as the default transport
Updated the translation library to avoid a problem with mbstring.func_overload