Re: proposal: modify incubation application process to require a reference to the code itself

[Andreas Hartmann <an...@apache.org>]

Andreas Hartmann wrote:

> Brian Behlendorf wrote:
> 
>>
>> In walking through the incubation documents (helping a couple of 
>> groups who have asked me about how to do this) it struck me that there 
>> was no requirement that the proposal provide a link to download and 
>> evaluate the code around which a project is being proposed - in fact 
>> it appears the code itself could be kept secret until project 
>> acceptance into the incubator.

Another thought:

What if a company considers to introduce an open source strategy,
but the decision depends on whether the code is accepted as an
Apache project or not? I think they will avoid showing the code
before the project is accepted or rejected.

I'm not experienced when it comes to these things, I hope you
tolerate my silly statements and maybe I can even learn
something :)

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: proposal: modify incubation application process to require a reference to the code itself

[Rodent of Unusual Size <Ke...@Golux.Com>]

-----BEGIN PGP SIGNED MESSAGE-----

Sanjiva Weerawarana wrote:
>
> Given that there are many places where one can start an open source
> project, IMO it makes perfect sense for Apache to have a higher
> standard. If the company's strategy question is whether to open source
> or not, then if the decision depends on acceptance to Apache then I'd
> say we're better off without it!

i disagree.  for one thing, this is basically stating that the proposal
isn't sufficient.  i disagree with that on principle; if the proposal
isn't enough to allow us to make up our minds, propping it up with the
code seems makeshift.

for another thing, the asf *does* have a higher standard: we require
transfer of ownership and ip.  it makes perfect sense to me that a
company may be willing to transfer those to the asf, but *not* be
willing to throw them into the open -- which is the potential if
the code is exposed before the acceptance and transfer.
- --
#ken	P-)}

Ken Coar, Sanagendamgagwedweinini  http://Ken.Coar.Org/
Author, developer, opinionist      http://Apache-Server.Com/

"Millennium hand and shrimp!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBQPJiFJrNPMCpn3XdAQHM7wP8CxzWkngqfh7hA88MAmI8JTloVv0dHDP7
X1/uHGQz1wBZ/ZxavOb1oTHfo+n9AkJnVq5TnjTutYymX8W7nEAF8YNG2OfBILoC
zlPqWyL51jUVNvtI2h0DdgPjizb5B66OzhTF1UT280W/lg6chkom5eV75a0kgquv
XE/9iyHq/VQ=
=Seyj
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: proposal: modify incubation application process to require a reference to the code itself

[Sanjiva Weerawarana <sa...@watson.ibm.com>]

"Andreas Hartmann" <an...@apache.org> writes:
> Another thought:
> 
> What if a company considers to introduce an open source strategy,
> but the decision depends on whether the code is accepted as an
> Apache project or not? I think they will avoid showing the code
> before the project is accepted or rejected.

Given that there are many places where one can start an open source
project, IMO it makes perfect sense for Apache to have a higher
standard. If the company's strategy question is whether to open source
or not, then if the decision depends on acceptance to Apache then I'd
say we're better off without it! 

Sanjiva.


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org