From nobody Wed Oct 18 09:08:04 2023
X-Original-To: freebsd-python@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 4S9Q454VQDz4xkSR;
	Wed, 18 Oct 2023 09:08:05 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4S9Q453w4Qz3dwM;
	Wed, 18 Oct 2023 09:08:05 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Authentication-Results: mx1.freebsd.org;
	none
Received: from pi by fc.opsec.eu with local (Exim 4.96.2 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1qt2X6-000CX2-0f;
	Wed, 18 Oct 2023 11:08:04 +0200
Date: Wed, 18 Oct 2023 11:08:04 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Pat Maddox <pat@patmaddox.com>
Cc: freebsd-python@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: Seeking guidance on submitting several new Python-based ports
Message-ID: <ZS-gdO5ZTdivqSnm@fc.opsec.eu>
References: <02ef0f84-d0a8-43e0-a726-8eee263de515@app.fastmail.com>
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-python
List-Help: <mailto:python+help@freebsd.org>
List-Post: <mailto:python@freebsd.org>
List-Subscribe: <mailto:python+subscribe@freebsd.org>
List-Unsubscribe: <mailto:python+unsubscribe@freebsd.org>
Sender: owner-freebsd-python@freebsd.org
X-BeenThere: freebsd-python@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <02ef0f84-d0a8-43e0-a726-8eee263de515@app.fastmail.com>
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-Rspamd-Queue-Id: 4S9Q453w4Qz3dwM

Hi!

> Is it reasonable to submit several ports as part of one PR?
> For my purposes, there are a handful of "leaf" ports:
[...]
> So on one extreme, I have to submit each port, one-at-a-time,
> in order. On the other extreme, I submit all 12 in one PR.
> 
> How should I go about submitting these new ports?

If you add one port per PR and set the proper dependencies in each PR,
it's easy for several committers to work on those ports.

> Also, should I stay as the maintainer, or should I change them
> to python@freebsd.org because they are Python ports?

For the beginning, it's probably best if you stay maintainer, because
you understand best when a port can be upgraded so that it does not interfere
with the main application.

This can otherwise become a problem (see gitlab-ce and the python
ports it depends on).

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?