From nobody Wed Jun 12 19:30:45 2024 X-Original-To: freebsd-git@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Vzwcz35DZz5NKF3 for ; Wed, 12 Jun 2024 19:30:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vzwcy4xyWz41nj for ; Wed, 12 Jun 2024 19:30:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=z+9kSFal; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::1033) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-2c2ecbc109fso146731a91.1 for ; Wed, 12 Jun 2024 12:30:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1718220657; x=1718825457; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=apqmzHiIDCQSGxVHfLfk+dxrktIIVA9Nhx3hHvtg7dQ=; b=z+9kSFalyfSuIIfluf1NN4GE6zH+N6xcoAP0T/2gr3hbJDhO+3AnLjhRqcf4jjfm9b djO4eufpnYgDICs1QjoFtqu/FsfxgHOqP7Bh5C7ACcAhqg41+4MG/GMHFIjZk6gjNITR NVmCXB/3ufxuhj8tDmVI4Pxq0PmIDT7jHj4Yi2u1cysUsVa4wcU5/6NBSxIJRlSCzbFf F4wtXCksMKfGKccgsRAkZD2kR0PdkzO9RCPSJMhbmHVDXobe1zRmjv/+9RMjhqNT9Tmw 3SYW9/lj9T1JL3/H7vYwT1A6XPwKSpn5+b0ZoRK3q3gQKPvRbBzKLPYO9HFJ8CRuX1UM gp3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718220657; x=1718825457; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=apqmzHiIDCQSGxVHfLfk+dxrktIIVA9Nhx3hHvtg7dQ=; b=SD9PmIQT+YsHsZxkOuauEc70FqOBPWwp0DynFWtfrH9x6NngDMst0yXRwkLx161Du1 j7PSujYIQdEeIze2wA/qictC/TD5Tut5slmyuVQg9R49cXtt9YtKSbQUQTvjikktZDLO VcI/xqSmTb6HVqIza11pBZ9MTYVNjk8mNsJOETlkD7wKJVOdcchCqjuXj/bMfpBet0ra p2OmjUt1LXpDtIIjrPziCFD5Lw3onZQppEOoEcl9CEARwbGHNq6q2iI0np6OaZk5ViXs 27uEn27fNcR3FvcyU3SeOQ1qqkuQmCG64pVd8/vH/k/pFcxfH+zgDVLupHXJxZlxlwab PMjA== X-Forwarded-Encrypted: i=1; AJvYcCXDO2hIn2vaHzGrLTZFZoP9gjEhIAgJCiL5vqKvRJ6/Yo6Li0liNGBI12EIlGdxNR1ZxgNIDDGKUe1TkbpATmFO94DCIbQv1A== X-Gm-Message-State: AOJu0YwDAdvRi/DzjWZ6tLo0VWDK3zPPJoczc/hEtk9PA1lDLx2DiqfA ca3vbyWUGDHHlc/uPDY1o1V17/OLoXdpo6YtcHWT0vnYcjTtNRo3GaNl0XXd8+RiO8lJw11wE1m 8JvWCRAHWk7ixOM/4R0fH5+MnZEG2BYvSRHfBMw== X-Google-Smtp-Source: AGHT+IF4Zk7Yoc5AMIxkw/XpR5DMsIj65K3463iInbWufn5NMXVI9LFRZar8yAKK7fjKxSaff/45ZIztUQU93mT1sS4= X-Received: by 2002:a17:90a:ea87:b0:2c3:1234:8bc0 with SMTP id 98e67ed59e1d1-2c4a771381bmr2612782a91.46.1718220656583; Wed, 12 Jun 2024 12:30:56 -0700 (PDT) List-Id: Discussion of git use in the FreeBSD project List-Archive: https://lists.freebsd.org/archives/freebsd-git List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-git@FreeBSD.org MIME-Version: 1.0 From: Warner Losh Date: Wed, 12 Jun 2024 13:30:45 -0600 Message-ID: Subject: github automation working group To: FreeBSD Hackers , freebsd-git Content-Type: multipart/alternative; boundary="000000000000e1c274061ab66b26" X-Spamd-Bar: / X-Spamd-Result: default: False [0.80 / 15.00]; SEM_URIBL(3.50)[discord.gg:url]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; BAD_REP_POLICIES(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1033:from]; ARC_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[bsdimp.com]; MLMMJ_DEST(0.00)[freebsd-git@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; R_DKIM_ALLOW(0.00)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-git@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4Vzwcy4xyWz41nj --000000000000e1c274061ab66b26 Content-Type: text/plain; charset="UTF-8" Greetings! I'd like to announce the formation of a github automation working group. The goals of this working group are two fold: 1. To improve the automation we use to move pull requests into the tree, including testing (and possibly phabricator and bz improvements as well, though that's follow on work). This will likely include batching of pull requests so we can run more extensive tests on the batch than we could on any individual one. 2. Improve the github experience for contributors that are using github pull requests. This will include things like checklists, automatic jobs that run to critique bits of the pull request and tooling to help the volunteers landing the pull requests in tracking the state and readiness, etc. 3. Grab-bag of whatever else makes it easier to contribute to FreeBSD. We'll be using two forums to communicate. First, for announcements and more structured discussions, we'll use the freebsd-git@freebsd.org mailing list. For the ephemeral communications, that will be on our discord server ( https://discord.gg/freebsd for invite) in the #github-hacking channel. I'm open to other forums that match the participants' needs, but this is where we're going to start. We'll also use a github repo to track the scripts we're creating and improving, as well as a useful place to have in-progress documentation in asciidoc format to merge into the handbook when it's ready. If it makes sense, we'll have VC meetings, but for now I'm not planning on one (though I am open to changing that if people think it would be useful). Please let me know if you are interested. All the latest data can be found on the wiki page https://wiki.freebsd.org/WorkingGroup/Github which will have pointers to all the things relevant. Warner P.S. I know this is a little different. I tried to do the 'git next steps' working group and that failed because its mandate was too big and I couldn't get people to join who wanted to commit to work. So, I've scaled back on the goals and am trying a new way to encourage people to collaborate. It's partially an experiment, and partially a guess that the people who can help the most will already have a discord account. --000000000000e1c274061ab66b26 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Greetings!

I'd like to announce the= formation of a github automation working group. The goals of this working = group are two fold:

1. To improve the automation w= e use to move pull requests into the tree, including testing (and possibly = phabricator and bz improvements as well, though that's follow on=C2=A0w= ork). This will likely include batching of pull requests so we can run more= extensive tests on the batch than we could on any individual=C2=A0one.
2. Improve the github experience for contributors that are using git= hub pull requests. This will include things like checklists, automatic jobs= that run to critique bits of the pull request and tooling to help the volu= nteers landing the pull requests in tracking the state and readiness, etc.<= /div>
3. Grab-bag of whatever else makes it easier to contribute to Fre= eBSD.

We'll be using two forums to communicate= . First, for announcements and more structured discussions, we'll use t= he freebsd-git@freebsd.org m= ailing list. For the ephemeral communications, that will be on our discord = server (https://discord.gg/freebsd for invite) in the #github-hacking channel. I'm open to other forums= that match the participants' needs, but this is where we're going = to start. We'll also use a github repo to track the scripts we're c= reating and improving, as well as a useful place to have in-progress docume= ntation in asciidoc format to merge into the handbook when it's ready.<= /div>

If it makes sense, we'll have VC meetings, but= for now I'm not planning on one (though I am open to changing that if = people think it would be useful).

Please let me kn= ow if you are interested.


Warner

P.S. I know this is a little different. I tried to do= the 'git next steps' working group and that failed because its man= date was too big and I couldn't get people to join who wanted to commit= to work. So, I've scaled back on the goals and am trying a new way to = encourage people to collaborate. It's partially an experiment, and part= ially a guess that the people who can help the most will already have a dis= cord account.
--000000000000e1c274061ab66b26--