>>>> Stephen J Turnbull writes:
>>>> "David" == David Masterson <dmaster(a)synopsys.com>
writes:
>>>> Stephen J Turnbull writes:
>>>> "Simon" == Simon Josefsson <jas(a)extundo.com> writes:
Simon> Looking at the Makefile in the CVS directory for the
Simon> package [is the best/only way to find maintainers]?
>> Yes, I think that's true. We should do something about
it.
David> Is there anything wrong with rendering the list of known
David> packages and their maintainers *somewhere* on the
David>
xemacs.org web-page?
In one sense, nothing, because it's already done: the known
packages
are in the Packages node of the XEmacs Users' Guide, and the
maintainer address is $PACKAGE-maintainer(a)xemacs.org. Also, that's
exactly what I suggested in the first line you cut, no?
If I did, I didn't realize it. Mea culpa.
The administrative holdups on getting it done are
1) privacy/spam: we don't want private addresses published on
the
web page without permission of the person. So we need to filter
personal addresses to ï¼ xemacs.org addresses.
2) We probably do want real names (or net aliases for the dogs among
us)
3) (Adrian's point) Since this information is already available in
many places, we want to eliminate redundancy so there will be
half a chance of keeping it up to date and accurate.
All good reasons. My suggestion was a mild one that I thought might
_eventually_ make it easier for people to see what packages XEmacs has
available and what levels they are at.
Perhaps we can do
package-lists-maintainer: dmaster(a)synopsys.com
hm?
The "synopsys" address is my work address and I wouldn't want
something like this going through there. However, I may volunteer for
it around the beginning of the year using my home system. I've had a
number of things going on lately including problems with my home
system that I think I just got ironed out. December will be studying
the configuration and security of Linux on my home system and then I
may finally be ready to get involved. I may be a 20 year programmer
of Unix, but I feel like a novice when it comes to making a system
visible on the Internet and keeping it safe from spammers and
crackers. I feel, though, that it's better to get it (close to) right
the first time than secure it later.
--
David Masterson David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer Synopsys, Inc.
Software Engineering Sunnyvale, CA