zsh-workers
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>,
	"Mikael Magnusson" <mikachu@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: RFE: Migration zsh git repo to github or gitlab
Date: Wed, 22 Jul 2020 05:57:14 +0000	[thread overview]
Message-ID: <f6ee0c8d-111e-4fb3-86a4-fd4489a89ac3@www.fastmail.com> (raw)
In-Reply-To: <CABB28Cz_QuC7CZB4AokOZ9yGJojmXvg3Z59VOz=bweUFgUkqAA@mail.gmail.com>

Tomasz Kłoczko wrote on Tue, 21 Jul 2020 20:08 +00:00:
> On Tue, 21 Jul 2020 at 20:39, Mikael Magnusson <mikachu@gmail.com> wrote:
> 
> > There are already mirrors on github, for example
> > https://github.com/zsh-users/zsh
> 
> 
> Thx for the update. It would be nice to add that info to zsh web page :)

Agreed.

> What about make that repo as not only mirror but main on and enable
> submitting issue tickets?

You're coupling two independent matters: where the issue tracker lives
has nothing to do with which repository is the "main" one.  Also, you
haven't actually mentioned what purpose you think enabling github issues
would achieve.

In any case:

I don't see a reason to move the "main" repository.  Such a move
wouldn't affect anyone who doesn't have push access, other than the
mirrors' admins.

I am sceptical about enabling submitting github issues from the public.
Fewer people triage pull requests than triage emailed patches.  That
being the case, I am concerned that enabling issues would basically
leave them for Oliver and me to handle, which would be a poor way to
divide the overall maintenance workload.

The question of a bug tracker was discussed a number of times before.
The conclusion was that we'd like something that integrates with our
existing workflow.

      reply	other threads:[~2020-07-22  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 19:06 Tomasz Kłoczko
2020-07-21 19:39 ` Mikael Magnusson
2020-07-21 20:06   ` Daniel Shahaf
2020-07-21 20:08   ` Tomasz Kłoczko
2020-07-22  5:57     ` Daniel Shahaf [this message]

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=f6ee0c8d-111e-4fb3-86a4-fd4489a89ac3@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=kloczko.tomasz@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@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).