Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message
Date: Sun, 01 Nov 2009 08:19:23 -0800	[thread overview]
Message-ID: <1257091305-sup-4606@masanjin.net> (raw)
In-Reply-To: <1257088992-sup-5165@peray>

Reformatted excerpts from Nicolas Pouillard's message of 2009-11-01:
> Have strong points against Ditz or this is also a lake of energy?

Both, really. Ditz was an experiment, and after using it for a while I
decided it was more trouble than it was worth. I also realized that I
*did* want a centralized web site after all, and not necessarily a
complicated distributed thing, both because I want non-technical users
to be able to submit bug reports, and because development, in reality,
*is* centralized.

(I had been doing some work on Sheila, which would've provided a web
frontent that people could use to submit bug reports, but even that
wouldn't be quite what I wanted.)

Having thought about it for a while, I think what I *really* want for
Sup is something that tracks bugs/feature requests at the feature branch
level (i.e. assumes that each feature branch provides a new feature or a
bugfix), has a web interface for non-technical users to submit bug
reports and for developers to browse/modify state on bugs, and which
uses email for discussion, like I did with Whisper. (And I would be fine
with it being git-specific.)

I am now spending all my energy trying to keep myself from building such 
a thing.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-11-01 16:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 17:14 Jon Dugan
2009-10-28 20:05 ` Nicolas Pouillard
2009-10-28 20:22   ` Jon Dugan
2009-10-29 10:29     ` Nicolas Pouillard
2009-10-30 21:53     ` William Morgan
2009-10-31 11:28       ` Tero Tilus
2009-11-01 14:39         ` William Morgan
2009-11-01 15:24           ` Nicolas Pouillard
2009-11-01 16:19             ` William Morgan [this message]
2009-11-01 16:48               ` Nicolas Pouillard
2009-11-01 17:30                 ` William Morgan
2009-11-01 17:49                   ` Nicolas Pouillard
2009-11-01 20:30           ` rick.tessner
2009-11-02  7:19             ` Tero Tilus
2009-11-02 15:07             ` William Morgan
2009-11-02  7:25           ` [sup-talk] Sup Issues Task Force (SITF) Tero Tilus
2009-11-02  9:14             ` Israel Herraiz
2009-11-02 15:08             ` William Morgan
2009-11-03  1:45               ` Tero Tilus
     [not found]       ` <1256940689-sup-888@arrakis.es.net>
2009-11-01 14:45         ` [sup-talk] [PATCH] minor nits in exception apology message William Morgan

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=1257091305-sup-4606@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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