You all know about GitHub Jobs by now, so we thought we'd kick off the official launch by highlighting some cool jobs we've found in the past seven days.

Some of Our Favorites

• node.js ninja apprentice for Nodejitsu
• Webアプリケーションエンジニア for Forschooner, Inc in Japan
• A Senior UI/Frontend/Rails Dev in Berlin

Futuristic Stuff

• Clojure related jobs
• node.js related jobs
• Redis related jobs
• iOS related jobs

Cool Companies

Drupal Engineers for Acquia:

We think developers who want to work on the best, most dynamic, and most interesting open-source web technology project on the planet have no better place to work than here – working on Drupal.

Software Engineer (Scala) for Remember the Milk:

Did you fall in love with Scala at first sight? Do you dream of actors, DSLs, implicits and pattern matching?

Machine Learning Specialist for Hello, Chair Inc:

Essentially, we want you to enter a Netflix Prize-esque competition against yourself.

And tons more on GitHub Jobs!

Sorry for the last minute notice, but GitHub will be buying beer for geeks at Flat Top Johnny's in Cambridge tonight (Tuesday, August 10th) around 9:30. We're piggybacking on the bostonrb after party, so come mix and mingle. I may even get a couple LinuxCon geeks to come out with us, which is why I'm here in the first place.

Also, even though PJ won't be there, it is his birthday so come and celebrate it as it was meant to be celebrated!

Where and When:

1 Kendall Sq
Cambridge, MA 02139
9:30p, Tues Aug 10th

We added a special header to all outgoing repository and direct message notifications that should make it much easier to filter emails:

Direct messages get a List-ID of user.github.com, while repositories get repo/user.github.com. Do you want to easily filter all notifications from a user or organization? GMail supports wildcards too:

This is a quick workaround for those getting flooded with notifications. We feel your pain, and are discussing ways to solve this without drowning you in a sea of checkboxes.

Update: Gist comments now get a List-ID of ID.gist.github.com.

In a little over twelve hours from now we'll be flipping the switch on GitHub Jobs. That means you only have until midnight PDT to post a job at our discounted $150 rate.

We're really excited with the quality of jobs being posted and can't wait to flip the switch. We've seen some awesome listings so far — look for some highlights on the blog tomorrow.

Another reminder to update your location and hiring status

If you're looking for work, we've designed a way to promote jobs you'll be interested in on your GitHub dashboard. But they will only be visible if you explicitly opt-in on the job profile section of your account settings — so if you're looking for work, make sure you've checked the available for hire checkbox.

We will also be using the location field of your public profile to better figure out what jobs you might be interested in — so make sure it's up to date.

I'm in Boulder again and it's time for another GitHub Meetup: Boulder Edition! Once again, we'll meet at my favorite South Boulder bar: The Southern Sun. Here's the details:

• When: 8:30pm, Tuesday, August 10th
• Where: Southern Sun Pub & Brewery, 627 S Broadway St, Boulder, CO 80305

It should be nice out at night, so if the weather is good, we'll all be outside at the picnic tables!

I'm currently at the Yet Another Perl Conference, Europe (YAPC::EU) doing some Git talkin' and one of the big talks here was by Patrick Michaud (pmichaud) about the very recent release of Rakudo Star, a useful and usable release of Perl 6.

This is a pretty big deal in the Perl community as it's the first useable Perl 6 implementation out there, which as many of you may know has been in the spec phase for a very long time. Well, today you can start playing in this early Perl 6 and giving feedback to the Perl community.

Also, it's hosted here at GitHub! The Rakudo team is using GitHub to develop it's implementation of Perl 6 at rakudo/rakudo

You can read the Rakudo Star release announcement from a few days ago here. And the announcement on Perl.com here.

To try it out, download the official release from the GitHub downloads page for Star:

http://github.com/rakudo/star/downloads

Then run :

$ perl Configure.pl --gen-parrot
$ make
$ sudo make install

That's it. You can read more about Perl 6 at http://perl6.org - you can also find a book on Perl 6 on GitHub at perl6/book. We're glad to see the core Perl community using GitHub so much.

A little while ago Mark Otto, Ben Bleikamp and Chris Jennings started up a little designer meetup they like to call Design Lunch. The first few meetups were a success — much design geekery was shared over lunch.

But we thought Design Lunch might be a little more awesome if we could have it somewhere a little less formal (where we didn't have to sit down), and wouldn't it be awesome if we could get a company to sponsor it?

Tomorrow (Thursday, August 5th) GitHub will be sponsoring Design Lunch: After Hours edition at Thirsty Bear at 6pm. Come talk design and have some beers on GitHub.

One week from today (August 10th) we're launching our job board: GitHub Jobs. Simple and focused, GitHub Jobs is a great way for the best developers to find the best jobs.

Want to post a job? All listings posted in the next seven days will receive a 50% discount: $150 for a 30 day listing (listings are normally $300).

Don't delay: post a job listing!

Find Great Developers

When you post a job on GitHub Jobs, you're sending a message: you want developers who care about their craft.

Starting next Tuesday, everyone will be able to search and browse jobs. Any developer on GitHub who has checked "Available for Hire" in their account settings will also be shown targeted job listings on their dashboard, based on their location and favorite programming languages.

Of course, these listings can be hidden permanently if you don't find them useful. But we think you will.

As GitHub Jobs grows we plan to add more ways for you to reach developers and more ways for developers to find the job they want. But for now we're starting with the basics: quality listings by quality companies.

Don't miss your chance to get 50% off and pay only $150 for a 30 day listing - post a job today!

The past few months I've been having this recurring dream where I kept seeing this image float around my room:

If you've been a veteran to our search, you'll know what I'm talking about — to say it was frustrating is an understatement. A few days ago we finalized some new dedicated hardware in an effort to make our search the best we can. So far, the results have been awesome. We've reduced search failures by around 80%. Here's a graph of search failures over time:

We're still in the process of ironing out some bugs in queries and re-indexing missing data, but so far we're pretty happy with the initial improvements. Here's to a brighter future filled with more successful and relevant GitHub search results!

Working on a Mac app? Writing the next big iPhone fad? Using GitHub should be a bit nicer now:

We're now suppressing .pbxproj and .xib files in commits and compare views.

Thanks to joericioppo for the idea!

Following our one millionth repository, we'd like to welcome a couple new notable faces around GitHub.

The first is the Mono project.

Mono is an open source implementation of Microsoft's .NET Framework based on the ECMA standards for C# and the Common Language Runtime.

You can find Mono's code under the mono organization.

The second is an official mirror of the OpenStack platform.

OpenStack Compute is software for automatically creating and managing large groups of virtual private servers. OpenStack Storage is software for creating redundant, scalable object storage using clusters of commodity servers to store terabytes or even petabytes of data.

If you aren't comfortable with bzr or don't feel like logging in to see the code (the official code is on launchpad), you can now keep up with development using Git & GitHub.

You can find OpenStack's code under the openstack organization.

Welcome to GitHub!

Last night, the one millionth git repository was created on GitHub. That is a heck of a lot of repositories.

Since we first launched, there have been a lot of interesting code filling those repositories, including projects like jQuery, Erlang/OTP, Ruby on Rails, curl, node.js, Redis, CakePHP, and an amazing amount of other great public and private projects.

There's been a lot of interesting gists made, too — they're full-fledged repositories, after all! — from spreading the word about RubyGems' move to piping Apple live event streams to a Campfire room to gists that create gists to GitHub matchmaking.

Thanks for choosing GitHub. Onward to ten million!

The Software Craftsmanship North America 2010 conference looks pretty interesting and has a killer speaker lineup. Gonna be in Chicago in October? Check it out. Want to be in Chicago in October? Here's your excuse!

Some info from the conference itself:

Software Craftsmanship North America (SCNA) is planting a root in the industry as the premier event for the Craftsmanship movement. Software Craftsmanship, which sprouts from the Agile Principles, embraces the core attributes of successful software developers. SCNA is the place to be to develop new software skills and techniques, meet other devoted craftsmen, or find quality people for your company!

Early bird registration ends August 15th so grab a ticket today!

When we launched Compare View earlier this year, we knew there was a killer feature still missing: the ability to compare branches across repositories. Easy forking and the networks that emerge as a result is what makes GitHub great. Limiting the Compare View to a single repository felt all wrong. So today we're flipping the switch on some non-trivial architectural changes that make cross-repository comparisons a reality:

Here's how it works: it's now possible to specify a <user>: prefix on the comparison's starting or ending point. When given, the <user> part identifies the owner of a another repository/fork in the same network. In the example above, we're comparing branches in the homebrew network with mxcl's master branch as the starting point and adamv's rvm branch as the ending point.

To change the starting or ending point, click the ref label buttons and enter the branch name or commit SHA1 to switch to. For example, we can change the starting point from mxcl's master branch to the brew07 branch like this:

A scheduled DB maintenance went haywire yesterday, taking a number of repositories temporarily offline.

While pushing and pulling were briefly offline (and for that we're sorry!), the first phase of the migration worked. The problem was we didn't know it worked - the tools we were using failed to report success (or anything, really). As a result we weren't able to start phase two, which left some repositories unaccessible via the web interface.

What should have been a few minutes of interrupted service for some users turned into a huge pain. But I don't want to blame our tools - the real problem is our maintenance strategy. Any amount of interrupted service is unacceptable at this point.

With that in mind, we're going to re-think the way we do maintenance. Zero downtime and uninterrupted service is the goal. GitHub should be there when you need it.

When we have a solution we'll post about it here (like we always do). Sorry for the outage - we really don't want it to happen again.