public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: GEORGE BARRICK <gbarrick@kent.edu>
To: cygwin-talk@sourceware.org
Subject: Q: about insectod4.gif
Date: Fri, 23 Aug 2013 17:21:00 -0000	[thread overview]
Message-ID: <CAKST5xOEuHuVH308J2QK=PrBzTXfbwGhV8WRN+28mS=qRz6j5A@mail.gmail.com> (raw)

Q: about insectod4.gif

                                              2013.08.23.17:22:16 UT

Hello cygwin folks,

         I teach at a small branch campus of a university.
I administer my own win7 workstation, and greatly
value cygwin because it gives me access to linux-like
FOSS software.

         Over the past few weeks, I have noticed insectod4.gif
scampering around the cygwin main page when I visit to
download the updated installation program.  Personally,
I think insectod4 is kind of quirky and cute, but it makes
other persons nervous.  I agree, these folks are typically
far less experienced with installing/uninstalling software.
They are often people who cannot even use a browser
when presented with a linux box.  However, they _are_
people from whom I need political support when I advocate
for FOSS software at my institution.

           For my own part, I think that I can probably block
insectod4 on my browser, but this is clearly both a political
and an "image" issue.  Not even "stupid" people should be
led by any means to believe that cygwin might harbor
software that is either buggy or infectious.  All that I am
saying is that it would probably be best for insectod4 _not_
to appear on the cygwin main page.

Thank you,

George                                              g_barrick_at_kent_dot_edu

             reply	other threads:[~2013-08-23 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 17:21 GEORGE BARRICK [this message]
2013-08-23 18:28 ` Christopher Faylor

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='CAKST5xOEuHuVH308J2QK=PrBzTXfbwGhV8WRN+28mS=qRz6j5A@mail.gmail.com' \
    --to=gbarrick@kent.edu \
    --cc=cygwin-talk@cygwin.com \
    --cc=cygwin-talk@sourceware.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).