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

Groups > linux.debian.project > #9278 > unrolled thread

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

Back to article view | Back to linux.debian.project

Contents

  DEP 15: Reserved namespace for DD-approved non-maintainer changes Sean Whitton <spwhitton@spwhitton.name> - 2017-06-07 23:00 +0200
    Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes Boyuan Yang <073plan@gmail.com> - 2017-06-07 23:50 +0200
    Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes Ian Jackson <ijackson@chiark.greenend.org.uk> - 2017-06-08 02:00 +0200
    Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes Christian Seiler <christian@iwakd.de> - 2017-06-08 11:50 +0200

#9278 — DEP 15: Reserved namespace for DD-approved non-maintainer changes

[Multipart message — attachments visible in raw view] — view raw

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 text is at
<http://dep.debian.net/deps/dep15/>.

The drivers are myself and Ian Jackson, who came up with the idea, but I
said I'd write up the formal proposal.

-- 
Sean Whitton

[toc] | [next] | [standalone]

#9279

[Multipart message — attachments visible in raw view] — view raw

在 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 text is at
> <http://dep.debian.net/deps/dep15/>.
> 
> The drivers are myself and Ian Jackson, who came up with the idea, but I
> said I'd write up the formal proposal.

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 random contributors (who might have absolutely no permission 
anywhere) can create forks (forked repositories) freely and request for review 
and eventual merge from the forked repo into main repo if necessary. People 
are much familiar with such workflow similar to GitHub / GitLab's fork-and-
merge behaviour.

That would also be much easier than setting up custom access control rules 
based on permission inside a single repository.

--
Boyuan Yang

[toc] | [prev] | [next] | [standalone]

#9280

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 this e-mail).  The canonical DEP text is at
> <http://dep.debian.net/deps/dep15/>.
> 
> The drivers are myself and Ian Jackson, who came up with the idea, but I
> said I'd write up the formal proposal.

Thanks, Sean.

For others: this was prompted by a conversation Sean and I had in a
pub on Monday.

Before we get into a detailed discussion here on -devel I think it
would be worth Sean and me getting the DEP draft into some kind of
reasonable shape that we both agree on.

So I won't reply in detail to the comments.

Ian.

[toc] | [prev] | [next] | [standalone]

#9282

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
> <http://dep.debian.net/deps/dep15/>.

I really hate to be negative here, but I just don't see the
point of it.

If I look at how I maintain packages, if someone sends me a
patch (or later once implemented a pull request), I will
always carefully look at that patch - regardless of who it
is from. Not because I necessarily mistrust people, but just
so I also am up to speed about the current state of the
package. I really don't see how having an area to pull from
where only DDs and selected DMs can push to would help here.
(And if contributions from a specific person come often
enough, I'd suggest co-maintainership anyway.)

To me this looks like a very complicated technical solution
to something that I've never encountered as a problem myself.

Again, sorry that I'm so negative here, and of course I have
my own biases, but maybe you could provide an example work-
flow where your proposal actually helps the maintainer and/
or the contributor?

Regards,
Christian

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.project

csiph-web