Post items as replies to suggest agenda items for dev chat on July 15, 2009.
Andrew Ozz, Peter Westwood, Jane Wells, and 4 others are discussing. Toggle Comments
Meta Tables again. I hate to bring it up, But its been raised again.
There needs to be a way to store Meta for comments, as well as meta for media (the postmeta table), as well as potentially for taxonomies (ie. more than a description, potentially computer-readable data).
Just as long as there’s no meta for meta. That scares me. 😛
Bugs and committer workflow. Just to refresh your memory a bit, see this and the follow-ups that are in line with it:
Dare I add, too, that based on the past 2 months and:
… things haven’t changed much?
You’re right, they haven’t changed much in the last two months. I’d guess that’s because of the “oh-crap-we-better-fix-this-right-now” issues around 2.8’s unexpected bugs. Once 2.8.1 is officially out, I’d think we could slow down enough to address some process issues and work out the wrangler/ranger/mentor stuff. I agree it should be a priority.
User experience for comment deletion undo / trash. (https://core.trac.wordpress.org/ticket/4529)
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.
I like that idea, but I think if you have something in the directory you should be required to be subscribed.
Yes, was thinking we can auto-add everybody listed there at the moment and add new emails as new plugins and themes are approved.
Agreed. Don’t forget cases where an author abandons the idea of working with WP, though. They need to be able to unsubscribe if they decide to switch to something else.
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. Here’s an example.
I like it too. Perhaps prospective maintainers can introduce themselves on wp-hackers (if not already known) and sign up as plugin developers on wordpress.org, preferably after adding a patch for that plugin on the plugins trac.
It’s a great idea – would it not be better as a blog/ forum with rss2email type subscription available – you could always auto-subscribe people to the feed as email but make it a more public environment and gain from code markup from syntaxhilighter
If it was a blog/forum with discussion, then it would wind up competing with hackers list, and wouldn’t be low volume. If it’s not low-volume, people will filter it and probably miss the important announcements (hey, we’re changing an API, so you’d better read up on the changes and update your plugin asap!).
@Jane: I wasn’t thinking of allowing on site discussion much as I would expect the email list to be broadcast – at most the discussion would be in response to announcements and may be best to just allow discussion via pingback – this at least allows the discussion to be linked to the source.
I think getting the benefits of WYSIWIG code hilighting etc that a mailing list can’t provide (without evil HTML emails) would be a good thing
Was thinking we would post each email here as a post too (we do that anyways) so quick questions/answers can be posted in the comments. However more in depth discussions should probably happen on wp-hackers where they will reach wider audience and ideas (preferably with basic patches or code examples) would go to track.
Worth looking at oEmbed as part of our ‘easier embeds’ feature?
← Agenda for today’s 2.9 dev chat: GSoC u…
The blog for our Summer of Code students… →
Subscribe to this blog and receive notifications of new posts by email.