From: Timothee Cour <timothee.cour2@gmail.com>
To: zsh-users@zsh.org
Subject: using gitlab (or other) issue tracker instead of mailing list?
Date: Sat, 31 Dec 2016 17:10:43 -0800 [thread overview]
Message-ID: <CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Spawned off from a separate discussion:
> regression: zsh completion stopped working after upgrading zsh 5.2=>5.3
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 ?
To summarize:
* github/gitlab are widely used so no particular signup would be needed
* using github.gitlab, ppl can click on Watch to follow/unfollow individual
issues or all of zsh issues to choose how much email from github they
receive
* it would lower the barrier of entry to enter bugs, ie get bugs fixed
faster
* all benefits of bug tracker as opposed to mailling list [tracking bugs,
cross references, search, syntax highlighting etc]
* avoids revealing your email address
* this has been adoped by https://github.com/zsh-users [Zsh community
projects (not directly affiliated with the zsh project)] probably for a
combination of the above reasons
Daniel Shahaf's comment:
> For one, I assume we won't consider a bug tracker that doesn't have
bidirectional email integration with this mailing list. (to minimise
workflow disruption)
The issue trackers I mentioned do have bidirectional email integration, eg
I can see github issues in my email and replying via email will also reply
in github issues, etc.
next reply other threads:[~2017-01-01 1:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 1:10 Timothee Cour [this message]
2017-01-02 21:42 ` Bart Schaefer
2017-01-12 17:34 ` Timothee Cour
[not found] ` <CAM4j=kOz5wpbUTEwcHXcOshJsRLkvpXmRtOvP1FiTx+V6Hu25w__35485.8083803721$1484248884$gmane$org@mail.gmail.com>
2017-01-12 20:01 ` Emailing this list from unsubscribed addresses (was: Re: using gitlab (or other) issue tracker instead of mailing list?) Daniel Shahaf
2017-01-12 20:07 ` Bart Schaefer
2017-01-13 8:22 ` Timothee Cour
2017-01-13 8:27 ` Bart Schaefer
2017-01-02 23:17 ` using gitlab (or other) issue tracker instead of mailing list? Axel Beckert
[not found] <CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA__37436.9124918759$1483233144$gmane$org@mail.gmail.com>
2017-01-02 15:38 ` Daniel Shahaf
2017-01-02 15:58 ` Frank Terbeck
2017-01-02 16:42 ` Daniel Shahaf
2017-01-02 16:27 ` Ray Andrews
2017-01-02 19:16 ` Peter Stephenson
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='CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA@mail.gmail.com' \
--to=timothee.cour2@gmail.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).