aimmath-developers — Development related messages

RE: [Aimmath-developers] Re: Sourceforge messages

[Gustav W D. <gw...@yo...>]

Dear Greg,

thank you for offering to add the version strings.

I am looking forward to reading your cvs documentation. I think a good place
to put it would be the DocManager on SourceForge. You have privileges to
place and edit documentation there (in fact I have given all of us this
privilege). I am glad that you volunteer to do this because I am very busy
at the moment and in any case not really qualified.

> For GAP, we have the following etiquette w.r.t. committing changes.
> Elementary changes like typos. and obvious bug fixes just commit.
> More substantial changes that may be controversial, submit a message
> with PROPOSAL in the header. If noone objects within 3 days one then
> takes that as an acceptance and the proposer may commit the changes.
> Maybe, with just 4 of us (at the moment) that time period should be a
> little longer, but does such a system seem acceptable?

I think that is very appropriate.

> A few months back, I sent some info. on what I called a Trig package.
> I'm thinking that I could add that into the distribution, along with
> sample quiz files. In fact, I think Neil's sample quiz files could also
> be included on Sourceforge.

I don't think that sample question files should go into cvs because they do
not really be developed by us as a team. Rather the important thing is that
they should be easily accessible by the non-developers. Also non-developers
should be able to easily submit their examples. I have however no bright
idea of how to implement this exactly.

> We should think about a standard directory for
> these: example perhaps with subdirectories. This brings up another idea.
> Perhaps we could have some notion of a ROOT path for includes. Let's
> say at the AIM (= ROOT) level we have directories:
>
>   AIM/
>      dev/    # information etc. useful for developers, howtos etc.
>      etc/    # scripts for packaging etc.
>      example/# sample quiz files
>      images/ # not present at Sourceforge
>      WEB_INF/
>
> Does that sound reasonable.
Reasonable yes, but not really necessary given my comments above.

Regards,

Gustav

[Aimmath-developers] Re: Sourceforge messages

[Greg G. <gr...@ma...>]

On Monday, 28 April 2003 5:27 PM, Gustav wrote:
GG> One other thing I'd like to see is version Id strings
GG> at the top of each file.
> That sounds like a very good idea. Would you be able to add these 
> strings to all the files and commit them?

Sorry, for the delay in reply, but yes I will do this. I committed one
file with such a header so that I was sure that the same strategy that
I knew from elsewhere worked. I'll probably do this over the weekend.

On Monday, 28 April 2003 5:27 PM, Gustav wrote: 
> Ken suggested that it would be useful to have our own little 
> guide to CVS on
> SourceForge because the documentation on SourceForge is a little
> overwhelming. Is there a volunteer for writing this?

Some time ago I wrote an email to a colleague detailing the essential
cvs commands, and I can adapt this and some other info. My plan would
be to create a new directory or two - for GAP we have directories 
dev for development, etc for various scripts used in packaging and the
like. I guess I'll start by creating a dev directory and put my info
on cvs in a file there; once it's in place, we can all have a turn
at modifying it further. Anyway, sorry for the delay again in replying
to this.

For GAP, we have the following etiquette w.r.t. committing changes.
Elementary changes like typos. and obvious bug fixes just commit.
More substantial changes that may be controversial, submit a message
with PROPOSAL in the header. If noone objects within 3 days one then
takes that as an acceptance and the proposer may commit the changes.
Maybe, with just 4 of us (at the moment) that time period should be a
little longer, but does such a system seem acceptable?

A few months back, I sent some info. on what I called a Trig package.
I'm thinking that I could add that into the distribution, along with
sample quiz files. In fact, I think Neil's sample quiz files could also
be included on Sourceforge. We should think about a standard directory for
these: example perhaps with subdirectories. This brings up another idea.
Perhaps we could have some notion of a ROOT path for includes. Let's
say at the AIM (= ROOT) level we have directories:

  AIM/
     dev/    # information etc. useful for developers, howtos etc.
     etc/    # scripts for packaging etc. 
     example/# sample quiz files
     images/ # not present at Sourceforge
     WEB_INF/

Does that sound reasonable.
      
  Regards,
  Greg

[Aimmath-developers] Welcome

[Gustav W D. <gw...@yo...>]

Dear Neil, Ken, Gregg,

I just added you to the developer's e-mail list. I thought this would be a
convenient way for us to communicate. The list is only open to AIM
developers, of which there are currently only us 4 but I would hope more
will join soon.

I am completely inexperienced at this business of administering a
development effort. So I would appreciate any plain-speaking advice you have
for me.

I have placed the last official release of AIM (version 2.1.0) into the
SourceForge CVS repository in the directory AIM (you may want to rename it
to ROOT locally so that it runs without changes). I did not place the
automatically generated files under CVS control.

To check out the system I committed one changed file (implementing the
"mark" and "validate" links in each question's navigation bar on the
student's quiz page). In future I will always send a message to this list
before any commit.

Ken suggested that it would be useful to have our own little guide to CVS on
SourceForge because the documentation on SourceForge is a little
overwhelming. Is there a volunteer for writing this? If not I will try to
write a page next weekend even though that would be a bit odd because I
believe that I am the least experienced member of the current development
team.

Best wishes,  Gustav
----------------------------------------
Dr Gustav W Delius, Department of Mathematics
University of York, York YO10 5DD, United Kingdom
Tel.: +44 (1904) 433 077, Fax.: +44 (1904) 433 071, office: G/110
http://www.york.ac.uk/mathematics/physics/delius/