Congratulations!
Are you going to publish the latest artifacts to the Apache incubating maven
repo (http://people.apache.org/repo/m2-incubating-repository)?
Thanks,
Raymond
- Original Message -
From: John Kaputin (gmail) [EMAIL PROTECTED]
To: woden-dev@ws.apache.org
Cc:
Currently the ip clearance template [1] specifies:
3. Receipt of the software grant form must be acknowledged by an Officer of
the ASF by recording in grants.txt. In most normal circumstances, the officer
should be the ASF Secretary.
And in the Copyright section:
Identify name recorded for
On Feb 20, 2007, at 12:30 PM, Jean T. Anderson wrote:
oh, hee hee, Jim already made the change to bullet 3 in revision
509668.
:-)
For those not on the commit notices, Jim also added:
the officer should be the ASF Secretary, who must be provided an
original copy of the grant or CCLA in
Jim Jagielski wrote:
...
No, a FAXed copy is fine. It's just that if someone rec's the
grant, they can't just log it in the cclas.txt/grants.txt file
and keep it. I need a copy as well.
We need to further clarify that such docs can be accepted either
by:
o Hardcopy snail-mailed to
Incubator PMC,
The release of XAP currently has 6 non-binding [+1] votes, but we still
need 3 more binding [+1] votes from the PMC. We have met all the issues
brought up with the first release candidate and a wait. Please take a
look at the release and give your feedback and votes.
Thank you,
Hola,
You've got three mentors ;) Where they at?
Personally, I've taken a look at the documentation, and it looks nice.
The RAT results are reasonable. I haven't actually tested the code,
but I'll trust your PPMC on it, so +1.
Yoav
On 2/20/07, Bob Buffone [EMAIL PROTECTED] wrote:
Incubator
At various times, various people have stated various rather
incongruent descriptions of what has to be done when a podling
performs a release
http://incubator.apache.org/guides/releasemanagement.html
One thing that seems to have been forgotten is that an approved
release must be in the form
I noticed yesterday that James Snell was being very proactive
and submitted the correct BIS notification for Abdera.
http://mail-archives.apache.org/mod_mbox/incubator-abdera-dev/
200702.mbox/raw/[EMAIL PROTECTED]
However, please note that Abdera is not yet an Apache Project,
even though it
Hi Roy
On a similar subject, Apache Tuscany is going to have similar
dependencies and we are trying to find out what's the right way to file the
notification. Could you please help us on the following thread :
http://www.mail-archive.com/general%40incubator.apache.org/msg12626.html
--
Luciano
Notta problem... I'd rather stick to writing code anyway ;-). Thanks
for the correction.
- James
Roy T. Fielding wrote:
I noticed yesterday that James Snell was being very proactive
and submitted the correct BIS notification for Abdera.
Roy,
At various times, various people have stated various rather
incongruent descriptions of what has to be done when a podling
performs a release
One thing that seems to have been forgotten is that an approved
release must be in the form of SOURCE CODE and must be placed
in the associated
On 2/20/07, Noel J. Bergman [EMAIL PROTECTED] wrote:
The associated PMC would be the Incubator, and you might notice that there
is not an incubator/ directory under those locations.
As I understand it, the primary issue is that there has been a lot of
emphasis to say that Incubator releases are
On Feb 20, 2007, at 7:11 PM, William A. Rowe, Jr. wrote:
In other words, we agree there is probably an export issue to resolve,
however /dist/incubator/ does not exist for a reason, and it would be
helpful if you ran changes to the incubator past the incubator PMC
before confusing our podlings
On Feb 19, 2007, at 11:28 PM, James M Snell wrote:
All of the instructions can be found at [1]. Just step through that
and
it shouldn't take too long.
As far as I understand, each project is responsible for it's own
notifications.
- James
[1] http://www.apache.org/dev/crypto.html
Thanks.
BIS notices have to be made if a product contains encryption
functionality controlled by the EAR's 5D002 classification, or
is specifically designed to make use of a 5D002 classified item
(as would the case if the source code contains calls to OpenSSL
or JCE interfaces), or if any released
On 2/20/07, Roy T. Fielding [EMAIL PROTECTED] wrote:
BIS notices have to be made if a product contains encryption
functionality controlled by the EAR's 5D002 classification, or
is specifically designed to make use of a 5D002 classified item
(as would the case if the source code contains calls to
What we actually have in svn is a mvn pom which references jxta and
bouncycastle:
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/runtime/
services/discovery/jxta/pom.xml
The bouncycastle reference is there because jxta needs it; there is
no direct reference from our code.
My
17 matches
Mail list logo
