reid@decwrl (Brian Reid) (03/03/86)
Welcome to mod.recipes. This is a "moderated" usenet group, whose purpose is to distribute a debugged set of online formatted recipes. The basic idea is that everyone reads through these recipes, saves the ones he likes and ignores the ones that he doesn't like, and then periodically prints out a personalized copy of "The USENET Cookbook". Everything posted to mod.recipes is put there by the newsgroup moderator, namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto, California. The moderator of a newsgroup is something like the editor of a magazine--I don't write much for it, but I must approve everything that goes out, and I edit the contributions for spelling, grammar, and stylistic consistency. Sometimes I add some historical information, or some commentary on the recipe. The mod.recipes system is almost completely automated. People submit recipes by mailing them to a certain mailbox. I proofread each recipe and check the dubious-looking ones to make sure that they are reasonable. I add a "rating" of each recipe according to how easy or hard it is to make, and how long it will take. I also add a copyright notice, copyrighting each recipe for the "USENET Community Trust", which is a California organization formed for the purpose of holding that copyright. I then copy the proofread recipes to an outgoing queue. Once a week, an automatic program is run that takes the first 4 recipes from the queue and sends them out to the network. The rate at which recipes go out is fixed, regardless of the rate at which recipes come in, though if the recipe arrival rate increases, I will increase the outgoing flow rate somewhat. I don't have time to proofread more than about 10 recipes a week, so that will be the absolute limit. At the moment we are in a good equilibrium with 4 recipes a week, and there is about a 4-week backlog. That means that I can be gone for 4 weeks and everything will run perfectly in my absence and you will never even know that I was gone. As you can see by looking at them, these recipes are encoded in a text formatting system, and are not ready to print as they stand. The advantage of this is that they can be formatted for a typesetter or laser printer as well as an ordinary printer, so that you can use the best printing device available to print your cookbook. I have written a set of programs, collectively called "the mod.recipes software", that must be installed somewhere on your machine before you can effectivel use these recipes. In messages that immediately follow this one, I will post the software sources, the documentation for how to use it, and the instructions for posting your own recipes. Brian Reid decwrl!reid or reid@decwrl.dec.com DEC Western Research Laboratory
recipes@decwrl.UUCP (05/29/86)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is to distribute the recipes of the USENET Cookbook. People read through these recipes, save the ones they like and ignore the ones that they don't like, and then periodically print out a personalized copy of "The USENET Cookbook". Everything posted to mod.recipes is put there by the newsgroup moderator, namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto, California. The moderator of a newsgroup is something like the editor of a magazine--I don't write much for it, but I must approve everything that goes out, and I edit the contributions for spelling, grammar, and stylistic consistency. Sometimes I add some historical information, or some commentary on the recipe. The mod.recipes system is almost completely automated. People submit recipes by mailing them to a certain mailbox. I proofread each recipe and check the dubious-looking ones to make sure that they are reasonable. I add a "rating" of each recipe according to how easy or hard it is to make, and how long it will take. If the recipe was submitted in English units (cups and teaspoons), I add metric equivalents (grams and milliliters). There have not yet been any recipes submitted in metric, but when that day comes, I will do the reverse. I also add a copyright notice, copyrighting each recipe for the "USENET Community Trust", which is a California organization formed for the purpose of holding that copyright. When a recipe has been edited, formatted, converted to metric, proofread, and marked with copyright, then it is placed in the outgoing queue. Once a week, an automatic program is run that takes the first 5 recipes from the queue and sends them out to the network. The rate at which recipes go out is fixed, regardless of the rate at which recipes come in, though if the recipe arrival rate increases, I will increase the outgoing flow rate somewhat. I don't have time to proofread more than about 6 to 8 recipes a week, so that will be the absolute limit. At the moment we are in a good equilibrium with 5 recipes a week, and there is about a 4-week backlog. That means that I can be gone for 4 weeks and everything will run perfectly in my absence and you will never even know that I was gone. As you can see by looking at them, these recipes are encoded in a text formatting system, and are not ready to print as they stand. The advantage of this is that they can be formatted for a typesetter or laser printer as well as an ordinary printer, so that you can use the best printing device available to print your cookbook. I have written a set of programs, collectively called "the mod.recipes software", that must be installed somewhere on your machine before you can effectivel use these recipes. In messages that immediately follow this one, I will post the software sources, the documentation for how to use it, and the instructions for posting your own recipes. (Because of its size, the automatic software distribution is limited to North America. Contact me by mail if you want a copy of the distribution outside North America). Brian Reid decwrl!reid or reid@decwrl.dec.com DEC Western Research Laboratory
reid@decwrl.UUCP (06/30/86)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is
to distribute the recipes of the USENET Cookbook.
People read through these recipes, save the ones they like and ignore the
ones that they don't like, and then periodically print out a personalized
copy of "The USENET Cookbook".
Everything posted to mod.recipes is put there by the newsgroup moderator,
namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto,
California. The moderator of a newsgroup is something like the editor of a
magazine--I don't write much for it, but I must approve everything that goes
out, and I edit the contributions for spelling, grammar, and stylistic
consistency. Sometimes I add some historical information, or some
commentary on the recipe.
The mod.recipes system is almost completely automated. People submit recipes
by mailing them to a certain mailbox. I proofread each recipe and check the
dubious-looking ones to make sure that they are reasonable. I add a "rating"
of each recipe according to how easy or hard it is to make, and how long it
will take. If the recipe was submitted in imperial units (cups and
teaspoons), I add metric equivalents (grams and milliliters); if the recipe
was submitted in metric units, then I add the imperial equivalents.
I also add a copyright notice, copyrighting each recipe for the "USENET
Community Trust", which is a California organization formed for the purpose
of holding that copyright. When a recipe has been edited, formatted,
converted to metric, proofread, and marked with copyright, then it is placed
in the outgoing queue.
Once a week, an automatic program is run that takes the first 5 recipes from
the queue and sends them out to the network. The rate at which recipes go
out is fixed, regardless of the rate at which recipes come in, though if the
recipe arrival rate increases, I will increase the outgoing flow rate
somewhat. I don't have time to proofread more than about 6 to 8 recipes a
week, so that will be the absolute limit. At the moment we are in a good
equilibrium with 5 recipes a week, and there is about a 4-week backlog. That
means that I can be gone for 4 weeks and everything will run perfectly in my
absence and you will never even know that I was gone.
As you can see by looking at them, these recipes are encoded in a text
formatting system, and are not ready to print as they stand. The advantage
of this is that they can be formatted for a typesetter or laser printer as
well as an ordinary printer, so that you can use the best printing device
available to print your cookbook.
I have written a set of programs, collectively called "the mod.recipes
software", that must be installed somewhere on your machine before you can
effectivel use these recipes. In messages that immediately follow this one,
I will post the software sources, the documentation for how to use it, and
the instructions for posting your own recipes. (Because of its size, the
automatic software distribution is limited to North America. Contact me by
mail if you want a copy of the distribution outside North America).
Brian Reid
{ucbvax,ihnp4,decvax}!decwrl!reid or reid@decwrl.dec.com
DEC Western Research Laboratoryreid@decwrl (Brian Reid) (08/30/86)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is
to distribute the recipes of the USENET Cookbook.
People read through these recipes, save the ones they like and ignore the
ones that they don't like, and then periodically print out a personalized
copy of "The USENET Cookbook".
Everything posted to mod.recipes is put there by the newsgroup moderator,
namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto,
California. The moderator of a newsgroup is something like the editor of a
magazine--I don't write much for it, but I must approve everything that goes
out, and I edit the contributions for spelling, grammar, and stylistic
consistency. Sometimes I add some historical information, or some
commentary on the recipe.
The mod.recipes system is almost completely automated. People submit recipes
by mailing them to a certain mailbox. I proofread each recipe and check the
dubious-looking ones to make sure that they are reasonable. I add a "rating"
of each recipe according to how easy or hard it is to make, and how long it
will take. If the recipe was submitted in imperial units (cups and
teaspoons), I add metric equivalents (grams and milliliters); if the recipe
was submitted in metric units, then I add the imperial equivalents.
I also add a copyright notice, copyrighting each recipe for the "USENET
Community Trust", which is a California organization formed for the purpose
of holding that copyright. When a recipe has been edited, formatted,
converted to metric, proofread, and marked with copyright, then it is placed
in the outgoing queue.
Once a week, an automatic program is run that takes the first 5 recipes from
the queue and sends them out to the network. The rate at which recipes go
out is fixed, regardless of the rate at which recipes come in, though if the
recipe arrival rate increases, I will increase the outgoing flow rate
somewhat. I don't have time to proofread more than about 6 to 8 recipes a
week, so that will be the absolute limit. At the moment we are in a good
equilibrium with 5 recipes a week, and there is about a 4-week backlog. That
means that I can be gone for 4 weeks and everything will run perfectly in my
absence and you will never even know that I was gone.
As you can see by looking at them, these recipes are encoded in a text
formatting system, and are not ready to print as they stand. The advantage
of this is that they can be formatted for a typesetter or laser printer as
well as an ordinary printer, so that you can use the best printing device
available to print your cookbook.
I have written a set of programs, collectively called "the mod.recipes
software", that must be installed somewhere on your machine before you can
effectivel use these recipes. In messages that immediately follow this one,
I will post the software sources, the documentation for how to use it, and
the instructions for posting your own recipes. (Because of its size, the
automatic software distribution is limited to North America. You should be
able to locate a copy of the software somewhere on your continent by posting
a request to an appropriate local newsgroup.)
Brian Reid
{ucbvax,ihnp4,decvax}!decwrl!reid or reid@decwrl.dec.com
DEC Western Research Laboratoryreid@decwrl (Brian Reid) (11/28/86)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is
to distribute the recipes of the USENET Cookbook.
People read through these recipes, save the ones they like and ignore the
ones that they don't like, and then periodically print out a personalized
copy of "The USENET Cookbook".
Everything posted to mod.recipes is put there by the newsgroup moderator,
namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto,
California. The moderator of a newsgroup is something like the editor of a
magazine--I don't write much for it, but I must approve everything that goes
out, and I edit the contributions for spelling, grammar, and stylistic
consistency. Sometimes I add some historical information, or some
commentary on the recipe.
The mod.recipes system is almost completely automated. People submit recipes
by mailing them to a certain mailbox. I proofread each recipe and check the
dubious-looking ones to make sure that they are reasonable. I add a "rating"
of each recipe according to how easy or hard it is to make, and how long it
will take. If the recipe was submitted in imperial units (cups and
teaspoons), I add metric equivalents (grams and milliliters); if the recipe
was submitted in metric units, then I add the imperial equivalents.
I also add a copyright notice, copyrighting each recipe for the "USENET
Community Trust", which is a California organization formed for the purpose
of holding that copyright. When a recipe has been edited, formatted,
converted to metric, proofread, and marked with copyright, then it is placed
in the outgoing queue.
Once a week, an automatic program is run that takes the first 5 recipes from
the queue and sends them out to the network. The rate at which recipes go
out is fixed, regardless of the rate at which recipes come in, though if the
recipe arrival rate increases, I will increase the outgoing flow rate
somewhat. I don't have time to proofread more than about 6 to 8 recipes a
week, so that will be the absolute limit. At the moment we are in a good
equilibrium with 5 recipes a week, and there is about a 4-week backlog. That
means that I can be gone for 4 weeks and everything will run perfectly in my
absence and you will never even know that I was gone.
As you can see by looking at them, these recipes are encoded in a text
formatting system, and are not ready to print as they stand. The advantage
of this is that they can be formatted for a typesetter or laser printer as
well as an ordinary printer, so that you can use the best printing device
available to print your cookbook.
I have written a set of programs, collectively called "the mod.recipes
software", that must be installed somewhere on your machine before you can
effectively use these recipes. In messages that immediately follow this one,
I will post the software sources, the documentation for how to use it, and
the instructions for posting your own recipes. (Because of its size, the
automatic software distribution is limited to North America. You should be
able to locate a copy of the software somewhere on your continent by posting
a request to an appropriate local newsgroup.)
Brian Reid
{ucbvax,ihnp4,decvax}!decwrl!reid or reid@decwrl.dec.com
DEC Western Research Laboratoryrecipes@decwrl.UUCP (01/28/87)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is
to distribute the recipes of the USENET Cookbook.
People read through these recipes, save the ones they like and ignore the
ones that they don't like, and then periodically print out a personalized
copy of "The USENET Cookbook".
Everything posted to mod.recipes is put there by the newsgroup moderator,
namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto,
California. The moderator of a newsgroup is something like the editor of a
magazine--I don't write much for it, but I must approve everything that goes
out, and I edit the contributions for spelling, grammar, and stylistic
consistency. Sometimes I add some historical information, or some
commentary on the recipe.
The mod.recipes system is almost completely automated. People submit recipes
by mailing them to a certain mailbox. I proofread each recipe and check the
dubious-looking ones to make sure that they are reasonable. I add a "rating"
of each recipe according to how easy or hard it is to make, and how long it
will take. If the recipe was submitted in imperial units (cups and
teaspoons), I add metric equivalents (grams and milliliters); if the recipe
was submitted in metric units, then I add the imperial equivalents.
I also add a copyright notice, copyrighting each recipe for the "USENET
Community Trust", which is a California organization formed for the purpose
of holding that copyright. When a recipe has been edited, formatted,
converted to metric, proofread, and marked with copyright, then it is placed
in the outgoing queue. Each week, on Thursday night, 5 recipes are posted
from the queue. There is about a 6-week backlog.
Recipes are posted both as cleartext and in troff form. To process them with
troff or nroff you will need special recipe macros; there is also some
"recipe software" that makes handling the recipes easier and more automatic.
This is all available from the decwrl archive server, which is described in
message "3 of 4" of this posting.
Brian Reid
{ucbvax,ihnp4,decvax}!decwrl!reid or reid@decwrl.dec.com
DEC Western Research Laboratoryrecipes@decwrl.UUCP (03/28/87)
Welcome to mod.recipes. This is a "moderated" USENET group, whose purpose is
to distribute the recipes of the USENET Cookbook.
People read through these recipes, save the ones they like and ignore the
ones that they don't like, and then periodically print out a personalized
copy of "The USENET Cookbook".
Everything posted to mod.recipes is put there by the newsgroup moderator,
namely me. I am Brian Reid of DEC Western Research Laboratory in Palo Alto,
California. The moderator of a newsgroup is something like the editor of a
magazine--I don't write much for it, but I must approve everything that goes
out, and I edit the contributions for spelling, grammar, and stylistic
consistency. Sometimes I add some historical information, or some
commentary on the recipe.
The mod.recipes system is almost completely automated. People submit recipes
by mailing them to a certain mailbox. I proofread each recipe and check the
dubious-looking ones to make sure that they are reasonable. I add a "rating"
of each recipe according to how easy or hard it is to make, and how long it
will take. If the recipe was submitted in imperial units (cups and
teaspoons), I add metric equivalents (grams and milliliters); if the recipe
was submitted in metric units, then I add the imperial equivalents.
I also add a copyright notice, copyrighting each recipe for the "USENET
Community Trust", which is a California organization formed for the purpose
of holding that copyright. When a recipe has been edited, formatted,
converted to metric, proofread, and marked with copyright, then it is placed
in the outgoing queue. Each week, on Thursday night, 5 recipes are posted
from the queue. There is about a 6-week backlog.
Recipes are posted both as cleartext and in troff form. To process them with
troff or nroff you will need special recipe macros; there is also some
"recipe software" that makes handling the recipes easier and more automatic.
This is all available from the decwrl archive server, which is described in
message "2 of 8" of this posting.
Brian Reid
{ucbvax,sun,decvax}!decwrl!reid or reid@decwrl.dec.com
DEC Western Research Laboratory