<MarkJaquith> Everyone ready?
<rboren> let's do it
<Strider72> hola
<MarkJaquith> photomatt_: what's the status on Happy Cog stuff? That may influence a lot of stuff.
<photomatt_> let's start by everyone saying what they'd like to talk about, free form
<skeltoac> I want a puppy
<photomatt_> then I'll collate and we can go in an order, and try to wrap it up by 1:30 at the latest <MarkJaquith> "Undo?" instead of JS "Are you sure?"
<photomatt_> I'd like to spend a few minutes on development wp-hackers vs trac
* westi arrives
<Strider72> start with broad sweeps or little stuff?
* nikolayb too
<skeltoac> wp-hackers has been a clusterbomb lately
<photomatt_> a better theme directory, perhaps with update support
<photomatt_> one-click plugin upgrades from admin
<rboren> Happy Cog, wpdb->prepare, jquery
<rboren> New theme
<westi> filter normalisation
<MarkJaquith> Better "Manage > Posts" default view (like a mini dashboard for your posts -- default view sucks now)
<Nazgul> wpdb-prepare indeed
<Strider72> Theme concept: Currently you can base a theme off a different one with a changed CSS file. What about "use that other theme, except for this modified header file"?
<westi> integrating GSOC stuff
<MarkJaquith> Improved comment handling in the admin -- "Comment inbox" -- Gmail-esque Archive/Spam/Delete
<nikolayb> code reuse from me
<westi> Undo
<westi> code reuse++
<Nazgul> Solve notices
<josephscott> some XML-RPC clean up, feature catch up.
<photomatt_> Nazgul, nikolayb: I don't know what those mean
<photomatt_> search posts and pages
<Nazgul> Solve notices = ticket #3155
<Strider72> links to Plugins' options pages on plugins page
<wp-trac-bot> Nazgul: http://trac.wordpress.org/ticket/3155 major, high, 2.4, quix0r->anonymous, new, Several "notice" messages in WP 2.1-alpha3
<nikolayb> photomatt_, there are a lot of places in the code which simlilar or the same code
<photomatt_> so refactoring?
-->| ai2097 (n=ai2097@pdpc/supporter/active/ai2097) has joined #wordpress-dev
<westi> photomatt_: yes refactoring
<photomatt_> okay, give me a minute and I'll divide this into user-facing and dev-facing
-->| jared (n=jared@worldcharitypoker.org) has joined #wordpress-dev
<photomatt_> okay I got it
<photomatt_> if you'd like to add something just private message me
<photomatt_> let's start with dev-facing since it's easier
<photomatt_> any objections to wpdb->prepare? MarkJaquith any comments on implementation?
<photomatt_> I'd be happy to see the death of sql injection
<rboren> No objections. Will mess up some plugins, but buy us security.
<skeltoac> plugins won't be able to query directly?
<MarkJaquith> No, they'll still be able to. Plugin impact should be small.
<photomatt_> that's what I expected
<rboren> Just some double escaping.
<MarkJaquith> Ryan is talking about a second component of that -- making all functions expect unslashed data.
<nikolayb> maybe we should try to find a way to make a query with one call of a wpdb method
<rboren> Yeah, I jump straight to component two. :-)
<photomatt_> that has a much larger impact
<nikolayb> now one has to call: $wpdb->get_results($wpdb->prepare(...));
<MarkJaquith> Yeah. wpdb->prepare() should have no compat impact by itself.
<rboren> Unless prepare also escapes.
<photomatt_> right now inside of wp most variables are "safe"
<photomatt_> for SQL use
<rboren> Except when they get run through parse str
<rboren> And of course most plugins don't escape a damn thing
<rboren> But, two issues here. I think everyone wants prepare.
<josephscott> parse_str is a problem.
<josephscott> wouldn't mind seeing it go away
<photomatt_> so the main thing to keep in mind for a change in how variables come in
<rboren> We've had that in AP
<rboren> API forever though
<photomatt_> is that for our core code it's easy to adapt, but for plugins I could see it being tricky to make a plugin version compatible with before and after
<MarkJaquith> The worst side effect is double-escaping -- it's not exactly catastrophic.
<photomatt_> to a user that's unacceptable
<rboren> Well, the bazillion plugins that don't escape at all will have no problems.
<jared> As a plugin dev I'd suggest that those who are escaping now could check for the new prepare function(s) and handle both cases
<MarkJaquith> We need to identify the functions that expect slashed data -- can't really get an idea of the impact until we have that.
<rboren> All except one, I think.
<MarkJaquith> And we need to move on this early in the cycle.
<photomatt_> agreed on both with MarkJaquith
<photomatt_> let's leave it there
<rboren> next?
<MarkJaquith> We can move forward with prepare() for any function that expects unslashed data. I'll post about how to implement.
<photomatt_> rboren said "jquery", did you have anything specific there?
<rboren> List manipulation from mdawaffe
<rboren> AJAX
<rboren> all moving to jquery
<photomatt_> hear hear
<photomatt_> next up, xml-rpc cleanup, josephscott?
<Nazgul> Are we going to include the Google SoC page-reorder project into the core?
<josephscott> I went though the current tickets: http://pastebin.ca/716344
<photomatt_> Nazgul: hold off on that
<josephscott> the xmlrpc.php file itself needs some clean up, spacing/tabs is icky and all over the place.
<Nazgul> Ok, thought it was part of list-manipulation
<josephscott> code is duplicated in some places and just plain broken in others.
<MarkJaquith> it's also been a source of security issues, so it could use a bunch of eyes on it.
<josephscott> (Alex C. mentioned some broken XML-RPC methods on the list a few weeks ago).
<photomatt_> josephscott: main concern right now is that's an island
<josephscott> in what way?
<photomatt_> it really only has one person looking at it in any given time, patches get rubberstamped more than reviewed, and we did have that SQL prob
<josephscott> I'd love to have more people on it
<josephscott> there are still parts of it that I don't think have been looked at in a very long time
<westi> its one area where a good test harness client would be _really_ useful
<photomatt_> very good point
<photomatt_> anyone want to look join in on xml-rpc and a possible test client?
<westi> i have always reviewed patches in xmlrpc with trepidation - it usually involves installing and testing with a few clients before I am happy
<josephscott> agreed, my hodge podge of test scripts is pretty basic at the moment.
<photomatt_> a test client like APE would be generally useful to the web
<josephscott> photomatt_: that's a good point, using the APE approach would be good.
<photomatt_> okay that's kind of sitting there so let's move on
<photomatt_> josephscott: could you send a note to wp-hackers to find a partner to work with on it?
<photomatt_> it's like a developer singles site
<photomatt_> quick loop back to Nazgul's question on page order manipulation
<bazza> haha
<photomatt_> Nazgul: could you expand?
<josephscott> photomatt_: yes, I'll put out request on wp-hackers
<Nazgul> There was a recent post on wp-hackers on somebodys SoC project which introduced a way of reordering pages on the backend
<Nazgul> It required some core changes, because not everything was pluggable.
<Strider72> that was outstanding
<photomatt_> was it any good?
<mdawaffe> that's "my" student's project
<photomatt_> page_order is something we have in core that I wonder if it's not better as a widget configuration
<mdawaffe> it's good - may need a tweak here or there
<photomatt_> or a general menu editor
<Strider72> http://bernardopadua.com/wp-sandbox/19-sep-2007/wp-admin/edit-pages.php
<Strider72> sandbox version
<photomatt_> login?
<MarkJaquith> test/test
<MarkJaquith> lucky first guess.
<Strider72> from his email:
<Strider72> I put it together in two ways: a complete wordpress package (
<Strider72> http://www.bernardopadua.com/wordpress/downloads/wordpress_with_page_ordering_19_september_2007.zip)
<Strider72> and a patch (
<Strider72> http://www.bernardopadua.com/wordpress/patches/ajax%20sortable%20pages%20for%20wp.19-09-07.patch).
<photomatt_> oh that's the one like the bbpress forum orderer
<mdawaffe> inspired by, yes
<mdawaffe> but better code
<mdawaffe> and allows reordering when people have 1000 pages
<MarkJaquith> Wow. It crashes Safari 2
<photomatt_> it's flashy, but it's also doing a lot of things at once, not sure if the best approach is to allow reordering and re-parenting at the same time
<Strider72> it's intuitive. I think both at once work.
<Strider72> very similar to some desktop outlining programs I've seen
<rboren> MarkJaquith: everything crashes Safari :-P
<photomatt_> I'm pretty luke-cold. but I will ask liz at HC to see if she can work it into our post-redesign user tests to see how it does there
<photomatt_> but I don't want to put it on the roadmap right now
<Nazgul> Can we at leat look at what's needed to make it usable as a plugin?
<Strider72> LOL. "luke-cold" :)
<MarkJaquith> Nazgul: always. :-)
<photomatt_> final dev topic: wp-hackers (and trac). what are your guys thoughts about that?
<westi> it would be nicer if you didn't have to switch to an alternative view
<skeltoac> Nazgul: yeah, that's way easy :)
<skeltoac> mv wp-hackers wp-whiners
<rboren> trac, good. wp-hackers, typical mailing list.
<Strider72> I think it would hurt the community aspect of WP to sequester the "in-crowd" from the rest.
<westi> with regard to trac it's good. it would be nice for all big changes to start as a ticket+patch and then be committed
<westi> so as to promote review and discussion before commit
<skeltoac> I don't like a closed-membership list
<skeltoac> any more than I like an open-membership list
<rboren> A lot of the more substantial discussion is done in trac.
<rboren> Political stuff on the hackers list.
<photomatt_> I can see part of the argument
<photomatt_> that once something is a ticket + patch most decisions have been made
<MarkJaquith> I think that some "policing" (I hate that word -- "guidance?") could be used to steer (or stop) the less productive conversations on wp-hackers.
<ai2097> See also: "herding cats".
<Strider72> policing would be good. Also, somebody suggested on list the use of "tags" in subject line.
<westi> i think the developer FAQs should help
<josephscott> having things brought up on the mailing list make it easier to discover what is going on. Harder to get a feel for where different topics are going on trac.
<MarkJaquith> josephscott: yeah, I see a disconnect.
<westi> tags in the subject line are nasty - they tend to encourage people to filter out stuff and then topics get missed
<photomatt_> but honestly a lot of these things don't lend themselves to committee or group decision making
<photomatt_> people could debate javascript libraries as long as they did php4/5
<ai2097> westi: People read everything now? There's just too much mail.
<skeltoac> I sure can't
<Nazgul> I liked the idea of reintroducing the weekly IRC meetup's. It makes discussion easier than a "slow medium" as trac or wp-hackers
<Strider72> Respectfully, Matt, how hard is it to delete a thread you're not interested in?
<westi> i try to... i unsubscribe for ml i can't keep up with
<photomatt_> delete threads? it's very easy
<skeltoac> Strider72: when it re-appears more than 100 times, that's a lot of times I have to read that subject line
<photomatt_> but that doesn't help the complaints that things need more dev presence
<ai2097> westi: I'm much the same way -- but it's hard to drop the whole list when the iota of things I care about only shows up on it.
<Strider72> true.
<photomatt_> personally I have no problem debating or discussing an issue with people I know have put in time with WP
<skeltoac> that's what makes a closed list attractive
<photomatt_> I think it could be open-reading, but maybe closed-participation
<skeltoac> and let people blog their opinions
<josephscott> that might be a reasonable middle ground
<MarkJaquith> How do people gain participation?
<josephscott> especially if the archive supported trackback :-)
<skeltoac> at that rate, we could move away from a list and toward a closed-comment, open-trackback blog
<Strider72> Matt -- might be an idea, but it would help the community aspect if the criteria for "participation approval" is made crystal clear -- i.e. cut-and-dried rule
<photomatt_> MarkJaquith: depends on how closed it is
<skeltoac> good point Strider72, clubhouse rules cannot exist in one person's mind
<photomatt_> my goal would be a 9:1 signal ratio
<MarkJaquith> who would be in charge of admitting people? Kicking them out?
<Nazgul> Link it to trac contributions?
<rboren> You must have this many patches in WP to ride this ride?
<josephscott> what have other projects done in this regard?
<MarkJaquith> You must be X Props tall. :-)
<Strider72> You' don't want people just coming into it to have the sense that it's a closed club. _Perception_ is very important here.
<photomatt_> contirbutions is nice
<Nazgul> It at leat proves som familiarity with the codebase.
<photomatt_> because it's accessible to anyone
<rboren> josephscott: Let the lists go up in flames and then the core contributors move somewhere else.
<photomatt_> yet still a good barrier
<westi> i think we must steer clear of quantitative qualifications - they need to be qualitative
<Nazgul> But qualitative is subjective.
<photomatt_> I think once you have the concept of a highly moderated lists
<josephscott> tricky part would be weighing contributions then. Someone might only submit one or two patches, but they could be huge
<skeltoac> I wouldn't mind voting on something like that
<photomatt_> the people who aren't stick out way more, and it's easier to corral them or ask them to leave
<skeltoac> let each member decide with their own criteria
<photomatt_> even better, have it be # of posts allowed per contribution :)
<Strider72> Votes are a good idea. What about a thing on Trac where people can +/- a ticket. If you have so many +es you're in.
<MarkJaquith> Strider72: look at the idea forum. People +1 some really bad ideas.
<skeltoac> I thought more like "anyone object to allowing so-and-so in?"
<josephscott> like the old upload/download ration on BBSs.
<MarkJaquith> Unless you mean +1s from vetted people.
<westi> and -# number of posts for every bug you introduce ;-)
<Nazgul> And the one fixing a ticket isn't always the reporter.
<photomatt_> rather than nailing down the implementation detalis
<photomatt_> I'm more interested in, generally, if core devs who currently don't particpate in wp-hackers would discuss more on a new thing
<skeltoac> yes
<photomatt_> I would
<skeltoac> a blog with closed commenting and open trackbacks would be perfect for me
<ai2097> Is this all-or-nothing open/closed, or -adding- a closed list to the open one?
<Nazgul> Not a core-dev bit I would.
<skeltoac> add Subscribe To to get that list-like feeling
<photomatt_> ai2097: additive
<MarkJaquith> I'm in favor of that. And it would be public readable?
<ai2097> Would a bridge/mediator be assigned between the two?
<photomatt_> I think everything should be public readable
<Strider72> I will just say this... I'm pretty new to the hacker's list (and perhaps overly vocal considering), but I doubt I would have become much involved at all if not for the open approachability of the list.
<MarkJaquith> No closed doors, just closed mics.
<filosofo> who could create posts?
<skeltoac> anyone who could comment
<skeltoac> anyway, let's put implementation details off
<photomatt_> we have to ask ourselves as well, if the kind of people who are core devs are driven away by wp-hackers, how many people who *could be* core devs are driven away?
<photomatt_> next up
<photomatt_> happy cog admin redesign
<photomatt_> first, I think we should more generically refer to it as the "admin redesign"
<rboren> yes
<rboren> Let's not drag HC down in the flames that every UI discussion entails.
<photomatt_> it's pretty much done on their end, which is mockups, they're just doing a few more screens
<Nazgul> Any recent screenshots we can see?
<photomatt_> important ones like post and dashboard are pretty final
<photomatt_> there is some new functionality introduced
<photomatt_> I'm not particularly interested in seeing the aesthetics debated
<MarkJaquith> I'm more worried about ergonomics than aesthetics. :-)
<photomatt_> as for more UI-based things, their decisions are largely based on user testing
<photomatt_> including menu organization, UI placement, etc
<rboren> I'm down with implementing what they have. The question is, can we get it all in 2.4?
<photomatt_> I think so
<MarkJaquith> How much functional change is there?
<photomatt_> MarkJaquith: dashboard is the most changed
<photomatt_> on the write page, the main change would be around categories and tags
<photomatt_> I think I could get core to reasonably approximate their mockups in about 2 weeks
<rboren> We'd have to do some admin menu back compat work.
<rboren> I think the menu changes should go in ASAP
<westi> the menu code needs some work anyway ;-)
<rboren> It needs to be scrapped :-)
<photomatt_> menu should be so simple, it astounds me
<rboren> Permissions, dynamic reparenting, all add complexity.
<rboren> And the cruft of back compat....
<MarkJaquith> Seriously. It's complete crap. We have an API, and we have the desired result. And we're doing Cirque du Soleil in between.
<rboren> Anyhow, due to the shaky nature of menus, would like to get those changes in early.
<rboren> Cirque du Soleil on mushrooms
<MarkJaquith> photomatt_: you say "pretty much done on their end" -- does that mean most of the screens are 100% done? Or that all of them are almost 100% done?
<photomatt_> what I'd like to do with it is after I get back from london have a series of iterative changes over the course of about 2 weeks that are the "redesign", perhaps with some placeholders
<photomatt_> so the dust should settle around the 19th
<photomatt_> after that I think we should talk about what we think about it in practice, rather than theory, and then also HC can do some user testing on the working code rather than notecards or mockups
|<-- jared has left irc.freenode.net ("BitchX: a modern client for a old world")
<photomatt_> and decide where to go from there
<MarkJaquith> Cool.
<photomatt_> once the core is in, the tasks become much more parallel
<photomatt_> and we could split up what needs to be worked on
<photomatt_> main functionality changes I can think of
<photomatt_> widget-based dashboard
<photomatt_> very different tag selector
<photomatt_> ability to have multiple instances of any widget
<photomatt_> image library
<photomatt_> eom
<westi> eom?
<MarkJaquith> :-)
<photomatt_> end of message :)
<Nazgul> end of Matt?
<photomatt_> maybe!
<Nazgul> But I like those ideas.
<skeltoac> walks in front of trains
<Strider72> I love the "widget based dashboard idea.
<skeltoac> roll-your-own always sounds sweet
<photomatt_> other userfacing topics
<photomatt_> undo?
* westi remembers how nice WP-Dash was
<skeltoac> lots of ways to implement undo, just a question of choosing one and making it go
<MarkJaquith> To misquote Designing the Obvious: Modal JS AYS is the devil.
<westi> undo would be nice so as to remove all the AYS
<skeltoac> well, all the ays except on the emptying of the trash :)
<MarkJaquith> Automated trash collection!
<photomatt_> we could go about it in a way that is the death march of 2.4
<photomatt_> I'd be pretty happy with something that just put a time-delay on actions
<photomatt_> sort of like how facebookdoes it with friends
<westi> time delay is bad
<MarkJaquith> so, (1) Show action as completed (2) show undo link (3) do it later if they haven't clicked "undo"
<photomatt_> you delete a comment, it goes to a little one-line message, and you can undo until you leave the page
<skeltoac> there will be those concerned that when they delete it they want it gone, so an immediate-action model will be a want
<Strider72> optional setting? "Enable undo"?
<photomatt_> it also saves having to have a generic content bucket where we could stick any data from WP in
<westi> it should be immediate or trash can like... i.e. you have to physically empty it
<photomatt_> Strider72: you're fired
<photomatt_> j/k
<westi> we don't need a generic bucket
<skeltoac> next time wink when you suggest a new option, Strider72
<Strider72> eek
<Strider72> ;)
<MarkJaquith> "Undo enabled. Undo?"
<westi> posts go to deleted-post status , pages to deleted-page and comments deleted instead of comment/ping/trackback
<skeltoac> haha MarkJaquith
<Strider72> LOL
<MarkJaquith> westi: so each thing has its own trash.
<westi> yes
<Strider72> "Are you sure you want to disable 'Are You Sure' messages?"
<MarkJaquith> saves a lot of "move to trash" "remove from trash" code.
<photomatt_> I don't know if it's necessary to provide it for *everything*
<westi> indeed.. and as the tables already have the concept of status it should work easily
<photomatt_> some places that might be 80% of the effort might be easier to leave out
<MarkJaquith> Post deletion, comment deletion.
<MarkJaquith> Category deletion
<photomatt_> like categories, which also modify posts
<photomatt_> yes
<westi> i think post/page/comment deletion is the key
<ai2097> What happens to comments if you delete the parent post is deleted?
<MarkJaquith> ai2097: they're deleted.
<rboren> post deletion would require updating taxonomy counts
<ai2097> MarkJaquith: And what if you already deleted a -single- comment from that post? ;)
<photomatt_> we're also talking about an anti-delete, not really undo
<ai2097> Or are we not handling multi-level un... ah.
<MarkJaquith> ai2097: nah, last-action undo.
<MarkJaquith> photomatt_: yeah -- which makes delayed execution sound like the ticket.
<photomatt_> some sites like digg have an actual timer
<photomatt_> you can edit this comment for X seconds
<photomatt_> most times when I've had an "oh shirt" moment
<Strider72> give them a status of "deleted" until time to commit, then actually deletes?
<MarkJaquith> I implemented that for MovableType back in 2003. :-)
<photomatt_> it's been an accidental click and I just always hit enter on the confirmation
<photomatt_> before my brain registers
<rboren> MarkJaquith has volunteered. Huzzah!
<photomatt_> if the comment minimized and queued the action for X seconds or until page unload that'd be enough I think
<MarkJaquith> What about when JS is off? No protection?
<photomatt_> yep
<skeltoac> ew
<westi> ew indeed. if we do away with the AYS then we need a trash can really
<skeltoac> onunload is bad juju
<westi> it's too easy to click on the wrong button
<photomatt_> westi: not suggesting that
<photomatt_> this isn't a global everywhere thing, just for places where mistakes are common
<skeltoac> a trash can is awfully complex compared to a temporary "deleted" status
<photomatt_> and it's easy
<westi> skeltoac: a trash can for posts/pages/comments can be a deleted status
<ai2097> skeltoac: I fail to see how they're different. ;)
<skeltoac> counting on the browser to store program state?
<photomatt_> trash can and multi-level undo would be pretty tough
<photomatt_> more work than benefit
<MarkJaquith> So: how to best implement last-action undo?
<photomatt_> MarkJaquith: you brought this up. what user problem or scenario are you trying to solve?
<skeltoac> simplest: pull back to draft/moderated and add a wp_cron job to delete it in a user-set amount of time, or just delete it if user set zero
<MarkJaquith> photomatt_: mostly comment stuff that is really slow.
<westi> just reworking the comment workflow to include undo of deletes would speed things up a lot (as well as other comment work flow changes like inline replying to comments in the admin back end)
<photomatt_> maybe we could do comments first and see how it goes
<photomatt_> we got a few months before shipping
<MarkJaquith> photomatt_: did HC do anything with regard to comment handling?
<photomatt_> MarkJaquith: did you want to tackle that?
<photomatt_> not that impacts this discussion
<MarkJaquith> photomatt_: yeah. I've been whiteboarding comments stuff for months.
<photomatt_> okay, done
<photomatt_> next up: searching posts and pages
<photomatt_> top-voted idea
<photomatt_> any thoughts?
<MarkJaquith> Ryan and I discussed this several months ago.
<westi> I believe it has had quite a discussion on trac too
<MarkJaquith> We really didn't like mashing them together in the same loop. There's no way to put a page in a post listing and have it make sense. So our idea was to have a search generate another WP_Query object.
<skeltoac> MarkJaquith: to make a unified result list make sense, it would have to be in relevance-order
<MarkJaquith> skeltoac: right -- which we don't have.
<photomatt_> IMO from a search interface POV they should be separated
<photomatt_> when they're displayed
<MarkJaquith> It requires theme support, and this way there is NO back compat issue.
<Strider72> Make it a parameter of the search function. Then the theme designer can decide.
<skeltoac> I pitched that in a kitchen discussion at Stinson
<MarkJaquith> Themes that don't support won't shot page results.
<skeltoac> show posts list, show pages list
<photomatt_> so the idea is a new loop people could put on their search templates?
<MarkJaquith> Yes.
<photomatt_> perfect
<westi> #1435 is the trac ticket
<wp-trac-bot> westi: http://trac.wordpress.org/ticket/1435 major, high, 2.4, markjaquith->anonymous, new, Pages should be searched
<MarkJaquith> rboren: where you at?
|<-- damejiar has left irc.freenode.net (Read error: 104 (Connection reset by peer))
<skeltoac> I got a whole lot of "that sucks" from donncha_ and josephscott if I recall. Do those opinions stand?
<rboren> Lurking about.
-->| damejiar (n=chatzill@201.247.150.72) has joined #wordpress-dev
<MarkJaquith> Still think we should split Page/Post results into two WP_Query objects?
<westi> It would be nice to have a relavence search but I suspect that it a lot more work
<ai2097> Unified search results in relevance order make a lot more sense user-wise. From a user perspective, relevance matters more than whether the content came from a page or a post.
<rboren> That's best for back compat. Or have an option themes could use to get combined results that can be distinguished with post_type.
<skeltoac> I agree westi, but we don't have a relevance search engine.
<josephscott> do we have a way to measure relavance?
<photomatt_> I think even if we could, pages and posts are very different
<rboren> And a method of summarizing pages for display in the search list.
<photomatt_> most people have a few of one and a bunch of the other
<Strider72> +1 rboren
<rboren> I just use google. ;-)
<ai2097> But readers don't really want to know or care about that.
<skeltoac> title + relevant excerpt is doable
<westi> I guess the biggest question is: What do people expect to get out of having Pages in the search results?
<photomatt_> 2. how do the most popular plugins that address this do it (from a user point of view, not implementation)
<MarkJaquith> I expect a little section at the top with a list of page titles. Or maybe in a little floated box.
<rboren> Most require theme changes cause the combine results.
<photomatt_> let's put those two on the todo, we don't have to decide or figure out right now
<MarkJaquith> two?
<MarkJaquith> (I'm taking notes)
<photomatt_> those two questions
<skeltoac> there is already page search in admin... I think I did it, so it can't be that hard
<Strider72> take this: the_search_query(); instead allow the_search_query(posts); or the_search_query(pages); or the_search_query(both);
<skeltoac> query_posts / query_pages
<photomatt_> let's close out with a final topic
<photomatt_> could every quickly check out alex gunsche's post to wp-hackers from a few minutes ago?
<photomatt_> I'm curious what you think, and how we should respond
<photomatt_> knowing that akismet is effectively a commercial plugin, too
<photomatt_> though the circumstances are pretty different
<skeltoac> bundling does not become wrong just because the plugin tastes bad
<MarkJaquith> No, but they are tarnishing the trademark.
<ai2097> skeltoac: However, it is not the official distribution. The question is, is this clearly indicated?
<skeltoac> I don't know
<MarkJaquith> They can do what they want -- but not in WordPress' name.
<skeltoac> MarkJaquith: I don't know how to substantiate "tarnish" in that case
<photomatt_> they are effectively our official german presence
<skeltoac> it's up to the trademark holder I guess
<westi> Looking at what they are doing.. I guess the problem is not the plugin it's self but the link to the signup page takes a referrer id
<Strider72> At the least they need to make clear that _they_ bundled it. At best... ???
<photomatt_> most of the international sites have some form of advertising on their sites
<rboren> indeed
<MarkJaquith> I don't have a problem with that. I have a problem with them modifying WordPress to do these things without rebranding.
<Nazgul> Yes, but I "expect" to see adds on somebody else's site, not on my own.
<photomatt_> some bundle plugins, but to my knowledge it's always something to do with the localization or calendar
<rboren> yes, such as RTL support
<rboren> And we've encouraged that in the past
<nikolayb> I have changed the Bulgarian version also
<photomatt_> Nazgul: it's not on by default like a sponsored theme, but it would be the equiv of us endorsing text-link-ads or a google plugin with the download
<MarkJaquith> Well, I'd make a strong distinction between Google (Adsense?) and TLA.
<skeltoac> if I held the trademark, I'd explain the offense and ask them to remove it
<Strider72> on the other hand... they _are_ doing German users a real service. Is it legit for them to get soemthing in return?
<photomatt_> are they entitled in that regard?
<skeltoac> getting something doesn't have to mean distributing a referral product
<MarkJaquith> Is the service a SERPs spamming service like TLA?
<skeltoac> Alex said it was
<skeltoac> dunno though
<photomatt_> http://translate.google.com/translate?u=http%3A//www.linklift.de/&hl=en&langpair=de%7Cen&tbb=1&ie=UTF-8
<Strider72> It's not quite like me taking Wordpress, filling it with spam, and calling it "StevePress". Devil's advocate to an extent. This does rub me the wrong way.
<ai2097> It's OK to bundle. It's OK to modify. It's not OK to pass it off as plain old WordPress. Is this agreeable?
<photomatt_> http://translate.google.com/translate?u=http%3A//wordpress-deutschland.org/download/deutsch/&hl=en&langpair=de%7Cen&tbb=1&ie=UTF-8
<Strider72> +1 ai2079
<photomatt_> what this probably impacts the most
<photomatt_> is we weren't planning to create official mini-sites for languages with existing communities
<photomatt_> like de, fr
<josephscott> "additional plugins" seems intentionally vague
<photomatt_> okay, I'll continue to look into it
<photomatt_> toni speaks german and talk to olaf, so he should be able to get some more info for us
<photomatt_> let's wrap things up for today, thanks everyone for coming out
<MarkJaquith> Shall I post notes to wp-hackers?
<rboren> Post to cabal.wordpress.org :-)
<photomatt_> http://codex.wordpress.org/Version_2.4
<photomatt_> I updated with a few of the things we talked about, feel free to edit
<MarkJaquith> cool
<ai2097> Is the transcript going there, too? I missed the first few minutes.
<--| skeltoac has left #wordpress-dev
<MichaelH> Will put log here http://codex.wordpress.org/IRC_Meetups/2007/September/September26RawLog
<westi> A summary to hackers as well would probably be a good idea
<westi> Just pointing at the codex page (and the raw log on the codex)
<photomatt_> does anyone feel like they don't have anything to tackle before the next meeting?
<MarkJaquith> I've got plenty to keep me busy.
<rboren> Well, we didn't translate anything into direct actions.
<rboren> But I'm sure we
<MarkJaquith> I did.
<rboren> we'll figure it out
<photomatt_> I think josephscott had a few too
<rboren> I'll commit mdawaffe's jquery stuff and nikolayb's js i18n stuff.
<josephscott> I've got some
<rboren> MarkJaquith gets prepare.
<nikolayb> rboren, mine nees some tinkering
<photomatt_> I'm going to follow up on de thing and finalizing HC
<mdawaffe> rboren: I have up to date copies here
<photomatt_> rboren: did you have anything you wanted to lead?
<rboren> Okay, I'll wait for you two to refresh patches.
<nikolayb> rboren, some things changed in the end of the 2.3 phase
<rboren> photomatt_: When do you want to start doing admin stuff?
<rboren> I could start with menus...
<photomatt_> I'll start the 6th, hope to finish around 19th
<rboren> I'll look over the high priority and "early" bugs and get that out of the way.
<rboren> And then pick up whatever no one else wants.
<photomatt_> cool, how about post/page search? could you answer the two questions for next week?
<rboren> sure
<MarkJaquith> Here's what I have: http://phpfi.com/265293
<MarkJaquith> 4. is Matt. 2. is Mike/Andy
<photomatt_> cool, same time next week work for everybody?
<photomatt_> that's a very nice list, MarkJaquith
* westi heads off to bed..
<westi> night all
<MarkJaquith> Yeah, this is a good time.
<MarkJaquith> g'night westi
=-= westi is now known as westi|gone
<MichaelH> do I hear </meetup>?
<photomatt_> yes

Back to IRC Meetups