These are proposed guidelines for establishing a Listserv/Netnews gateway. Please comment. It is the responsibility of the person requesting the gateway to do the following. 1. Get the approval of the Listserv list owner(s) and the Listserv administrator at the host node. Send them each a copy of the posting "General information on Listserv/Netnews gateways", posted regularly to bit.admin. If any one of these people objects, the gateway is not done. (Note: This document has not been written yet.) 2. Find a site that is willing to do the gateway. Sites that might be willing include psuvm.bitnet, auvm.bitnet, and ysub.bitnet. 3. Get the approval of the Listserv list readers. This could be done somewhat informally by posting to the list and asking if there are objections. If the issue was controversial, a formal vote should be held according to the same guidelines as for creating a new Usenet group. If there was no major dissenting opinion within 14 days, a vote would not be needed. 4. If there is a Usenet group where crossposting would be logical, get the approval of the people who read that group (in the same way as approval of the Listserv readers was gotten). 5. Post to bit.admin to see if there are any objections. The subject of the posting should be "Gateway for <listname> under discussion". Again, if there was no major dissenting opinion within 14 days, a vote would not be needed; otherwise a vote would be held. It is ok to do steps 3, 4, and 5 all at the same time. 6. Write to [log in to unmask] or [log in to unmask] to say that all of the criteria have been met and to indicate the gateway site, Listserv host node, list owner(s), and a short (45 character maximum) description of the list. News-admin will register the gateway and will give a go ahead to start the gateway. Please wait for a response from news-admin before turning on the gateway. 7. Post to bit.admin to say that all of the above criteria have been met and that the gateway is operational. The subject of the posting should be "Gateway for <listname> operational".