From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16936 invoked by alias); 28 Dec 2015 15:23:48 -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: X-Seq: 37441 Received: (qmail 23133 invoked from network); 28 Dec 2015 15:23:47 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=KSv8EmMW3KphPBTKplPc0CuUc1Y=; b=ogdPId 5kMnU5BCxSBR0REGLaMJYN5ROfOdgOLlOlFzVK0tv6KrE0PRwTNySe4N3MzUfJP5 NTDgFDNbEMFUGespuBSMwMKvjxMT0yVq5Wr+EYA2Gah4O0wiQTxa2DP5YrsuwK0A 20mWExWdjC1x++sM0nOanghCqMyEZuOacUJPo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=KSv8EmMW3KphPBTKplPc0CuUc1Y=; b=E+7Pa UbnQPqTbo+J7xaY2V4BID/ZEXPCZ9tQzPUg6FHYq2flzBn9l89Px8+fy7FtHvf/C HTzGj0rApQNtQHN4UmscycASAtyqLm4t8KzxbleUa83WNw7uOj+YK8E32p407pFt 3VxVs3dCCPz24xqaGVcbH4M9SjcV66J+uE9qZ0= X-Sasl-enc: 2qClznvt1Rn1mVOmG+rEjMYcHn1j48mibQxIe5XERROc 1451316225 Date: Mon, 28 Dec 2015 15:23:36 +0000 From: Daniel Shahaf To: "Nikolay Aleksandrovich Pavlov (ZyX)" Cc: Bart Schaefer , zsh-workers@zsh.org Subject: Re: Using GitHub Message-ID: <20151228152234.GA3028@tarsus.local2> References: <151223151331.ZM32187@torch.brasslantern.com> <2850751450977769@web16h.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2850751450977769@web16h.yandex.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Nikolay Aleksandrovich Pavlov (ZyX) wrote on Thu, Dec 24, 2015 at 20:22:49 +0300: > > > 24.12.2015, 02:13, "Bart Schaefer" : > > On Dec 23, 12:04pm, Lewis, Eric wrote: > > } > > } What are the development team's thoughts about adopting a tool like GitHub > > } for issue/bug tracking? > > > > Something along the lines of "Git off my lawn, ya whippersnapper" seems > > pretty likely. > > > > More seriously: We tried using the tracker on SourceForge and it didn't > > really work -- it wasn't well-monitored or kept up to date. Adding yet > > another source of bug reports, conversations to monitor, and updates to > > record, is not appealing, nor at this point is that something I have > > much time to attend to. > > Problem may be that this is bug tracker on sourceforge: sourceforge is > not popular nowadays. Also have a look at how Bram did: they have an > issue tracker on github which posts to vim-dev, with a mailing daemon > which posts back in case of replies. So users that got used to GH have > their issue tracker, and users got used to mailing list get issues > too. Though, of course, this makes GH issue tracker secondary because > issues posted to vim-dev do not appear there. I think that's more or less what we'll want, too: a place to record bugs in, without additional process or overhead. E.g., all conversation continues to happen on-list; developers can close issues from within their existing workflow (email and commit messages); but we gain a place to record known-but-not-yet-fixed bugs. Come to think of it, even just creating a BUGS file at the root of the source tree and recording known issues in it would be an improvement over having nothing at all. Cheers, Daniel > > Others may have different feelings/opinions. > > > > > Others may have different feelings/opinions.