[15:00:42] <MarkJaquith> Who is here?
[15:00:46] |<-- fergbrain has left irc.freenode.net (Connection timed out)
[15:01:01] <Nazgul> Me
[15:01:11] <mdawaffe> I'll probably be in and out
[15:01:12] <Strider72> present
[15:01:19] <TVSET> here
[15:01:29] <MarkJaquith> rboren and photomatt_london ?
[15:01:39] <Strider72> keeping tabs mostly. I'm in and out as well
[15:02:17] <rboren> MarkJaquith: I'm here, but i have toddler duty.
[15:02:24] <rboren> So typing will be slow.
[15:02:32] <photomatt_london> howdy
[15:05:02] <--| josephscott has left #wordpress-dev
[15:05:37] -->| josephscott (firstname.lastname@example.org) has joined #wordpress-dev
[15:06:07] <MarkJaquith> I've started moving forward on prepare() and marking places that expect pre-slashed data. Marking those places with: // expected_slashed ($slashed_varname)
[15:06:49] -->| fergbrain (n=AndrewFe@wl-dhcp142-33.Mines.EDU) has joined #wordpress-dev
[15:07:07] * westi|dinner is making and eating dinner
[15:07:11] <rboren> MarkJaquith: good stuff
[15:07:18] -->| Danco (email@example.com) has joined #wordpress-dev
[15:07:20] <MarkJaquith> Good news is that many of the places that expect slashed data are inputs that would seldom have need for slashing.
[15:07:39] <rboren> slugs, ids, and such?
[15:07:40] <MarkJaquith> Things like meta_keys (which are usually a-zA-Z0-9_)
[15:08:01] <MarkJaquith> yeah. So that mutes the impact somewhat.
[15:08:19] -->| skeltoac_mac (firstname.lastname@example.org) has joined #wordpress-dev
[15:09:28] <besonen_mobile2> i'm here to offer some feedback about the wp-hackers s/n issue. just finishing up another task.
[15:09:51] =-= skeltoac_mac has changed the topic to ``2.4 Planning at each Wednesday 12:00 PDT (01900 UTC)
[15:10:46] <MarkJaquith> I'll be writing an article about $wpdb->prepare() sometime in the next week, targeted towards plugin developers (good thing is that it is in 2.3, so they can start updating now)
[15:13:27] <MarkJaquith> One other thing I'd like to work on for 2.4: new default "bird's-eye/dashboard" view for Manage > Posts. The dropdowns/search stuff is great for specific views, but the default unfiltered view is not all that useful, especially for things like drafts.
[15:14:18] <MarkJaquith> Don't know if that is affected by admin redesign at all.
[15:15:16] <mdawaffe> MarkJaquith: tangentially - we never did that: if ( count < 35 ) dropdown(); else textbox();
[15:15:16] <Nazgul> Talking about design. Will Sandbox be included in 2.4?
[15:15:42] <MarkJaquith> mdawaffe: for authors/cats ?
[15:15:46] <mdawaffe> yeah
[15:16:01] <MarkJaquith> Runs into scaling issues?
[15:16:03] <skeltoac_mac> Sandbox 1.0 is ready and it supports tags nicely, so I see no reason not to put it in.
[15:16:13] <mdawaffe> MarkJaquith: yeah
[15:16:44] <MarkJaquith> mdawaffe: would be awesome if it had unobtrusive JS autosuggest for the textbox
[15:16:58] <mdawaffe> agreed
[15:17:44] <MarkJaquith> I believe the plan for Sandbox was to bundle it as a non-default theme. Right?
[15:19:42] <mdawaffe> skeltoac_mac: does sandbox 1.0 still have its own skin mechanism (in contrast to WP's native potential for stylesheet only themes)
[15:19:44] <mdawaffe> ?
[15:19:52] <skeltoac_mac> no
[15:20:09] <MarkJaquith> Uses WP native stylesheet-only themes.
[15:20:13] <mdawaffe> good
[15:20:16] <skeltoac_mac> we ripped that out and encouraged stylesheet-only themes
[15:20:23] <mdawaffe> awesome :)
[15:21:23] <skeltoac_mac> non-default theme, yes
[15:21:47] -->| Ozh (email@example.com) has joined #wordpress-dev
[15:22:01] <Ozh> (hello)
[15:22:23] -->| jared (firstname.lastname@example.org) has joined #wordpress-dev
[15:22:27] <skeltoac_mac> I wouldn't mind too much if we broke default-based themes (few or none that I know of)
[15:22:57] <MarkJaquith> How would we be breaking default-based themes?
[15:22:59] <skeltoac_mac> but I wouldn't want to put sandbox in a "default" dir
[15:23:34] <skeltoac_mac> we wouldn't be unless we changed the kubrick dirname from "default"
[15:23:50] <MarkJaquith> ah. Short-sighted directory name, that.
[15:23:50] <skeltoac_mac> which isn't part of the proposal
[15:23:59] <skeltoac_mac> yup :)
[15:24:36] <MarkJaquith> josephscott: how goes the XML-RPC buddy search?
[15:24:41] <rboren> We can move kubrick and map requests for default to the new dir.
[15:24:53] <josephscott> I had two responses
[15:25:08] <josephscott> Dougal said he may have some time, perhaps
[15:25:19] <josephscott> which is excellent, he knows all the background stuff
[15:25:26] <MarkJaquith> excellent.
[15:25:55] <josephscott> and Paolo Tresso who expressed an interest
[15:26:07] <MarkJaquith> rboren, skeltoac_mac, will sandbox files work when integrated into another theme (i.e. without Sandbox's functions.php) ?
[15:27:17] <skeltoac_mac> Sandbox's functions defined in functions.php are unconditional at this time -- fatal to remove
[15:28:06] <skeltoac_mac> themes based on another theme and providing their own functions.php should not prevent loading the basis theme's functions.php
[15:28:07] <skeltoac_mac> does it?
[15:31:01] <Nazgul> MarkJaquith, will there be another 2.0.x maintenace release? We still have some treck tickets milestoned for 2.0.eventually that are just sitting there.
[15:31:42] <MarkJaquith> Nazgul: yeah, there will be. But most of those 2.0.eventually things are probably going to have to be sidelined if they're not security issues.
[15:32:33] <MarkJaquith> skeltoac_mac: I'm thinking of fallback, say if a theme doesn't supply comments.php
[15:32:39] <MarkJaquith> It'll use /default/comments.php
[15:32:52] <skeltoac_mac> oh
[15:33:02] <Nazgul> Afaik non of them are security related. Mind if Ise them than?
[15:33:13] <skeltoac_mac> MarkJaquith: sandbox wasn't meant for that
[15:33:16] <Nazgul> "I close" I mean
[15:33:19] <MarkJaquith> skeltoac_mac: also with get_header() if header.php is missing... get_sidebar(), get_footer()
[15:33:49] <MarkJaquith> skeltoac_mac: Okay, so fallback would still be to Kubrick
[15:33:59] <MarkJaquith> Nazgul: go for it.
[15:34:00] -->| io_error (n=error@unaffiliated/ioerror/x-384576) has joined #wordpress-dev
[15:35:33] <MarkJaquith> rboren: where are we with page searching?
[15:35:43] <Ozh> doing fallback to default theme will probably break a lot of themes (style wise, if not code wise)
[15:35:43] <rboren> The shed is red.
[15:36:06] <josephscott> and the discussion plentiful :-)
[15:36:17] <MarkJaquith> Ozh: fallback to default theme is what we've been doing the whole time.
[15:36:17] <rboren> I'm leaning toward a unified search of everything with page content and excerpts stripped via filter.
[15:37:01] <MarkJaquith> So, relevance-based results?
[15:37:10] <Ozh> Mark: but not extended to more file than doing now, then ? I thought it was about falling back to every missing files (single pages archives etc)
[15:37:22] <rboren> If we can work it, otherwise just use the ordering we already have.
[15:38:06] <jared> <MarkJaquith> rboren: where are we with page searching?
[15:38:06] <jared> <Ozh> doing fallback to default theme will probably break a lot of themes
[15:38:06] <jared> (style wise, if not code wise)
[15:38:07] <jared> <rboren> The shed is red.
[15:38:07] <jared> <josephscott> and the discussion plentiful :-)
[15:38:07] <jared> <MarkJaquith> Ozh: fallback to default theme is what we've been doing the
[15:38:08] <jared> whole time.
[15:38:11] <jared> <rboren> I'm leaning toward a unified search of everything with page content
[15:38:12] <rboren> And maybe add a function that excerpts the relevant part of the post or page.
[15:38:17] <MarkJaquith> Ozh: no, that kind of fallback is still within the theme. If no single.php, use index.php
[15:38:22] <Ozh> ok
[15:38:35] <jared> oops, sorry
[15:38:41] <rboren> no worries
[15:38:59] <MarkJaquith> rboren: so the ordering would be based on date of publishing
[15:39:12] <rboren> yeah, that's what we do now, i think
[15:39:27] <ai2097> "Last modified" might be a good fake for "relevance," but that's a detail ;)
[15:39:38] <rboren> but relevance would be sweet and should be the default if we go there
[15:39:42] <MarkJaquith> Only problem there is that unless you're creating new pages all the time, pages will fall off.
[15:40:54] <ai2097> MarkJaquith: which is what last modified ordering -could- help deal with (albeit in my specific case). But +1 on that.
[15:43:09] <MarkJaquith> mdawaffe, you started on jQuery stuff yet?
[15:43:33] -->| zamoose (email@example.com) has joined #wordpress-dev
[15:43:36] <mdawaffe> MarkJaquith: I have a fairly comprehensive patch that should apply cleanly with a few tweaks
[15:43:53] -->| dcj (firstname.lastname@example.org) has joined #wordpress-dev
[15:43:59] <MarkJaquith> Great. That up on Trac?
[15:44:01] <mdawaffe> I wanted to know if photomatt_london has already started modifying admin files on his local box
[15:44:09] <mdawaffe> MarkJaquith: will be this afternoon
[15:44:29] <mdawaffe> last time photomatt_london did that, he reverted a bunch of other changes so that his patch would apply cleanly :)
[15:44:51] <MarkJaquith> Hm... I didn't think photomatt_london was going to start on that until he got back, but I could be mistaken (or he could have gotten itchy fingers)
[15:45:28] <mdawaffe> ok - I'll put it up this afternoo for people to disagree with in any case :)
[15:45:36] <--| io_error has left #wordpress-dev ("Vote Yes to Dr. No!")
[15:46:11] <dcj> you guys are too effcient
[15:46:16] <dcj> 45 minutes late and the party's over ? :)
[15:46:27] <zamoose> yeah, no kidding
[15:46:29] <dcj> this must be a stand-up IRC meeting
[15:46:29] <zamoose> *grin*
[15:46:29] <error_bot> zamoose: Sent 16 weeks, 0 days, 14 hours, and 40 minutes ago: <RandyWalker> thank you very much for all your help
[15:47:26] <MarkJaquith> rboren: how about refactoring of the admin menu code. Given that any thought, or do you want to wait until Matt starts doing some of the admin redesign (which I think may affect a little bit of the admin menu)
[15:47:45] <rboren> I was gonna wait for that.
[15:47:51] <rboren> Come in behind and make it work :-)
[15:47:58] <--| Danco has left #wordpress-dev
[15:48:17] =-= mdawaffe is now known as mdawaffe|bbl
[15:48:52] <MarkJaquith> okay. My thought about that was that we should definitely retain current API functions for adding menus ... but if the hacky altering of the global arrays has to break, that wouldn't break my heart. Especially if an API for doing the same thing emerged.
[15:49:20] <rboren> agreed
[15:50:15] <TVSET> it would be nice to have more CSS control over admin menu
[15:50:25] =-= westi|dinner is now known as westi
[15:50:35] * westi turns up late
[15:50:36] <TVSET> there was a ticket in trac with my first attempt, but it wans't localization-friendly :)
[15:50:46] -->| CodeNinja (n=Brian@cpe-75-179-6-115.neo.res.rr.com) has joined #wordpress-dev
[15:51:38] <MarkJaquith> photomatt_london: you still here? Have anything to say about wp-hackers S/N ratio issues?
[15:52:59] <zamoose> is the issue that those with commit access and/or real intellectual sway in the process just tune out the list due to noise?
[15:53:05] <zamoose> is that the issue that we need to address?
[15:53:08] <westi> MarkJaquith: he has very lagged poor WIFI so he may have lost connection
[15:54:02] <MarkJaquith> zamoose: (1) too much noise (2) positive feedback loop causes bad S/N ratio to reduce S, further lowering the ratio.
[15:55:02] <zamoose> I think the issue remains, though: if you create a "ghettoized" area for Those In The Know, how do you encourage/recruit the next generation of contributors?
[15:55:15] <zamoose> I can understand not wanting to wade through the chaff
[15:55:57] <zamoose> somebody's gotta be out amongst the hoi polloi
[15:56:48] <besonen_mobile2> zamoose is hitting the nail on the head
[15:57:22] <ai2097> That whole argument's already gone down on the list, and it can go back-and-forth 'till everyone's fingers fall off. What's option 3?
[15:57:40] <MarkJaquith> Yeah, that's definitely a concern. Trac contributions could be one way that people prove themselves.
[15:58:20] <zamoose> trac suffers from the s/n problem just as badly, though
[15:58:28] <zamoose> how many dupe issues get submitted?
[15:58:40] <zamoose> how many post2cat tickets were generated and then closed in the last two weeks?
[15:58:41] <MarkJaquith> I don't think it's that bad on Trac.
[15:58:55] <zamoose> I subscribe to the "all tickets" mailing option
[15:59:02] <zamoose> it definitely gets bad on certain days
[15:59:14] <zamoose> esp. coming back on a Monday after a bughunt weekend *grin*
[15:59:15] <TVSET> I just unsubscribed from that
[15:59:32] <westi> trac is not too bad and the post2cat type issues can be solved with better communication of changes which I am trying to address
[16:00:01] <westi> with weekly posts on whats happening in trunk
[16:00:11] <zamoose> westi: the fact remains, though, that people [ab]use trac in a similar fashion to wp-hackers, submitting what ought to be Support forum posts...
[16:01:02] <westi> zamoose: yes and they will do that what ever unless we take the approach that other projects have taken in limiting what can be a ticket
[16:01:08] <MarkJaquith> zamoose: but at least with Trac, we can close tickets... they don't tend to go on and on like wp-hackers threads.
[16:01:26] <zamoose> true, but ANYONE can close AND reopen them
[16:01:31] <zamoose> it's a degree of control
[16:01:49] <zamoose> but I think it benefits from more of a "security by obscurity" than the other venues
[16:02:01] <westi> if you reduce the control on those who can close and open tickets you just put more work on the people with the power
[16:02:12] <MarkJaquith> Yeah.
[16:02:23] <westi> and increase the hurdle height for people who want to contribute
[16:02:33] <besonen_mobile2> exactly
[16:02:38] <zamoose> I understand that
[16:02:41] <Strider72> how often do people close tickets that they shouldn't close?
[16:02:47] <westi> we need _anyone_ to be able to reopen a ticket if the issue is not fixed
[16:02:48] <zamoose> 5% of the time or so
[16:02:55] <zamoose> in my estimation..
[16:03:18] <zamoose> westi:
[16:03:20] <zamoose> agreed
[16:03:21] <Strider72> better to reopen existing than just have them post a new one.
[16:03:22] <MarkJaquith> But we have people watching, like lloydbudd et al, who handle that nicely.
[16:04:06] <westi> the only thing trac needs is a way to block people when we get the very infrequent spam attacks
[16:04:13] <zamoose> I guess what I'm trying to express is that if wp-hackers is shut down as the Forum Where The Magic Happens and Trac gets promoted fully to that status, there is a distinct possibility that it could begin to exhibit similar behavior
[16:04:21] <lloydbudd> the team is pretty good about it, I'm only a small part of it
[16:04:49] <zamoose> what, you don't want discount Soma?
[16:05:00] <zamoose> and that supr-gro grass seed, my goodness!
[16:05:09] <zamoose> *grin*
[16:06:10] <MarkJaquith> We're not talking about having Trac be where discussions/future of project type stuff happens. Trac is for fixing bugs and letting your code speak.
[16:06:28] <Strider72> Could it make sense to put a posting limit on the mailing list? 2 emails per day or something? Would at least encourage consolidating comments (and taking aspects of discussion off-list)
[16:06:41] <zamoose> it also gets "Here's an idea and let's get diffs associated with it" tickets, Mark...
[16:07:04] <dcj> down with artificial limits
[16:07:05] |<-- fergbrain has left irc.freenode.net (Read error: 113 (No route to host))
[16:07:06] <zamoose> Strider72: artificially limiting discussion isn't a great idea, IMNSHO
[16:07:14] <dcj> if somebody is being abusive on a list then warn them and then ban them
[16:07:46] <besonen_mobile2> 2 emails per day is interesting because it provides a mechanism for encouraging people to think before they post
[16:08:04] <dcj> or to withhold useful comments because they're afraid they'll have somethign more important to say later
[16:08:14] <besonen_mobile2> and doesn't create a barrier
[16:08:17] <zamoose> dcj++
[16:08:18] <MarkJaquith> I think that's a recipe for having people cram a bunch of topics into one e-mail.
[16:08:25] <zamoose> most def
[16:08:27] <Strider72> I'm not advocating so much as bouncing ideas.... :)
[16:08:41] <dcj> i'm not advocating so much as crushing ideas :)
[16:08:53] <zamoose> what about a web-based system with a karmic component ala Slashdot?
[16:08:59] <dcj> i don't believe there is any kind of regular "list standards" email on the ilst
[16:09:03] <dcj> that might be a good starting point
[16:09:09] <zamoose> then the annoying ones get karma'd out of the discussion
[16:09:13] <dcj> to clarify and elaborate on what is considered good form for the list
[16:09:18] <zamoose> griefers, etc. can be policed by the community itself
[16:09:27] <dcj> send it once a month (perhaps in lieu of the fairly useless and chatter-inspiring "stats" post)
[16:09:33] <Strider72> I'm on another list that has that as a "strongly encouraged rule", but not enforced by software in any way.
[16:10:09] <Strider72> dcj: heh :)
[16:10:24] <dcj> you can get a lot of mileage by having a few moderator-types gently curtail conversations
[16:10:28] <dcj> (ahem, php, cough)
[16:10:44] <dcj> assign rights of banning/probation to some moderator-types
[16:10:44] <MarkJaquith> dcj: I agree.
[16:11:08] <zamoose> the mailing list stats that [checks wp-hackers list] Roy sends out each month are an interesting metric -- any way to leverage something like that?
[16:11:44] <jared> I think the moderator concept is a good one; maybe a warning then a ban
[16:11:52] <dcj> definitely work probation in there
[16:11:56] <MarkJaquith> zamoose: I don't think we're looking for quantitative methods like karma points or statistics.
[16:11:58] <dcj> you can ban somebody from posting for a week or something
[16:12:11] <zamoose> so the question becomes: how to jumpstart a meritocratic mailing list?
[16:12:25] <jared> The most important thing I think would be putting an end to out of control threads
[16:12:27] <dcj> just the understanding that inappropriate behavior will have consequences helps a lot
[16:12:31] * TVSET agrees with the human moderation idea
[16:12:33] <ai2097> Get a cool-headed list mom.
[16:12:36] <jared> by someone who everyone will/must respect
[16:12:41] <dcj> somebody comes in and says "OK, that's enough guys. Thanks."
[16:12:53] <dcj> and if people flagrantly abuse the declaration, they get a week vacation from posting.
[16:13:16] <dcj> this is what apple's programmer lists do
[16:13:24] <Nazgul> There are a lot of list out there where a moderator "approves" posts before they're forwarded to the list.
[16:13:25] <dcj> they're still busy as hell but fairly high signal:noise
[16:13:41] <dcj> i think complete moderation is too much work for the moderators
[16:13:44] <Nazgul> Think bugtraq for instance
[16:13:50] <dcj> for the size of this list
[16:14:09] <besonen_mobile2> moderation is too much work
[16:14:36] <TVSET> post moderation is much lighter... pre-moderation needs several people in different time zones with lots of free time on their hands ;)
[16:14:38] <dcj> that's why consequences-based intervention is good - it can slack off and on elastically without dire consequences
[16:14:42] <Strider72> I think the "Rules" posting each month is a must-have too. Encourage taking things off-list at times, how to quote appropriately (instead of <500 lines of nested quotes> followed by "me too", etc...
[16:14:43] <TVSET> that just limits the moderators' pool
[16:14:45] <Nazgul> No more work than reading all post and moderating them afterwards if needed.
[16:15:17] <dcj> Nazgul: tons more work
[16:15:17] <TVSET> Strider72: i think 40% of Gmail users has something to do with overquoting :)
[16:15:21] <Ozh> define('END_FORMULA', "OK, that's enough guys. Thanks.") && promote committers to list-mom/banner status
[16:15:38] <Ozh> with a clear mailing list rules & goal
[16:15:48] <dcj> Nazgul: compare it with a traffic cop who only enforces on a car-by-car basis when there's a traffic jam
[16:15:55] <dcj> Nazgul: when things are flowing smoothly, just kick back.
[16:17:02] <Strider72> Heh. Give an award for the first person banned. ;)
[16:17:34] <Nazgul> dcj: See your point.
[16:18:19] <zamoose> I like this post hoc comment moderation solution:
[16:18:19] <zamoose> http://www.younggogetter.com/2007/08/28/douche-bag-our-first-official-wordpress-plugin/
[16:18:21] <zamoose> *grin*
[16:18:32] <besonen_mobile2> i agreed that establishing some official guidelines would help a lot--and these can be casually referenced by any participant
[16:18:44] <MarkJaquith> Would like to have this conversation when photomatt_london is around -- maybe next week when he's back in the States. He kick-started it and likely has some ideas on the matter.
[16:18:55] <ai2097> besonen_mobile2: Be careful -- citizen enforcement could lead to more flamage.
[16:20:08] <besonen_mobile2> ai2097: my experience has been that this is generally not the case
[16:20:41] <Strider72> If a "citizen" gets over-zealous with enforement, a mod can poke them in the ribs....
[16:21:08] <Strider72> zamoose, that plugin is hysterical. :)
[16:21:25] <besonen_mobile2> in fact it's typically easier because everyone is empowered maintain community standards
[16:22:51] <zamoose> so here's one of the issues I see in this whole S/N issue
[16:23:21] <zamoose> there's a perception that the upper reaches of the WP development community are unresponsive to enduser concerns, suggestions, etc.
[16:23:40] <zamoose> true or not, it has resulted in fire from all corners (see: Habari)
[16:23:57] <zamoose> fair or not, it is a perception that is out there
[16:24:05] <zamoose> I too want to hear Matt's take on the issue
[16:24:35] <zamoose> but in waiting for him to make his call/pronouncement/etc. seems to be in-line with those criticisms (once again, fair or not)
[16:25:10] <zamoose> now obviously Automattic pays the WP.org hosting bills and thus can make every call they wish in re: services and infrastructure offered
[16:25:34] <zamoose> and if I don't like it, I can establish something on my polly wolly crappy DH shared host and attempt to draw others
[16:25:46] <MarkJaquith> I want to hear his opinion. It's not a pronouncement, but it does carry weight.
[16:26:04] <zamoose> no I understand that
[16:26:16] <ai2097> Could I ask about work on api.wordpress.org WRT bug 5117?
[16:26:35] <ai2097> I know we only have a couple minutes left, but I'd really like to work on fixing that bug.
[16:26:41] <zamoose> I cede the floor to the Honorable ai...
[16:26:42] <zamoose> *grin*
[16:27:38] <MarkJaquith> ai2097: agreed that it is an issue. "up to date" is assumed, so we get false positives.
[16:27:48] <MarkJaquith> Might be better if the UI for displaying it was different.
[16:28:18] <ai2097> Well, the service doesn't indicate a difference between "not present" and "no updates" so the UI doesn't know what to show.
[16:28:21] <MarkJaquith> Have three states: "update available," "up to date," "unknown"
[16:28:23] <Ozh> 'up to date', 'please update', 'could not checked' are sane & needed options I think
[16:28:29] <Ozh> (voilà)
[16:28:58] <jared> +1 to that (Mark & Ozh)
[16:29:02] <ai2097> I need to change api.wordpress.org's service to add that piece of information, but the source isn't available -- I can't make a patch to fix this bug on my own.
[16:29:25] <ai2097> (Well, short of scraping SVN *g*)
[16:29:59] <Ozh> also, this kind of enforces an extra column I guess, in plugin list presentation, otherwise list would get really unreadable & long
[16:30:10] <zamoose> does api need to be fixed or the WP end of things parser?
[16:30:30] <ai2097> The API returns nothing if the plugin is not in the repo, and if the plugin is up to date.
[16:30:39] <zamoose> Ozh: why not break it into three sections, grouped verticall?
[16:30:47] <MarkJaquith> I think we could do it without using a lot of space. Think red x, green check, orange question mark.
[16:30:50] <zamoose> errm verticaly
[16:30:58] * zamoose smacks forehead
[16:31:11] <MarkJaquith> er, red exclamation point.
[16:31:35] <zamoose> Mark: with a legend at the top or bottom?
[16:31:40] <Ozh> Mark: yes. In any case, no more extra line under checked plugin.
[16:31:41] <westi> MarkJaquith: excellent idea - in the row itself
[16:31:42] <zamoose> or title="" attributes
[16:32:02] <MarkJaquith> zamoose: yeah. title. And for things that have update, expand like we do now.
[16:32:20] <Strider72> +1 on MarkJaquith's icon concept. Must include title= though so mouseover shows what it means.
[16:32:24] <jared> Icons in the rows + a one line legend would be nice
[16:32:27] <zamoose> I still think out-of-date plugins should be marked in "color: red" so as to blind the admins
[16:32:31] <MarkJaquith> But we need the API to support it first. I'll assign the ticket to Matt and we can discuss next week.
[16:32:50] <ai2097> Thank you so much.
[16:32:52] <Ozh> could this (presentation with red/green/orange stuff) be something the happy cog team have an idea about ? (sorry I'm not sure I'm fully aware of their mission)
[16:33:06] <MarkJaquith> Another reason to assign it to Matt. Don't know the answer to that.
[16:33:19] <MarkJaquith> He should be getting started on that in the next week.
[16:34:28] <Ozh> (maybe dumb idea, but I thought, if the admin part is fully revamped, this might even be worth a '3.0' version)
[16:34:42] <zamoose> are there any other mockups of the designs floating around out there other than the three wireframes Matt posted a while back?
[16:34:53] <Strider72> What about the discussion about adding a hook or API for third-party checking? non-WP-hosted plugins?
[16:35:03] <MarkJaquith> Ozh: really don't want to get into version inflation territory just yet.
[16:35:12] <ai2097> Strider72: Trac #5116
[16:35:13] <wp-trac-bot> ai2097: http://trac.wordpress.org/ticket/5116 normal, normal, 2.3.1, Quandary->anonymous, new, WordPress (plugin) updates can trigger innapropriatly for non-hosted plugins
[16:35:22] <MarkJaquith> zamoose: don't think so.
[16:35:45] |<-- CodeNinja has left irc.freenode.net (Read error: 110 (Connection timed out))
[16:35:47] <zamoose> can someone crack into Matt's email and make it so? *grin*
[16:36:21] <MarkJaquith> Strider72: I'd be open to that. We want to encourage hosting on wp.org, but I don't think it should be mandatory.
[16:36:55] <jared> I'd think for non-WP hosted plugins, there could be at least a hook in that plugins could use to implement their own version checking
[16:37:13] <zamoose> what about having plugins simply host the README?
[16:37:29] <zamoose> allow for download location to be specified in the metadata
[16:37:33] <MarkJaquith> zamoose: we don't want to make the client side too heavy.
[16:37:36] <zamoose> then there's only one update beacon
[16:37:45] <MarkJaquith> oh, hm.
[16:37:54] <zamoose> the devs update their README on wp.org
[16:37:59] <zamoose> when they release a new version
[16:38:00] <ai2097> zamoose: Because then wordpress.org would advertise the plugin.
[16:38:03] <jared> Yeah, I think quot-updates only for WP-hosted, but notification hooks for others
[16:38:05] <ai2097> Which may not be desirable.
[16:38:22] <zamoose> or it could be very desirable
[16:38:24] <jared> meant auto-updates
[16:38:49] <Strider72> Modify the wordpress plugin hosting to allow for a "update notification"-only entries for non-hosted plugins?
[16:38:55] <zamoose> yes
[16:39:09] <MarkJaquith> The readme.txt format is documented and the parsing code is open source, so someone could implement it on their own site if they didn't want it on wp.org for whatever reason.
[16:39:21] <MarkJaquith> I think Alex King has done that.
[16:39:24] <zamoose> then, theoretically, there could exist a known ecosystem of "WordPress-approved" plugins
[16:40:15] <jared> What about (once the not-available status mentioned above is implemented), a hook that fires only on not-available responses, to allow plugin devs to use their own, if they want to
[16:40:17] <Strider72> I'm just thinking that the "single beacon" idea is a good one. If your WordPress install is checking all over the place when you load (or reload) the Plugins page, it could take a looong time.
[16:40:24] <ai2097> Waiting 10 minutes for your plugin page to load because it's pinging disparate places that are down is not a fun user experience. Also, I'd rather not splatter my stats hither and thither. ;)
[16:41:45] <Ozh> the pinging could be ajaxed, like with devnew & incoming links ?
[16:41:55] <ai2097> I run with JS turned off.
[16:42:20] <--| skeltoac_mac has left #wordpress-dev
[16:42:39] <Strider72> You'd have to ajax the whole page, wouldn't you/ Does the checking happen every time the page loads?
[16:42:55] <MarkJaquith> Well, we've run long. Have some stuff to think about for next week, or maybe to bring up on wp-hackers. I'm off to start dinner.
[16:43:11] <ai2097> Sorry for the late question. :)
[16:43:13] <zamoose> back to the ramparts, errr, wp-hackers!
[16:43:16] <Ozh> last suggestion -- not sure if it's the place, it has been already expressed by some on wp-hackers I think : I'd love to have something like xref.wordpress.org (ideal would be xref.wordpress.org/XXX where 'XXX' would be '1.5', '2.0', ..., '2.2.2', '2.2.3', '2.3' & trunk
[16:43:53] <westi> Ozh: by xref do you mean phpxref style?
[16:43:56] <Ozh> yes
[16:43:57] <ai2097> Ozh: What I'd love? Good PHPdoc. ;)
[16:44:00] |<-- MarkJaquith has left irc.freenode.net ()
[16:44:24] <Strider72> MArk's gone. Bring out the beer!
[16:44:28] <westi> Ozh: I hope to do something like that esp when we have more phpDOC stuff in as that makes it really useful
[16:44:46] <Ozh> i don't know if there are other/better stuff than phpxref, but that's my most used WP related tool
[16:44:46] <ai2097> @since. @since. @since.
[16:44:56] <westi> also I'm considering a wphooks.flatearth.org style WP blog which functions <> versions mapping
[16:45:36] <Ozh> woot
[16:45:41] <westi> i just need to write the searching and importing code to generate the content automatically - pulling in and parsing the PHPdoc for the functions
[16:45:48] <westi> as the post content
[16:45:53] <ai2097> What? There is no PHPDoc.
[16:46:36] <westi> ai2097: there is some... it took a while to persuade matt ;-) there is more detailed docs on the codex though
[16:47:33] <ai2097> I'm all about specifying public APIs to a T; PHPDoc is my weapon of choice. I don't see nearly enough of it to be useful (and I see plenty of subtle API semantic changes between releases).