git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Lars Schneider <larsxschneider@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)
Date: Tue, 19 Sep 2017 09:07:53 -0700	[thread overview]
Message-ID: <20170919160753.GA75068@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1709191733450.219280@virtualbox>

Hi,

Johannes Schindelin wrote:

> To relate that, you are using a plain text format that is not well defined
> and not structured, and certainly not machine-readable, for information
> that is crucial for project management.
>
> What you need is a tool to aggregate this information, to help working
> with it, to manage the project, and to be updated automatically. And to
> publish this information continuously, without costing you extra effort.
>
> I understand that you started before GitHub existed, and before GitHub was
> an option, the script-generated What's cooking mail was the best you could
> do.

I think you are subtly (but not directly, for some reason?) advocating
moving project management for the Git project to GitHub Issues.

For what it's worth:

 1. I would be happy to see Git adopt a bug tracker.  As we've
    discussed on the list before, I suspect the only way that this is
    going to happen is if some contributors start using a bug tracker
    and keep up with bugs there, without requiring everyone to use it.
    That is how the Linux Kernel project started using
    bugzilla.kernel.org, for example.

 2. GitHub Issues is one of my least favorite bug trackers, for what
    it's worth.  If some sub-project of Git chooses to use it, then
    that's great and I won't get in their way.  I'm just providing
    this single data point that approximately any other tracker
    (Bugzilla, JIRA, debbugs, patchwork) is something I'd be more
    likely to use.

 3. This advice might feel hopeless, because if the maintainer is not
    involved in the initial pilot, then how does the bug tracker get
    notified when a patch has been accepted?  But fortunately this is
    a problem other people have solved: e.g. most bug trackers have an
    API that can be used to automatically notify the bug when a patch
    with a certain subject line appears on a certain branch.

Thanks and hope that helps,
Jonathan

  reply	other threads:[~2017-09-19 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 19:56 What's cooking in git.git (Aug 2017, #05; Tue, 22) Junio C Hamano
2017-08-23  1:00 ` Brandon Williams
2017-08-23 21:38 ` Lars Schneider
2017-08-24 19:33   ` Junio C Hamano
2017-09-15 16:18     ` Johannes Schindelin
2017-09-15 18:33       ` Junio C Hamano
2017-09-15 20:15         ` Johannes Schindelin
2017-09-15 21:22           ` Junio C Hamano
2017-09-18 14:41             ` Johannes Schindelin
2017-09-19  2:32               ` Junio C Hamano
2017-09-19 15:43                 ` Johannes Schindelin
2017-09-19 16:07                   ` Jonathan Nieder [this message]
2017-09-29 11:55                     ` Johannes Schindelin
2017-09-19 16:20                   ` Jonathan Nieder
2017-09-19 17:08                   ` Nicolas Morey-Chaisemartin
2017-09-29 12:15                     ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170919160753.GA75068@aiede.mtv.corp.google.com \
    --to=jrnieder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.com \
    /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://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).