Re: [VOTE] Accept Apache Streams as an Incubator Project

[James M Snell]

+1


On Wed, Nov 14, 2012 at 7:24 AM, Ross Gardler wrote:

> +1
>
> (Love the idea of Apache Screams, we could then have a Wookie Scream in a
> Rave)
>
> Ross
>
> > -Original Message-
> > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
> > Sent: 14 November 2012 14:49
> > To: general
> > Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project
> >
> > Hi,
> >
> > On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B.
> >  wrote:
> > > Please vote.
> >
> >   [x] +1 Accept Streams into the incubator
> >
> > Though I do think there's some life also in the alternative name, "Apache
> > Screams", that came up in discussion during ACEU. ;-)
> >
> > BR,
> >
> > Jukka Zitting
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[ANNOUNCE] Apache Abdera 0.4.0-incubating

[James M Snell]

The Apache Abdera community is pleased to announce the 0.4.0-incubating
release.

You can download binary and source distributions from:

  http://incubator.apache.org/abdera

Introduction


The goal of the Apache Abdera project is to build a
functionally-complete, high-performance implementation of the IETF Atom
Syndication Format (RFC 4287) and Atom Publishing Protocol (RFC 5023)
specifications.

Abdera is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

Release Summary
===
 * A simplified server side framework and API for implementing services.
 * Server side filter API for intercepting requests and implementing
   concerns such as security.
 * A collection of pre-bundled Atom Publishing Protocol adapters for
   JDBC, JCR, filesystems, and CouchDB.
 * An improved JSON serialization mechanism.
 * New extensions such as OAuth support.
 * New StreamWriter interface for fast Atom document serialization
 * Improved Unicode performance for IRI implementation
 * URI Template Support
 * HTML Parser
 * Many API improvements and bug fixes!

Please feel free to send any feedback to our mailing lists:
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more
information on how to get involved with the development of Abdera, visit
our website at: http://incubator.apache.org/abdera

Thank you for your interest in Apache Abdera!

- Apache Abdera Project

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Abdera 0.4.0-incubating Take 7

[James M Snell]

sebb wrote:

[snip]
Two of the tests fail on IBM Java 6:
java version "1.6.0" [snip]


We do not claim to support Java 6 at this time. We can look at this 
issue in the next release.  I invite you to please submit a jira issue.


- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Abdera 0.4.0-incubating Take 7

[James M Snell]

Dan's added the missing md5's.

- James

Martijn Dashorst wrote:

On 4/7/08, James M Snell <[EMAIL PROTECTED]> wrote:

 Not critical. We can generate the md5 files for the zip files and make
those available with the final release.


I tend to disagree here. How can we tell the file hasn't been updated
in the mean time? Or that the version Sebb has downloaded is the same
as you have published?

IMO the .md5 files are an essential part of a release.

Martijn



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Abdera 0.4.0-incubating Take 7

[James M Snell]

sebb wrote:

[snip]
But where can I find the key?



http://svn.apache.org/repos/asf/incubator/abdera/java/tags/abdera-0.4.0-incubating/KEYS


[snip]
And where is the SVN tag please?



http://svn.apache.org/repos/asf/incubator/abdera/java/tags/abdera-0.4.0-incubating/

> [snip]
> Some of the MD5 digest files are missing.

Not critical. We can generate the md5 files for the zip files and make 
those available with the final release.


- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Release Abdera 0.4.0-incubating Take 7

[James M Snell]

Ok, we've updated the release candidate... please review

Take 7 of the vote to release Apache Abdera 0.4.0-incubating. The
following things have changed:
- All necessary files now include ASL headers
- LICENSE file now includes pointers to non-ASL licenses and Mark
Pilgrim's license
- NOTICE files in the jars are much cleaner thanks to the new
maven-remote-resource plugin.
- Information about a jar's dependencies and their licenses are now
included in META-INF/DEPENDENCIES instead of the NOTICE file.
- The NOTICE file in the distributions contains all the stuff not in
lib/*-LICENSE.txt and provides a pointer to the lib directory for the
additional stuff.
- Everything is signed

Binary distributions:

http://people.apache.org/~dandiep/abdera-take7/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.zip
http://people.apache.org/~dandiep/abdera-take7/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.tar.gz

Source distributions:

http://people.apache.org/~dandiep/abdera-take7/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.zip
http://people.apache.org/~dandiep/abdera-take7/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.tar.gz

Maven Repository: http://people.apache.org/~dandiep/abdera-take7/

- The Abdera folks


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Approve the release of Apache Abdera 0.4.0-incubating (updated)

[James M Snell]

Notice added. Do you see anything else?

- James

sebb wrote:

[snip]

 > Also, SVN includes the file
 > 
dependencies/i18n/src/main/java/org/apache/abdera/i18n/text/data/CompositionExclusions.txt
 > which is not AL licensed; IMO it should be attributed in the NOTICE file.
 >


I've just removed the file completely as we actually no longer need it
 at runtime. In the future, I plan to automate the process of downloading
 and processing that file during the build process.



However the product still depends on the file - I don't think the fact
that the file is not in SVN makes any dfference.
[snip]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Approve the release of Apache Abdera 0.4.0-incubating (updated)

[James M Snell]

sebb wrote:

The following do not seem to be test files, nor are they trivially short.
So they should have AL headers please:

core/src/main/resources/abdera.properties.example
dependencies/deps.properties



Done


The top level NOTICE file should not have the 4 line == header.


Removed


Also, SVN includes the file
dependencies/i18n/src/main/java/org/apache/abdera/i18n/text/data/CompositionExclusions.txt
which is not AL licensed; IMO it should be attributed in the NOTICE file.



I've just removed the file completely as we actually no longer need it 
at runtime. In the future, I plan to automate the process of downloading 
and processing that file during the build process.


- James


Probably something needs to go in the LICENSE file as well



On 01/04/2008, James M Snell <[EMAIL PROTECTED]> wrote:

I've added license headers to the build scripts and to the localization
 file and log4j.properties file. The rest I intend to leave as is.  Is
 that sufficient?  If so, we'll roll a new build.


 - James

 sebb wrote:
 > On 31/03/2008, James M Snell <[EMAIL PROTECTED]> wrote:
 >> In the FAQ I see this: "A file without any degree of creativity in
 >>  either its literal elements or its structure is not protected by
 >>  copyright law; therefore, such a file does not require a license header.
 >
 > Yes, but:
 >
 >>   If in doubt about the extent of the file's creativity, add the license
 >>  header to the file."
 >
 >>  Here's the breakdown that I see from Rat:
 >>
 >>  None of the build scripts contain license headers.  Given that the build
 >>  scripts are everyday, normal maven build scripts, I do believe they
 >>  qualify under the "a file without any degree of creativity" clause.
 >
 > I disagree.
 >
 > Note that all Commons poms include the AL header.
 >
 >>   ? adapters/pom.xml
 >>   ? client/pom.xml
 >>   ? core/pom.xml
 >>   ? examples/pom.xml
 >>   ? extensions/pom.xml
 >>   ? extensions/gdata/pom.xml
 >>   ? extensions/geo/pom.xml
 >>   ? extensions/html/pom.xml
 >>   ? extensions/json/pom.xml
 >>   ? extensions/main/pom.xml
 >>   ? extensions/media/pom.xml
 >>   ? extensions/oauth/pom.xml
 >>   ? extensions/opensearch/pom.xml
 >>   ? extensions/serializer/pom.xml
 >>   ? extensions/sharing/pom.xml
 >>   ? extensions/wsse/pom.xml
 >>   ? parser/pom.xml
 >>   ? security/pom.xml
 >>   ? server/pom.xml
 >>   ? spring/pom.xml
 >>   ? dependencies/deps.properties
 >>
 >>  The following file used to provide localization strings may possibly
 >>  require a license header.
 >>
 >>   ? core/src/main/resources/abderamessages.properties
 >>
 >>  The following are configuration files used at runtime, the majority of
 >>  which consist of only a few lines of text and also fall under the above
 >>  quoted clause.
 >>
 >>   ? client/src/main/java/log4j.properties
 >>   ? core/src/main/resources/abdera.properties.example
 >>   ?
 >
 > These have less content, so the creative aspect is definitely lower.
 > However, I don't think there's no creativity involved.
 >
 >>  
core/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory.example
 >>   ?
 >>  
core/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
core/src/test/resources/META-INF/services/org.apache.abdera.converter.ConverterProvider
 >>   ?
 >>  
examples/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
extensions/complete/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
 >>   ?
 >>  
extensions/complete/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
extensions/complete/resources/META-INF/services/org.apache.abdera.parser.NamedParser
 >>   ?
 >>  
extensions/html/src/main/resources/META-INF/services/org.apache.abdera.parser.NamedParser
 >>   ?
 >>  
extensions/json/src/main/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
 >>  !?
 >>  
extensions/main/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
extensions/media/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
extensions/opensearch/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
extensions/sharing/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
 >>   ?
 >>  
parser/src/main/resources/META-INF/services/org.apache.abdera.write

Re: [VOTE] Approve the release of Apache Abdera 0.4.0-incubating (updated)

[James M Snell]

I've added license headers to the build scripts and to the localization 
file and log4j.properties file. The rest I intend to leave as is.  Is 
that sufficient?  If so, we'll roll a new build.


- James

sebb wrote:

On 31/03/2008, James M Snell <[EMAIL PROTECTED]> wrote:

In the FAQ I see this: "A file without any degree of creativity in
 either its literal elements or its structure is not protected by
 copyright law; therefore, such a file does not require a license header.


Yes, but:


  If in doubt about the extent of the file's creativity, add the license
 header to the file."



 Here's the breakdown that I see from Rat:

 None of the build scripts contain license headers.  Given that the build
 scripts are everyday, normal maven build scripts, I do believe they
 qualify under the "a file without any degree of creativity" clause.


I disagree.

Note that all Commons poms include the AL header.


  ? adapters/pom.xml
  ? client/pom.xml
  ? core/pom.xml
  ? examples/pom.xml
  ? extensions/pom.xml
  ? extensions/gdata/pom.xml
  ? extensions/geo/pom.xml
  ? extensions/html/pom.xml
  ? extensions/json/pom.xml
  ? extensions/main/pom.xml
  ? extensions/media/pom.xml
  ? extensions/oauth/pom.xml
  ? extensions/opensearch/pom.xml
  ? extensions/serializer/pom.xml
  ? extensions/sharing/pom.xml
  ? extensions/wsse/pom.xml
  ? parser/pom.xml
  ? security/pom.xml
  ? server/pom.xml
  ? spring/pom.xml
  ? dependencies/deps.properties

 The following file used to provide localization strings may possibly
 require a license header.

  ? core/src/main/resources/abderamessages.properties

 The following are configuration files used at runtime, the majority of
 which consist of only a few lines of text and also fall under the above
 quoted clause.

  ? client/src/main/java/log4j.properties
  ? core/src/main/resources/abdera.properties.example
  ?


These have less content, so the creative aspect is definitely lower.
However, I don't think there's no creativity involved.


 
core/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory.example
  ?
 
core/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
core/src/test/resources/META-INF/services/org.apache.abdera.converter.ConverterProvider
  ?
 
examples/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
extensions/complete/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
  ?
 
extensions/complete/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
extensions/complete/resources/META-INF/services/org.apache.abdera.parser.NamedParser
  ?
 
extensions/html/src/main/resources/META-INF/services/org.apache.abdera.parser.NamedParser
  ?
 
extensions/json/src/main/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
 !?
 
extensions/main/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
extensions/media/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
extensions/opensearch/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
extensions/sharing/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
  ?
 
parser/src/main/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
  ?
 
contrib/rss/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory



Agreed.


 The following simple files are used for example purposes and do not
 contain any creative content whatsoever.

  ? examples/src/main/resources/xmlcontent.xml
  ? examples/src/main/resources/log4j.properties
  ? examples/src/main/resources/simple.xml
  ? examples/src/main/resources/test.xslt
  ? examples/src/main/resources/content.xslt
  ? examples/src/main/resources/org/apache/abdera/examples/appserver/web.xml


Not much creativity, and small files, so the AL header is not essential.


 The following were also (inappropriately) flagged by RAT

  ? extensions/complete/resources/META-INF/LICENSE.htmlparser.txt
  ? extensions/complete/resources/META-INF/NOTICE.htmlparser.txt
  ? extensions/complete/resources/META-INF/NOTICE.serializer.txt
  ? extensions/json/src/main/resources/META-INF/LICENSE.htmlparser.txt
  ? extensions/json/src/main/resources/META-INF/NOTICE.htmlparser.txt
  ? extensions/json/src/main/resources/META-INF/NOTICE.serializer.txt
  ? dependencies/legal/servlet-api-LICENSE.txt
  ? dependencies/legal/htmlparser-LICENSE.txt


 The following resources are test resources that in addition to not
 containing any degree of creative content, they arguably should not
 contain license headers because the presence of the license header could
 potentially impact the results of the tests.



Probably.
Though if the AL header affects the parsing, then there may well be a
problem with the parsing...


  ? adapters/hibernate/src/test/resources/abdera/a

Re: [VOTE] Approve the release of Apache Abdera 0.4.0-incubating (updated)

[James M Snell]

er/src/test/resources/feed.xml
 ? parser/src/test/resources/simple.xml
 ? 
parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entry_content_base64_2.xml
 ? 
parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entry_content_base64.xml
 ? 
parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entry_author_email.xml
 ? 
parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entry_author_name.xml
 ? 
parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/atom10_namespace.xml

 ? parser/src/test/resources/complete.xml
 ? parser/src/test/resources/simpleService.xml
 ? parser/src/test/resources/simpleEntry.xml
 ? parser/src/test/resources/test.xslt
 ? parser/src/test/resources/entry.xml
 ? parser/src/test/resources/content.xslt
 ? spring/src/test/resources/org/apache/abdera/spring/beans.xml
 ? contrib/rss/src/test/resources/rss1.rdf
 ? 
adapters/hibernate/src/test/resources/abdera/adapter/hibernate.properties

 ? security/src/test/resources/log4j.properties
 ? server/src/test/resources/abdera/adapter/sample.properties

This one documentation file, which contains only a single one sentence 
statement, does not contain a license header.


 ? docs/knownissues.txt

Which of these files do you think we absolutely have to add license 
headers to?


- James

sebb wrote:

On 31/03/2008, Dan Diephouse <[EMAIL PROTECTED]> wrote:

sebb wrote:
 > On 31/03/2008, James M Snell <[EMAIL PROTECTED]> wrote:
 >
 >>
 >


-1: There are MD5 and SHA1 digests in the directory, but the archives

 > have no signatures.
 >
 >

OK, I will fix this.


 Maven Repository: http://people.apache.org/~dandiep/abdera-take6/

 >>
 >>
 >
 > -0: The abdera-bundle-0.4.0-incubating-sources.jar does not appear to
 > have any content - only the META-INF directory is present. Is that
 > correct?
 >

This is just a by-product of Maven. We can delete it.


-1: The NOTICE files in that jar (and others) contains far too much.

 > The NOTICE file is for required attribtions ONLY (e.g. as per an About box)
 > There's really no need to repeat ASF for each project used by Abdera.
 >

Having too much information in the NOTICE files is not a crime. The
 Maven remote-resources plugin aggregates all this stuff for us so we
 never miss any notice that we need to put in.


Unfortunately the plugin generates incorrect information.
It *is* a problem having all the redundant information.

See for example:

http://www.apache.org/legal/src-headers.html
also
http://wiki.apache.org/legal/3party/notice
http://wiki.apache.org/legal/3party/notice/discuss


-1: The LICENSE files need to either contain copies of the 3rd party

 > licenses, or they need to have a reference to the 3rd party licences.
 > Equally, there is no need for the lib directory to contain copies of
 > the AL for every ASF product.
 >

Why does the LICENSE file need to have a copy of all the other licenses?
 These are contained in the lib/ directory like many other ASF projects.



See the last paragraph of:

http://www.apache.org/dev/apply-license.html#new


 Re: the ASL license in lib/ - once again having too much information is
 not a crime. This is a service to uesrs so they know where the libraries
 came from.


I agree the source is useful, but the place for this is the LICENSE file.


-1: RAT report says:

 >
 > 99 Unknown Licenses
 >
 > Some of these are trivial, but most require an AL header.
 >

Not true - there is not consensus that properties/xml files need to have
 headers. All the Java source code files have headers. If there are
 specific files that you feel should have a license that don't please
 list them and explain why. I'm not saying that we didn't miss something,
 but I am saying that the ones that I know about don't necessarily
 require a header.


Yes, they do, see:

http://www.apache.org/legal/src-headers.html#faq-exceptions


What is the SVN tag that corresponds with the archives?

 >
 >

the branch will be tagged once its released.

 Dan


 --
 Dan Diephouse
 MuleSource
 http://mulesource.com | http://netzooid.com



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Approve the release of Apache Abdera 0.4.0-incubating (updated)

[James M Snell]

The Abdera project has resolved the issues raised previously and have 
voted to release a new build of the 0.4.0-incubating release.


Binary distributions:

http://people.apache.org/~dandiep/abdera-take6/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.zip
http://people.apache.org/~dandiep/abdera-take6/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.tar.gz

Source distributions:

http://people.apache.org/~dandiep/abdera-take6/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.zip
http://people.apache.org/~dandiep/abdera-take6/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.tar.gz

Maven Repository: http://people.apache.org/~dandiep/abdera-take6/

Please take a look and cast your vote!

- Abdera Team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Approve the release of Apache Abdera 0.4.0-incubating

[James M Snell]

Good catch; sorry for missing that.  Will get those fixed shortly.

- James

Luciano Resende wrote:

Have you guys run RAT over the release ? I tried it over the source
distribution and various source files are missing ASF license header.

[1] http://people.apache.org/~lresende/abdera/rat.log

On Sun, Mar 23, 2008 at 3:37 PM, Dan Diephouse
<[EMAIL PROTECTED]> wrote:

The Apache Abdera project has voted to release the 0.4.0-incubating
 release [1]. The vote passed with 7 +1s. Two of these were IPMC votes,
 Garrett Rooney and Davanum Srinivas.

 Binary distributions:

 
http://people.apache.org/~dandiep/abdera-take4/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.zip
 
http://people.apache.org/~dandiep/abdera-take4/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating.tar.gz

 Source distributions:

 
http://people.apache.org/~dandiep/abdera-take4/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.zip
 
http://people.apache.org/~dandiep/abdera-take4/org/apache/abdera/apache-abdera/0.4.0-incubating/apache-abdera-0.4.0-incubating-src.tar.gz

 Maven Repository: http://people.apache.org/~dandiep/abdera-take4/

 Please take a look and cast your vote!

 - Abdera Team

 1.
 
http://mail-archives.apache.org/mod_mbox/incubator-abdera-dev/200803.mbox/[EMAIL
 PROTECTED]

 --
 Dan Diephouse
 MuleSource
 http://mulesource.com | http://netzooid.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: November Incubator Reports ARE LATE!

[James M Snell]

Posted.

Noel J. Bergman wrote:
> James M Snell wrote:
> 
>> I am preparing the Abdera report now; once I hear back from the other
>> committers on whether there is anything else to add I will post it.
> 
> The Incubator PMC has a deadline to meet.  That deadline is about an hour
> from now.  I am preparing the report now and will submit it.  With or
> without Abdera, which is not yet posted.
> 
>   --- Noel
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: November Incubator Reports ARE LATE!

[James M Snell]

I am preparing the Abdera report now; once I hear back from the other
committers on whether there is anything else to add I will post it.  My
apologies for it being late.

- James

Noel J. Bergman wrote:
> ... from:
> 
>   Abdera
>   Lokahi
>   NMaven
>   ServiceMix
>   Woden
>   WSRP4J
>   XAP
>   Yoko
> 
> They must be submitted IMMEDIATELY.
> 
>   --- Noel
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Announce] Apache Abdera 0.3.0

[James M Snell]

The Apache Abdera community is pleased to announce the 0.3.0-incubating
release.

You can download binary and source distributions from:

http://people.apache.org/dist/incubator/abdera/0.3.0-incubating

Builds are available for Java 1.5 and Java 1.4.2.

For further information, visit our web site at:
http://incubator.apache.org/abdera

Introduction


The goal of the Apache Abdera project is to build a
functionally-complete, high-performance implementation of the IETF Atom
Syndication Format (RFC 4287) and Atom Publishing Protocol (in-progress)
specifications.

Abdera is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

Release Summary
===

 * Support for the Atompub final draft
 * Refactored and simplified Server framework
 * Refactored and simplified AbderaClient
 * ExtensionFactory can now provide the mime type for extension elements
 * Improved extensibility
 * Updated dependencies
 * XPath support improvements
 * Geotagging extensions
 * Simple Sharing extensions
 * WSSE Authentication
 * Bidi extensions (experimental)
 * Atompub features extensions (experimental)
 * Feed paging extensions
 * Feed license extensions
 * XML Encryption with Diffie-Hellman key exchange
 * Spring integration support
 * Extensions now packaged in separate jars for modular distribution
 * Improved error handling
 * More examples
 * Less bugs
 * Lots of other improvements

Please feel free to send any feedback to our mailing lists:
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more
information on how to get involved with the development of Abdera, visit
our website at: http://incubator.apache.org/abdera

Thank you for your interest in Apache Abdera!

- Apache Abdera Project



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release Abdera 0.3.0-incubating

[James M Snell]

Excellent. Thanks for taking a look.  I will give this one more day for
review and will cut the release tomorrow.

- James

Kevan Miller wrote:
> 
> On Oct 1, 2007, at 11:20 AM, James M Snell wrote:
> 
>> Ok, we have three +1's (Yoav, Garrett and Ant) and I have addressed the
>> most significant issues raised by Kevan.  I've given it about a weeks
>> time to see if there are any additional issues.  Unless there are any
>> objections (or unless I'm getting some part of the process wrong ;-) ..)
>> I'm going to assume that we're good to go for release.
> 
> Hi James,
> Sorry for my slow feedback... Your changes look good. Here's my +1.
> 
> --kevan
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release Abdera 0.3.0-incubating

[James M Snell]

Ok, we have three +1's (Yoav, Garrett and Ant) and I have addressed the
most significant issues raised by Kevan.  I've given it about a weeks
time to see if there are any additional issues.  Unless there are any
objections (or unless I'm getting some part of the process wrong ;-) ..)
I'm going to assume that we're good to go for release.

- James

Kevan Miller wrote:
> 
> On Sep 27, 2007, at 12:45 PM, James M Snell wrote:
> 
>> Ok, we have made a couple of bug fixes and, more importantly, we have
>> softened the bouncy castle dependency and will no longer ship that jar.
>>  This release has been well tested and reviewed and has received the
>> requisite number of +1's from the committers.
>>
>> The release candidate can be found here:
>>
>>   http://people.apache.org/~jmsnell/abdera/0.3.0
> 
> Hi James,
> I've taken a look at your binary and src downloads. I'm seeing the
> following problems which, IMHO, most of these issues should be addressed.
> 
> 1. No incubator DISCLAIMER in your generated Jar files. Your README
> contains a DISCLAIMER notice. However, I think each of your jar files
> needs to contain a disclaimer, also.
> 2. No ASF Copyright in your NOTICE files. As described here --
> http://www.apache.org/legal/src-headers.html#notice. There should be a
> copyright notice for the work that's occurring within the Abdera
> project, itself.
> 3. No LICENSE or NOTICE (or DISCLAIMER) files in
> lib/abdera-i18n-0.3.0-incubating.jar of your binary distribution.
> 4. Missing Apache source license headers. RAT is noting the following
> files from your source are missing license headers. IMO, a number of
> these files could and should have an Apache source license header.
> 
> !? ./client/src/main/java/log4j.properties
> !?
> ./contrib/rss/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !? ./contrib/rss/src/test/resources/rss1.rdf
> !?
> ./core/src/main/java/org/apache/abdera/util/XmlRestrictedCharReader.java
> !? ./core/src/main/resources/abdera.properties.example
> !? ./core/src/main/resources/abderamessages.properties
> !?
> ./core/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory.example
> 
> !? ./dependencies/deps.properties
> !? ./dependencies/i18n/build.properties
> !?
> ./dependencies/i18n/src/main/resources/org/apache/abdera/i18n/unicode/data/ucd.res
> 
> !? ./dependencies/legal/axiom-NOTICE.txt
> !? ./dependencies/legal/retroweaver-LICENSE.txt
> !? ./dependencies/legal/wstx-asl-NOTICE.txt
> !? ./dependencies/legal/xmlsec-NOTICE.txt
> !? ./docs/knownissues.txt
> !? ./examples/src/main/resources/content.xslt
> !? ./examples/src/main/resources/log4j.properties
> !? ./examples/src/main/resources/simple.xml
> !? ./examples/src/main/resources/test.xslt
> !? ./examples/src/main/resources/xmlcontent.xml
> !?
> ./examples/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !?
> ./examples/src/main/resources/org/apache/abdera/examples/appserver/web.xml
> !?
> ./extensions/json/src/main/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
> 
> !?
> ./extensions/main/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !?
> ./extensions/media/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !?
> ./extensions/opensearch/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !? ./extensions/opensearch/src/test/resources/opensearch.xml
> !?
> ./extensions/sharing/src/main/resources/META-INF/services/org.apache.abdera.factory.ExtensionFactory
> 
> !?
> ./parser/src/main/resources/META-INF/services/org.apache.abdera.writer.NamedWriter
> 
> !? ./parser/src/test/resources/complete.xml
> !? ./parser/src/test/resources/content.xslt
> !? ./parser/src/test/resources/entry.xml
> !? ./parser/src/test/resources/feed.xml
> !? ./parser/src/test/resources/simple.xml
> !? ./parser/src/test/resources/simpleEntry.xml
> !? ./parser/src/test/resources/simpleFeed.xml
> !? ./parser/src/test/resources/simpleService.xml
> !? ./parser/src/test/resources/test.xslt
> !? ./parser/src/test/resources/xmlcontent.xml
> !?
> ./parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/atom10_namespace.xml
> 
> !?
> ./parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entry_author_email.xml
> 
> !?
> ./parser/src/test/resources/www.feedparser.org/tests/wellformed/atom10/entr

Re: [VOTE] Release Abdera 0.3.0-incubating

[James M Snell]

Done. New zips, same place.  The incubation disclaimer was just added to
the end of the notice file.

  http://people.apache.org/~jmsnell/abdera/0.3.0

- James

Garrett Rooney wrote:
> [snip]
> The other comments in your mail are valid, and I'm sure James will fix
> them along with the few files that do have license header problems and
> reroll the zips.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release Abdera 0.3.0-incubating

[James M Snell]

I will go ahead and add the disclaimer to the jars as there are folks
who use MAVEN to build and it's likely the jars will end up included in
some repos somewhere separately from the main dist package.  I am also
adding a copyright 2006-2007 statement to the NOTICE and the copyright
headers to the java files.  The other files I will leave as is -- most
of them are either simple properties files or test resources that are
downloaded from other projects or resources during the build and are
used for running the junit tests.

- James

ant elder wrote:
> I'm not so sure any of these issues are serious enough to block the release
> so I'm going still to give it a +1.
> 
> Most of the missing license headers are not in significant files and the top
> level LICENSE is there in the distributions which is the main thing, and I
> don't think LICENSE/NOTICE/DISCLAIMER files are required within jar files
> included with in a distribution, they're only necessary when the jars are
> distributed separately
> 
>...ant
> 
> On 9/27/07, Garrett Rooney <[EMAIL PROTECTED]> wrote:
>> On 9/27/07, Kevan Miller <[EMAIL PROTECTED]> wrote:
>>
>>> 2. No ASF Copyright in your NOTICE files. As described here -- http://
>>> www.apache.org/legal/src-headers.html#notice. There should be a
>>> copyright notice for the work that's occurring within the Abdera
>>> project, itself.
>> Umm, yes it is.  It's on line 6 and 7 of the file:
>>
>> This product includes software developed by
>> The Apache Software Foundation (http://www.apache.org/).
>>
>>> 4. Missing Apache source license headers. RAT is noting the following
>>> files from your source are missing license headers. IMO, a number of
>>> these files could and should have an Apache source license header.
>>>
>>> !? ./client/src/main/java/log4j.properties
>>> !? ./contrib/rss/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./contrib/rss/src/test/resources/rss1.rdf
>>> !? ./core/src/main/java/org/apache/abdera/util/
>>> XmlRestrictedCharReader.java
>>> !? ./core/src/main/resources/abdera.properties.example
>>> !? ./core/src/main/resources/abderamessages.properties
>>> !? ./core/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory.example
>>> !? ./dependencies/deps.properties
>>> !? ./dependencies/i18n/build.properties
>>> !? ./dependencies/i18n/src/main/resources/org/apache/abdera/i18n/
>>> unicode/data/ucd.res
>>> !? ./dependencies/legal/axiom-NOTICE.txt
>>> !? ./dependencies/legal/retroweaver-LICENSE.txt
>>> !? ./dependencies/legal/wstx-asl-NOTICE.txt
>>> !? ./dependencies/legal/xmlsec-NOTICE.txt
>>> !? ./docs/knownissues.txt
>>> !? ./examples/src/main/resources/content.xslt
>>> !? ./examples/src/main/resources/log4j.properties
>>> !? ./examples/src/main/resources/simple.xml
>>> !? ./examples/src/main/resources/test.xslt
>>> !? ./examples/src/main/resources/xmlcontent.xml
>>> !? ./examples/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./examples/src/main/resources/org/apache/abdera/examples/
>>> appserver/web.xml
>>> !? ./extensions/json/src/main/resources/META-INF/services/
>>> org.apache.abdera.writer.NamedWriter
>>> !? ./extensions/main/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./extensions/media/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./extensions/opensearch/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./extensions/opensearch/src/test/resources/opensearch.xml
>>> !? ./extensions/sharing/src/main/resources/META-INF/services/
>>> org.apache.abdera.factory.ExtensionFactory
>>> !? ./parser/src/main/resources/META-INF/services/
>>> org.apache.abdera.writer.NamedWriter
>>> !? ./parser/src/test/resources/complete.xml
>>> !? ./parser/src/test/resources/content.xslt
>>> !? ./parser/src/test/resources/entry.xml
>>> !? ./parser/src/test/resources/feed.xml
>>> !? ./parser/src/test/resources/simple.xml
>>> !? ./parser/src/test/resources/simpleEntry.xml
>>> !? ./parser/src/test/resources/simpleFeed.xml
>>> !? ./parser/src/test/resources/simpleService.xml
>>> !? ./parser/src/test/resources/test.xslt
>>> !? ./parser/src/test/resources/xmlcontent.xml
>>> !? ./parser/src/test/resources/www.feedparser.org/tests/
>>> wellformed/atom10/atom10_namespace.xml
>>> !? ./parser/src/test/resources/www.feedparser.org/tests/
>>> wellformed/atom10/entry_author_email.xml
>>> !? ./parser/src/test/resources/www.feedparser.org/tests/
>>> wellformed/atom10/entry_author_name.xml
>>> !? ./parser/src/test/resources/www.feedparser.org/tests/
>>> wellformed/atom10/entry_content_base64.xml
>>> !? ./parser/src/test/resources/www.feedparser.org/tests/
>>> wellformed/atom10/entry_conte

[VOTE] Release Abdera 0.3.0-incubating

[James M Snell]

Ok, we have made a couple of bug fixes and, more importantly, we have
softened the bouncy castle dependency and will no longer ship that jar.
 This release has been well tested and reviewed and has received the
requisite number of +1's from the committers.

The release candidate can be found here:

  http://people.apache.org/~jmsnell/abdera/0.3.0

High level change summary for this release:

  * Support for the Atompub final draft
  * Refactored and simplified Server framework
  * Refactored and simplified AbderaClient
  * Spring integration support
  * ExtensionFactory can now provide the mime type for extension elements
  * Improved extensibility
  * Updated dependencies
  * XPath support improvements
  * Geotagging extensions
  * Simple Sharing extensions
  * WSSE Authentication
  * Bidi extensions (experimental)
  * Atompub features extensions (experimental)
  * Feed paging extensions
  * Feed license extensions
  * XML Encryption with Diffie-Hellman key exchange
  * Extensions now packaged in separate jars for modular distribution
  * Improved error handling
  * More examples
  * Less bugs
  * Lots of other improvements

- James

James M Snell wrote:
> The Apache Abdera project is ready to let loose it's 0.3.0-incubating
> release.  The 0.3.0 branch was created a couple of weeks ago and has
> since undergone a solid review by both committers and users.  A number
> of issues were identified and fixed. The current candidate zips have
> received the requisite number of +1's to release.
> 
> The 0.3.0-incubating release candidate zips are available for download
> at http://people.apache.org/~jmsnell/abdera/0.3.0
> 
> The one issue that might hold us up is the fact that we are shipping the
> bouncy castle jar.  As I've mentioned on a couple of other notes, it
> would not be difficult for us to soften the dependency on that jar and
> not ship it.
> 
> - James
> 
> 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Abdera 0.3.0

[James M Snell]

Ok, I've got no problem with this.

cc'ing the abdera-dev list: I'll make the change a bit later today and
will re-roll the zips.

- James

Kevan Miller wrote:
> 
> On Sep 17, 2007, at 11:45 AM, James M Snell wrote:
> 
>> The Apache Abdera project is ready to let loose it's 0.3.0-incubating
>> release.  The 0.3.0 branch was created a couple of weeks ago and has
>> since undergone a solid review by both committers and users.  A number
>> of issues were identified and fixed. The current candidate zips have
>> received the requisite number of +1's to release.
>>
>> The 0.3.0-incubating release candidate zips are available for download
>> at http://people.apache.org/~jmsnell/abdera/0.3.0
>>
>> The one issue that might hold us up is the fact that we are shipping the
>> bouncy castle jar.  As I've mentioned on a couple of other notes, it
>> would not be difficult for us to soften the dependency on that jar and
>> not ship it.
> 
> Hi James,
> IMO, I think we've gotten a pretty clear message -- you can't include
> the BouncyCastle jar, unless you obtain an Apache-compatible license for
> the IDEA implementation. I doubt that will happen. So, I recommend you
> switch to a soft dependency...
> 
> --kevan
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Abdera 0.3.0

[James M Snell]

The Apache Abdera project is ready to let loose it's 0.3.0-incubating
release.  The 0.3.0 branch was created a couple of weeks ago and has
since undergone a solid review by both committers and users.  A number
of issues were identified and fixed. The current candidate zips have
received the requisite number of +1's to release.

The 0.3.0-incubating release candidate zips are available for download
at http://people.apache.org/~jmsnell/abdera/0.3.0

The one issue that might hold us up is the fact that we are shipping the
bouncy castle jar.  As I've mentioned on a couple of other notes, it
would not be difficult for us to soften the dependency on that jar and
not ship it.

- James


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Export Notification - Using BouncyCastle in Tuscany Rel 1.0

[James M Snell]

I'll say "Generally Soft".  There are a couple of classes that require
bouncy to compile, but their use is entirely optional.  Two of the
classes are example code that is only shipped in source form -- we test
compile the examples before shipping them.  The other classes are
optional utility classes that are shipped as part of the optional
security module.  Other crypto providers can be used as an alternative
and it would literally only take a couple of minutes to remove the
compile-time dependency.

- James

William A. Rowe, Jr. wrote:
> James M Snell wrote:
>> Well, as far as Abdera is concerned, there'd be absolutely no problem
>> with not shipping the jar.  We can easily document how to go off and get
>> the jar and the functions we're using it for can be provided by other
>> crypto providers.  If the board does not want us shipping it, just let
>> us know and I'll pull it out.
> 
> Out of curiosity, is it a hard or soft dependency?
> 
> And I'm still curious to know if bouncycastle has an unencumbered alternate
> download without IDEA.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Export Notification - Using BouncyCastle in Tuscany Rel 1.0

[James M Snell]

Well, as far as Abdera is concerned, there'd be absolutely no problem
with not shipping the jar.  We can easily document how to go off and get
the jar and the functions we're using it for can be provided by other
crypto providers.  If the board does not want us shipping it, just let
us know and I'll pull it out.

- James

William A. Rowe, Jr. wrote:
> [snip]
> Which is to say we cannot ship it, because we can't inflict that on our
> users, never mind the ASF's exposure.
> 
> Bill
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Export Notification - Using BouncyCastle in Tuscany Rel 1.0

[James M Snell]

FWIW, just as a general FYI, Abdera also ships the bouncycastle jar but
use of the jar is limited to the optional security and example modules
and it's use has been documented in several locations.

- James

Kevan Miller wrote:
> 
> On Sep 15, 2007, at 5:59 AM, ant elder wrote:
> 
>> On 9/15/07, Kevan Miller <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>> On Sep 14, 2007, at 3:26 PM, Venkata Krishnan wrote:
>>>
 Hi,

 We are using Apache Rampart 1.3 to enable ws security into the ws-
 binding-axis2 module for Apache Tuscany v1.0 which we hope to
 release in a week.  Using Rampart seems to bring in the
 Bouncycastle dependency for encryption functions.  I have followed
 the instructions on http://www.apache.org/dev/crypto.html#sources
 and I have attached the patch in this mail to include Tuscany to
 the matrix on http://www.apache.org/licenses/exports/.  I have also
 run the xsl and the generated mail sample is also attached in this
 mail.

 Could somebody please help with reviewing and applying the patch.
 Also, is there anything else to do with this other than the mention
 on the Distro README which we will do.
>>>
>>> There was a discussion earlier this year about Tuscany, BouncyCastle,
>>> and a patented IDEA algorithm implemented by BouncyCastle -- http://
>>> mail-archives.apache.org/mod_mbox/incubator-general/200702.mbox/%
>>> [EMAIL PROTECTED]
>>>
>>> Here's some background information -- http://mail-archives.apache.org/
>>> mod_mbox/www-legal-discuss/200508.mbox/%3C1AB1C8BD-
>>> [EMAIL PROTECTED]
>>>
>>> Did the Tuscany project reach a decision about the patented IDEA
>>> algorithm in BouncyCastle?
>>
>>
>> That previous discussion was about including a JXTA dependency, for
>> this one
>> I think we're just following what we've seen other Apache projects that
>> support ws-security are doing, so I guess we were assuming was ok. Are
>> you
>> saying its not ok to distribute the BouncyCastle jar (and if so then
>> is the
>> Geronimo jar a drop in replacement)?
> 
> Hi Ant,
> I wasn't aware of other projects using BouncyCastle. I would hope that
> they've considered the patent issues regarding BouncyCastle's encryption
> library.
> 
> I'm not saying that you cannot ship the BouncyCastle jar. I am saying
> that the Tuscany project should make a decision about what to do with
> the BouncyCastle jar. If you ask my opinion, I would recommend you not
> distribute the BouncyCastle jar, but that's only my opinion.
> 
> I'm not aware of an explicit Apache policy that prohibits shipping the
> jar file (assuming that your license and notice files properly document
> the jar). I think the patent issues associated with it should at least
> cause a concern for a project. Ultimately, I think it's a project
> decision. At a minimum, these issues need to be properly documented to
> your users, so they can make an informed decision. The Geronimo project
> decided not to redistribute the BouncyCastle jar. Instead, we copied
> unencumbered code into the Geronimo project (we only needed an
> ASN1.codec implementation).
> 
> Here's background information for you:
> 
> BouncyCastle implements the IDEA algorithm (e.g. in
> bcprov-jdk14-136.jar). The IDEA algorithm is patented and the patent is
> held by MediaCrypt (http://www.mediacrypt.com). MediaCrypt provides a
> variety of commercial/non-commercial licenses for use of the IDEA
> algorithm (e.g.
> http://www.mediacrypt.com/_contents/10_idea/102040_li_nc.asp). IMO,
> BouncyCastle does a horrible job of communicating this information to
> consumers of the BouncyCastle jar. BouncyCastle is aware that they are
> shipping encumbered code --
> http://www.bouncycastle.org/docs/docs1.4/org/bouncycastle/crypto/engines/IDEAEngine.html
> references the patent. I've seen claims that MediaCrypt will only pursue
> royalties from actual "users" of the algorithm --
> http://www.bouncycastle.org/devmailarchive/msg05065.html.
> 
> --kevan
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: BouncyCastle IDEA patent

[James M Snell]

Good to know.

- James

Bill Stoddard wrote:
> David Jencks wrote:
>>
>> On Feb 21, 2007, at 12:38 PM, Jeremy Boynes wrote:
>>
>>> On Feb 21, 2007, at 12:05 PM, Matt Hogstrom wrote:
>>>
 Regarding Bouncy Castle, IIRC they used to include the IDEA
 algorithm in their distribution and provided a one-off for Geronimo
 to use to bypass the patent issue.  Not sure if that is an issue or
 not for Tuscany but just a heads up.
>>
>> IIUC && RC the resolution to this is that we copied the
>> non-patent-related bouncycastle code into the geronimo-util module
>> because bouncycastle declined to produce an unencumbered release.  I'd
>> suggest that if you don't need the patented code you use the
>> geronimo-util jar instead.
>>
> Yep, that's my recollection as well.
> 
>> thanks
>> david jencks 
> 
> Bill
> 
> Bill
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: podling BIS notifications

[James M Snell]

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.
> 
>   PROTECTED]>
> 
> 
> However, please note that Abdera is not yet an Apache Project,
> even though it is a released product, and that the responsible
> party is the Incubator PMC.  I have corrected the information on
> the exports page accordingly, which will show up on the live site
> after 5:11pm PST. There is no need to correct the notice.
> 
> In the future, it is generally better for such notices to be
> submitted by an ASF officer and from an apache.org address.
> If the NSA chooses to knock on your door, we want you to be able
> to put the right hat on while talking to them.
> 
> Roy
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: BouncyCastle export for Tuscany, was: [Vote] Abdera v0.2.2

[James M Snell]

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

Jeremy Boynes wrote:
> On Feb 17, 2007, at 5:27 PM, James M Snell wrote:
> 
>> I've gone ahead and filed the export notification and updated the ASF
>> exports page [1].  I also added an appropriate notification to the
>> distributions README.
>>
>> [1] http://www.apache.org/licenses/exports/
> 
> In Tuscany our next release will have a dependency on JXTA which has one
> on BouncyCastle so I believe we will need to do this as well. I couldn't
> see anything on that page about how to file the notification - what did
> you need to do and who is authorized to do this on behalf of the ASF?
> 
> Thanks
> -- 
> Jeremy
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Announce] Abdera 0.2.2 (Incubating)

[James M Snell]

The Apache Abdera community is pleased to announce the 0.2.2-incubating
release.

You can download binary and source distributions from:

http://people.apache.org/dist/incubator/abdera/0.2.2-incubating

Builds are available for Java 1.5 and Java 1.4.2.

For further information, visit our web site at:
http://incubator.apache.org/abdera

Introduction


The goal of the Apache Abdera project is to build a
functionally-complete, high-performance implementation of the IETF Atom
Syndication Format (RFC 4287) and Atom Publishing Protocol (in-progress)
specifications.

Abdera is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

Release Summary
===

 * Fix the XHTML/XML entry content bug
 * Fix StAX API conformance bugs
 * Update to Apache Axiom 1.2.1
 * Various API Cleanups

Please feel free to send any feedback to our mailing lists:
abdera-dev@incubator.apache.org
abdera-user@incubator.apache.org

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more
information on how to get involved with the development of Abdera, visit
our website at: http://incubator.apache.org/abdera

Thank you for your interest in Apache Abdera!

- Apache Abdera Project

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Abdera v0.2.2

[James M Snell]

I've gone ahead and filed the export notification and updated the ASF
exports page [1].  I also added an appropriate notification to the
distributions README.

[1] http://www.apache.org/licenses/exports/

Garrett Rooney wrote:
> On 2/17/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>> Your quarterly report mentions possibly legal issues related to crypto.
>> What are the issues?
> 
> We need to file a export notification for use of crypto code (not our
> code, third party, bouncy castle, I believe) in one of the abdera
> modules.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: REMINDER: BOARD REPORTS

[James M Snell]

We're working on ours. Hoping to get it in by the end of the day. :-)

- James

Henri Yandell wrote:
> And because naming and shaming works:
> 
> Abdera
> [snip]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Abdera v0.2.2

[James M Snell]

I've added a short change list to the README included in the
distribution. Nothing detailed but enough to hit the high points.

- James

Luciano Resende wrote:
> This kind of information would be good to be documented, maybe in a form of
> a RELEASE_NOTES and included on the distribution. I didn't see any
> reference
> for what's changed on the zip distribution for JDK 1.5.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Abdera v0.2.2

[James M Snell]

Ok, not a problem. I'll add that in.

- James

Luciano Resende wrote:
> This kind of information would be good to be documented, maybe in a form of
> a RELEASE_NOTES and included on the distribution. I didn't see any
> reference
> for what's changed on the zip distribution for JDK 1.5.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Abdera v0.2.2

[James M Snell]

The main issues resolved include a critical bug in handling XML and
XHTML content in Atom entries and resolving some StAX API conformance
issues by upgrading to Axiom 1.2.1.  We've also eliminated our
dependence on the Stax Reference Implementation. Beyond that, the
remaining changes were relative minor API updates (e.g., hiding
constructors that are not intended for general use, etc).

- James

Thomas Dudziak wrote:
> On 2/8/07, James M Snell <[EMAIL PROTECTED]> wrote:
> 
>> The Abdera team is ready to release version v0.2.2.  This is a bug fix
>> release that addresses a number of critical issues.  There are no new
>> features.  We would appreciate if folks could take a look and weigh in.
> 
> Do you have a list of changes somewhere ? I couldn't find any issues
> assigned to version 0.2.2 in Abdera's JIRA
> (http://issues.apache.org/jira/browse/ABDERA).
> 
> Tom
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Vote] Abdera v0.2.2

[James M Snell]

The Abdera team is ready to release version v0.2.2.  This is a bug fix
release that addresses a number of critical issues.  There are no new
features.  We would appreciate if folks could take a look and weigh in.

// JDK 1.5
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.zip
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.zip.md5

// JDK 1.4.2
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.jdk142.zip
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.jdk142.zip.md5

// Source
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.src.zip
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.src.zip.md5

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Abdera 0.2.0-incubating Release

[James M Snell]

My apologies and thanks for the reminded about the 72-hour thing; I'd
completely forgotten about that point.

- James

Noel J. Bergman wrote:
> James,
> 
> You posted your vote at:
> 
>> Monday, December 04, 2006 17:12
> 
> You closed the vote after receiving the minimum possible number of votes by 
> announcing and releasing at:
> 
>> Tuesday, December 05, 2006 18:47
> 
> That's just over 24 hours.  It is considered an ASF practice to wait at least 
> 72 hours to allow more people to review and comment.
> 
>   --- Noel
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Abdera 0.2.0-incubating Release

[James M Snell]

Doh! I thought I'd caught all of those. Thx.  I'll update those now.

- James

Yoav Shapira wrote:
> Hi,
> I'm referring to the docs included in the release distro, not on the
> site ;)  Just a small note for the next time.
> 
> Yoav
> 
> On 12/5/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> If you're referring to documentation on the site, I planned to update
>> that once the release was up.
>>
>> - James
>>
>> Yoav Shapira wrote:
>> > Hi,
>> > +1 for the release.
>> >
>> > Small nit: much of the documentation still says the version of
>> > 0.1-incubating.  The binary distro files are fine, they say
>> > 0.2-incubating, so hopefully users won't be too confused, but this
>> > will be a good thing to fix for future releases ;)
>> >
>> > Yoav
>> >
>> > On 12/4/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> >> The Abdera PPMC is ready to go with our 0.2.0-incubating release. This
>> >> drop delivers a number of important updates and fixes:
>> >>
>> >>  * A reworked API that improves usability
>> >>  * Decoupled extensions from the underlying parser implementation
>> >>  * A Atom Publishing Protocol client implementation
>> >>  * Updated support for the current Atom Publishing Protocol
>> >>draft specification
>> >>  * Added support for Internationalized Resource Identifiers (IRIs)
>> >>  * Improved Thread Safety
>> >>  * Fixed a number of classloader issues that kept Abdera from
>> >>working properly in application server environments.
>> >>  * Improved Javadocs
>> >>  * Added test cases and sample code
>> >>  * Added experimental Bidirectional Text support
>> >>  * Improved implementation of OpenSearch v1.0 and v1.1 extensions
>> >>  * Implementation of MediaRSS extensions
>> >>  * Implementation of Feed Paging and Archiving extensions
>> >>  * GoogleLogin Authentication Support
>> >>
>> >> Release Candidate:
>> >>
>> >> JDK 1.5:
>> >> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip
>> >> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip.md5
>> >>
>> >> JDK 1.4.2:
>> >> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip
>> >>
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip.md5
>> >>
>> >> Source:
>> >> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip
>> >> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip.md5
>> >>
>> >>
>> >> We'd like to go ahead with the release.  It would be excellent if
>> y'all
>> >> could weigh in.
>> >>
>> >> - James
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Abdera 0.2.0-incubating Release

[James M Snell]

If you're referring to documentation on the site, I planned to update
that once the release was up.

- James

Yoav Shapira wrote:
> Hi,
> +1 for the release.
> 
> Small nit: much of the documentation still says the version of
> 0.1-incubating.  The binary distro files are fine, they say
> 0.2-incubating, so hopefully users won't be too confused, but this
> will be a good thing to fix for future releases ;)
> 
> Yoav
> 
> On 12/4/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> The Abdera PPMC is ready to go with our 0.2.0-incubating release. This
>> drop delivers a number of important updates and fixes:
>>
>>  * A reworked API that improves usability
>>  * Decoupled extensions from the underlying parser implementation
>>  * A Atom Publishing Protocol client implementation
>>  * Updated support for the current Atom Publishing Protocol
>>draft specification
>>  * Added support for Internationalized Resource Identifiers (IRIs)
>>  * Improved Thread Safety
>>  * Fixed a number of classloader issues that kept Abdera from
>>working properly in application server environments.
>>  * Improved Javadocs
>>  * Added test cases and sample code
>>  * Added experimental Bidirectional Text support
>>  * Improved implementation of OpenSearch v1.0 and v1.1 extensions
>>  * Implementation of MediaRSS extensions
>>  * Implementation of Feed Paging and Archiving extensions
>>  * GoogleLogin Authentication Support
>>
>> Release Candidate:
>>
>> JDK 1.5:
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip.md5
>>
>> JDK 1.4.2:
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip.md5
>>
>> Source:
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip
>> http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip.md5
>>
>>
>> We'd like to go ahead with the release.  It would be excellent if y'all
>> could weigh in.
>>
>> - James
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Abdera 0.2.0-incubating Release

[James M Snell]

The Abdera PPMC is ready to go with our 0.2.0-incubating release. This
drop delivers a number of important updates and fixes:

 * A reworked API that improves usability
 * Decoupled extensions from the underlying parser implementation
 * A Atom Publishing Protocol client implementation
 * Updated support for the current Atom Publishing Protocol
   draft specification
 * Added support for Internationalized Resource Identifiers (IRIs)
 * Improved Thread Safety
 * Fixed a number of classloader issues that kept Abdera from
   working properly in application server environments.
 * Improved Javadocs
 * Added test cases and sample code
 * Added experimental Bidirectional Text support
 * Improved implementation of OpenSearch v1.0 and v1.1 extensions
 * Implementation of MediaRSS extensions
 * Implementation of Feed Paging and Archiving extensions
 * GoogleLogin Authentication Support

Release Candidate:

JDK 1.5:
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.zip.md5

JDK 1.4.2:
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.jdk142.zip.md5

Source:
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip
http://people.apache.org/~jmsnell/abdera.0.2.0-incubating.src.zip.md5


We'd like to go ahead with the release.  It would be excellent if y'all
could weigh in.

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Extracting code from an incubation project

[James M Snell]

All,

The Abdera project currently contains a bit of code that implements the
IRI (RFC3987) specification in a way that could be easily extracted out
into its own project.  Recently I posed a question to the Jakarta
Commons and WS Commons projects to see if there would be interest in
pulling that code out into its own commons project.  The response was
generally positive but there was a question raised about the process of
taking code that is currently in incubation and using it to seed a new
non-incubator commons project (in either jakarta or ws).  There was
mention of a past similar discussion on this list but I could not find
it in the archives.

So, the question is simple: if the Abdera PPMC agrees to separate out
the code and either the Jakarta or WS commons projects agree to accept
it, what is the process we need to follow?

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Extracting code from an incubation project

[James M Snell]

Thx. That's simple enough.  Completely overlooked that thread somehow.

- James

Garrett Rooney wrote:
> On 11/21/06, James M Snell <[EMAIL PROTECTED]> wrote:
> 
>> So, the question is simple: if the Abdera PPMC agrees to separate out
>> the code and either the Jakarta or WS commons projects agree to accept
>> it, what is the process we need to follow?
> 
> Check out the thread with the subject "Graduating a part of an
> incubating project into an existing TLP" from the
> [EMAIL PROTECTED] archives from September of this year.
> 
> The short version is that assuming the IP issues have been taken care
> of (they have, the IRI code in Abdera was developed on our mailing
> lists under a CLA, and anything that existed before that work that it
> depends on was covered by a Software Grant from IBM) you can basically
> just do it.  Any committers who go with that code would of course need
> to be granted commit access to the destination project just as any
> other new committer would, of course, and the details of that would
> naturally be up to the destination TLP.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANNOUNCE] Apache Abdera v-0.1.0-incubating

[James M Snell]

The Apache Abdera community is pleased to announce its first developer
preview release (version 0.1.0-incubating)

You can download binary and source distributions from:

http://people.apache.org/dist/incubator/abdera/0.1.0-incubating

Builds are available for Java 1.5 and Java 1.4.2.

For further information, visit our web site at:
http://incubator.apache.org/abdera

Introduction


The goal of the Apache Abdera project is to build a
functionally-complete, high-performance implementation of the IETF Atom
Syndication Format (RFC 4287) and Atom Publishing Protocol (in-progress)
specifications.

Abdera is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

Release Summary
===

 * Parsing Atom Syndication Format 1.0 Feeds
 * Serializing Atom Syndication Format 1.0 Feeds
 * Extension support
 * XML Digital Signature and XML Encryption support
 * High performance incremental parsing model
 * Feed Object Model API


Please feel free to send any feedback to our mailing lists:
abdera-dev@incubator.apache.org
abdera-user@incubator.apache.org

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more
information on how to get involved with the development of Abdera, visit
our website at: http://incubator.apache.org/abdera


Thank you for your interest in Apache Abdera!

- James Snell



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Re: Abdera 0.1.0 Release Candidate

[James M Snell]

Ok, so with this we have three +1 votes and no -1's.  As far as I know
this means that the release is approved.  I've copied the zip's and the
checksums over to
/x1/www/people.apache.org/dist/incubator/abdera/0.1.0-incubating and
will be preparing the release email shortly.

- James

Davanum Srinivas wrote:
> +1 from me. sorry for the delay.
> 
> -- dims
> 
> On 8/17/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
>> On 8/15/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
>>
>> > i'm +1
>>
>> Ok, that's one from Robert and one from me, does anyone else on the
>> PMC care to chime in?
>>
>> -garrett
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] Re: Abdera 0.1.0 Release Candidate

[James M Snell]

Whoops. This is an artifact of switching my trunk image over to branch.
   I'll pull those jars out.

- James

Garrett Rooney wrote:
> On 8/14/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
>> On 8/14/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> > Ok, so we've addressed most of the issues raised in the note below and
>> > believe we are ready to move forward with 0.1.0.  The new zips are
>> > available at http://people.apache.org/~jmsnell
>>
>> +1 from me (binding)
> 
> Actually, hold that...  James, I just noticed that there are some
> jetty jars in the abdera.0.1.0-incubating.zip file.  We didn't start
> using jetty for the tests until recently, after that branch was cut.
> what are they doing in there?
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Vote] Re: Abdera 0.1.0 Release Candidate

[James M Snell]

Ok, so we've addressed most of the issues raised in the note below and
believe we are ready to move forward with 0.1.0.  The new zips are
available at http://people.apache.org/~jmsnell

At your convenience, we'd appreciate it if y'all could review and weigh
in on the release. Thanks!

robert burrell donkin wrote:
> [snip]
> there's a lot of documentation that hasn't been written up yet do i'll
> certainly do that :-)
> 

Additional documentation will be coming.  Right now there are docs that
demonstrate the basic usage of the API which covers the primary goal for
0.1.0

>> but from what I understand, the next step is
>> to ask y'all to review and approve the release candidate.
> 
> i note that you haven't included sample MD5 sums and signatures.
> that's fine if you're confident.
> 

md5 sums have been provided.

> a few notes on best practice for future reference:
> * the binary and source distributions should unpack to directories
> with different names. this makes things more convenient for people who
> download both source and binary versions. also makes it more obvious
> when the source is downloaded. conventionally the source would unpack
> to abdera-x.y.z-incubator-src.

Done

> * list supported build tool versions (ant and maven) in the build
> README (doesn't work with installation of maven 1.0.2)

Done

> * the MANIFEST files should comply with the various java standards on
> this matter. these are really a long way away so i can't list just a
> few corrections. creating complient releases should be included in the
> release management guide very soon but for now see
> http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
> 

Hopefully they're better now.

> important notes
> * there are no license or notice files in the jars distributed in the
> binary. though this is not necessarily a blocking issue, these
> artifacts cannot be distributed as raw jars without them. therefore
> these jars cannot be distributed through maven. if you want to do
> this, you must include LICENSE and NOTICE files in the jars.
> 

Fixed.

> blocking issues
> * copyright headers missing from too many source files (pom.xmls,
> build.xmls, numerous xml and xslt files, docs/*.html). not all of
> these files will be substantial enough for copyright to exist in them
> but IMHO there are so many that this should be addressed before
> releasing.
> 

Fixed.

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Abdera 0.1.0 Release Candidate (please review)

[James M Snell]

Hey Robert,

Thanks for the excellent feedback.  At this point I believe we've
addressed all of the issues you raised and should be re-roll the zips
shortly.

- James

robert burrell donkin wrote:
> On 7/26/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> The Abdera podling has reached a point where the committers feel we're
>> ready to cut a 0.1.0 "developer preview" / "developer milestone"
>> release.  We have +1's from all committers [1] and zero -1's.
>>
>> The release candidate is available at: http://people.apache.org/~jmsnell
>>
>> Java5 and JDK 1.4.2 versions are available, as well as a source
>> distribution.  All source contains appropriate copyright statements and,
>> as far as I know, all dependency requirements have been met.
>>
>> Ant and Maven build options are available.
>>
>> Given that this is the first release, please forgive me if I have missed
>> a step in here somewhere,
> 
> there's a lot of documentation that hasn't been written up yet do i'll
> certainly do that :-)
> 
>> but from what I understand, the next step is
>> to ask y'all to review and approve the release candidate.
> 
> i note that you haven't included sample MD5 sums and signatures.
> that's fine if you're confident.
> 
> a few notes on best practice for future reference:
> * the binary and source distributions should unpack to directories
> with different names. this makes things more convenient for people who
> download both source and binary versions. also makes it more obvious
> when the source is downloaded. conventionally the source would unpack
> to abdera-x.y.z-incubator-src.
> * list supported build tool versions (ant and maven) in the build
> README (doesn't work with installation of maven 1.0.2)
> * the MANIFEST files should comply with the various java standards on
> this matter. these are really a long way away so i can't list just a
> few corrections. creating complient releases should be included in the
> release management guide very soon but for now see
> http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
> 
> important notes
> * there are no license or notice files in the jars distributed in the
> binary. though this is not necessarily a blocking issue, these
> artifacts cannot be distributed as raw jars without them. therefore
> these jars cannot be distributed through maven. if you want to do
> this, you must include LICENSE and NOTICE files in the jars.
> 
> blocking issues
> * copyright headers missing from too many source files (pom.xmls,
> build.xmls, numerous xml and xslt files, docs/*.html). not all of
> these files will be substantial enough for copyright to exist in them
> but IMHO there are so many that this should be addressed before
> releasing.
> 
> IMO the license headers should be addressed before this release
> 
> - robert
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Abdera 0.1.0 Release Candidate (please review)

[James M Snell]

The Abdera podling has reached a point where the committers feel we're
ready to cut a 0.1.0 "developer preview" / "developer milestone"
release.  We have +1's from all committers [1] and zero -1's.

The release candidate is available at: http://people.apache.org/~jmsnell

Java5 and JDK 1.4.2 versions are available, as well as a source
distribution.  All source contains appropriate copyright statements and,
as far as I know, all dependency requirements have been met.

Ant and Maven build options are available.

Given that this is the first release, please forgive me if I have missed
a step in here somewhere, but from what I understand, the next step is
to ask y'all to review and approve the release candidate.

- James

[1] See the thread starting from this message:
http://mail-archives.apache.org/mod_mbox/incubator-abdera-dev/200607.mbox/[EMAIL
 PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE-RESULT] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

Garrett Rooney wrote:
>[snip]
>> As soon as my user account is set up, I can check in the initial drop
>> of the code.
> 
> I believe we'll also need the software grant on file first.
> 

Ok,  I'll look into getting that software grant in by Friday.

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE-RESULT] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

I faxed my CLA in this afternoon.  As soon as my user account is set up,
I can check in the initial drop of the code.

Garrett Rooney wrote:
> On 6/6/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
> 
>> http://incubator.apache.org/projects/abdera.html
> 
> Note that this URL won't work for an hour or so, until it gets rsynced
> over to Ajax.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE-RESULT] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

I'll be faxing my CLA in tomorrow.  Rob should be sending his in soon as
well.

Paul Querna wrote:
>[snip]
> Mailing lists:
> http://issues.apache.org/jira/browse/INFRA-829
> 
> Repository:
> https://svn.apache.org/repos/asf/incubator/abdera/
> 
> Initial committers:
> abdera=eliast,rubys,yoavs
> 
> James M Snell and Robert Yates do not have CLAs or accounts.
> 
> Bugzilla:
> http://issues.apache.org/jira/browse/INFRA-830
> 
> -Paul
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE-RESULT] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

I personally prefer bugzilla for the simple fact that I've very little
experience with Jira :-) ... either is fine tho... the proposal was just
following what I saw in some of the other proposals :-)

- James

Paul Querna wrote:
>[snip]
>> Perhaps we should consult the initial project members and see if they
>> would prefer JIRA to Bugzilla, before we actually start creating
>> projects and so forth...
> 
> I also wouldn't mind Jira, I was just following what was in the proposal :)
> 
> -Paul
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

Yoav Shapira wrote:
> Hi,
> +1 on accepting the proposal for incubation.
> 
> I am also interested in personally contributing to this project as a
> committer, though I regretfully do not have the bandwidth to
> effectively mentor this proposal.  I hope the proposal team doesn't
> mind that I've just added myself to the wiki as a member of the
> initial set of committers.
> 

Don't mind at all.

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Incubator to sponsor and accept Abdera for incubation

[James M Snell]

Sam Ruby wrote:
>[snip]
> However, with that being said, whatever the wiki page may say, the
> people on this project will receive the benefit (ha!) of my personal
> style of quiet mentoring.
> 

And your test cases. Don't forget your test cases.  Test cases are Good. :-)

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Yes, personally I would love to collaborate with the ROME folks on this.
 Their project has a much broader scope in that it supports Atom plus
all the various flavors of RSS, but there are a number of ways in which
the two projects could feed off of and into each other.

- James

Noel J. Bergman wrote:
> Nick Lothian wrote:
> 
>> There's also Jakarta FeedParser, which has an Atom parser.
> 
>> Also the ROME project (http://rome.dev.java.net/) has been debating
>> requesting incubation at Apache for quite a long time. We've got an
>> Atom parser, too.
> 
> IIRC, FeedParser is languishing for need of a community.  Roller also has an
> Atom parser, AIUI.  Is there any desire to combine forces in this domain?  I
> saw Dave Johnson expressing interest in this proposal, too.
> 
>   --- Noel
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name options (was Re: ARI, Atom Reference Implementation [Proposal])

[James M Snell]

Trademarked. I liked it too.

http://tess2.uspto.gov/bin/showfield?f=doc&state=b0fu7h.2.1

Noel J. Bergman wrote:
>> what was wrong with "Atomate"? I really liked that one.
> 
> So did I, actually.  Not that I have a horse in this race.
> 
>   --- Noel
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Abdera (was: Re: ARI, Atom Reference Implementation [Proposal])

[James M Snell]

Ok, given all the +1's in favor of the name Abdera, I've updated the
proposal to use the new name.  The wiki has been updated accordingly:

http://wiki.apache.org/incubator/AbderaProposal

- James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name options (was Re: ARI, Atom Reference Implementation [Proposal])

[James M Snell]

The project will consist of three distinct components

a. An Atom parser/serializer.  This is the Axiom-based code that is
available in the tar referenced by the proposal

b. An Atom Publishing Protocol Client... likely taking the form of a set
of utility/helper objects based on the Commons HttpClient

c. An Atom Publishing Protocol Server... likely taking the form of a set
of interfaces and utility objects intended to allow any application to
provide an "atom interface".

Ultimately, I would also like to see an "Atom store" developed.  The
Atom store is a data persistent layer built around the Atom data model
and publishing protocol.

- James

Sanjiva Weerawarana wrote:
> Hi James,
> 
> (Greetings; hope u r doing well :))
> 
> How far does this project intend to go in implemention Atom? Is it a
> client side only, a tool to support Atom generation from some other app,
> APP, etc. etc.?
> 
> (Sorry if this is an obvious answer question; I'm not an Atom expert at
> all.)
> 
> Thanks,
> 
> Sanjiva.
> 
> On Wed, 2006-05-24 at 16:47 -0700, James M Snell wrote:
>> Ok, so here are a few of the name options that seem to be the safest (in
>> no particular order)
>>
>> Iaea  (adapted, of course, from the U.N. nuclear watchdog group)
>> Anu   (Dims suggestion, sanskrit for "atom")
>> Atomico   (Spanish/Italian for "atomic")
>> Dalton(Suggested by Robert B. Donkin)
>> Abdera(birthplace of the philosopher Demokritos)
>>
>> I think any of these would work.
>>
>> - James
>>
>> Yoav Shapira wrote:
>>> Hi,
>>>
>>> On 5/24/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>>> Ok, it was worth a shot.  I've been stewing over possible name
>>>> selections for a couple days and can't seem to come up with any strong
>>>> possibilities.
>>> Why not take the stuff that's been suggested so far (there have been
>>> 10+ ideas, no?), put it to a vote here, and take the resulting name so
>>> the project can move along?  If the committers on the project *really*
>>> dislike it later, they may change it.
>>>
>>> Or do you mean that you want to pick something yourself and don't want
>>> a community-chosen name?  (I don't really care, I'm just curious to
>>> see if I misinterpreted your original call for names)
>>>
>>> Yoav
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Name options (was Re: ARI, Atom Reference Implementation [Proposal])

[James M Snell]

Ok, so here are a few of the name options that seem to be the safest (in
no particular order)

Iaea  (adapted, of course, from the U.N. nuclear watchdog group)
Anu   (Dims suggestion, sanskrit for "atom")
Atomico   (Spanish/Italian for "atomic")
Dalton(Suggested by Robert B. Donkin)
Abdera(birthplace of the philosopher Demokritos)

I think any of these would work.

- James

Yoav Shapira wrote:
> Hi,
> 
> On 5/24/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> Ok, it was worth a shot.  I've been stewing over possible name
>> selections for a couple days and can't seem to come up with any strong
>> possibilities.
> 
> Why not take the stuff that's been suggested so far (there have been
> 10+ ideas, no?), put it to a vote here, and take the resulting name so
> the project can move along?  If the committers on the project *really*
> dislike it later, they may change it.
> 
> Or do you mean that you want to pick something yourself and don't want
> a community-chosen name?  (I don't really care, I'm just curious to
> see if I misinterpreted your original call for names)
> 
> Yoav
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

I've gone through all of the suggestions offered here and have done a
variety of trademark/google searches on each.  I think for every one
that there has been at least two or three relevant hits either on google
or USPTO. A community chosen name is great, so long as it doesn't cause
any potential trademark headaches.

- James

Yoav Shapira wrote:
> Hi,
> 
> On 5/24/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> Ok, it was worth a shot.  I've been stewing over possible name
>> selections for a couple days and can't seem to come up with any strong
>> possibilities.
> 
> Why not take the stuff that's been suggested so far (there have been
> 10+ ideas, no?), put it to a vote here, and take the resulting name so
> the project can move along?  If the committers on the project *really*
> dislike it later, they may change it.
> 
> Or do you mean that you want to pick something yourself and don't want
> a community-chosen name?  (I don't really care, I'm just curious to
> see if I misinterpreted your original call for names)
> 
> Yoav
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Ok, it was worth a shot.  I've been stewing over possible name
selections for a couple days and can't seem to come up with any strong
possibilities.

- James

Martin Cooper wrote:
> On 5/24/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>
>> Does any one have any problems with simply calling this project
>> "Atom"... as in, "The Apache Atom Implementation" ?
> 
> 
> Well, unless I'm mistaken, it would actually be (at least) the second Atom
> implementation at the ASF, since Roller has one already. Simply calling it
> Atom implies it has some special status, especially in the phrase you use
> above (i.e. "The Apache Atom Implementation"). So I would not be in favour
> of that name.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Does any one have any problems with simply calling this project
"Atom"... as in, "The Apache Atom Implementation" ?

- James

Garrett Rooney wrote:
> On 5/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> The following is a new project incubation proposal. We welcome your
>> feedback and would like to extend a invitation for participation
>> including mentors.
>>
>> The proposal is also located at
>>   http://wiki.apache.org/incubator/AriProposal
>>
>> The initial source for the project is available at:
>>   http://www.snellspace.com/public/ari.tar.gz
> 
> I would be interested in helping to mentor this project, and perhaps
> eventually working on C implementations of some of its functionality.
> 
> One comment though, you might want to reroll ari.tar.gz so it unpacks
> into a directory named ari, as opposed to spilling all sorts of stuff
> into the current working directory.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Good catch. Ok, we'll keep looking :-)

Davanum Srinivas wrote:
> http://www.google.com/search?q=+%22wave+systems%22+software seems too
> close for comfort.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Yes, I did run a search. There were a number of hits for the term
"wave", but none of which seem particularly relevant/conflicting. (one
business consultant firm, a cigarette brand, a medical science research
firm, swimming goggles, etc)

- James

Davanum Srinivas wrote:
> James,
> 
> did you search for trademarks?
> http://tess2.uspto.gov/bin/gate.exe?f=tess&state=vmko9c.6.51
> 
> thanks,
> dims
> 
> On 5/23/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> Alrighty. Thanks for the all the name suggestions. I've been Googling
>> like crazy and the best candidate seems to be "Wave"
>>
>> The three initial committers are fine with that name.  If there are no
>> objections, I can go ahead and update the proposal to use that name.
>>
>> - James
>>
>> Garrett Rooney wrote:
>> > On 5/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hello,
>> >>
>> >> The following is a new project incubation proposal. We welcome your
>> >> feedback and would like to extend a invitation for participation
>> >> including mentors.
>> >>
>> >> The proposal is also located at
>> >>   http://wiki.apache.org/incubator/AriProposal
>> >>
>> >> The initial source for the project is available at:
>> >>   http://www.snellspace.com/public/ari.tar.gz
>> >
>> > I would be interested in helping to mentor this project, and perhaps
>> > eventually working on C implementations of some of its functionality.
>> >
>> > One comment though, you might want to reroll ari.tar.gz so it unpacks
>> > into a directory named ari, as opposed to spilling all sorts of stuff
>> > into the current working directory.
>> >
>> > -garrett
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Alrighty. Thanks for the all the name suggestions. I've been Googling
like crazy and the best candidate seems to be "Wave"

The three initial committers are fine with that name.  If there are no
objections, I can go ahead and update the proposal to use that name.

- James

Garrett Rooney wrote:
> On 5/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> The following is a new project incubation proposal. We welcome your
>> feedback and would like to extend a invitation for participation
>> including mentors.
>>
>> The proposal is also located at
>>   http://wiki.apache.org/incubator/AriProposal
>>
>> The initial source for the project is available at:
>>   http://www.snellspace.com/public/ari.tar.gz
> 
> I would be interested in helping to mentor this project, and perhaps
> eventually working on C implementations of some of its functionality.
> 
> One comment though, you might want to reroll ari.tar.gz so it unpacks
> into a directory named ari, as opposed to spilling all sorts of stuff
> into the current working directory.
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Thanks for all the name suggestions given thus far.  Keep 'em coming.

The two names I have in mind (in order of preference) are:

1. Wave
2. Atomos

- James


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

+1. it would be VERY helpful to have an Axiom expert advising on the
project, even if it's not in a formal mentor role.

- James

robert burrell donkin wrote:
> On 5/23/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
> 
> 
> hi eran
> 
> I'm Eran Chinthaka, one of the contributors from Axiom and Axis2
>> projects. I also would like to mentor this project as I have worked a
>> lot with Axiom and involved in integrating Atom and RSS feed generation
>> in to Axis2.
> 
> 
> i was hoping that some axis folks would jump in :)
> 
> But I read the FAQ [1] and it states you have to be a member of ASF to
>> become a mentor. So I wonder whether I can help as a mentor as I'm just
>> a PMC member.
> 
> 
> AIUI not as a mentor. it's a particular role involving oversight and the
> current concensus amongst the membership is that this is something that
> should be restricted to members only.
> 
> but that doesn't mean that it wouldn't be good to have you involved. you
> don't need to be a formal mentor to offer guidance on list. if you're going
> to be able to find some time to help out with the coding then maybe it'd be
> a good idea if your name were added to the proposal as a developer.
> 
> - robert
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Not good: http://www.jtauber.com/demokritos

FTR, the names we've kicked around include "Covalence" (too close to
Covalent), "Valencia" (Spanish for "Valence"), atomos (Latin root for
"Atom"), and chimie (French for chemistry).  Our lawyers didn't like
"Covalence" or "Valencia" so those were shot down during the donation
approval process.  I'd be happy with just about any name so long as it
means we can move forward :-)

- James

Garrett Rooney wrote:
> On 5/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
>> That's fine. We've gone through a number of names internally and pretty
>> much gave up on trying to come up with something good. Alternative name
>> suggestions would be greatly appreciated. :-)
> 
> How about "Democritus"?
> 
> For those who haven't been crawling around wikipedia looking for names
> related to atom, Democritus was the Greek philosopher who came up with
> atomism, the theory that all objects in the universe are composed of
> small, indestructible elements, atoms.
> 
> http://en.wikipedia.org/wiki/Democritus
> http://en.wikipedia.org/wiki/Atomism
> 
> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

That's fine. We've gone through a number of names internally and pretty
much gave up on trying to come up with something good. Alternative name
suggestions would be greatly appreciated. :-)

- James

Roy T. Fielding wrote:
> On May 22, 2006, at 12:23 PM, James M Snell wrote:
> 
>> The following is a new project incubation proposal. We welcome your
>> feedback and would like to extend a invitation for participation
>> including mentors.
>>
>> The proposal is also located at
>>   http://wiki.apache.org/incubator/AriProposal
>>
>> The initial source for the project is available at:
>>   http://www.snellspace.com/public/ari.tar.gz
> 
> -1 under that name.  Atom is owned by the IETF.  The IETF does not have
> reference implementations -- any one implementation is as referenced
> as any other.  It would be socially rude (and factually incorrect) to
> use such a name here.
> 
> Roy
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Paul Querna wrote:
>[snip]
> I am also interested in helping mentor the project, and to work on a C
> implementation of its functionality.  Possibly even donate
> code for a C based parser.
> 

Excellent. Thank you.

- James


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Garrett Rooney wrote:
> On 5/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> The following is a new project incubation proposal. We welcome your
>> feedback and would like to extend a invitation for participation
>> including mentors.
>>
>> The proposal is also located at
>>   http://wiki.apache.org/incubator/AriProposal
>>
>> The initial source for the project is available at:
>>   http://www.snellspace.com/public/ari.tar.gz
> 
> I would be interested in helping to mentor this project, and perhaps
> eventually working on C implementations of some of its functionality.
> 

Excellent.

> One comment though, you might want to reroll ari.tar.gz so it unpacks
> into a directory named ari, as opposed to spilling all sorts of stuff
> into the current working directory.
> 

Doh! sorry about that. Fixed.

- James

> -garrett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

ARI, Atom Reference Implementation [Proposal]

[James M Snell]

Hello,

The following is a new project incubation proposal. We welcome your
feedback and would like to extend a invitation for participation
including mentors.

The proposal is also located at
  http://wiki.apache.org/incubator/AriProposal

The initial source for the project is available at:
  http://www.snellspace.com/public/ari.tar.gz

Thank you,

- James M Snell
  [EMAIL PROTECTED]
  [EMAIL PROTECTED]

=

= ARI, an Atom Reference Implementation Proposal =

== 0. Rationale ==

The fundamental goal of ARI is to provide a high-quality and
functionally-complete reference implementation of the Atom Syndication
Format (RFC4287) and the Atom Publishing Protocol specifications
published by the IETF Atompub working group.

== 0.1 Criteria ==

=== Meritocracy: ===

Apache was chosen for an incubator for the guidance the community can
provide.

=== Community: ===

The contributed work was inspired by open source development and by the
need to have functionally complete implementations of the Atom
specifications available for developers to use.  To be successful, the
project needs to build a strong and diverse community to validate its
mission and carry it forward. Further, the project needs to be guided by
the same general principles of open and transparent development that has
helped to shape the standards upon which the project is based.

=== Core Developers: ===

The initial committers for the project are employees of the donating
company. Two of the developers have worked on open source projects
before and have experience with and a deep understanding of open source
principles.

=== Alignment: ===

The initial code has been implemented in Java and is based primarily on
the same Apache Axiom / StAX XML parsing API that underpins the Apache
Axis2 project.  As such, the implementations draws heavily on the work
of other existing Apache projects and will continue to do so.

== 0.2 Warning signs ==

=== Orphaned products: ===

The initial committers are users of this toolkit and have a long-term
interest in use and maintenance of the code.

=== Inexperience with open source: ===

Several of the commiters are very experienced in Open Source
environment. All efforts have and will be made to ensure that the work
done and momentum will be in strict adherence to open source guidelines.

=== Homogenous developers: ===

As noted above, the initial list of developers consists of paid
employees of the donating company.  However, efforts will be made to
actively expand the team of developers committing to the project.

The current list of committers bring with them a broad range of
experiences with open source, standards, emerging technologies, and
product development.

=== Reliance on salaried developers: ===

The initial set of committers are salaried developers. Through the
incubation process, more diversity will hopefully be achieved in many
aspects, including reliance on salaried developers.

=== No ties to other Apache products: ===

The initial codebase relies heavily on existing Apache technologies and
will continue to do so.

=== A fascination with the Apache brand: ===

The committers are intent on developing a strong open source community.
We believe that the Apache Software Foundation's emphasis on community
development makes it the most suitable choice.

== 1. Scope of the subprojects ==

The initial scope of the project will be the development of a
Java-language reference implementation of the Atom Syndication Format
and Atom Publishing Protocol specifications, along with a selection of
extensions and utility functions.  It is expected, however, that C/C++
and possibly other language implementations will be explored in the
future.

The Atom Syndication Format implementation will include a
high-performance parser and serializer for Atom documents, a set of
API's for working with the Atom data model, support for a variety of
extensions to the Atom format, and support for various advanced features
such as XPath, XML Digital Signatures, Feed paging, etc.

The Atom Publishing Protocol implementation will include both client and
server implementations designed with the dual purpose of demonstrating
the proper function of the protocol and providing the tools necessary to
build and deploy Atom Publishing-based applications.

== 2. Initial source ==

The initial source for the ARI project was originally written to address
the needs of the donating company's own internal Atom development
activities.  A snapshot of the initial source is available at
http://www.snellspace.com/public/ari.tar.gz.

== 2.1 External Dependencies of the project ==

The current ARI implemenation depends on the following components:

 * Apache Axiom 1.0
 * StAX XML API's
 * The Woodstox XML Parser
 * Java Activation Framework (JAF) and JavaMail API
 * Jaxen (optional for XPath support)
 * Junit (for unit testing)
 * Apache Ant (for the build)

== 3. Identify the ASF res