Most of the individuals involved in reviewing open source licenses have reviewed drafts of this
license, but they could not review the final one
until it was approved by the ASF itself. So now it
is final and they can let us know whether the changes
we made in response to their comments were sufficient. We could not reasonably ask them to pre-approve a moving target.
Of course it could be a conflict, though I am unable
to see what I could possibly gain by misstating the
background for Apache or misinterpreting the results.
I'd never risk my reputation as a Ph.D. just because
some people believe in OSS marketing (I don't).
The statistical study was performed by Audris based
on raw data sources that he selected. My part was
to help in phrasing the hypotheses (not our
hypotheses, but what others
have been saying in
regard to OSS) and writing the Apache history, along
with some general word-smithing.
We are very careful not to over-generalize in the paper.
The hypotheses are not, and cannot be, proven by
the study -- that is impossible. The point of the study
is to provide a repeatable analysis of two projects and
see whether the hypotheses hold for those projects.
The same analysis can then be performed by others.
That is the most we can do in studies of software
projects, since it is impossible to repeat a real
project many times.
Re:What about the "waka" protocol by Roy Fielding?
on
HTTP's Days Numbered
·
· Score: 1
Waka has not yet been released in specification form due to the economy sucking away all of my free time, and that talk never happened because ApacheCon 2001 Europe was cancelled. I did get a lot of work done on it during my vacation just prior to 9/11.
I recently changed jobs and am now
chief scientist at Day Software.
My protocol work will get back on track soon and I will be able to introduce waka at ApacheCon 2002.
However, I should note that Don Box (whom I know from UCI) is mistaken in his complaints. HTTP is not an RPC (SOAP is, but SOAP is not and never will be part of the HTTP standard). HTTP has included an asynchronous completion mechanism since 1994 (see the 202 Accepted response). I have no idea why folks at Microsoft can't read the specification of HTTP and make use of the protocol as it was designed to be used.
I have plenty of reasons to replace HTTP with a better protocol, but none of them involve making the Web act like a DCOM service, which is simply a bad architecture for the Internet.
Re:I'm more worried about the precompiled binarys
on
Themes.org Cracked
·
· Score: 1
None of the downloadable binaries or packaged distributions at apache.org were modified by the cracker.
Slashdot Mirror
Most of the individuals involved in reviewing open source licenses have reviewed drafts of this license, but they could not review the final one until it was approved by the ASF itself. So now it is final and they can let us know whether the changes we made in response to their comments were sufficient. We could not reasonably ask them to pre-approve a moving target.
Of course it could be a conflict, though I am unable to see what I could possibly gain by misstating the background for Apache or misinterpreting the results. I'd never risk my reputation as a Ph.D. just because some people believe in OSS marketing (I don't).
The statistical study was performed by Audris based on raw data sources that he selected. My part was to help in phrasing the hypotheses (not our hypotheses, but what others have been saying in regard to OSS) and writing the Apache history, along with some general word-smithing.
We are very careful not to over-generalize in the paper. The hypotheses are not, and cannot be, proven by the study -- that is impossible. The point of the study is to provide a repeatable analysis of two projects and see whether the hypotheses hold for those projects. The same analysis can then be performed by others. That is the most we can do in studies of software projects, since it is impossible to repeat a real project many times.
Waka has not yet been released in specification form due to the economy sucking away all of my free time, and that talk never happened because ApacheCon 2001 Europe was cancelled. I did get a lot of work done on it during my vacation just prior to 9/11.
I recently changed jobs and am now chief scientist at Day Software. My protocol work will get back on track soon and I will be able to introduce waka at ApacheCon 2002.
However, I should note that Don Box (whom I know from UCI) is mistaken in his complaints. HTTP is not an RPC (SOAP is, but SOAP is not and never will be part of the HTTP standard). HTTP has included an asynchronous completion mechanism since 1994 (see the 202 Accepted response). I have no idea why folks at Microsoft can't read the specification of HTTP and make use of the protocol as it was designed to be used.
I have plenty of reasons to replace HTTP with a better protocol, but none of them involve making the Web act like a DCOM service, which is simply a bad architecture for the Internet.
None of the downloadable binaries or packaged distributions at apache.org were modified by the cracker.