From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id D155412A8 for ; Wed, 6 May 2015 12:11:45 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 06 May 2015 03:11:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,379,1427785200"; d="scan'208";a="706015997" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga001.fm.intel.com with ESMTP; 06 May 2015 03:11:44 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.76]) by IRSMSX107.ger.corp.intel.com ([169.254.10.215]) with mapi id 14.03.0224.002; Wed, 6 May 2015 11:11:43 +0100 From: "Mcnamara, John" To: "dev@dpdk.org" Thread-Topic: GitHub sandbox for the DPDK community Thread-Index: AQHQhCdlg1RCyqklQ0KpSAVz9bdNYJ1uv4kg Date: Wed, 6 May 2015 10:11:42 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 10:11:46 -0000 Hi, It is always difficult to sell change unless there is a majority in favour of it. If the project was already on GitHub and someone was proposing to move to a ML/Patch workflow then we would probably see as much resistance. Here are some advantages and disadvantage of GitHub from personal experience of working with projects that were exclusively hosted there. Some advantages of GitHub: * Integrated bug tracker with #num linking of commits to issues and issues to commits. * Inline code reviews of pull requests (PR)s. * Patches can be viewed in the context of the surrounding code. * Ability to tag issues/PRs with tags like "Bug", "Documentation" and to add them to milestones. This give a project level view of the current state of issues/PRs. * Easy integration and automatic updating with third party tools like ReadTheDocs, TravisCI and Coverity. This makes it very easy to setup a continuous integration environment. Personally, I find the third party tool integration the most compelling feature. It allows you to configure the tools to work with updates to the repo rather than configuring the repo (via hooks) to work with the tools. The issue tracker integration is also very useful. These features aren't exclusive to GitHub and we could probably replicate the useful ones into our current workflow (issue tracking in particular is missing). The advantage that GitHub has is that these features are already there and fully integrated. Some disadvantages of using GitHub: * Issue/PR discussions aren't threaded and in long discussions it can be a little unclear who is replying to whom/what. * If there are a lot of forks with PRs the network tree becomes too big and GitHub doesn't display it. * The fork/PR workflow with rebasing, squashing and "push --force" on branches is probably a significant change to most people's workflow. John. --=20