From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: ideas for the web site
Date: Fri, 11 Feb 2011 15:08:50 +0100 [thread overview]
Message-ID: <87pqqyu0i5.fsf@gnu.org> (raw)
In-Reply-To: AANLkTimUKg4X+DC5BgBiG6AJ6C42_B4XxTeUSuYtX36H@mail.gmail.com
Hi Julian!
These all sound like great ideas to me! You normally have access to the
web page repository, so feel free to commit your changes there and just
send a note so we can check what’s up there.
IMO the parts discussing features or technical merits should be really
concise. It could even be a simple bullet list with no sentences, or at
least presented in such a way that the reader can quickly skim over it.
We may also want a paragraph, or a slogan, regarding extensibility and
user freedom. Like “enhancing software freedom”, or “practical software
freedom”, something like that[*]. ;-)
Do you think you’ll be able to work on it by Tuesday? :-)
Thanks,
Ludo’.
[*] It may sound presumptuous, but hey, that’s marketing.
next prev parent reply other threads:[~2011-02-11 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 5:44 ideas for the web site Julian Graham
2011-02-11 8:42 ` Andy Wingo
2011-02-11 14:08 ` Ludovic Courtès [this message]
2011-02-11 16:23 ` Julian Graham
2011-02-12 10:12 ` Ludovic Courtès
2011-02-13 0:32 ` Julian Graham
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pqqyu0i5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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.
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).