ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] Gitlab (or similar) hosting at kernel.org
Date: Mon, 10 Sep 2018 21:44:20 +0200	[thread overview]
Message-ID: <CAKMK7uGLyP4yk+gcJfAdJxr5h7q4F5d9+UTHr9_juFATBM4HZA@mail.gmail.com> (raw)
In-Reply-To: <06539e48-f20c-431d-51aa-3d299ef894ac@linuxfoundation.org>

On Mon, Sep 10, 2018 at 9:00 PM, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> Hi, all:
>
> The topic of Gitlab comes up quite a bit recently, so I think it's worth
> having a separate conversation about it. Kernel.org provides gitolite
> hosting, which works great for most "old skool" maintainers who are
> comfortable with "everything over email" (see Greg's talk about patches
> carved into stone tablets [1]). However, just in case I'm stuck in an
> echo chamber, I wanted to ask if providing a more "holistic" platform
> like Gitlab (or one of its alternatives like Pagure, pending evaluation)
> is something we should be actively considering to be offered centrally
> as a standard kernel.org service.

Except I'm massively misreading the tea leaves I don't expect drm to
move from fd.o to k.org. Our interaction surface towards the userspace
projects hosted on fd.o (mesa, X11, wayland, ...) is much bigger than
towards the other parts of the kernel, I expect us to stay with those
folks. Being able to reassign/move issues and have simple
cross-project discussions with those guys matters a lot. Same reasons
really for us abandoning kernel bugzilla in favour of the fd.o one.

Of course that's just drm, no idea who else might entertain this.
-Daniel

>
> .. [1]
> https://kernel-recipes.org/en/2016/talks/patches-carved-into-stone-tablets/
>
> Regards,
> --
> Konstantin Ryabitsev
> The Linux Foundation
> kernel.org
>
>
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2018-09-10 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 19:00 Konstantin Ryabitsev
2018-09-10 19:44 ` Daniel Vetter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKMK7uGLyP4yk+gcJfAdJxr5h7q4F5d9+UTHr9_juFATBM4HZA@mail.gmail.com \
    --to=daniel.vetter@ffwll.ch \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox