From: Karsten Heymann <kheymann@blue-cable.net>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Co-maintainer, a least for some time?
Date: Wed, 19 May 2010 20:08:15 +0200 [thread overview]
Message-ID: <4BF4290F.9030600@blue-cable.net> (raw)
In-Reply-To: <36D3D817-7AE4-4E18-A71B-9675672CC077@gmail.com>
Hi,
Am 19.05.2010 17:46, schrieb Carsten Dominik:
> I think an issue-tracking system would be great. And if there are
> other people besides John who want to take up individual issues, I am
> sure this would be good.
One solution would be to switch the git repository to github.com and use
it's integrates issues functionality. From their site:
Issues
GitHub Issues adds lightweight issue tracking tightly integrated with
your repository. Close issues from commit messages, let users label
and vote on issues and drag & drop issues to priorize.
See it in action at
http://github.com/splitbrain/dokuwiki-plugin-data/issues
Maybe it's worth a look.
Yours
Karsten
next prev parent reply other threads:[~2010-05-19 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 8:08 Co-maintainer, a least for some time? Carsten Dominik
2010-05-19 12:38 ` Bastien
2010-05-19 13:17 ` Dan Davison
2010-05-19 14:28 ` Eric Schulte
2010-05-19 15:49 ` Carsten Dominik
2010-05-19 15:46 ` Carsten Dominik
2010-05-19 18:08 ` Karsten Heymann [this message]
2010-05-19 18:15 ` Matthew Jones
2010-05-19 18:51 ` Anthony Lander
2010-05-19 21:23 ` Carsten Dominik
2010-05-19 21:39 ` Anthony Lander
2010-05-19 21:22 ` Carsten Dominik
2010-05-19 22:30 ` Nick Dokos
2010-05-19 16:24 ` Carsten Dominik
2010-05-19 17:01 ` Thomas S. Dye
2010-05-19 21:41 ` Bernt Hansen
2010-05-20 14:22 ` David Maus
2010-05-20 15:19 ` Carsten Dominik
2010-05-20 16:27 ` Matt Lundin
2010-05-20 21:26 ` John Wiegley
2010-05-20 15:17 ` Matt Lundin
[not found] <4bf55eb1.216ae50a.74d1.0bfeSMTPIN_ADDED@mx.google.com>
2010-05-20 17:52 ` Thomas Renkert
2010-05-20 21:34 ` John Wiegley
2010-05-20 21:57 ` Greg Newman
2010-05-20 22:24 ` John Wiegley
2010-05-20 22:52 ` Greg Newman
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: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF4290F.9030600@blue-cable.net \
--to=kheymann@blue-cable.net \
--cc=emacs-orgmode@gnu.org \
/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://git.savannah.gnu.org/cgit/emacs/org-mode.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).