Date: Wed, 12 Jun 2024 13:30:45 -0600 From: Warner Losh <imp@bsdimp.com> To: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-git <freebsd-git@freebsd.org> Subject: github automation working group Message-ID: <CANCZdfr2aoQ4U3JSsm4XcMJ4tgoaAimvJWS_Oy9emh=z=JRFTg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--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 <div dir=3D"ltr">Greetings!<div><br></div><div>I'd like to announce the= formation of a github automation working group. The goals of this working = group are two fold:</div><div><br></div><div>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.</di= v><div>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><div>3. Grab-bag of whatever else makes it easier to contribute to Fre= eBSD.</div><div><br></div><div>We'll be using two forums to communicate= . First, for announcements and more structured discussions, we'll use t= he <a href=3D"mailto:freebsd-git@freebsd.org">freebsd-git@freebsd.org</a> m= ailing list. For the ephemeral communications, that will be on our discord = server (<a href=3D"https://discord.gg/freebsd">https://discord.gg/freebsd</= a> 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><div><br></div><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).</div><div><br></div><div>Please let me kn= ow if you are interested.</div><div><br></div><div>All the latest data can = be found on the wiki page=C2=A0<a href=3D"https://wiki.freebsd.org/WorkingG= roup/Github">https://wiki.freebsd.org/WorkingGroup/Github</a>; which will ha= ve pointers to all the things relevant.</div><div><br></div><div>Warner</di= v><div><br></div><div>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.</div></div> --000000000000e1c274061ab66b26--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr2aoQ4U3JSsm4XcMJ4tgoaAimvJWS_Oy9emh=z=JRFTg>