Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ukma!brian
From: brian@ms.uky.edu (Brian Sturgill)
Newsgroups: news.admin,news.groups
Subject: Re: comp.sources.projects (was Re: A rehash (but yet important) ...)
Message-ID: <7138@e.ms.uky.edu>
Date: Thu, 20-Aug-87 12:01:50 EDT
Article-I.D.: e.7138
Posted: Thu Aug 20 12:01:50 1987
Date-Received: Sat, 22-Aug-87 10:32:51 EDT
References: <7130@e.ms.uky.edu> <329@brandx.rutgers.edu>
Organization: U of Ky, Math. Sciences, Lexington KY
Lines: 54
Xref: mnetor news.admin:868 news.groups:1377

In article <329@brandx.rutgers.edu>, webber@brandx.rutgers.edu (Webber) writes:
> In article <7130@e.ms.uky.edu>, brian@ms.uky.edu (Brian Sturgill) writes:
	...
> Actually the problem is that the scope of the group is too narrow.  I propose
> deleting it and creating:
> 
>    comp.sources.projects: an unmoderated group dedicated to messages
>        concerning the following aspects of producing software for donation:
>           a) announcement of interest in finding software for particular tasks
>           b) announcement of commencement of new pd software projects    
>           c) requests for bug reports in anticipation of new release
>           d) announcement of availability of alpha quality software
>           e) queries about interest in group programming projects over
>              the net.
> 
> Such a group would subsume comp.sources.wanted and at the same time be
> interesting enough that the software requests would get a broader
> hearing.
> 
> Comments?
> 
> ------- BOB (webber@aramis.rutgers.edu ; rutgers!aramis.rutgers.edu!webber)

I think this might be a good solution.
I am not married to the idea of going back to the 'net.sources' style group,
I just believe the current system is very bad (i.e worse than net.sources).
In addition to the above, it would be nice if a "standard" format for messages
were developed much like that which is done in the bug groups.
Something like:

WANTED | (ALPHA|BETA|release #) AVAILABLE | REQUEST FOR COMMENT

PROJECT
	A one liner saying what the PROJECT being developed/wanted/etc is.

ENVIRONMENT
	The environment under which the program should/will run.

OUTLINE
	I. An outline (in outline form) of the main features.
		A. point A, etc.

Needless to say the above is not a final form, but I think it is much
easier to deal with messages in a standard format... Note that it
is not necessary to enforce the format -- improperly format messages
would probably just be ignored by most people.

Brian

---------------
           Brian Sturgill          System Manager
   University of Kentucky Departments of Mathematical Sciences
        brian@ms.uky.edu                brian@ms.uky.csnet
        {uunet,cbosgd}!ukma!brian       brian@UKMA.BITNET