daemon@rutgers.UUCP (02/18/87)
From: Bruce Tanner <CERRITOS@USC-ECL.ARPA>
I'm posting this to the net for Mark. Please contact him directly.
-Bruce
------
NODE PROPOSAL DOCUMENT 1/22/87
Version 0.7
Draft of Proposed NODE Guidelines
By Mark Randall
Amiga Tech Users Group (Pasadena, CA)
NODE stands for Newsletter On Disk Exchange. Its purpose is to allow the
hundreds of active Amiga users groups across the country and around the world
to exchange newsletter articles, information and ideas. NODE will remain as
informal and non-structured as possible. This guideline will suggest some
ideas about a minimal format that will allow NODE to be easy to implement and
maximize the usefulness of the information exchanged.
In general, the concept behind NODE is one of those ideas whose time has come.
Participating users groups will put the articles from their newsletters onto a
disk and mail it to a central location. The articles from all of the groups
will be put onto one disk which will be copied and sent back to the groups.
The groups may then print out the articles they think will be of interest to
their members and can include the rest on a disk of the month, etc. Further
distribution of the information can be accomplished by uploading to BBS's,
distributing to stores or posting on information services.
The main goal is to get the most information to the most people at no cost to
anyone. This clearly meets the prime directive of users groups, to distribute
information. A principal goal in the design of the NODE concept is to make
participation as easy as possible for already over-burdened users group
personnel. Hopefully, it can make life much easier for newsletter editors
since they will have dozens of articles of various lengths and topics ready to
print out. There are many other potential benefits from NODE, the first of
which will be establishing a world wide communications channel for users group
officers to coordinate activities and exchange ideas.
That in a nutshell is the idea. The rest of this obese document discusses
organization, implementation, and enhancements. I have a gut feeling that
such a simple idea should be simple to define but things don't seem to work
out that way. I apologize.
The implementation of NODE requires three basic steps.
a. Organization
b. Format
c. Distribution
Organization
The first step in organization is this document. Once a format guideline has
been decided on, a core team of users groups must be organized to create the
first issue. So far the following users groups have been contacted and have
indicated that they will participate:
Amiga Tech Users Group
Los Angeles Amiga Users Group
Amiga Friends
South County AUG
Westside AUG
San Fernando Valley AUG
Inland Empire AUG
San Diego AUG
First Amiga Users Group
Amuse (New York)
North West AUG
These groups were contacted by phone or in person. This gets expensive so as
soon as this document reaches version 1.0, it will be used to enlist new
groups. Hopefully, NODE itself will gain wide enough distribution that it
will reach new users groups and become self-publicizing. The format will be
included in each issue.
Once a sample issue has been generated and the "pump has been primed", so to
speak. The second step in organization is the establishment of a NODE
Executive Committee. The executive will be comprised of key users groups who
will serve on a rotating basis. The responsibilities of the executive include:
Updating and improving the NODE concept
Selecting the NODE "Hub" users group
Selecting the NODE "Relay" users groups
The compilation, duplication and distribution of NODE will be the
responsibility of one "Hub" users group. This group is the central spoke in
the wheel. The duty of being the hub will rotate every year to a new
volunteer group. Amiga Tech Users Group has volunteered to be the hub group
for the first year.
The "Relay" groups are users groups that will be responsible for international
NODE distribution. Eventually, we hope to have relay groups that will gather
& send information up the chain and handle the "downline" distribution of NODE
in Europe, Australia, and South America.
As part of any organizational attempt the rules and boundaries must be laid
out. All of this may seem obvious but it has to be spelled out somewhere so
here it is:
The volunteers duplicating NODE are only human so to prevent the NODE network
from drowning in its own success:
NODE participation is open only to formal users groups that meet regularly and
publish a monthly newsletter. It is NOT open to individuals. Individuals
wishing to receive NODE should join their closest NODE group. If there is no
local group then start one!
The disk sent in by a users group must have articles on it. NODE is set up on
an "exchange" basis. If a group is just starting and has no articles to
exchange but wants to get NODE, they should contact the closest NODE group and
get copies from them until they can start generating articles and information
on their own.
Groups participating in NODE have the responsibility of spreading the
information as far and wide as possible. They should think of themselves as
"distributors" in their area. Each group should build a "downline" of clubs
that are not yet large or organized enough to participate directly in the
network.
Some people always seem to try to cash in on the good will and good deeds of
others. To prevent creeping commercialism:
Do not include any advertisements in your NODE submission. We can't spare the
disk space and it isn't fair to other vendors.
NODE participation is only open to non-profit groups. NODE may not be sold
commercially although non-profit groups may duplicate NODE and charge
reasonable media and duplication fees. (i.e. $3-4).
NODE may be placed on commercial electronic networks but the network may not
copyright the material, imply sole distribution rights or otherwise hinder the
free flow of NODE information in any way.
The groups involved with the creation and distribution of NODE are not
responsible for the content of the articles. ALL NODE materials go out
unedited and exactly as received. The original author holds all responsibility
for the content of his work.
While the articles are freely distributable for non-commercial purposes, all
rights for other distribution are reserved by the original author.
The information included in NODE is exactly as it was received from the groups.
If you edit or delete anything from NODE please change the name of the disk
and indicate that it has been edited so that altered versions of NODE do not
mistakenly get distributed as the complete original text.
It is only fair that credit be given to the author and his group. It will also
make it easier to know who to contact and where he is should there be any
questions, comments or replies to the article. The following is a suggested
header for all NODE articles. Once we have decided on a standard header, it
should always appear with every article:
A MEGABYTE WITHOUT MEGABUCKS!
By Cris Erving Amiga Tech Users Group (Pasadena)
From SCANlines 10/86 via NODE 4/87
The reference to the original publication is necessary so that the original
unedited text can be found. The original date of publication is important
because some information can be outdated and superseded. The reference to
NODE and the issue is so that the same articles will not be re-submitted to
NODE accidentally and wind up endlessly looping through the network.
FORMAT
The goal of the NODE format is to make the information as accessible as
possible to newsletter editors so that they can edit and print it out
regardless of their software and hardware configuration.
The disk you send to the NODE hub group must be a good quality double sided
3.5 inch floppy. Please try to verify the data before you send the disk.
It would be a waste to deprive everyone of your information because of a
read/write error. It's worth the extra two minutes.
Creating a NODE submission:
* Format & verify a DSDD 3.5 inch disk
* Create a drawer with icon named after your group
* Put the articles from your latest newsletter in the drawer
* Put standard project icons with each file
* Set the default tool to :MORE
* Use a descriptive name for the article
* Use standard extensions like .REV for reviews
.SRC for source code, .PRG for compiled programs etc.
* Schematics and illustrations should be in IFF format
* Set the default tool for IFF pictures to :SHOW
* Verify all files on the disk
The text of your articles should be unformatted with no control codes, fonts
or styles. The maximum line length should be 75 characters. Terminate each
line with a line feed. Separate paragraphs with a blank line. Include the
standard NODE header at the top of every article.
CONTENT
The content is up to you and should reflect your users group. Remember that
NODE is for articles only and the programs that accompany them. NODE is not
a P.D. swap, we will leave that task in the capable hands of Fred Fish and
John Foust. No one is going to edit your materials so try to stick to these
common sense" guidelines.
Use the text as it appears in your newsletter. This means you have already
edited it checking for grammar, spelling, brevity and style. In general, let's
try to stay away from libellous statements, unrestrained product bashing and
other verbal hostility. Hopefully, NODE will continue to foster the already
excellent relationship between manufacturers, vendors and users groups. Please
label editorial opinion as such and include a disclaimer along the lines of
"The opinions expressed here are those of the author and not necessarily the
publisher". In your "Club News/Announcements" article be sure to include a
contact name, address and phone number so that other groups up and down the
chain can contact you directly.
DISTRIBUTION
The goals of the current distribution program are:
* Ease of use
* Maintaining low costs
* Fast distribution
Every month the NODE groups will mail their NODE submission to the hub group
via first class US mail. Each users groups submission is called a "Packet".
There will be a cut off date established each month for that month's NODE.
Packets received after the cut off will be included on the following NODE.
Currently, the proposed cut off is the last Friday of each month. NODE will
be assembled, duplicated and return mailed by the following Friday.
A proper NODE packet consists of:
* The sturdy mailing envelope it arrives in
* A regular size mailing label clearly marked with your
return address
* A return postage 39 cent stamp
* Your NODE submission disk
The current hub group address is:
NODE
2227 Canyon Rd.
Arcadia CA 91006
The NODE hub group will provide the return envelope so that a standard size
can be used to facilitate stuffing. The hub group will:
* Backup the finished NODE onto your disk
* Drop the disk into a standard envelope
* Peel your label and stick it on the envelope
* Lick your stamp and slap it on the envelope
* Drop it in a mail box
No mailing list will be maintained. Those groups that send a packet will
receive NODE. Those that don't, won't. This is the only way we can keep
from doing lots of paper work and book keeping. In a cooperative volunteer
effort such as this, the hub group cannot be responsible for doing any groups
job for them. In order for this system to work everyone must do their part
exactly as defined in the NODE standard.
New information about NODE and the NODE format will be included in the root
directory of each issue of NODE. It will be called NODE NEWS. Please refer
to this for updates and changes.
SUMMARY
The response to the initial versions of this document has been enthusiastic.
We request your input as we head towards version 1.0. The first issue of NODE
will be 4/87. It seems that the first issue will be available to well over
2000 end users. The cut off for that issue is the last Friday of February.
We encourage your participation in the premier of NODE.
Version 1.0 of the NODE guideline will be on NODE 4/87. Here are some of the
new ideas being considered for inclusion.
* Move the cut off up at least one week to promote 1 month
turnaround for the majority of groups
* Include a file called NODE LIST on each issue that has a
name, address, phone # & # of members for each NODE group
* Develop a format for NODE MAIL which would be a method for
user group officers to exchange ideas on the disk. Topics
might include P.D. swaps, cooperative efforts and user
sponsored shows, etc.
* Approach Commodore-Amiga about submitting an official
column to each issue outlining new products, news, and
updates.
* Solicit famous Amiga personalities to write regular
columns in NODE.
* Obtain a corporate sponsor to underwrite the costs of
envelopes and pre-paid return postage.
* Bi-annual NODE meetings at the Winter & Summer Consumer
Electronics Shows. (Las Vegas and Chicago)
* Have the hub group send a dozen mailing labels with their
return address in the first NODE sent to a new group.
* When NODE outgrows 1 disk, develop a standard of
compressing the data with ARChive or other utility.
* Have the info nets submit edited versions of their
message bases to NODE. Along the lines of Best of
BIX in Byte magazine. Good promotion for them and
good info for our members.
* Have the NODE executive committee select an alternate
group to replace the hub group should the hub group not
be able to complete their year commitment.
All of the above ideas have pro's and con's in cost, convenience and effort.
None of this is cast in stone (yet). We need your input on these ideas and
how they should be implemented.
Thank You,
Mark Randall
2227 Canyon Rd.
Arcadia CA 91006
(818) 355-6111 After 6:00 P.M. P.S.T.
FidoNET ECHOmail: JPL Voyager Pasadena
ACKNOWLEDGEMENTS
The funding to start NODE has been provided by a grant from Color America
Foundation, a non-profit educational organization.
Thanks to all of the officers of the users groups in the Southern California
Amiga Network (SCAN) for working together to create the atmosphere of
cooperation that has made NODE a reality.
-------bj@well.UUCP (02/21/87)
This sounds GREAT, just what the Amiga needs. If you wish to actually organize this information and make it available using a consistent and easily understandable user interface I will devote effort toward publishing this information using the InfoMinder package, gratis Amiga domination. The ROM Kernel for 1.2 is also distributed as such. We have to get this info out to users. Also, new product introductions and reviews are easier to do (and avoid the printing delays) than the existent systems. If interested please email me. Thx. -Jim Becker Terrapin Software