Conference azur::mcc

1.0. "MCC developer's notesfile" by TOOK::P_SAVAGE (Peter Savage) Thu Aug 24 1989 09:47

    PURPOSE OF THE MCC NOTES FILE

       The MCC notes file provides management module developers a
       place to discuss development issues with the T1.0.0 toolkit.
       This conference also provides developers with a place to share
       work-arounds and code.  This notes file will not replace the
       NACQAR system but it will allow users without access to the QAR
       system with a way of communicating problems to the DECmcc developers.

       The notes file will be for in-house use only. The information in
       this notes file will only be available to third party developers
       through the third party program team only.


    MEMBERSHIP IN CONFERENCE

       Membership in the conference will be open to anyone.

       Since membership will be open the moderators will monitor all
       "flames".  The conference is here to benefit the members, not for
       airing grievances. Where appropriate, some notes will be moved to
       other internal notes files.

       The DECmcc developement team will monitor this notes file 
       so that questions get answered.


    CONFERENCE CONTENTS AND RESTRICTIONS

       Before entering a new note it is the responsibility of the person
       entering the note to determine if a new notes is needed. The use
       of keywords and a consistent format for the subject of each note
       will help scanning the conference to determine if a new note is
       needed.

       It is not a goal of the conference to duplicate information that
       can be easily obtained from other sources. The purpose is to make
       it easier to find or obtain information regarding the field test
       kit only. 

       An example of how to use the conference would be when a problem
       is encountered using a specific common routine, the problem is
       not listed in the release notes, the information in the SRM does
       not clarify the question, and the "Guide to writing an AM" does
       not have an example or specify how to use the routine. In this
       case the problem would be entered in the notes file along with
       the code segment, and a request for clarification. 


    PREDEFINED NOTES

       1 - Introduction to the notes file and moderator messages
       2 - Keywords (as new keywords are added they are documented here)
       3 - T1.0.0 upgrade announcements 
       4 - Related Notes Files (pointers to other notes files)
       5 - Documentation Descriptions 
       6 - Introductions


    KEYWORD NOTE AND USAGE    

       The Keywords topic is to be used whenever a new keyword is
       defined for the conference. A new entry is to be added to the
       Keyword note. The entry should include in the subject line the
       new keyword:

            KEYWORD - Groups

       And the content of the entry should include a quick definition of
       what the keyword means:

            Groups refers to attribute groups. The Keyword is to be 
            used to flag notes dealing with the support of attribute
            groups; problems, questions, and information.

       The use of keywords is strongly encouraged. This will help
       conference users in searching for information and getting full
       benefit of the Notes capabilities.


    MODERATOR RESPONSIBILITIES

       The moderator(s) of the conference will be responsible for
       purging duplicate messages, monitoring/removing/moving
       inappropriate topics, and periodically purging old notes.

       Initially the moderators for the conference will be Peter Savage,
       Jill Callander, and Steve Wong.

    TOPIC SUBJECT LINE FORMAT

       To help make it easier to find information in the notes file. The
       topic of each note should follow a simple format.

       Format:  TOPIC CODE - [Component - ] Topic Title

       TOPIC CODES: ANNOUNCE
                    CLOSE TOPIC
                    INFO
                    KEYWORD
                    PROBLEM
                    QUESTION
                    REQUEST
                    SAMPLE
                    SOLUTION

       New topic codes will be added as they are needed. 

       The Component is the component for which the note applies. If a
       topic does not relate to a specific implementation then the
       Component field is not supplied. 

       The Topic Title is a short description of the topic.

       Example:

       Topic Author       Date         Repl  Title
       ----------------------------------------------------------------------
         1   TOOK::USER1  26-AUG-1989     0  INFO-Conference Use    
         2   TOOK::USER2  29-AUG-1989     1  KEYWORD - definitions
         3   TOOK::USER3  13-SEP-1989     9  ANNOUNCE- T1.0.0 upgrades
         :    :      :        :           :     :
         32  TOOK::USER3  17-AUG-1989     3  QUESTION- use of descriptors
            
       Topic Author       Date         Repl  Title
       ----------------------------------------------------------------------
         32  TOOK::USER3  17-AUG-1989     3  QUESTION- use of descriptors
             TOOK::USER1  26-AUG-1989  32.1  INFO- set version to 1         
             TOOK::USER2  29-AUG-1989  32.2  SOLUTION- only use MCC descrips 
             TOOK::USER3  29-AUG-1989  32.3  CLOSE TOPIC


    CONFERENCE FILENAME AND LOCATION

       The MCC notes file will be located on the TOOK cluster. 

            add entry TOOK::MCC.NOTE


    

    
    This is a bit redundant but....
    
    A lot of the questions being asked require a bit of understanding
    of who is asking the question and why they need the answer.
        
    It would be appreciated if people would place introductions in note
    number 6. Developers find refering to these introductions useful
    in answering notes. If we understand what you are working on
    it helps us to provide you with the right type of information.
    

When entering notes into the conference please note that a significant number
of the members of this conference regularly printed out new notes, or have
them delievered via mail. The posting of long notes (in excess of 5-10 pages
or non-ascii input) is considered a burden.

Please limit all notes to ascii text where possible. If you have a postscript
file or a map file please post a pointer to a public directory where it can
be copied from. Your cooperation in this measure will help us save an awful 
lot of trees.

MODERATOR

    
    
    I think it would be extremely helpful if the moderators would examine
    each new note for the appropriateness and usefulness of the note title.
    
    If a note does not have a descriptive enough title, the mods should
    change the title to something meaningful to the readership.
    
    Given the recent comments about dividing the conference into two, it
    seems clear that many are frustated by the poor note titles, and
    searching through the conference is extremely difficult.
    
    2�,
    
    Marc
                      

I like the idea, but unluckily I am the only active moderator. Along with
moderating this conference I am the project lead for the FCL PM, Notification
"PM", Notifcation FM, as well as the developer of the targetting functions
in the v1.2 notification FM and general developer....

Reading the conference takes alot of time, if there is someone out there who
feels that they have a bit of time on there hands I would be willing to
consider a (maybe rotating) moderator/user position. This person could help
not in getting the notes answered (I nudge late responses and answer those
that I have the experience with), but in helping append keywords to
the notes, and "fixing" titles.

If there are any volunteers please contact me through mail, or call.

thanks
jill

    
    Just wanted to introduce to you all a new player. Erik Mintz is
    the Ultrix/system integration project lead within the DECmcc 
    development team. He has graciously offered to help be co-moderator of
    this "quiet little" notes conference.
    
    Just to bring you up to date on a few personnel changes in our
    organization over the last few months...Pete Savage who used to be
    co-moderator, is no longer within our group; please address all
    moderator requests to either Erik or myself.
    
    Thanks for you patronage ;->
    
    (yes I am still catching up on all my back logged notes, if I haven't
    gotten to yours yet, some one will...)
    

I have started cleaning up note 3, to make current announcements easier to find.
If you need to refer to an older announcement note, let me know.

Please post questions in a different note.  Note 4 is for kit copy and
PAK questions.  For other questions, find a relevant topic (or start a
new note).

Thanks you,

-- Erik (Moderator)

There are currently too many keywords in this conference
to be able to effectively locate anything by trying to use them.

If you want to help people who may need to locate information
in a note you are writing, put a descriptive title on it
and use one of the (zillions of) keywords that already
exist.

If you absolutely need a new keyword created, contact one of the
moderators (by mail) and ask them to create a keyword for you.