On Tue, Jul 28, 2009 at 4:18 AM, D. Michael McIntyre<[email protected]> wrote: > I'd remove the final "/." from the end, just finishing with "go to > http://rosegardenmusic.com</p>" (Pet peeve of mine. If you can't find an > unambiguous way to punctuate the end of a sentence that terminates with a URL, > don't punctuate it at all.)
If the final full stop is not part of the clickable URL, then I don't really see the problem in making it adjacent. The URL is perfectly well delimited by behaviour and (if you squint) colour, and presumably you can right-click-Copy to get it into the clipboard. In situations where the URL is not necessarily going to be clickable, I often put a space before the following stop, though I agree it's not very satisfactory. (This could be our most inconsequential discussion on this list for some time.) > Actually, the whole license issue is a big can of worms by itself. I just did > a little surfing for a reliable external link, and got into all kinds of GPL2 > vs. GPL3 stuff. The licenses are not compatible, and we have all kinds of > random borrowed code snippets, all from GPL 2 or LGPL 2 sources as far as I > can see (except that one Artistic License file Ohloh.net complains about.) That's a good point. If we can't be sure that all our sources are "v2 or later", then we can't offer "v2 or later" ourselves. Then of course we could potentially run into trouble if we link against something whose author decides to switch to v3 only at some point... in fact, we really ought to review whether any of our dependencies are already like that. Hang on, I'll have a look. I'm just looking in the Debian package copyright files here, so inaccuracies are still possible. libqt4-dev: LGPL, GPL2 or GPL3 - no problem libasound2-dev: LGPL - no problem libjack-dev: GPL2 or later or LGPL - no problem LADSPA header: LGPL - no problem DSSI header: LGPL - no problem liblrdf0-dev: GPL2 or later - no problem libfftw3-dev: GPL2 or later - no problem liblo0-dev: GPL2 only! liblircclient-dev: GPL2 or later - no problem librdf: Apache - no problem Any code we have borrowed from Qt (GPL2 or GPL3), KDE libraries (mostly LGPL) or programs (GPL2 or later), or Sonic Visualiser (GPL2 or later) is no problem. What bits have we picked up from other sources? I believe we could switch from "v2 or later" to "v2 only" without needing to confer with any outside contributors, since we wouldn't be granting any additional rights by doing so. But we couldn't so easily switch back again, or from v2 to v3, later, so it's probably not a good idea to do it too lightly. Chris ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
