[wp-trac] [WordPress Trac] #14746: Post Formats
WordPress Trac
wp-trac at lists.automattic.com
Sat Nov 6 02:05:59 UTC 2010
#14746: Post Formats
----------------------------+-----------------------------------------------
Reporter: ryan | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.1
Component: Template | Version:
Severity: normal | Keywords: ongoing-project ui-feedback
----------------------------+-----------------------------------------------
Comment(by mikeschinkel):
Replying to [comment:110 nacin]:
> Interesting idea, but I think revisiting this every 4-6 months (i.e.
every major release) seems sensible.
Not saying my solution is the correct approach, but I think you'll find
4-6 months way too long for the initial follow-up.
Once people start using Post Formats there will be a flood of ideas for
how to use them initially as the 80 percentile use-case patterns emerge
(almost by definition you will not have gotten all of them right no matter
how hard you try.) If there is no near-term way for these common use-case
patterns to be added in a project timeframe people will get frustrated. If
there is not some form of "relief" value people will likely do an end-run
as @greenshady suggests which will likely torpedo the stated goal of
interoperability.
> Just tacking on more formats as we go whenever someone comes up with a
use case is against the goal of having consistency and a standard across
just one area of theme development.
Not "when someone comes up with a use-case" but when it becomes clear
there is an large number of people need the use-case. I'm talking the
ability to add 2-3 a month, not hundreds. Digg-like voting could surface
that; I'm sure there's a plugin that could support that on a WordPress
post somehow.
> A constantly moving standard is impossible to hit.
All standards that are not-moving are by nature dying, as well as those
that were not well-vetted by the broader community in advance. Providing a
simple process to announce the release of new formats on a monthly or bi-
monthly timeframe could allow for crowdsourcing of the needed options.
As always, JMTCW.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/14746#comment:111>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list