From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10995 invoked by alias); 10 May 2010 14:23:27 -0000 Received: (qmail 10977 invoked by uid 22791); 10 May 2010 14:23:25 -0000 X-SWARE-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from up.nbi.dk (HELO mail2.nbi.dk) (130.225.212.6) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 10 May 2010 14:23:21 +0000 Received: from [192.168.9.216] (unknown [193.206.22.97]) by mail2.nbi.dk (Postfix) with ESMTP id D68883C976 for ; Mon, 10 May 2010 16:23:18 +0200 (CEST) Message-ID: <4BE816D5.8060106@webdrake.net> Date: Mon, 10 May 2010 14:23:00 -0000 From: Joseph Wakeling User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: gsl-discuss@sourceware.org Subject: Re: Flat (uniform) random distribution and some development/contribution queries References: <4BE7EAAD.20603@webdrake.net> In-Reply-To: <4BE7EAAD.20603@webdrake.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2010-q2/txt/msg00011.txt.bz2 Further to previous message ... > The functionality seems generic and useful enough that I was surprised > not to find a library available. Anyway, it seems like it would be easy > enough to implement as part of GSL. Is there interest in having this? > If so, I'll map out a brief API description and/or sample code. ... yes, I _have_ read the part of the GSL website which says, > To maintain stability, any new functionality is encouraged as packages, > built on top of GSL and maintained independently by their authors, as > in other free software projects. The design of GSL permits extensions > to be used alongside the existing library easily by simple linking. What I'd like to know is if there are any recommended practices for making my work "friendly" to the GSL in the sense that it can be readily incorporated back if/when it gets the necessary level of approval. Questions would include, (i) Is it OK to have functions named along the lines of, gsl_mylib_func() ... as per typical GSL fashion, so that the API will remain stable if/when the code is incorporated into GSL? (ii) Are there any recommended practices related to VCS that will make it easier to incorporate a semi-independent project into GSL and preserve version history? (iii) What's the appropriate etiquette to follow regarding discussion, of the project status? How much discussion can/should I make on this and other GSL lists, for example? I would like the work to be developed in as close collaboration with the wider GSL community as possible. Thanks & best wishes, -- Joe