Public Access to Perforce?
Aniruddha Bohra
bohra at cs.rutgers.edu
Wed Aug 18 08:24:14 PDT 2004
Could this please be moved to -chat or something.
Current has too much traffic as it is :(
Thanks
Aniruddha
David Rhodus wrote:
>On Wed, 18 Aug 2004 16:11:44 +0100, Doug Rabson <dfr at nlsystems.com> wrote:
>
>
>>On Wednesday 18 August 2004 15:28, David Rhodus wrote:
>>
>>
>>>On Wed, 18 Aug 2004 17:57:19 +0400, Roman Kurakin <rik at 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.
>>
>>
>
>Well that is fine if that is the method in which you are using the
>perforce system. But when overly large commits hit the cvs tree from
>perforce which should have came with incremental changes so there
>could be more detail public scrutiny, etc.. there is a problem.
>
>
>
More information about the freebsd-current
mailing list