From: Hitoshi Mitake <mitake.hitoshi@gmail.com>
To: Turbo Fredriksson <turbo@bayour.com>
Cc: stgt <stgt@vger.kernel.org>
Subject: Re: RFC: using launchpad as a public issue tracker of tgt
Date: Sat, 19 Apr 2014 14:10:15 +0900 [thread overview]
Message-ID: <8738h9ucp4.wl%mitake.hitoshi@gmail.com> (raw)
In-Reply-To: <075E87E1-C640-4F22-BF88-FB5763C2FEF0@bayour.com>
At Thu, 17 Apr 2014 12:07:57 +0200,
Turbo Fredriksson wrote:
>
> On Apr 17, 2014, at 8:51 AM, Hitoshi Mitake wrote:
>
> > It seems that tgt doesn't have a public issue tracker. I'd like to
> > propose laucnhpad for this purpose:
> > https://launchpad.net/tgt-project
>
> DISCLAIMER
> Having absolutly nothing to do with the project, other than a user.
> DISCLAIMER
>
>
> I'd like to say that launchpad sucks. It's ugly, cumbersome and
> an irritant to use. It doesn't do anything that GitHub isn't
> already doing much better and simpler.
>
> Enabling the issue tracker in the GitHub repo is just two clicks
> away (literally), so there's absolutly no point in adding an external
> tracker.
I think using the issue tracker of github isn't a good idea. Because
tgt is using github just as git repository. The development is based
on this mailing list. If we start to use the isse tracker of github,
other developers will start to send pull requests instead of patch to
the list.
>
> It (Launchpad) is also a real mess to setup and administrate (at
> least if using it on your own servers).
And I cannot see ugly points of launchpad (and we can use public
server). Which part of launchpad do you dislike?
Thanks,
Hitoshi
prev parent reply other threads:[~2014-04-19 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 6:51 RFC: using launchpad as a public issue tracker of tgt Hitoshi Mitake
2014-04-17 10:07 ` Turbo Fredriksson
2014-04-19 5:10 ` Hitoshi Mitake [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738h9ucp4.wl%mitake.hitoshi@gmail.com \
--to=mitake.hitoshi@gmail.com \
--cc=stgt@vger.kernel.org \
--cc=turbo@bayour.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox