Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] New website design for sup - preview
Date: Mon, 12 Apr 2010 10:25:03 +0300	[thread overview]
Message-ID: <1271055277-sup-2613@tilus.net> (raw)
In-Reply-To: <20100411193358.GA12371@urvas>

Rogutės Sparnuotos, 2010-04-11 22:33:
> It looks like what you are proposing is not a new website, but a
> shift in targeted audience.

I don't think it is.  But it might be just me.

> You seem to be addressing the naive user, while forgetting the more
> technical ones.

I don't really agree with this point either.  Except that the features
list is missing configurability & extensibility (keybindings and
hooks).

The features list is an issue worth a conversation.

> There is this sentence at http://sup.rubyforge.org/:
> "
>   The goal of Sup is to become the email client of choice for nerds
>   everywhere.
> "

Thats a real point I think.  IMO "client of choice for nerds" is
relevant and will be for quite some time to come.

> 2. First 700px of the page show nothing useful, except for a screenshot
>    and big letters.

I find the features list, screenshot(s), main navigation and app name
very, very usefull.

> 3. Some very useful, even if technical, pieces information has been lost in
>    conversion:
>    "Handle massive amounts of email."

The point is there, though not with those exact words.  Introduction
starts "Sup is a console-based email client for people with a lot of
email".

>    "
>      you can clone the git repository like so: 
>      git clone git://gitorious.org/sup/mainline.git
>    "

Link to gitorious project page (which is there) is IMO better than
cloning instructions.

> 4. You have replaced the credit to Xapian and RubyMail with the credit to
>    the authors of the website :)

Xapian credit is in the features list, but RubyMail credit is indeed missing.

> As for the GMail guide, wouldn't it be very useful in the wiki?

+1

HOWTOs should IMO be in wiki.  That helps to keep them up to date.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  parent reply	other threads:[~2010-04-12  7:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 15:54 Anirudh Sanjeev
2010-04-11 16:15 ` Ramkumar Ramachandra
2010-04-11 16:39   ` Ben Walton
2010-04-11 17:43   ` Anirudh Sanjeev
2010-04-11 19:33 ` Rogutės Sparnuotos
2010-04-11 19:56   ` Michael Stapelberg
2010-04-11 20:12   ` Anirudh Sanjeev
2010-04-11 22:47     ` rogutes
2010-04-12  5:30       ` Anirudh Sanjeev
2010-04-12  7:25   ` Tero Tilus [this message]
2010-04-11 20:47 ` Philipp
2010-04-11 21:14   ` Anirudh Sanjeev
2010-04-12  7:56   ` Tero Tilus
2010-04-12  6:53 ` Tero Tilus
2010-04-14 12:34   ` William Morgan
2010-04-14 12:32 ` William Morgan
2010-04-14 18:55   ` Anirudh Sanjeev
2010-04-14 18:30 ` Michael Stipicevic
2010-04-11 16:23 Michael Stapelberg

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=1271055277-sup-2613@tilus.net \
    --to=tero@tilus.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