speaker

• Mr. Yu Kaneshiro, NTT Advanced Technology
• Mr. Shota Kondo, Internet Initiative Japan Inc.
• Macnica Networks Corp. Kayo Hirota

At the "Developers Summit 2016" held at Meguro Gajoen on February 19, 2016 (Friday), "User companies talk about what is a software development environment that improves productivity and quality to support team development? I gave a lecture titled,

First of all, our company, Macnica networks, introduced GitHub Enterprise. Before the introduction, we asked the attendees at the venue about their awareness of GitHub, and found that 60-70% of them knew about GitHub.com (hereinafter referred to as GitHub) or GitHub Japan. Only 10-20% of respondents knew about GitHub Enterprise. We need to raise awareness of GitHub Enterprise even more! I felt this keenly.

To give you a brief introduction of our company, GitHub Japan was established in June 2015, and Macnica networks signed a contract with us as the sole distributor in Japan. Since then, we have been working with GitHub Japan to provide implementation and technical support to Japanese customers.

GitHub is a service for sharing and publishing code. A certain user commented, "We are moving from 'using GitHub is convenient' to 'not using GitHub is outdated'." We have received comments such as "I'm using it" and "It's a tool that makes development more fun."

GitHub was founded in 2008 and started its service. Designed as a “platform for developers by developers”, it supports software development worldwide. In 2008, it started as a web service that hosts Git repositories and connects developers. Released a function to manage . In 2012, we received requests from many companies that they wanted to use GitHub, which is widely used for open source, in their business, but it was difficult to store the code outside the company, so we released GitHub Enterprise, which can be managed on-premises. This is a paid service that can be placed inside your own firewall or placed in a cloud environment such as Azure or AWS that you manage yourself.

Regarding the scope of adoption of GitHub, almost all open source projects are developed on GitHub, and it has spread to companies, local governments, and universities in all industries as a software development platform.

GitHub is designed based on the vision that "if there is an environment where developers can develop with the correct workflow, more and more wonderful software development will be possible", making your software development more enjoyable, productive and efficient Our goal is to do. Today, I would like to introduce three points necessary to achieve this.

The first is that it is possible to build a process in which not only individual developers but also various stakeholders can participate. Submit issues, write code, discuss, review, and more, all in one place. GitHub is a platform that allows everyone to communicate in the same place, including quality-related personnel and intellectual property-related legal personnel. Second, it also serves as an integrated platform for development. Of course, issue management and version management can be integrated with other development tools such as testing and development, so efficiency can be improved by linking with various subsystems with GitHub at the core. The third is GitHub Flow, a workflow invented by GitHub. With GitHub Flow, anyone can easily create their own branch that they can modify themselves, so parallel development can be done without affecting the master branch or mixing work with other developers. can. Anything you develop on your own branch can be shown and suggested to other developers before merging into the master branch. While asking for opinions on the content, such as whether it is not deviated from the specification, we repeatedly discuss, code review, and modify it to determine whether it conforms to the specification, and if it is good, submit a request to incorporate it into the main branch (pull request function) can do. GitHub's greatest value is here! We believe that this workflow has greatly changed team development and is one of the reasons why the number of users continues to grow exponentially. In summary, the act of creating a branch is A place to formulate and verify hypotheses and the act of making a pull request is a place to discuss and draw conclusions and the act of merging and deploying is accepted or rejected because it does not meet the specifications. has become This simple and powerful flow is used in software development all over the world.

Now, let's move on to the customer's actual session on how the development environment has changed and why it was introduced.