Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Mon, Jun 19, 2017 at 10:41:54AM -0300, Antonio Terceiro wrote: > I would imagine that any PR workflow would allow anyone to add a comment > saying they have reviewed the changes and they look good, withing the > same "place" where the maintainer is already looking at. Indeed, but it would be

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On 06/19/2017 05:37 PM, Sean Whitton wrote: > On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote: >> On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton >> wrote: >>> Someone might contribute a fix in the form of a PR, and an uploader of >>> the package might review

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Monday, June 19, 2017 04:37:12 PM Sean Whitton wrote: > Hello Jeremy, > > On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote: > > On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton wrote: > > > Someone might contribute a fix in the form of a PR, and an uploader

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Hello Jeremy, On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote: > On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton > wrote: > > Someone might contribute a fix in the form of a PR, and an uploader of > > the package might review that fix and determine that it

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Mon, Jun 19, 2017 at 10:18:52AM +0100, Sean Whitton wrote: > Hello Christian, > > On Sun, Jun 11, 2017 at 08:16:43PM +0100, Sean Whitton wrote: > > Christian Seiler writes: > > > > > Your goal in wanting to stop people from having to deal with > > > patch files manually

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton wrote: > Someone might contribute a fix in the form of a PR, and an uploader of > the package might review that fix and determine that it should be > merged. They then look at the master branch and decide that it should >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Hello Christian, On Sun, Jun 11, 2017 at 08:16:43PM +0100, Sean Whitton wrote: > Christian Seiler writes: > > > Your goal in wanting to stop people from having to deal with > > patch files manually is laudable, but I see the following way > > forward to achieve that goal: >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Christian Seiler writes: > Your goal in wanting to stop people from having to deal with > patch files manually is laudable, but I see the following way > forward to achieve that goal: > > - Pull requests. > > - Make it easier to create personal copies of remote (!) >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Christian Seiler writes: > Your goal in wanting to stop people from having to deal with > patch files manually is laudable, but I see the following way > forward to achieve that goal: > > - Pull requests. > > - Make it easier to create personal copies of remote (!) >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Sun, 11 Jun 2017, Sean Whitton wrote: > Henrique de Moraes Holschuh writes: > > > Not just that. If it is for NMUs, one also has to ensure it matches > > what got uploaded (regardless of method: NMU patch, PR, branch...). > > I'm not sure what you're getting at here -- this

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On 06/11/2017 07:44 PM, Sean Whitton wrote: > Christian Seiler writes: > >> To me this looks like a very complicated technical solution >> to something that I've never encountered as a problem myself. > > Could you explain which parts of the proposal you find to be "very >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Christian Seiler writes: > To me this looks like a very complicated technical solution > to something that I've never encountered as a problem myself. Could you explain which parts of the proposal you find to be "very complicated"? Possibly I've made them seem much more

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Ansgar Burchardt writes: > What about contributions to non-packaged parts of Debian? This DEP isn't about those -- are you saying that it ought to be extended? > I also don't like having more systems only a subset of contributors > can use. I share this concern, but it is

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Henrique de Moraes Holschuh writes: > Not just that. If it is for NMUs, one also has to ensure it matches > what got uploaded (regardless of method: NMU patch, PR, branch...). I'm not sure what you're getting at here -- this DEP is for changes that *aren't* to be uploaded as

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Fri, 09 Jun 2017, Tollef Fog Heen wrote: > > Per the DEP: > > > > > it is very useful for a maintainer to know that a change has been > > > approved by someone who has been trusted by the project with the > > > technical ability to NMU the package > > > > This would be much more cumbersome to

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

]] Sean Whitton > Per the DEP: > > > it is very useful for a maintainer to know that a change has been > > approved by someone who has been trusted by the project with the > > technical ability to NMU the package > > This would be much more cumbersome to achieve with PRs. I'm not sure why

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Hi Sean, Am 2017-06-07 22:56, schrieb Sean Whitton: I am hereby reserving DEP number 15 for my draft DEP, "Reserved namespaces for DD-approved non-maintainer changes". I'd like to suggest discussing this DEP on d-devel (which is the Reply-to for this e-mail). The canonical DEP text is at

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Sean Whitton writes: > I am hereby reserving DEP number 15 for my draft DEP, "Reserved > namespaces for DD-approved non-maintainer changes". > > I'd like to suggest discussing this DEP on d-devel (which is the > Reply-to for this e-mail). The canonical DEP text is at >

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Hello Jeremy, On Wed, Jun 07, 2017 at 05:06:10PM -0400, Jeremy Bicha wrote: > On Wed, Jun 7, 2017 at 4:56 PM, Sean Whitton wrote: > > I am hereby reserving DEP number 15 for my draft DEP, "Reserved > > namespaces for DD-approved non-maintainer changes". > > I think

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Thu, Jun 08, 2017 at 05:41:22AM +0800, Boyuan Yang wrote: > Just wondering why we need to control the branch name of proposed topic > branch, or even use a single repo to receive contributions. > > My thought is that all we need is the "Pull Request / Merge Request" feature > on Alioth, where

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Sean Whitton writes ("DEP 15: Reserved namespace for DD-approved non-maintainer changes"): > I am hereby reserving DEP number 15 for my draft DEP, "Reserved > namespaces for DD-approved non-maintainer changes". > > I'd like to suggest discussing this DEP on d-devel (which is the > Reply-to for

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

在 2017年6月7日星期三 +08 下午9:56:39，Sean Whitton 写道： > Dear all, > > I am hereby reserving DEP number 15 for my draft DEP, "Reserved > namespaces for DD-approved non-maintainer changes". > > I'd like to suggest discussing this DEP on d-devel (which is the > Reply-to for this e-mail). The canonical DEP

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On Wed, Jun 7, 2017 at 4:56 PM, Sean Whitton wrote: > I am hereby reserving DEP number 15 for my draft DEP, "Reserved > namespaces for DD-approved non-maintainer changes". I think this proposal somewhat contradicts DEP-14. It also feels to me like this proposal is