[GO-ESSP] Setting up a GO-ESSP Portal re-use repository

[Stephens, A (Ag)]

Roland,

Glad to hear your positive response. I agree that we should explicitly state all dependencies and the implementation technology. Another spin-off from this might be that if you have encoded something in Perl, I might need a Python version but I can translate your code rather than starting from scratch.

Elaborating on your suggestion we would need:

MyComponent - v0.4
------------------

Browser compability:

NS4 - works fine
NS6 - works fine
IE5 - works, but values don't default automatically
Mozilla 1.2.1 - works fine
Firefox 1.0.5 - works fine on linux, buggy display on Windows

Implementation details:

Written in: python 
Requires: MySQL

Tested with: 
Python 1.5 and MySQL6.0 - works fine
Python 2.3 and MySQL6.0 - works fine
Python 2.4 and MySQL6.2 - works fine

etc etc

Note that by 'component', we can mean many things. The more dependencies, the less likely someone is to pick up and use an application. Hence, I think we should concentrate on relatively small components where possible.

Kind regards,

Ag


-----Original Message-----
From: Roland Schweitzer [mailto:Roland.Schweitzer at noaa.gov]
Sent: Tue 12/07/2005 3:12 PM
To: Stephens, A (Ag); go-essp at ucar.edu
Subject: Re: [GO-ESSP] Setting up a GO-ESSP Portal re-use repository
 
Ag,

What a great idea.  I think the register should include information 
about the implementation technology and the dependencies (both 
dependencies for the implementation and for external support pieces).  
For example, a system might be implemented in PHP and require a mySQL 
backend and have only been tested using an Apache server.  Or say it 
might be implemented in Java as a servlet using Velocity and Struts and 
require Java 1.5 or greater and Tomcat 5 or greater.  If I were browsing 
the registry this information would tell me a lot about how difficult I 
think it might be to use the component based on what technology I'm 
already using in my shop.

This sort of information is a little bit more difficult to encode in 
because there are some nuances.  Something tested on Tomcat might well 
run just fine in other servlet containers.  Just having the raw 
information would be a good start, but we could add some subtlety by 
including qualifiers like "required", "recommended" or "tested with".

Roland