Try the TOPICS option. with TOPICS you can create a "sub-group" of
subscribers who receive mail under a particular TOPIC, while the rest of the
subscribers do not.

To do this, add  "TOPICS= WG1" (no quotes) to your lists's header ("WG1"
standing for "Work Group 1"), and have the sub-group of subscribers working
on the project post all their mail to your list with the preface in the
Subject line "WG1:" (no quotes).

You will also need to add to your list's header  "Default-Topics= Other" (no
quotes)

Before starting to use the TOPIC, send the command:

SET [Listname] TOPICS= -WG1 for *@*

This will set all subscribers to the condition of not receiving the TOPIC
"WG1" - when you add a TOPIC to a list which already has subscribers, all
subscribers will receive all TOPICS unless the option is deselected.

Then have all those interested send the comand:

SET [Listname] TOPICS= +WG1

This will cause LISTSERV to send all postings labeled with this TOPIC to
those who have so selected the TOPIC. All other will never even see these
postings.

You can also attach files to these postings which others on the list will not
be bothered to have to download. You must, of course, change the header to
"FILES= yes".

You can add up to 11 TOPICS, plus the "Other" category for unlabeled
postings.

good luck,

  John

 John M. Roraback, Ph.D.
 PsyUSA Network Manager
 [log in to unmask]

In a message dated Sat, 15 Feb 1997 13:28:32 -0800  [log in to unmask]
writes:

>  Recently, on the QBasic (don't laugh) mailing list, someone proposed
>  gathering the efforts of list subscribers to create a series of useful
>  projects using BASIC compilers. (The first project is a DOS Shell type
>  program.)
>
>  In under a week, there were 13 people signed on for the task. The current
>  number stands somewhere over 15 people.
>
>  Our problem, however, is communication. Our work is on a slightly
>  different tangent than the QBasic list, so posts regarding the project
>  aren't really appropriate (especially since the members of our group
>  constitute a minority of the rest of the list).
>
>  That's where we were hoping someone here could help out. We're really
>  hoping to find someone who could host a separate list that people working
>  on the project can stay in touch. Ideally, we'd also like permission to
>  distribute source code and compiled work. As I mentioned, our number at
>  the moment is somewhere just about 15. Communication off the list for
>  members is a little awkward at the moment, so I can't give any estimates
>  as to an average number of daily posts.
>