This.. is a bit of a bombshell:
Software is eating the world. Meanwhile, Microsoft is eating the software world… one acquisition at a time.
Earlier this week GitHub Sponsors came out of beta to general availability for developers with bank accounts in 30 countries (and growing). Also, check out the companion video celebrating some of the developers of GitHub Sponsors. Next steps?
This is just the beginning for native sponsorships on GitHub. We’re working hard to build out great sponsorship experiences around the world.
The 2.0 release of Github Desktop shipped yesterday. Here’s a quick breakdown of what’s new…
You can resolve merge conflicts more easily, co-author commits to share credit with others, and check out your GitHub pull requests. And with the 2.0 release, rebasing and stashing are now also supported on GitHub Desktop—the two most requested features.
HUGE news coming from GitHub today:
We’re thrilled to announce the beta of GitHub Sponsors, a new way to financially support the developers who build the open source software you use every day. Open source developers build tools for the rest of us. GitHub Sponsors is a new tool to help them succeed, too.
100% of sponsorship money goes to the developers and they’re even matching contributions up to $5k during a developer’s first year! Also, the whole thing is tightly integrated in to GitHub itself:
Open source projects can also express their funding models directly from their repositories. When
.github/FUNDING.ymlis added to a project’s master branch, a new “Sponsor” button will appear at the top of the repository. Clicking the button opens a natively rendered view of the funding models listed in that file.
There’s lots to digest here, but at first glance this looks like an amazing addition to the open source ecosystem. 🎉
Today, Atlassian Bitbucket, GitHub, and GitLab are issuing a joint blog post in a coordinated effort to help educate and inform users of the three platforms on secure best practices relating to the recent Git ransomware incident.
So what happened?
On Thursday, May 2, the security teams of Atlassian Bitbucket, GitHub, and GitLab learned of a series of user account compromises across all three platforms. These account compromises resulted in a number of public and private repositories being held for ransom by an unknown actor. Each of the teams investigated and assessed that all account compromises were the result of unintentional user credential leakage by users or other third-parties, likely on systems external to Bitbucket, GitHub, or GitLab. The security and support teams of all three companies have taken and continue to take steps to notify, protect, and help affected users recover from these events.
You can sign up for the beta here.
The state of the Octoverse has landed and with it a new dataset of top programming languages for 2018.
According to languages by contributor (as of Sept 30, 2018)… Ruby dropped from #5 to #10, Python swapped with PHP to take over the #3 spot — plus so much more…if you dig into the data.
Here’s the visual…
New GitHub CEO, Nat Friedman:
I’m thrilled to share that the Microsoft acquisition of GitHub is complete. 🎉 Monday is my first day as CEO. Millions of people rely on GitHub every day, and I am honored by the opportunity to lead this company.
He goes on to share the two principles for GitHub and these three objectives that are at the top of his mind moving forward:
- Ensuring GitHub is the best place to run productive communities and teams
- Making GitHub accessible to more developers around the world
- Reliability, security, and performance
Today, we’re introducing future-forward features that further shape GitHub to better reflect how developers work. New to our platform, GitHub Actions and GitHub Connect advance development workflows and break down barriers between teams. We’re also releasing powerful new security tools with the GitHub Security Advisory API, new ways to learn across teams with GitHub Learning Lab for organizations, and more.
Actions stole the show (are you signed up for the beta yet?), but there’s a lot here. Stay tuned for more coverage/conversations as we have time to digest it all.
In total the project took a year and a half to upgrade from Rails 3.2 to Rails 5.2. Along the way we took time to clean up technical debt and improve the overall codebase while doing the upgrade. Below we’ll talk about how we upgraded Rails, lessons we learned and whether we’d do it again.
Congrats to Eileen and the team on this massive effort! Click through to read how they did it and the lessons the learned along the way.
The news is true. Microsoft is acquiring GitHub and is expecting the agreement to close by the end of the year.
Chris Wanstrath writes on the GitHub blog:
When GitHub first launched ten years ago, I could have never imagined this headline.
Their focus is on the long tail and the developer.
What hasn’t changed, however, is our focus on the developer. From the beginning, we have been obsessed with building a product for the people using it. We want to make developers more productive and we want more people to become developers. So as we look to the next decade of software development and beyond, we know it’s all about the developer.
The relationship that has formed between GitHub and Microsoft is years in the making.
…as we’ve gotten to know the team at Microsoft over the past few years through collaborating on projects from Git LFS to Electron, we’ve learned that they agree. Their work on open source has inspired us, the success of the Minecraft and LinkedIn acquisitions has shown us they are serious about growing new businesses well, and the growth of Azure has proven they are an innovative development platform.
…most importantly, we both believe we can do greater things together than alone
As part of this change, Nat Friedman will be taking on the role of GitHub’s CEO. We have been searching for a new CEO for some time and found in both Microsoft and Nat a partner we believe will strengthen and grow the GitHub community and company over the next few years.
We have been in the trenches for years covering the dramatic shift of Microsoft.
Here’s a fairly comprehensive list of our coverage shared in an issue on a trending repo on GitHub. If for some reason that issue gets deleted I have archived the list here.
Parker Moore, on GitHub’s blog:
Today, custom domains on GitHub Pages are gaining support for HTTPS as well, meaning over a million GitHub Pages sites will be served over HTTPS.
We have partnered with the certificate authority Let’s Encrypt on this project. As supporters of Let’s Encrypt’s mission to make the web more secure for everyone, we’ve officially become Silver-level sponsors of the initiative.
If your custom domain uses
ALIAS records, no action is required to go HTTPS. If (like me), you have a custom domain using
A records, follow along here.
Jon Rohan writes on the GitHub Blog:
To support your project’s contributors it’s important to make the contributing experience as frictionless as possible. Migrating our Octicons to Figma let us cut out painful steps in our previous workflow. Having their API available for automating the work has allowed contributors to contribute using powerful platform-agnostic design tools without any overly complex setup.
This seems to be one of the first major steps I’ve seen to use a platform-agnostic design tool like Figma, which lets you design, prototype, and gather feedback all in a browser based design tool. Couple that with a robust API and some robots to automate things as well as open up your design flow to contributors.
It’s the time of year for 2017 wrap-ups and 2018 predictions. We expect these from bloggers and news sites, but this seems like an odd post coming from GitHub:
Data is on the rise, placing an even greater emphasis on security, cloud, and open source. Jason Warner, SVP of Technology, shares his predictions on the major technology trends for 2018.
I wouldn’t call too many of these predictions bold, but it’ll be interesting to see how well they hold up.