Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #7720

Re: Python Policy

Path csiph.com!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod
From Piotr Ożarowski <piotr@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Python Policy
Date Tue, 20 Oct 2015 17:20:02 +0200
Message-ID <qlGRI-7xO-19@gated-at.bofh.it> (permalink)
References <qlmzE-2TP-23@gated-at.bofh.it> <qlqae-8it-37@gated-at.bofh.it> <qlG5k-6l5-35@gated-at.bofh.it>
X-Original-To debian-python@lists.debian.org
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Oct 20 15:17:10 2015
Old-Return-Path <piotr@ozarowski.pl>
X-Amavis-Spam-Status No, score=-6.399 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, CAPINIT=0.5, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate:hard: -6.1
Mail-Followup-To debian-python@lists.debian.org
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
X-Operating-System Debian GNU/Linux (3.16.0-4-amd64)
User-Agent Mutt/1.5.23 (2014-03-12)
X-Mailing-List <debian-python@lists.debian.org> archive/latest/13032
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20151020151649.GR15907@sar0.p1otr.com
Approved robomod@news.nic.it
Lines 38
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Tue, 20 Oct 2015 17:16:49 +0200
X-Original-Message-ID <20151020151649.GR15907@sar0.p1otr.com>
X-Original-References <20151019133137.6174ef07@limelight.wooz.org> <20151019212639.GF3846@p1otr.com> <20151020102017.343f3443@limelight.wooz.org>
Xref csiph.com linux.debian.maint.python:7720

Show key headers only | View raw


[Barry Warsaw, 2015-10-20]
> Here's my concern: I don't want too much duplication of information in
> multiple locations.  That's a sure recipe for bitrot, and I know no one wants
> to have to edit information in more than one place.
> 
> Until now, the wiki has been the more convenient place to make these changes,
> but I agree in principle with your opinion that some of that information must
> be captured in policy.  So here's what I suggest.
> 
> For standards we must all adhere to, such as branch and tag names, source-full
> branches, the use of git-dpm, and maybe a few other points, these should go in
> policy.rst.
> 
> The wiki page points to the policy document but doesn't otherwise describe
> those details.  That way, there's only one place to change when/if these
> standards change.
> 
> The wiki then goes on to describe common workflows, how to create new
> repositories, mr, etc.  These aren't specifically policy related but are
> mostly there to help developers get started, or handle tricky situations.
> 
> If you're in agreement with that split, I'll update both the policy and wiki.

if policy describes f.e. tag name convention and our tools create
correct configuration out of the box, then there's no need to mention it
on the wiki so yes, I agree with what you said. I don't even mind to
list only few things in policy now and extend it later, once we figure
out whats best for us (and work on wiki only for now), but at some point
I want a set of rules (a "standard"!) that will make my life as sponsor
easier and this is F*****G important for me. I will leave this team the
moment I have to read README.sources each day when I sponsor a package.
If you want help from me, make it easier for me to review your work.

(most of RFS emails I get contain "RFS: DPMT: foo version" subject and
nothing else, it works for me, I'm lazy and I prefer to read
non-technical books rather than RFS mails :P)
-- 
evil general Piotr

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Python Policy Barry Warsaw <barry@debian.org> - 2015-10-19 19:40 +0200
  Re: Python Policy Scott Kitterman <debian@kitterman.com> - 2015-10-19 20:50 +0200
  Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:10 +0200
    Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:30 +0200
      Re: Python Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-19 21:40 +0200
        Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:50 +0200
    Re: Python Policy Brian May <bam@debian.org> - 2015-10-20 00:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 00:40 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:50 +0200
          Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:10 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:40 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:00 +0200
  Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 23:30 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 22:20 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 23:00 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-20 23:10 +0200
        Re: Python Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-21 02:20 +0200
          Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 02:50 +0200
          Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-21 10:00 +0200
            Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 16:00 +0200
              Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:30 +0200
                Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-22 11:40 +0200
                Re: DPMT Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 12:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 23:40 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 03:00 +0200
          Re: Python Policy Vincent Bernat <bernat@debian.org> - 2015-10-21 10:40 +0200
            Re: Python Policy Brian May <brian@microcomaustralia.com.au> - 2015-10-21 11:50 +0200
              PyPI wheels (was Re: Python Policy) Barry Warsaw <barry@debian.org> - 2015-10-21 16:00 +0200
                Re: PyPI wheels (was Re: Python Policy) Ian Cordasco <graffatcolmingov@gmail.com> - 2015-10-21 16:50 +0200
                Re: PyPI wheels (was Re: Python Policy) Jeremy Stanley <fungi@yuggoth.org> - 2015-10-21 17:50 +0200
            Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 15:50 +0200
          Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-21 14:10 +0200
            Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-21 15:50 +0200
              Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-21 16:20 +0200
                Re: DPMT Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-21 23:40 +0200
                Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-22 01:00 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-23 01:40 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-23 01:40 +0200
  Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 00:00 +0200
    Re: DPMT Policy Brian May <bam@debian.org> - 2015-10-20 00:30 +0200
    Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:10 +0200
      Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:10 +0200
        Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 23:40 +0200
  Re: Python Policy Brian May <bam@debian.org> - 2015-10-20 00:00 +0200

csiph-web