WordPress.org

Ready to get started?Download WordPress

Make WordPress Systems

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • John James Jacoby 2:29 am on January 6, 2015 Permalink |
    Tags: ,   

    Can I please have commit access granted to buddypress.svn.wordpress.org for the username “dcavins″?

    David will be focusing on BuddyPress’s invitations API in 2.3, and should be considered a permanent committer for all releases going forward.

    We’ve talked about the responsibilities, expectations, and security of commit access. It will be great to have his expertise in improving BuddyPress’s invitations, and we’re pumped up and ready for him to get started.

     
  • Andrew Nacin 6:54 pm on December 29, 2014 Permalink |
    Tags:   

    Can I have r5763-deploy for the wporg-web role updated? Requires an nginx deploy. It retires phpdoc.wordpress.org. (There will be more cleanup here, this is just the important part.)

     
  • Konstantin Kovshenin 9:21 am on December 16, 2014 Permalink |
    Tags: ,   

    Hello! Can we please have the mysql and mysqldump CLI tools installed on WordCamp.org? We’d like to use them to dump and (possibly) restore cherry-picked non-global tables during our city.wordcamp.org/year migration. Thanks!

     
  • Andrew Nacin 5:26 am on December 16, 2014 Permalink |  

    Moving the NFS mounts 

    Per a conversation with @barry, we’re going to move most NFS mounts on .org to a single centralized location. Here’s the checklist, in order:

    After that:

     
  • Andrew Nacin 8:24 pm on December 13, 2014 Permalink |
    Tags: caching, lb,   

    We’re going to be doing a HEAD request to https://api.wordpress.org/translations/core/1.0/?version=4.1 on the 4.1 about page, in JavaScript. While the heavy operations performed there are cached in memcache for 15 minutes, I think it may be prudent for us to (temporarily?) cache it at the load balancers to avoid being CPU-bound.

    Suggestion: cache OPTIONS and HEAD requests to https://api.wordpress.org/translations/core/1.0/ for a period of time. A minute or 15 minutes is fine, but so is an hour.

     
  • Ian Dunn 5:38 pm on December 12, 2014 Permalink |
    Tags:   

    @otto42, can you please give my account access to close tickets on themes.trac? I need to test out some i18n changes to the theme upload script and don’t want to clutter the trac w/ a bunch of open test tickets.

     
  • Ian Dunn 8:06 pm on December 11, 2014 Permalink |
    Tags:   

    @nacin, the new Training team would like to use training@ in conjunction with SupportFlow. Could you please setup the address for them? Once it’s active I can setup SupportFlow.

    xref https://make.wordpress.org/systems/2014/11/18/email-google-apps/
    cc @liljimmi

     
  • Alex Shiels 4:11 am on December 4, 2014 Permalink |  

    I seem to have lost access to a couple of things, notably dotorg.trac and phpmyadmin on mc – 403 on both. Sandbox and svn access are fine, as is access to the mc root. I have had a couple of proxy issues lately – is the problem on my side?

     
    • Alex Shiels 5:46 am on December 11, 2014 Permalink | Log in to Reply

      This is still happening intermittently – it mostly fails but occasionally works. When it has worked, I’ve been on a different internet connection. Which suggests that it probably isn’t the proxy. And forcing the proxy on (as opposed to using the pac) doesn’t fix it.

      Dion confirmed that I appear to have access. Could this be an IP block or similar? It’s a default Nginx 403 page, if that helps.

    • Barry 5:55 am on December 11, 2014 Permalink | Log in to Reply

      Sorry for the delay. There have been some new proxies added lately, especially in your neck of the woods. List has been updated.

  • John James Jacoby 8:16 pm on December 1, 2014 Permalink |
    Tags: ,   

    Can I please have commit access granted to buddypress.svn.wordpress.org for the username “tw2113″?

    Michael will be focusing primarily on documentation similar to the fine work Drew does with WordPress core.

    We’ve chatted about the responsibilities and expectations commit access comes with, and we’re excited to have him aboard improving BuddyPress’s code documentation.

     
  • Jen 9:01 pm on November 18, 2014 Permalink |
    Tags: , gmail   

    Email & Google Apps 

    We have a handful of @wordpress.org email addresses set up as forwards. For the teams that need an official email address and a supportpress/supportflow setup, we have been doing addresses on wordcamp.org (which has mailboxes) or setting up one-off gmail addresses to handle the mailbox, the owner of which might get lost over time. I talked to Barry at the team meetup days at WCSF about this and he said we should put wordpress.org on gmail for email. Matt said this was okay.

    I’ve reclaimed the Foundation account for google apps for non-profits (a WC organizer had used the tax id to claim it without asking first, so we had to jump through some hoops). I’ve set up the account and gone through the steps with Ashish Shukla to have it recognize wordpress.org as the domain. The next step would be to modify the MX record to start routing email through the google apps account, but that gets complicated when it comes to ensuring no disruption to existing forwards, which is why Ashish and I were waiting for Barry to be available. When I spoke to Barry today, he said that @nacin is doing something around email too, so now he’s not super comfortable making changes at all lest we inadvertently step on each others’ toes.

    @nacin: what is the thing you are doing with email, and does it preclude a shift to having actual mailboxes that are official? Let’s coordinate with whomever else is working on this to make sure everyone’s needs are met. I’m happy to share the google credentials with the appropriate people to get it going. We also get stuff like official hangouts the teams can use, calendar, etc. as part of the google apps account. If there’s a reason *not* to take Barry’s advice about using google apps/gmail for the team emails, I can remove wordpress.org from the google account (if so, please explain).

     
    • Andrew Nacin 11:02 pm on November 18, 2014 Permalink | Log in to Reply

      Hey @jenmylo, I’m trying to figure out the exact use case for doing this. We’ve always done forwards, which works perfectly well for these two situations:

      • An individual person who needs their mail forwarded to their primary email
      • A group email that needs to be forwarded to multiple people

      Google Apps would add overhead to both of these.

      Then there’s the third use case, which is a “mailbox.” Even if we switched to Google Apps, we wouldn’t actually have people accessing these mailboxes directly. We would pipe emails through a SupportPress or Supportflow install. The only benefit to this setup, thus, would be replacing this procedure: “setting up one-off gmail addresses to handle the mailbox, the owner of which might get lost over time”.

      Yes, this is indeed our current approach. But it actually works quite well. I know of eight such accounts in use, and all of the passwords are stored in a single configuration location. I’m not sure about the missing owner situation — perhaps it has happened before, but in order for SupportPress/Supportflow to actually connect to these accounts, it needs the password anyway, which ultimately controls everything for these. Even if we moved to Google Apps, we’d still need a similar configuration.

      I remember talking to Barry about this at WCSF and at the time at least, we both thought this was about WordCamp.org moving to Google Apps. I don’t know what the requirements are there (with regards to organizing teams and how that all works), and I have no opinion either way on which direction WordCamp.org is set up. With WordPress.org, I don’t see the reason for switching.

      I’ve been dealing with a few email-related things, primarily @chat.wordpress.org. I don’t think what I’m working on would be affected by anything here.

      • Jen 11:08 pm on November 18, 2014 Permalink | Log in to Reply

        cc @barry ^^

      • Ian Dunn 1:26 pm on November 19, 2014 Permalink | Log in to Reply

        If there isn’t a consensus for setting up real mailboxes, we could work around that for SupportFlow installs by setting up foo@wordpress.org aliases that forward to wordpress-foo@gmail.com, and then connect the Gmail account to SupportFlow.

        One drawback to that is that replies to the user would be sent from the Gmail account, rather than the WordPress.org account. That’s not a big deal, but it does feel a little janky, and the user will end up with two addresses in their address book for the same entity.

        • Dion Hulse 4:11 am on November 20, 2014 Permalink | Log in to Reply

          I don’t have any knowledge of how SupportFlow works, but is there any reason why the email would have to be sent via the mailbox?
          Couldn’t you just use the WordPress.org outgoing SMTP & BCC the email to the gmail account if required?

          • Ian Dunn 12:06 pm on November 20, 2014 Permalink | Log in to Reply

            Sorry, I’m not folllowing. Are you saying it’s possible to setup a foo@wordpress.org alias, and then send mail from it as if it were a regular account? Or that the current @wordpress.org addresses have regular SMTP accounts, but with the mailbox disabled?

            In my limited experience, the ability to send mail from an address is coupled with having a mailbox, but maybe that’s just an artificial restriction that things like Plesk have added on top of the mail service itself?

            • Samuel Wood (Otto) 11:32 pm on November 21, 2014 Permalink

              I’m not entirely certain on all the details, but no, an “account” is not necessarily linked to a sending address.

              For example, for the themes supportpress (where commercial theme listings are handled), there is a forward to a gmail account. SP retrieves the email from there. But any replies are actually sent back through our own SMTP server at mail.wordpress.org. So, the gmail account never actually sees the replies, we don’t send replies back through it or from it. It’s just a receiving box and holding area (and spam-scanner).

              I am unfamiliar with Plesk.

            • Ian Dunn 8:58 pm on November 23, 2014 Permalink

              Ah, ok. I think that would work for our purposes, then.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel