Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Wed, 04 Nov 2009 11:00:43 +0100	[thread overview]
Message-ID: <1257328487-sup-8593@midna.zekjur.net> (raw)
In-Reply-To: <1257327692-sup-7174@elly>

Hi,

Excerpts from Israel Herraiz's message of Mi Nov 04 10:44:02 +0100 2009:
> I have been using Trac since a couple of years now, and it is sensible
> to spam, ok, but you can always delete comments, tickets, or anything
I am referring to trac 0.11.5, which does not have a possibility to delete
comments or tickets without installing a third-party plugin (which is
hard to use because you have to use ticket IDs). If I am wrong, please tell me
where they hid the possibility, so I don’t need the plugin anymore.

> in general, and force people to register to post comments or tickets,
> to fight against spam.
I consider forcing people to register to post comments/tickets as the end of
bug reports for my project. I personally would only register at a bugtracker if
the bug was *really* important and there would be *no* other possibility to
contact the author of the software. However, I want to get every bugreport for
my software and thus lower the requirements for users to actually help me
improve my software by submitting bugreports.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2009-11-04 10:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 21:52 Nicolas Pouillard
2009-11-02  1:17 ` Kevin Riggle
2009-11-02  8:30   ` Nicolas Pouillard
2009-11-02  7:01 ` Tero Tilus
2009-11-02  8:46   ` Nicolas Pouillard
2009-11-02  9:50     ` Tero Tilus
2009-11-02 14:58       ` William Morgan
2009-11-02 14:53   ` William Morgan
2009-11-02 17:38     ` Nicolas Pouillard
2009-11-02 14:50 ` William Morgan
2009-11-02 17:47   ` Nicolas Pouillard
2009-11-02 19:20     ` William Morgan
2009-11-02 20:23       ` Nicolas Pouillard
2009-11-02 20:40   ` Joe Wölfel
2009-11-02 21:49     ` Nicolas Pouillard
2009-11-03 14:50   ` Mike Kelly
2009-11-03 15:16     ` William Morgan
2009-11-03 15:34       ` Mike Kelly
2009-11-03 16:49         ` Reid Thompson
2009-11-03 17:03           ` Reid Thompson
2009-11-03 18:04           ` William Morgan
2009-11-03 19:30             ` Reid Thompson
2009-11-03 16:20       ` Sebastian Schwarz
2009-11-03 17:03         ` Daemian Mack
2009-11-03 18:06           ` Mike Kelly
2009-11-03 17:25         ` William Morgan
2009-11-03 17:37           ` Dan Falcone
2009-11-03 18:33         ` Tero Tilus
2009-11-03 23:11 ` Jim Cheetham
2009-11-04  0:07   ` Mike Kelly
2009-11-04  9:38     ` Michael Stapelberg
2009-11-04  9:44       ` Israel Herraiz
2009-11-04 10:00         ` Michael Stapelberg [this message]
2009-11-04 10:05           ` Israel Herraiz
2009-11-04 23:40             ` Israel Herraiz

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=1257328487-sup-8593@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox