unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: guild hall update
Date: Mon, 22 Aug 2011 22:49:32 +0200	[thread overview]
Message-ID: <87fwkt6ujn.fsf@ambire.localdomain> (raw)
In-Reply-To: <87wre5jv0r.fsf@pobox.com> (Andy Wingo's message of "Mon, 22 Aug 2011 18:00:52 +0200")

() Andy Wingo <wingo@pobox.com>
() Mon, 22 Aug 2011 18:00:52 +0200

   Another big change is that I renamed the package.  The problem was
   that the package itself isn't really a "guild hall" -- it marks you as
   a member of the guild, giving you access to various guild halls on the
   net.  After some hemming and hawwing I renamed it to "sigil" -- a
   graphic sign that marks you as a member of some group.

I kind of dislike the "marked as a member of some group" meme, whether
expressed as "guild" or "sigil".  Traditionally, guilds were irascibly
exclusive, subverting competition, introducing proprietary "extensions"
and "trade marks", and (ultimately) capturing and controlling the
prevalent regulatory regime.  (Side note: For a contemporary example at
grander / graver scale, see U.S. SEC MUI memory holing.)  It bothers me
that there is a "join and (only then you will) be cool" mindset at all.

The nice property of tools (and objects, as opposed to organizations, in
general, i suppose) is that people do not belong to them, and can share
them.  If the term "tool" (e.g., "guile-tool") is too boring, might i
suggest something exciting but still tool-ish, like "sword" or "club" (or
"cudgel" :-D) or "wand" or "knife" or "blade" or "zapper"?  Plenty of
acronym fodder, there, as well.  Or just go w/ acronyms directly: "tool
of choice" => "toc", "advanced package tool" => "apt", etc.

BTW, I think the long word "guile-package-manager" is fine, too.  You can
alias "sigil" to that, as that strikes your fancy, and others can do the
same, or different, as it strikes theirs.

   [...]

Looks pretty cool; keep up the good work!



  parent reply	other threads:[~2011-08-22 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 16:00 guild hall update Andy Wingo
2011-08-22 20:32 ` Ludovic Courtès
2011-08-22 20:47   ` Andy Wingo
2011-08-22 20:49 ` Thien-Thi Nguyen [this message]
2012-01-03 16:35   ` Andy Wingo
2012-01-03 18:00     ` Thien-Thi Nguyen
2011-08-23 20:31 ` Andreas Rottmann
2011-09-04 12:35 ` Ludovic Courtès

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=87fwkt6ujn.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).