Browse: Home / devs
New Home For bbPress Development Chatter

New Home For bbPress Development Chatter

By Jeffro on April 1, 2010

Gautam who is a member of the WPTavern forum recently let us know that he has setup a bbPress Developers area for bbPress developers to chat about developments in the software similar to how WordPress has one. If you are a member of the WPTavern forums and are also one of the few who decided to help regenerate the bbPress project, send him a private message with your email address and he will add you as a member to the blog.

When asked whether the site was endorsed by Matt or considered official, Gautam responded that Matt doesn’t really know about the site just yet. I imagine he will now.

While we are on the topic of bbPress, might as well provide an update as to what’s been going on. As far as I can tell, there has not been a developer chat since January 13th, 2010 and a few other people have noticed this as well. The bbPress forums are still pretty active. In fact, many people are now asking support questions regarding bbPress with BuddyPress.

There is a thread in the tavern forum specifically regarding the off and on activity process surrounding the bbPress project. In this thread, I asked two individuals that initially showed quite a bit of interest in helping to regenerate the project why their activity has faded.

Jeffro – Considering you two were part of the rally to get things back on track for the project, are you both still interested in helping out? Are you guys waiting on direction on what to do and where to go from Matt?

Ryan Hellyer – I wanted to help, but it seemed that after the first IRC meeting or so it was looking like the project was going to just stagnate again, so I haven’t taken much notice since.

Justin Tadlock – Same here. I’ve even went so far as to code my own mini-forum using WP’s custom post types and taxonomies. It’s actually not too difficult. But, I lost the code on a recent computer crash. I might revisit the idea though.

Hopefully at some point, bbPress gets the ball rolling on a consistent basis. Perhaps that will happen once bbPress is turned into a WordPress plugin.

Posted in | Tagged , , | 6 Responses

WordPress Dev Chat For 12-03-09

WordPress Dev Chat For 12-03-09

By Jeffro on December 4, 2009

wordpresslogoPlugin Development Information Post Idea

If you host a plugin on the WordPress plugin repository, you should have received an email letting you know about what is coming in WordPress 2.9 that might break your plugin. The idea was to have 2-3 of these per major release and eventually for point releases if they are likely to break plugins. However, the information contained in these emails will also be published to the WordPress development blog to cover all bases. Andrew is supposed to be publishing the first email on the dev blog either today or within the next few days. Hopefully, this approach solves the complaints of plugin authors saying they don’t have enough time or enough knowledge to know whether their plugin will work on the next version of WordPress.

Google Gears: Leave It In Or Remove It.

The recent news of Google slowly letting support for Google Gears slip by the wayside as they move towards the advancements of HTML5 Cache means that WordPress will either have to remove Gears support or replace it with an equivalent. According to Andrew Ozz, the HTML 5.0 specs are only designed for taking a web app completely offline and cannot be used (for now) the same way as Gears. While the conversation then went into details on reasons for removal, Matt said he was fine with taking it out but that they made *such a big deal* out of putting it in, they need to have a timeline for a replacement unless they no longer believe that the performance increase is valid or worth it. In the end, the decision was to leave it in for now with a view to removing in 3.0 along with a statement about what replaces it – something better or nothing because there is no need / replacement.

Minimum intervals between first beta and final release and between first RC and final

This topic was brought up by Demetris who was inspired by Ubuntu. E.g. Do not go from RC1 to final in less than 14 days, so that people have time to test/translate/upgrade plugins. However, Ryan Boren mentions that the main thing is testing audience. Longer betas don’t get new audience so its the same old people doing the same old things.

Demetris makes the case that if string-freeze were to happen with RC1 that it would give translators enough time to work on the translations. Ryan then makes the announcement that WordPress 2.9 is currently in string freeze which was also mentioned on the Polyglots mailing list today. Matt has been talking about a new i18n strategy where new versions just go live with old strings if they don’t update within X days of release. Ryan usually judges by the amount of i18n tickets that are around when to call string-freeze. However, he agrees that they need to announce string freeze at least a couple of weeks before the anticipated release.

WordPress.org Features Page

I’ve mentioned this in previous Dev chat cliff notes but Demetris was also working on creating a new features page that would replace the one currently on WordPress.org. Matt says he’ll make those new changes live and thanked him for putting it together.

Jane expressed some concerns about the new default first post: http://core.trac.wordpress.org/ticket/11008

Since WordPress 2.9 is in string freeze, the current implementation of the First Post will remain. The discussion then turned to improving the Help tab that is seen throughout the backend of WordPress. One idea that was mentioned by beaulebens gained some traction:

beaulebens – personally i think it would make sense that the entire dashboard was a “welcome screen” the first time (or until you dismissed it) you visited wp-admin, but that’s more work than just the sample post approach. Where “welcome screen” was some sort of “getting started” list of things you should/might want to do/take note of.

I mentioned that I thought the handbook was supposed to supplement the Help tab in the dashboard but that it doesn’t seem to be happening this time around. Then beaulebens had another great idea. beaulebens – it would be awesome if the handbook was available via API, and could be pulled in at relevant places in the Help tab. Quite a few people cheered for that idea.

If you’re interested in reading more in-depth into the discussions including ideas and such that were not mentioned here, view the Chat archive and scroll up. Meetings begin with and end with

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 4PM Eastern time or 9PM UTC Thursdays. #wordpress-dev.

Posted in | Tagged , , , ,

WordPress Dev Chat For 10-22-09

WordPress Dev Chat For 10-22-09

By Jeffro on October 24, 2009

wordpresslogo

Upgrade notification in core

The consensus is that it will not happen. However, Lynne Pops idea to change the first default post in a new install of WordPress to something that contains useful information will likely happen. No update email in core. Use the mailing list. Improve the copy in the first post to give hints and tips like subscribing to the list.

Trac voting

I was responsible for this question. In trac, each ticket has an up or down arrow where people can vote yes or no with regards to their approval of the ticket or to get it in core. As I suspected, the votes mean nothing and the up or down arrows are for decoration.

Multiple custom image sizes with retroactive image reprocessing

Leogermani wrote a patch that adds the possibility to add multiple custom sizes in addition to the core thumnail, medium and large. It also lets you regenerate all the thumbs, in case you changed any size. A few folks were not too keen on the rebuilding effect on previous images the patch would include and it won’t make it into 2.9. However, an edited patch looks good for 3.0.

Mailing lists

The recent WordPress Security thread on the hackers mailing lists ruffled a few feathers of long time members. So, the idea was to create a mailing list for what some deem as useless discussion. There will be a renewed effort to state what the hackers list is meant to be used for in terms of the discussions and content. Westi and others may act as more of a figure head as well. Enhancing this page is a good start which covers mailing list etiquette.

#WordPress ops

Thank goodness this simple thing is over and done with. Matt has added the following people as ops to the WordPress IRC channel. sivel, Viper007Bond, bazza, MarkJaquith, Ozh

Trac configuration

This had to do with enabled XMLRPC into Trac but it’s above my level of comprehension so if you’re interested, the conversation picks up here.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 3 Responses

WordPress Dev Chat For 10-15-09

WordPress Dev Chat For 10-15-09

By Jeffro on October 16, 2009

wordpresslogo

Admin templating – filosofo – I’d like to propose that we abstract a lot of the admin markup, in particular the stuff that’s repeated a lot, such as form elements and things like tables of posts, comments. Much of the core stuff is hard-coded, and plugin authors still have to manually create form elements for option pages.

The basic idea is that too much code was copy and paste material when instead, the code should be written in a way that can be re-used. Alot of the discussion revolves around the creation of option pages, something that will be overhauled in WordPress 3.0.

filosofo - 1) is there interest
westi - we should try and make it easy for plugins to add things _and_ remove our C&P code
junsuijin - if done right it should save plugin and theme authors a lot of work on creating options pages
filosofo - 2) does anybody have any great implementations of something like this that they’d suggest
westi - I think we should make the first focus of this Options pages re-work for 3.0
filosofo - 3) how about I create a ticket and put some code up for people to look at?
westi - ticket++
junsuijin - filosofo++ i’ll add my code as well just to get another take on it if necessary
AaronCampbell - I think there’s interest…a ticket seems a good next step
westi - filosofo: my requirements – lightweight, easy to review, easy to maintain, reduces code size, reduces plugin code size
azaozz - perhaps that has to start with fixing/redoing most of the admin css
junsuijinit- seems that 3.0 options overhaul will necessitate a redesign in anything we ultimately end up using anyway
junsuijin - or at least there’s a good chance
azaozz - there’s a lot in there accumulated over the years

The line of thinking is that for now, PHP4 works. but PHP5 gets you better stuff. Mark Jaquith updated the statistic to say that now 13% of WordPress users are running on PHP4.

jeffr0 – Sorry to interrupt but who do we complain to about the IRC logfile site not working since October 1st?

I’m happy to say that Peter Westwood helped get the IRC logfile site back up and running. I use this site to compile these notes after the meeting and I’m sure there are plenty of others who dive into the logs to see what was discussed.

In the “hopefully simple patches for 2.9″ category: Internal support for conditional scripts (same as existing conditional style support), #10891

The team discussed this and they are not sure if this is the best way to achieve the requirement here and also about how this would interact with the script concatenation so they don’t think it is right for 2.9 due to the feature freeze. Its been moved out to future for now.

http://core.trac.wordpress.org/ticket/10958 Some plugins have unnatural peaks of 20.000 downloads pr day, making the stats unreliable as a measure of a plugins trust within the community. Should be acted upon.

Ever notice in the popular plugins pane in the administration panel of WordPress and see a porn related plugin or some other goofy thing linked to in their? This is most likely the result of plugins taking advantage of the lax way of tracking downloads for plugins.

The team already knows they need something better than what they have but sometimes, the increase in downloads are legitimate. For example, SexyBookmarks was featured on the NYTimes. So in the end, if something seems fishy, we are supposed to report it to plugins at wordpress.org and have them take a look into it.

demetris1 – I started a page in the Codex, as we agreed last week. http://codex.wordpress.org/User:Demetris/Features

Last week, Demetris proposed updating the features page on WordPress.org. He has now created a Codex page so we can collaborate on the effort and provide feedback.

Jane Wells also announced during the meeting that registration for WordCamp New York had opened up. Late in the chat:

Jane_ – jeffr0: you were officially the first ticket purchase

Bragging Rights!

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 1 Response

WordPress Dev Chat For 10-08-09

WordPress Dev Chat For 10-08-09

By Jeffro on October 12, 2009

wordpresslogo

demetris – http://wordpress.org/about/features/ — This page needs some work, or maybe a rewrite — A few months ago a poor soul was asking at the forum when the pMachine importer will be ready! :-D — I’m willing to help with this

I agree with what demetris had to say regarding that specific page on the WordPress.org site. The entire features page needs to be slimmed down, updated, and rewritten so common folks can understand it. I proposed the feature comparison between WordPress.org and .com as a starting point for listing features. http://get.wp.com/ Demetris stated he would create a draft of his proposal for the page on the Codex and then provide updates in follow up meetings.

2.9 feature freeze and scheduling.

While the target date for 2.9 was October 31st, it’s obvious now that won’t happen. The overhaul of the media user interface  is more work than first thought which is the cause for the delay. However, WordPress 2.9 has been declared feature frozen with the exception of three features. oEmbed, post thumbnails, and media UI. The target date for the first beta of WordPress 2.9 is October 31st. From that point forward, progress will be assessed each week with RC releases in November. The final version of WordPress 2.9 has a shot at being released in the second half of November or early December.

Also, once 2.9 hits RC1, work will begin on WordPress 3.0.

I asked Jane about the progress of the CMS handbook project.

Not a top priority, given things will change with 2.9 and no eager dev volunteers to write stuff . Will start push again after meetup. If someone wanted to devote 10-15 hours per week to wrangling people, it would move faster, but no one has volunteered that kind of time, and 2.9 is a higher priority for me personally, since my part has to be done before we hit freeze. Once we’re in beta etc, I’m not needed much on 2.9, and I can shift focus to docs.

Rough Sketches of Media UI.

This link was passed on during the dev chat which contains a PDF file showing pictures of a hand drawn user interface for the Media component. I have a hard time figuring it out without pretty pictures so hopefully, once Jane’s Macbook AIR gets fixed, we can see prettier versions.

ShaneF proposed changing /wp-admin/upload.php to /wp-admin/media-library.php

Shane believes upload.php has no meaning as it’s usually a library.

Jane – I’d suggest waiting until merge with MU and looking at all those names
MarkJaquith – Yeah, our wp-admin URLs are a mess, this needs a comprehensive look at a later date.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 3 Responses

WordPress Dev Chat For 9-17-09

WordPress Dev Chat For 9-17-09

By Jeffro on September 18, 2009

wordpresslogoThis weeks meeting covered basic image editing which is being worked on by Andrew Ozz, Gallery improvements, embeds, and the possibility of a new supported legacy branch of WordPress. The chat heavily focused on the topic of handling gallery improvements along with the use of photo albums. This is a topic that has been discussed in great length in previous meetings.

WordPress IRC Channel Ops – Back in March of this year, a poll was conducted for individuals to vote on who should be added as channel operators for WordPress on IRC. Sometimes in IRC, it turns into the wild west and it becomes frustrating very quickly when there is a troll or spammer which can’t be dealt with thanks to the lack of operator presence. Hopefully, that will no longer be the case as Matt has added Vipder007bond and Sivel to the ops list.

Basic image editing –
azaozz - sure, image editor has been in for few days, no much comments on it for now..
azaozz - at the moment it keeps all old files, so when editing an image many times, files accumulate
azaozz – perhaps needs a way to check which (old) sizes have been used in posts and delete the rest
junsuijin - post meta?
azaozz - may need to separate the attachments meta into 3 fields, old meta, sizes and exif
azaozz - any questions/wishes/complains about it?
sivel - azaozz: honestly haven’t had time to look at the code or play with it
azaozz - ok, if there are any, add them to the ticket :)

I have no idea what the ticket number is. A search in trac for image editor or image editing didn’t provide me with any clear answers.

MarkJaquith – Galleries — this has been disappointing to me. We need to make some decisions. I feel like we’ve thrown a bunch of ideas around but we need to stop waffling.

This topic took up the bulk of time for the meeting. It looks unlikely that the code created through the GSoC project for Media in general will not be used. The general line of thought is to create an album taxonomy which would not be limited to the traditional ‘album’ displays. Considering the magnitude of this project, images will be the primary focus as first with other media types to follow. Last but not least, this project has a high possibility of being one of the first canonical plugins for core which just means one plugin but many contributors.

jeffr0 – Directed at Mark. Has their been any talk of a new supported legacy branch?

Considering the security stuff earlier this month, some folks have been suggesting that WordPress bring back a supported legacy branch of WordPress. I decided to ask if any talk of this has been ongoing in the inner dev circle and Mark replied that he wasn’t aware of any. In fact, Mark stated he would be extremely opposed to an LTS (Long Term Service) branch. Sivel doesn’t think it is something that they are ready to undertake.

MarkJaquith – I’d rather direct resources to making upgrades smoother and showcasing well-coded plugins that won’t break on upgrade.
westi - The only way a LTS branch is going to exist is if the person that wants it creates it. our resources are better directed elsewhere

Embeds – Viper007Bond has been cranking away on something called embeds which would make embedding video content easier. (Trac Ticket 10337) The talk was a bit too technical for me to understand but Mark Jaquith along with some others believe that the code will need an independent security review. If you want to read more about easier embeds, point your browser to here and scroll up.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 3 Responses

WordPress Dev Chat For 9-10-09

WordPress Dev Chat For 9-10-09

By Jeffro on September 11, 2009

wordpresslogo This weeks meeting consisted of an agenda that was light to non existent. However, we still managed to find some things to talk about such as the addition of changed files that are linked to in a release post, quite a few issues dealing with the plugin repository and more.

So far, two people have volunteered to help make the administration area of WordPress more accessible. Jane is giving it till Monday and then she’ll try to get a group together to figure out the best approach.

the question of downloading single file vs full upgrade process

Thanks to Mark Jaquith who dived around in Trac, 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 link and zip file will also be shown in future release posts.

One interesting question I had regarding this new upgrading option is whether uploading just the changed files counted as a full upgrade? Ever since I have used WordPress, upgrades have always been a matter of overwriting the previous package. Mark Jaquith told me it should be the same, if the zip file of changed/added files is accurate. This is good news because I wanted there to be an option in-between the auto upgrade not working and uploading the entire package of WordPress. 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.

If we find any issues related to the new site wide profiles site, who do we report them to? Andy Peatling or what?

Jane told me we should report issues within this forum thread.

Has anyone heard anything at all about 2.8.4 being affected by the latest attacks? I have not.

MarkJaquith – jeffr0: what’s likely happening, if you hear about that, is that they didn’t clean up, and someone has continuing access, even though their install is clean.

Most of the discussion from this point on deals with plugins, the repository, removing bad plugins, reporting compatibility, etc. I’ll just provide a few tidbits of the conversation as nothing much was decided, just a bunch of ideas discussed.

azaozz – there’s another thing about plugins too. Some submit nicer code to get in the repository and then start to add base64_decode stuff
junsuijinany – ideas for handling that type of thing tho azaozz?
azaozz – at the moment the simplest way is to start a forum thread about it
junsuijin – i mean short of scanning any and all plugin submissions for base64 and making it illegal in wp or something
junsuijin – azaozz: would it be worthwhile to have some kind of cron script running over the entire plugins/themes repos, scanning (preg_match) for predefined ‘illegal’ functions like base64, eval, etc. and temporarily disabling any plugins/themes that have uploaded files containing such functions? could also push status messages to end-users that may have gotten the filthy versions
westi - junsuijin: automatic scanning like that will likely just trigger false-positives
scribu – junsuijin: exactly, there are legitimate uses for eval
azaozz – it can only flag some plugins, they will have to be checked by hand..
junsuijin – true westi, it could, but i don’t know any other easy way to make sure that kind of stuff doesn’t happen, and it would be quite possible to make exceptions for any authors that need eval or whatnot

If you’re interested in reading the rest of the conversation, visit the log file and start at Sep 10 21:39:01 2009. If you’re interested in the conversation related to reporting plugin compatibility, start here and work your way up.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 4 Responses

WordPress Dev Chat For 7-30-09

WordPress Dev Chat For 7-30-09

By Jeffro on August 3, 2009

wordpresslogoShane had: “I think we should talk about getting WordPress 3.0 into PHP 5.3.0+ min. PHP 4 is not supported anymore and we need to think about getting the code into a object based for speed and security.”

According to Mark Jaquith, there is about 15% of the WordPress userbase running on PHP4. 0.05% of people are running PHP 5.3. 5.3 does not appear to be an option. Mark also states that supporting 4 isn’t that much of a burden. They are slowly introducing PHP5-only features, which should help reduce that PHP4 percentage. When asked by Jane Wells if he had spoken to any other core developers, Mark said the team did not want to completely abandon 15% of the user base. Perhaps a better approach is seeing how we can reduce that number without forcing anyone’s hand. One way to reduce that percentage is to do outreach to webhosts while also getting some major plugin authors to switch to PHP5 code.

The plan is to add a nag page that only administrators of a WordPress blog can see starting with WordPress 2.9. This nag will feature a link to an article in the Codex that explains why WordPress is dropping PHP4 support and moving to PHP5 only. The Codex page will then be updated with host specific information.

The next topic was the Ideas Forum. Jane Wells: I’ve been cleaning it out, want to get rid of everything outdated etc before we start upgrading it with some better organization. for the stuff that is very technical, I can’t judge if the suggestions are outdated, still good, or valid but dumb. could use some help with people going through and leaving comments so i can close ones that shouldn’t still be there.

Over the coming days, weeks, Jane is going to be going through the Ideas forum and tag certain items she is unsure about that the other core developers can review. Andrew Ozz will also be closing ideas down that deal with TinyMCE being an Rich Text Editor and not an HTML Creation tool. According to Jane, not that many new ideas are being submitted. The ideas forum is a side project and won’t be taken down for work until everything is in order for Sam Bauers to hack away. The ideas forum will be upgraded to bbPress 1.0. One of the ideas proposed by Jane is to create categories for suggestions so people can see what is already there easier, perhaps mapping them to Trac categories. The ideas are not being deleted, but rather closed.

The decision was also made that the team will not be using Uservoice what so ever to do the ideas forum. They will use bbPress 1.0. According to Jane, the plugins on the ideas forum are over two years old. Once the ideas forum gets to the point where it’s ready to be reorganized, the topic will be placed on the agenda for people to weigh in.

Also, there will be a few changes to the status choices for ideas. Among some of the proposed changes: “You can do this with a plugin” -> This is plugin material. As is “good idea! we’re working on it” and “sorry, not right now” and “this is not a core suggestion”.

The next topic was about about committers, workflow and bugs. However, I can’t summarize it because it makes no sense to me. All I can say is that this topic seems to be discussed at every development meeting so it must be pretty important or pretty complicated. If you’re interested in reading the discussion on this topic, I suggest you read through the log file for the meeting. The topic begins at Jul 30, 21:54:34.

One thing I wanted to mention which is not directly related to the meeting is something I read later on in the evening regarding the WordPress Planet feed. Someone brought up a website that was part of the feed that had not been updated in over two years. Jane said she MIGHT put up a vote on the dev blog for people to nominate sites to be included on planet feed and/or sites to take off. Again, she said MIGHT, so it’s no guarantee. However, I was wondering out of curiosity, how many of you would nominate WordPress Tavern to be added to that feed? If not, let me know your reasons why.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , | 19 Responses

WordPress Dev Chat For 7-15-09

WordPress Dev Chat For 7-15-09

By Jeffro on July 15, 2009

From now on, the way I am going to format these posts is to bold the item that was listed on the agenda and then below it, publish a summary of what was decided for that item.

Creating an announcements mailing list that include all plugin and theme developers and using it to send information on significant core changes that are likely to affect them. It would be very low volume (1-2 emails per month) and would include by default everybody that is listed as contributor to at least one plugin or theme hosted on wordpress.org. Of course it would be open to everybody to subscribe or unsubscribe.

The majority of folks who participated in the chat agreed that this was a great idea. The list would be low volume where announcements could be pushed out if their are changes to the WordPress API. This would provide theme and plugin authors a heads up on a change that may break their project. Plugin and theme authors would have the ability to ‘Opt-Out‘ if they don’t want the announcements.

matt posted about adopting plugins: “I saw something on PEAR today I like (I know, gasp!) and it was where certain modules were marked as abandoned and up for adoption, and they seemed to have a mechanism for adoption.” example: http://pear.php.net/package/Net_DNS

Many thought the idea of inactive plugins on the repository to be put up for adoption was a great idea. If an author got an email about a change and knew they weren’t going to have time to bother updating, the WordPress team could point them somewhere to announce that. The thinking right now is that based on a number of failed attempts to get in touch with the plugin author could be a base for what is considered non maintained. Then it goes up for adoption, or branches and the old one is marked as dead.

scribu - an edge case: what if a plugin author still maintains a plugin, but doesn’t update it on Extend?
ddebernardy - then he answers the mail
Jane_ - if there’s a policy in place that un-updated plugins in repository go to bed after time, am guessing they’d be more likely to update there too

Meta tables was on the agenda but has been pushed to the July 22nd meeting.

Ddebernardy wanted to talk about bugs and committer workflow, but without rboren, hard to make any firm progress This topic might be discussed again on the July 22nd meeting.

westi posted “User experience for comment deletion undo / trash. (http://core.trac.wordpress.org/ticket/4529)”

The question regarding this ticket deals with the User Interface. There might be a poll in the future where users can vote on whether they want a link to a trash can or a simpe undo. Next was the discussion surrounding whether the stuff in the trash can should auto-delete or not after 30 days. The decision was that by default, trash will autoclear but there will be hooks available to override how long before things get deleted.

The results from the media survey were to be published the night of the meeting with screenshots but it hasn’t happened yet. Look for that on the dev blog at some point in the near future. Also, the poll results didn’t change much from last time.

Out of all the GsOC projects, all but one passed. The event management plugin suite for buddypress is the one not moving forward, though the student says he is going to keep working on it even though it’s no longer gsoc

To see the entire log file for this day which contains the fine details into the various agenda topics, head over to the WordPress Dev IRC Channel Log.

Posted in | Tagged , , , | 2 Responses