* Blog mentions: Garrett Rooney: Joey Hess: http://kitenet.net/~joey/blog/entry/thoughts_less_random_than_expected-2005-10-17-19-52.html Brett Glass article on FreeBSD history: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=82360+0+/usr/local/www/db/text/2002/freebsd-chat/20020929.freebsd-chat * Release management: From: Brad Appleton Subject: Re: Release management policy fundamentals To: Subversion Users Date: Thu, 13 Jan 2005 02:24:41 -0600 Reply-To: Brad Appleton Thanks Ron, Tom and Jason for the kind words. I started a page with a collection of links to online resources on branching and merging at You'll find several papers there that deal with branching and release management policy (including stuff written by folks other than myself :-) I also highly recommend Michael E. Bays book "Software Release Methodology" Jason Butlin wrote: > Try this http://www.cmcrossroads.com/bradapp/acme/branching/ Ron Bieber wrote: > The book referred to below is EXCELLENT for the types of questions you > are asking. I highly recommend picking it up as well. > > On Wed, 2005-01-12 at 01:13, Tom Mornini wrote: > > Here's a good book, written by someone who reads this list. :-) > > > > http://www.amazon.com/exec/obidos/ASIN/0201741172/103-5855470-7615011 -- Brad Appleton www.bradapp.net Software CM Patterns (www.scmpatterns.com) Effective Teamwork, Practical Integration "And miles to go before I sleep." -- Robert Frost * Google for "release management within open source projects" to get Justin's PDF. * http://liw.iki.fi/liw/texts/debian-lessons Lars Wirzenius on Debian project management * http://www.for-the-people.org/blog/entries/view Whoa! List of F/OSS events, from a political not technical perspective. * Paper describing freedom as a motivation: http://freesoftware.mit.edu/papers/lakhaniwolf.pdf * "The Politics of Magic Pixie Dust" by Alek Tarkowski http://terminal.n17.waw.pl/stable/pliki/tarkowski_aoir_paper.pdf * describes the vanishingly rare cases where software can be open but not free, according to some slight discrepencies of definition, but in practice, you will probably never encounter software that is one without being the other. * Links: www.benkler.org http://cas.uchicago.edu/workshops/stss/ http://opensource.mit.edu/papers/mccormick.pdf [big] Also, Walt Scacchi's stuff http://sourceforge.net/projects/aistockbot/ (for laughs) "How About a Nice Cup of ..." http://people.debian.org/~branden/humor/the_real_official_motto.jpeg * Footnote the word "culture" with a note that academic anthropologists study free software culture: Though there are academic anthropologists studying free software culture, for example see . * Open Source's take on the terminology question: http://www.opensource.org/advocacy/faq.php http://www.opensource.org/advocacy/case_for_hackers.php#marketing http://www.opensource.org/advocacy/free-notfree.php * Sun vs RedHat: http://www.eweek.com/article2/0,1759,1573433,00.asp * Kuro5hin article on SourceForge: * Genealogical history of computer languages (with a great chart) http://www.levenez.com/lang/ * '™' / '®' * ACM Queue article by Jordan Hubbard, basically an Open Source overview. Licensing, community management discussions; excellent references. http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=151 * David Wheeler's SCM comparison essay: http://www.dwheeler.com/essays/scm.html * Quick Reference Guide to Free Software Revision Control Systems http://www.zooko.com/revision_control_quick_ref.html * Google's domain-restrict feature: http://www.google.com/help/refinesearch.html#domain * Comparison of free software hosting services: http://www.ibiblio.org/fosphost/exhost.htm * Mako's doc on how to run a free project. http://tldp.org/HOWTO/Software-Proj-Mgmt-HOWTO/intro.html * commentary on Apache Avalon http://www.jadetower.org/muses/archives/000146.html * Bug trackers and related stuff. http://linas.org/linux/pm.html" * Serendipitous find from Mako: http://mako.yukidoke.org/projects/collablit/writing/BenjMakoHill-CollabLit_and_Control.pdf * Andy says: Zak Greant was a key spokesperson for MySQL, and he has thought deeply about their funding and business model. Now he's moved on, but I believe you can still reach him through zak@mysql.com. I've talked to him a lot and I'm sure he'd be willing to talk to you for your book.