an example of software design:
i have gone through every menu of 'mailman' in
order to change:
to:
and there are only two place in some two dozen menus
(with suboptions) in which this statement occurs.
yet, after changing the list title and the footer
(the thing at the end of every post) to the corrected
description, the e-mail still includes the old version
in the e-mail header, which cannot be changed back.
it apparently will remain with the comma no matter
what the software settings are for the local list
(it could be a higher up menu not part of the list,
but list creation). point being: the comma may have
to be put back for consistency, as the software has
a design oversight or bug that becomes the determiner
of what works and what does not. kind of like blogs,
and forms of interacting/interfacing ideas online.
On Monday, March 28, 2005, at 08:26 PM, brian carroll wrote:
i have gone through every menu of 'mailman' in
order to change:
"open discussion of art, architecture, and culture"
to:
open discussion of art, architecture and culture"
and there are only two place in some two dozen menus
(with suboptions) in which this statement occurs.
yet, after changing the list title and the footer
(the thing at the end of every post) to the corrected
description, the e-mail still includes the old version
in the e-mail header, which cannot be changed back.
it apparently will remain with the comma no matter
what the software settings are for the local list
(it could be a higher up menu not part of the list,
but list creation). point being: the comma may have
to be put back for consistency, as the software has
a design oversight or bug that becomes the determiner
of what works and what does not. kind of like blogs,
and forms of interacting/interfacing ideas online.
On Monday, March 28, 2005, at 08:26 PM, brian carroll wrote:
To: "open discussion of art, architecture, and culture" <design-l.v2@xxxxxxxxxxxxxxxxx>
Subject: Re: [design] avoiding the blog
Reply-To: "open discussion of art, architecture and culture"