Subject:
|
LEGO Direct ng possibilities (was: Re: Cleaning up the main homepage)
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Mon, 10 Apr 2000 00:36:48 GMT
|
Highlighted:
|
(details)
|
Viewed:
|
1500 times
|
| |
|
|
In lugnet.admin.general, Scott Arthur writes:
> In lugnet.admin.general, Manfred Moolhuysen writes:
> > I have a similar problem: It is rather difficult to find the messages
> > from Brad Justus between the very many reactions. Would it be feasable
> > to copy his VIM's (Very Importand Messages) to a special area ?
>
> He needs his own group. Every time he makes a pronouncement it cloggs the
> system up for days.
OK, let's talk a bit about some possible solutions... First, let's nail down
the problem: The problem isn't that the system is clogged up per se (it's
always clogged up :) but that Brad's announcements/pronouncements are so
quickly lost among the clogging up,...yes? Thus it would be helpful not only
if there were a way to find Brad's messages among the resulting clamour but
also if there were a way to find them as fast as possible as they appear...?
(I'll take this problem specification forward assuming that's the problem.)
So, what kind of 'his own group' is best?
We could set something up under .announce -- perhaps
lugnet.announce.lego-direct
which people could subscribe to for instant email delivery just as they
currently do for the other .announce.* groups. Or we could set up something
under .dear-lego, perhaps
lugnet.dear-lego.direct.announce
or
lugnet.dear-lego.lego-direct.announce
(or some other name?) which people could subscribe to the same way.
Or we could set up a whole new ng hierarchy for LEGO Direct outside of
lugnet.dear-lego, perhaps
lugnet.lego-direct
and
lugnet.lego-direct.announce
and later
lugnet.lego-direct.[future-expansion]
Or, since Brad has said he'll be encouraging other divisions of LEGO to
participate from time to time, we could create a whole new ng hierarchy for
the whole of TLC itself (in terms of the company), with LEGO Direct as a
subgroup of this -- perhaps:
lugnet.lego.announce
lugnet.lego.direct
lugnet.lego.direct.announce
lugnet.lego.direct.[future-expansion]
lugnet.lego.[future-expansion]
Other possibilites? Here's an older thread (highly related) with more ideas:
http://www.lugnet.com/admin/general/?n=3827
Some questions
--------------
Regarding lugnet.announce.lego-direct:
- Does the .announce portion suggest an appropriate amount of immediacy and/
or urgency and/or importance? (it should)
- Does the .lego-direct appendage suggest that these are announcements (a)
_about_ LEGO Direct or (b) _from_ LEGO Direct? (not a showstopper if it's
confusing, but a little better if it suggests the latter)
Regarding lugnet.dear-lego.lego-direct.announce:
- Is that too ng name too icky and long? And do the hyphens (-) get visually
confused with the periods (.)?
- Does it seem weird to have .announce at the end when the other announcements
groups are at the front?
- If the LEGO Direct channel develops into a fertile, productive two-way
channel, does the 'dear-lego' part just get in the way in the long run?
Regarding lugnet.lego-direct.* & lugnet.lego-direct.announce
- (Same question about .announce at the end -- is it too strange?) In the
case of a new .lego-direct.* ng tree, would you prefer
(a) lugnet.lego-direct.announce and
lugnet.lego-direct
or
(b) lugnet.announce.lego-direct and
lugnet.lego-direct
? In both cases, posts to the announcements area would require followups
to the main discussion area (i.e., lugnet.lego-direct).
Regarding lugnet.lego.* & lugnet.lego.direct.announce:
- (Same question again about .announce) Would you prefer
(a) lugnet.lego.direct.announce and
lugnet.lego.direct
or
(b) lugnet.announce.lego-direct and
lugnet.lego.direct
or
(c) lugnet.announce.lego.direct and
lugnet.lego.direct
----------
I'm leaning toward the third main option the most strongly (the .lego.*
ng subtree), even though it's the most radical of the three main options.
The reason is that it would be a "clean break" from past confusion and would
also keep .dear-lego back to how it was originally intended -- as a one-way
open-letter-writing area (something I think we'll all probably still want to
use some day or another even when/if there is a full two-way channel in
another area).
James Brown also suggested creating a .faq subgroup of .lego.*:
http://www.lugnet.com/admin/general/?n=3953
Anyway, if you like the .lego.* idea, we can always worry about all the myriad
possibilites of subgroups later, adding them when needed. Probably we'd just
start out with 3 groups:
lugnet.lego -- anything relating to LEGO as a company (as opposed to
specific products).
lugnet.lego.announce -- announcements from the LEGO Company -- either
posted directly by someone working for LEGO, or copies of LEGO press
releases posted by the community; this would be a very low-bandwidth
group, possibly with restricted posting access (if needed), but which
anyone/everyone could read and subscribe to for instant email delivery.
lugnet.lego.direct -- anything relating to LEGO Direct (this can be
expanded to handle additional subgroups if needed).
--Todd
|
|
Message has 1 Reply:
Message is in Reply To:
111 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- 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
|
|
|
|
