On Tue, 2010-10-05 at 07:27 +0000, Mark Struberg wrote: > Hi Upayavira! > > It's technically possible to restrict SVN paths afaik. Don't we do > this for parts of our internal member/infra area already? > > The thing is that I first like to browse through the sources, just to > be sure. Since the project already uses ASL since a long time, I doubt > that there are any problems. > > We can also move this into isis/contribution/ and add a README > explaining that these are the original projects which got moved to the > ASF repos and do not necessarily express the opinion of the ASF.
Technically it is possible to prevent people viewing a portion of *our* copy of our repo. But folks can collect a copy via rsync, and they have complete access to the whole thing. Any protection we put on will not work then. Has it been in a public SVN? If so, just dump it into Apache's SVN and do the review in public. That is all a part of what incubation involves - that kind of code audit. Upayavira --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
