Source forge tracking system for POC--Info required

[Sue Rhee]

On Wed, 29 Oct 2003, Ware, Doreen wrote:

> Hi Pankaj,
>
> I am not sure if sorceforge is usually used for bug tracking purposes.

I know of two projects that are heavily using the bug tracking feature of
Sorceforge: GO and GMOD.

> Shuly is taking care of the documentation.  We will use sorceforge as our
> CVS repository.  Shuly will be writting up the documentation. I will reveiw
> this with her at the end of the week. I do not plan on running a mirror but
> maintaining one repository structure.  If we will be using Source forge then
> our CVS should be located there.

Do you think there should be a backup server, in case Sorceforge is
temporaily down etc?

Sue

> Doreen
>
> -----Original Message-----
> From: Pankaj Jaiswal [mailto:pj37 at cornell.edu]
> Sent: Wednesday, October 29, 2003 10:26 AM
> To: po-dev at plantontology.org
> Subject: Re: Source forge tracking system for POC--Info required
>
>
> Hi Shuly,
>
> Wait until I hear from them, in the meantime tell them it's the same group.
>
> Here is what I told them in reference to those 2 questions raised by
> Sourceforge. The following statements were mentioned in the original grant
> proposal, except that we will use the Sourceforge, which we have now chosen
> to
> be an additional mirror site for distribution. Actually, we wanted to have a
> bug
> tracking system only, but we need to furnish all these details in order to
> have it.
>
>  >
>  > 1. A technical description (at least two paragraphs in
>  > length) of the software you are developing, including the
>  > programming language(s) used in its development and its
>  > major features.
>  >
>
> the ontologies will be made available both as flat file DAG-Edit format, and
> as
> richer RDF [http:// www.w3.org/RDF/] and DAML-OIL [http://
> www.w3.org/TR/daml+oil-reference] formats that DAG-Edit and a number of
> other GO
> Consortium tools can process.  Diagrams used to supplement the text
> definitions
> will be downloadable in common archive formats (tar-gzip and zip).
> Although this project is not primarily directed at software development, any
>
> software developed in support of the Plant Ontology Consortium
> (http://www.plantontology.org) will be available under an open source
> license.
>
> Technical info for source forge -
> we are using tools developed by the Gene Ontology Project
> operating system: unix / linux
> programming language: perl,  cgi scripts
> database: MySQL
>
>
>  > 2. Details of the Open Source license (either the name of an
>  > OSI-approved license, or the exact terms of the license if
>  > it is not an OSI-approved license) which will be used by
>  > your project.
>  >
>
> All ontologies, associations and software will be released to the public
> under
> an open source license that allows free use and distribution
> (http://www.opensource.org).  Releases of ontologies will be made following
> a
> quarterly schedule as outlined in the project description.  Releases of
> associations will follow the release schedules of TAIR and Gramene, software
>
> will be released as soon as it is judged minimally useable by third parties.
> The
> manner and mode of release will be as described in the project description.
> In accordance with common open source practice, all works will be
> copyrighted
> jointly by the members of the Plant Ontology Consortium solely for the
> purpose
> of protecting the integrity of the work.
>
>  >
>
>
>

-----------------------------------------------------------------------------
Sue Rhee                         	rhee at acoma.stanford.edu
The Arabidopsis Information Resource	URL: www.arabidopsis.org
Carnegie Institution of Washington	FAX: +1-650-325-6857
Department of Plant Biology		Tel: +1-650-325-1521 ext. 251
260 Panama St.
Stanford, CA 94305
U.S.A.
-----------------------------------------------------------------------------