From: Andrew Ardill <andrew.ardill@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Greg Troxel <gdt@ir.bbn.com>,
Jonathan Nieder <jrnieder@gmail.com>,
opticyclic <opticyclic@gmail.com>,
git@vger.kernel.org
Subject: Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests
Date: Thu, 1 Mar 2012 12:20:52 +1100 [thread overview]
Message-ID: <CAH5451krbyZCRm8JR+kf+8cDqkbnQKnzXGxmncmRF9YPXvckNA@mail.gmail.com> (raw)
In-Reply-To: <7vaa41qgf4.fsf@alter.siamese.dyndns.org>
On 1 March 2012 12:05, Junio C Hamano <gitster@pobox.com> wrote:
> Andrew Ardill <andrew.ardill@gmail.com> writes:
>
>> On 1 March 2012 11:37, Greg Troxel <gdt@ir.bbn.com> wrote:
>>>
>>> Do people really think it's reasonable to use non-Free tools to develop
>>> git? That seems surprising to me.
>>
>> Maybe not, and if that is the case I am more than happy to let this die.
>
> I won't speculate how big or small part of the Git community you would be
> repelling by using a closed/commertial offering. It may not be such a big
> deal, or it may be. I simply do not know.
Neither do I - let's find out!
> But we will never find out until we try. The same thing can be said for
> the usefulness of having a bug tracker and feasibility of keeping it
> reasonably clean and useful over time with volunteer effort. I commend
> you for finally stepping up and biting the bullet to start an experiment.
I have been meaning to get this going for a few months now, the latest
thread kickstarted me again.
> One request I may have is to give read/browse-only access to unregistered
> users without any account (I hate having to maintain credentials to random
> websites, and I imagine so do many other people), but I am not the target
> audience, so please do not bend backwards to implement such if it is too
> much trouble with the system.
>
> Thanks.
I have given browse access by default to Anyone (does not require
log-in). JIRA is highly customisable, so most requests are typically
feasible.
Regards,
Andrew Ardill
next prev parent reply other threads:[~2012-03-01 1:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:19 Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests opticyclic
2012-02-29 18:23 ` Brian Gernhardt
2012-02-29 18:53 ` Junio C Hamano
2012-02-29 22:53 ` Jonathan Nieder
2012-02-29 23:58 ` Andrew Ardill
2012-03-01 0:37 ` Greg Troxel
2012-03-01 0:45 ` Andrew Ardill
2012-03-01 0:50 ` Junio C Hamano
2012-03-01 1:05 ` Andrew Ardill
2012-03-01 1:05 ` Junio C Hamano
2012-03-01 1:20 ` Andrew Ardill [this message]
2012-03-01 5:16 ` Miles Bader
2012-03-01 5:40 ` Andrew Ardill
2012-03-01 16:52 ` Scott Chacon
2012-03-01 20:23 ` Junio C Hamano
2012-03-01 11:29 ` Thomas Rast
2012-03-01 11:54 ` Ævar Arnfjörð Bjarmason
2012-03-01 12:46 ` Andrew Ardill
2012-03-01 12:28 ` Andrew Ardill
2012-03-01 17:10 ` Junio C Hamano
2012-03-02 4:03 ` Neal Kreitzinger
2012-03-02 4:19 ` Jonathan Nieder
2012-03-02 4:21 ` Junio C Hamano
2012-03-02 5:50 ` Neal Kreitzinger
2012-03-02 6:25 ` Jonathan Nieder
2012-03-02 7:03 ` Junio C Hamano
2012-03-02 14:18 ` Andreas Ericsson
2012-03-02 16:45 ` Junio C Hamano
2012-03-07 8:03 ` Andrew Ardill
2012-03-07 9:52 ` Vincent van Ravesteijn
2012-03-07 13:04 ` Joern Huxhorn
2012-03-07 13:53 ` Jonathan Nieder
2012-03-07 14:47 ` Joern Huxhorn
2012-03-07 15:08 ` Pau Garcia i Quiles
2012-03-07 17:18 ` Phil Hord
2012-02-29 19:18 ` Carlos Martín Nieto
2012-02-29 21:37 ` Sitaram Chamarty
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=CAH5451krbyZCRm8JR+kf+8cDqkbnQKnzXGxmncmRF9YPXvckNA@mail.gmail.com \
--to=andrew.ardill@gmail.com \
--cc=gdt@ir.bbn.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=opticyclic@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).