* Using GitHub @ 2015-12-23 17:04 Lewis, Eric 2015-12-23 23:13 ` Bart Schaefer 0 siblings, 1 reply; 4+ messages in thread From: Lewis, Eric @ 2015-12-23 17:04 UTC (permalink / raw) To: zsh-workers [-- Attachment #1: Type: text/plain, Size: 254 bytes --] What are the development team's thoughts about adopting a tool like GitHub for issue/bug tracking? Eric Lewis Web Developer, Interactive News The New York Times 620 Eighth Avenue, 2nd Floor New York, NY 10018 Office: (212) 556-2081 Cell: (610) 715-8560 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using GitHub 2015-12-23 17:04 Using GitHub Lewis, Eric @ 2015-12-23 23:13 ` Bart Schaefer 2015-12-24 17:22 ` Nikolay Aleksandrovich Pavlov (ZyX) 0 siblings, 1 reply; 4+ messages in thread From: Bart Schaefer @ 2015-12-23 23:13 UTC (permalink / raw) To: zsh-workers 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. Others may have different feelings/opinions. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using GitHub 2015-12-23 23:13 ` Bart Schaefer @ 2015-12-24 17:22 ` Nikolay Aleksandrovich Pavlov (ZyX) 2015-12-28 15:23 ` Daniel Shahaf 0 siblings, 1 reply; 4+ messages in thread From: Nikolay Aleksandrovich Pavlov (ZyX) @ 2015-12-24 17:22 UTC (permalink / raw) To: Bart Schaefer, zsh-workers 24.12.2015, 02:13, "Bart Schaefer" <schaefer@brasslantern.com>: > 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. > > Others may have different feelings/opinions. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using GitHub 2015-12-24 17:22 ` Nikolay Aleksandrovich Pavlov (ZyX) @ 2015-12-28 15:23 ` Daniel Shahaf 0 siblings, 0 replies; 4+ messages in thread From: Daniel Shahaf @ 2015-12-28 15:23 UTC (permalink / raw) To: Nikolay Aleksandrovich Pavlov (ZyX); +Cc: Bart Schaefer, zsh-workers Nikolay Aleksandrovich Pavlov (ZyX) wrote on Thu, Dec 24, 2015 at 20:22:49 +0300: > > > 24.12.2015, 02:13, "Bart Schaefer" <schaefer@brasslantern.com>: > > 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-12-28 15:23 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-12-23 17:04 Using GitHub Lewis, Eric 2015-12-23 23:13 ` Bart Schaefer 2015-12-24 17:22 ` Nikolay Aleksandrovich Pavlov (ZyX) 2015-12-28 15:23 ` Daniel Shahaf
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).