Subject:
|
RE: lugnet.cad hierarhcy
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Thu, 29 Apr 1999 14:09:11 GMT
|
Viewed:
|
807 times
|
| |
| |
In lugnet.cad.dev, ipapp@GEOMETRIA.hu (Papp Imre) writes:
> I agree with that dat postings and comments should be closely related.
> Why isn't enough simply decide that comments on dat postings should be
> sent back strait to cad.dat?
Because then .cad.dat would become too clogged with multiple types of
discussions -- models, parts, primitives, ideas, etc. And people have
different interests. There is great utility in having focused groups for
each of these, which people can mix & match to suit their own personal
needs.
> This way every new dat posting (part, model, etc) could start a new
> thread and comments/discussion could follow it in the thread. But in
> this case replies would be messages not containing dat file at all, and
> this could hurt the rule that cad.dat serves only for posting dat
> files.
The rule that .cad.dat about only posting DAT files is really basically just
a legacy rule, going back to when the group was created last October. The
group was literally created overnight (right after PaulG released the first
LDLITE 1.0):
http://www.lugnet.com/news/display.cgi?lugnet.cad:49
http://www.lugnet.com/news/display.cgi?lugnet.cad.dat:1
In the haste to create the ng, not much thought was put into it. Also, at
the time, there was really no way to forsee what an integrated role the ng
would end up playing in the discussions. The original thought was that it
would just to be a place to post models, and maybe occasionally someone
might make a follow-up posting. Also, at the time .cad.dat was christened,
there was only one other group in the .cad.* hierarchy.
Anyway, to make a long story short, the rule about having to post DAT
content in .cad.dat certainly isn't a sacred rule -- it's just the way it
happened to be set up originally.
--Todd
|
|
Message is in Reply To:
2 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|