git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Greg Troxel <gdt@ir.bbn.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Junio C Hamano <gitster@pobox.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, 01 Mar 2012 14:16:42 +0900	[thread overview]
Message-ID: <buo399s3nph.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <CAH5451kWaRGutP1esuvjSK-arrEc=5m-SDwVHACx6QF9JFj-MQ@mail.gmail.com>

Andrew Ardill <andrew.ardill@gmail.com> writes:
> Additionally, if we are not prepared to use non-Free tools, we should
> probably stop using github.

I think the issue isn't "using" non-free tools so much as it's getting
_locked into_ non-free tools.

So if JIRA makes all its data trivially exportable in a format which
is easy to use, and there's some way of isolating references to it so
that it's possible to switch to something else without undue hardship,
maybe it's not such a big deal.

[Github is a prime example of a non-free tool which is largely avoids
the lockin issue, and I imagine that's why so many free projects
happily use it.  That's generally true of any git repo site, given the
super-easy cloneability of git repos, but Github also provides good
export of the meta-data it keeps (issues, etc).]

-Miles

-- 
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.

  parent reply	other threads:[~2012-03-01  5:16 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
2012-03-01  5:16           ` Miles Bader [this message]
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=buo399s3nph.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=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).