Date: Wed, 18 Aug 2004 16:11:44 +0100 From: Doug Rabson <dfr@nlsystems.com> To: freebsd-current@freebsd.org, drhodus@machdep.com Cc: Roman Kurakin <rik@cronyx.ru> Subject: Re: Public Access to Perforce? Message-ID: <200408181611.45299.dfr@nlsystems.com> In-Reply-To: <fe77c96b04081807281c76200@mail.gmail.com> References: <200408160104.03708.chris@behanna.org> <4123603F.2050201@cronyx.ru> <fe77c96b04081807281c76200@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 18 August 2004 15:28, David Rhodus wrote: > On Wed, 18 Aug 2004 17:57:19 +0400, Roman Kurakin <rik@cronyx.ru> wrote: > > I fully agree with you. But this not affect "open source"ness. > > I'd rather call it open development. > > > > rik > > Yes, it does when the public doesn't have direct access to the > development work going on. Thats what started this thread in the > first place. This is ludicrous. You don't have access to my private source trees on my private machines where I test and develop software before committing it to CVS. How does that change the fact that when I commit that software it has a standard two clause BSD open source license. Its the results that are open source, not the pre-commit experiments. Next you will be demanding that everyone writes every single thought they have about FreeBSD into some interminable web log so that the project can be truly 'open source'.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408181611.45299.dfr>