Re: [VOTE] OODT Graduation to TLP

[Niclas Hedhman]

+1

On Thu, Nov 11, 2010 at 11:18 PM, Mattmann, Chris A (388J)
 wrote:
> Hi IPMC'ers and the rest of the Incubator community,
>
> The OODT community has been discussing graduation to TLP [1]. There is
> overwhelming consensus in the community (all +1 VOTEs including those from
> our mentors) that we've achieved what's required here in the Incubator, and
> so we'd like to put forth the following board resolution for the next Board
> meeting to promote OODT to an Apache TLP and graduate from the Incubator.
>
> Please VOTE on the below resolution for promoting OODT to an Apache TLP and
> graduating from the Incubator. The VOTE is open for 72 hrs.
>
> [ ] +1 Accept OODT's graduation from the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept OODT's graduation from the Incubator because...
>
> =
>      Establish the Apache OODT Project
>
>       WHEREAS, the Board of Directors deems it to be in the best
>       interests of the Foundation and consistent with the
>       Foundation's purpose to establish a Project Management
>       Committee charged with the creation and maintenance of
>       open-source software related to the construction of scientific,
>      data management systems for distribution at no charge to the public.
>
>       NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>       Committee (PMC), to be known as the "Apache OODT Project",
>       be and hereby is established pursuant to Bylaws of the
>       Foundation; and be it further
>
>       RESOLVED, that the Apache OODT Project be and hereby is
>       responsible for the creation and maintenance of software
>       related to the construction of scientific, data management
>      systems; and be it further
>
>       RESOLVED, that the office of "Vice President, Apache OODT" be
>       and hereby is created, the person holding such office to
>       serve at the direction of the Board of Directors as the chair
>       of the Apache OODT Project, and to have primary responsibility
>       for management of the projects within the scope of
>       responsibility of the Apache OODT Project; and be it further
>
>       RESOLVED, that the persons listed immediately below be and
>       hereby are appointed to serve as the initial members of the
>       Apache OODT Project:
>
>      * Andrew Hart (ah...@apache.org)
>      * Brian Foster (bfos...@apache.org)
>      * Cameron Goodale (good...@apache.org)
>       * Chris A. Mattmann (mattm...@apache.org)
>      * Dan Crichton (crich...@apache.org)
>       * David Kale (davek...@apache.org)
>      * David Woollard (wooll...@apache.org)
>      * Ian Holsman (i...@apache.org)
>      * Joshua Garcia (joshu...@apache.org)
>      * Justin Erenkrantz (jerenkra...@apache.org)
>      * Paul Ramirez (prami...@apache.org)
>      * Sean Hardman (shard...@apache.org)
>      * Sean McCleese (smccl...@apache.org)
>      * Sean Kelly (ke...@apache.org)
>
>       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris A. Mattmann
>       be appointed to the office of Vice President, Apache OODT, to
>       serve in accordance with and subject to the direction of the
>       Board of Directors and the Bylaws of the Foundation until
>       death, resignation, retirement, removal or disqualification,
>       or until a successor is appointed; and be it further
>
>       RESOLVED, that the Apache OODT Project be and hereby
>       is tasked with the migration and rationalization of the Apache
>       Incubator OODT sub-project; and be it further
>
>       RESOLVED, that all responsibilities pertaining to the Apache
>       Incubator OODT sub-project encumbered upon the
>       Apache Incubator Project are hereafter discharged.
> =
>
> Here's my +1 (binding).
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add me to the Incubator UNIX group

[Patrick Hunt]

Thanks Joe!

On Fri, Nov 12, 2010 at 10:23 PM, Joe Schaefer  wrote:
> Done.
>
>
>
> - Original Message 
>> From: Patrick Hunt 
>> To: general@incubator.apache.org
>> Sent: Sat, November 13, 2010 1:17:45 AM
>> Subject: Re: Please add me to the Incubator UNIX group
>>
>> Sorry, that is I'm trying to finalize the Whirr release. Thanks.
>>
>> On Fri,  Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
>> > Hello, a  hand please?
>> >
>> > Can someone with the necessary karma please add me  to the Incubator
>> > UNIX group so that I can finalize the release/site? I'm  the release
>> > manager and commiter on the project.
>> >
>> >  Thanks,
>> >
>> >  Patrick
>> >
>>
>> -
>> 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
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please add me to the Incubator UNIX group

[Joe Schaefer]

Done.



- Original Message 
> From: Patrick Hunt 
> To: general@incubator.apache.org
> Sent: Sat, November 13, 2010 1:17:45 AM
> Subject: Re: Please add me to the Incubator UNIX group
> 
> Sorry, that is I'm trying to finalize the Whirr release. Thanks.
> 
> On Fri,  Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
> > Hello, a  hand please?
> >
> > Can someone with the necessary karma please add me  to the Incubator
> > UNIX group so that I can finalize the release/site? I'm  the release
> > manager and commiter on the project.
> >
> >  Thanks,
> >
> >  Patrick
> >
> 
> -
> 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

Re: Please add me to the Incubator UNIX group

[Patrick Hunt]

Sorry, that is I'm trying to finalize the Whirr release. Thanks.

On Fri, Nov 12, 2010 at 10:16 PM, Patrick Hunt  wrote:
> Hello, a hand please?
>
> Can someone with the necessary karma please add me to the Incubator
> UNIX group so that I can finalize the release/site? I'm the release
> manager and commiter on the project.
>
> Thanks,
>
> Patrick
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Please add me to the Incubator UNIX group

[Patrick Hunt]

Hello, a hand please?

Can someone with the necessary karma please add me to the Incubator
UNIX group so that I can finalize the release/site? I'm the release
manager and commiter on the project.

Thanks,

Patrick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Whirr version 0.2.0-incubating

[Patrick Hunt]

With 3 +1's (Tom White's binding vote was cast on the whirr-dev list)
and no -1's the vote
passes. I'm working to publish the release and will send announcements
as soon as that's
done.

Thanks everyone.

Patrick

On Fri, Nov 12, 2010 at 4:52 PM, Doug Cutting  wrote:
> +1 Checksums & sigs are correct.  Licensing looks good.
>
> Doug
>
> On 11/10/2010 08:59 AM, Patrick Hunt wrote:
>>
>> This is the second incubator release for Apache Whirr, version
>> 0.2.0-incubating.
>>
>> PPMC release vote thread:
>> http://markmail.org/message/kdfnohhod6wdrqaz
>>
>> The issues fixed for 0.2.0-incubating
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230&styleName=Html&version=12315339
>>
>> Source and binary files:
>> http://people.apache.org/~phunt/whirr-0.2.0-candidate-0/
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachewhirr-032
>>
>> The tag to be voted upon:
>>
>> http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.2.0-incubating
>>
>> The vote is open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> -
>> 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
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Paolo Castagna]

Jeremy Carroll wrote:

I think this comes down to saxon as the issue

is this helpful?
http://svn.apache.org/viewvc/servicemix/smx4/bundles/tags/org.apache.servicemix.bundles.saxon-9.1.0.1_1/pom.xml?view=markup 


It seems to me that the servicemix project, which I do not know, has its own
Maven repo with Saxon in it:
http://svn.apache.org/repos/asf/servicemix/m2-repo/net/sf/saxon/

 "If you want to get a specific library into the Central repository,
  all you need to do is sign up for an account on https://issues.sonatype.org/,
  create an artifact bundle, and upload it to a staging repository.
  Sonatype will perform some due diligence to make sure that the
  artifact has a license compatible with unrestricted distribution,
  and we will then promote the uploaded artifacts to the Central
  Maven repository."
  -- 
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central


Perhaps, this is what we need to do.

Hopefully, we are not the only one in the world wanting Saxon artifacts in
the Maven Central repository.

Paolo

the other items (CyberNeko, XML Commons)  may be work to find the right 
links ...


  [5] http://repo1.maven.org/maven2/nekohtml/nekohtml/0.9.5/
  [6] http://repo1.maven.org/maven2/xml-resolver/xml-resolver/1.2/

:-)

Paolo



Jeremy


Jeremy Carroll wrote:

On 11/12/2010 11:51 AM, Paolo Castagna wrote:


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


Also, this relates to the release process and publishing of artifacts
in the Maven Central repository.

I am still unclear if these sort of messages is appropriate here or
they should go to jena-devel.

The Jena GRDDL Reader has these dependencies (in addition to Jena2
and ARQ): Saxon-HE v9.x(?) [1], CyberNeko HTML Parser v0.9.5(?) [2],
BrowserLauncher2 v1.0(?) [3] and XML Commons Resolver v1.2 (?) [4].

AFAIK only nekohtml and xml-commons-resolver are currently in the
Maven repo [5,6].

I don't see where XML Commons Resolver is actually used, but this
could just be my ignorance of Xerces and/or Saxon internals.

How this will impact the building/releasing process within the
Apache incubator?

Maven artifacts are not mandatory (which is good):

 "Releases for podling MUST be distributed through
  http://www.apache.org/dist/incubator/podling In addition,
  the Podling MAY choose to distribute approved releases through
  other channels like the central Maven repository." [7]

However, I'd like to publish GRDDL artifacts in the Maven repo,
as well as all the other Jena artifacts [8].

These are also relevant:

 "Besides, we discourage putting release repository/pluginRepository
  in your POM. In ideal conditions, all your dependencies should
  be already in central and central repository is self-contained.
  Otherwise people's build might break because of missing dependencies.
  If some of your dependencies are not in central, please upload them
  using our 3rd-party artifacts bundle upload service." [9] via [10]

 "While most projects understand the importance of publishing artifacts
  to Central, there are still a few projects out there that don't have
  the same appreciation. When a project refuses to upload artifacts to
  Central, for whatever reason, we encourage people to submit artifact
  bundles to Central themselves.
  Sonatype is replacing this process with a self-serve approach. If you
  want to get a specific library into the Central repository, all you
  need to do is sign up for an account on https://issues.sonatype.org/,
  create an artifact bundle, and upload it to a staging repository.
  Sonatype will perform some due diligence to make sure that the
  artifact has a license compatible with unrestricted distribution,
  and we will then promote the uploaded artifacts to the Central
  Maven repository." [11]

You can include me with the people who do appreciate finding artifacts in
the Maven Central repository (no matter how they are produced: Maven, 
Ant+Ivy,

etc.).

Any help/suggestion is more than welcome,
Paolo

  [1] http://saxon.sourceforge.net/
  [2] http://sourceforge.net/projects/nekohtml/
  [3] http://browserlaunch2.sourceforge.net/
  [4] http://xml.apache.org/commons/
  [5] http://repo1.maven.org/maven2/nekohtml/nekohtml/0.9.5/
  [6] http://repo1.maven.org/maven2/xml-resolver/xml-resolver/1.2/
  [7] 
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

  [8] http://repo2.maven.org/maven2/com/hp/hpl/jena/
  [9] 
https://docs.sonatype.org/display/Repository/Central+Sync+Requirements

 [10] http://www.apache.org/dev/publishing-maven-artifacts.html
 [11] 
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central 




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Jeremy Carroll]

I think this comes down to saxon as the issue

is this helpful?
http://svn.apache.org/viewvc/servicemix/smx4/bundles/tags/org.apache.servicemix.bundles.saxon-9.1.0.1_1/pom.xml?view=markup

the other items (CyberNeko, XML Commons)  may be work to find the right 
links ...


Jeremy


Jeremy Carroll wrote:

On 11/12/2010 11:51 AM, Paolo Castagna wrote:


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


Also, this relates to the release process and publishing of artifacts
in the Maven Central repository.

I am still unclear if these sort of messages is appropriate here or
they should go to jena-devel.

The Jena GRDDL Reader has these dependencies (in addition to Jena2
and ARQ): Saxon-HE v9.x(?) [1], CyberNeko HTML Parser v0.9.5(?) [2],
BrowserLauncher2 v1.0(?) [3] and XML Commons Resolver v1.2 (?) [4].

AFAIK only nekohtml and xml-commons-resolver are currently in the
Maven repo [5,6].

I don't see where XML Commons Resolver is actually used, but this
could just be my ignorance of Xerces and/or Saxon internals.

How this will impact the building/releasing process within the
Apache incubator?

Maven artifacts are not mandatory (which is good):

 "Releases for podling MUST be distributed through
  http://www.apache.org/dist/incubator/podling In addition,
  the Podling MAY choose to distribute approved releases through
  other channels like the central Maven repository." [7]

However, I'd like to publish GRDDL artifacts in the Maven repo,
as well as all the other Jena artifacts [8].

These are also relevant:

 "Besides, we discourage putting release repository/pluginRepository
  in your POM. In ideal conditions, all your dependencies should
  be already in central and central repository is self-contained.
  Otherwise people's build might break because of missing dependencies.
  If some of your dependencies are not in central, please upload them
  using our 3rd-party artifacts bundle upload service." [9] via [10]

 "While most projects understand the importance of publishing artifacts
  to Central, there are still a few projects out there that don't have
  the same appreciation. When a project refuses to upload artifacts to
  Central, for whatever reason, we encourage people to submit artifact
  bundles to Central themselves.
  Sonatype is replacing this process with a self-serve approach. If you
  want to get a specific library into the Central repository, all you
  need to do is sign up for an account on https://issues.sonatype.org/,
  create an artifact bundle, and upload it to a staging repository.
  Sonatype will perform some due diligence to make sure that the
  artifact has a license compatible with unrestricted distribution,
  and we will then promote the uploaded artifacts to the Central
  Maven repository." [11]

You can include me with the people who do appreciate finding artifacts in
the Maven Central repository (no matter how they are produced: Maven, 
Ant+Ivy,

etc.).

Any help/suggestion is more than welcome,
Paolo

  [1] http://saxon.sourceforge.net/
  [2] http://sourceforge.net/projects/nekohtml/
  [3] http://browserlaunch2.sourceforge.net/
  [4] http://xml.apache.org/commons/
  [5] http://repo1.maven.org/maven2/nekohtml/nekohtml/0.9.5/
  [6] http://repo1.maven.org/maven2/xml-resolver/xml-resolver/1.2/
  [7] 
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

  [8] http://repo2.maven.org/maven2/com/hp/hpl/jena/
  [9] 
https://docs.sonatype.org/display/Repository/Central+Sync+Requirements

 [10] http://www.apache.org/dev/publishing-maven-artifacts.html
 [11] 
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central



-
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

Re: [VOTE] OODT Graduation to TLP

[Paul Zimdars]

Yes yes yes! :) +1 non-binding.

Paul
On Fri, 2010-11-12 at 19:42 -0800, Cameron Goodale wrote:
> +1 non-binding
> 
> Best Regards,
> 
> Cameron
> 
> On Fri, Nov 12, 2010 at 10:40 AM, Ramirez, Paul M (388J) <
> paul.m.rami...@jpl.nasa.gov> wrote:
> 
> > +1 (non binding) for making OODT a TLP.
> >
> > Thanks,
> > Paul
> >
> > On Nov 11, 2010, at 7:18 AM, Mattmann, Chris A (388J) wrote:
> >
> > > Hi IPMC'ers and the rest of the Incubator community,
> > >
> > > The OODT community has been discussing graduation to TLP [1]. There is
> > > overwhelming consensus in the community (all +1 VOTEs including those
> > from
> > > our mentors) that we've achieved what's required here in the Incubator,
> > and
> > > so we'd like to put forth the following board resolution for the next
> > Board
> > > meeting to promote OODT to an Apache TLP and graduate from the Incubator.
> > >
> > > Please VOTE on the below resolution for promoting OODT to an Apache TLP
> > and
> > > graduating from the Incubator. The VOTE is open for 72 hrs.
> > >
> > > [ ] +1 Accept OODT's graduation from the Incubator
> > > [ ] +0 Don't care.
> > > [ ] -1 Don't accept OODT's graduation from the Incubator because...
> > >
> > > =
> > >  Establish the Apache OODT Project
> > >
> > >   WHEREAS, the Board of Directors deems it to be in the best
> > >   interests of the Foundation and consistent with the
> > >   Foundation's purpose to establish a Project Management
> > >   Committee charged with the creation and maintenance of
> > >   open-source software related to the construction of scientific,
> > >  data management systems for distribution at no charge to the public.
> > >
> > >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >   Committee (PMC), to be known as the "Apache OODT Project",
> > >   be and hereby is established pursuant to Bylaws of the
> > >   Foundation; and be it further
> > >
> > >   RESOLVED, that the Apache OODT Project be and hereby is
> > >   responsible for the creation and maintenance of software
> > >   related to the construction of scientific, data management
> > >  systems; and be it further
> > >
> > >   RESOLVED, that the office of "Vice President, Apache OODT" be
> > >   and hereby is created, the person holding such office to
> > >   serve at the direction of the Board of Directors as the chair
> > >   of the Apache OODT Project, and to have primary responsibility
> > >   for management of the projects within the scope of
> > >   responsibility of the Apache OODT Project; and be it further
> > >
> > >   RESOLVED, that the persons listed immediately below be and
> > >   hereby are appointed to serve as the initial members of the
> > >   Apache OODT Project:
> > >
> > >  * Andrew Hart (ah...@apache.org)
> > >  * Brian Foster (bfos...@apache.org)
> > >  * Cameron Goodale (good...@apache.org)
> > >   * Chris A. Mattmann (mattm...@apache.org)
> > >  * Dan Crichton (crich...@apache.org)
> > >   * David Kale (davek...@apache.org)
> > >  * David Woollard (wooll...@apache.org)
> > >  * Ian Holsman (i...@apache.org)
> > >  * Joshua Garcia (joshu...@apache.org)
> > >  * Justin Erenkrantz (jerenkra...@apache.org)
> > >  * Paul Ramirez (prami...@apache.org)
> > >  * Sean Hardman (shard...@apache.org)
> > >  * Sean McCleese (smccl...@apache.org)
> > >  * Sean Kelly (ke...@apache.org)
> > >
> > >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris A. Mattmann
> > >   be appointed to the office of Vice President, Apache OODT, to
> > >   serve in accordance with and subject to the direction of the
> > >   Board of Directors and the Bylaws of the Foundation until
> > >   death, resignation, retirement, removal or disqualification,
> > >   or until a successor is appointed; and be it further
> > >
> > >   RESOLVED, that the Apache OODT Project be and hereby
> > >   is tasked with the migration and rationalization of the Apache
> > >   Incubator OODT sub-project; and be it further
> > >
> > >   RESOLVED, that all responsibilities pertaining to the Apache
> > >   Incubator OODT sub-project encumbered upon the
> > >   Apache Incubator Project are hereafter discharged.
> > > =
> > >
> > > Here's my +1 (binding).
> > >
> > > Cheers,
> > > Chris
> > >
> > > ++
> > > Chris Mattmann, Ph.D.
> > > Senior Computer Scientist
> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > Office: 171-266B, Mailstop: 171-246
> > > Email: chris.mattm...@jpl.nasa.gov
> > > WWW:   http://sunset.usc.edu/~mattmann/
> > > ++
> > > Adjunct Assistant Professor, Computer Science Department
> > > University of Southern California, Los Angeles, CA 90089 USA

Re: [Proposal] Accept Jena into the Incubator

[Paolo Castagna]

Jeremy Carroll wrote:

On 11/12/2010 11:51 AM, Paolo Castagna wrote:


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


Also, this relates to the release process and publishing of artifacts
in the Maven Central repository.

I am still unclear if these sort of messages is appropriate here or
they should go to jena-devel.

The Jena GRDDL Reader has these dependencies (in addition to Jena2
and ARQ): Saxon-HE v9.x(?) [1], CyberNeko HTML Parser v0.9.5(?) [2],
BrowserLauncher2 v1.0(?) [3] and XML Commons Resolver v1.2 (?) [4].

AFAIK only nekohtml and xml-commons-resolver are currently in the
Maven repo [5,6].

I don't see where XML Commons Resolver is actually used, but this
could just be my ignorance of Xerces and/or Saxon internals.

How this will impact the building/releasing process within the
Apache incubator?

Maven artifacts are not mandatory (which is good):

 "Releases for podling MUST be distributed through
  http://www.apache.org/dist/incubator/podling In addition,
  the Podling MAY choose to distribute approved releases through
  other channels like the central Maven repository." [7]

However, I'd like to publish GRDDL artifacts in the Maven repo,
as well as all the other Jena artifacts [8].

These are also relevant:

 "Besides, we discourage putting release repository/pluginRepository
  in your POM. In ideal conditions, all your dependencies should
  be already in central and central repository is self-contained.
  Otherwise people's build might break because of missing dependencies.
  If some of your dependencies are not in central, please upload them
  using our 3rd-party artifacts bundle upload service." [9] via [10]

 "While most projects understand the importance of publishing artifacts
  to Central, there are still a few projects out there that don't have
  the same appreciation. When a project refuses to upload artifacts to
  Central, for whatever reason, we encourage people to submit artifact
  bundles to Central themselves.
  Sonatype is replacing this process with a self-serve approach. If you
  want to get a specific library into the Central repository, all you
  need to do is sign up for an account on https://issues.sonatype.org/,
  create an artifact bundle, and upload it to a staging repository.
  Sonatype will perform some due diligence to make sure that the
  artifact has a license compatible with unrestricted distribution,
  and we will then promote the uploaded artifacts to the Central
  Maven repository." [11]

You can include me with the people who do appreciate finding artifacts in
the Maven Central repository (no matter how they are produced: Maven, Ant+Ivy,
etc.).

Any help/suggestion is more than welcome,
Paolo

  [1] http://saxon.sourceforge.net/
  [2] http://sourceforge.net/projects/nekohtml/
  [3] http://browserlaunch2.sourceforge.net/
  [4] http://xml.apache.org/commons/
  [5] http://repo1.maven.org/maven2/nekohtml/nekohtml/0.9.5/
  [6] http://repo1.maven.org/maven2/xml-resolver/xml-resolver/1.2/
  [7] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
  [8] http://repo2.maven.org/maven2/com/hp/hpl/jena/
  [9] https://docs.sonatype.org/display/Repository/Central+Sync+Requirements
 [10] http://www.apache.org/dev/publishing-maven-artifacts.html
 [11] 
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Paolo Castagna]

Jeremy Carroll wrote:
The question about whether Apache would like to rethink our earlier 
legal advice to require click through license agreement before executing 
untrusted code in a sandbox should probably go to legal-discuss@ mailing 
list, - at what point in the process should I initiate that discussion?


(good idea)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Paolo Castagna]

Jeremy Carroll wrote:

On 11/12/2010 11:51 AM, Paolo Castagna wrote:


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


BrowserLauncher2 could be removed in favor of a much simpler approach
(i.e. write it in a file!).


That is actually superseded by a Java6 facility, so I should do a small 
piece of recoding and remove the dependency


+1

(and, if I can help, let me know.)

Of course, it would be even easier/less work, to remove the click
through altogether (this is probably my favorite option).


What other Apache projects do in a similar situation (i.e. you want
to warn the user about some potential security issues and therefore
you ask the user to actively agree, press a button, etc. to make sure
the user reads it (I know, I know...))?


The GRDDL component runs XSLT from the Web, in a sandbox.
The HP lawyer who advised, understanding the risks of running 3rd party 
code, wanted an explicit user action to agree to the BSD license terms, 
to have a firmer leg to stand on if the the 3rd party code proved 
malicious, and the sandbox inadequate.

(The browser launcher is used only for the click through agreement to BSD)


I was not able to find a single Apache project which requires a click
through to 'ensure' users agree to the license.

Paolo

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] OODT Graduation to TLP

[Cameron Goodale]

+1 non-binding

Best Regards,

Cameron

On Fri, Nov 12, 2010 at 10:40 AM, Ramirez, Paul M (388J) <
paul.m.rami...@jpl.nasa.gov> wrote:

> +1 (non binding) for making OODT a TLP.
>
> Thanks,
> Paul
>
> On Nov 11, 2010, at 7:18 AM, Mattmann, Chris A (388J) wrote:
>
> > Hi IPMC'ers and the rest of the Incubator community,
> >
> > The OODT community has been discussing graduation to TLP [1]. There is
> > overwhelming consensus in the community (all +1 VOTEs including those
> from
> > our mentors) that we've achieved what's required here in the Incubator,
> and
> > so we'd like to put forth the following board resolution for the next
> Board
> > meeting to promote OODT to an Apache TLP and graduate from the Incubator.
> >
> > Please VOTE on the below resolution for promoting OODT to an Apache TLP
> and
> > graduating from the Incubator. The VOTE is open for 72 hrs.
> >
> > [ ] +1 Accept OODT's graduation from the Incubator
> > [ ] +0 Don't care.
> > [ ] -1 Don't accept OODT's graduation from the Incubator because...
> >
> > =
> >  Establish the Apache OODT Project
> >
> >   WHEREAS, the Board of Directors deems it to be in the best
> >   interests of the Foundation and consistent with the
> >   Foundation's purpose to establish a Project Management
> >   Committee charged with the creation and maintenance of
> >   open-source software related to the construction of scientific,
> >  data management systems for distribution at no charge to the public.
> >
> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >   Committee (PMC), to be known as the "Apache OODT Project",
> >   be and hereby is established pursuant to Bylaws of the
> >   Foundation; and be it further
> >
> >   RESOLVED, that the Apache OODT Project be and hereby is
> >   responsible for the creation and maintenance of software
> >   related to the construction of scientific, data management
> >  systems; and be it further
> >
> >   RESOLVED, that the office of "Vice President, Apache OODT" be
> >   and hereby is created, the person holding such office to
> >   serve at the direction of the Board of Directors as the chair
> >   of the Apache OODT Project, and to have primary responsibility
> >   for management of the projects within the scope of
> >   responsibility of the Apache OODT Project; and be it further
> >
> >   RESOLVED, that the persons listed immediately below be and
> >   hereby are appointed to serve as the initial members of the
> >   Apache OODT Project:
> >
> >  * Andrew Hart (ah...@apache.org)
> >  * Brian Foster (bfos...@apache.org)
> >  * Cameron Goodale (good...@apache.org)
> >   * Chris A. Mattmann (mattm...@apache.org)
> >  * Dan Crichton (crich...@apache.org)
> >   * David Kale (davek...@apache.org)
> >  * David Woollard (wooll...@apache.org)
> >  * Ian Holsman (i...@apache.org)
> >  * Joshua Garcia (joshu...@apache.org)
> >  * Justin Erenkrantz (jerenkra...@apache.org)
> >  * Paul Ramirez (prami...@apache.org)
> >  * Sean Hardman (shard...@apache.org)
> >  * Sean McCleese (smccl...@apache.org)
> >  * Sean Kelly (ke...@apache.org)
> >
> >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris A. Mattmann
> >   be appointed to the office of Vice President, Apache OODT, to
> >   serve in accordance with and subject to the direction of the
> >   Board of Directors and the Bylaws of the Foundation until
> >   death, resignation, retirement, removal or disqualification,
> >   or until a successor is appointed; and be it further
> >
> >   RESOLVED, that the Apache OODT Project be and hereby
> >   is tasked with the migration and rationalization of the Apache
> >   Incubator OODT sub-project; and be it further
> >
> >   RESOLVED, that all responsibilities pertaining to the Apache
> >   Incubator OODT sub-project encumbered upon the
> >   Apache Incubator Project are hereafter discharged.
> > =
> >
> > Here's my +1 (binding).
> >
> > Cheers,
> > Chris
> >
> > ++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.mattm...@jpl.nasa.gov
> > WWW:   http://sunset.usc.edu/~mattmann/
> > ++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++
> >
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 

Sent from a Tin Ca

Re: [Proposal] Accept Jena into the Incubator

[Jeremy Carroll]

On 11/12/2010 6:05 PM, Benson Margulies wrote:

CyberNeko and TagSoup both have acceptable licenses. Some people
prefer TagSoup because it does not require Xerces.

Have you read http://www.apache.org/legal/resolved.html?


No I hadn't. That is very useful.

A first reaction, concerning the GRDDL dependencies, is:
1) BrowserLauncher needs to go - I will make the code changes
2) Saxon dependency is a B
3) Cyberneko is fine - Jena already has dependencies on Xerces

The question about whether Apache would like to rethink our earlier 
legal advice to require click through license agreement before executing 
untrusted code in a sandbox should probably go to legal-discuss@ mailing 
list, - at what point in the process should I initiate that discussion?


Jeremy



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Benson Margulies]

CyberNeko and TagSoup both have acceptable licenses. Some people
prefer TagSoup because it does not require Xerces.

Have you read http://www.apache.org/legal/resolved.html?


On Fri, Nov 12, 2010 at 8:50 PM, Jeremy Carroll  wrote:
> On 11/12/2010 5:47 PM, Benson Margulies wrote:
>>
>> CyberNeko is at least class B, since Tika uses it.
>>
> The actual requirement is for a parser that makes a reasonable job of HTML
> in the wild, and implements SAX2
>
> No particular reason for CyberNeko but it met those requirements, works, and
> met our previous legal requirements
>
> Jeremy
>
>
> -
> 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

Re: [Proposal] Accept Jena into the Incubator

[Jeremy Carroll]

On 11/12/2010 5:47 PM, Benson Margulies wrote:

CyberNeko is at least class B, since Tika uses it.

The actual requirement is for a parser that makes a reasonable job of 
HTML in the wild, and implements SAX2


No particular reason for CyberNeko but it met those requirements, works, 
and met our previous legal requirements


Jeremy


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Benson Margulies]

CyberNeko is at least class B, since Tika uses it.

On Fri, Nov 12, 2010 at 8:45 PM, Jeremy Carroll  wrote:
> On 11/12/2010 11:51 AM, Paolo Castagna wrote:
>>
>> Also (from the JenaProposal):
>>
>> "The Jena GRDDL Reader has some additional dependencies:
>> http://jena.sourceforge.net/grddl/license.html";
>>
>> BrowserLauncher2 could be removed in favor of a much simpler approach
>> (i.e. write it in a file!).
>
> That is actually superseded by a Java6 facility, so I should do a small
> piece of recoding and remove the dependency
>
>>
>> What other Apache projects do in a similar situation (i.e. you want
>> to warn the user about some potential security issues and therefore
>> you ask the user to actively agree, press a button, etc. to make sure
>> the user reads it (I know, I know...))?
>
> The GRDDL component runs XSLT from the Web, in a sandbox.
> The HP lawyer who advised, understanding the risks of running 3rd party
> code, wanted an explicit user action to agree to the BSD license terms, to
> have a firmer leg to stand on if the the 3rd party code proved malicious,
> and the sandbox inadequate.
> (The browser launcher is used only for the click through agreement to BSD)
>
>>
>> Can someone comment/advise in relation to these two?
>>
>>  - http://www.mozilla.org/MPL/MPL-1.0.html (i.e. Saxon)
>
> I noticed some other apache project with dependency on Saxon. Jena GRDDL
> Reader uses it for XSLT2 support.
>
>>  - http://jena.sourceforge.net/grddl/neko-LICENSE.txt (i.e. CyberNeko
>>   HTML Parser)
>
> which started life in Apache I believe
>
> Jeremy
>
>
> -
> 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

Re: [Proposal] Accept Jena into the Incubator

[Jeremy Carroll]

On 11/12/2010 11:51 AM, Paolo Castagna wrote:


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


BrowserLauncher2 could be removed in favor of a much simpler approach
(i.e. write it in a file!).


That is actually superseded by a Java6 facility, so I should do a small 
piece of recoding and remove the dependency




What other Apache projects do in a similar situation (i.e. you want
to warn the user about some potential security issues and therefore
you ask the user to actively agree, press a button, etc. to make sure
the user reads it (I know, I know...))?


The GRDDL component runs XSLT from the Web, in a sandbox.
The HP lawyer who advised, understanding the risks of running 3rd party 
code, wanted an explicit user action to agree to the BSD license terms, 
to have a firmer leg to stand on if the the 3rd party code proved 
malicious, and the sandbox inadequate.

(The browser launcher is used only for the click through agreement to BSD)



Can someone comment/advise in relation to these two?

 - http://www.mozilla.org/MPL/MPL-1.0.html (i.e. Saxon)


I noticed some other apache project with dependency on Saxon. Jena GRDDL 
Reader uses it for XSLT2 support.



 - http://jena.sourceforge.net/grddl/neko-LICENSE.txt (i.e. CyberNeko
   HTML Parser)


which started life in Apache I believe

Jeremy


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Whirr version 0.2.0-incubating

[Doug Cutting]

+1 Checksums & sigs are correct.  Licensing looks good.

Doug

On 11/10/2010 08:59 AM, Patrick Hunt wrote:

This is the second incubator release for Apache Whirr, version
0.2.0-incubating.

PPMC release vote thread:
http://markmail.org/message/kdfnohhod6wdrqaz

The issues fixed for 0.2.0-incubating
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230&styleName=Html&version=12315339

Source and binary files:
http://people.apache.org/~phunt/whirr-0.2.0-candidate-0/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachewhirr-032

The tag to be voted upon:
http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.2.0-incubating

The vote is open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
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

Re: [VOTE] Accept Stanbol for incubation

[Isabel Drost]

+1

On 12.11.2010 Mattmann, Chris A (388J) wrote:
> +1...binding.
> 
> Cheers,
> Chris
> 
> 
> On 11/12/10 9:01 AM, "Sander W G van der Waal"
>  wrote:
> 
> +1 (non-binding)
> 
> Sander
> 
> > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> > Sent: 10 November 2010 15:11
> > To: Incubator General
> > Subject: [VOTE] Accept Stanbol for incubation
> > 
> > Hi,
> > 
> > I think we're ready to vote on the
> > http://wiki.apache.org/incubator/StanbolProposal now, copy included
> > below.
> > 
> > This is TPFKAF - The Project Formerly Known As FOO.
> > 
> > Please cast your votes:
> > 
> > [ ] +1 Accept Stanbol for incubation
> > [ ] +0 Don't care
> > [ ] -1 Reject for the following reason:
> > 
> > The vote is open for at least 72 hours.
> > 
> > Thanks!
> > -Bertrand
> > 
> > 
> > = Apache Stanbol incubation proposal =
> > 
> > == Abstract ==
> > Apache Stanbol is a modular software stack and reusable set of
> > components for semantic content management.
> > 
> > == Proposal ==
> > Stanbol components are meant to be accessed over RESTful interfaces to
> > provide semantic services for content management. The current code is
> > written in Java and based on the OSGi modularization framework, but
> > other server-side languages might be used as well.
> > 
> > Applications include extending existing content management systems
> > with (internal or external) semantic services, and creating new types
> > of content management systems with semantics at their core.
> > 
> > The architecture of the current (alpha-level) code consists of four layers:
> >  * Persistence: services that store (or cache) semantic information
> > 
> > and make it searchable
> > 
> >  * Lifting: services that add semantic information to "non-semantic"
> > 
> > pieces of content
> > 
> >  * Knowledge models and reasoning: services that enhance the semantic
> > 
> > information
> > 
> >  * Interaction: intelligent user interface management and generation
> > 
> > == Background ==
> > Stanbol comes out of the IKS project (Interactive Knowledge Stack,
> > http://iks-project.eu/), a research project funded by the European
> > Community (EC) which aims to create a semantic content management
> > software stack.
> > 
> > One of the goals of IKS is for its software to survive the 4-year
> > funding period of the EC, which ends in 2012.
> > 
> > Developing its code in the open at the Apache Software Foundation, and
> > growing a community before IKS funding runs out, is the best way to
> > ensure the sustainability of the Stanbol software.
> > 
> > For more background information, some articles and tutorials on FISE,
> > which was the first usable IKS module, can be found in the "FISE
> > links" section of http://wiki.iks-project.eu/index.php/FISE
> > 
> > == Rationale ==
> > Content Management Systems (CMS) can benefit from semantic add-ons in
> > a number of ways, including more intelligent linking, automatic or
> > semi-automatic tagging of content, enhanced user interactions based on
> > intelligent and dynamically adaptable user scenario modeling, etc.
> > 
> > However, many CMS vendors and developers are not aware of or skilled
> > enough in semantic technologies to make effective use of them.
> > Research in semantic technologies often happens in academic circles
> > which might not make their findings available in a way that's easily
> > consumable by today's CMS vendors and developers.
> > 
> > Some big companies are using semantic technologies behind the scenes
> > to provide powerful services, but that technology is usually not
> > accessible to smaller vendors.
> > 
> > Stanbol aims to bridge these gaps by providing CMS vendors and
> > developers with easy to integrate semantic components that add value
> > to their offerings.
> > 
> > At the same time, more experimental advanced semantic applications
> > will be built on the Stanbol stack, with the medium-term goal of
> > enabling pure semantic-based content management and other
> > applications.
> > 
> > == Initial Goals ==
> > 
> >  * Import the existing IKS code.
> >  * Clean up as needed to take advantage of Apache infrastructure
> > 
> > (Hudson continuous builds, etc.)
> > 
> >  * Replace up any dependencies that do not fulfill Apache licensing
> > 
> > criteria.
> > 
> >  * Create the Stanbol website and migrate IKS website/wiki information
> > 
> > to it as needed.
> > 
> >  * Make a first release and publicize it to start growing the community.
> > 
> > == Current Status ==
> > === Meritocracy ===
> > As IKS is an EC research project with funding, it does not formally
> > operate as a meritocracy.
> > 
> > However, due to the open source way of working adopted by the
> > consortium, an informal meritocracy has emerged within IKS.
> > 
> > We estimate that adapting to the ASF's meritocratic way of working
> > will be easy for the initial set of Stanbol committers, as the
> > differences to the current way of working are not dramatic.
> > 
> > === Community ===
> > T

Re: [Proposal] Accept Jena into the Incubator

[Paolo Castagna]

Andy Seaborne wrote:



On 12/11/10 08:40, Nick Kew wrote:


On 8 Nov 2010, at 23:36, Ross Gardler wrote:

I am pleased to offer, for your consideration, the following proposal 
to accept Jena, a semantic web framework into the incubator. The text 
of the proposal is copied here for your convenience and can be found 
at http://wiki.apache.org/incubator/JenaProposal


Strong +1 in principle.  I'd offer to mentor, but I see you now have 
plenty.


One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?  The openjena.org page referenced
relies on references that are broken links!


Grr ... rotting links ...

Where?  I'll fix them ASAP.  Checking:

http://openjena.org/Licenses/index.html


Also (from the JenaProposal):

"The Jena GRDDL Reader has some additional dependencies: 
http://jena.sourceforge.net/grddl/license.html";


BrowserLauncher2 could be removed in favor of a much simpler approach
(i.e. write it in a file!).

What other Apache projects do in a similar situation (i.e. you want
to warn the user about some potential security issues and therefore
you ask the user to actively agree, press a button, etc. to make sure
the user reads it (I know, I know...))?

Can someone comment/advise in relation to these two?

 - http://www.mozilla.org/MPL/MPL-1.0.html (i.e. Saxon)
 - http://jena.sourceforge.net/grddl/neko-LICENSE.txt (i.e. CyberNeko
   HTML Parser)

Thanks,
Paolo



I found the links for JUnit and WoodSToX have rotted.  Anything else 
gone bad?


Andy

-
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

Re: [Proposal] Accept Jena into the Incubator

[Tim Williams]

+1

On Fri, Nov 12, 2010 at 12:00 PM, Sander W G van der Waal
 wrote:
> +1 (non-binding)
>
> Sander
>
>> From: Ross Gardler [mailto:rgard...@apache.org]
>> Sent: 08 November 2010 23:37
>> To: general@incubator.apache.org
>> Subject: [Proposal] Accept Jena into the Incubator
>>
>> I am pleased to offer, for your consideration, the following proposal to
>> accept Jena, a semantic web framework into the incubator. The text of
>> the proposal is copied here for your convenience and can be found at
>> http://wiki.apache.org/incubator/JenaProposal
>>
>> We currently have two mentors so we're looking for at least one more.
>>
>> Note that there is already an overlapping discussion about interaction
>> between this and other semantic web projects in the incubator. As
>> champion of this proposal I have recommended that the Jena team
>> participate in this discussion. I'm not able to speak for the Jena
>> committers, but I am keen to see *appropriate* sharing of code between
>> projects.
>>
>> However, I don't believe that this should be forced upon the three
>> projects as part of their incubation. Such collaboration should emerge
>> through community engagement, with mentor guidance, rather than through
>> incubator conditions of entry or graduation.
>>
>> Comments and volunteers welcome.
>>
>> Now for the proposal:
>>
>> = Jena, a Semantic Web Framework =
>> == Abstract ==
>> Jena is a semantic web framework for Java, based on W3C standards.
>>
>> == Proposal ==
>> Jena provides a semantic web framework in Java that implements the key
>> W3C recommendations for the core semantic web technologies of RDF and
>> SPARQL.  Jena is a number of components and modules built on this core
>> system.  It currently includes:
>>
>>   * an API for working with RDF
>>   * Parsers and writers for the RDF formats (RDF/XML, Turtle, N-triples,
>> NQuads, TriG)
>>   * an implementation of SPARQL, the W3C standard RDF query language
>>   * multiple storage systems for RDF data including in-memory,
>> file-backed, in SQL databases and in custom scalable storage systems
>>   * an API for manipulation of OWL
>>   * a rule-based inference engine
>>   * an implementation of GRDDL for extraction of RDF from XML formats
>>   * a standards compliant IRI library.
>>
>> The project includes facilities based around this core to encourage the
>>   creation of components and contributions both as part of Jena and also
>>   as companion open source activities.
>>
>> This proposal includes the main components of Jena: the main Jena
>> download, ARQ, GRDDL, SDB, TDB, the IRI  library and Joseki.  Other
>> components may be contributed later - we're  just starting with the main
>> part of Jena for now.
>>
>> == Background ==
>> The W3C recommendations provide detailed specifications and it is
>> important to follow these standards so that independently built
>> applications can exchange data over the web.  Jena provides high quality
>>   Java implementations of RDF input/output and storage so that
>> application  writers can concentrate on the application, not the
>> low-level details.
>>
>> W3C Semantic Web: http://www.w3.org/standards/semanticweb/
>>
>> Jena has been on !SourceForge since 2001.
>> http://sourceforge.net/projects/jena/
>>
>> == Rationale ==
>> The open source project was originally created as part of a research
>> activity in HPLabs.  In building new systems, the researchers identified
>>   the value of a common platform that dealt with the low level details
>> of  the standards.  This lead to engagement with the standards process
>> and  the creation of a framework that provided a library to deal with
>> the  details of semantic web standards.  This work was released as Jena.
>> The  developers have contributed implementation experience back to the
>> working groups.
>>
>> None of the contributors now work for HP.  Providing a uniform
>> contributor and licensing framework assists commercial use of Jena.
>>
>> == Current Status ==
>> Jena is already an established project with a large user base in
>> industry and academia.  It currently uses a BSD-style three-clause
>> license with a number of contributing copyright holders. Support is
>> primarily provided via the jena-...@groups.yahoo.com mailing list. The
>> majority of the team was employed in HPLabs, and HP holds the majority
>> of the copyright over the code - there are contributions from non-HP
>> companies.  HP decided to close the research group as of October 2009
>> and the people from HPLabs connected with the project have moved on to
>> several different semantic web companies.
>>
>> This change does not immediately affect Jena because the people who were
>>   in HP still remain active contributors to Jena.  The project continues
>> to be supported and actively enhanced.  There is now the  opportunity to
>> become an open source project without a single large  organisation
>> involved.
>>
>> === Meritocracy ===
>> The Jena team has always been self-determining; there h

Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3

[Greg Reddin]

On Thu, Nov 11, 2010 at 9:47 PM, Mattmann, Chris A (388J)
 wrote:
> [ ] +1 Release the packages as Apache SIS 0.1-incubating.
>
> [ ] -1 Do not release the packages because...

+1.

Thanks,
Greg

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] OODT Graduation to TLP

[Ramirez, Paul M (388J)]

+1 (non binding) for making OODT a TLP.

Thanks,
Paul

On Nov 11, 2010, at 7:18 AM, Mattmann, Chris A (388J) wrote:

> Hi IPMC'ers and the rest of the Incubator community,
> 
> The OODT community has been discussing graduation to TLP [1]. There is
> overwhelming consensus in the community (all +1 VOTEs including those from
> our mentors) that we've achieved what's required here in the Incubator, and
> so we'd like to put forth the following board resolution for the next Board
> meeting to promote OODT to an Apache TLP and graduate from the Incubator.
> 
> Please VOTE on the below resolution for promoting OODT to an Apache TLP and
> graduating from the Incubator. The VOTE is open for 72 hrs.
> 
> [ ] +1 Accept OODT's graduation from the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept OODT's graduation from the Incubator because...
> 
> =
>  Establish the Apache OODT Project
> 
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software related to the construction of scientific,
>  data management systems for distribution at no charge to the public.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache OODT Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache OODT Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to the construction of scientific, data management
>  systems; and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache OODT" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache OODT Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache OODT Project; and be it further
> 
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache OODT Project:
> 
>  * Andrew Hart (ah...@apache.org)
>  * Brian Foster (bfos...@apache.org)
>  * Cameron Goodale (good...@apache.org)
>   * Chris A. Mattmann (mattm...@apache.org)
>  * Dan Crichton (crich...@apache.org)
>   * David Kale (davek...@apache.org)
>  * David Woollard (wooll...@apache.org)
>  * Ian Holsman (i...@apache.org)
>  * Joshua Garcia (joshu...@apache.org)
>  * Justin Erenkrantz (jerenkra...@apache.org)
>  * Paul Ramirez (prami...@apache.org)
>  * Sean Hardman (shard...@apache.org)
>  * Sean McCleese (smccl...@apache.org)
>  * Sean Kelly (ke...@apache.org)
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris A. Mattmann
>   be appointed to the office of Vice President, Apache OODT, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
> 
>   RESOLVED, that the Apache OODT Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator OODT sub-project; and be it further
> 
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator OODT sub-project encumbered upon the
>   Apache Incubator Project are hereafter discharged.
> =
> 
> Here's my +1 (binding).
> 
> Cheers,
> Chris
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3

[patrick o'leary]

And also great work Chris !

On Fri, Nov 12, 2010 at 10:16 AM, patrick o'leary  wrote:

> Still looks good to me, but thanks for spotting the licensing stuff
>
> +1
>
>
> On Fri, Nov 12, 2010 at 10:15 AM, Ramirez, Paul M (388J) <
> paul.m.rami...@jpl.nasa.gov> wrote:
>
>> +1,
>>
>> --Paul Ramirez
>>
>> On Nov 11, 2010, at 7:47 PM, Mattmann, Chris A (388J) wrote:
>>
>> > Hi Folks,
>> >
>> > I have posted a 3rd candidate for the Apache SIS 0.1-incubating release.
>> The
>> > source code is at:
>> >
>> > http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc3/
>> >
>> > This release addresses the following comments from IPMC members during
>> the
>> > RC #2 VOTE:
>> >
>> > From Ant Elder:
>> >
>> > In NOTICE file
>> >
>> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt
>> > everything after the line "The Apache Software Foundation
>> > (http://www.apache.org/) ." shouldn't be
>> there.
>> >
>> > In the LICENSE file
>> >
>> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.tx
>> > t everything including and after the line "APACHE TIKA SUBCOMPONENTS"
>> > shouldn't be there (should it? what is using those extra licenses?).
>> >
>> >
>> > See the included CHANGES.txt file for details on release contents and
>> latest
>> > changes. The release was made using the Maven2 release plugin, according
>> to
>> > Jukka Zitting's notes from Tika-ville:
>> >
>> > http://tinyurl.com/yz2cqls
>> >
>> > Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177
>> [1]
>> > to make this happen for our next release.
>> >
>> > See the included README.txt file for an example of how to use Apache SIS
>> in
>> > a Tomcat environment and how to run the demo.
>> >
>> > This plugin creates a Apache SIS 0.1-incubating tag at:
>> >
>> > http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/
>> >
>> > Please vote on releasing these packages as Apache SIS 0.1-incubating.
>> The
>> > vote is open for the next 72 hours. Only votes from Incubator PMC are
>> > binding, but everyone is welcome to check the release candidate and
>> voice
>> > their approval or disapproval. The vote passes if at least three binding
>> +1
>> > votes are cast.
>> >
>> > [ ] +1 Release the packages as Apache SIS 0.1-incubating.
>> >
>> > [ ] -1 Do not release the packages because...
>> >
>> > Thanks!
>> >
>> > Cheers,
>> > Chris
>> >
>> > P.S. Here's my +1.
>> >
>> > [1] https://issues.apache.org/jira/browse/INFRA-3177
>> >
>> > ++
>> > Chris Mattmann, Ph.D.
>> > Senior Computer Scientist
>> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> > Office: 171-266B, Mailstop: 171-246
>> > Email: chris.mattm...@jpl.nasa.gov
>> > WWW:   http://sunset.usc.edu/~mattmann/
>> > ++
>> > Adjunct Assistant Professor, Computer Science Department
>> > University of Southern California, Los Angeles, CA 90089 USA
>> > ++
>> >
>> >
>> >
>> >
>> > -
>> > 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
>>
>>
>

Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3

[patrick o'leary]

Still looks good to me, but thanks for spotting the licensing stuff

+1

On Fri, Nov 12, 2010 at 10:15 AM, Ramirez, Paul M (388J) <
paul.m.rami...@jpl.nasa.gov> wrote:

> +1,
>
> --Paul Ramirez
>
> On Nov 11, 2010, at 7:47 PM, Mattmann, Chris A (388J) wrote:
>
> > Hi Folks,
> >
> > I have posted a 3rd candidate for the Apache SIS 0.1-incubating release.
> The
> > source code is at:
> >
> > http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc3/
> >
> > This release addresses the following comments from IPMC members during
> the
> > RC #2 VOTE:
> >
> > From Ant Elder:
> >
> > In NOTICE file
> >
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt
> > everything after the line "The Apache Software Foundation
> > (http://www.apache.org/) ." shouldn't be
> there.
> >
> > In the LICENSE file
> >
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.tx
> > t everything including and after the line "APACHE TIKA SUBCOMPONENTS"
> > shouldn't be there (should it? what is using those extra licenses?).
> >
> >
> > See the included CHANGES.txt file for details on release contents and
> latest
> > changes. The release was made using the Maven2 release plugin, according
> to
> > Jukka Zitting's notes from Tika-ville:
> >
> > http://tinyurl.com/yz2cqls
> >
> > Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177
> [1]
> > to make this happen for our next release.
> >
> > See the included README.txt file for an example of how to use Apache SIS
> in
> > a Tomcat environment and how to run the demo.
> >
> > This plugin creates a Apache SIS 0.1-incubating tag at:
> >
> > http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/
> >
> > Please vote on releasing these packages as Apache SIS 0.1-incubating. The
> > vote is open for the next 72 hours. Only votes from Incubator PMC are
> > binding, but everyone is welcome to check the release candidate and voice
> > their approval or disapproval. The vote passes if at least three binding
> +1
> > votes are cast.
> >
> > [ ] +1 Release the packages as Apache SIS 0.1-incubating.
> >
> > [ ] -1 Do not release the packages because...
> >
> > Thanks!
> >
> > Cheers,
> > Chris
> >
> > P.S. Here's my +1.
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-3177
> >
> > ++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.mattm...@jpl.nasa.gov
> > WWW:   http://sunset.usc.edu/~mattmann/
> > ++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++
> >
> >
> >
> >
> > -
> > 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
>
>

Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3

[Ramirez, Paul M (388J)]

+1,

--Paul Ramirez

On Nov 11, 2010, at 7:47 PM, Mattmann, Chris A (388J) wrote:

> Hi Folks,
> 
> I have posted a 3rd candidate for the Apache SIS 0.1-incubating release. The
> source code is at:
> 
> http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc3/
> 
> This release addresses the following comments from IPMC members during the
> RC #2 VOTE:
> 
> From Ant Elder:
> 
> In NOTICE file 
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt
> everything after the line "The Apache Software Foundation
> (http://www.apache.org/)." shouldn't be there.
> 
> In the LICENSE file
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.tx
> t everything including and after the line "APACHE TIKA SUBCOMPONENTS"
> shouldn't be there (should it? what is using those extra licenses?).
> 
> 
> See the included CHANGES.txt file for details on release contents and latest
> changes. The release was made using the Maven2 release plugin, according to
> Jukka Zitting's notes from Tika-ville:
> 
> http://tinyurl.com/yz2cqls
> 
> Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177 [1]
> to make this happen for our next release.
> 
> See the included README.txt file for an example of how to use Apache SIS in
> a Tomcat environment and how to run the demo.
> 
> This plugin creates a Apache SIS 0.1-incubating tag at:
> 
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/
> 
> Please vote on releasing these packages as Apache SIS 0.1-incubating. The
> vote is open for the next 72 hours. Only votes from Incubator PMC are
> binding, but everyone is welcome to check the release candidate and voice
> their approval or disapproval. The vote passes if at least three binding +1
> votes are cast.
> 
> [ ] +1 Release the packages as Apache SIS 0.1-incubating.
> 
> [ ] -1 Do not release the packages because...
> 
> Thanks!
> 
> Cheers,
> Chris
> 
> P.S. Here's my +1.
> 
> [1] https://issues.apache.org/jira/browse/INFRA-3177
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> 
> 
> -
> 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

Re: [VOTE] Accept Stanbol for incubation

[Mattmann, Chris A (388J)]

+1...binding.

Cheers,
Chris


On 11/12/10 9:01 AM, "Sander W G van der Waal" 
 wrote:

+1 (non-binding)

Sander

> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> Sent: 10 November 2010 15:11
> To: Incubator General
> Subject: [VOTE] Accept Stanbol for incubation
>
> Hi,
>
> I think we're ready to vote on the
> http://wiki.apache.org/incubator/StanbolProposal now, copy included
> below.
>
> This is TPFKAF - The Project Formerly Known As FOO.
>
> Please cast your votes:
>
> [ ] +1 Accept Stanbol for incubation
> [ ] +0 Don't care
> [ ] -1 Reject for the following reason:
>
> The vote is open for at least 72 hours.
>
> Thanks!
> -Bertrand
>
>
> = Apache Stanbol incubation proposal =
>
> == Abstract ==
> Apache Stanbol is a modular software stack and reusable set of
> components for semantic content management.
>
> == Proposal ==
> Stanbol components are meant to be accessed over RESTful interfaces to
> provide semantic services for content management. The current code is
> written in Java and based on the OSGi modularization framework, but
> other server-side languages might be used as well.
>
> Applications include extending existing content management systems
> with (internal or external) semantic services, and creating new types
> of content management systems with semantics at their core.
>
> The architecture of the current (alpha-level) code consists of four layers:
>  * Persistence: services that store (or cache) semantic information
> and make it searchable
>  * Lifting: services that add semantic information to "non-semantic"
> pieces of content
>  * Knowledge models and reasoning: services that enhance the semantic
> information
>  * Interaction: intelligent user interface management and generation
>
> == Background ==
> Stanbol comes out of the IKS project (Interactive Knowledge Stack,
> http://iks-project.eu/), a research project funded by the European
> Community (EC) which aims to create a semantic content management
> software stack.
>
> One of the goals of IKS is for its software to survive the 4-year
> funding period of the EC, which ends in 2012.
>
> Developing its code in the open at the Apache Software Foundation, and
> growing a community before IKS funding runs out, is the best way to
> ensure the sustainability of the Stanbol software.
>
> For more background information, some articles and tutorials on FISE,
> which was the first usable IKS module, can be found in the "FISE
> links" section of http://wiki.iks-project.eu/index.php/FISE
>
> == Rationale ==
> Content Management Systems (CMS) can benefit from semantic add-ons in
> a number of ways, including more intelligent linking, automatic or
> semi-automatic tagging of content, enhanced user interactions based on
> intelligent and dynamically adaptable user scenario modeling, etc.
>
> However, many CMS vendors and developers are not aware of or skilled
> enough in semantic technologies to make effective use of them.
> Research in semantic technologies often happens in academic circles
> which might not make their findings available in a way that's easily
> consumable by today's CMS vendors and developers.
>
> Some big companies are using semantic technologies behind the scenes
> to provide powerful services, but that technology is usually not
> accessible to smaller vendors.
>
> Stanbol aims to bridge these gaps by providing CMS vendors and
> developers with easy to integrate semantic components that add value
> to their offerings.
>
> At the same time, more experimental advanced semantic applications
> will be built on the Stanbol stack, with the medium-term goal of
> enabling pure semantic-based content management and other
> applications.
>
> == Initial Goals ==
>  * Import the existing IKS code.
>  * Clean up as needed to take advantage of Apache infrastructure
> (Hudson continuous builds, etc.)
>  * Replace up any dependencies that do not fulfill Apache licensing
> criteria.
>  * Create the Stanbol website and migrate IKS website/wiki information
> to it as needed.
>  * Make a first release and publicize it to start growing the community.
>
> == Current Status ==
> === Meritocracy ===
> As IKS is an EC research project with funding, it does not formally
> operate as a meritocracy.
>
> However, due to the open source way of working adopted by the
> consortium, an informal meritocracy has emerged within IKS.
>
> We estimate that adapting to the ASF's meritocratic way of working
> will be easy for the initial set of Stanbol committers, as the
> differences to the current way of working are not dramatic.
>
> === Community ===
> The IKS project plan includes an important effort to build a community
> around the software that it produces. Several community workshops have
> already taken place, attended by more than 40 European CMS developers
> and vendors.
>
> See http://wiki.iks-project.eu/index.php/Workshops for more info.
>
> A community is emerging around IKS, and moving to the Apache project
> governance model should h

RE: [VOTE] Accept Stanbol for incubation

[Sander W G van der Waal]

+1 (non-binding)

Sander

> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> Sent: 10 November 2010 15:11
> To: Incubator General
> Subject: [VOTE] Accept Stanbol for incubation
> 
> Hi,
> 
> I think we're ready to vote on the
> http://wiki.apache.org/incubator/StanbolProposal now, copy included
> below.
> 
> This is TPFKAF - The Project Formerly Known As FOO.
> 
> Please cast your votes:
> 
> [ ] +1 Accept Stanbol for incubation
> [ ] +0 Don't care
> [ ] -1 Reject for the following reason:
> 
> The vote is open for at least 72 hours.
> 
> Thanks!
> -Bertrand
> 
> 
> = Apache Stanbol incubation proposal =
> 
> == Abstract ==
> Apache Stanbol is a modular software stack and reusable set of
> components for semantic content management.
> 
> == Proposal ==
> Stanbol components are meant to be accessed over RESTful interfaces to
> provide semantic services for content management. The current code is
> written in Java and based on the OSGi modularization framework, but
> other server-side languages might be used as well.
> 
> Applications include extending existing content management systems
> with (internal or external) semantic services, and creating new types
> of content management systems with semantics at their core.
> 
> The architecture of the current (alpha-level) code consists of four layers:
>  * Persistence: services that store (or cache) semantic information
> and make it searchable
>  * Lifting: services that add semantic information to “non-semantic”
> pieces of content
>  * Knowledge models and reasoning: services that enhance the semantic
> information
>  * Interaction: intelligent user interface management and generation
> 
> == Background ==
> Stanbol comes out of the IKS project (Interactive Knowledge Stack,
> http://iks-project.eu/), a research project funded by the European
> Community (EC) which aims to create a semantic content management
> software stack.
> 
> One of the goals of IKS is for its software to survive the 4-year
> funding period of the EC, which ends in 2012.
> 
> Developing its code in the open at the Apache Software Foundation, and
> growing a community before IKS funding runs out, is the best way to
> ensure the sustainability of the Stanbol software.
> 
> For more background information, some articles and tutorials on FISE,
> which was the first usable IKS module, can be found in the “FISE
> links” section of http://wiki.iks-project.eu/index.php/FISE
> 
> == Rationale ==
> Content Management Systems (CMS) can benefit from semantic add-ons in
> a number of ways, including more intelligent linking, automatic or
> semi-automatic tagging of content, enhanced user interactions based on
> intelligent and dynamically adaptable user scenario modeling, etc.
> 
> However, many CMS vendors and developers are not aware of or skilled
> enough in semantic technologies to make effective use of them.
> Research in semantic technologies often happens in academic circles
> which might not make their findings available in a way that’s easily
> consumable by today’s CMS vendors and developers.
> 
> Some big companies are using semantic technologies behind the scenes
> to provide powerful services, but that technology is usually not
> accessible to smaller vendors.
> 
> Stanbol aims to bridge these gaps by providing CMS vendors and
> developers with easy to integrate semantic components that add value
> to their offerings.
> 
> At the same time, more experimental advanced semantic applications
> will be built on the Stanbol stack, with the medium-term goal of
> enabling pure semantic-based content management and other
> applications.
> 
> == Initial Goals ==
>  * Import the existing IKS code.
>  * Clean up as needed to take advantage of Apache infrastructure
> (Hudson continuous builds, etc.)
>  * Replace up any dependencies that do not fulfill Apache licensing
> criteria.
>  * Create the Stanbol website and migrate IKS website/wiki information
> to it as needed.
>  * Make a first release and publicize it to start growing the community.
> 
> == Current Status ==
> === Meritocracy ===
> As IKS is an EC research project with funding, it does not formally
> operate as a meritocracy.
> 
> However, due to the open source way of working adopted by the
> consortium, an informal meritocracy has emerged within IKS.
> 
> We estimate that adapting to the ASF’s meritocratic way of working
> will be easy for the initial set of Stanbol committers, as the
> differences to the current way of working are not dramatic.
> 
> === Community ===
> The IKS project plan includes an important effort to build a community
> around the software that it produces. Several community workshops have
> already taken place, attended by more than 40 European CMS developers
> and vendors.
> 
> See http://wiki.iks-project.eu/index.php/Workshops for more info.
> 
> A community is emerging around IKS, and moving to the Apache project
> governance model should help grow it - also by reassuring community
> members that t

RE: [Proposal] Accept Jena into the Incubator

[Sander W G van der Waal]

+1 (non-binding)

Sander

> From: Ross Gardler [mailto:rgard...@apache.org]
> Sent: 08 November 2010 23:37
> To: general@incubator.apache.org
> Subject: [Proposal] Accept Jena into the Incubator
> 
> I am pleased to offer, for your consideration, the following proposal to
> accept Jena, a semantic web framework into the incubator. The text of
> the proposal is copied here for your convenience and can be found at
> http://wiki.apache.org/incubator/JenaProposal
> 
> We currently have two mentors so we're looking for at least one more.
> 
> Note that there is already an overlapping discussion about interaction
> between this and other semantic web projects in the incubator. As
> champion of this proposal I have recommended that the Jena team
> participate in this discussion. I'm not able to speak for the Jena
> committers, but I am keen to see *appropriate* sharing of code between
> projects.
> 
> However, I don't believe that this should be forced upon the three
> projects as part of their incubation. Such collaboration should emerge
> through community engagement, with mentor guidance, rather than through
> incubator conditions of entry or graduation.
> 
> Comments and volunteers welcome.
> 
> Now for the proposal:
> 
> = Jena, a Semantic Web Framework =
> == Abstract ==
> Jena is a semantic web framework for Java, based on W3C standards.
> 
> == Proposal ==
> Jena provides a semantic web framework in Java that implements the key
> W3C recommendations for the core semantic web technologies of RDF and
> SPARQL.  Jena is a number of components and modules built on this core
> system.  It currently includes:
> 
>   * an API for working with RDF
>   * Parsers and writers for the RDF formats (RDF/XML, Turtle, N-triples,
> NQuads, TriG)
>   * an implementation of SPARQL, the W3C standard RDF query language
>   * multiple storage systems for RDF data including in-memory,
> file-backed, in SQL databases and in custom scalable storage systems
>   * an API for manipulation of OWL
>   * a rule-based inference engine
>   * an implementation of GRDDL for extraction of RDF from XML formats
>   * a standards compliant IRI library.
> 
> The project includes facilities based around this core to encourage the
>   creation of components and contributions both as part of Jena and also
>   as companion open source activities.
> 
> This proposal includes the main components of Jena: the main Jena
> download, ARQ, GRDDL, SDB, TDB, the IRI  library and Joseki.  Other
> components may be contributed later - we're  just starting with the main
> part of Jena for now.
> 
> == Background ==
> The W3C recommendations provide detailed specifications and it is
> important to follow these standards so that independently built
> applications can exchange data over the web.  Jena provides high quality
>   Java implementations of RDF input/output and storage so that
> application  writers can concentrate on the application, not the
> low-level details.
> 
> W3C Semantic Web: http://www.w3.org/standards/semanticweb/
> 
> Jena has been on !SourceForge since 2001.
> http://sourceforge.net/projects/jena/
> 
> == Rationale ==
> The open source project was originally created as part of a research
> activity in HPLabs.  In building new systems, the researchers identified
>   the value of a common platform that dealt with the low level details
> of  the standards.  This lead to engagement with the standards process
> and  the creation of a framework that provided a library to deal with
> the  details of semantic web standards.  This work was released as Jena.
> The  developers have contributed implementation experience back to the
> working groups.
> 
> None of the contributors now work for HP.  Providing a uniform
> contributor and licensing framework assists commercial use of Jena.
> 
> == Current Status ==
> Jena is already an established project with a large user base in
> industry and academia.  It currently uses a BSD-style three-clause
> license with a number of contributing copyright holders. Support is
> primarily provided via the jena-...@groups.yahoo.com mailing list. The
> majority of the team was employed in HPLabs, and HP holds the majority
> of the copyright over the code - there are contributions from non-HP
> companies.  HP decided to close the research group as of October 2009
> and the people from HPLabs connected with the project have moved on to
> several different semantic web companies.
> 
> This change does not immediately affect Jena because the people who were
>   in HP still remain active contributors to Jena.  The project continues
> to be supported and actively enhanced.  There is now the  opportunity to
> become an open source project without a single large  organisation
> involved.
> 
> === Meritocracy ===
> The Jena team has always been self-determining; there has not been a
> project manager in charge of the effort.  Instead, it has grown through
>   individuals contributing to the codebase as part of their research
>

Re: [DISCUSS] Poddling new committer process

[Justin Erenkrantz]

On Fri, Nov 12, 2010 at 12:20 AM, ant elder  wrote:
> I'd like to propose that the process for Incubator poddlings to make
> someone a new committer is simplified so that all that is needed are
> votes from poddling committers and that there is no longer any need
> for votes from Incubator PMC members or a separate Incubator PMC vote.

+1.

As Bertrand said, I'm ok with requiring at least one mentor voting and
notice sent to private@ *afterwards*.  -- justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Poddling new committer process

[Bertrand Delacretaz]

On Fri, Nov 12, 2010 at 4:41 PM, Glen Daniels  wrote:
> ...I also agree with Bertrand's point about notifying private@, and would be 
> OK
> with requiring a (single) mentor/IPMC vote to ensure that someone is paying
> attention... but it would be nice if we didn't need two

Ok, one mentor is enough, agreed.
-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Poddling new committer process

[Glen Daniels]

+1 from me.

I also agree with Bertrand's point about notifying private@, and would be OK
with requiring a (single) mentor/IPMC vote to ensure that someone is paying
attention... but it would be nice if we didn't need two.

--Glen

On 11/12/2010 3:20 AM, ant elder wrote:
> I'd like to propose that the process for Incubator poddlings to make
> someone a new committer is simplified so that all that is needed are
> votes from poddling committers and that there is no longer any need
> for votes from Incubator PMC members or a separate Incubator PMC vote.
> 
> As justification, this is the process that was in place some years ago
> and it worked fine like that, there is the "experiment" currently in
> place with some poddlings doing this which seems to be working ok, and
> the board has said they're ok with it.
> 
>...ant
> 
> -
> 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

Re: [DISCUSS] Poddling new committer process

[Mattmann, Chris A (388J)]

+1 from me...

Cheers,
Chris


On 11/12/10 12:20 AM, "ant elder"  wrote:

I'd like to propose that the process for Incubator poddlings to make
someone a new committer is simplified so that all that is needed are
votes from poddling committers and that there is no longer any need
for votes from Incubator PMC members or a separate Incubator PMC vote.

As justification, this is the process that was in place some years ago
and it worked fine like that, there is the "experiment" currently in
place with some poddlings doing this which seems to be working ok, and
the board has said they're ok with it.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3

[Kevan Miller]

+1. Source, sigs/checksums, build -- all look good.

Thanks Chris!

--kevan
On Nov 11, 2010, at 10:47 PM, Mattmann, Chris A (388J) wrote:

> Hi Folks,
> 
> I have posted a 3rd candidate for the Apache SIS 0.1-incubating release. The
> source code is at:
> 
> http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc3/
> 
> This release addresses the following comments from IPMC members during the
> RC #2 VOTE:
> 
> From Ant Elder:
> 
> In NOTICE file 
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt
> everything after the line "The Apache Software Foundation
> (http://www.apache.org/)." shouldn't be there.
> 
> In the LICENSE file
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.tx
> t everything including and after the line "APACHE TIKA SUBCOMPONENTS"
> shouldn't be there (should it? what is using those extra licenses?).
> 
> 
> See the included CHANGES.txt file for details on release contents and latest
> changes. The release was made using the Maven2 release plugin, according to
> Jukka Zitting's notes from Tika-ville:
> 
> http://tinyurl.com/yz2cqls
> 
> Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177 [1]
> to make this happen for our next release.
> 
> See the included README.txt file for an example of how to use Apache SIS in
> a Tomcat environment and how to run the demo.
> 
> This plugin creates a Apache SIS 0.1-incubating tag at:
> 
> http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/
> 
> Please vote on releasing these packages as Apache SIS 0.1-incubating. The
> vote is open for the next 72 hours. Only votes from Incubator PMC are
> binding, but everyone is welcome to check the release candidate and voice
> their approval or disapproval. The vote passes if at least three binding +1
> votes are cast.
> 
> [ ] +1 Release the packages as Apache SIS 0.1-incubating.
> 
> [ ] -1 Do not release the packages because...
> 
> Thanks!
> 
> Cheers,
> Chris
> 
> P.S. Here's my +1.
> 
> [1] https://issues.apache.org/jira/browse/INFRA-3177
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.mattm...@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> 
> 
> -
> 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

Re: [Proposal] Accept Jena into the Incubator

[Jeremy Carroll]

On 11/12/2010 3:28 AM, Ross Gardler wrote:

One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?



We have discussed this and the team believe they are licence 
compatible. They have undertaken to remove any licence 
incompatibilities during incubation if they have missed anything.


The team culture has been one that has been very aware of licensing 
issues, and we had regular legal advice when the project was in-house at HP.


Jeremy


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Ross Gardler]

On 12/11/2010 09:40, Nick Kew wrote:


On 8 Nov 2010, at 23:36, Ross Gardler wrote:


I am pleased to offer, for your consideration, the following proposal to accept 
Jena, a semantic web framework into the incubator. The text of the proposal is 
copied here for your convenience and can be found at 
http://wiki.apache.org/incubator/JenaProposal


Strong +1 in principle.  I'd offer to mentor, but I see you now have plenty.

One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?


We have discussed this and the team believe they are licence compatible. 
They have undertaken to remove any licence incompatibilities during 
incubation if they have missed anything.


Ross

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Poddling new committer process

[Bertrand Delacretaz]

Hi,

On Fri, Nov 12, 2010 at 9:20 AM, ant elder  wrote:
> I'd like to propose that the process for Incubator poddlings to make
> someone a new committer is simplified so that all that is needed are
> votes from poddling committers and that there is no longer any need
> for votes from Incubator PMC members or a separate Incubator PMC vote

I like the idea but suggest requiring at least two +1 votes from the
podling's mentors (or incubator PMC members acting as temporary
substitute mentors in case of absence) instead of just PPMC members.

The rationale is to make sure mentors are following the action.

Also, I'd like to keep the notices to priv...@incubator.apache.org
when a new committer is voted in, with a reference to the vote results
thread.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Andy Seaborne]

On 12/11/10 08:40, Nick Kew wrote:


On 8 Nov 2010, at 23:36, Ross Gardler wrote:


I am pleased to offer, for your consideration, the following proposal to accept 
Jena, a semantic web framework into the incubator. The text of the proposal is 
copied here for your convenience and can be found at 
http://wiki.apache.org/incubator/JenaProposal


Strong +1 in principle.  I'd offer to mentor, but I see you now have plenty.

One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?  The openjena.org page referenced
relies on references that are broken links!


Grr ... rotting links ...

Where?  I'll fix them ASAP.  Checking:

http://openjena.org/Licenses/index.html

I found the links for JUnit and WoodSToX have rotted.  Anything else 
gone bad?


Andy

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal] Accept Jena into the Incubator

[Nick Kew]

On 8 Nov 2010, at 23:36, Ross Gardler wrote:

> I am pleased to offer, for your consideration, the following proposal to 
> accept Jena, a semantic web framework into the incubator. The text of the 
> proposal is copied here for your convenience and can be found at 
> http://wiki.apache.org/incubator/JenaProposal

Strong +1 in principle.  I'd offer to mentor, but I see you now have plenty.

One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?  The openjena.org page referenced
relies on references that are broken links!

-- 
Nick Kew
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS] Poddling new committer process

[ant elder]

I'd like to propose that the process for Incubator poddlings to make
someone a new committer is simplified so that all that is needed are
votes from poddling committers and that there is no longer any need
for votes from Incubator PMC members or a separate Incubator PMC vote.

As justification, this is the process that was in place some years ago
and it worked fine like that, there is the "experiment" currently in
place with some poddlings doing this which seems to be working ok, and
the board has said they're ok with it.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org