briandoll

We just posted more details on this incident: https://github.com/blog/1698-weak-passwords-brute-forced

Super sad situation, but this is a classic Streisand effect in the making. http://en.wikipedia.org/wiki/Streisand_effect

GitHubber here. There's some great questions in this thread already. I'm AFK this weekend, but if you've got more questions about our structure, or how we use GitHub.com to work like this, ask away and I'll try to answer them in a blog post next week.

Loved that talk! It was Clay Shirky "How the Internet will (one day) transform government" http://www.ted.com/talks/clay_shirky_how_the_internet_will_o...

They are! You can see them listed on the homepage as well as the community page, which lists organizations by country: http://government.github.com/community/

If you see any that are missing, please do open a pull request: https://github.com/github/government.github.com

s/last/this past/

https://github.com/blog/1547-release-your-software

We've got a list of security researchers who have disclosed vulnerabilities to us responsibly (including Homakov) on our help site: https://help.github.com/articles/responsible-disclosure-of-s...

Yep, this was inspired by TextMate. Here's the blog post when this was announced: https://github.com/blog/793-introducing-the-file-finder

Hard to believe that shipped two years ago

We're really happy not having sales commissions at GitHub.

Further reading: Optimizing Sales for Happiness https://github.com/blog/1230-optimizing-sales-for-happiness

I'm quoted in the article and I wanted to clear one thing up that was missing from it.

When bots get reported to us by people using GitHub our support folks reach out to the bot account owner and encourage them to build a GitHub service[1] instead. As a service, the same functionality would still be available to everyone using GitHub, but it would be opt-in instead.

A few months ago we heard from some developers of service integrations that beyond the existing API features, it would be handy to be able to provide a form of "status" for commits. We added the commit status API [2] in September to accommodate that. We're always open to feedback on how the API and service integrations can improve.

The point is, GitHub services are a much better way to build integrations on GitHub.

[1] https://github.com/github/github-services [2] https://github.com/blog/1227-commit-status-api

Google Analytics site speed data is only based on 1%[1] of your traffic while New Relic's Real User Monitoring aims to track all of your traffic. I'm sure that can lead to differences in accuracy.

(Disclosure: I used to work for New Relic)

[1] https://developers.google.com/analytics/devguides/collection...

D3 is beautiful and accessible, but more importantly I think it re-frames our approach to visualizing data, rather than jamming data into pre-made charts.

The D3 wiki documentation is incredible. I've been meaning to do this for a while, but I'm going to read through the docs over the holidays.

You can check out the wiki and browse it locally: https://github.com/mbostock/d3/wiki/_access

The spike in repository creation in July was from the PLD Linux Distribution joining GitHub. We're looking into the pull request spike in the spring, too.

I tend to aggregate data into something manageable before I attempt to graph it, regardless of what tool I'm using. If you can deal with daily numbers, you only need 365 rows per year, and less than 9k per year if you're doing hourly numbers.

Here's another list, sans product hype:

Unix command-line tools like awk and grep. Set operation commands are essential too (http://www.catonmat.net/blog/set-operations-in-unix-shell/)

Ruby/Python/Perl for more complex massaging and wrangling

Excel (yes, really) for quick stats and graphs, great 1st step in understanding what you have

D3.js for visualization

I've used R in the past, but I found I was trying to squeeze data into R models. D3 is pretty hard to grasp initially (I'm very much still learning) but I'm finding that it's helping me think through how to visualize the data I have, rather than just forcing it into one of a few standard charts.

Same here. I write a lot of notes in markdown that I sync using Dropbox. I often want to read and edit those notes on my phone or ipad, but I don't remember the exact file names.

Similarly, I wish photo apps had a "use most recent photo" button, instead of making me select my photos, scroll down to the very bottom, and click on the last square.

Gist is great for that too: https://gist.github.com/

Great news! I've been using the Prismatic app daily since it came out. It perfectly fits the job of "what's going on". I tend to skim on the iPhone and save good articles to read later (or with Pocket, another favorite).

The tech is really interesting too. High Scalability had a post this summer on how it all works: http://highscalability.com/blog/2012/7/30/prismatic-architec...

Yea, I came here to say that too. I can't imagine adding a Dropbox-only solution when something like filepicker.io exists.

Correction: We (GitHub) do not push data to BigQuery. Ilya's project archives the GitHub public timeline. That data is then uploaded from his archive into BigQuery. The BigQuery project is public, so anyone can use it.

Yep, the repository is public and a big chunk of this public data is accessible on BigQuery for anyone to query and analyze.

Ilya Grigorik and myself just gave a talk at Strata[1] on interesting analysis and visualizations that people did with the GitHub Archive as part of the GitHub data challenge[2].

We'll post a link to the talk soon. We announced during the talk that BigQuery will soon (in the next day or two) have an archive of the GitHub public timeline from February 2011 to now. I can't wait to see what people do with it!

[1] http://strataconf.com/stratany2012/public/schedule/speaker/2...

[2] https://github.com/blog/1162-github-data-challenge-winners

The fatal flaw both in a "chief culture officer" and a "chief dissent officer" is the assumption that this is one person's job, who sits on high, vs. being _everyone's_ job.

A job title with "culture" in it doth not a culture make.

It's humbling to read this, and makes me incredibly proud to know Jim and Jen Remsik, who created and run Madison Ruby.

She wouldn't take advantage of this thread by linking to her event management business, so I will: http://saplingevents.com/

Jen does an incredible job building unique and interesting events and totally gets the important details that make a conference memorable and exciting. If you're thinking of hosting an event, I'd definitely give her a call.

The website says that the book will be for sale on Amazon soon. Anyone know if it will be Kindle friendly? The text looks like it would convert easily from the web pages, if not.

I live in Marin. It seems very strange Comcast won't service it. Are you living on the docs?

Check out: http://sonic.net/

Every git repository on GitHub can also be used with svn.

Details: https://github.com/blog/1178-collaborating-on-github-with-su...

Another great part of using pull requests, is that they allow everyone to see what's going on, mid-stream. They are awesome for major features, especially if you open them early on.

We all collaborate via pull requests as various features are being worked on. This way, when someone leaves a comment asking about the overall design (code or visual), suggesting a different approach, it's done while the feature is in development, not when the author thinks the feature is ready to ship.

Doing a big code review after a feature has been completely built and is ready to ship seems like a mini-waterfall process.

If you don't know who your representative is by name, you can look them up here: http://www.house.gov/representatives/find/