On 1/31/11, Luc Maisonobe <luc.maison...@free.fr> wrote: > Le 31/01/2011 19:49, Phil Steitz a écrit : >> On 1/31/11 12:38 PM, Matt Benson wrote: >>> +1, as long as your "seed code" is authored solely by yourself and >>> cannot be claimed the property of any other entity, my ignorance of EU >>> IP law notwithstanding. >>> >> Good point. I know Luc is well aware of this, but I should have >> added clean IP as a requirement. > > Yes, I am aware of this. As I already have an ICLA on file and as I am > the sole author of this and will of course put the Apache header and > license file, I wonder if I need to send a Software Grant too. It seems > overkill to me but I can do it, of course. >
Hi, Luc--I hope you didn't read my input as intending to cast doubt on what you may or may not know. But I did make the point to suggest the idea of whether an SGA would be needed. From what you've said, if I were in your place I would also deem it overkill. If it's just code from your private workspace that's never yet seen the light of day it would seem to fall under your ICLA. br, Matt > Luc > >> >> Phil >>> Matt >>> >>> On 1/31/11, Phil Steitz <phil.ste...@gmail.com> wrote: >>>> On Mon, Jan 31, 2011 at 11:23 AM, <luc.maison...@free.fr> wrote: >>>>> Hi all, >>>>> >>>>> I have a bunch of code lying around to deal with BSP trees (useful in >>>>> different kinds of geometry modeling) and I would like to start a new >>>>> sandbox component to improve it and maybe merge it back to [math] if >>>>> useful or let it grow as a standalone component. >>>>> >>>>> Do you agree with the idea ? How do I start a new sandbox component ? >>>>> >>>> Just create the directory and start hacking :) >>>> >>>> Seriously, any Commons committer can create a sandbox component at any >>>> time. All that is required is to state intention to do so. Talking >>>> about the idea is good to gauge interest and as always to improve >>>> ideas; but to get started all you need to do is create the directory >>>> in svn. >>>> >>>> Phil >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
