Guys,
Be careful when you edit the wiki. Wiki program will send a mail to
all subscribers (e.g. IPMC, many committers, ..., etc) by trivial
changes.
So, we should collate all on our list.
- Edward
On Thu, Jul 24, 2008 at 3:37 PM, Apache Wiki [EMAIL PROTECTED] wrote:
Dear Wiki user,
You
Dear all, Sorry for mis-send.
- Edward
On Thu, Jul 24, 2008 at 4:12 PM, Edward J. Yoon [EMAIL PROTECTED] wrote:
Guys,
Be careful when you edit the wiki. Wiki program will send a mail to
all subscribers (e.g. IPMC, many committers, ..., etc) by trivial
changes.
So, we should collate all on
Up for vote, the Buildr 1.3.2 release. The release vote passed within
the PPMC with +3 (+5 including non-binding votes) and no -1:
http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/[EMAIL
PROTECTED]
We're voting on the source distributions available here:
On Wed, Jul 16, 2008 at 5:59 AM, Bertrand Delacretaz
[EMAIL PROTECTED] wrote:
Could the respective mentors fix that?
Other projects might be missing as well, I just checked based on this
month's incubator board report.
After waiting a week for people to step up, I went ahead and added a
page
Michael Stroucken wrote:
I have not been assigned to any part of this project as an employee of the
university, and I am participating out of personal interest. I believe the
project can improve services not just at our data centers, but at data centers
in general.
[...]
Finally, as for the
On Wed, 2008-07-23 at 11:10 -0700, Doug Cutting wrote:
Henning Schmiedehausen wrote:
[...]
Hi Doug,
I noticed that you cut out the part about interfacing with
Apache-incompatible code. As this project will be surrounded on all
sides by non-Apache license able code, do you have a plan on how to
Hello,
I've also been closely following the messages exchanged about the Tashi project
proposal and I too, like Michael Stroucken, would like to respond to them.
I'm the other initial committer listed on the project proposal, Michael Ryan.
I am a software engineer at Intel and I have my own
I posted a Jira issue and a patch:
http://issues.apache.org/jira/browse/INCUBATOR-79
regarding updating a guide for creating eclipse update sites. The update
corrects an inaccuracy regarding how to specify the digestUrl.
Please review. If there are no comments in 72 hours, I'll update the
+1,
but i've noticed another potential issue in
CasEditor-linux.gtk.x86-2.2.2-incubating.zip which i'll mention in case
others object - there are some licenses in the top level LICENSE file and
some other licenses in the about_files folder that are not mentioned in the
top LICENSE file. I guess
Henning Schmiedehausen wrote:
I noticed that you cut out the part about interfacing with
Apache-incompatible code. As this project will be surrounded on all
sides by non-Apache license able code, do you have a plan on how to
amend this and how does the current demo code handle this?
I would
Yoav Shapira wrote:
After waiting a week for people to step up, I went ahead and added a
page for Thrift. I'm curious how come none of the Thrift mentors or
committers said anything?
Thanks! This has been on my to-do list. I was intending to hassle the
Thrift committers, as I felt that
Alan, has this been resolved for JSecurity?
I visit http://incubator.apache.org/projects/jsecurity.html and I get a 404
Also, JSecurity is not listed on incubator.apache.org on the right hand
side...
I don't know how this is supposed to work, so I'm hoping those more
knowledgeable than me will
Passed with +3 and no -1.
Assaf
On Mon, Jul 21, 2008 at 1:36 PM, Assaf Arkin [EMAIL PROTECTED] wrote:
Up for vote, the Buildr 1.3.2 release. The release vote passed within
the PPMC with +3 (+5 including non-binding votes) and no -1:
Doug Cutting wrote:
There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel
and CMU would like to collaborate on open source software. Intel and
CMU have a prototype, and Yahoo! is interested in helping to develop
this further. All three believe that other parties will also
Doug Cutting wrote:
I would expect that Tashi would use Xen command-line programs, not link
directly to Xen's C API's.
Why? Personally, I hope that you are wrong. I would expect Tashi to define
a vendor neutral layer to which Xen, VMware, KVM, etc., implementations
could be written.
Henning Schmiedehausen wrote:
The wording for the Yahoo! slot sounded to me like there has been a
decision at management level that CMU, Intel and Yahoo! want to do some
work on that subject [...]
I believe that we've made it clear that there are no corporate slots, and
that the language
16 matches
Mail list logo
