incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <>
Subject Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts
Date Tue, 23 Jun 2015 23:16:49 GMT
On Tue, Jun 23, 2015 at 6:22 AM, Alex Harui <> wrote:
> Yep, that’s the “tax” of Apache.  IMO, its main reason for existing is to
> make users of ASF projects feel comfortable incorporating our source into
> their projects because we’ve done our due diligence on the IP/legal stuff
> on every line of source.  Even for “alpha” quality code, when we say
> “here, go try this, it may be buggy” we are also saying “we feel pretty
> good it is safe to eventually be part of your production code and won’t
> have effects on how you license and use this code”.  Yes, folks shouldn’t
> put alpha code into production, but you know how reality is: some manager
> sees your POC and suddenly you have a team adding more code on top of it.

I think I just got it! Let me continue the tax analogy: at this point ASF has
a flat one-size-fits-all tax of putting something, anything out there. We
optimize for the most demanding case: the case of guaranteeing clean
IP AND reasonably stable functionality.

What I'm suggesting here is that perhaps we should think about having
a progressive tax. A tax that starts small for things that have very little
potential to cause ASF trouble and culminate with the most demanding
one. The one we currently have today.

Does this make sense?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message