You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Brian Behlendorf <br...@collab.net> on 2004/07/09 23:30:34 UTC
Re: several messages
On Fri, 9 Jul 2004, 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.
>
> I'd like to express a concern about this. I think the decision about
> incubation should not depend on the code. When a the idea / goals /
> concepts of a project can attract developers, they would certainly
> be interested in improving the code base. Couldn't it even be
> possible to re-build the code base from scratch?
>
> Is it really useful to require a certain quality standard already
> in the beginning of the incubation process?
Good points. One could propose a project without pre-existing code, along
the lines of "I think this needs to be done, and I'm want to start writing
code here for it". But, so far all the Incubator projects to date have
pointed to pre-existing code the project would bootstrap from. And that
seems to match the pattern of how many open source projects start - as a
branch or continuation from a prior one.
Bad code can definitely be the basis for later good code; Linus once said
the best way he found to spur developers to write device drivers for Linux
was to check in a clearly broken driver for the device. A missing driver
wasn't enough to incent someone with that device to take a look; a broken
or incomplete driver was instead a defect that needed to be fixed.
Much corporate software, though, is software we don't want to see.
Without casting aspersions, let's say that pressures from deadlines,
legacy customers, fixes optimized for "don't break the build tonight!"
rather than "what's the right way to solve this?" don't always result in
long-term quality. I won't use that to characterize any of the
contributions we've had to date from corporations, let me be clear; most
likely, knowing the contributors, we've been seeing the creme of the crop.
:) It's still a concern one should have when starting a project.
OpenOffice, for example, has still not gotten past much of its legacy, 4
years after launching, and still has a huge learning curve for new
developers.
> 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.
Indeed, that is one subtext to my proposal. I hold this idealistic image
of Apache as a place where developers, who have work to get done and just
want to be able to work with others on achieving the same goals (and be
protected legally while doing it) can leave their corporate affiliations
on the back of their chair and approach discussions and decision-making
based on what's best for the community and the codebase. At the same
time, the majority of contributors here (by my reckoning, a real survey
could be fun) are at least in part paid for their involvement by their
employers, and that's because the employer benefits from the resulting
work in some way.
That kind of influence isn't all bad - for example, it can help focus
efforts on specific hard technial challenges that require full-time work,
or to wrap up a development branch and make a release rather than the
perpetual beta.
On the other hand, I don't want corporations to view Apache as a "channel"
for broader adoption of a new standard they've invented, a way to get a PR
bang to help the stock price, etc. I am /not/ opposed to doing things
like joint press releases or having us talk to execs about how we work or
setting up, as we may in the future, some sort of corporate sponsorship
plan to help with fundraising. But when it comes to projects and their
technical direction, I'd like to see us adopt policies that defuse the
political tension that often arises.
One way to do that, I feel, is asking that proposals to the incubator for
new projects for incubation be able to point to pre-existing code.
Perhaps it's nothing more than a tarball sitting on a corporate server
somewhere. Perhaps it's already a SourceForge project, or codehaus, or
Alphaworks, or java.net, or whatever. By requiring that, we would be
asking companies to make the plunge into releasing something publicly
under an Open Source license (doesn't have to be Apache's license first,
though it would be once incubated) before bringing it to us. That
reduces the pressue on us to accept - instead of saying "accept this
proposal, or this code isn't released at all", it's "accept this proposal,
because Apache can help build a real community around the code."
On the flip side, I know that our brand is powerful enough in the business
world, that hearing from an internal open-source advocate, "Apache is
willing to host this project for us" could be compelling compared to
"we'll run this project ourselves" - it might even be enough to encourage
the company to make the release rather than keep it themselves. Yet, I
don't know if playing an Open Source Robin Hood is what we want to be; my
hunch is that the most successful technologies tend to originate in the
public sphere anyways, with companies pulling it in or building internal
clones for a more mass-market product.
If it's a good idea for a company to Open Source a technology, it should
be a good idea whether or not Apache is involved. If we're involved, then
in theory, we can make it even more successful, by removing the influence
and power of a single vendor/developer, and constructing a
consensus-driven "do-ocracy"[1].
Phew, OK, sorry about the long-winded piece. But yeah, that's one
meta-question I had hoped to ferret out by making my original proposal.
And then when I realized there were more practical advantages (such as
being able to evaluate the quality of the code) I felt asking the simple
question first would be a good approach.
On Fri, 9 Jul 2004, Cliff Schmidt wrote:
> +1
>
> If someone wants to propose a project, I think it is quite reasonable
> for them to show the code that would be the basis of the project.
> However, I think the interesting stuff is in the details here. For
> instance:
>
> Q: must the source be licensed under the Apache License before
> project acceptance?
>
> IMO: no
Agreed.
> Q: must the source be licensed under an OSI-approved open source
> license?
>
> IMO: I could see arguments either way. If the purpose is to assess
> the merit of the code itself, any legal mechanism that provides for
> anyone in the community to conveniently read the source should be
> acceptable, even if the license restricts distribution, for instance.
> However, if the purpose of this new rule is also to require commitment
> to open source that isn't dependent on the Apache brand, then we would
> specify the code must be available under an OSI-approved license prior
> to proposing.
It should at least be under a license that doesn't cause the person who
views the code to be contaminated should they decide to work on a similar
project elsewhere. That means, no NDA's. Given my broader thoughts
above, my ideal would be that it would be Open Source licensed already.
> Q: what would this mean for project proposals that do not include an
> initial code base?
>
> IMO: While some might say that no project should start in Apache
> without an initial code base, I would personally like to allow for
> this possibility, depending on the make-up of the initial committers
> and related communities. Therefore, I would suggest that any proposal
> that suggests the new project would be built on some particular initial
> code base would need to have that code base available for review. Any
> proposal that does not suggest this (including those that might want to
> base a new project on some other piece of software without actually
> using the old source as a base) would not need to open any source.
Right. Presumably if slightly later on there's a body of code that looks
interesting, it can be evaluated by the PPMC for the same reasons.
> Q: if the bar to bring projects into the incubator is meant to be
> relatively low as long as the legal and community issues are reasonable,
> should we even be evaluating the code base at all?
>
> IMO: we could probably have long discussions about whether the best
> long term future for the ASF requires some degree of technical
> evaluation of projects or not; however, without diving into this issue
> for the moment, I would suggest that perusal of any significant code
> base could be done just for any glaring problems (potential legal
> entanglements with dependencies, inappropriate technical dependencies,
> etc). Problems that are found may not necessarily have to be fixed
> before project approval, but I think it would be nice to allow major
> issues to be discovered and responded to during the evaluation of the
> proposal.
+1.
> Q: how close must the evaluated code base be to the one eventually
> contributed after project acceptance? In other words, could a proposal
> show most of the planned contribution without having 100% of it ready?
> Could the contributor make changes to the source between the time of
> proposal and the initial grant (e.g. what about changing the license
> header? what about doing a little more than that?)
>
> IMO: we shouldn't put strict limits on this -- any abuse of the
> intention behind this requirement (such as a significant bait-and-switch
> with code bases) would probably be obvious and could be dealt with on a
> case-by-case basis.
+1.
Anyone want to throw this up on the Wiki and see what sticks?
Brian
[1] I've heard a couple people use the term here, but Google appears to
point to http://www.libertyforall.net/2002/archive/do-ocracy.html as the
origin of the term...
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Consensus! (was Re: several messages)
Posted by Brian Behlendorf <br...@collab.net>.
On Wed, 14 Jul 2004, Rodent of Unusual Size wrote:
> Brian Behlendorf wrote:
>>
>> Anyways, I'll desist on this if it doesn't seem like there's convergence
>> towards something. Like many conversations in the ASF these days the
>> responses strike me more as "here's where you're wrong" rather than a
>> constructive discussion, to which I feel compelled to respond
>> point-by-point (trying to find middle grounds), and I don't have the
>> energy to campaign for something that just seemed like a simple oversight.
>
> sorry if i, at least, have come across this way. let me restate my
> personal position: i'm fine with 'show us the code before acceptance'
> being a strong *recommendation*, but not with it being a requirement.
> and i think the decision about whether or not the code needs to be seen
> first should be left up to the incubator pmc.
OK, I think this is reasonable. Quibbling about requirement vs. strong
suggestion is too minor to bother :)
> i don't like ndas on principle, and hope they can be avoided. however,
> if the incubator pmc thinks that's the way to go for a particular
> proposal, i think it's their call. (although i don't promise not to
> lobby against it. ;-)
I'd be against it as well, but agree.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Review under NDA (was RE: several messages)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Can we wait to really hash this out until someone does?
Was just responding to a request to clarify my earlier reply to you and Ken.
I've nothing more to add. :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Review under NDA (was RE: several messages)
Posted by Brian Behlendorf <br...@collab.net>.
On Wed, 14 Jul 2004, Noel J. Bergman wrote:
> I'm told my earlier message was unclear.
>
> Unless our legal counsel changes my understanding, which I consider rather
> unlikely, since I've already pursued the question, I am absolutely opposed
> to reviewing code under an NDA (unless it is something unusual, like it
> expires without prejudice in two weeks time). I intend to continue being
> very protective of the Foundation and our members, and that includes
> preventing them from "contamination due to exposure to code."
I don't think any of us agree that it would be a bad idea; fortunately, no
one currently is asking us to, and AFAIK no one has in the past. Can we
wait to really hash this out until someone does?
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Review under NDA (was RE: several messages)
Posted by "Noel J. Bergman" <no...@devtech.com>.
I'm told my earlier message was unclear.
Unless our legal counsel changes my understanding, which I consider rather
unlikely, since I've already pursued the question, I am absolutely opposed
to reviewing code under an NDA (unless it is something unusual, like it
expires without prejudice in two weeks time). I intend to continue being
very protective of the Foundation and our members, and that includes
preventing them from "contamination due to exposure to code."
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: several messages
Posted by "Noel J. Bergman" <no...@devtech.com>.
Rodent of Unusual Size wrote:
> i don't like ndas on principle, and hope they can be avoided. however,
> if the incubator pmc thinks that's the way to go for a particular
> proposal, i think it's their call. (although i don't promise not to
> lobby against it. ;-)
I do, unless our legal counsel changes my understanding, which I consider
rather unlikely, since I've already pursued that question. I intend to
continue being very protective of the Foundation and our members, and that
includes preventing them from "contamination due to exposure to code."
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: several messages
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
-----BEGIN PGP SIGNED MESSAGE-----
Brian Behlendorf wrote:
>
> Anyways, I'll desist on this if it doesn't seem like there's convergence
> towards something. Like many conversations in the ASF these days the
> responses strike me more as "here's where you're wrong" rather than a
> constructive discussion, to which I feel compelled to respond
> point-by-point (trying to find middle grounds), and I don't have the
> energy to campaign for something that just seemed like a simple oversight.
sorry if i, at least, have come across this way. let me restate my
personal position: i'm fine with 'show us the code before acceptance'
being a strong *recommendation*, but not with it being a requirement.
and i think the decision about whether or not the code needs to be seen
first should be left up to the incubator pmc.
i don't like ndas on principle, and hope they can be avoided. however,
if the incubator pmc thinks that's the way to go for a particular
proposal, i think it's their call. (although i don't promise not to
lobby against it. ;-)
- --
#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
iQCVAwUBQPVaNprNPMCpn3XdAQG3BwP/ZkdWpubZVHa1+N0SeeIlWzwaGMx3XUmt
NnJ93DDd+cEx1SG8UJJ/wy5vqV29V0oM+FVVfX23TAWI5gCtI40xSKkEQmXJuBMM
aC/yiVE29A5DkV1Wb71ZgDlc9eXqnZx9DSdo0ITvZ5P4iKcJoDW4+6pmjsNltam1
YvbknT4yI6E=
=9eWV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
PR issues (was: several messages)
Posted by "Noel J. Bergman" <no...@devtech.com>.
Steven Noels wrote:
> Noel J. Bergman wrote:
> > One is an older one that is not from a big company, and is
> > seemingly and finally starting to get squared away. The
> > other one is a recent submission that more closely fits
> > your description, and concerns have been raised to the
> > contributor about it.
> Perhaps also a hint towards Brian's feelings about evolving
> discussion styles: could we name things here? I see reference
> to specific "projects" but cannot/don't want to name-guess.
I don't believe that this is what Brian meant about evolving discussion
styles. I believe he was referring to a defensive mode of discussion versus
trying to more constructively address concerns being raised.
Brian has a perfectly valid concern, which to restore context is:
> > > it's interesting to note that those incubator projects that
> > > consist of code from larger companies and associated with
> > > a big-bang PR tend to not see as much participation in the
> > > incubator as the more grass-roots proposals like Geronimo
> > > or the more modest launches like XMLBeans. So I'm trying
> > > to explore why, and how can we improve.
Without wanting to mention names, I agree with Brian about the problem, but
also observe that this has happened with the source having been visible
prior to Incubation. So that's why I separate those two issues, and concur
with a goal to improve participation, and prevent abuse of the Incubator for
PR purposes.
I have suggested to the PRC folks some basic guidelines for Incubator
related PR:
- promote the ASF as a place for exciting new things.
- attract developers to help build them.
- require Incubator branding since while these communities
are in the Incubator incubated, they do not have the
imprimatur of being official ASF projects.
- discourage PR prior to actually bringing the project to the ASF.
The last item gets into timing issues, but we don't want a situation were we
have an extensive period of PR and have to keep prodding the Grantor to
start incubation.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: several messages
Posted by Steven Noels <st...@outerthought.org>.
On 14 Jul 2004, at 16:58, Noel J. Bergman wrote:
> One is an older one that
> is not from a big company, and is seemingly and finally starting to get
> squared away. The other one is a recent submission that more closely
> fits
> your description, and concerns have been raised to the contributor
> about it.
This was a lovely discussion to read - unfortunately I wasn't able to
participate due to intermittent, read-only mail access. Perhaps also a
hint towards Brian's feelings about evolving discussion styles: could
we name things here? I see reference to specific "projects" but
cannot/don't want to name-guess.
For the record: I resonate with much of Brian's worries, unfortunately
in real life all of this might boil down to case-by-case judgements by
hopefully well-informed mentors or ASF peeps, rather than following a
policy checklist that anyone can implement. And I think this is the
gist of the Incubator: actual folks reasoning about case-by-case
decisions as history unfolds.
And the fact that BigCo is discovering the need for an open source
strategy, and regards the ASF as an ideal platform for this, will
confront us with the need to have a good intersection of ASF folks
dealing with incubation directly, rather than reasoning about
incubation rules in general.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: several messages
Posted by "Noel J. Bergman" <no...@devtech.com>.
Brian Behlendorf wrote:
>>> On the other hand, I don't want corporations to view Apache as a
"channel"
>>> for broader adoption of a new standard they've invented, a way to get a
PR
>>> bang to help the stock price, etc.
>>
>> i do not think that is going to happen.
>
> It's happened already, Ken.
>
> it's interesting to note that those incubator projects that consist of
> code from larger companies and associated with a big-bang PR tend to not
> see as much participation in the incubator as the more grass-roots
> proposals like Geronimo or the more modest launches like XMLBeans. So
> I'm trying to explore why, and how can we improve.
Ok, this is a different issue. I share your concern and desire for a
solution. I am not sure which projects you have in mind, but I can think of
two projects on my radar that might fit the bill. One is an older one that
is not from a big company, and is seemingly and finally starting to get
squared away. The other one is a recent submission that more closely fits
your description, and concerns have been raised to the contributor about it.
However, the source for that has been available in the public eye, so the
proposed litmus test would not have corrected the problem. I think we're
all open to suggestions that would.
> when I get calls out of the blue from companies who (paraphrased,
> exaggerated slightly) "want to open-source this prototype legacy
> code we wrote (that we couldn't build a business around) through
> Apache so we can get a PR boost for our upcoming [IPO/product
> release/funding announcement/etc]."
I'll go back to the Community aspect. I would hope that such a proposal
would not be of interest, but I'm concerned about what ASF Members want to
incubate.
The benefit to the contributor is not a criteria, although if we've decided
that a project is a good fit, I don't mind the mutual benefit of a splash.
If we have a project coming from a corporation with a bunch of developers,
we want to build an independent community for it. Having a splash can help
US, too, since it can be used to draw in new contributors. And it gives us
a chance to work with, and see how, the new community handles expanding its
committer base.
> Like many conversations in the ASF these days the responses strike
> me more as "here's where you're wrong" rather than a constructive
> discussion
I'm sorry you feel that way. For myself, I considered your proposal, and
many of the responses.. As a general thing, I would like to see the code.
My objection was to it as a mandate, which is why I did point out the
reasons why I did not think it made sense as a mandate. I am very
interested in what things we can do to prevent abuse of the ASF Incubator.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: several messages
Posted by Brian Behlendorf <br...@collab.net>.
On Tue, 13 Jul 2004, Rodent of Unusual Size wrote:
> Brian Behlendorf wrote:
>>
>>> 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.
>>
>> Indeed, that is one subtext to my proposal.
>
> [snippage]
>
> i don't think i'm getting this. are you saying that, if they want to
> avoid revealing the code until the concept has been accepted, we should
> automatically ignore the proposal? 'show us the code or take a walk' ?
It's a statement that "Apache accepts it as a project" shouldn't be the
trigger for a company to release its code under an Open Source license.
It's my opinion, but I was looking to see who might share it. Showing the
code is a litmus test of sorts of the proposers' intents, and I still
think it's useful on technical and legal grounds in deciding whether to
even allow a project in the front door.
>> On the other hand, I don't want corporations to view Apache as a "channel"
>> for broader adoption of a new standard they've invented, a way to get a PR
>> bang to help the stock price, etc.
>
> i do not think that is going to happen.
It's happened already, Ken. It's not been much of a problem in practice,
and I think we've kind of looked at this as a grand experiment of sorts...
but it's interesting to note that those incubator projects that consist of
code from larger companies and associated with a big-bang PR tend to not
see as much participation in the incubator as the more grass-roots
proposals like Geronimo or the more modest launches like XMLBeans. So I'm
trying to explore why, and how can we improve.
> not only because we've been publicly thorny about this issue in the
> past, but because the people directly tasked with the interface -- the
> incubator -- take their jobs seriously and are especially vigilant.
I don't intend my "it's happened" as a slight on incubator people, nor
should this be seen as a bad thing - it goes back to my own involvement in
starting Jakarta and XML, and I think it's been a useful thing. But I
know it's the impression that people in the public have when I get calls
out of the blue from companies who (paraphrased, exaggerated slightly)
"want to open-source this prototype legacy code we wrote (that we couldn't
build a business around) through Apache so we can get a PR boost for our
upcoming [IPO/product release/funding announcement/etc]." Such people are
of course ill-informed about why we exist, what we can do for them, and
what we expect from groups who approach us to become projects; but I
thought it would be useful to see if there are things we can do at the
inception of an incubator project to address this mis-perception in a way
copacetic to our own principles of fairness, transparency, and community.
That's when a requirement that the code be already published on a public
web site under an open source license (or otherwise available for
inspection in an unencumbered way) seemed an interesting litmus test.
>> But when it comes to projects and their technical direction, I'd like
>> to see us adopt policies that defuse the political tension that often
>> arises.
>
> i don't see that a 'show us the code' requirement is a technical direction
> at all. i see it as a political/philosophical stance.
You might not have understood me above. I agree, it is a statement of
philosophy, as much as our vaunted "three +1s, no vetos" is a statement of
philosophy. When the code is available at the time the incubator is
considering whether to accept a project into the incubator, the discussion
can be quite technical - is the code base suitable for the direction the
proposed project would want to head in, does this project overlap too much
with another existing project, etc. On the other hand, with only the
description of what the code does, you have to trust the individuals or
company behind the proposal to be accurately describing what the code
does, its quality/suitability, and perhaps that proposer's history in
prior situations. The latter feels more politically tense" than the
former - thus my statement quoted above.
> i have no problem with the incubator making a case-by-case evaluation of
> what's needed to process/accept a proposal. i *do* have a problem with
> setting down a policy that ties its hands, whether that policy is 'show
> us the code' or 'you don't need to show us the code.'
Every requirement is a "ties its hands" kind of thing - none are, prima
facie, good or bad. It's what we decide for ourselves. It's kind of like
the no-more-than-50%-from-a-single-employer requirement... er,
guideline... er, suggestion... for projects to graduate out of the
incubator. Flexibility is good, but so is predictability.
>> That reduces the pressue on us to accept - instead of saying "accept
>> this proposal, or this code isn't released at all"
>
> i think everyone involved is strong-willed enough to bristle and
> take umbrage at such a thing, rather than being cowed by it.
Obviously it's not said directly as I said it above; the communication is
more subtle. And you did quote me out of the context that makes that
sentence make sense.
> 'show us the code' could be construed as 'we don't want to even look
> at your code unless you let everyone else see it at the same time.'
> i'm not sure how i feel about that construction.
Doesn't everyone get a look at it eventually anyways? Isn't subscription
to general@incubator open anyways?
In fact I thought we had agreement that allowing only select people to
look at the code under NDA was not the best idea... I certainly wasn't
arguing for it.
Anyways, I'll desist on this if it doesn't seem like there's convergence
towards something. Like many conversations in the ASF these days the
responses strike me more as "here's where you're wrong" rather than a
constructive discussion, to which I feel compelled to respond
point-by-point (trying to find middle grounds), and I don't have the
energy to campaign for something that just seemed like a simple oversight.
Carry on.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: several messages
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
-----BEGIN PGP SIGNED MESSAGE-----
Brian Behlendorf wrote:
>
>> 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.
>
> Indeed, that is one subtext to my proposal.
[snippage]
i don't think i'm getting this. are you saying that, if they
want to avoid revealing the code until the concept has been
accepted, we should automatically ignore the proposal? 'show
us the code or take a walk' ?
> On the other hand, I don't want corporations to view Apache as a "channel"
> for broader adoption of a new standard they've invented, a way to get a PR
> bang to help the stock price, etc.
i do not think that is going to happen. not only because we've been
publicly thorny about this issue in the past, but because the
people directly tasked with the interface -- the incubator -- take
their jobs seriously and are especially vigilant.
> But when it comes to projects and their
> technical direction, I'd like to see us adopt policies that defuse the
> political tension that often arises.
i don't see that a 'show us the code' requirement is a technical direction
at all. i see it as a political/philosophical stance.
> One way to do that, I feel, is asking that proposals to the incubator for
> new projects for incubation be able to point to pre-existing code.
as before, i disagree. i have no problem with the incubator making a
case-by-case evaluation of what's needed to process/accept a proposal.
i *do* have a problem with setting down a policy that ties its hands,
whether that policy is 'show us the code' or 'you don't need to show us
the code.'
> That
> reduces the pressue on us to accept - instead of saying "accept this
> proposal, or this code isn't released at all"
i think everyone involved is strong-willed enough to bristle and
take umbrage at such a thing, rather than being cowed by it.
'show us the code' could be construed as 'we don't want to even look
at your code unless you let everyone else see it at the same time.'
i'm not sure how i feel about that construction.
- --
#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
iQCVAwUBQPRKUZrNPMCpn3XdAQHfVQQAsqsWx2dT/hm+PCAK3pxJaTruPhigctEz
Lkb3dAAyMilDD7o58HPYLpl5zUS/H+SAfcXYqeg2WKDM/+V5JZLsArM0GPZmywDt
uCK5lcvoQ2arfHJmmBOr0eGXwphLULaID4vw16ZlysFrQ+5hqZrPvF/s7iYc86zH
lOO2jbvAVhs=
=NmT7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org