Starjava is not built as part of make world (at least it wasn't when they
were together). If JAC were to host I'd prefer it to be a separate
starjava subversion repository with separate access control. JAC already
have 3 subversion servers (internal, starlink and oracdr) so adding a new
one is not a problem.
Peter was worried about the code going onto google code / sourceforge and
being orphaned if Peter and Mark stopped developing it. Since JAC are
heavy users of splat and I'm making people use topcat we may be able to
consider hosting it.
Tim
On Tue, 23 Sep 2008, Brad Cavanagh wrote:
> On Sep 21, 2008, at 11:59 PM, Peter W. Draper wrote:
>
>>> Unless there are strong objections, we should have all the starjava code
>>> together under subversion, as part of the Starlink Lifeboat, regardless
>>> of Astrogrid additions. Surely the source would still be available to
>>> AG or anyone else if Mark moves on to new pastures.
>>
>> I agree with this position. Given the uncertainty of future support it
>> might be better if the code was kept as part of the Starlink subversion
>> repository, at least that would stop it from being orphaned.
>
> I agree with Malcolm and Peter. Further, having starjava in SVN with
> everything else makes it easier for keen external users to get at everything.
> JCMT users, in particular, want GAIA, SMURF, and SPLAT, and if they're
> especially keen and are building it themselves, telling them they need to do
> a second checkout only makes them less likely to want to build it themselves.
> Putting everything together lowers the activation energy, I guess.
>
> Brad.
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|