Zsh Mailing List Archive
Messages sorted by:
Re: using gitlab (or other) issue tracker instead of mailing list?
- X-seq: zsh-users 22326
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxx
- Subject: Re: using gitlab (or other) issue tracker instead of mailing list?
- Date: Mon, 2 Jan 2017 13:42:31 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=9DxjPD/OB+s8tDpkPsL8QwPNvW0nbeqSSX2K3LhmBx0=; b=FV+W9ng6vh/4nH5qYTYt7oGsanNpceWSwSADZZm/0w3u1B188Z3F8B9nSCl/Gt8g4T AD5a0TFVEpvi/fSxrEXsk8NEglk0LZy2v1D1w0VTXyrODP9EFCkqcGMTijpvRyS32dFL 4dE+gYfoAYq/TyVlDBIa36fwYvtFpFzzg31p1JCe5azhDd/Plye1+RAsuOkW9ZrLl1Dy PZFbmyYLjmyY17uN+8SBuvqNq03woR3pXgKafYuTOqplv+LeYuMl18phvElTPdQiG7aL 8dO2JDW0U3NJ3Rm+G0iuOAQTY0U4ILHNs0pempJv/IKbM+uEhiOsJsLwFEtRHBYEPhOV 72Jw==
- In-reply-to: <CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA@mail.gmail.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA@mail.gmail.com>
On Dec 31, 5:10pm, Timothee Cour wrote:
} What are your requirements for tracking zsh issues, and could this be
} accomplished by a standard issue tracker (eg github/gitlab/bitbucket)
} instead of this mailing list ?
I think the answer to the "instead" part of that question is "no,"
if only because of the long-standing practice of linking changes to
discussion threads by use of the list archive article number.
My personal requirements for any tracker that isn't the zsh-workers
mailing list are (1) somebody else is responsible for operating it;
(2) it's at least as useful to those of us who are updating the code
as it is to the people who just want to report problems; and (3) I
no longer have to carry on this discussion.
By way of relatively recent analogy, we switched version control from
CVS to git because the people who were proponents of the change got
involved with the process, and provided suggestions/assistance/tools,
and in several cases actually became involved in code maintenance.
Without that degree of commitment to whatever bug tracker you propose
we adopt, continuing to push it is just a distraction.
Messages sorted by: