21 Mar
2007
21 Mar
'07
2:44 p.m.
Jay West wrote:
That way, they don't pay for updates they
don't receive (if
the particular tree they are tracking doesn't change much). They could
even set parameters like, only send me a cd if there are more than 20
files updated, or until 6 months passes with some updates at least -
whichever comes first.
That works too, I guess - anything that doesn't increase the burden on
whoever's admin for the system - and things like that can all be automated.
I've been wanting to have a separate list for
classiccmp policy
discussion. That may keep some of the more heated discussions off the
main list. If people buy into my idea for the global
software/classicdata repository I'd be happy to set up another list for
discussion of that record format, techniques, design discussion, etc.
Well that works for me (and count me in as a list member).
That all being said, it's also no big deal if
someone wants the
classiccmp server to host a small list for some other purpose.
You know, I've been meaning to ask - do you plan to ever offer mailing list
services for vintage computing matters via on classiccmp.org (in a similar way
to what you already do with web space)?
Of course I have no idea what the security implications would be :-) It was
just a general thought as another potential service for classiccmp.org one
day. (I joined a Yahoo-hosted list for one manufacturer's vintage hardware
recently, and my immediate thought was that boy, does yahoo suck for such things!)
Fairly soon we'll need to have a discussion about
the classiccmp server
hardware, it's definitely time for an upgrade. Disk at the very least. I
hate going through the server hardware discussion on the list, but it's
probably not something that needs another separate list? I dunno. Open
to ideas.
Not sure. Depends on whether you've received any negative feedback in the past
when there have been server discussions on here. Maybe people just silently
grit their teeth though ;)
cheers
J.