Re: Python Policy

Thanks for the feedback Piotr. I've made all the changes you suggest, except one. I'll discuss that below and include an updated diff against master. On Oct 19, 2015, at 11:26 PM, Piotr Ożarowski wrote: >I'm against this change. If we want all team packages to follow some >rules, these rules

Re: Python Policy

On Oct 20, 2015, at 12:37 AM, Piotr Ożarowski wrote: >should we also document that we're not OpenStack Packaging Team? Or zope-packaging? . Agreed that there are different teams here, but I am hoping that we can do some consolidation. E.g. I posted on the zope list that I'd like to pull those

Re: Python Policy

[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

Re: DPMT Policy

> > >> Is policy.rst automatically kept in sync somehow in between > > >> python-modules.git and http://python-modules.alioth.debian.org/? > > > > > >no, I do it by hand (any other team member can do it as well). > > > > How? > > scp policy.rst alioth:dpmt_home/public_html rst2html policy.rst >

Re: Python Policy

Latest diff against master. If you're happy with this, I'll merge to master, update the web page, and trim the wiki. Cheers, -Barry diff --git a/policy.rst b/policy.rst index c09f03a..123792c 100644 --- a/policy.rst +++ b/policy.rst @@ -1,39 +1,44 @@ - -

Re: Python Policy

thanks a lot for preparing all this. On 10/20/2015 10:53 PM, Barry Warsaw wrote: > +DPMT requires upstream tarballs; releases cannot be made from upstream git > +repositories directly. This is because PyPI contains upstream tarballs, and > +tarballs are what we upload to the Debian archive. i

Re: Python Policy

On Oct 20, 2015, at 05:16 PM, Piotr Ożarowski wrote: >I will leave this team the moment I have to read README.sources each day when >I sponsor a package. Nobody wants that! (either you leaving or having to read README.source for every package). Cheers, -Barry

Re: Python Policy

[Barry Warsaw, 2015-10-20] > Latest diff against master. If you're happy with this, I'll merge to master, > update the web page, and trim the wiki. I have few comments, but even if I didn't, please wait at least until after the weekend (or better: 7 days) so that others have time to review it

Re: Python Policy

[Barry Warsaw, 2015-10-20] > On Oct 19, 2015, at 09:04 PM, Piotr Ożarowski wrote: > > >Debian Python Policy¹ is something every single packages that extends > >Python should follow. There are many teams (more than 4) each of them > >can have their own policy that extends DPP. > > This is an

Re: Python Policy

[Barry Warsaw, 2015-10-20] > I also think it would be fine to *eventually* merge the two teams. I suspect > there isn't really much benefit to keeping them separate and a lot of > unnecessary cost. Is there anybody on PAPT who doesn't want to be on DPMT? /me puts his PAPT admin hat on WHAT?

Re: DPMT Policy

> >> Is policy.rst automatically kept in sync somehow in between > >> python-modules.git and http://python-modules.alioth.debian.org/? > > > >no, I do it by hand (any other team member can do it as well). > > How? scp policy.rst alioth:dpmt_home/public_html -- Piotr Ożarowski

Re: Python Policy

On Oct 21, 2015, at 11:17 AM, Ben Finney wrote: >On the contrary, I think the Policy document should document the >rationale for contingent decisions like this. When it is inevitably >discussed again in the future, it is always better to know the intent of >the authors. +1 Cheers, -Barry

Re: Python Policy

On Oct 20, 2015, at 11:30 PM, Piotr Ożarowski wrote: >I have few comments, but even if I didn't, please wait at least until after >the weekend (or better: 7 days) so that others have time to review it and >comment / propose changes. Fair enough. Of course, it's in a vcs so it's easy to change!

Re: Python Policy

"IOhannes m zmölnig (Debian/GNU)" writes: > thanks a lot for preparing all this. > > On 10/20/2015 10:53 PM, Barry Warsaw wrote: > > +DPMT requires upstream tarballs; releases cannot be made from upstream git > > +repositories directly. This is because PyPI contains