Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.unit0.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Mattia Rizzolo Newsgroups: linux.debian.maint.python Subject: Re: What is the process to update the DPMT and PAPT policies? Date: Mon, 16 Sep 2019 10:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Sep 16 07:55:24 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.633 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.015, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-ot1-f50.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/CeSIDfoEf8eH2KTrEEEYtCvkzv01kotLnjkkN0NCw4=; b=ptn5No17MsAFppzPK+JMdDQbJia98Qqp5INe6mjd6s1O3mX/SbJg6K50GV61PtzYx5 r1GC91LMV2TgLF559vetJ0TKJGVz/e3tnGTaVTGvwNSE3IOJTp7XzwB+2sYHc82ScGKd C9kxY3yjsAO5Im+FUbCoBn9gaPGEjCIvF95EXJljaih9HrZprRdfqv689RELX3cGayQM YUvGzUCjNGMeSgC/9RW2ERB2/zv72zwxApiXwO8j/IrcA3AmQCJUR3dXfXMif7WQda6K vWbWZBaMUkBnFg+m+b/TXki4NqTiI5zn0aPDw9CQzo8W4BGCmeKl054Z9/lfbLG6hySi iLpw== X-Gm-Message-State: APjAAAV6uTMG+9RO+N2N80PDZbm2UZFheVHiU3gY5BWwd3l1TFLTpR73 18h/5K7AYD4Y1FbXvI2QTf2CDPFEeeo= X-Google-SMTP-Source: APXvYqxNK87g8E+iHsmAvSRfkxqx9BLQf4AqopcFUKb76Zft5ANA4HrLi4ouaM/5vduikaoj/UZlKw== X-Received: by 2002:a9d:d28:: with SMTP id 37mr14004743oti.279.1568620508768; Mon, 16 Sep 2019 00:55:08 -0700 (PDT) X-Received: by 2002:a9d:4597:: with SMTP id x23mr32143981ote.185.1568620508370; Mon, 16 Sep 2019 00:55:08 -0700 (PDT) MIME-Version: 1.0 X-Gmail-Original-Message-ID: Content-Type: multipart/alternative; boundary="000000000000305cd30592a6eca5" X-Mailing-List: archive/latest/17359 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAHKYmevR86dtSWxKBBeBReK_uBrRE4QsSMAZpmiFXRnTo1yLVw@mail.gmail.com Approved: robomod@news.nic.it Lines: 54 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 16 Sep 2019 09:54:56 +0200 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:11823 --000000000000305cd30592a6eca5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Mon, 16 Sep 2019, 1:59 am Louis-Philippe V=C3=A9ronneau, wrote: > What is the process to update the DPMT and PAPT policies? I feel the > DPMT policy is pretty good and I feel the PAPT policy could copy a bunch > of stuff from there. > I wonder, I think the historical reasons for papt and dpmt to be separated don't quite stand anymore. Perhaps the only difference left is the actual technical difference between an application and a module as described in the python policy (rather in the team one). Could this be a good moment to make the two policies totally converge, and actually merge them into a single "python team policy"? Perhaps in a near-ish future the two "sub-"teams could even be merged? > > --000000000000305cd30592a6eca5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Mon, 16 Sep 2019, 1:59 am Louis-Philippe V=C3=A9= ronneau, <pollo@debian.org> w= rote:
What is the process to update the DPMT and PAPT policies? I feel the
DPMT policy is pretty good and I feel the PAPT policy could copy a bunch of stuff from there.

I wonder, I think the historical reasons for papt and d= pmt to be separated don't quite stand anymore.=C2=A0 Perhaps the only d= ifference left is the actual technical difference between an application an= d a module as described in the python policy (rather in the team one).

Could this be a good moment = to make the two policies totally converge, and actually merge them into a s= ingle "python team policy"?

Perhaps in a near-ish future the two "sub-"teams co= uld even be merged?

--000000000000305cd30592a6eca5--