Subject:
|
Re: Mailing list gateways
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Tue, 26 Jan 1999 00:37:29 GMT
|
Viewed:
|
2310 times
|
| |
|
|
sparre@sys-323.risoe.dk (Jacob Sparre Andersen) writes:
> > I don't agree here. To me, "users" implies they are using a specific
> > program or package. I'd rather have
> > lugnet.cad <- same as always
> > lugnet.cad.l-cad <- discussion specific to parts updates. Maybe
> > program support.
>
> Todd has got me away from the lugnet.cad.users idea. Lets
> keep the plain lugnet.cad for the general stuff.
>
> I don't like to use the name l-cad for the group name. We
> can just as well chose one (or two) that makes sense without
> knowledge of the history of the group.
Apart from .l-cad being a legacy thing, both CAD and LEGO are there twice in
the full expansion of lugnet.cad.l-cad:
l u g net . cad . l - cad
| | | ||| ||| | |||
LEGO Users Group Network CAD LEGO CAD
So maybe it's a little bit redundant. :)
> Current ideas for the part and programming stuff:
>
> lugnet.cad.development
> lugnet.cad.programming (maybe together with lugnet.cad.parts)
Although the ng name would be too long, wouldn't .programing be a child of
development? Programming is always development (hopefully :), but development
isn't always programming.
What are all the types of "development" thingies talked about and decided on in
L-CAD? Parts, programming, testing parts, testing code, feedback, . . . other?
Here are some more random mostly-overlapping ideas -- just ideas:
long alternatives short alternatives
------------------------------------- ------------------------
lugnet.cad.software lugnet.cad.sw
lugnet.cad.software.development lugnet.cad.sw.dev
lugnet.cad.applications lugnet.cad.apps
lugnet.cad.applications.development lugnet.cad.apps.dev
lugnet.cad.parts.development lugnet.cad.parts.dev
lugnet.cad.elements.development lugnet.cad.elements.dev
> > > Can/should we transfer the L-CAD archives to the newsgroups?
> >
> > Yes, if they won't flood the current messages (that is, they can be
> > transferred directly to the archives).
>
> They will show up as "unread" in the newsgroup they are
> posted to. If we post them to one of the new groups, the
> problem will be reduced a bit.
There are at least a couple (err, three?) ways to do it --
1. Put them in straight into the archives but not into the newsgroup (in other
words, into the newsgroup, but pre-expired).
2. Put them in as regular articles as soon as the group is created and let
them go out to everyone via e-mail (probably a very bad idea :-).
3. Put them in as regular articles as soon as the group is created, but make
sure not to e-mail them to people subscribed to the group via e-mail.
--Todd
|
|
Message has 1 Reply:
 | | Re: Mailing list gateways
|
| (...) How about these real candidates for the lugnet.cad.* hierarchy? lugnet.cad Unchanged, except for possible loss of content to groups below lugnet.cad.dat Unchanged lugnet.cad.dev.parts Parts development and publishing lugnet.cad.dev.apps (...) (26 years ago, 26-Jan-99, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Mailing list gateways
|
| (...) [...] (...) I have, but we can just as well wait - and work on the suggestion until then. (...) Todd has got me away from the lugnet.cad.users idea. Lets keep the plain lugnet.cad for the general stuff. I don't like to use the name l-cad for (...) (26 years ago, 25-Jan-99, to lugnet.admin.general)
|
80 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
