unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Subject: Re: GHM debriefing
Date: Wed, 31 Aug 2016 13:40:52 +0000	[thread overview]
Message-ID: <87fuplm4yj.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87eg5769n9.fsf@gnu.org>

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> [ Unknown signature status ]
> Hello!
>
> The GNU Hackers Meeting (GHM) took place last week, with ~50 people
> including 4 Guix hackers (less than at FOSDEM!).  I found myself talking
> 3 times (!) about Guix, hoping the audience would not saturate. ;-)
>
>   https://www.gnu.org/ghm/program.html
>
> Slides online, and hopefully videos will follow:
>
>   https://www.gnu.org/software/guix/help/#talks
>
> The first talk was the usual status update in which I also talked about
> challenges that we face to scale up, how we address them and what
> remains to be done.
>
> On that topic, I had an interesting discussion with Nicolas Petton of
> Emacs about patch tracking.  Nicolas explained that Gitlab (free
> software) doesn’t have some of the technical defects that GitHub has; in
> particular it can rebase instead of merging, thereby helping preserve a
> linear history, and it can be dealt with “mostly” by email.  Perhaps we
> could try running an instance and see what it’s like.

Before you came up with gitlab, I started a thread[0] to see what the
feedback would be like, and some people mentioned gitlab.
Personal experience is not so much, but I prefer it over most systems
I've used now. We use it in a non-public instance for bug-tracking and I
just started using it on gitlab.com (too lazy to setup my own) for
adding an issues/milestones/roadmap feature to the preparation from $now
to live systems shipped with $applications and NixOS/GuixSD and more.

I would very much welcome the move to (a selfhosted) gitlab (instance),
even if it would only be for better patches and bugs tracking.
The current status (email in general) is terrible, and we can only move
upwards.
The features gitlab offers look promising so far.


Also: someone should package gitlab for Guix ;)
Btw: I had a short view into the local doctors/hospital IT suppliers a
couple of years ago, and the solutions were 99% Windows based. I like
GNU/health (http://health.gnu.org/), having this as a package and
service could be another big selling point for Guix.

[0]: https://lists.gnu.org/archive/html/guix-devel/2016-08/msg00854.html
-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

  parent reply	other threads:[~2016-08-31 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 22:09 GHM debriefing Ludovic Courtès
2016-08-29 12:48 ` David Craven
2016-08-29 13:50 ` Vincent Legoll
2016-08-29 15:20 ` Christopher Allan Webber
2016-08-30 15:57   ` Ludovic Courtès
2016-08-31 13:40 ` ng0 [this message]
2016-08-31 13:48   ` David Craven
2016-08-31 22:28 ` Clément Lassieur
2016-08-31 23:08   ` Leo Famulari
2016-09-01  6:41   ` ng0
2016-09-01 12:24   ` Ludovic Courtès
2016-09-03  8:05   ` Hartmut Goebel
  -- strict thread matches above, loose matches on Subject: below --
2013-08-29 21:52 Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87fuplm4yj.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).