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:05:43 +1100 [thread overview]
Message-ID: <CAH5451mbB8kU_0P=PwpyxT_3+s_UY1TxRF-sBTUZ5kxeZGHe3g@mail.gmail.com> (raw)
In-Reply-To: <7vehtdqh46.fsf@alter.siamese.dyndns.org>
On 1 March 2012 11:50, Junio C Hamano <gitster@pobox.com> wrote:
> Andrew Ardill <andrew.ardill@gmail.com> writes:
>
>> Additionally, if we are not prepared to use non-Free tools, we should
>> probably stop using github. (This example is a little trite, seeing as
>> there are non-github alternatives available for grabbing the source
>> code.
>
> Just on this part.
>
> Github is not the only place to grab the source code. Far from it.
I understand that Github is not the only place to grab the source code
(maybe it was not clear that I understood that), however the point was
more that even though Github is not-Free many people still use it to
develop Free software (including people developing git). As Free
alternatives to Github are available not many people mind too much (or
so it seems).
Why do people use Github at all? Perhaps, because it provides an
accessible, reliable, powerful and supported platform, with large
amount of penetration in the market and some very desirable features.
I believe that JIRA in the OnDemand package offers similar benefits.
Additionally, Free alternatives would still be available (the mailing
list). Perhaps there is too much controversy to anoint a JIRA issue
tracker as 'official', however I continue to hear people ask for a
tracker, and apart from Jonathan Nieder with the Debian bug tracker
see no one else putting their hands up.
In any case, I spun the instance up because nothing happens until
someone does something, and if it fails then at least we have a record
of trying it next time someone asks :)
I would love to see it succeed.
Regards,
Andrew Ardill
next prev parent reply other threads:[~2012-03-01 1:06 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 [this message]
2012-03-01 1:05 ` Junio C Hamano
2012-03-01 1:20 ` Andrew Ardill
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='CAH5451mbB8kU_0P=PwpyxT_3+s_UY1TxRF-sBTUZ5kxeZGHe3g@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).