all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Florian Paul Schmidt <mista.tapas@gmx.net>
Cc: guix-devel@gnu.org
Subject: Re: Separate Mailing Lists for Patches vs General Dev Discussion?
Date: Tue, 26 Jul 2016 10:44:48 +0000	[thread overview]
Message-ID: <87twfcvftr.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <5796782D.1010104@gmx.net> (Florian Paul Schmidt's message of "Mon, 25 Jul 2016 22:35:57 +0200")

Hi,

Florian Paul Schmidt writes:

> Hi,
>
> I'm following the Guix-Project, even if not contributing much because
> of time constraints. The one, very simple to implement, thing that
> would make following the project more easy IMHO would be a separate
> list for patches. Or maybe the other way around: A separate list for
> more general discussion :)
>
> What do you think?
>
> Regards,
> Flo
>

I don't know if that's a fix.
In my opinion we need a web application which is smart enough to
figure out what patches are and append the discussion around it
there, but it needs to offer ways to not just display this but
to contribute to the discussion in a webbrowser for example.

That's of course not our core problem, but it could make it a bit
more appealing.

I would say we could keep "guix-devel" for patches and
discussions around them and create another list for discussion,
for example "guix-discuss".

No fix, but could help to separate patches and general
discussions.

What do you all think?
-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-07-26 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 20:35 Separate Mailing Lists for Patches vs General Dev Discussion? Florian Paul Schmidt
2016-07-26 10:44 ` ng0 [this message]
2016-07-26 11:23   ` Andreas Enge
2016-07-26 12:34 ` Ludovic Courtès
2016-07-26 12:47   ` Vincent Legoll
2016-07-27 22:05     ` Ludovic Courtès
2016-07-29 11:56       ` Vincent Legoll
2016-07-29 15:28         ` Leo Famulari
2016-07-26 16:25 ` Danny Milosavljevic

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=87twfcvftr.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=mista.tapas@gmx.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.