As announced on Drupal.org at https://drupal.org/node/1661464 and at the Drupal meetups in and around Los Angeles this month, Drupal.org will be going down for scheduled maintenance for approximately 30 minutes. The official announcement is included below.
Please keep in mind that while some things won't work while Drupal.org is undergoing maintenance, you can still interact with Drupal community members in and around Los Angeles here at http://groups.drupal.org/dtla, http://groups.drupal.org/sgv, http://groups.drupal.org/la, etc. and in real-time on IRC at #drupal-la.
Why post an event announcement? It's possible that new members to our community may not have gotten the news that this downtime has been scheduled. Unless you're heavily involved with Drupal or the Drupal community (i.e. you go to all the meetups, read Planet Drupal, are on the official Drupal.org mailing lists, etc.) it's possible you may not have heard this was happening.
Additionally, anyone who subscribes to the above groups' iCal feeds, e.g. at http://groups.drupal.org/ical/219129, will now have the maintenance period show up in their calendar.
Official announcement
On Monday, July 2 from 6:00 PM to 6:30 PM PDT (01:00 to 01:30 UTC), drupal.org will be briefly brought down for updates. The main website, drupal.org, will be inaccessible, as will SSH-based access, both read and write, to all Git repositories hosted on drupal.org. Read-only access to Git repositories over the http:// or git:// protocol will be uninterrupted, as will access to all other parts of the web presence.
This will be the first (major) deployment of new Git-related functionality on Drupal.org since the migration from CVS to Git. We'll be deploying some fixes that have prevented a couple of projects from making releases, as well as long-overdue functionality allowing project and sandbox maintainers to set the default branch on their repository. No more empty master branches!