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.

LieGrue,
strub



--- On Tue, 10/5/10, Upayavira <[email protected]> wrote:

> From: Upayavira <[email protected]>
> Subject: RE: [jira] Commented: (ISIS-3) Import Naked Objects code into the 
> Apache repo
> To: [email protected]
> Date: Tuesday, October 5, 2010, 6:32 AM
> On Mon, 2010-10-04 at 20:55 +0000,
> Mark Struberg wrote: 
> > Robert already created 
> > https://issues.apache.org/jira/browse/INFRA-3039
> > 
> > which links to ISIS-3
> > 
> > Is it possible to import the whole svn dump into 
> > /incubator/isis/private/initial-import/nakedobjects
> > There will be other imports (NO sister projects for
> tooling) too. Our
> > idea was to make the whole private folder only
> accessible for
> > committers (and not public) because this stuff is not
> yet IP cleared.
> 
> "IP cleared"? Is there anything you don't have the right to
> publish in
> there? Or is it just that you haven't ensured everything is
> licensed
> correctly?
> 
> The /asf/repos SVN repository is considered entirely
> public. Folks can
> get dumps of it, that will not sit behind the ASF authz
> file, so
> anything that you put in there will be visible to some
> folks.
> 
> Remember that the rules for putting stuff into SVN are much
> more relaxed
> than those for making releases. So long as you aren't
> breaking
> copyright, you can put stuff into SVN.
> 
> What is the stuff that you don't feel comfortable having
> public?
> 
> Upayavira
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to