From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: trac integration
Date: Wed, 28 Sep 2016 01:21:50 +0200 [thread overview]
Message-ID: <CAHmME9rrMKSRjRYPYhH5yWnEZHyOq4Luua9V9Z0CmLJBo+3Wqg@mail.gmail.com> (raw)
In-Reply-To: <2e24d64b-6b90-d88d-2e4b-82f852230663@hupie.com>
Hi Ferry,
I suppose this would be something for the contrib/ section. I wouldn't
be all together opposed to filling this directory with lots of
different integrations for various project management applications,
web servers, and so forth, but one pitfall I've seen numerous times in
my projects and others is that these go stale and get abandoned fairly
quickly, but nobody realizes because it's alongside the active
project. On the other hand, when it's in a separate repo, it's easier
to see how active it is and what the status is. So, I see both the
advantages of it and disadvantages to integrating it into the cgit
repository.
If we do wind up keeping it in its own repository and not integrating
it into cgit's, of course I'd be happy to host this on git.zx2c4.com
alongside cgit, and give you ownership over the repo.
Jason
prev parent reply other threads:[~2016-09-27 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 20:56 mailings
2016-09-27 23:21 ` Jason [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=CAHmME9rrMKSRjRYPYhH5yWnEZHyOq4Luua9V9Z0CmLJBo+3Wqg@mail.gmail.com \
--to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).