Back to GitHub.com GitHub Support Contact GitHub

GitHub partners with the Fintech Open Source Foundation (FINOS)

We’re proud to announce our membership in the Fintech Open Source Foundation (FINOS)—a newly launched nonprofit foundation promoting open innovation in financial services—along with technical organizations like Red Hat and Nodesource and financial organizations like Citigroup, UBS, and HSBC.

Financial services institutions increasingly rely on open source software to build the best software for their customers, improve infrastructure, and unlock the potential of their engineering teams. We’ve seen this firsthand on GitHub, where contributions by members of fintech organizations have grown by 40 percent in the past year—and we expect this trend to continue. Joining FINOS will allow us to work better with the growing community of open source developers addressing the unique challenges and opportunities of the financial services industry.

What is FINOS?

The Symphony Software Foundation recently announced its launch as FINOS, with the goal of providing an independent and accessible forum dedicated to driving open innovation in the financial services industry. See the announcement to learn more.

In addition to programs carried over from the Symphony Software Foundation, FINOS will continue to broaden its scope by adding new programs, members, and contributors. The full breadth of Foundation programs advance open source practices, mindsets, and software that address the specific challenges and opportunities of the financial services industry.

FINOS’ commitment to fostering open collaboration will be critical as financial technology firms continue to evolve. We’re thrilled to join them in this mission and better serve the open source developers building the future of finance.

The fight progresses as the net neutrality deadline approaches

When the U.S. Federal Communications Commission (FCC) published its repeal of net neutrality regulations in the Federal Register on February 22, the U.S. Congress had 60 legislative days to disapprove of the FCC order. Approximately half of that time is up. To learn more about how this timeline works—and why the pressure is on—check out the following resources:

Meanwhile, the quest to find one more vote to move the process forward in the Senate continues. Write Congress to aid in the search.

On May 2, small businesses will deliver a letter to Congress, urging disapproval of the FCC order. The first week of May is Small Business Week, and Congresspeople take business owners from their districts very seriously. If you represent a small business in the U.S., sign the letter.

Meanwhile, at least 33 U.S. states and many cities have enacted or have pending actions to protect net neutrality. California is considering passing S.B. 822, the strongest and most comprehensive set of net neutrality protections in the country. GitHub joined almost 60 startups in a letter of support for this bill, which has its second committee hearing tomorrow. If you’re in California, tell state legislators to protect net neutrality by supporting S.B. 822.

Not in the U.S.? Help spread the word about the fight for net neutrality, or learn more about and get involved in the most pressing open internet issues in your country.

Updates to our Privacy Statement and Terms of Service

We’re in the process of updating our policies, and we’d like to get your input! We want to hear what you think of them and whether any of our changes or clarifications can be improved. Head on over to our Site Policy repository to see the open pull requests.

What’s changed

About every six months, we review our terms and policies to make sure they’re as clear as they can be and decide whether we should make any updates. This time around, we’re very focused on bringing our policies into alignment with a new law in Europe known as the General Data Protection Regulation, so we’ve made some changes to our Privacy Statement and Terms of Service to cover our compliance with that law. We’ve made other changes to our terms to clarify account control and developer obligations when integrations are created for others.

Updates to our Privacy Statement

Over the last few months, we’ve gotten a few questions asking about our General Data Protection Regulation (GDPR) compliance. We are proud to announce that we are compliant with the GDPR. Additionally, we have always provided the same level of privacy protection to our users regardless of their residency, location, or citizenship—and that will not change. We provide strong privacy and security protection to all of our users.

For the most part, our changes to the Privacy Statement are only points of clarification. GitHub doesn’t ask for more personal data from our users than we need to provide our services to you. Where we offer you the option of giving us more data, we provide you the ability to access and delete the data you have given us. For example, you can always remove your profile information, your comments in issues, and your repository contents. We have gone through our Privacy Statement to provide more context and transparency, though, so our users understand exactly why we ask for information and what we’ll do with it.

GDPR Compliance

  • The GDPR requires us to inform our users about the legal basis on which we process their data. In this update, we explain what data we collect and why
  • We describe our security practices in more detail
  • We now provide a separate page describing our tracking, our use of cookies, and listing our subprocessors (the vendors and third parties we have engaged to process personal data on our behalf)
  • Throughout the Privacy Statement, we provide greater transparency and insight into our data collection, data handling, data retention, and data deletion processes
  • If you are a Corporate Terms of Service customer and you need a Data Protection Agreement with us, please contact support. We will be happy to provide one. Please understand that with the GDPR compliance deadline coming up, our volume of requests is high, but we will respond to you as promptly as possible

Updates to our Terms of Service and other policies

Standard Terms of Service and Corporate Terms of Service

Much like the changes to the Privacy Statement, most of the changes to our terms are clarifications of pre-existing sections. Here are a few sections we’d like to highlight:

  • Third Party Applications: We combined the Marketplace section with general requirements for those creating integrations for other users to provide better protections for GitHub users and their data. The Marketplace section is now called “Third Party Applications,” since it now applies to more than just GitHub’s Marketplace. We’ve also added a “Third Party Applications” section to the Privacy Statement to discuss our users’ privacy expectations in regards to those applications
  • Access to Private Repositories: In Section E, we clarified the purposes for which we may be required to access private repository contents, in line with the security obligations of our GDPR compliance program
  • More definitions: We included definitions of “User Accounts” and “Organizations” and described who has control of those types of accounts

Other policies

  • Community Forum Code of Conduct: Last year we launched the Community Forum. The Community Forum is a growing part of our platform and we thought it’d be great to include the Code of Conduct in our Site Policy repository, since we hadn’t yet included it
  • Marketplace Developer Agreement: We’ve made some updates to this agreement that reflect some of the changes to the Marketplace over the past year
  • Takedown policies: We’ve updated our takedown policies to add clarification around what’s covered by our DMCA policy
  • Statement Against Modern Slavery and Child Labor: We’ve added our 2018 statement describing the steps we’ve taken to prevent modern slavery and child labor from occurring in our business and supply chain

Taking action

We’ll leave the pull requests open until 5 pm Friday, May 18. Then, we’ll take a week to go through your comments and make changes to improve the policies. We’ll enact the new policies on Friday, May 25.

We look forward to hearing from you!

Introducing GitHub Learning Lab: A new way to level up on GitHub

GitHub is more than a home for code. It’s a forum for collaboration, a sandbox for testing, a launchpad for deployment, and often, a platform for learning new skills. After training thousands of people to use Git and GitHub, the GitHub Training Team has established a tried-and-true method for helping new developers retain more information and ramp up quickly as they begin their software journeys. And now, we’re making those experiences accessible to developers everywhere with GitHub Learning Lab.

github-learning-lab

Instead of a traditional tutorial or webcast, GitHub Learning Lab is an app that gives you a learning experience you can actively participate in, without leaving GitHub. Our friendly bot will take you through a series of practical, fun labs that will give you the skills you need in no time—and share helpful feedback along the way.

Start learning

How it works

With GitHub Learning Lab, you’ll learn through issues opened by a bot in a GitHub repository. After you finish tasks, the bot will comment on your work and even review your pull requests like a project collaborator would.

If you have questions that come up while you complete a course, you can get answers in the GitHub Learning Lab Community Forum. This is a new way to get support from a community of learners and expert trainers (including members of the GitHub Training Team) as your journey progresses.

Check out the GitHub Learning Lab Community Forum

What’s covered

You’ll find five courses covering our most popular topics at launch:

Introduction to GitHub: Get an introduction to the most common, collaborative workflow for developers around the world.

Communicating using Markdown: Learn how to communicate on GitHub and beyond with Markdown’s simple syntax.

GitHub Pages: Host a website or blog directly from your GitHub repository.

Moving your project to GitHub: Get tips for migrating your code and contributors to GitHub.

Managing merge conflicts: Learn why merge conflicts happen and how to fix them.

Coming soon to GitHub Learning Lab:

Contributing to open source: Make your first open source contribution in a friendly mapping project.

What’s next

This is just the beginning. We’ll be expanding how this app helps new developers, inviting new course authors, and adding more topics as we go. Let us know what you think in the Community Forum.

Learn more about GitHub Learning Lab

Review pull requests from within Visual Studio

The GitHub for Visual Studio Extension team has been running a beta of pull request reviews from within Visual Studio for nearly a month, and we’re very excited to announce the feature has shipped this week!

Viewing, checking out, and reviewing pull requests are part of our every day workflow as GitHub users. And if you develop with Visual Studio, you no longer have to leave your editor to work in pull requests with your team.

What to expect

The most recent release of our extension supports you through these common pull request workflows:

Pull request navigation

  • Quickly view all of the pull requests on the repository you’ve cloned from Team Explorer
  • View the details of a specific pull request and checkout the pull request branch
  • See which pull request is checked out right from the status bar. If you don’t have one checked out, this button will link you back to the list of pull requests

navigation

Review code

  • Start a review from the GitHub pane within Visual Studio
  • Open the diff view of files edited within the pull request by clicking on any of the changed files
  • Leave an inline comment, and start a review from that comment
  • Submit a review that comments, approves, or request changes to the pull request

Review Code

Address feedback in Visual Studio

  • Click on a comment in the GitHub pane within Visual Studio to open it in a diff
  • View all of the reviewers for a given pull request
  • View all of the reviews that a specific reviewer has left on a pull request

address feedback

What else is in this release

This release also includes:

  • An enhancement to make navigation from diff to editor view more discoverable
  • A bug fix for GitHub Enterprise users that was causing avatars to be repeatedly downloaded
  • A fix for an initilization bug that caused MEF initialization to slow down Visual Studio extensively
  • A navigation improvement that gives users one-click access to the pull request they’re working on or the list of pull requests if they are not currently on one—even if the GitHub panel is not open
  • An update using GraphQL instead of REST

How you can help

As we continue to build on the GitHub for Visual Studio Extension, we want to know how we can best support the workflows of our users and contributors. Even if you don’t write code in Visual Studio, we’re wondering:

  1. How do you and your teammates communicate in pull requests?
  2. When in an editor, how do you use GitHub.com to: (a) Look at the list of pull requests? (b) Open a new pull request? (c) Look at the details of the pull request you are working on?
  3. When reviewing a pull request, what is important to you? For example, does it matter to you who authors a pull request?

Let us know on Twitter at @GitHubVS or head over to our tracking issue on pull request workflows to share your thoughts and help us improve our features!

Connect with us

If you haven’t already, be sure to follow us on Twitter at @GitHubVS to see what we’re up to or check out our repository and start contributing!

Newer

Subscribe

Discover new ways to build better

Try Marketplace apps free for 14 days

Learn more