This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Re: Interpolation interface
- To: edwin at netwood dot net
- Subject: Re: Interpolation interface
- From: Brian Gough <bjg at network-theory dot co dot uk>
- Date: Mon, 2 Apr 2001 22:44:32 +0100 (BST)
- Cc: gsl-discuss at sources dot redhat dot com
- References: <3AC654C4.A1C442AA@netwood.net>
In the long run there should be be something like that, as there was
for SLATEC -- we will have to see how things go when we have released
version 1.0. Without an existing codebase to refer to the design
problems are too unfocused.
E. Robert Tisdale writes:
> Gerard Jungman wrote:
> [snip] > We encourage user participation... [snip] > Anyway, we
> appreciate the input.
> I don't doubt your sincerity but you must realize that your
> remarks sound hollow to the GSL User Group (GSLUG pronounced
> "slug".)
> The GSLUG does not "own" the GSL API. The GSL developers (just
> you and Brian Gough now) own the GSL API and determine what gets
> into the GSL and what doesn't. This discourages participation by
> GSL users. If you want to encourage participation in GSL design
> and development, you should yield ownership to the GSLUG and let
> them decide, collectively, what goes into the API and what doesn't.
> The problem is that I don't know how you would determine who is a
> member of the GSLUG and who isn't -- who has the right to
> participate (vote?) and who doesn't. Maybe you could require
> GSLUG members to physically appear at regular meetings (at LANL or
> some neutral site) to vote on what gets into the GSL API. Maybe
> you could require GSLUG members to distribute a significant
> application under the GPL which uses the GSL API.
>