public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hugh Sasse <hgs@dmu.ac.uk>
To: Dave Korn <dave.korn@artimi.com>
Cc: cygwin@cygwin.com
Subject: RE: setup.exe needs package name selection filter
Date: Fri, 20 Jun 2008 12:38:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.64.0806201235530.25299@brains.eng.cse.dmu.ac.uk> (raw)
In-Reply-To: <000501c8d2c7$68afb690$2708a8c0@CAM.ARTIMI.COM>

On Fri, 20 Jun 2008, Dave Korn wrote:

> reikred wrote on 20 June 2008 02:08:
> 
> > Christopher Faylor wrote:
> >> 
> >> Yes.  It's called
> >>
> "make-setup.exe-demands-and-then-sit-back-and-wait-for-people-to-implement-y
> our-profound-ideas@cygwin.com"
> >> 
> >> cgf
> >> 
        [...]
> > 
> > Please read it in the spirit of a suggestion of a feature
> > that I think could be VERY useful to a lot of people, not
> > just the 1% of cygwin users that know how to implement it.
> > 
> > rr
> 
> 
>   It's definitely a good suggestion, quite possibly a great suggestion.
        [...]
>   I think the point that cgf is getting at is that there is no shortage of
> suggestions or good ideas or enhancement requests or wish lists nor any
> difficulty in coming up with new ones.  But without a bit of getting-it-done
> elbow grease, a suggestion is really very little use on its own.

This is a recurring problem for the Free Software movement.  People
want Free Software to spread, and there are efforts, such as the
attempt to get a record number of downloads for Firefox 3, as
promotional activities.  But a constant theme is that suggestions
from users are not welcomed; instead they provoke various forms of
the response: "If you want it, send a patch".  This fails to
recognise that one reason programmers don't like maintenance
programming is that reading code is more difficult than writing it.
This is a pre-requisite for changing the code.  It also fails to
recognise that a user for one project who is completely unfamiliar
with the code base, may be busy contributing to other projects, and
that some suggestions may be very much easier for someone familiar
with the code than someone who is not.  Also, if users' suggestions
are (effectively) dismissed in this way, it will prevent the use of
Free Software by non-programmers, which runs counter to the desire
for it to spread.  Most of the potential users of Free Software are
non-programmers.  [Yes, this is less so for Cygwin.]

Clearly decisions are not made in the same way as for a software
business, where finance is fundamental, but I'd suggest that unless
the needs of users are given greater status, then Free Software
advocacy will be somewhat hobbled.  But as this is a cultural problem,
and there is no immediately obvious technical solution, I'm unsure
how one might practically improve the situation.  I do think more
thought should be given to it, though.

> 
>     cheers,
>       DaveK

        Hugh

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2008-06-20 12:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  0:57 reikred
2008-06-20  1:02 ` wynfield
2008-06-20  1:08   ` Christopher Faylor
2008-06-20  2:07     ` reikred
2008-06-20 12:23       ` Dave Korn
2008-06-20 12:38         ` Hugh Sasse [this message]
2008-06-20 12:44           ` Mark J. Reed
2008-06-20 13:33             ` Eric Blake
2008-06-20 14:29               ` Mark J. Reed
2008-06-20 18:09                 ` Larry Hall (Cygwin)
2008-06-20 18:25                   ` Mark J. Reed
2008-06-20 23:07                   ` Christopher Faylor
2008-06-21  2:46                     ` Mark J. Reed
2008-06-23 12:02                     ` Hugh Sasse
2008-06-24 11:16                       ` Reini Urban
2008-06-24 11:49                         ` Hugh Sasse
2008-06-24 11:53                           ` Reini Urban
2008-06-24 14:59                           ` Christopher Faylor
2008-06-24 18:55                             ` Hugh Sasse
2008-06-21 13:04         ` NightStrike
2008-06-21 13:42           ` 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=Pine.GSO.4.64.0806201235530.25299@brains.eng.cse.dmu.ac.uk \
    --to=hgs@dmu.ac.uk \
    --cc=cygwin@cygwin.com \
    --cc=dave.korn@artimi.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).