Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: The C Containers library Date: Sat, 31 Oct 2015 13:40:27 -0700 Organization: None to speak of Lines: 26 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="26907"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+q1yt09NaEexd21Ra0aE39" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:HxlaO8R5LFgtOZL64wQNGsFaqwc= sha1:oEkEu2xiGRtbHSqH77ltWVhUUvM= Xref: csiph.com comp.lang.c:74490 jacobnavia writes: [...] > The C containers library is written in C and features nice stuff. Fully > open source (no license) available at: > > https://code.google.com/p/ccl/ "Project Hosting on Google Code will close on January 25th, 2016." You might consider migrating to another site. I use GitHub myself; there's even an "Export to GitHub" button on the web page. The web page says it's under the "New BSD License". Was that your choice, or was it the default when you set up the project? I offer no opinion on how or whether you *should* license your project, but the phrase "no license" is unclear. You can release it to the public domain if you like, but be aware that "public domain", "open source", and "no license" are three *very* different things. (I'm curious to see how and whether you manage to interpret this as a personal attack.) -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"