sourceforge

[Chris Albertson <chrisalbertson90278@yahoo.com>]

--- Mark Pitts <PITTS@shands.ufl.edu> wrote:
<snip>
> 
> I agree with Chris that there's no reason we shouldn't start working
> on defining particulars of the database.  IMHO, this is the most
> important step in the whole process.  
> 
> I'd like to handle the Sourceforge part.  It's going to take a little
> while for me to get up to speed on programming for this type of
> application, so I can at least run the Sourceforge site while I'm
> learning.  If there are no objections I'll start the setup process
> immediately.

Good.  There are a few decisions to be made.  You can have one
big project or mutiple projects.  Write access is by project
so you have to think how fine grained the control needs to be.

One request, how about one directory in the CVS tree for test
data?  Say you check in that CD you just got or (more likely)
some " gzipped" subset of it.  It could be the start of a
regression test suite.  We can argue over it but I'd suggest
an intial directury structure something like this

   TASS
      Test_Data
         Images
            <FITS images go here>
         Star Lists
            <lists of stars go here>
      Catalogs
         <catalogs used by the project go here>
      Src
         <one directory per "project" where each has 
          a project leader wh can say yes or no to code changes>

          I assume each directory here would miiror the larger
          structure.  For example I have a program called
          fits2postgres.  Inside that I would have a "src",
          "data" and "doc" directory tree.

      www
         <All of the HTML pages on source forge are kept here>

You are doing the work, so do as yu see fit

>

=====
Chris Albertson 
  Home:   310-376-1029  chrisalbertson90278@yahoo.com
  Cell:   310-990-7550
  Office: 310-336-5189  Christopher.J.Albertson@aero.org

__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com