all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: Eli Zaretskii <eliz@gnu.org>,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Thu, 21 Jul 2016 22:50:05 +0200	[thread overview]
Message-ID: <m3zipaaf7m.fsf@exodia.verona.se> (raw)
In-Reply-To: <877fce3flr.fsf@russet.org.uk> (Phillip Lord's message of "Thu, 21 Jul 2016 21:23:28 +0100")

phillip.lord@russet.org.uk (Phillip Lord) writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: phillip.lord@russet.org.uk (Phillip Lord)
>>> Date: Thu, 21 Jul 2016 19:40:24 +0100
>>> Cc: emacs-devel@gnu.org
>>> 
>>> There needs to be the willingness to adopt it, if we choose something,
>>> though.
>>
>> Expect it to be adopted if it makes our jobs simpler, like faster, or
>> saves us from doing some of the stuff at all.  Otherwise, you will
>> have difficulty convincing at least me to move.
>
> *shrugs*
>
> As with everything, it will makes things somewhat slower during
> adoption. And I can only give you anecdotal evidence that it will make
> things better after adoption.
>
>
>> Also, I think the solution should support text-mode browsers, such as
>> Lynx or Emacs's eww on TTY frames.  IOW, anything that requires GUI
>> and won't work otherwise is probably out of question to begin with.
>> (This requirement is not for me personally.)
>
> If that is a hard requirement, then I think we are not going to get much
> further with a web 2.0 program. The best option is going to be somewhere
> to host clones for developers, and then use debbugs.

Gitlab has a cli-interface, so you can do things with it from a shell.

(FWIW I'm not doing any advocating here, I'm just helping to provide
info.)

I have set up gitlab instances for clients, and its not hard to do using
docker-compose.

I don't find the gitlab bug tracker spectacular, but it's not designed
to be either, AFAICT. 

> But, it really is a hard requirement.
>
> Phil
>

-- 
Joakim Verona



  reply	other threads:[~2016-07-21 20:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 13:54 Development suggestions from an ENSIME developer Lars Ingebrigtsen
2016-07-20 14:02 ` Clément Pit--Claudel
2016-07-22 22:48   ` Robert Cochran
2016-07-23  7:30     ` Eli Zaretskii
2016-07-23  9:00     ` Lars Ingebrigtsen
2016-07-23 19:52       ` Richard Stallman
2016-07-23 13:50     ` Clément Pit--Claudel
2016-07-23 20:14     ` Phillip Lord
2016-07-25 18:34       ` Robert Cochran
2016-08-03  6:05   ` John Wiegley
2016-08-06 18:42     ` Alex Dunn
2016-07-20 14:03 ` Dmitry Gutov
2016-07-20 14:08   ` Lars Ingebrigtsen
2016-07-20 14:12     ` Dmitry Gutov
2016-07-20 14:23       ` Christian Kruse
2016-07-20 14:41         ` Dmitry Gutov
2016-07-20 14:30 ` Christian Kruse
2016-07-20 14:44   ` Lars Ingebrigtsen
2016-07-20 15:02     ` Clément Pit--Claudel
2016-07-20 15:07       ` Lars Ingebrigtsen
2016-07-20 15:31         ` Clément Pit--Claudel
2016-07-20 17:00 ` Stefan Monnier
2016-07-21 18:40   ` Phillip Lord
2016-07-21 19:30     ` Eli Zaretskii
2016-07-21 20:22       ` Stefan Monnier
2016-07-21 21:26         ` Christian Kruse
2016-07-21 22:04         ` Dmitry Gutov
2016-07-21 20:23       ` Phillip Lord
2016-07-21 20:50         ` joakim [this message]
2016-07-22  6:59         ` Eli Zaretskii
2016-07-22 10:46           ` Lars Ingebrigtsen
2016-07-22 11:48             ` Lars Ingebrigtsen
2016-07-22 13:00               ` Robert Weiner
2016-07-22 13:34                 ` Eli Zaretskii
2016-07-22 14:28                   ` Robert Weiner
2016-07-22 14:45             ` Ted Zlatanov
2016-07-22 13:35           ` Stefan Monnier
2016-07-22 14:38             ` Eli Zaretskii
2016-07-22 14:56               ` Stefan Monnier
2016-07-22 15:58                 ` Phillip Lord
2016-07-22 15:47           ` Phillip Lord

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=m3zipaaf7m.fsf@exodia.verona.se \
    --to=joakim@verona.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=phillip.lord@russet.org.uk \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.