What is it exactly I have to do?? REMEMBER... I am a =volunteer=

[jim@mercury.laney.edu]

I didn't catch this part of Roman's response before, and I think it needs
special handling.

> 
> Date:    Fri, 02 Jul 1999 13:10:41 +0200
> To:      seul-edu@seul.org
> From:    Malonowa <malonowa@wanadoo.fr>
> Subject: Re: Ok, http://gperiodic.seul.org exists
> 
> I think this goes for all software that SEUL is involved in as well. 
> You need to get your projects up to a commercial standard for them to 
> be useful and for people in the world to sit up and notice your work.

Just a minute... Do the rest of the group concur with this? If you do,
this may be the wrong group for me. I think I made it clear I have my
hands in many pies, no? 

I bring up to date what I offer: Best effort, NO GUARANTEE WHATSOEVER.

I need help getting roster to the point where it is useful, that means
docs and coding. Are there any offers in kind here? 

I am interested in packaging things SEUL offers for debian.  I have
already said I am a very new maintainer; I'm not interested in trying
to get debian policy modified on behalf of anyone besides myself. 

Therefore, I will package relatively easy SEUL offerings PROVIDED:
they MUST FOLLOW THE DEBIAN POLICY DOCUMENT. For most of the things I
have seen so far, following policy is not very work-intensive. For
example, all gperiodic would require is a man page giving the name, a
short description and as many sources of information -- on how to run
the thing, and on chemistry and/or physics as you deem appropriate.
Also, there is NO reason you cannot have the exact same information in
some other form. Having a man page does NOT imply not having other forms
of documentation.

If not, I have already sent a RTP (request to package) on your behalf
to one of the debian mailing lists, this request has both the "current
projects" and "existing software" URLs. Given the apparent request to
NOT have a man page, which goes contrary to debian policy, I will not
be packaging anything because I don't have time to try to merge your
policies with debian's.

However, I will continue work on roster; I was going to do that anyway.
EDUML looks interesting, I think I can at least come up with input and
output filters for it that work with roster. If that helps it work with
k12admin, so much the better.

-Jim, who is now wondering if you think I fit in this project.