From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ram Rachum <cool-rr@cool-rr.com>, git@vger.kernel.org
Subject: Re: Gui criticism
Date: Sat, 05 Dec 2009 12:14:54 -0800 [thread overview]
Message-ID: <7v3a3prxdt.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <94a0d4530912051137u682a3a99ved9d19338b881b13@mail.gmail.com> (Felipe Contreras's message of "Sat\, 5 Dec 2009 21\:37\:52 +0200")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> I don't think the mailing list is the best place for this, that's why
> I just started a project in SourceForge, so that users can post these
> kinds of issues in the ideatorrent:
> https://sourceforge.net/apps/ideatorrent/git-ux/ideatorrent/
Two issues and a half offhand after entering one:
- I found the experience of adding an "idea" too clunky and slow.
Writing a well thought out e-mail can be done in the same time.
- Although enforcing a minimum structure of "idea" description is a good
thing to do, I found the current structure presented by that web page
lacks focus. It has problem description and a rather broad and vague
"idea", and it feels to me that it is promoting entering any garbage
without discussing feasibility, "pros-and-cons" or necessary steps to
achieve a particular goal.
- The largest issue of this kind of system is who will be moderating and
how capable they are.
next prev parent reply other threads:[~2009-12-05 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 18:51 Gui criticism Ram Rachum
2009-12-05 19:25 ` Michael J Gruber
2009-12-05 19:37 ` Felipe Contreras
2009-12-05 19:51 ` Martin Langhoff
2009-12-05 20:14 ` Junio C Hamano [this message]
2009-12-05 20:25 ` Felipe Contreras
2009-12-05 20:41 ` Junio C Hamano
2009-12-08 7:12 ` Marco Costalba
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=7v3a3prxdt.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=cool-rr@cool-rr.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.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