From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12240 invoked from network); 22 Jul 2020 05:58:26 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 22 Jul 2020 05:58:26 -0000 Received: (qmail 5278 invoked by alias); 22 Jul 2020 05:58:17 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46257 Received: (qmail 21776 invoked by uid 1010); 22 Jul 2020 05:58:17 -0000 X-Qmail-Scanner-Diagnostics: from out3-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25877. spamassassin: 3.4.4. Clear:RC:0(66.111.4.27):SA:0(-2.6/5.0):. Processed in 4.410605 secs); 22 Jul 2020 05:58:17 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgeekgddutdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfffgr nhhivghlucfuhhgrhhgrfhdfuceougdrshesuggrnhhivghlrdhshhgrhhgrfhdrnhgrmh gvqeenucggtffrrghtthgvrhhnpeehjeeihfejfeffheetheduhfeuieeuvdelueffieeh kedvleeihffhhfevvddugeenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepugdrshesuggrnhhi vghlrdhshhgrhhgrfhdrnhgrmhgv X-ME-Proxy: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-92-g11c785d-fm-20200721.004-g11c785d5 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 22 Jul 2020 05:57:14 +0000 From: "Daniel Shahaf" To: =?UTF-8?Q?Tomasz_K=C5=82oczko?= , "Mikael Magnusson" Cc: zsh-workers@zsh.org Subject: Re: RFE: Migration zsh git repo to github or gitlab Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Tomasz K=C5=82oczko wrote on Tue, 21 Jul 2020 20:08 +00:00: > On Tue, 21 Jul 2020 at 20:39, Mikael Magnusson wro= te: >=20 > > There are already mirrors on github, for example > > https://github.com/zsh-users/zsh >=20 >=20 > 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.