Ready to get started?Download WordPress

Make WordPress.org

Updates from December, 2012 Toggle Comment Threads | Keyboard Shortcuts

  • Samuel Sidler 8:24 am on May 24, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    As we’ve been doing weekly, we had another meta trac triage yesterday. @atimmer, @coffee2code, @iandunn, @nacin, @Otto42, and @samuelsidler attended.

    We’d love some feedback on #30. That is, anyone interested in creating better theme preview data, it’d be great to have it submitted to the ticket. There’s a current proposal that could use some feedback as well.

    @jenmylo: For #482, will the training team be using their P2 or using the community P2? They’ve been using the community one recently. If they’ll continue to use the┬ácommunity P2, we can wontfix that ticket.

    Next week (Friday at 17:00 UTC), we’ll be looking at the Plugins Directory component (I won’t be present).

  • Samuel Sidler 11:54 am on May 10, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    We did a meta trac triage on Friday.

    • @Clorith, @coffee2code, @georgestephanis, @iandunn, @otto42, @samuelsidler attended
    • We’ll be doing another meta trac triage exactly a week later on May 16, 2014 17:00 UTC.
    • Our focus this time (and next) was on the General component in trac and closing out some of the issues. We made it through about half of the tickets in that component (20) and a handful were fixed.
    • @otto42 wants to ask anyone and everyone for help with responsive fixes for WordPress.org (#461)
    • A number of tickets need follow up. Some have been assigned so we know who’s on point. I’m taking a number of others.

    Those interested, we’ll see you next week!

  • George Stephanis 3:36 pm on November 28, 2013 Permalink | Log in to leave a Comment
    Tags: ,   

    The plugins repo is currently serving up the 2.6.1b1 tag for Jetpack, but saying that it’s 2.6.

    When you download the file and open it up, the changelog contained in the readme.txt file matches the 2.6.1b1 tag, not the 2.6 tag, or trunk (which it had glitched to previously a few months back).

    Trunk’s current readme does point to 2.6 as the stable tag.

    Today, on Thanksgiving, I’m thankful that this is just a minor bugfix point release that slipped out early, and everything that changed in it should be safe and good to have deployed. However, users that upgrade to or install it via their dashboard, or download the zip are still getting told that it’s a beta release, which can certainly scare users.

    cc: @otto42 @samuelsidler

    I’m going to be trying to do whitespace commits to some of the readme.txt files, hoping to glitch it back to being correct again.

    • George Stephanis 3:39 pm on November 28, 2013 Permalink | Log in to Reply

      Also emailed to plugins@wordpress.org

    • Samuel Wood (Otto) 3:43 pm on November 28, 2013 Permalink | Log in to Reply

      You know how I once said that branches don’t matter?

      Yeah, I was wrong. Get rid of the /branches/2.6 directory. It’s seeing that and building the 2.6 zip from that.

      • George Stephanis 3:46 pm on November 28, 2013 Permalink | Log in to Reply

        I’m moving them all into /branches/point-release-branches/ — that should keep it from catching, yes?

      • George Stephanis 3:46 pm on November 28, 2013 Permalink | Log in to Reply

      • J.D. Grimes 4:17 pm on November 28, 2013 Permalink | Log in to Reply

        So does this mean that plugins shouldn’t have a branches directory, unless they want the zip to come from there? Or do we just need to have a 2.6.0 tag if we want a 2.6 branch?

        • George Stephanis 4:51 pm on November 28, 2013 Permalink | Log in to Reply

          I think what’s happening is that the zip generated by branches goes to the same url as those generated by tags. So while it’s parsing the plugin headers from the tags and using that to populate the plugin page, the branches get parsed afterwards, and then that zip overwrites the tag zip.

          So the plugins page is built off of the tag, but the branch zip winds up being what’s built at the url the tag one should live at, if they’re named identically.

          As such, I think I could have renamed it to branches/2.6-legacy and been fine?

    • George Stephanis 4:00 pm on November 28, 2013 Permalink | Log in to Reply

      Confirmed, it’s serving 2.6 again now.

      Major thanks for the response, especially on a holiday. Gin & Tonics are on me next time.

  • Isaac Keyet 11:30 pm on November 4, 2013 Permalink | Log in to leave a Comment
    Tags: forums, , todos   

    Migrating & Merging Mobile App Forums 

    Hey guys, this is something we’ve discussed many times in the past and.. what can I say. It’s close to our hearts.

    To recap, the plan of action was to…

    • Collect all threads and rooms within each of the apps forums (ex.: ios.forums.wordpress.org). I know @nacin had made some progress on this.
    • Create a new subforum here on WordPress.org titled “Mobile Apps” or similar.
    • Import each forum as a sub-forum of “Mobile Apps”
    • Mobile group to manually go through and add cross-platform threads (like FAQs, the plugin blacklist, general how-tos).

    If I remember correctly we figured we could start with a forum that has extremely low traffic to see how that goes, say the Nokia app’s forum (an app that’s in hibernation).

    What do you think? Does this fit in on the road map?

    • Sam Sidler 3:31 pm on November 7, 2013 Permalink | Log in to Reply

      This sounds generally fine. I assume you want the forums to be part of the support forums not their own thing? I’m not sure how hard this would be given the codebase that’s on the support forum. @otto42 would know more. When we can get it done will depend a lot on how long it’ll take (and if we have encoding issues…).

      I do wonder… What’s the goal of moving them over? Better visibility to mobile forums? Do we get a lot of misfiled forum posts to the support forums that belong in the mobile forums? I notice that each of the mobile apps has its own site. Would there be interest in bringing those in under wordpress.org/mobile/[platformname] for consistency?

      • Isaac Keyet 6:53 pm on November 7, 2013 Permalink | Log in to Reply

        Yes, the plan has been to consolidate the sites’ content: landing pages/download, “how to contribute” (now make/mobile and the mobile handbook), FAQ/Help (could be in the forums), dev blogs (now all are closed, we only use make/mobile), the official app blogs (could live under wordpress.org/mobile/platform), and the forums.

        There are two main reasons for moving the forums (and everything, really) over:
        1. Maintaining all these separate sites has proven to be a difficult task (usually lag behind further than they should).
        2. There’s a lot of overlap and redundant content, this goes for landing pages, feature listings, download links, ‘get involved’ type pages, as well as support.

        @aerych and I did talk about how if this proves to be hard to do in a timely and swift manner we could simply dump all the content in the current forums to an archive to live on somewhere and redirect hits to a new Mobile Apps forum under Support here on WordPress.org. We could then go through and manually add everything we think would make sense to have ‘global’ for the apps and what makes sense on the app level (by creating sub-forums). We’d hate to lose all the threads, but as long as we can preserve them somehow I doubt it’d be a problem for neither users nor us.

      • Isaac Keyet 8:34 pm on November 8, 2013 Permalink | Log in to Reply

        Just checking in, would be nice to figure out a way forward. Feel free to ping me or @aerych anytime.

      • Isaac Keyet 11:45 pm on December 4, 2013 Permalink | Log in to Reply

        @samuelsidler, any update here? I know it’s crunch time for 3.8 but we need a resolution, been a month today :)

        • Sam Sidler 11:22 pm on December 5, 2013 Permalink | Log in to Reply

          Sorry for not getting back to you @isaackeyet.

          Talking this over with @nacin, we’re going to punt until 1Q or 2Q next year. Migrating things over doesn’t make sense right now (on the old bbPress), but work is starting on the a bbPress 2.x solution for the future. We’ll probably do some locale forums first, then can bring these over before bringing over all of the support forums. I think it’s best to wait until we have new forums rather than trying to migrate the mobile forums into the old forums.

          • Isaac Keyet 11:52 pm on December 5, 2013 Permalink | Log in to Reply

            No problem.

            Maybe then the best option is to simply archive the old forums and start fresh, manually carrying over important topics and threads. We could then just disable logins and posting on the individual forums and create a message to display for anyone visiting to go to the new forum with any discussions.

            Given that it’s been over 1.5 years since we first initiated the move it just seems like there may just be no way it can happen if it didn’t happen up until now.

          • Isaac Keyet 5:59 pm on December 9, 2013 Permalink | Log in to Reply

            We decided to go with the simple approach outlined above.

            @samuelsidler could we get new subforums created so we can start migrating (manually)? Or let me know when/how we can talk about what needs to be done.

  • Jen Mylo 4:46 pm on October 23, 2013 Permalink | Log in to leave a Comment
    Tags: , events, import   

    A while back on September 11, @andreamiddleton tried to import the /events blog into the /community blog since we were merging teams. She hit a bug/error/some kind of blocker in the import and reported it. @nacin and @otto42 said they’d look into the weird encoding issues. It wasn’t a priority, sure, but in the meantime we’re double-posting stuff and we still haven’t truly merged the groups. Could someone see if this can be figured out?

    • Samuel Wood (Otto) 4:51 pm on October 23, 2013 Permalink | Log in to Reply

      I’m uncertain how to do that importing myself. Nacin said he knew what that involved, but I’m unclear.

      I was never able to sort the encoding issues or duplicate them on a local setup. So no fixes from this end at present. I’m sure that if they happen again, we can sort them out with some database jiggery-pokery on a one-time basis though.

      • Jen Mylo 5:01 pm on October 23, 2013 Permalink | Log in to Reply

        I just tried to do the import again, because I don’t want to add something else to nacin’s plate. Asked him about this a few days back in skype and he didn’t reply, so am figuring 3.7 is all-consuming.

        Multiple errors, and now things are imported with the wrong author again, but I’d rather have to manually adjust them than let it drag out.

      • Jen Mylo 5:35 pm on October 23, 2013 Permalink | Log in to Reply

        Dunno if this will help or not, but in doing the manual reassigning of authors, one of the bugs I’m seeing is that when a post starts with a sentence containing an em dash, p2 made that line the post title on /events, and then didn’t know how to deal with it on import, so it created a blank post (permalink and comments, but no title or post content).

      • Jen Mylo 7:29 pm on October 25, 2013 Permalink | Log in to Reply

        I manually updated the authors on the imported posts. The only thing that doesn’t update is the gravatar, because it’s saved based on the original email, it doesn’t seem to refresh the gravatar link when author/email is updated (should we make a ticket for core so that it does?).

        I think we’re ready for you to redirect /events to /community.


  • Jen Mylo 4:11 pm on October 23, 2013 Permalink | Log in to leave a Comment
    Tags: categories, ,   

    @otto42: @iandunn posted a plugin on trac for the /community team site 5 weeks ago. Could that get added, or if it’s not ready could you tell him what he needs to change? It’s a bottleneck for some stuff we want to do on our team site to make it easier for groups working on separate projects. Thanks!

    • Samuel Wood (Otto) 4:15 pm on October 23, 2013 Permalink | Log in to Reply

      I’ll take a look at it. First I’ve seen it.

      If you need something like this, don’t hesitate to tell me about it before it becomes a bottleneck.

      • Jen Mylo 4:18 pm on October 23, 2013 Permalink | Log in to Reply

        Awesome, thanks! @iandunn said he was just waiting for you to commit it, so I thought it was in a review queue. Fast forward past a couple of WCs, Automattic meetup, miscellaneous catchup, and I noticed it still wasn’t there. Not a big deal, just wanted to make sure you’d even seen it.

        When something gets posted to trac that needs review, would it be helpful to post a note about it here, or is the trac notification normally enough?

        • Samuel Wood (Otto) 4:45 pm on October 23, 2013 Permalink | Log in to Reply

          The trac notification is not really enough. If something is holding things up and needs eyeballs and a commit, let somebody (me, Sam, etc) know directly… For now. Until we work out the process better.

          I troll through meta from time to time looking for things to finish up, but if I’m not actually CC’d on something, I’m probably not getting emails or notifications about it right now.

          • Jen Mylo 4:47 pm on October 23, 2013 Permalink | Log in to Reply

            I think Ian mentioned it to you in a skype chat, but we should all be better about posting notes here to keep a record. @iandunn: For future stuff, can you also post here and do an @otto42 mention in the post so he’ll be sure to see it? Thanks!

            • Ian Dunn 4:50 pm on October 23, 2013 Permalink

              Otto: Ah, my bad, I assumed you were subscribed to the mailing list and saw everything.

              Jen: No problem.

  • Drew Jaynes (DrewAPicture) 5:14 pm on August 2, 2013 Permalink | Log in to leave a Comment
    Tags: Codex   

    In anticipation of the 3.6 release, the docs team added function references in the Codex in April for 37 functions and a filter that now need to be deleted.

    We’ve already had one report of a “missing” function on Trac. For now, I’ve just deleted all of the content in those pages, but they’re obviously still showing up in searches.

    Can one of you elevate my privileges in the Codex and/or take care of deleting these? The list of pages is here: https://gist.github.com/DrewAPicture/6141436

    @otto42 @nacin @coffee2code @samuelsidler

  • Jen Mylo 4:49 pm on January 29, 2013 Permalink | Log in to leave a Comment
    Tags: menu,   

    @otto42: Could you add in a menu under the header to the spinoff of p2 you are running for the make sites? Working on a new theme for make sites in general, but in the meantime this would make it easier for teams to use a custom menu to organize stuff without adding more noise to the sidebar.

    They added a menu like this to Mike Admas’s team’s p2 at Automattic:
    Screen shot 2013-01-29 at 12.19.00 PM

    Tacked on top of content area like that and just using the standard colors/fonts already in this theme would be great.

    p.s. autocomplete for author mentions doesn’t seem to be working?

    • Jen Mylo 4:49 pm on January 29, 2013 Permalink | Log in to Reply

      Not sure why that image won’t show.

    • Samuel Wood (Otto) 5:16 pm on January 29, 2013 Permalink | Log in to Reply


      • Image has no src there, so not sure what the image is supposed to be.
      • Autocomplete works fine if you let the javascript load. Right now this is a minor https related problem on the make sites. Fixable though.
      • Jen Mylo 5:22 pm on January 29, 2013 Permalink | Log in to Reply

        I must be having js issues on this site, since the image got uploaded, autocomplete not working, when I hit post or reply I get an AYS about leaving the page, and even though I keep unchecking the Notify me of new posts by email, with every post I get an email to confirm a new subscription. Not happening on the other make sites, just this one.

    • Samuel Wood (Otto) 5:21 pm on January 29, 2013 Permalink | Log in to Reply

      NM, found the image.

      Yes, adding a custom menu space should be easy enough.

      • Jen Mylo 5:23 pm on January 29, 2013 Permalink | Log in to Reply

        Great, thanks!

        • Samuel Wood (Otto) 5:27 pm on January 29, 2013 Permalink | Log in to Reply

          @jenmylo Actually, turns out that there already is a custom menu space there, it’s just unstyled. Make a new custom menu and set it to “primary” and add whatever you like. Then I can add additional styling rules to make it look prettier.

          • Jen Mylo 6:02 pm on January 29, 2013 Permalink | Log in to Reply

            Cool, they must have added it and I never noticed, sorry for bothering you. No need to bother with styling, since working on a new theme anyway. Added it on the /community site and yeah, it’s not the best looking thing I’ve ever seen, but it really doesn’t need to be. :)

  • Jen Mylo 1:48 pm on January 28, 2013 Permalink | Log in to leave a Comment
    Tags: learn.wordpress.org   

    Going to want to start doing some work on learn.wordpress.org this week and next: new theme, possibly a plugin or two. Who should I ping for that, @otto42 or @coffee2code?

  • Jen Mylo 2:44 am on December 18, 2012 Permalink | Log in to leave a Comment

    Team rep votes are in! Unsurprisingly, it’s Otto as team rep with no backup rep for now. If we’re able to open up more opportunities for contributing to site and tool improvements, maybe next time. @otto42, you are on the hook for weekly updates on make/updates about projects happening on the wordpress.org site. Thanks!

    • Samuel Wood (Otto) 3:47 pm on December 25, 2012 Permalink | Log in to Reply

      At present, doing a weekly doesn’t make any sense since we’re not doing anything special. I’ll report in after the new year with plans and such.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc