X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mr21p30im-asmtp003.me.com (mr21p30im-asmtp003.me.com [17.111.174.66]) by lists.alpinelinux.org (Postfix) with ESMTP id E97495C52BD for ; Mon, 16 Jul 2018 09:09:09 +0000 (GMT) Received: from process-dkim-sign-daemon.mr21p30im-asmtp003.me.com by mr21p30im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0PBY00D00C2JJO00@mr21p30im-asmtp003.me.com> for alpine-devel@lists.alpinelinux.org; Mon, 16 Jul 2018 09:09:09 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1531732149; bh=PJ/rA1C838NeL0WMgMbZdVR7u5Xjpo7wR+nVGTjgCQg=; h=From:Content-type:MIME-version:Subject:Message-id:Date:To; b=MjgoxFNnCZJkjIZ5RamyaFblAHqTNk5BPMCOIoTxdxjWwnFsrLeCQOvnGHvB48E52 P4tNKigxO/iZkjnrtH6yxMGjjSR7x0AEQlR2FezMSXRTvsoLqGX8X5FwCvBmk+5DA/ O0jfCeYqj+7QAmdNSLz/pLPItrqTdLPxncZKzgex1cRv3ZfSZZ+mqD0gffNKq6VZgq /LdZiuoGPLdofFw5LOPV5OxpD0CiQhcWPFVU1nllpIPxYjE2iJbzMmCoeu5AmrGehQ r5VFtWP41NXJklwyPU+2AAzLNGRedw7Co9cVfJz3yxfFH49fCJOITaY0kbbWjRx9UY 4V0b/XDARyHJg== Received: from icloud.com ([127.0.0.1]) by mr21p30im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0PBY00OJ2C2WMO30@mr21p30im-asmtp003.me.com> for alpine-devel@lists.alpinelinux.org; Mon, 16 Jul 2018 09:09:07 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-07-16_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1807160110 From: Chris Ely Content-type: multipart/alternative; boundary="Apple-Mail=_A067F5BE-AA14-42DA-B30E-1EC3BB6924ED" X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: [alpine-devel] GitHub aports automation improvements Message-id: <6650E9AE-89D8-4BBF-96B3-AFC54C90CDAD@icloud.com> Date: Mon, 16 Jul 2018 05:08:56 -0400 To: alpine-devel@lists.alpinelinux.org X-Mailer: Apple Mail (2.3445.8.2) --Apple-Mail=_A067F5BE-AA14-42DA-B30E-1EC3BB6924ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello, To help address the backlog of PRs on the aports repository I'm = suggesting more automation to make things easier all around. 1. https://probot.github.io/apps/invite-contributors/ = Configuration: .github/invite-contributors.yml isOutside: true 2. https://github.com/zalando/zappr Configuration: .zappr.yaml approvals: minimum: 3 from: collaborators: true orgs: - alpinelinux pattern: "^(:\\+1:|=F0=9F=91=8D)$" veto: pattern: "^(:\\-1:|=F0=9F=91=8E)$" 3. https://probot.github.io/apps/dep/ = 4. https://probot.github.io/apps/wip/ = 5. = https://zapier.com/apps/github/integrations/mattermost/13208/post-new-gith= ub = Also, since the master branch is being managed external to GitHub, I'd = suggest protecting that branch and making a new one (e.g. github) that = can be used to quickly merge the PRs to. This will allow simple use of = the GitHub web interface to merge PRs using squash / rebase / merge = commits to that branch from which you can move those commits to master = in your external repository. You could do this with patch sets or setup = github as a remote or some other preferred way. The idea behind this workflow is that contributors get invited after = their first contribution and from that point on can help with merging = new PRs into the github branch but would not be able to change the = master branch (as that's hosted external to GitHub and protected). This = way you can get a pool of contributors helping out with simple changes = and give the developers a single source to find the changes that have = been community approved. Thoughts?= --Apple-Mail=_A067F5BE-AA14-42DA-B30E-1EC3BB6924ED Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hello,

To help address the backlog of PRs on the aports repository = I'm suggesting more automation to make things easier all = around.

 1. https://probot.github.io/apps/invite-contributors/
= Configuration: .github/invite-contributors.yml
= isOutside: true

 2. https://github.com/zalando/zappr
= Configuration: .zappr.yaml
= approvals:
  minimum: = 3
  from:
=     collaborators: true
=     orgs:
=       - alpinelinux
=   pattern: "^(:\\+1:|=F0=9F=91=8D)$"
=   veto:
    = pattern: "^(:\\-1:|=F0=9F=91=8E)$"

 3. https://probot.github.io/apps/dep/
 4. https://probot.github.io/apps/wip/
 5. https://zapier.com/apps/github/integrations/mattermost/13208/po= st-new-github

Also, since the master branch is being managed external to = GitHub, I'd suggest protecting that branch and making a new one (e.g. = github) that can be used to quickly merge the PRs to. This will allow = simple use of the GitHub web interface to merge PRs using squash / = rebase / merge commits to that branch from which you can move those = commits to master in your external repository. You could do this with = patch sets or setup github as a remote or some other preferred = way.

The idea = behind this workflow is that contributors get invited after their first = contribution and from that point on can help with merging new PRs into = the github branch but would not be able to change the master branch (as = that's hosted external to GitHub and protected). This way you can get a = pool of contributors helping out with simple changes and give the = developers a single source to find the changes that have been community = approved.

Thoughts?
= --Apple-Mail=_A067F5BE-AA14-42DA-B30E-1EC3BB6924ED-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---