unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: moving to gitlab?
Date: Tue, 22 Jan 2019 20:18:25 -0800	[thread overview]
Message-ID: <CA+XASoXrHAe90PP-VSfmKsjRLwU+r+i8gR+Ue0d5LYDpHNypaw@mail.gmail.com> (raw)
In-Reply-To: <smuef94w46x.fsf@linuxpal.mit.edu>

On Tue, Jan 22, 2019 at 5:30 PM Greg Troxel <gdt@lexort.com> wrote:
>
> Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:
>
> > Any chance or interest in moving to gitlab? My apologies if this has
> > been discussed already. Not that I ever contribute anything directly
> > to Guile (2 patches in 6 years?), but it feels like it would be an
> > improvement in terms of communication, sending patches, etc. May be it
> > would even encourage more developers to contribute? Sending patches
> > over a mailing list shouldn't be a thing anymore. Again, my apologies.
>
> I can't speak for the coalition, but generally there is a notion that
> FSF projects are hosted on infrastructure operated by a charitable
> non-profit that has the advancement of Free Software as the goal.
>
> Also, history shows that the place people move to because of concerns
> about $PREVIOSU_PLACE will follow suit eventually...
>
> If your point is that the self-hosted infrastructure should have some
> way for random poeple to provide in-tool changes, that sounds sensible.

I realize I might have opened a can of worms, but yes, mainly that
would be the main motivation. Making it more easy for people to
contribute. Nowadays people are used to these kind of tools and, in my
experience, they are really useful.

Thanks,

Aleix



  parent reply	other threads:[~2019-01-23  4:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  9:25 ping: Fixes for guile.m4 Alex Sassmannshausen
2019-01-21 14:42 ` Mike Gran
2019-01-22  7:44   ` alex sassmannshausen
2019-01-22 23:02   ` moving to gitlab? (was: Re: ping: Fixes for guile.m4) Aleix Conchillo Flaqué
2019-01-23  1:30     ` moving to gitlab? Greg Troxel
2019-01-23  2:12       ` Nala Ginrut
2019-01-23  4:18       ` Aleix Conchillo Flaqué [this message]
2019-01-23 14:51         ` Mike Gran
2019-01-25  4:19           ` Amin Bandali
  -- strict thread matches above, loose matches on Subject: below --
2019-01-23  3:10 brettg

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=CA+XASoXrHAe90PP-VSfmKsjRLwU+r+i8gR+Ue0d5LYDpHNypaw@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=gdt@lexort.com \
    --cc=guile-devel@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.
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).