From nobody Tue Jan 31 22:03:28 2023 X-Original-To: freebsd-current@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 4P5zZx2BPZz3cR1T for ; Tue, 31 Jan 2023 22:03:37 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.evolve.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5zZw4c2lz3rsq; Tue, 31 Jan 2023 22:03:36 +0000 (UTC) (envelope-from grembo@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 7925f828; Tue, 31 Jan 2023 22:03:28 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 74fb6f0d (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Tue, 31 Jan 2023 22:03:28 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: Tooling Integration and Developer Experience From: Michael Gmelin In-Reply-To: Date: Tue, 31 Jan 2023 23:03:28 +0100 Cc: User Ngor , freebsd-current@freebsd.org Message-Id: References: To: Kurt Jaeger X-Mailer: iPhone Mail (20B110) X-Rspamd-Queue-Id: 4P5zZw4c2lz3rsq X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 31. Jan 2023, at 22:44, Kurt Jaeger wrote: >=20 > =EF=BB=BFHi! >=20 >>>> This can be as easy as moving everything into Phabricator. >>> There's the issue that Phabricator itself is no longer supported >>> upstream: > [...] >>> https://we.phorge.it/ >=20 >> Should be no harder than regular update. They even have a HOWTO >> https://we.phorge.it/w/installation_and_setup/update_from_phabricator/ >=20 > So, as a step 0 we would need a phorge port... >> 1. Upgrade to Phorge >> 2. Setup Maniphest for bugs and tasks >> 3. Migrate bugs into Maniphest >> 4. Enable Harbormaster (Build/CI) - this requires coordination with >> whoever is working on pre-commit CI. > [...] >> Infra operations are hard, and I have experience with it. I'd be happy to= >> help. >=20 > Do you think you can provide a phorge port ? >=20 I created the phabricator port in 2014 and have been maintaining it since th= en. I=E2=80=99m also subscribed to phorge, so technically I could also maint= ain a phorge port (I also have many years of experience in maintaining and u= sing phabricator instances, also fixing bugs and adding some local features)= . So far I haven=E2=80=99t created a port for phorge, as progress on it seemed= very slow (and many of the changes were also merged into phab) and therefor= e there was little incentive to migrate any of the instances I maintain. AFAIK FreeBSD=E2=80=99s phabricator instance is not based on the port and us= es custom patches anyway (I can=E2=80=99t remember having a single communica= tion with phabricator-admin regarding the port), therefore having a phorge p= ort most likely isn=E2=80=99t a pre-condition for the project to use it. Best=20 > --=20 > pi@opsec.eu +49 171 3101372 Now what ? >=20