Frumph 6:22 pm on January 28, 2011

Agenda for 01/29/2010 WPTRT

IRC Channel #wordpress-themes
#freenode
10am EST. Saturday

Theme Out Of Date –
1. Code the search to not include themes out of date, create new search for out of date themes – big “out of date” marker on the theme page for themes that are past a certain point.
2. Suspension for themes that haven’t updated past a certain point.

Swap out a couple of the featured themes.
Finalize Child Themes on repository guidelines for reviewing. (and recommendations to consider to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devs if any implementation is necessary)
WPTRT Base Theme
SEO Discussion Site vrs SEO Sales site, author uri, theme uri – this one is a given that a theme uri must point to a page specifically for the theme and author uri must point to a developement page for the author if the main author’s page is not a general blog site for the developer.

Anything else anyone want to toss in?

Chip Bennett 7:10 pm on January 28, 2011

Draft Security Guidelines/Checklist
Review Queue Status / Review Quota Commitments
Frumph 7:37 pm on January 28, 2011

^ Need Otto’s opinion on if theme out of date by date queries can be adjusted, example adding AND DATE > $outofdate and making a seperate search query for those that are out of date, and the out of date button based on the update date on the theme and the global $outofdate that’s set?
- Frumph 7:44 pm on January 28, 2011
  
  Also child-theme tag and post-formats tags wanted to implement, added to questions for otto
Ian Stewart 7:59 pm on January 28, 2011

What’s the WPTRT Base Theme?
- Chip Bennett 9:34 pm on January 28, 2011
  
  Tune in tomorrow to find out. 😉
- Ian Stewart 2:19 am on January 29, 2011
  
  Aw, man. I guess I’ll be reading the logs. 🙂 Or will there be a recap posted here?
Frumph 8:01 pm on January 28, 2011

Couple of things, it’s the getting rid of P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. on here and using twentyten – and we’re discussing putting together a theme with best practices that could be used as a reference along with twentyten for various coding functionality
- Rahul Bansal 5:26 am on January 29, 2011
  
  This seems a great thing to do. Many new theme-developers will save their own time and time of reviewers!
Frumph 1:32 pm on January 29, 2011

Addition, look into getting email address for the leads cais and pross, to send email notifications for ‘please update your theme’ and possible future suspensions, etc. – based on Ian’s recommendations below
Andrew Nacin 12:53 pm on February 7, 2011

A few notes, as a drive by:
– Infrastructure and preparation are good, but we’re not sure if we want to see child themes in the directory until we can deal with them from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. side. We’re planning on that for 3.2, and it’s something I’ll work on with Otto from each end of the candle.
– A base theme sounds kind of like Twenty Ten 🙂
– I think P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. is best here if this blog is about conversation and planning.
- Edward Caissie 1:27 pm on February 7, 2011
  
  A “blog” using P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. as its theme would generally be “about conversation and planning” but that is not the pidgeon hole the WPTRT had in mind for this site.
- Chip Bennett 1:58 pm on February 7, 2011
  
  No offense, but shouldn’t the people primarily charged with using this site (i.e. the WPTRT members) be the ones best-suited to determine whether or not P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. is most appropriate?
  
  We don’t intend to take the same tack as, say, wpdevel, with our use of this site. I think that one of our primary objectives is to use this site as an educational tool/resource, which would include a lot of tutorial-type blog posts. P2 is not so well-suited toward this end.
  
  I should note, also, that any Theme that supports threaded comments will serve equally well as P2 with regard to furthering discussion.
  
  Finally: we have had many, many issues with comments not posting immediately/at all with P2 – something that is rather counter-productive to the end of encouraging commenting/discussion. As a function-over-form type of person, this drives me crazy. For all I care, we could run TwentyTen on this site, and it would serve us equally well. (Though I wouldn’t mind giving Pilcrow or Coraline a spin.)
  - Andrew Nacin 2:44 pm on February 7, 2011
    
    If comments aren’t posting, that’s going to be an issue regardless of the theme. It’s something I plan to look into this week and next.
    - Chip Bennett 11:04 pm on February 7, 2011
      
      I respectfully disagree. We are hearing multiple instances of issues with the AJAX-ified comment form simply hanging on submit; also, sometimes comments appear in the backend, but not on the front end – all kinds of wonky problems. Maybe it’s a problem with the make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ WP install, but I’m much more inclined to suspect P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.. (The easy way to find out, of course, would be to switch Themes and observe whether or not the problem persists.)
      
      Nevertheless: regardless of our reasons, why should we have to 1) ask, and 2) justify our decision, to switch Themes? (I’m sure this limitation applies to all teams using make.wordpress.org sites; I realize we’re not alone in this regard.)
    - Lance Willett 12:41 am on February 8, 2011
      
      I think it’s not P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. but something weird with this domain and cookies. When I access this site with Safari I appear to be “logged in” here, even though I’m not a user on this site. Is make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ using WP.com cookies for anything? When I post from Safari the comment from spins endlessly and doesn’t ever post.
      
      If I access with Firefox I do not appear to be logged in, and I just enter my details and comment without a problem.
    - Andrew Nacin 1:55 am on February 8, 2011
      
      It’s definitely some funky WP.org stuff we have going on. It’s not P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/., and while it may be exacerbated by P2, it’s something we have to fix, not just for this blog.
      
      The only reason I suggested that P2 makes sense, is that ideally the make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ blogs (and there will be more soon) are designed around the need for conversation, collaboration, coordination, and communication among people contributing to, in this case, the theme review process. Informative blog posts sound more like Codex or handbook articles. But we can discuss further.
      
      It’s not about you needing to justify anything. More to the point, no team is or should be autonomous — we’re all gears in a larger machine, with a lot of overlap. Any recommendations ultimately trickle down and bubble up to affect many other working groups, developers, and users.
      
      That these various groups (UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing., theme reviewers, etc) can operate independently is fantastic. But the’re naturally full of interdependencies, and they all are delegated extensions of the project leadership. This is especially important when fulfilling the various visions and long-term goals of what we want WordPress and wordpress.org to be.
      
      You guys do great work and I want to help more than I interfere — just looking out for you guys.
      - Edward Caissie 3:27 am on February 8, 2011
        
        The only reason I suggested that P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. makes sense, is that ideally the make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ blogs (and there will be more soon) are designed around the need for conversation, collaboration, coordination, and communication among people contributing to, in this case, the theme review process. Informative blog posts sound more like Codex or handbook articles. But we can discuss further.
        
        This is the sort of communication we need to go forward with … and would have helped to better understand your earlier comment. Do we have any ETA for the “fixes”? This may essentially only be affecting this particular installation but it is a source of frustration and it would be great if it could be addressed sooner rather than later.
    - Edward Caissie 7:24 pm on February 8, 2011
      
      Not sure if this is related to the issues on the site but I keep getting this script issue being reported:
      
      Script: chrome://afterthedeadline/content/atd.js:675
      
      … while browsing with Firefox.
- Chip Bennett 2:15 pm on February 7, 2011
  
  Oh, regarding Child Themes: I don’t think we are intending to drive any particular implementation path or date; we just want to make sure that we’ve got our infrastructure (i.e. Guidelines, workflow, etc.) in place, so that when the “switch” is thrown, we’ll be ready to receive and process submitted Child Themes.
  
  I like the thought that we’re looking at something at least as far out as 3.2. It gives us both the time to plan properly, and also a tentative target to which to point developers who inquire about implementation.
  - Andrew Nacin 2:43 pm on February 7, 2011
    
    Indeed.