Re: Removal of old incubator releases

[Tommaso Teofili]

On Fri, 22 Nov 2019 at 00:15, Justin Mclean 
wrote:

> Hi,
>
> > I have a few questions:
> > 1. are projects required to delete those old incubating release because
> the
> > projects are now TLPs ?
>
> More encouraged than required I think.
>

ok, thx.


>
> > 2. in the case of Joshua, even it's been a while since the project moved
> > outside of Incubator, that's still the latest release hence I wonder:
> > should we remove it anyway?
>
> Perhaps it would be good time to make a new release?
>

sure, we are discussing to cut a new (6.2) release.

Thanks,
Tommaso


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

Re: Removal of old incubator releases

[Tommaso Teofili]

Hi Justin, all,

I have a few questions:
1. are projects required to delete those old incubating release because the
projects are now TLPs ?
2. in the case of Joshua, even it's been a while since the project moved
outside of Incubator, that's still the latest release hence I wonder:
should we remove it anyway ?

Thanks and regards,
Tommaso

On Sun, 17 Nov 2019 at 11:34, Neil C Smith  wrote:

> On Sat, 16 Nov 2019, 23:49 Justin Mclean, 
> wrote:
>
> > It looks like you have some old incubator releases here:
> > https://dist.apache.org/repos/dist/release/incubator/
> >
> > We’re cleaning up the release area and it would be great if you can
> remove
> > these old releases.
> >
>
> If you mean NetBeans 11.0, this is not an old release. It's the current LTS
> release until next April, so left there deliberately.
>
> Best wishes,
>
> Neil
>
> >
>

Re: Mentors wanted for Apache Annotator (incubating)

[Tommaso Teofili]

if needed (also having been involved in the original open annotation
wg) I can help mentoring.

Regards,
Tommaso
Il giorno lun 15 ott 2018 alle ore 09:19 Bertrand Delacretaz
 ha scritto:
>
> Hi,
>
> On Sun, Oct 14, 2018 at 1:41 PM ajs6f  wrote:
> > ...I'm very interested in Annotator (especially, as an apache Jena 
> > committer, from the linked
> > data side) so I'd be happy to mentor
>
> Note that you need to be an Incubator PMC member to be an "official"
> mentor - if Apache members or Incubator PMC members who know you think
> you should become one, they are welcome to discuss that on the
> private@incubator.a.o list. Apache Foundation Members can join that
> PMC just by asking, but others need to be elected.
>
> You can anyway act as an informal mentor by helping on the podling's
> lists, and do most everything that mentors do, even if not an
> Incubator PMC member yet.
>
> -Bertrand
>
> -
> 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

[RESULT][VOTE] - Graduate Apache Joshua (incubating) as a TLP

[Tommaso Teofili]

Since 72 hours have passed, the vote for graduating Apache Joshua as a
TLP passes with 3 +1 binding votes from

Chris Mattmann
Tom Barber
Jean-Baptiste Onofré

and 1 non binding +1 from

Kellen Sunderland

Thanks and regards,
Tommaso

Il giorno ven 21 set 2018 alle ore 18:31 kellen sunderland
 ha scritto:
>
> +1 many thanks for putting the vote together Tomasso.
>
> On Fri, Sep 21, 2018 at 9:06 AM Jean-Baptiste Onofré 
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 21/09/2018 14:53, Tommaso Teofili wrote:
> > > Hi all,
> > >
> > >
> > > The Apache Joshua podling PMC would like the project to graduate to a
> > TLP.
> > > Joshua entered Incubation on February 13th, 2016.
> > > The 6.1 release was the first one done within ASF as an Incubator
> > > project, the PPMC has grown since incubation start.
> > >
> > > Vote:
> > > [ ] +1 - Recommend Graduation of Apache Joshua as a TLP
> > > [ ] -1 - Do not recommend graduation of Apache Joshua because ….
> > >
> > >
> > > The Graduation Proposal was written, discussed and voted on the
> > > project dev@ list [1,2] and here on general@ [3]. As per
> > > recommendations made in [3], the By-Laws Clause was removed [4].
> > > The final resolution can be found at [5].
> > >
> > >
> > > Regards,
> > > Tommaso
> > >
> > >
> > > [1] :
> > https://lists.apache.org/thread.html/2687c75696b61344dadf085c1f48443f71baaf88a9b012f86c35d2e6@%3Cdev.joshua.apache.org%3E
> > > [2] :
> > https://lists.apache.org/thread.html/8ef1f4a9919f56979507fae749af691acb011e9ca7da9bc64bbfc8aa@%3Cdev.joshua.apache.org%3E
> > > [3] :
> > https://lists.apache.org/thread.html/6c274f2ec6261828c636e950447a2c7d926bcc91f95cc10f183690a7@%3Cdev.joshua.apache.org%3E
> > > [4] :
> > https://lists.apache.org/thread.html/7bd8bb062c96cde65c4d7fd4dd1310aed0169d5922b40ec78216d161@%3Cdev.joshua.apache.org%3E
> > > [5] :
> > > 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, for distribution at no charge to
> > >
> > > the public, related to statistical and other forms of machine
> > >
> > > translation.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >
> > > Committee (PMC), to be known as the "Apache Joshua Project",
> > >
> > > be and hereby is established pursuant to Bylaws of the
> > >
> > > Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Joshua Project be and hereby is
> > >
> > > responsible for the creation and maintenance of software
> > >
> > > related to statistical and other forms of machine translation;
> > >
> > > and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Joshua" 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 Joshua Project, and to have primary responsibility
> > >
> > > for management of the projects within the scope of
> > >
> > > responsibility of the Apache Joshua 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 Joshua Project:
> > >
> > >
> > > * Tom Barber  
> > >
> > >
> > > * Thamme Gowda
> > >
> > >
> > > * Felix Hieber
> > >
> > >
> > > * Lewis John McGibbney
> > >
> > >
> > > * Chris Mattmann  
> > >
> > >
> > > * Matt Post   
> > >
> > >
> > > * Paul Ramirez
> > >
> > >
> > > * Henry Saputra   
> > >
> > >
> > > * Kellen Sunderland   

[VOTE] - Graduate Apache Joshua (incubating) as a TLP

[Tommaso Teofili]

Hi all,


The Apache Joshua podling PMC would like the project to graduate to a TLP.
Joshua entered Incubation on February 13th, 2016.
The 6.1 release was the first one done within ASF as an Incubator
project, the PPMC has grown since incubation start.

Vote:
[ ] +1 - Recommend Graduation of Apache Joshua as a TLP
[ ] -1 - Do not recommend graduation of Apache Joshua because ….


The Graduation Proposal was written, discussed and voted on the
project dev@ list [1,2] and here on general@ [3]. As per
recommendations made in [3], the By-Laws Clause was removed [4].
The final resolution can be found at [5].


Regards,
Tommaso


[1] : 
https://lists.apache.org/thread.html/2687c75696b61344dadf085c1f48443f71baaf88a9b012f86c35d2e6@%3Cdev.joshua.apache.org%3E
[2] : 
https://lists.apache.org/thread.html/8ef1f4a9919f56979507fae749af691acb011e9ca7da9bc64bbfc8aa@%3Cdev.joshua.apache.org%3E
[3] : 
https://lists.apache.org/thread.html/6c274f2ec6261828c636e950447a2c7d926bcc91f95cc10f183690a7@%3Cdev.joshua.apache.org%3E
[4] : 
https://lists.apache.org/thread.html/7bd8bb062c96cde65c4d7fd4dd1310aed0169d5922b40ec78216d161@%3Cdev.joshua.apache.org%3E
[5] :
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, for distribution at no charge to

the public, related to statistical and other forms of machine

translation.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management

Committee (PMC), to be known as the "Apache Joshua Project",

be and hereby is established pursuant to Bylaws of the

Foundation; and be it further

RESOLVED, that the Apache Joshua Project be and hereby is

responsible for the creation and maintenance of software

related to statistical and other forms of machine translation;

and be it further

RESOLVED, that the office of "Vice President, Apache Joshua" 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 Joshua Project, and to have primary responsibility

for management of the projects within the scope of

responsibility of the Apache Joshua 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 Joshua Project:


* Tom Barber  


* Thamme Gowda


* Felix Hieber


* Lewis John McGibbney


* Chris Mattmann  


* Matt Post   


* Paul Ramirez


* Henry Saputra   


* Kellen Sunderland       


* Tommaso Teofili 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tommaso Teofili

be appointed to the office of Vice President, Apache Joshua 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 Joshua Project be and hereby

is tasked with the migration and rationalization of the Apache

Incubator Joshua podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache

Incubator Joshua podling encumbered upon the Apache Incubator

Project are hereafter discharged.

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

Re: [DISCUSS] - Graduation of Apache Joshua

[Tommaso Teofili]

Good point Pierre, thanks. It's probably a remnant from an older template.
How should we fix that ? Is there a completely new template and/or should
we just remove that ?

Regards,
Tommaso

Il giorno ven 14 set 2018 alle ore 10:54 Pierre Smits <
pierresm...@apache.org> ha scritto:

> Given the recent discussions regarding project by-laws in this ml and
> elsewhere, is the following element
>
> RESOLVED, that the initial Apache Joshua PMC be and hereby is
>
> tasked with the creation of a set of bylaws intended to
>
> encourage open development and increased participation in the
>
> Apache Joshua Project; and be it further
>
> intentional or just a copy-paste remnant from another graduation
> proposal/template?
>
>
>
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion <https://trafodion.apache.org>, Vice President*
> *Apache Directory <https://directory.apache.org>, PMC Member*
> Apache Incubator <https://incubator.apache.org>, committer
> *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
> since 2008*
> Apache Steve <https://steve.apache.org>, committer
>
> On Fri, Sep 14, 2018 at 10:24 AM, Tommaso Teofili <
> tommaso.teof...@gmail.com
> > wrote:
>
> > Dear all,
> >
> > at Apache Joshua podling we discussed and voted a while back for the
> > graduation of the project to TLP [1]. It then took a while to take it up
> to
> > the next step of coming up with a draft resolution [2] and bring it to
> this
> > list.
> > So please help us drive Apache Joshua to TLP.
> >
> > Regards,
> > Tommaso
> >
> > [1] : https://markmail.org/message/j36u7q7z6fqc7svi
> > [2] :
> > 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, for distribution at no charge to
> >
> > the public, related to statistical and other forms of machine
> >
> > translation.
> >
> >
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >
> > Committee (PMC), to be known as the "Apache Joshua Project",
> >
> > be and hereby is established pursuant to Bylaws of the
> >
> > Foundation; and be it further
> >
> >
> >
> > RESOLVED, that the Apache Joshua Project be and hereby is
> >
> > responsible for the creation and maintenance of software
> >
> > related to statistical and other forms of machine translation;
> >
> > and be it further
> >
> >
> >
> > RESOLVED, that the office of "Vice President, Apache Joshua" 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 Joshua Project, and to have primary responsibility
> >
> > for management of the projects within the scope of
> >
> > responsibility of the Apache Joshua 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 Joshua Project:
> >
> >
> >
> > * Tom Barber  
> >
> > * Thamme Gowda   
> >
> > * Felix Hieber 
> >
> > * Lewis John McGibbney 
> >
> > * Chris Mattmann 
> >
> > * Matt Post 
> >
> > * Paul Ramirez   
> >
> > * Henry Saputra
> >
> > * Kellen Sunderland 
> >
> > * Tommaso Teofili
> >
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tommaso Teofili
> >
> > be appointed to the office of Vice President, Apache Joshua 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 initial Apache Joshua PMC be and hereby is
> >
> > tasked with the creation of a set of bylaws intended to
> >
> > encourage open development and increased participation in the
> >
> > Apache Joshua Project; and be it further
> >
> >
> >
> > RESOLVED, that the Apache Joshua Project be and hereby
> >
> > is tasked with the migration and rationalization of the Apache
> >
> > Incubator Joshua podling; and be it further
> >
> >
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> >
> > Incubator Joshua podling encumbered upon the Apache Incubator
> >
> > Project are hereafter discharged.
> >
>

[DISCUSS] - Graduation of Apache Joshua

[Tommaso Teofili]

Dear all,

at Apache Joshua podling we discussed and voted a while back for the
graduation of the project to TLP [1]. It then took a while to take it up to
the next step of coming up with a draft resolution [2] and bring it to this
list.
So please help us drive Apache Joshua to TLP.

Regards,
Tommaso

[1] : https://markmail.org/message/j36u7q7z6fqc7svi
[2] :
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, for distribution at no charge to

the public, related to statistical and other forms of machine

translation.



NOW, THEREFORE, BE IT RESOLVED, that a Project Management

Committee (PMC), to be known as the "Apache Joshua Project",

be and hereby is established pursuant to Bylaws of the

Foundation; and be it further



RESOLVED, that the Apache Joshua Project be and hereby is

responsible for the creation and maintenance of software

related to statistical and other forms of machine translation;

and be it further



RESOLVED, that the office of "Vice President, Apache Joshua" 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 Joshua Project, and to have primary responsibility

for management of the projects within the scope of

responsibility of the Apache Joshua 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 Joshua Project:



* Tom Barber  

* Thamme Gowda   

* Felix Hieber 

* Lewis John McGibbney 

* Chris Mattmann 

* Matt Post 

* Paul Ramirez   

* Henry Saputra

* Kellen Sunderland         

* Tommaso Teofili



NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tommaso Teofili

be appointed to the office of Vice President, Apache Joshua 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 initial Apache Joshua PMC be and hereby is

tasked with the creation of a set of bylaws intended to

encourage open development and increased participation in the

Apache Joshua Project; and be it further



RESOLVED, that the Apache Joshua Project be and hereby

is tasked with the migration and rationalization of the Apache

Incubator Joshua podling; and be it further



RESOLVED, that all responsibilities pertaining to the Apache

Incubator Joshua podling encumbered upon the Apache Incubator

Project are hereafter discharged.

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC1

[Tommaso Teofili]

+1 (binding)

Il giorno dom 3 dic 2017 alle ore 16:22 Suneel Marthi 
ha scritto:

> +1 binding
>
> On Sat, Dec 2, 2017 at 12:57 PM, Sergio Fernández 
> wrote:
>
> > +1 (binding)
> >
> > Most of the minor issues I've seen so far are already reported by Justin.
> > So let's address them for the next release. Good luck at NIPS!
> >
> >
> >
> > On Nov 30, 2017 4:45 PM, "Chris Olivier"  wrote:
> >
> > Hello All,
> >
> >
> > This is a call for releasing Apache MXNet (incubating) 1.0.0, release
> > candidate 1.
> >
> >
> > Apache MXNet community has voted and approved the release.
> >
> >
> > *Vote thread:*
> >
> > https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
> > 7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
> >
> >
> > *Result thread:*
> >
> > https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
> > ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E
> >
> >
> > *The source tarball, including signatures, digests, etc. can be found
> at:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc1/
> >
> >
> >
> > *The release tag can be found here: *
> >
> > https://github.com/apache/incubator-mxnet/tree/1.0.0.rc1
> >
> >
> >
> > *The release hash is *25720d0e3c29232a37e2650f3ba3a2454f9367bb* and can
> be
> > found here:*
> >
> >  > 25720d0e3c29232a37e2650f3ba3a2454f9367bb>
> >
> >
> >
> > *Release artifacts are signed with the following key:*
> >
> > 16DD B2E2 FE0C 3925 CB13  38D7 21F3 F9AB C622 DF82
> >
> >
> >
> > *KEY files are available here:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> >
> >
> >
> > *For information about the contents of this release, see:*
> >
> >  > Apache+MXNet+%28incubating%29+1.0+Release+Notes>
> >
> >
> >
> > The vote will be open for at least 72 hours.
> >
> >
> > [ ] +1 Release this package as 1.0.0
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 Do not release this package because...
> >
> >
> > Thanks,
> >
> >
> > -Chris Olivier
> >
> > cjolivie...@apache.org
> >
>

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

result thread is out, will move on with the remaining steps.

Regards,
Tommaso

Il giorno mar 13 giu 2017 alle ore 03:08 lewis john mcgibbney <
lewi...@apache.org> ha scritto:

> PING @Tommaso, can you please close this thread out and we can move on with
> the release?
> Thank you
>
> On Sat, Jun 10, 2017 at 12:56 PM, lewis john mcgibbney  >
> wrote:
>
> > Thank you Justin and John,
> > @tommaso, please progress with the RESULT thread and we can continue with
> > the release process.
> > Lewis
> >
> > On Sat, Jun 10, 2017 at 11:59 AM,  > incubator.apache.org> wrote:
> >
> >>
> >> From: Justin Mclean 
> >> To: general@incubator.apache.org
> >> Cc:
> >> Bcc:
> >> Date: Sat, 10 Jun 2017 12:19:46 +1000
> >> Subject: Re: [VOTE] - Approve the release of Apache Joshua incubating
> 6.1
> >> (rc4)
> >> Hi,
> >>
> >> > @justin, if you are interested in continuing to help Joshua incubating
> >> with
> >> > the release process then pleae stick with us until we iron this one
> out.
> >>
> >> I’ve already voted +1 on the release.
> >>
> >> That GitHub issue looks resolved to me i.e. the copyright owner gave you
> >> permission to use the code under an Apache license.
> >>
> >>
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

[RESULT] [VOTE] - Approve the release of Apache Joshua incubating 6.1

[Tommaso Teofili]

Hi all,

the vote passed with binding +1s from

Lewis John McGibbney
Justin Mclean
John D. Ament

Thanks a lot for your support.
Regards,
Tommaso

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

perfect, thanks all for your support for this release.

Regards,
Tommaso


Il giorno sab 10 giu 2017 alle ore 21:56 lewis john mcgibbney <
lewi...@apache.org> ha scritto:

> Thank you Justin and John,
> @tommaso, please progress with the RESULT thread and we can continue with
> the release process.
> Lewis
>
> On Sat, Jun 10, 2017 at 11:59 AM, <
> general-digest-h...@incubator.apache.org>
> wrote:
>
> >
> > From: Justin Mclean 
> > To: general@incubator.apache.org
> > Cc:
> > Bcc:
> > Date: Sat, 10 Jun 2017 12:19:46 +1000
> > Subject: Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1
> > (rc4)
> > Hi,
> >
> > > @justin, if you are interested in continuing to help Joshua incubating
> > with
> > > the release process then pleae stick with us until we iron this one
> out.
> >
> > I’ve already voted +1 on the release.
> >
> > That GitHub issue looks resolved to me i.e. the copyright owner gave you
> > permission to use the code under an Apache license.
> >
> >
>

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

thanks Justin for your vote.

The mentioned files should come from [1.2], which contains AL2 header.
When building Joshua you may found the compiled binaries, but they are not
shipped together with the source release; so if I understand things
correctly we should be fine.

Regards,
Tommaso

[1] :
https://github.com/apache/incubator-joshua/blob/master/scripts/training/parallelize/sentserver.c
[2] :
https://github.com/apache/incubator-joshua/blob/master/scripts/training/parallelize/sentclient.c


Il giorno gio 1 giu 2017 alle ore 03:29 Justin Mclean <
jus...@classsoftware.com> ha scritto:

> Hi,
>
> +1 binding
>
> I checked:
> - name includes incubating
> - signatures and hashes correct
> - disclaimer exists
> - LICENSE is OK
> - NOTICE contains wrong year please fix
> - no unexpected binary files
> - source files have ASF headers
> - can compile from source
>
> I’m curious to know where these files come from [1][2]. I found them
> elsewhere without Apache headers but was unable to find how they were
> licensed.
>
> Thanks,
> Justin
>
> 1. ./scripts/training/parallelize/sentclient.c
> 2../scripts/training/parallelize/sentserver.c
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

ping, anyone ?!

Il giorno dom 7 mag 2017 alle ore 09:06 Henry Saputra <
henry.sapu...@gmail.com> ha scritto:

> LICENSE file looks good
> NOTICE file looks good
> DISCLAIMER file looks good
> No 3rd party exes in source artifact
> Signature file for source looks good
> Hash files for source look good
>
> +1 (binding)
>
> On Wed, May 3, 2017 at 1:44 AM, Tommaso Teofili <tommaso.teof...@gmail.com
> >
> wrote:
>
> > Hello incubator PMCs,
> >
> > The Apache Joshua community PPMCs and developers have voted and
> > approved the proposal to release Apache Joshua 6.1 (incubating).
> > Apache Joshua is a statistical machine translation toolkit.
> >
> > [VOTE] thread:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-joshua-
> > dev/201703.mbox/%3CCAGnSx06x0aNW9BxJ-QA2K-2%3Df7tqvqa_2a_ijKj%2B_
> > L81XwpPog%40mail.gmail.com%3E
> >
> > [RESULT][VOTE] thread:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-joshua-
> > dev/201705.mbox/%3CCAGnSx06CrpVe14Y5FVqqskUKprbY9tqvjw2JOB6hGMF9ngnDRA%
> > 40mail.gmail.com%3E
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Git source tag (23d5bda277028ea42b142b221639fd233a08da36):
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-joshua.git;a=commit;h=
> > 23d5bda277028ea42b142b221639fd233a08da36
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachejoshua-1005
> >
> > Source Release Artifacts:
> > https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
> >
> > PGP release keys (signed using 891768A5):
> > https://git1-us-west.apache.org/repos/asf?p=incubator-
> > joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c
> > 3a2460a98d;hb=HEAD
> >
> > The vote will be open for ~72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.  Then
> > please vote:
> >
> > [ ] +1 Approve the release
> > [ ] +0 No opinion
> > [ ] -1 Do not approve the release because ...
> >
> > Thanks,
> > Tommaso on behalf of the Apache Joshua (incubating) team
> >
>

[VOTE] - Approve the release of Apache Joshua incubating 6.1 (rc4)

[Tommaso Teofili]

Hello incubator PMCs,

The Apache Joshua community PPMCs and developers have voted and
approved the proposal to release Apache Joshua 6.1 (incubating).
Apache Joshua is a statistical machine translation toolkit.

[VOTE] thread:

http://mail-archives.apache.org/mod_mbox/incubator-joshua-dev/201703.mbox/%3CCAGnSx06x0aNW9BxJ-QA2K-2%3Df7tqvqa_2a_ijKj%2B_L81XwpPog%40mail.gmail.com%3E

[RESULT][VOTE] thread:

http://mail-archives.apache.org/mod_mbox/incubator-joshua-dev/201705.mbox/%3CCAGnSx06CrpVe14Y5FVqqskUKprbY9tqvjw2JOB6hGMF9ngnDRA%40mail.gmail.com%3E

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Git source tag (23d5bda277028ea42b142b221639fd233a08da36):
https://git-wip-us.apache.org/repos/asf?p=incubator-joshua.git;a=commit;h=23d5bda277028ea42b142b221639fd233a08da36

Staging repo:
https://repository.apache.org/content/repositories/orgapachejoshua-1005

Source Release Artifacts:
https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/

PGP release keys (signed using 891768A5):
https://git1-us-west.apache.org/repos/asf?p=incubator-joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c3a2460a98d;hb=HEAD

The vote will be open for ~72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.  Then
please vote:

[ ] +1 Approve the release
[ ] +0 No opinion
[ ] -1 Do not approve the release because ...

Thanks,
Tommaso on behalf of the Apache Joshua (incubating) team

Re: [VOTE] Release Apache Streams 0.5 (incubating)

[Tommaso Teofili]

+1 (binding)
Tommaso
Il giorno lun 13 mar 2017 alle 14:48 Matt Franklin 
ha scritto:

> Hi Incubator PMC,
>
> The Apache Streams community has voted and approved the proposal to release
> Apache Streams 0.5 (incubating).
>
> The dev-list vote succeeded with 3 IPMC +1s, so we now request a
> lazy-consensus vote from the wider IPMC.
>
> The 0.5.0-incubating release simplifies the build process by combining the
> master POM and the project parent POM. It also contains various other code
> improvements and simplifications.
>
> Thread [VOTE] : https://s.apache.org/3q6X
> Thread [VOTE] [RESULT] : https://s.apache.org/rWN1
>
> The Release candidate to be voted upon is 0.5-incubating, with the
> following artifacts up for a vote:
>
> incubator-streams source tag (0.5-incubating):
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;a=tag;h=c56bfa9e060e2ff4e2b19704e0053de7f2fa325b
>
> incubator-streams-examples source tag (0.5-incubating):
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams-examples.git;a=tag;h=2cf40517cd93654db3ec90f853d4db2aaab90790
>
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachestreams-1024/
>
> Source releases:
>
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.5-incubating/streams-project-0.5-incubating-source-release.zip
> SHA1: a3512225b06eeda6f4551cd89ce9faa55a4fc1ea
>
>
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.5-incubating/streams-examples-0.5-incubating-source-release.zip
> SHA1: ca91ccaad4e53dee387b311679cb1beb73ae54a0
>
> Release artifacts are signed with the following keys:
> https://people.apache.org/keys/committer/mfranklin.asc
>
> Signatures and hashes can be found in the staging repository and the dist
> location (
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.5-incubating/)
>
> Note that Maven 3.3.9 and JDK 1.8+ are now required, and that MAVEN_OPTS
> should set the java heap to at least 2G for best results.
>
> These repositories must be verified (mvn clean verify) in the right order:
> first streams-project, then streams-examples.
>
> Note that to execute the full suite of integration tests, one must first
> prepare a testing environment with docker databases and working credentials
> to all providers.
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Tommaso Teofili]

2016-02-01 16:20 GMT+01:00 Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov>:

> Hey Jim,
>
> This is a valid concern, one that I hope is mediated by taking
> however long it takes in Incubation to attract some new committers
> to work on the project. Hopefully too you saw how long I took to
> allow the discussion to occur and so forth.
>
> Lewis has actively contributed to Joshua already - you can see -
> via the HomeBrew package he created, see:
>
> https://github.com/Homebrew/homebrew/pull/45746
>
>
> You can see too it wasn’t something just recent or something
> super quick it’s something he had to work at.
>
> As for me, my involvement is going to be limited, but I am
> actively pursuing Tika’s integration with Joshua as part of
> TIKA-1343: http://issues.apache.org/jira/browse/TIKA-1343.
>
> Finally my suspicion is that Tom, Henry and Tommaso will
> contribute a lot as well.
>

FWIW although I'm new to Joshua I am very interested and plan to contribute
(maybe we integrations here and there, hint hint) as much as I can.

Regards,
Tommaso


>
> Thanks for listening.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -Original Message-
> From: Jim Jagielski 
> Reply-To: "general@incubator.apache.org" 
> Date: Monday, February 1, 2016 at 4:20 AM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: Re: [VOTE] Accept Joshua as an Apache Incubator Podling
>
> >I know this is specifically called-out in the proposal, but it
> >does seem worthy of further discussion.
> >
> >This has a pretty small list of initial committers, esp when one considers
> >how over-booked 2 of them appear to be.
> >
> >So, realistically, how active do both Chris and Lewis expect
> >to be?
> >
> >> On Jan 30, 2016, at 3:00 PM, Mattmann, Chris A (3980)
> >> wrote:
> >>
> >> Hi Everyone,
> >>
> >> OK the discussion is now completed. Please VOTE to accept Joshua
> >> into the Apache Incubator. I’ll leave the VOTE open for at least
> >> the next 72 hours, with hopes to close it next Friday the 5th of
> >> February, 2016.
> >>
> >> [ ] +1 Accept Joshua as an Apache Incubator podling.
> >> [ ] +0 Abstain.
> >> [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
> >>
> >> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> >> members are binding but all are welcome to VOTE!
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++
> >> Chris Mattmann, Ph.D.
> >> Chief Architect
> >> Instrument Software and Science Data Systems Section (398)
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 168-519, Mailstop: 168-527
> >> Email: chris.a.mattm...@nasa.gov
> >> WWW:  http://sunset.usc.edu/~mattmann/
> >> ++
> >> Adjunct Associate Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: jpluser 
> >> Date: Tuesday, January 12, 2016 at 10:56 PM
> >> To: "general@incubator.apache.org" 
> >> Cc: "p...@cs.jhu.edu" 
> >> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> >>Translation
> >> Toolkit
> >>
> >>> Hi Everyone,
> >>>
> >>> Please find attached for your viewing pleasure a proposed new project,
> >>> Apache Joshua, a statistical machine translation toolkit. The proposal
> >>> is in wiki draft form at:
> >>>https://wiki.apache.org/incubator/JoshuaProposal
> >>>
> >>> Proposal text is copied below. I’ll leave the discussion open for a
> >>>week
> >>> and we are interested in folks who would like to be initial committers
> >>> and mentors. Please discuss here on the thread.
> >>>
> >>> Thanks!
> >>>
> >>> Cheers,
> >>> Chris (Champion)
> >>>
> >>> ———
> >>>
> >>> = Joshua Proposal =
> >>>
> >>> == Abstract ==
> >>> [[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >>> translation toolkit. It includes a Java-based decoder for translating
> >>>with
> >>> phrase-based, hierarchical, and syntax-based translation models, a
> >>> Hadoop-based grammar extractor 

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Tommaso Teofili]

+1 (binding)

Tommaso

2016-01-30 21:00 GMT+01:00 Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov>:

> Hi Everyone,
>
> OK the discussion is now completed. Please VOTE to accept Joshua
> into the Apache Incubator. I’ll leave the VOTE open for at least
> the next 72 hours, with hopes to close it next Friday the 5th of
> February, 2016.
>
> [ ] +1 Accept Joshua as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
>
> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> members are binding but all are welcome to VOTE!
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -Original Message-
> From: jpluser 
> Date: Tuesday, January 12, 2016 at 10:56 PM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation
> Toolkit
>
> >Hi Everyone,
> >
> >Please find attached for your viewing pleasure a proposed new project,
> >Apache Joshua, a statistical machine translation toolkit. The proposal
> >is in wiki draft form at:
> https://wiki.apache.org/incubator/JoshuaProposal
> >
> >Proposal text is copied below. I’ll leave the discussion open for a week
> >and we are interested in folks who would like to be initial committers
> >and mentors. Please discuss here on the thread.
> >
> >Thanks!
> >
> >Cheers,
> >Chris (Champion)
> >
> >———
> >
> >= Joshua Proposal =
> >
> >== Abstract ==
> >[[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >translation toolkit. It includes a Java-based decoder for translating with
> >phrase-based, hierarchical, and syntax-based translation models, a
> >Hadoop-based grammar extractor (Thrax), and an extensive set of tools and
> >scripts for training and evaluating new models from parallel text.
> >
> >== Proposal ==
> >Joshua is a state of the art statistical machine translation system that
> >provides a number of features:
> >
> > * Support for the two main paradigms in statistical machine translation:
> >phrase-based and hierarchical / syntactic.
> > * A sparse feature API that makes it easy to add new feature templates
> >supporting millions of features
> > * Native implementations of many tuners (MERT, MIRA, PRO, and AdaGrad)
> > * Support for lattice decoding, allowing upstream NLP tools to expose
> >their hypothesis space to the MT system
> > * An efficient representation for models, allowing for quick loading of
> >multi-gigabyte model files
> > * Fast decoding speed (on par with Moses and mtplz)
> > * Language packs — precompiled models that allow the decoder to be run as
> >a black box
> > * Thrax, a Hadoop-based tool for learning translation models from
> >parallel text
> > * A suite of tools for constructing new models for any language pair for
> >which sufficient training data exists
> >
> >== Background and Rationale ==
> >A number of factors make this a good time for an Apache project focused on
> >machine translation (MT): the quality of MT output (for many language
> >pairs); the average computing resources available on computers, relative
> >to the needs of MT systems; and the availability of a number of
> >high-quality toolkits, together with a large base of researchers working
> >on them.
> >
> >Over the past decade, machine translation (MT; the automatic translation
> >of one human language to another) has become a reality. The research into
> >statistical approaches to translation that began in the early nineties,
> >together with the availability of large amounts of training data, and
> >better computing infrastructure, have all come together to produce
> >translations results that are “good enough” for a large set of language
> >pairs and use cases. Free services like
> >[[https://www.bing.com/translator|Bing Translator]] and
> >[[https://translate.google.com|Google Translate]] have made these
> services
> >available to the average person through direct interfaces and through
> >tools like browser plugins, and sites across the world with higher
> >translation needs use them to translate their pages through automatically.
> >
> >MT does not require the infrastructure of large corporations in order to
> >produce feasible output. Machine translation can be resource-intensive,
> >but need not be prohibitively so. Disk and memory 

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Tommaso Teofili]

what about moving forward to [VOTE] ?

Regards,
Tommaso

2016-01-22 4:31 GMT+01:00 Henri Yandell :

> On Wed, Jan 20, 2016 at 10:37 AM, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
>
> > All of this can be worked during Incubation and I think we have
> > the right folks here who can help to get it set up.
> >
>
> Yup - my question was well answered; thanks all :)
>
> Hen
>

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Tommaso Teofili]

2016-01-30 2:31 GMT+01:00 Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov>:

> Yep I was giving it a few more days to see if there was any interest.
>
> I intend to call the VOTE in a few hours :-)
>

cool, thanks!


>
> Thanks Tommaso! Have you added your interest to the wiki?
>

sure, I've added myself as a committer :)

Cheers,
Tommaso



>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++
>
>
>
>
>
> -Original Message-
> From: Tommaso Teofili <tommaso.teof...@gmail.com>
> Reply-To: "general@incubator.apache.org" <general@incubator.apache.org>
> Date: Friday, January 29, 2016 at 8:29 AM
> To: "general@incubator.apache.org" <general@incubator.apache.org>
> Subject: Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> Translation Toolkit
>
> >what about moving forward to [VOTE] ?
> >
> >Regards,
> >Tommaso
> >
> >2016-01-22 4:31 GMT+01:00 Henri Yandell <bay...@apache.org>:
> >
> >> On Wed, Jan 20, 2016 at 10:37 AM, Mattmann, Chris A (3980) <
> >> chris.a.mattm...@jpl.nasa.gov> wrote:
> >>
> >> > All of this can be worked during Incubation and I think we have
> >> > the right folks here who can help to get it set up.
> >> >
> >>
> >> Yup - my question was well answered; thanks all :)
> >>
> >> Hen
> >>
>
>

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Tommaso Teofili]

Hi Chris, all,

that's a very interesting proposal, if you wish I can help (with my
OpenNLP/Lucene hat on).

Regards,
Tommaso

2016-01-13 7:56 GMT+01:00 Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov>:

> Hi Everyone,
>
> Please find attached for your viewing pleasure a proposed new project,
> Apache Joshua, a statistical machine translation toolkit. The proposal
> is in wiki draft form at: https://wiki.apache.org/incubator/JoshuaProposal
>
> Proposal text is copied below. I’ll leave the discussion open for a week
> and we are interested in folks who would like to be initial committers
> and mentors. Please discuss here on the thread.
>
> Thanks!
>
> Cheers,
> Chris (Champion)
>
> ———
>
> = Joshua Proposal =
>
> == Abstract ==
> [[joshua-decoder.org|Joshua]] is an open-source statistical machine
> translation toolkit. It includes a Java-based decoder for translating with
> phrase-based, hierarchical, and syntax-based translation models, a
> Hadoop-based grammar extractor (Thrax), and an extensive set of tools and
> scripts for training and evaluating new models from parallel text.
>
> == Proposal ==
> Joshua is a state of the art statistical machine translation system that
> provides a number of features:
>
>  * Support for the two main paradigms in statistical machine translation:
> phrase-based and hierarchical / syntactic.
>  * A sparse feature API that makes it easy to add new feature templates
> supporting millions of features
>  * Native implementations of many tuners (MERT, MIRA, PRO, and AdaGrad)
>  * Support for lattice decoding, allowing upstream NLP tools to expose
> their hypothesis space to the MT system
>  * An efficient representation for models, allowing for quick loading of
> multi-gigabyte model files
>  * Fast decoding speed (on par with Moses and mtplz)
>  * Language packs — precompiled models that allow the decoder to be run as
> a black box
>  * Thrax, a Hadoop-based tool for learning translation models from
> parallel text
>  * A suite of tools for constructing new models for any language pair for
> which sufficient training data exists
>
> == Background and Rationale ==
> A number of factors make this a good time for an Apache project focused on
> machine translation (MT): the quality of MT output (for many language
> pairs); the average computing resources available on computers, relative
> to the needs of MT systems; and the availability of a number of
> high-quality toolkits, together with a large base of researchers working
> on them.
>
> Over the past decade, machine translation (MT; the automatic translation
> of one human language to another) has become a reality. The research into
> statistical approaches to translation that began in the early nineties,
> together with the availability of large amounts of training data, and
> better computing infrastructure, have all come together to produce
> translations results that are “good enough” for a large set of language
> pairs and use cases. Free services like
> [[https://www.bing.com/translator|Bing Translator]] and
> [[https://translate.google.com|Google Translate]] have made these services
> available to the average person through direct interfaces and through
> tools like browser plugins, and sites across the world with higher
> translation needs use them to translate their pages through automatically.
>
> MT does not require the infrastructure of large corporations in order to
> produce feasible output. Machine translation can be resource-intensive,
> but need not be prohibitively so. Disk and memory usage are mostly a
> matter of model size, which for most language pairs is a few gigabytes at
> most, at which size models can provide coverage on the order of tens or
> even hundreds of thousands of words in the input and output languages. The
> computational complexity of the algorithms used to search for translations
> of new sentences are typically linear in the number of words in the input
> sentence, making it possible to run a translation engine on a personal
> computer.
>
> The research community has produced many different open source translation
> projects for a range of programming languages and under a variety of
> licenses. These projects include the core “decoder”, which takes a model
> and uses it to translate new sentences between the language pair the model
> was defined for. They also typically include a large set of tools that
> enable new models to be built from large sets of example translations
> (“parallel data”) and monolingual texts. These toolkits are usually built
> to support the agendas of the (largely) academic researchers that build
> them: the repeated cycle of building new models, tuning model parameters
> against development data, and evaluating them against held-out test data,
> using standard metrics for testing the quality of MT output.
>
> Together, these three factors—the quality of machine translation output,
> the feasibility of translating on standard computers, and the 

Re: A suggestion: podling post-mortems

[Tommaso Teofili]

I like this idea, +1.

Tommaso

2015-10-12 13:18 GMT+02:00 Andrew Bayer :

> I'd like to make a suggestion - after a podling graduates or is terminated,
> the podling's mentors should be responsible for putting together a post
> mortem report, or an exit interview, or whatever you want to call it. This
> would cover the pain points in onboarding the podling, particular issues
> hit during incubation, what made the podling easier or harder to get to
> graduation, and ideally a self assessment of what the mentors think they
> could have done better.
>
> I think this would be very valuable - it'd help shine a light on
> inefficiencies in getting into the ASF's infrastructure, show things to
> watch for/discuss in podling cultural integration, and provide more
> information and self-support for future mentors.
>
> Thoughts?
>
> A.
>

Re: [VOTE] Accept Horn into the ASF incubator

[Tommaso Teofili]

+1

Tommaso

2015-09-01 1:13 GMT+02:00 Edward J. Yoon :

> Hi folks,
>
> I would like to call a vote to accept Horn, as a new Apache Incubator
> project. The full proposal is available at the end of this mail and as
> a https://wiki.apache.org/incubator/HornProposal (the changes from
> initial discussion draft are addition of 2 committers from cldi-kaist
> team and Rich as a mentor).
>
> The VOTE is open for at least the next 72 hours:
>
> [ ] +1 Accept Horn into the Apache Incubator
> [ ] 0
> [ ] -1 Do not accept Horn into the Apache Incubator bc ..
>
> I'd like to get the voting started w/ my own +1
>
> Thanks!
>
> == Abstract ==
>
> Horn [hɔ:n] (korean meaning of Horn is a "Spirit") is a neuron-centric
> programming APIs and execution framework for large-scale deep
> learning, built on top of Apache Hama.
>
> == Proposal ==
>
> It is a goal of the Horn to provide a neuron-centric programming APIs
> which allows user to easily define the characteristic of artificial
> neural network model and its structure, and its execution framework
> that leverages the heterogeneous resources on Hama and Hadoop YARN
> cluster.
>
> == Background ==
>
> The initial ANN code was developed at Apache Hama project by a
> committer, Yexi Jiang (Facebook) in 2013. The motivation behind this
> work is to build a framework that provides more intuitive programming
> APIs like Google's MapReduce or Pregel and supports applications
> needing large model with huge memory consumptions in distributed way.
>
> == Rationale ==
>
> While many of deep learning open source softwares such as Caffe,
> DeepDist, DL4j, and NeuralGiraph are still data or model parallel
> only, we aim to support both data and model parallelism and also
> fault-tolerant system design. The basic idea of data and model
> parallelism is use of the remote parameter server to parallelize model
> creation and distribute training across machines, and the BSP
> framework of Apache Hama for performing asynchronous mini-batches.
> Within single BSP job, each task group works asynchronously using
> region barrier synchronization instead of global barrier
> synchronization, and trains large-scale neural network model using
> assigned data sets in BSP paradigm. Thus, we achieve data and model
> parallelism. This architecture is inspired by Google's !DistBelief
> (Jeff Dean et al, 2012).
>
> == Initial Goals ==
>
> Some current goals include:
>
>  * builds new community
>  * provides more intuitive programming APIs
>  * needs both data and model parallelism support
>  * must run natively on both Hama and Hadoop2
>  * needs also GPUs and InfiniBand support (FPGAs if possible)
>
> == Current Status ==
>
> === Meritocracy ===
>
> The core developers understand what it means to have a process based
> on meritocracy. We will provide continuous efforts to build an
> environment that supports this, encouraging community members to
> contribute.
>
> === Community ===
>
> A small community has formed within the Apache Hama project community,
> universities, and companies such as deep learning startup, instant
> messenger service company, and mobile manufacturing company. And many
> people are interested in the large-scale deep learning platform
> itself. By bringing Horn into Apache, we believe that the community
> will grow even bigger.
>
> === Core Developers ===
>
> Edward J. Yoon, Thomas Jungblut, Jungin Lee, and Minho Kim
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> Apache Hama is already a core open source component at Samsung
> Electronics, and Horn also will be used by Samsung Electronics and
> Cldi Inc., and so there is no direct risk for this project to be
> orphaned.
>
> === Inexperience with Open Source ===
>
> Some are very new and the others have experience using and/or working
> on Apache open source projects.
>
> === Homogeneous Developers ===
>
> The initial committers are from different organizations such as,
> Microsoft, Samsung Electronics, Seoul National University, Technical
> University of Munich, KAIST, LINE plus, and Cldi Inc.
>
> === Reliance on Salaried Developers ===
>
> Few will be worked as a full-time open source developer. Other
> developers will also start working on the project in their spare time.
>
> === Relationships with Other Apache Products ===
>
>  * Horn is based on Apache Hama
>  * Apache Zookeeper is used for distributed locking service
>  * Natively run on Apache Hadoop and Mesos
>  * Horn can be somewhat overlapped with Singa podling (If possible,
> we'd also like to use Singa or Caffe to do the heavy lifting part).
>
> === An Excessive Fascination with the Apache Brand ===
>
> Horn itself will hopefully have benefits from Apache, in terms of
> attracting a community and establishing a solid group of developers,
> but also the relation with Apache Hadoop, Zookeeper, and Hama. These
> are the main reasons for us to send this proposal.
>
> == Documentation ==
>
> Initial plan about Horn can be found at
> 

Re: [VOTE] Release Apache Commons RDF 0.1.0-incubating RC2

[Tommaso Teofili]

+1

Tommaso

2015-05-11 22:52 GMT+02:00 Lewis John Mcgibbney lewis.mcgibb...@gmail.com:

 Hi Sergio/Folks,
 Thanks for putting together the Commons RDF 0.1.0-incubating RC again.
 Sigs are good.
 Source builds and tests A OK.
 DRAT [0] stats are good!

   Notes Binaries Archives Standards Apache Generated Unknown  0 0 0 32 32 0
 0

 On Sun, May 10, 2015 at 7:08 PM, general-digest-h...@incubator.apache.org
 
 wrote:

 
  [X] +1 Release this package


 This VOTE is IPMC binding.
 Thanks
 Lewis

 [0] https://github.com/chrismattmann/drat

Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project

[Tommaso Teofili]

2014-04-28 10:45 GMT+02:00 Ted Dunning ted.dunn...@gmail.com:

 Edward,

 Sub-projects are generally frowned on.  Incubator projects can graduate
 eventually to a top-level project, but starting a project as a sub is not
 so good.  The incubator docs on this are pretty good reading.

 But if the committer community for your real-time BSP is (or can be) the
 same as the committer community for Hama itself, you might want to just
 fold this new code directly into Hama itself.  No need in that case for a
 separate project.

 If the committer community is very different, then a separate project is
 warranted.

 I don't think that the Hama development is such a high bandwidth thing that
 splitting is required.  To my mind that says that joining groups together
 is better than breaking them apart.  Together, the two efforts can feed off
 each other.  Apart, they could each run down due to lack of interest.


+1 to Ted's suggestion, we can create a separate directory on trunk for
Meerkat (or a branch) and eventually have separate release processes for
Hama core stuff and Meerkat stuff if that's needed.



 You will know much better than any of us the details of your communities.


as far as I can see Meerkat is being developed by Edward and another
committer so it should be relatively straightforward to let him/her join
the Hama community.

My 2 cents,
Tommaso







 On Mon, Apr 28, 2014 at 4:23 AM, Edward J. Yoon edwardy...@apache.org
 wrote:

  Hi guys,
 
  As some people already might know, I'm recently working on real-time
  data processing project on top of Hama BSP model, called Meerkat[1]
  (currently only few developers (from two organizations, Kakaotalk and
  DataSayer) are involved in this project).
 
  According to our internal study, Storm-like DAG-style and
  fault-tolerant streaming processing framework can be implemented on
  top of Hama BSP model. And, furthermore, we're thinking, it may be
  possible to connect to other BSP applications using some smart input
  and output formats in the future e.g., streaming graph or learning BSP
  applications. Thus, we believe that we may be able to have an
  next-generation architecture that processes and analyzes the data
  rapidly in real-time, beyond complex old-style data collecting,
  storing, ordering, processing, and analyzing architecture.
 
  Does it make sense to you? If so, I'd like to start to move from
  github to ASF soon, although this is very *early* stage. Because, it's
  highly related with Apache Hama and others. Hama sub-module or
  sub-project, (or Apache incubator?). Which is best you think?
 
  I'm also CC'ing general@i.a.o to see more feedbacks (from Apache big
  data OSS communities).
 
  1. https://github.com/datasayer/meerkat
 
  --
  Best Regards, Edward J. Yoon
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 

Re: Hoya Proposal

[Tommaso Teofili]

I just can speak for the Hama-to-Yarn use case (with my newbie hat on) and
it seems Hoya may be really helpful as the entry point to address it as it
provides a set of simple and useful tools.
For the sake of the names I think Hoya would be good (while Hyena would
not).

Just my 0.02 cents,
Tommaso


2014/1/17 Steve Loughran ste...@hortonworks.com

 On 16 January 2014 12:41, Tommaso Teofili tommaso.teof...@gmail.com
 wrote:

  Hi all,
 
  @Steve I'm curious to know if also Apache Hama may leverage Hoya to be
  deployed on YARN.
 
 
 If you are going to make a 100% commit to running in YARN -which, if you
 aren't ready yet, Hama should be able to do in some point in the future-
 then I'd say go for it! and then point you at Twill to get you started.

 If all you are trying to do is deploy the BSP daemons in a YARN cluster,
 and they don't need any persistent localfs storage, then Hoya should work.
 You already use ZK for the binding mechanism, don't you?


 If yes, that'd hopefully bring some more people involved from Hama as well.
 


 That'd be great!

 --
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to
 which it is addressed and may contain information that is confidential,
 privileged and exempt from disclosure under applicable law. If the reader
 of this message is not the intended recipient, you are hereby notified that
 any printing, copying, dissemination, distribution, disclosure or
 forwarding of this communication is strictly prohibited. If you have
 received this communication in error, please contact the sender immediately
 and delete it from your system. Thank You.

Re: Hoya Proposal

[Tommaso Teofili]

Hi all,

@Steve I'm curious to know if also Apache Hama may leverage Hoya to be
deployed on YARN.

If yes, that'd hopefully bring some more people involved from Hama as well.

My 0.02 cents,
Tommaso



2014/1/14 Enis Söztutar enis@gmail.com

  +1 -I'd really like input from the HBase and Accumulo teams as they are
 the
 first apps we're trying to work with.
 Great, please add me as a mentor than.

 There is another animal named Nyala  (

 http://thewebsiteofeverything.com/animals/mammals/Artiodactyla/Bovidae/Tragelaphus/Tragelaphus-angasii.html
 ).
 Not sure how similar / dissimilar to jena.

 For future reference to Hadoop-related projects:
 http://thewebsiteofeverything.com/habitats/Savanna.html

 Enis


 On Mon, Jan 13, 2014 at 2:21 PM, Ted Dunning ted.dunn...@gmail.com
 wrote:

  Too many people will read that as Jena, the city in Thuringia.
 
  https://en.wikipedia.org/wiki/Jena
 
  -1
 
 
 
 
  On Mon, Jan 13, 2014 at 1:57 PM, Andy Seaborne a...@apache.org wrote:
 
   On 13/01/14 20:25, Bertrand Delacretaz wrote:
  
   On Mon, Jan 13, 2014 at 5:36 PM, Bertrand Delacretaz
   bdelacre...@apache.org wrote:
  
   On Mon, Jan 13, 2014 at 3:33 PM, Steve Loughran 
  ste...@hortonworks.com
   wrote:
  
   ...What do people think about a project name Hyena? It's close
   enough, lives
   in the savannah...
  
  
   I think it's too close to http://jena.apache.org/
  
  
   to be clear, this is a strong -1 from me, having confusing project
   names inside Apache is not ok. Hyena and Jena sound exactly the same
   in several languages, unfortunately.
  
  
   The j-e-n in Jena is like Jen-kins or Gen-er-al.
  
   It is derived from Jennifer
  
   http://en.wikipedia.org/wiki/Jennifer_%28given_name%29
  
   which is often, but not here, with nn:
  
   http://en.wikipedia.org/wiki/Jenna
  
   Andy
  
  
   -Bertrand
  
  
  
   -
   To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
   For additional commands, e-mail: general-h...@incubator.apache.org
  
  
 

[IP CLEARANCE][VOTE][RESULT] Sling Replication

[Tommaso Teofili]

Hi all,

since the 72hours have passed and no -1s have been cast the lazy consensus
vote for the Sling Replication IP Clearance passes.

Regards,
Tommaso


2013/11/29 Tommaso Teofili tommaso.teof...@gmail.com

 Hi all,

 Apache Sling has received the donation of a replication module. the
 process is tracked under SLING-3254 [1] and the source code patch is
 available in SLING-3223 [2].

 The IP Clearance document is placed under:
 http://incubator.apache.org/ip-clearance/sling-replication.html

 Note that we intend to place the code below:
 https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/replication
 see [2] for more details.

 Please vote to approve this contribution.  Lazy consensus applies: if no
 -1 votes are cast

 within the next 72 hours, the vote passes.

 [ ] +1 Accept Sling Replication into Apache Sling
 [ ] -1 Reject the contribution because...

 Thanks and regards,
 Tommaso

 [1] : https://issues.apache.org/jira/browse/SLING-3254
 [2] : https://issues.apache.org/jira/browse/SLING-3223

[IP CLEARANCE][VOTE] Sling Replication

[Tommaso Teofili]

Hi all,

Apache Sling has received the donation of a replication module. the process
is tracked under SLING-3254 [1] and the source code patch is available in
SLING-3223 [2].

The IP Clearance document is placed under:
http://incubator.apache.org/ip-clearance/sling-replication.html

Note that we intend to place the code below:
https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/replication
see [2] for more details.

Please vote to approve this contribution.  Lazy consensus applies: if no -1
votes are cast

within the next 72 hours, the vote passes.

[ ] +1 Accept Sling Replication into Apache Sling
[ ] -1 Reject the contribution because...

Thanks and regards,
Tommaso

[1] : https://issues.apache.org/jira/browse/SLING-3254
[2] : https://issues.apache.org/jira/browse/SLING-3223

Re: [PROPOSAL] - Java OffHeap Memory Pool

[Tommaso Teofili]

2013/4/18 Olivier Lamy ol...@apache.org

 Hi,
 Could that be part of directmemory as sub project ?


+1 or either see if there's interest in merging directly into DM (probably
requiring an IP clearance).

Tommaso



 2013/4/17 serkan özal serkanoza...@hotmail.com:
  Project Name: Jillegal
 
 
  1. Abstract:
  GC is one of the time taken operations in Java. GC run anytime, marks,
 swaps and compacts objects at memory. If there are so many live objects,
 managing them by GC leads to overhead. If objects can be allocated outside
 of GC, there will be no overhead for the application. The session will go
 through the new method of creating and using object off-heap with no
 additional serialization/deserialization or any other overheads.
 
 
  2. Proposal:
  For off-heap memory, I propose a solution that objects are allocated and
 initialized at off-heap instead of heap. Not only object attributes are
 allocated at off-heap, but also object header and metadata are allocated at
 off-heap. So while a reference to this object at off-heap is being
 interpreted, JVM knows which class this object references to. You can get
 your off-heap object from an object pool instead of with new operator.
 This object pool allocates a fixed size memory region from off-heap and
 create empty objects with given class on there. These empty objects can be
 created as lazy or eager. Another advantage off this technique is that
 objects in pool are layout in memory as sequential. While accessing an
 object, its neighbour objects are also fetched to CPU cache, so CPU cache
 hit rate for sequential object accesses are increased. On the other hand,
 freeing unused objects is responsibility of developer by calling free
 method of object pool which means there is no dead object detection
 mechanism like GC. Therefore, getting all objects from off-heap for whole
 application is dangerous and not recommended. Because, this will cause
 memory leaks. In addition, this technique can be combined with Java
 Instrumentation API. With @FromOffHeap annotation, developer can sign
 classes these must be allocated from off-heap instead of heap. With Java
 Instrumentation API, all new operators for signed classes with
 @FromOffHeap annotation can ben transformed to code that allocates
 objects of signed class from off-heap via object pool. So developer doesn't
 change all new keywords for getting from object pool in code. Instread of
 this, just sign class with @FromOffHeap annotation and all new keywords
 transformed for getting from object pool at class load time. This technique
 was used at a real time CDR processing system for Turk Telekom. There were
 billions of objects were used. Managing these objects by GC caused to
 performance overhead. For some most used classes, we allocated these
 objects from off-heap instead of new keyword. After some processings on
 them (takes 4-5 hours), we release these allocated memory regions to
 operating system by freeing them. Allocating objects from off-heap pool
 helps us to gain significant execution time performance.
 
 
  3. Rationale:
  In general, off-heap pool implementations are implemented by
 serialization/deserialization to allocated off-heap memory region via
 ByteBuffer class. But this technique leads to extra execution overhead.
 Because while reading from an object, the target object must be created by
 deserializing all primitive fields eagerly or only required fields on
 demand and while writing to an object, the attribute has been set by
 application, must be deserialized to allocated off-heap memory region. In
 addition, objects itself is created at heap, so GC knows and tracks it.
 With my solution, all of these overheads are overcomed.
 
 
  4. Initial Goals:
   * Allocating objects from off-heap and using them as normal
 on-heap Java object. * Allocating arrays for object types from
 off-heap and using them as normal on-heap Java object arrays. *
 Allocating arrays for primitive types from off-heap and using them as
 normal on-heap Java primitive type arrays. * Allocating strings
 from off-heap and using them as normal on-heap strings. *
 Implementing auto expandable off-heap pool that expands when its delegated
 off-heap pool implementation is full. * All features must be
 supported for 32 bit and 64 bit JVM. * All features must be
 supported for Sun HotSpot JVM, Oracle JRockit, IBM J9.
 
  5. Currently Implemented Features:
 
   * Allocating objects from off-heap and using them as normal
 on-heap Java object * Allocating arrays for object types from
 off-heap and using them as normal on-heap Java object array *
 Allocating arrays for primitive types from off-heap and using them as
 normal on-heap Java primitive type arrays * Implementing auto
 expandable off-heap pool that expands when its delegated off-heap pool
 implementation is full. * All features are supported for 32 bit and
 64 bit 

Re: [VOTE] Graduate Apache Onami as TLD

[Tommaso Teofili]

+1 (binding)

Tommaso


2013/3/28 Olivier Lamy ol...@apache.org

 +1 (binding)

 2013/3/26 Christian Grobmeier grobme...@gmail.com:
  Hi all,
 
  Apache Onami entered incubation before more than 3 months. Since then
  the community has proven to be pretty active and healthy.
 
  A few releases were made and the status page has been completed:
  http://incubator.apache.org/projects/onami.html
 
  Three new committers were added in the past weeks.
 
  SVNSearch shows, there is clearly one guy who is outstanding in his
  motivation, but others do commit as well:
 
 http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fonami
 
  Mailinglist Archives show the Community is discussing in public:
  http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/
 
  The community consists of new Apache-people and some more
  experienced Apache-people. I do not see any problem regarding
  developing the Apache-way.
 
  A [DISCUSS] thread on general@ showed no concerns.
 
  Simone Tripodi has been elected as the new Chair:
 
 http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/201303.mbox/%3CCAPFNckisQo29Ssy6Q-WkKgAZLRa3VW%2B7afLCEbbVy6HsWX_rAg%40mail.gmail.com%3E
 
  A resolution has been created and voted on:
 
 http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/201303.mbox/%3CCAPFNckjDujef_G6t1%3DjuTdOvuXsgxWq-%2BGntiOMdFpE%3DgwReDg%40mail.gmail.com%3E
 
  The community vote for becoming a TLD was successful too:
  http://onami-dev.markmail.org/thread/6w2dvrs3bj755kdm
 
  We now kindly ask the IPMC to review our findings and vote on the
  Onami graduation.
 
  [ ] +1, yes propose the graduation of Apache Onami to the board
  [ ] -1, no, don't let Apache Onami graduate, because...
 
 
  Thanks,
  Christian
 
  --
  http://www.grobmeier.de
  https://www.timeandbill.de
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 



 --
 Olivier Lamy
 Ecetera: http://ecetera.com.au
 http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Graduate cTAKES from Incubator

[Tommaso Teofili]

+1

Tommaso


2013/3/8 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 On Tue, Mar 5, 2013 at 10:54 PM, Chen, Pei
 pei.c...@childrens.harvard.edu wrote:
  This is to open a VOTE to graduate Apache cTAKES podling from the Apache
 Incubator.

   [x] +1 Graduate Apache cTAKES podling from Apache Incubator

 Good luck!

 BR,

 Jukka Zitting

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

Re: [VOTE] Release Apache Onami Parent 3-incubating

[Tommaso Teofili]

+1

Tommaso


2013/3/7 Simone Tripodi simonetrip...@apache.org

 Good morning incubator,

 the Apache Onami PPMC has voted Apache Onami Parent 3-incubating, and
 already got 3 IPMC binding votes from IPMC members:

  - Mohammad Nour El-Din (*)
  - Olivier Lamy (*)
  - Christian Grobmeier (*)

 We solved 5 issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314120version=12323948

 There are still a couple of issues left in JIRA:

 https://issues.apache.org/jira/issues/?jql=component%20%3D%20parent%20AND%20project%20%3D%20ONAMI%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC

 SVN source tag

 http://svn.apache.org/repos/asf/incubator/onami/tags/org.apache.onami.parent-3-incubating/

 Staging repo:
 https://repository.apache.org/content/repositories/orgapacheonami-322/

 Release artifact:

 https://repository.apache.org/content/repositories/orgapacheonami-322/org/apache/onami/org.apache.onami.parent/3-incubating/org.apache.onami.parent-3-incubating-source-release.zip

 Vote will be open for at least 72 hours and closes ~ on March 10th at
 7:30pm GMT.

 Many thanks in advance, all the best,
 -Simo

 [ ] +1, let's get it rmblee!!!
 [ ] +/-0, fine, but consider to fix few issues before...
 [ ] -1, nope, because... (and please explain why)

 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.org/

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

Re: [VOTE] Accept MRQL into the Incubator

[Tommaso Teofili]

+1

Tommaso


2013/3/6 Alex Karasulu akaras...@apache.org

 +1 (binding)


 On Wed, Mar 6, 2013 at 7:04 PM, Leonidas Fegaras fega...@cse.uta.edu
 wrote:

  Dear ASF members,
  I would like to call for a VOTE for acceptance of MRQL into the
 Incubator.
  The vote will close on Monday March 11, 2013.
 
  [ ] +1 Accept MRQL into the Apache incubator
  [ ] +0 Don't care.
  [ ] -1 Don't accept MRQL into the incubator because...
 
  Full proposal is pasted below and the corresponding wiki is
 
  http://wiki.apache.org/**incubator/MRQLProposal
 http://wiki.apache.org/incubator/MRQLProposal
 
  Only VOTEs from Incubator PMC members are binding,
  but all are welcome to express their thoughts.
  Sincerely,
  Leonidas Fegaras
 
 
  = Abstract =
 
  MRQL is a query processing and optimization system for large-scale,
  distributed data analysis, built on top of Apache Hadoop and Hama.
 
  = Proposal =
 
  MRQL (pronounced ''miracle'') is a query processing and optimization
  system for large-scale, distributed data analysis. MRQL (the MapReduce
  Query Language) is an SQL-like query language for large-scale data
  analysis on a cluster of computers. The MRQL query processing system
  can evaluate MRQL queries in two modes: in MapReduce mode on top of
  Apache Hadoop or in Bulk Synchronous Parallel (BSP) mode on top of
  Apache Hama. The MRQL query language is powerful enough to express
  most common data analysis tasks over many forms of raw ''in-situ''
  data, such as XML and JSON documents, binary files, and CSV
  documents. MRQL is more powerful than other current high-level
  MapReduce languages, such as Hive and PigLatin, since it can operate
  on more complex data and supports more powerful query constructs, thus
  eliminating the need for using explicit MapReduce code. With MRQL,
  users will be able to express complex data analysis tasks, such as
  PageRank, k-means clustering, matrix factorization, etc, using
  SQL-like queries exclusively, while the MRQL query processing system
  will be able to compile these queries to efficient Java code.
 
  = Background =
 
  The initial code was developed at the University of Texas of Arlington
  (UTA) by a research team, led by Leonidas Fegaras. The software was
  first released in May 2011. The original goal of this project was to
  build a query processing system that translates SQL-like data analysis
  queries to efficient workflows of MapReduce jobs. A design goal was to
  use HDFS as the physical storage layer, without any indexing, data
  partitioning, or data normalization, and to use Hadoop (without
  extensions) as the run-time engine. The motivation behind this work
  was to build a platform to test new ideas on query processing and
  optimization techniques applicable to the MapReduce framework.
 
  A year ago, MRQL was extended to run on Hama. The motivation for this
  extension was that Hadoop MapReduce jobs were required to read their
  input and write their output on HDFS. This simplifies reliability and
  fault tolerance but it imposes a high overhead to complex MapReduce
  workflows and graph algorithms, such as PageRank, which require
  repetitive jobs. In addition, Hadoop does not preserve data in memory
  across consecutive MapReduce jobs. This restriction requires to read
  data at every step, even when the data is constant. BSP, on the other
  hand, does not suffer from this restriction, and, under certain
  circumstances, allows complex repetitive algorithms to run entirely in
  the collective memory of a cluster. Thus, the goal was to be able to
  run the same MRQL queries in both modes, MapReduce and BSP, without
  modifying the queries: If there are enough resources available, and
  low latency and speed are more important than resilience, queries may
  run in BSP mode; otherwise, the same queries may run in MapReduce
  mode. BSP evaluation was found to be a good choice when fault
  tolerance is not critical, data (both input and intermediate) can fit
  in the cluster memory, and data processing requires complex/repetitive
  steps.
 
  The research results of this ongoing work have already been published
  in conferences (WebDB'11, EDBT'12, and DataCloud'12) and the authors
  have already received positive feedback from researchers in academia
  and industry who were attending these conferences.
 
  = Rationale =
 
  * MRQL will be the first general-purpose, SQL-like query language for
  data analysis based on BSP.
  Currently, many programmers prefer to code their MapReduce
  applications in a higher-level query language, rather than an
  algorithmic language. For instance, Pig is used for 60% of Yahoo
  MapReduce jobs, while Hive is used for 90% of Facebook MapReduce
  jobs. This, we believe, will also be the trend for BSP applications,
  because, even though, in principle, the BSP model is very simple to
  understand, it is hard to develop, optimize, and maintain non-trivial
  BSP applications coded in a general-purpose programming
  

Re: [PROPOSAL] MRQL for the Apache Incubator

[Tommaso Teofili]

Nice proposal indeed, I'd say having 3 mentors is usually better to avoid
release headaches.
Regards,
Tommaso


2013/3/4 Edward J. Yoon edwardy...@apache.org

 Sure I can. :)

 Of course, we'll welcome more mentors from incubator IPMC if there're
 volunteers.

 On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org
 wrote:
  On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz 
 bdelacre...@apache.org
  wrote:
 
  On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu
  wrote:
   == Champion ==
   * Edward J. Yoon edwardyoon AT apache DOT org
   == Nominated Mentors ==
   * Alex Karasulu akarasulu AT apache DOT org
  ...
 
  Is Edward going to stay on as a mentor as well?
 
  Two (active) mentors is the bare minimum IMO.
 
 
  I suspect so but let's hear from Edward himself.
 
  Best Regards,
  -- Alex



 --
 Best Regards, Edward J. Yoon
 @eddieyoon

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

Re: [VOTE] Accept Provisionr into the Apache Incubator

[Tommaso Teofili]

+1
Tommaso


2013/3/4 Olivier Lamy ol...@apache.org

 +1

 2013/3/3 Andrei Savu as...@apache.org:
  Hi Guys,
 
  I'd like to call a VOTE for acceptance of Provisionr into the Apache
  Incubator.
 
  The vote will close on March 8.
 
  [] +1 Accept Provisionr into the Apache incubator
  [] +0 Don't care.
  [] -1 Don't accept Provisionr into the incubator because...
 
  Full proposal is pasted at the bottom on this email, and the
 corresponding
  wiki is http://wiki.apache.org/incubator/ProvisionrProposal
 
  Only VOTEs from Incubator PMC members are binding, but all are welcome to
  express their thoughts.
 
  Thanks,
  Andrei Savu
 
  --
  Provisionr Proposal
 
  == Abstract ==
 
  Provisionr is an effort to develop a service that can be used to create
 and
  manage pools of virtual machines on multiple clouds. Our focus is on
  semi-automated workflows and cloud portability.
 
  == Proposal ==
 
  Provisionr solves the problem of cloud portability by hiding completely
 the
  APIs and only focusing on building a cluster that matches the same set of
  assumptions on all clouds, assumptions like: running a specific operating
  system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed
  packages and binaries, sane dns settings (forward  reverse ip
 resolution -
  as needed for Hadoop), ntp settings, networking settings, firewall, ssh
  admin access, vpn access etc.
 
  As a secondary goal Provisionr should also provide primitives for
 building
  automatic or semi-automatic workflows for configuring services, workflows
  that assume that all the machines share a common set of characteristics
 as
  described above.
 
  == Background ==
 
  Creating clusters on cloud infrastructure is non-trivial because careful
  orchestration is required. To make it easy to deploy services we need to
  start from a foundation that matches a common set of assumptions on
  multiple providers.
 
  == Rationale ==
 
  This project started as a re-write of the core of Apache Whirr but has a
  different target being more focused on semi-automated workflows and cloud
  portability.
 
  == Initial Goals ==
 
   * Build a community
   * Provide an excellent user experience for semi-automatic workflows
 (e.g.
  using Rundeck)
   * Implement a REST service and a Web Console
   * Add support for more providers
 
  == Current Status ==
 
  Provisionr had four releases on [[
  https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's
 used
  to deploy Hadoop clusters on-demand at Axemblr and infrastructure for
  testing / QA.
 
  === Meritocracy ===
 
  We plan to invest in supporting a meritocracy. We will discuss the
  requirements in an open forum. Several companies have already expressed
  interest in this project, and we intend to invite additional developers
 to
  participate. We will encourage and monitor community participation so
 that
  privileges can be extended to those that contribute.
 
  === Community ===
 
  The community interested in cloud service infrastructure is currently
  spread across many smaller projects, and one of the main goals of this
  project is to build a vibrant community to share best practices and build
  common infrastructure.
 
  === Core developers ===
 
  Core developers are very experienced in the Apache ecosystem. To achieve
  more diversity of developers, we will be eager to recruit developers from
  diverse companies.
 
   * Andrei Savu - asavu at apache dot org  (Apache Whirr PMC)
   * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC)
   * Alex Ciminian -  alex.ciminian at gmail dot org
 
  === Alignment ===
 
  Provisionr complements Apache Whirr and later on it should provide a
 robust
  foundation for more advanced functionalities.
 
  == Known Risks ==
 
  === Orphaned products ===
 
  The contributors have significant open source experience and the project
 is
  being used as part of a commercial product, so the risk of being orphaned
  is relatively low. We plan to mitigate this risk by recruiting additional
  committers.
 
  === Inexperience with Open Source ===
 
  Most of the initial committers have experience working on open source
  projects. Andrei Savu and Ioan Eugen Stan have experience as committers
 and
  PMC members on other Apache projects.
 
  === Homogenous Developers ===
 
  We are committed to recruiting additional committers from other companies
  based on their contributions to the project.
 
  === Reliance on Salaried Developers ===
 
  It is expected that Provisionr development will occur on both salaried
 time
  and on volunteer time, after hours. The majority of initial committers
 are
  paid by their employer to contribute to this project. However, they are
 all
  passionate about the project, and we are confident that the project will
  continue even if no salaried developers contribute to the project. We are
  committed to recruiting additional committers including non-salaried
  developers.
 
  === Relationships with Other 

Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator

[Tommaso Teofili]

+1

Tommaso


2013/2/6 Suresh Marru sma...@apache.org

 + 1 (binding)

 Cheers,
 Suresh

 On Feb 5, 2013, at 11:18 AM, Mattmann, Chris A (388J) 
 chris.a.mattm...@jpl.nasa.gov wrote:

  Hi Folks,
 
  OK, now that discussion has settled down, I'd like to call a VOTE for
  acceptance of Apache Open Climate Workbench into the Incubator.
  I'll leave the VOTE open the rest of the week and close it out next
  Monday, February 11th early am PT.
 
  [ ]  +1 Accept Apache Open Climate Workbench into the Incubator
  [ ]  +0 Don't care.
  [ ]  -1 Don't accept Apache Open Climate Workbench into the Incubator
  because...
 
  Full proposal is pasted at the bottom of this email. Only VOTEs from
  Incubator PMC members are binding, but all are welcome to express their
  thoughts.
 
  Thank you!
 
  Cheers,
  Chris
 
  P.S. Here's my +1 (binding)
 
  -
  = Apache Open Climate Workbench, tool for scalable comparison of remote
  sensing observations to climate model outputs, regionally and globally. =
  === Abstract ===
  The Apache Open Climate Workbench proposal desires to contribute an
  existing community of software related to the analysis and evaluation of
  climate models, and related to the use of remote sensing data in that
  process.
 
  Specifically, we will bring a fundamental software toolkit for analysis
  and evaluation of climate model output against remote sensing data. The
  toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model
  Evaluation System (RCMES)]]. RCMES provides two fundamental components
 for
  the easy, intuitive comparison of climate model output against remote
  sensing data. The first component called RCMED (for Regional Climate
  Model Evaluation Database) is a scalable cloud database that decimates
  remote sensing data and renalysis data related to climate using Apache
  OODT extractors, Apache Tika, etc. These transformations make
  traditionally heterogeneous upstream remote sensing data and climate
 model
  output homogeneous and unify them into a data point model of the form
  (lat, lng, time, value, height) on a per parameter basis. Latitude (lat)
  and Longitude (lng) are in WGS84 format, but can be reformatted on the
  fly. time is in ISO 8601 format, a string sortable format independent of
  underlying store. value carries with it units, related to interpretation
  and height allows for different values for different atmospheric vertical
  levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop
  and Apache Hive, along with hooks to PostGIS and MySQL (traditional
  relational databases). The second component of the system, RCMET (for
  Regional Climate Model Evaluation Toolkit) provides facilities for
  connecting to RCMED, dynamically obtaining remote sensing data for a
  space/time region of interest, grabbing associated model output (that the
  user brings, or from the Earth System Grid Federation) of the same form,
  and then regridding the remote sensing data to be on the model output
  grid, or the model output to be on the remote sensing data grid. The
  regridded data spatially is then temporally regridded using techniques
  including seasonal cycle compositing (e.g., all summer months, all
  Januaries, etc.), or by daily, monthly, etc. The uniform model output and
  remote sensing data are then analyzed using pluggable metrics, e.g.,
  Probability Distribution Functions (PDFs), Root Mean Squared Error
 (RMSE),
  Bias, and other (possibly user-defined) techniques, computing an analyzed
  comparison or evaluation. This evaluation is then visualized by plugging
  in to the NCAR NCL library for producing static plots (histograms, time
  series, etc.)
 
  We also have performed a great deal of work in packaging RCMES to make
 the
  system easy to deploy. We have working Virtual Machines (VMWare VMX and
  Virtual Box OVA compatible formats) and we also have an installer built
 on
  Python Buildout (http://buildout.org/) called Easy RCMET for
 dynamically
  constructing the RCMET toolkit.
 
  RCMES is currently supporting a number of recognized climate projects of
  (inter-)national significance. In particular, RCMES is supporting the
  [[http://www.globalchange.gov/what-we-do/assessment|U.S. National
 Climate
  Assessment (NCA) activities]] on behalf of NASA's contribution to the
 NCA;
  is working with the [[http://www.narccap.ucar.edu/|North American
 Regional
  Climate Change Assessment Program (NARCCAP)]]; and is also working with
  the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated
  Regional Downscaling Experiment (CORDEX)]].
 
  === Proposal ===
  We propose to transition the RCMES software community, which includes
  developers of the RCMET and RCMED software, along with users of RCMES in
  the CORDEX project across a variety of academic institutions, scientists
  helping to improve the RCMES metrics, and visualizations, and regridding
  algorithms, packagers making RCMES easier to install, and 

Re: [VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

thanks Bertrand, I just realized that.
Sorry for the delay, I didn't know Fabian is in the IPMC (sorry Fabian).

Tommaso


2013/1/30 Bertrand Delacretaz bdelacre...@apache.org

 On Fri, Jan 25, 2013 at 9:25 AM, Tommaso Teofili
 tommaso.teof...@gmail.com wrote:
  ...we just need one more vote, please anyone?...

 You do have 3 IPMC members vote in this thread: yourself, Fabian and
 myself.

 -Bertrand

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

[RESULT][VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

The Apache Clerezza Graduation Resolution vote [1] passes with 3 binding
+1s and 1 non binding +1s from the following people:
- Bertrand Delacretaz*
- Fabian Christ*
- Tommaso Teofili*
- Andreas Kuckartz

no other votes were collected.
Regards,
Tommaso

[1] : http://markmail.org/message/l3qbhqk4yvn7rmha


2013/1/18 Tommaso Teofili tommaso.teof...@gmail.com

 Hi all,

 as per [VOTE][RESULT] on clerezza-dev@i.a.o mailing list [1] and after
 having successfully completed podling name search [2] I'm opening the vote
 for the below Apache Clerezza TLP graduation resolution.

 X. Establish the Apache Clerezza 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, for distribution at no charge to
 the public, related to Apache Clerezza platform.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Clerezza Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Clerezza Project be and hereby is
responsible for the creation and maintenance of software
related to an OSGi-based modular application and set of
components for building RESTFul Semantic Web applications and
 services;
and be it further

RESOLVED, that the office of Vice President, Apache Clerezza 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 Clerezza Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Clerezza 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 Clerezza Project:

  * Reto Bachmann-Gmuer r...@apache.org
  * Tsuyoshi Ito i...@apache.org
  * Hasan Hasan   ha...@apache.org
  * Tommaso Teofili tomm...@apache.org
  * Bertrand Delacretaz   bdelacre...@apache.org
  * Florent André   flor...@apache.org
  * Rupert Westenthaler rwes...@apache.org
  * Daniel Spicar  dspi...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
be appointed to the office of Vice President, Apache Clerezza, 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 initial Apache Clerezza PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Clerezza Project; and be it further

RESOLVED, that the Apache Clerezza Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Clerezza podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Clerezza podling encumbered upon the Apache Incubator
Project are hereafter discharged.

 Please cast your votes:
 [ ] +1 Graduate Apache Clerezza podling from Apache Incubator
 [ ] +0 Indifferent to the graduation status of Apache Clerezza podling
 [ ] -1 Reject graduation of Apache Clerezza podling from Apache Incubator
 because ...

 Vote is open for the next 72 hours thus it'll close on January 21st at
 12.00 CET.

 Regards,
 Tommaso


 [1] :
 http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201301.mbox/%3CCAGnSx07PHaN9nbRrbFzFpRQyODuj1XJXnAEXYffyMxWD47m0Gw%40mail.gmail.com%3E
 [2] : https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-20

Re: [VOTE] Apache Ambari (incubating) 1.2.0 Release Candidate RC0.

[Tommaso Teofili]

ok thanks, it worked now, therefore my +1.

Tommaso


2013/1/29 Hitesh Shah hit...@hortonworks.com

 Hi Tommaso,

 There are setup steps mentioned at
 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development for
 getting Ambari to build.
 The web layer requires node.js and brunch.

 thanks
 -- Hitesh

 On Jan 28, 2013, at 11:05 PM, Tommaso Teofili wrote:

  If I download the SVN tag and run 'mvn install'
 
  I get the following:
 
  [INFO] Reactor Summary:
  [INFO]
  [INFO] Ambari Main ... SUCCESS
 [9.258s]
  [INFO] Apache Ambari Project POM . SUCCESS
 [0.045s]
  [INFO] Ambari Web  FAILURE
 [1.744s]
  [INFO] Ambari Server . SKIPPED
  [INFO] Ambari Agent .. SKIPPED
  [INFO]
  
  [INFO] BUILD FAILURE
  [INFO]
  
  [INFO] Total time: 56.720s
  [INFO] Finished at: Mon Jan 28 15:06:56 CET 2013
  [INFO] Final Memory: 8M/81M
  [INFO]
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile) on project
  ambari-web: An Ant BuildException has occured: Execute failed:
  java.io.IOException: Cannot run program npm (in directory
  /Users/user/Desktop/amb/ambari-web): error=2, No such file or directory
  [ERROR] around Ant part ...exec dir=/Users/user/Desktop/amb/ambari-web
  executable=npm failonerror=false... @ 4:90 in
 
 /Users/user/Desktop/amb/ambari-web/target/antrun/build-ambari-web-compile.xml
  [ERROR] - [Help 1]
  [ERROR]
  [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e
  switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR]
  [ERROR] For more information about the errors and possible solutions,
  please read the following articles:
  [ERROR] [Help 1]
  http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
  [ERROR]
  [ERROR] After correcting the problems, you can resume the build with the
  command
  [ERROR]   mvn goals -rf :ambari-web
 
  am I missing anything?
 
  Apart from that it looks good.
 
  Tommaso
 
 
  2013/1/28 Mahadev Konar maha...@apache.org
 
  Hi everyone,
 
  This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote
  was held on developer mailing list and it
  passed with 8 +1's with 6 of them binding.
 
  mahadev (IPMC, PPMC)
  ddas (IPMC, PPMC)
  acmurthy (IPMC)
  jitendra (PPMC)
  hitesh (PPMC)
  yusaku (PPMC)
 
 
 
 http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E
 
 
  The staging Staging site is:
  http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/
 
  with user docs at:
 
 
 http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html
  and dev docs at:
  https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development
 
  SVN source tag:
 
 https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0
 
  PGP release keys (signed using 8EE2F25C)
  http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C
 
  One can look into the issues fixed in this release at
 
 
 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI
 
  Vote will be open for 72 hours.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)
 
  thanks
  mahadev
 
  -
  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 Ambari (incubating) 1.2.0 Release Candidate RC0.

[Tommaso Teofili]

If I download the SVN tag and run 'mvn install'

I get the following:

[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ... SUCCESS [9.258s]
[INFO] Apache Ambari Project POM . SUCCESS [0.045s]
[INFO] Ambari Web  FAILURE [1.744s]
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 56.720s
[INFO] Finished at: Mon Jan 28 15:06:56 CET 2013
[INFO] Final Memory: 8M/81M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile) on project
ambari-web: An Ant BuildException has occured: Execute failed:
java.io.IOException: Cannot run program npm (in directory
/Users/user/Desktop/amb/ambari-web): error=2, No such file or directory
[ERROR] around Ant part ...exec dir=/Users/user/Desktop/amb/ambari-web
executable=npm failonerror=false... @ 4:90 in
/Users/user/Desktop/amb/ambari-web/target/antrun/build-ambari-web-compile.xml
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :ambari-web

am I missing anything?

Apart from that it looks good.

Tommaso


2013/1/28 Mahadev Konar maha...@apache.org

 Hi everyone,

  This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote
 was held on developer mailing list and it
  passed with 8 +1's with 6 of them binding.

  mahadev (IPMC, PPMC)
  ddas (IPMC, PPMC)
  acmurthy (IPMC)
  jitendra (PPMC)
  hitesh (PPMC)
  yusaku (PPMC)


 http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E


 The staging Staging site is:
 http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/

 with user docs at:

 http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html
 and dev docs at:
 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development

  SVN source tag:
  https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0

  PGP release keys (signed using 8EE2F25C)
  http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C

 One can look into the issues fixed in this release at

 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI

 Vote will be open for 72 hours.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)

 thanks
 mahadev

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

Re: [VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

just to confirm my binding vote (already expressed on clerezza-dev@):

+1

Tommaso

p.s.
we just need one more vote, please anyone?


2013/1/22 Tommaso Teofili tommaso.teof...@gmail.com




 2013/1/22 Bertrand Delacretaz bdelacre...@apache.org

 Hi,

 On Mon, Jan 21, 2013 at 11:22 AM, Tommaso Teofili
 tommaso.teof...@gmail.com wrote:
  ...should i cancel and re open the vote with the
  updated paragraph?...

 I suggest that you just reply to this message with the modified
 version of that first paragraph that you suggest, and wait 24 hours in
 case anyone complains - that's doesn't change the essence of the vote,
 so no need to restart the vote IMO.



 ok perfect, thanks Bertrand.
 Here's the resolution updated as per Suresh's suggestion.

 X. Establish the Apache Clerezza 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, for distribution at no charge to
the public, related to an OSGi-based modular application and
set of components for building RESTFul Semantic Web applications
and services.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Clerezza Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Clerezza Project be and hereby is
responsible for the creation and maintenance of software
related to an OSGi-based modular application and set of
components for building RESTFul Semantic Web applications and
 services;
and be it further

RESOLVED, that the office of Vice President, Apache Clerezza 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 Clerezza Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Clerezza 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 Clerezza Project:

  * Reto Bachmann-Gmuer r...@apache.org
  * Tsuyoshi Ito i...@apache.org
  * Hasan Hasan   ha...@apache.org
  * Tommaso Teofili tomm...@apache.org
  * Bertrand Delacretaz   bdelacre...@apache.org
  * Florent André   flor...@apache.org
  * Rupert Westenthaler rwes...@apache.org
  * Daniel Spicar  dspi...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
be appointed to the office of Vice President, Apache Clerezza, 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 initial Apache Clerezza PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Clerezza Project; and be it further

RESOLVED, that the Apache Clerezza Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Clerezza podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Clerezza podling encumbered upon the Apache Incubator
Project are hereafter discharged.

 Regards,
 Tommaso

 p.s.:
 keep voting :-)

Re: [VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

2013/1/22 Bertrand Delacretaz bdelacre...@apache.org

 Hi,

 On Mon, Jan 21, 2013 at 11:22 AM, Tommaso Teofili
 tommaso.teof...@gmail.com wrote:
  ...should i cancel and re open the vote with the
  updated paragraph?...

 I suggest that you just reply to this message with the modified
 version of that first paragraph that you suggest, and wait 24 hours in
 case anyone complains - that's doesn't change the essence of the vote,
 so no need to restart the vote IMO.



ok perfect, thanks Bertrand.
Here's the resolution updated as per Suresh's suggestion.

X. Establish the Apache Clerezza 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, for distribution at no charge to
   the public, related to an OSGi-based modular application and
   set of components for building RESTFul Semantic Web applications
   and services.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Clerezza Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Clerezza Project be and hereby is
   responsible for the creation and maintenance of software
   related to an OSGi-based modular application and set of
   components for building RESTFul Semantic Web applications and
services;
   and be it further

   RESOLVED, that the office of Vice President, Apache Clerezza 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 Clerezza Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Clerezza 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 Clerezza Project:

 * Reto Bachmann-Gmuer r...@apache.org
 * Tsuyoshi Ito i...@apache.org
 * Hasan Hasan   ha...@apache.org
 * Tommaso Teofili tomm...@apache.org
 * Bertrand Delacretaz   bdelacre...@apache.org
 * Florent André   flor...@apache.org
 * Rupert Westenthaler rwes...@apache.org
 * Daniel Spicar  dspi...@apache.org

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
   be appointed to the office of Vice President, Apache Clerezza, 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 initial Apache Clerezza PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Clerezza Project; and be it further

   RESOLVED, that the Apache Clerezza Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Clerezza podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Clerezza podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

Regards,
Tommaso

p.s.:
keep voting :-)

Re: [VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

Thanks Suresh for your tip, should i cancel and re open the vote with the
updated paragraph?

Tommaso


2013/1/18 Suresh Marru sma...@apache.org

 Hi Tommaso,

 As per the template [1], the first paragraph of the resolution should have
 ${DESCRIPTION-AND-SCOPE} you currently only have the project name which is
 not introduced until the second paragraph.

 May be you want to consider changing:
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, for distribution at no charge to
the public, related to Apache Clerezza platform.

 to

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, for distribution at no charge to
the public, related to an OSGi-based modular application and set of
components for building RESTFul Semantic Web applications and
  services.


 Cheers,
 Suresh

 [1]  -
 https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt


 On Jan 18, 2013, at 6:02 AM, Tommaso Teofili tommaso.teof...@gmail.com
 wrote:

  Hi all,
 
  as per [VOTE][RESULT] on clerezza-dev@i.a.o mailing list [1] and after
  having successfully completed podling name search [2] I'm opening the
 vote
  for the below Apache Clerezza TLP graduation resolution.
 
  X. Establish the Apache Clerezza 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, for distribution at no charge to
the public, related to Apache Clerezza platform.
 
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Clerezza Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
 
RESOLVED, that the Apache Clerezza Project be and hereby is
responsible for the creation and maintenance of software
related to an OSGi-based modular application and set of
components for building RESTFul Semantic Web applications and
  services;
and be it further
 
RESOLVED, that the office of Vice President, Apache Clerezza 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 Clerezza Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Clerezza 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 Clerezza Project:
 
  * Reto Bachmann-Gmuer r...@apache.org
  * Tsuyoshi Ito i...@apache.org
  * Hasan Hasan   ha...@apache.org
  * Tommaso Teofili tomm...@apache.org
  * Bertrand Delacretaz   bdelacre...@apache.org
  * Florent André   flor...@apache.org
  * Rupert Westenthaler rwes...@apache.org
  * Daniel Spicar  dspi...@apache.org
 
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
be appointed to the office of Vice President, Apache Clerezza, 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 initial Apache Clerezza PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Clerezza Project; and be it further
 
RESOLVED, that the Apache Clerezza Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Clerezza podling; and be it further
 
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Clerezza podling encumbered upon the Apache Incubator
Project are hereafter discharged.
 
  Please cast your votes:
  [ ] +1 Graduate Apache Clerezza podling from Apache Incubator
  [ ] +0 Indifferent to the graduation status of Apache Clerezza podling
  [ ] -1 Reject graduation of Apache Clerezza podling from Apache Incubator
  because ...
 
  Vote is open

[jira] [Created] (PODLINGNAMESEARCH-20) Establish whether Apache Clerezza is a suitable name

[Tommaso Teofili (JIRA)]

Tommaso Teofili created PODLINGNAMESEARCH-20:


 Summary: Establish whether Apache Clerezza is a suitable name
 Key: PODLINGNAMESEARCH-20
 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-20
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Tommaso Teofili


A suitable name search is required in order for Clerezza to graduate from the 
incubation. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[VOTE] - Apache Clerezza Graduation Resolution

[Tommaso Teofili]

Hi all,

as per [VOTE][RESULT] on clerezza-dev@i.a.o mailing list [1] and after
having successfully completed podling name search [2] I'm opening the vote
for the below Apache Clerezza TLP graduation resolution.

X. Establish the Apache Clerezza 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, for distribution at no charge to
   the public, related to Apache Clerezza platform.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Clerezza Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Clerezza Project be and hereby is
   responsible for the creation and maintenance of software
   related to an OSGi-based modular application and set of
   components for building RESTFul Semantic Web applications and
services;
   and be it further

   RESOLVED, that the office of Vice President, Apache Clerezza 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 Clerezza Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Clerezza 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 Clerezza Project:

 * Reto Bachmann-Gmuer r...@apache.org
 * Tsuyoshi Ito i...@apache.org
 * Hasan Hasan   ha...@apache.org
 * Tommaso Teofili tomm...@apache.org
 * Bertrand Delacretaz   bdelacre...@apache.org
 * Florent André   flor...@apache.org
 * Rupert Westenthaler rwes...@apache.org
 * Daniel Spicar  dspi...@apache.org

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
   be appointed to the office of Vice President, Apache Clerezza, 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 initial Apache Clerezza PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Clerezza Project; and be it further

   RESOLVED, that the Apache Clerezza Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Clerezza podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Clerezza podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

Please cast your votes:
[ ] +1 Graduate Apache Clerezza podling from Apache Incubator
[ ] +0 Indifferent to the graduation status of Apache Clerezza podling
[ ] -1 Reject graduation of Apache Clerezza podling from Apache Incubator
because ...

Vote is open for the next 72 hours thus it'll close on January 21st at
12.00 CET.

Regards,
Tommaso


[1] :
http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201301.mbox/%3CCAGnSx07PHaN9nbRrbFzFpRQyODuj1XJXnAEXYffyMxWD47m0Gw%40mail.gmail.com%3E
[2] : https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-20

[jira] [Commented] (PODLINGNAMESEARCH-12) Establish whether Apache Amber is a suitable name

[Tommaso Teofili (JIRA)]

[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526457#comment-13526457
 ] 

Tommaso Teofili commented on PODLINGNAMESEARCH-12:
--

bq. http://amber-lang.net/

with a logo which is 'awfully' similar to the current Apache Amber one...

 Establish whether Apache Amber is a suitable name
 ---

 Key: PODLINGNAMESEARCH-12
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Antonio Sanso

 We have to do some investigations to ensure that Apache Amber is a suitable 
 name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Comment Edited] (PODLINGNAMESEARCH-12) Establish whether Apache Amber is a suitable name

[Tommaso Teofili (JIRA)]

[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526457#comment-13526457
 ] 

Tommaso Teofili edited comment on PODLINGNAMESEARCH-12 at 12/7/12 3:32 PM:
---

 http://amber-lang.net/

with a logo which is 'awfully' similar to the current Apache Amber one...

  was (Author: teofili):
bq. http://amber-lang.net/

with a logo which is 'awfully' similar to the current Apache Amber one...
  
 Establish whether Apache Amber is a suitable name
 ---

 Key: PODLINGNAMESEARCH-12
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Antonio Sanso

 We have to do some investigations to ensure that Apache Amber is a suitable 
 name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Re: [VOTE] Stanbol to graduate from the incubator

[Tommaso Teofili]

+1 (binding).

Tommaso

2012/9/5 Fabian Christ christ.fab...@googlemail.com

 Hi,

 the Stanbol podling has discussed [1] that we are ready for
 graduation. The project has created two releases during incubation and
 created an active community around the topic of semantic content
 management. The PPMC internal vote for a resolution to establish the
 project got positive feedback [2].

 We are now asking the IPMC to vote on the resolution to establish
 Stanbol and to recommend the resolution to the board. The resolution
 to vote on is also available online [3].

 [1] http://markmail.org/thread/6shesliws7naqgit
 [2] http://markmail.org/thread/ml3pfnz3ttmmpe5g
 [3] http://incubator.apache.org/stanbol/graduation-resolution.html

 ===

 X. Establish the Apache Stanbol 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 a set of reusable components
for semantic content management 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 Stanbol Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Stanbol Project be and hereby is
responsible for the creation and maintenance of software
related to a set of reusable components for semantic
content management; and be it further

RESOLVED, that the office of Vice President, Apache Stanbol 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 Stanbol Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Stanbol 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 Stanbol Project:

  * Alessandro Adamoualex...@apache.org
  * Andrea Nuzzolese anuzzol...@apache.org
  * Andreas Gruber   agru...@apache.org
  * Andreas Kuckartz a...@apache.org
  * Benjamin Nagel   bna...@apache.org
  * Bertrand Delacretaz  bdelacre...@apache.org
  * Cihan Cimen  ci...@apache.org
  * Concetto Bonafedeconcel...@apache.org
  * Enrico Daga  enrid...@apache.org
  * Fabian Christfchr...@apache.org
  * Florent Andréflor...@apache.org
  * Olivier Grisel   ogri...@apache.org
  * Ozgur Kilic  oz...@apache.org
  * Reto Bachmann-Gmür   r...@apache.org
  * Rupert Westenthaler  rup...@apache.org
  * Suat Gonul   s...@apache.org
  * Szaby Grünwald   sza...@apache.org
  * Tommaso Teofili  tomm...@apache.org
  * Valentina Presutti   v...@apache.org
  * Walter Kasperwkas...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Fabian Christ
be appointed to the office of Vice President, Apache Stanbol, 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 initial Apache Stanbol PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Stanbol Project; and be it further

RESOLVED, that the Apache Stanbol Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Stanbol podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Stanbol podling encumbered upon the Apache Incubator
Project are hereafter discharged.


 --
 Fabian
 http://twitter.com/fctwitt

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

Re: Clerezza status (Was: [Incubator Wiki] Update of August2012 by BertrandDelacretaz)

[Tommaso Teofili]

Hi Jukka,

2012/8/9 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 On Mon, Aug 6, 2012 at 11:26 AM, Apache Wiki wikidi...@apache.org wrote:
  +   As in our last report in May, we believe Clerezza should graduate
 soon, but
  +   unfortunately that hasn't happened yet. Activity is currently fairly
 low,
  +   and it looks like Clerezza might remain a small/low activity
 project, but
  +   the PPMC is functional, has done releases and invited additional
 committers
  +   so there's no need to stay in the Incubator any longer once a plan
 to attempt
  +   to grow the community is in place.

 Do you have an idea what happened around a year ago when dev@ activity
 dropped from the hundreds it was for a long time to the dozens where
 it's mostly stayed since then? Alarmingly the low mark seems to have
 been last month when only a single non-automated post was sent to
 dev@.


As far as I can understand that mostly depends on some of the most active
salaried developers got a new job thus they weren't able to keep up the
same contribution rate to the project.
Also, if I remember correctly, some discussions about the Clerezza security
module were quite hot and that may have played a role in this, but
actually I don't think that's the main reason.



 I recall Clerezza having release trouble due to complex/unreleased
 dependencies for a long time. Could that have contributed to the loss
 of momentum? I think it would be useful to somehow capture experience
 like this, perhaps ultimately for use by ComDev in something like a
 How to maintain community momentum? guide.


While I think that guide would be very useful (even if it'd quite hard to
grasp the very deep reasons / solutions) I think the unreleased
dependencies problem was resolved in not so long time.

I think the main reason for the low activity lately is related to the
previous point about salaried devs and to the fact that the most commonly
used pieces of Clerezza (e.g. the RDF API in Apache Stanbol) look quite ok
and stable requiring a minimal development effort.
At the same time there are a number of improvements that the PPMC is aware
of and that could be done.
Another hurdle to newcomers is in my opinion the huge number of modules /
pieces Clerezza is made of which may look scaring at first :-)



 Anyway, it sounds like the community has a reasonably good idea on how
 to proceed, so I'm not too worried yet even though Clerezza is already
 getting pretty close to its three-year mark at the Incubator. Though
 I'd really love to see Clerezza showing notable improvement or even
 graduating before that milestone is reached.


sure, +1.



 If the efforts to grow or reactivate the community fail, would it be a
 good idea to seek to join forces with some related projects like
 Stanbol, Any23 or UIMA? Or do you feel that there are still enough
 active people to allow the project to function as a standalone TLP
 (able to reach 3 PMC votes for releases, etc.)?


I've not a strong opinion at the moment, I think Clerezza could be a nice
TLP but at the same time I wonder if merging efforts with Apache Stanbol
could be a better idea.
I see lots of discussions about the Clerezza API happening on
stanbol-dev@(since it's massively using it), and the two PPMCs share a
number of
members, however there could be good points against that merge (first of
all: different high level scopes).
Therefore my very early opinion is that Clerezza should go for TLP but
after having cleaned its structure based on the most commonly used modules,
tweak the website / docs in order to focus on providing users / devs with a
smaller set of outstanding features.

My 2 cents,
Tommaso



 BR,

 Jukka Zitting

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

Re: [VOTE] Accept Drill into the Apache Incubator

[Tommaso Teofili]

+1

Tommaso

2012/8/8 Ted Dunning ted.dunn...@gmail.com

 I would like to call a vote for accepting Drill for incubation in the
 Apache Incubator. The full proposal is available below.  Discussion
 over the last few days has been quite positive.

 Please cast your vote:

 [ ] +1, bring Drill into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Drill into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.  The start of the vote is just before 3AM UTC on 8
 August so the closing time will be 3AM UTC on 11 August.

 Thank you for your consideration!

 Ted

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

 = Drill =

 == Abstract ==
 Drill is a distributed system for interactive analysis of large-scale
 datasets, inspired by
 [[http://research.google.com/pubs/pub36632.html|Google's Dremel]].

 == Proposal ==
 Drill is a distributed system for interactive analysis of large-scale
 datasets. Drill is similar to Google's Dremel, with the additional
 flexibility needed to support a broader range of query languages, data
 formats and data sources. It is designed to efficiently process nested
 data. It is a design goal to scale to 10,000 servers or more and to be
 able to process petabyes of data and trillions of records in seconds.

 == Background ==
 Many organizations have the need to run data-intensive applications,
 including batch processing, stream processing and interactive
 analysis. In recent years open source systems have emerged to address
 the need for scalable batch processing (Apache Hadoop) and stream
 processing (Storm, Apache S4). In 2010 Google published a paper called
 Dremel: Interactive Analysis of Web-Scale Datasets, describing a
 scalable system used internally for interactive analysis of nested
 data. No open source project has successfully replicated the
 capabilities of Dremel.

 == Rationale ==
 There is a strong need in the market for low-latency interactive
 analysis of large-scale datasets, including nested data (eg, JSON,
 Avro, Protocol Buffers). This need was identified by Google and
 addressed internally with a system called Dremel.

 In recent years open source systems have emerged to address the need
 for scalable batch processing (Apache Hadoop) and stream processing
 (Storm, Apache S4). Apache Hadoop, originally inspired by Google's
 internal MapReduce system, is used by thousands of organizations
 processing large-scale datasets. Apache Hadoop is designed to achieve
 very high throughput, but is not designed to achieve the sub-second
 latency needed for interactive data analysis and exploration. Drill,
 inspired by Google's internal Dremel system, is intended to address
 this need.

 It is worth noting that, as explained by Google in the original paper,
 Dremel complements MapReduce-based computing. Dremel is not intended
 as a replacement for MapReduce and is often used in conjunction with
 it to analyze outputs of MapReduce pipelines or rapidly prototype
 larger computations. Indeed, Dremel and MapReduce are both used by
 thousands of Google employees.

 Like Dremel, Drill supports a nested data model with data encoded in a
 number of formats such as JSON, Avro or Protocol Buffers. In many
 organizations nested data is the standard, so supporting a nested data
 model eliminates the need to normalize the data. With that said, flat
 data formats, such as CSV files, are naturally supported as a special
 case of nested data.

 The Drill architecture consists of four key components/layers:
  * Query languages: This layer is responsible for parsing the user's
 query and constructing an execution plan.  The initial goal is to
 support the SQL-like language used by Dremel and
 [[https://developers.google.com/bigquery/docs/query-reference|Google
 BigQuery]], which we call DrQL. However, Drill is designed to support
 other languages and programming models, such as the
 [[http://www.mongodb.org/display/DOCS/Mongo+Query+Language|Mongo Query
 Language]], [[http://www.cascading.org/|Cascading]] or
 [[https://github.com/tdunning/Plume|Plume]].
  * Low-latency distributed execution engine: This layer is responsible
 for executing the physical plan. It provides the scalability and fault
 tolerance needed to efficiently query petabytes of data on 10,000
 servers. Drill's execution engine is based on research in distributed
 execution engines (eg, Dremel, Dryad, Hyracks, CIEL, Stratosphere) and
 columnar storage, and can be extended with additional operators and
 connectors.
  * Nested data formats: This layer is responsible for supporting
 various data formats. The initial goal is to support the column-based
 format used by Dremel. Drill is designed to support schema-based
 formats such as Protocol Buffers/Dremel, Avro/AVRO-806/Trevni and CSV,
 and schema-less formats such as JSON, BSON or YAML. In addition, it is
 designed to support column-based formats such as Dremel,
 AVRO-806/Trevni and RCFile, and row-based 

Re: [VOTE] Graduation of DirectMemory as a TLP

[Tommaso Teofili]

+1

Tommaso

2012/8/1 Tim Williams william...@gmail.com

 The DirectMemory community is ready to graduate and become a full TLP.
  We began incubation in October 2011 and have demonstrated our ability
 to function according to the Apache Way.  We've successfully made a
 release.  We have begun to grow the community.  We didn't hold a
 separate formal vote - it's not a requirement - but the sense of the
 community is that we're ready to go[1].

 Please VOTE to submit the below resolution to the board for consideration:

 [ ] +1 DirectMemory graduates to TLP
 [ ] -1 DirectMemory isn't ready, because...

 Vote will remain open for 72hrs...

 Thanks,
 --tim

 [1] - http://markmail.org/thread/3j4q7xehzn72dhk4



 X. Resolution to establish the Apache DirectMemory 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 a
second level, off-heap, cache able to store large amounts of
 data without filling
up the Java heap and thus avoiding long garbage collection cycles.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the The Apache DirectMemory
 Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that The Apache DirectMemory Project be and hereby is
responsible for the creation and maintenance of a software
project related to a second level off-heap cache; and be it further

RESOLVED, that the office of Vice President, DirectMemory 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
DirectMemory Project, and to have primary responsibility for
management of the projects within the scope of responsibility of
The Apache DirectMemory 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 DirectMemory Project:

  * Ioannic Canellos (iocanel)
  * Maurizio Cucchiara (mcucchiara)
  * Christian Grobmeier (grobmeier)
  * Olivier Lamy (olamy)
  * Raffaele P. Guidi (raffaeleguidi)
  * Simone Gianni (simoneg)
  * Simone Tripodi (simonetripodi)
  * Tommaso Teofill (tommaso)
  * Benoit Perroud (bperroud)

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Raffaele P.
Guidi be and hereby is appointed to the office of Vice
President, DirectMemory, 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 initial Apache DirectMemory Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DirectMemory podling; and be it further

RESOLVED, that all responsibility pertaining to the Apache
Incubator DirectMemory podling encumbered upon the Apache Incubator
PMC are hereafter discharged.

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

Re: [VOTE] Release Apache Amber 0.22-incubating

[Tommaso Teofili]

Anyone else from the IPMC willing to review this ?
Thanks in advance,
Tommaso

2012/7/21 Raymond Feng enjoyj...@gmail.com

 +1 from me.

 Thanks,
 Raymond

 On Jul 18, 2012, at 12:33 AM, Simone Tripodi wrote:

  Good morning IPMC,
 
  I'm writing today to submit you the VOTE of the first release ever of
  Apache Amber 0.22 under the Incubator.
 
  PPMC vote already passed on amber-dev@ http://s.apache.org/Ulr with
  already 1 IPMC binding vote.
 
  We solved 28 issues:
 
 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311100styleName=Htmlversion=12322240
 
  There are still 14 issues left in JIRA:
 
 http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12311100status=1
 
  SVN source tag (r1359173):
 
 https://svn.apache.org/repos/asf/incubator/amber/tags/amber-0.22-incubating/
 
  Staging repo:
  https://repository.apache.org/content/repositories/orgapacheamber-039/
 
  Staging binaries:
  http://people.apache.org/builds/incubator/amber/
 
  Staging site:
  http://incubator.apache.org/amber/0.22-incubating/
 
  PGP release keys (signed using 19FEA27D):
  http://www.apache.org/dist/incubator/amber/KEYS
 
  Vote will be open for 72 hours and will close ~ on July the 21th at
 7:30am GMT
 
  [ ] +1, let's get it rmblee!!!
  [ ] +/-0, fine, but consider to fix few issues before...
  [ ] -1, nope, because... (and please explain why)
 
  Many thanks in advance, all the best!
  -Simo
 
  http://people.apache.org/~simonetripodi/
  http://simonetripodi.livejournal.com/
  http://twitter.com/simonetripodi
  http://www.99soft.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: [VOTE] Accept Blur into the Apache Incubator

[Tommaso Teofili]

+1

Tommaso

2012/7/20 Aaron McCurry amccu...@gmail.com

 I would like to call a vote for accepting Blur for incubation in the
 Apache Incubator. The full proposal is available below.

 Please cast your vote:

 [ ] +1, bring Blur into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Blur into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.

 Thank you for your consideration!

 Aaron

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

 = Blur Proposal =

 == Abstract ==
 Blur is a search platform capable of searching massive amounts of data
 in a cloud computing environment. Blur leverages several existing
 Apache projects, including Apache Lucene, Apache Hadoop, Apache
 !ZooKeeper and Apache Thrift.  Both bulk and near real time (NRT)
 updates are possible with Blur.  Bulk updates are accomplished using
 Hadoop Map/Reduce and NRT are performed through direct Thrift calls.

 == Proposal ==
 Blur is an open source search platform capable of querying massive
 amounts of data at incredible speeds. Rather than using the flat,
 document-like data model used by most search solutions, Blur allows
 you to build rich data models and search them in a semi-relational
 manner similar to joins while querying a relational database. Using
 Blur, you can get precise search results against terabytes of data at
 Google-like speeds.  Blur leverages multiple open source projects
 including Hadoop, Lucene, Thrift and !ZooKeeper to create an
 environment where structured data can be transformed into an index
 that runs on a Hadoop cluster.  Blur uses the power of Map/Reduce for
 bulk indexing into Blur.  Server failures are handled automatically by
 using !ZooKeeper for cluster state and HDFS for index storage.

 == Background ==
 Blur was created by Aaron !McCurry in 2010. Blur was developed to
 solve the challenges in dealing with searching huge quantities of data
 that the traditional RDBMS solutions could not cope with while still
 providing JOIN-like capabilities to query the data.  Several other
 open source projects have implemented aspects of this design including
 elasticsearch, Katta and Apache Solr.

 == Rationale ==
 There is a need for a distributed search capability within the Hadoop
 ecosystem. Currently, there are no other search solutions that
 natively leverage HDFS and the failover features of Hadoop in the same
 manner as the Blur project. The communities we expect to be most
 interested in such a project are government, health care, and other
 industries where scalability is a concern. We have made much progress
 in developing this project over the past 2 years and believe both the
 project and the interested communities would benefit from this work
 being openly available and having open development.  In future
 versions of Blur the API will more closely follow the API’s provided
 in Lucene so that systems that already use Lucene can more easily
 scale with Blur. Blur can be viewed as a query execution engine that
 Lucene based solutions can utilize when scale becomes an issue.

 == Initial Goals ==
 The initial goals of the project are:
  * To migrate the Blur codebase, issue tracking and wiki from
 github.com and integrate the project with the ASF infrastructure.
  * Add new committers to the project and grow the community in The Apache
 Way.

 == Current Status ==

 === Meritocracy ===
 Blur was initially developed by Aaron !McCurry in June 2010.  Since
 then Blur has continued to evolve with the support of a small
 development team at Near Infinity.  As a part of the Apache Software
 Foundation, the Apache Blur team intends to strongly encourage the
 community to help with and contribute to the project.  Apache Blur
 will actively seek potential committers and help them become familiar
 with the codebase.

 === Community ===
 A small community has developed around Blur and several project teams
 are currently using Blur for their big data search capability. The
 source code is currently available on GitHub and there is a dedicated
 website (blur.io) that provides an overview of the project. Blur has
 been shared with several members of the Apache community and has been
 presented at the Bay Area HUG (see
 http://www.meetup.com/hadoop/events/20109471/).

 === Core Developers ===
 The current developers are employed by Near Infinity Corporation, but
 we anticipate interest developing among other companies.

 === Alignment ===
 Blur is built on top of a number of Apache projects; Hadoop, Lucene,
 !ZooKeeper, and Thrift. It builds with Maven.  During the course of
 Blur development, a couple of patches have been committed back to the
 Lucene project, including LUCENE-2205 and LUCENE-2215.  Due to the
 strong relationship with the before mentioned Apache projects, the
 incubator is a good match for Blur.

 == Known Risks ==

 === Orphaned Products ===
 There is only a small risk of being orphaned. The customers that
 currently use 

Re: [VOTE] Apache Stanbol Entityhub 0.10.0-incubating

[Tommaso Teofili]

Sorry for my late vote, everything (build, test, sigs, checks, etc.) looks
fine to me.
+1

Tommaso

2012/7/10 Fabian Christ christ.fab...@googlemail.com

 Dear Incubator,

 the Apache Stanbol podling is still in need for one more vote from an
 IPMC member on this release. Please, have a look and make your vote.

 This vote is now open for two weeks!

 Best,
  - Fabian

 2012/7/6 Fabian Christ christ.fab...@gmail.com:
  Hi,
 
  this vote is now open for about 10 days and we are still in need for
  one more vote from an IPMC member to proceed.
 
  It would be really great to finish this release vote soon, so that the
  Apache Stanbol podling could go on with the next steps towards
  graduation.
 
  Thanks for your time,
- Fabian
 
  2012/7/3 Fabian Christ christ.fab...@gmail.com:
  Dear Incubator,
 
  this vote is still open and we are looking for at least one more vote
 from
  an IPMC member to pass. Would be great if someone finds the time to
 verify
  the release.
 
  - Fabian
 
  *(Sent from my mobile. Sorry for typos.)
 
  Am 29.06.2012 08:46 schrieb Fabian Christ christ.fab...@gmail.com:
 
  Hi,
 
  we are in need of at least one more IPMC vote to get this release out.
  It would be great if someone finds the time to check before the
  weekend.
 
  Thanks,
   - Fabian
 
  2012/6/26 Fabian Christ christ.fab...@googlemail.com:
   2012/6/26 sebb seb...@gmail.com:
   Where is the SVN tag for the release?
  
   Here are the SVN tags.
  
   - source-assembly-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/source-assembly-0.10.0-incubating
   - stanbol-parent-1-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/stanbol-parent-1-incubating
   - org.apache.stanbol.commons.solr.core-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/org.apache.stanbol.commons.solr.core-0.10.0-incubating
   - org.apache.stanbol.commons.web.base-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/org.apache.stanbol.commons.web.base-0.10.0-incubating
   - org.apache.stanbol.data.parent-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/org.apache.stanbol.data.parent-0.10.0-incubating
   - org.apache.stanbol.data.sites.dbpedia-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/org.apache.stanbol.data.sites.dbpedia-1.0.4-incubating
   - apache-stanbol-entityhub-0.10.0-incubating
tag:
  
 https://svn.apache.org/repos/asf/incubator/stanbol/tags/apache-stanbol-entityhub-0.10.0-incubating
  
   To check that the released artifacts match those tags, you can use
 the
   mentioned script
  
$ check_release_matches_tag.sh 257 /tmp
  
   --
   Fabian
   http://twitter.com/fctwitt



 --
 Fabian
 http://twitter.com/fctwitt

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

Re: [VOTE] Graduate Flume podling from Apache Incubator

[Tommaso Teofili]

+1
Tommaso

2012/6/5 Arvind Prabhakar arv...@apache.org

 This is a call for vote to graduate Flume podling from Apache Incubator.

 Flume entered the Incubator in June of 2011. Since then it has added nine
 new committers and made two signifiant releases following the ASF policies
 and guidelines. The community of Flume is active, healthy and growing and
 has demonstrated the ability to self-govern using accepted
 Apache practices. Flume community has voted to proceed with graduation [1]
 and the result can be found at [2].

 Please cast your votes:

 [  ] +1 Graduate Flume podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Flume podling
 [  ] -1 Reject graduation of Flume podling from Apache Incubator

 This vote will be open for 72 hours. Please find the proposed board
 resolution below.

 [1] http://s.apache.org/Ckq
 [2] http://s.apache.org/DBv

 Regards,
 Arvind Prabhakar


X. Establish the Apache Flume 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 a system for aggregating
   large amounts of log data on Apache Hadoop's HDFS and
   other scalable storage 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 Flume Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Flume Project be and hereby is
   responsible for the creation and maintenance of software
   related to  a system for aggregating large amounts of log
   data on Apache Hadoop's HDFS and other scalable storage
   systems; and be it further

   RESOLVED, that the office of Vice President, Apache Flume 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 Flume Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Flume 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 Flume Project:

 * Aaron Kimball  kimba...@apache.org
 * Andrew Bayer   aba...@apache.org
 * Ahmed Radwan   ah...@apache.org
 * Arvind Prabhakar   arv...@apache.org
 * Brock Noland   br...@apache.org
 * Bruce Mitchenerbru...@apache.org
 * Derek Deeter   ddee...@apache.org
 * Eric Sammeresam...@apache.org
 * Hari Shreedharan   hshreedha...@apache.org
 * Henry Robinson he...@apache.org
 * Jaroslav Cecho jar...@apache.org
 * Jonathan Hsieh jmhs...@apache.org
 * Juhani Connollyjuha...@apache.org
 * Mike Percy mpe...@apache.org
 * Mingjie Laim...@apache.org
 * Nick Verbeck   nerdyn...@apache.org
 * Patrick Hunt   ph...@apache.org
 * Prasad Mujumdarpras...@apache.org
 * Ralph Goersrgo...@apache.org
 * Will McQueen   w...@apache.org

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
   be appointed to the office of Vice President, Apache Flume, 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 initial Apache Flume PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Flume Project; and be it further

   RESOLVED, that the Apache Flume Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Flume podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Flume podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

Re: [VOTE] [PROPOSAL] cTAKES for the Apache Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso

2012/6/5 Chen, Pei pei.c...@childrens.harvard.edu

 Hi,
 We are proposing cTAKES to be an Apache Incubator Project and would like
 to request that the IPMC vote for cTAKES to join the Incubator.
 Below, you will find the original proposal and details.

 Please cast your vote:
 [ ] +1 to recommend cTAKES to be an Apache Incubator Project
 [ ] 0 don't care
 [ ] -1 no, don't recommend yet, (because...)

 Thanks,
 Pei

 On 05/30/2012 11:59 PM, Chen, Pei wrote:
  Hi All,
 
  We would like to propose cTAKES to be an Apache Incubator project.
 
  cTAKES: (clinical Text Analysis and Knowledge Extraction System) is an
 natural language processing tool for information extraction from electronic
 medical record clinical free-text.  Additional information is available at
 http://en.wikipedia.org/wiki/CTAKES and
 https://wiki.nci.nih.gov/display/VKC/cTAKES+2.5 .
 
  The draft proposal document is available at
  http://wiki.apache.org/incubator/cTAKESProposal
 
  We're excited about the opportunity to work with ASF and the community
 to create an Incubator project for Natural Language Processing for the
 clinical domain.  We'll welcome all feedback on the proposal.
 
  Thanks.
 
 
 
  ---
  Pei Chen
  Lead Application Development Specialist Childrens Hospital Boston /
  Harvard Medical School
  300 Longwood Avenue, Enders 142
  Boston, MA 02115
  tel: (617) 919-4423
  fax: (617) 730-0057
  pei.c...@childrens.harvard.edu
 
 
 
  -
  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 Crunch into the Apache Incubator

[Tommaso Teofili]

+1

Tommaso

2012/5/23 Josh Wills jwi...@cloudera.com

 I would like to call a vote for accepting Apache Crunch for
 incubation in the Apache Incubator. The full proposal is available
 below.  We ask the Incubator PMC to sponsor it, with phunt as
 Champion, and phunt, tomwhite, and acmurthy volunteering to be
 Mentors.

 Please cast your vote:

 [ ] +1, bring Crunch into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Crunch into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.

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

 Proposal text from the wiki:

 --
 = Crunch - Easy, Efficient MapReduce Pipelines in Java and Scala =

 == Abstract ==

 Crunch is a Java library for writing, testing, and running pipelines
 of !MapReduce jobs on Apache Hadoop.

 == Proposal ==

 Crunch is a Java library for writing, testing, and running pipelines
 of !MapReduce jobs on Apache Hadoop. Its main goal is to provide a
 high-level API for writing and testing complex !MapReduce jobs that
 require multiple processing stages.  It has a simple, flexible, and
 extensible data model that makes it ideal for processing data that
 does not naturally fit into a relational structure, such as time
 series and serialized object formats like JSON and Avro. It supports
 running pipelines either as a series of !MapReduce jobs on an Apache
 Hadoop cluster or in memory on a single machine for fast testing and
 debugging.

 == Background ==

 Crunch was initially developed by Cloudera to simplify the process of
 creating sequences of dependent !MapReduce jobs, especially jobs that
 processed non-relational data like time series. Its design was based
 on a paper Google published about a Java library they developed called
 !FlumeJava that was created in order to solve a similar class of
 problems. Crunch was open-sourced by Cloudera on !GitHub as an Apache
 2.0 licensed project in October 2011. During this time Crunch has been
 formally released twice, as versions 0.1.0 (October 2010) and 0.2.0
 (February 2012), with an incremental update to version 0.2.1 (March
 2012) .  These releases are also distributed by Cloudera as source and
 binaries from Cloudera's Maven repository.

 == Rationale ==

 Most of the interesting analytical and data processing tasks that are
 run on an Apache Hadoop cluster require a series of !MapReduce jobs to
 be executed in sequence. Developers who are creating these pipelines
 today need to manually assign the sequence of tasks to perform in a
 dependent chain of !MapReduce jobs, even though there are a number of
 well-known patterns for fusing dependent computations together into a
 single !MapReduce stage and for performing common types of joins and
 aggregations. This results in !MapReduce pipelines that are more
 difficult to test, maintain, and extend to support new functionality.

 Furthermore, the type of data that is being stored and processed using
 Apache Hadoop is evolving. Although Hadoop was originally used for
 storing large volumes of structured text in the form of webpages and
 log files, it is now common for Hadoop to store complex, structured
 data formats such as JSON, Apache Avro, and Apache Thrift. These
 formats allow developers to work with serialized objects in
 programming languages like Java, C++, and Python, and allow for new
 types of analysis to be performed on complex data types. Hadoop has
 also been adopted by the scientific research community, who are using
 Hadoop to process time series data, structured binary files in the
 HDF5 format, and large medical and satellite images.

 Crunch addresses these challenges by providing a lightweight and
 extensible Java API for defining the stages of a data processing
 pipeline, which can then be run on an Apache Hadoop cluster as a
 sequence of dependent !MapReduce jobs, or in-memory on a single
 machine to facilitate fast testing and debugging. Crunch relies on a
 small set of primitive abstractions that represent immutable,
 distributed collections of objects. Developers define functions that
 are applied to those objects in order to generate new immutable,
 distributed collections of objects. Crunch also provides a library of
 common !MapReduce patterns for performing efficient joins and
 aggregation operations over these distributed collections that
 developers may integrate into their own pipelines. Crunch also
 provides native support for processing structured binary data formats
 like JSON, Apache Avro, and Apache Thrift, and is designed to be
 extensible to support working with any kind of data format that Java
 supports in its native form.

 == Initial Goals ==

 Crunch is currently in its first major release with a considerable
 number of enhancement requests, tasks, and issues recorded towards its
 future development. The initial goal 

Re: AMBER Status: let down by incubator?

[Tommaso Teofili]

2012/5/10 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 On Thu, May 10, 2012 at 5:59 PM, Daniel Shahaf d...@daniel.shahaf.name
 wrote:
  (And, drive-by -- we have both Amber and Ambari -- are the names too
 similar?)

 Dunno. I tend to confuse them occasionally, but that's probably just
 because they by chance happen to be reporting in the same month.

 Not sure if there's much confusion beyond that as they're targeting
 different domains, OAuth and Hadoop.

 Amber and Ambari, have you encountered cases of confusion because of
 your similar names?


not that I know.

BTW, starting from the discussion on LEGAL-134 we are now starting to move
forward [1].

Regards,
Tommaso

[1] : http://markmail.org/thread/34vapf2md7vul7yk



 BR,

 Jukka Zitting

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

Re: [VOTE] Graduation of Hama as a TLP

[Tommaso Teofili]

I think the vote can be closed.
Cheers,
Tommaso

2012/4/28 Steve Loughran steve.lough...@gmail.com

  [X ] +1 Hama graduation

 Binding.

 -Steve

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

Re: [VOTE] Graduation of Hama as a TLP

[Tommaso Teofili]

[x] +1 Hama graduation

2012/4/28 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 On Wed, Apr 25, 2012 at 8:03 AM, Edward J. Yoon edwardy...@apache.org
 wrote:
  The community graduation vote was held and passed with 6 positive (4
  binding) votes, no negative votes[1]. Now I would like to ask the IPMC
  to approve the graduation. Please VOTE on the below resolution for
  promoting Hama to an Apache TLP and graduating from the Incubator.

   [x] +1 Hama graduation


 PS. You may want to revise the wording of the resolution, as
 distributed computing framework based on Bulk Synchronous Parallel
 doesn't sound like good language to me (though English isn't my native
 language). A better alternative could be distributed computing
 framework based on the Bulk Synchronous Parallel model.


yes, it sounds better :-)



 BR,

 Jukka Zitting

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

Re: May reports due in ten days

[Tommaso Teofili]

Hi Jukka, all,
Amber devs are trying to have a better understanding on how to solve the IP
Clearance stuff via legal-discuss@ [1].
Regards,
Tommaso

[1] : http://markmail.org/thread/p2taqtcvnxw4o6ri

2012/4/22 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 It'll soon be time for the podlings reporting in May [1]  to start
 drafting their reports.

 When doing so, please consider the review results from February [2]:

  IP clearance: Amber
  Release trouble: Clerezza, Stanbol
  Low activity: Ambari, Nuvem, PhotArk, SIS, Wink, Zeta Components
  Low diversity: Airavata, Droids, VCL, Wookie
  Ready to graduate: Jena, Lucene.NET, NPanday, OpenNLP

 Has the situation in your podling changed over the last three months?
 If not, what's your plan for improving the situation?

 For example, I notice that Clerezza has made a release, but Stanbol
 still needs one. Also, Lucene.NET and NPanday are yet to graduate. Did
 something come up to prevent progress, or have you just not gotten
 around to it yet (which BTW is fine; much better than having bigger
 issues)?

 And to any projects in the Low activity category that still aren't
 seeing increased activity: Do you have a good reason to expect
 activity to pick up, or should we consider retiring the project?

 [1] http://wiki.apache.org/incubator/May2012
 [2] http://wiki.apache.org/incubator/February2012

 BR,

 Jukka Zitting

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

Re: [VOTE] Release ManifoldCF 0.5-incubating, RC6

[Tommaso Teofili]

+1 (binding),
Tommaso

2012/4/12 Karl Wright daddy...@gmail.com

 +1 from me (binding).

 Karl

 On Wed, Apr 11, 2012 at 11:16 PM, Shinichiro Abe
 shinichiro.ab...@gmail.com wrote:
  Hi,
 
  Please vote on whether or not to release ManifoldCF 0.5-incubating, RC6.
  This RC has passed our podling vote and awaits your inspection.
 
  You can download the release candidate from
 
 http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC6/
  and there is also a tag in svn under
 
 https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.5-incubating-RC6/
 .
 
  It has done improvements for its distribution(bin,lib,src)
  and build process as to core dependencies.
 
  Thank you,
  Shinichiro Abe
  -
  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] Graduate Sqoop podling from Apache Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso

2012/2/24 Arvind Prabhakar arv...@apache.org

 This is a call for vote to graduate Sqoop podling from Apache Incubator.

 Sqoop entered Incubator in June of 2011. Since then it has added three
 new committers from diverse organizations, added two new PPMC members,
 and made two releases following the ASF policies and guidelines. The
 community of Sqoop is active, healthy and growing and has demonstrated
 the ability to self-govern using accepted Apache practices. Sqoop
 community has voted to proceed with graduation [1] and the result can
 be found at [2].

 Please cast your votes:

 [  ] +1 Graduate Sqoop podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Sqoop podling
 [  ] -1 Reject graduation of Sqoop podling from Apache Incubator

 This vote will be open for 72 hours. Please find the proposed board
 resolution below.

 [1] http://markmail.org/thread/xwhjtkik7pgrmypi
 [2] http://s.apache.org/sqoop

 Thanks,
 Arvind Prabhakar

 X. Establish the Apache Sqoop 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 efficiently transferring
   bulk data between Apache Hadoop and structured datastores
   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 Sqoop Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Sqoop Project be and hereby is
   responsible for the creation and maintenance of software
   related to efficiently transferring bulk data between Apache
   Hadoop and structured datastores; and be it further

   RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Sqoop 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 Sqoop Project:

 * Aaron Kimball kimba...@apache.org
 * Andrew Bayer  aba...@apache.org
 * Ahmed Radwan  ah...@apache.org
 * Arvind Prabhakar  arv...@apache.org
 * Bilung Leeb...@apache.org
 * Greg Cottman  gcott...@apache.org
 * Guy le Marguyle...@apache.org
 * Jaroslav Cechojar...@apache.org
 * Jonathan Hsiehjmhs...@apache.org
 * Olivier Lamy  ol...@apache.org
 * Paul Zimdars  pzimd...@apache.org
 * Roman Shaposhnik  r...@apache.org

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
   be appointed to the office of Vice President, Apache Sqoop, 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 initial Apache Sqoop PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Sqoop Project; and be it further

   RESOLVED, that the Apache Sqoop Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Sqoop podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Sqoop podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

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

Re: [VOTE] Release Apache Hama 0.4-incubating (RC5)

[Tommaso Teofili]

+1 (binding)
Tommaso

2012/2/18 Edward J. Yoon edwardy...@apache.org

 Hi all,

 We'd like to ask your approval to release the Hama RC5 as Apache Hama
 0.4.0-incubating.

 This RC5 has passed the Hama PMC votes:
 http://markmail.org/thread/iksvds4wthzelcoo

 Artifacts is:
 http://people.apache.org/~edwardyoon/dist/0.4-RC5/

 Signing Keys is available at:

 http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/files/KEYS

 SVN Tag is here:
 https://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC5/

 And, the staging web site is at:
 http://people.apache.org/~edwardyoon/site/

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (because why)

 This vote will remain open for at least 72 hours.
 Thanks!

 --
 Best Regards, Edward J. Yoon
 @eddieyoon

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

Re: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)

[Tommaso Teofili]

+1 (binding)
Tommaso

2012/2/9 Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov

 Hi Folks,

 OK there has been enough discussion here. It's time to VOTE for a new IPMC
 chair and it looks like the remaining folks (including me) that were in
 the running
 have aligned beyond the following nominee: Jukka Zitting. Suffice to say,
 he was
 *my first choice* :)

 In the interest of moving the current discussion matters forward, please
 VOTE
 on this recommendation to the board by the IPMC. I'll leave the VOTE open
 for at least the next 72 hours:

 [ ] +1 Recommend Jukka Zitting for the IPMC chair position.
 [ ] +0 Don't care.
 [ ]  -1 Don't recommend Jukka Zitting for the IPMC chair position
 because...

 Note that only VOTEs from the Incubator PMC members are binding, but
 all are welcome to voice their opinion and it will be recorded in the final
 tallies.

 Finally, just to note, these VOTEs on personnel are normally the only
 thing in Apache that is discussed in private (human/social issues), but
 in the interest of openness and transparency that has been demonstrated
 here during these discussions, I will hold this VOTE on the public list.

 Thanks!

 Cheers,
 Chris

 P.S. Here's my +1. Thanks buddy.

 On Feb 8, 2012, at 3:11 PM, Benson Margulies wrote:

  I am happy to step out of the way for Jukka. He was clever enough to
  stay out of the email s*** storm, and that alone, in my mind, renders
  him most qualified.
 
  On Wed, Feb 8, 2012 at 6:02 PM, Christian Grobmeier grobme...@gmail.com
 wrote:
  I already mentioned that I would have nominated you, and so I am
  delighted to read your message. It will be very difficult to choose
  between all these strong candidates.
 
  Cheers
 
  On Wed, Feb 8, 2012 at 11:49 PM, Jukka Zitting jukka.zitt...@gmail.com
 wrote:
  Hi,
 
  After consideration and some convincing (thanks!), I've decided to
  throw also my hat into the ring as a candidate to be the next chairman
  of the IPMC.
 
  I believe in that role I could be more effective in focusing more of
  our collective attention at where I think it would do most good - at
  the actual podlings we're here to help.
 
  That said, the current incubation process clearly has problems and I
  very much support efforts to improve the way we work (even if the
  result is to replace the Incubator with something better). However,
  I'd like to leave the leadership on these efforts to others and, as
  mentioned elsewhere, rather try to act as a balancing force that helps
  achieve consensus where possible.
 
  Should I be elected, I'd resign as the chairman of the Jackrabbit PMC.
  In fact I think it's in any case high time for Jackrabbit to be
  rotating that role.
 
  Finally, if elected (and assuming the IPMC still exists), I'd serve
  for at most two years before calling for a re-election, or possibly
  much less if I don't find enough free cycles to perform the duty as
  well as it should.
 
  BR,
 
  Jukka Zitting
 


 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@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 BVal as a TLP

[Tommaso Teofili]

+1 (binding)
Tommaso

2012/2/8 Mohammad Nour El-Din mn...@apache.org

 Hi...

   It has been discussed, since a while, about the graduation of Apache
 BVal, whether to graduate to a TLP or Subproject and whether it is time or
 not, [1], [2] and [3].
 In the past few weeks there has been a [VOTE], [4], which formally
 discussed the graduation to a TLP project. Result announcement can be found
 here, [5]. It also has been decided to name the project Apache BVal [6].
 The resolution charter content has been discussed and reviewed here [7].

 *NOTE*: As per Niall's request, his name has been removed from the proposed
 PMC [8].

 The Apache Bean Validation community sees it is time to request an IPMC
 [VOTE] on recommending this resolution [9] to the ASF board.

 Accordingly, would you please cast your vote:

 [ ] +1 to recommend Bean Validation's graduation
 [ ]  0 don't care
 [ ] -1 no, don't recommend yet, (because...)

 The vote will be open for 72 hours.

 [1] - http://s.apache.org/oTC
 [2] - http://s.apache.org/I8C
 [3] - http://s.apache.org/EQE
 [4] - http://s.apache.org/rU
 [5] - http://s.apache.org/7Sw
 [6] - http://s.apache.org/tY
 http://markmail.org/message/kzqgd7ff7t6p62va
 [7] - *http://s.apache.org/49R*
 [8] - http://s.apache.org/JYS
 [9] - See below:

 ## Resolution to create a TLP from graduating Incubator podling

X. Establish the Apache BVal 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 Bean Validation
 Specification and its implementation as Apache BVal
 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 BVal Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache BVal Project be and hereby is
 responsible for the creation and maintenance of software
 related to creating an implementation compliant with the
 Bean Validation Specification and a library of pre-developed
 validators and extensions; and be it further

 RESOLVED, that the office of Vice President, Apache BVal 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 BVal Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache BVal 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 BVal Project:

   - Albert Lee allee8...@apache.org
   - Carlos Vara Callau carlosv...@apache.org
   - David Jencks djen...@apache.org
   - Donald Woods dwo...@apache.org
   - Gerhard Petracek gpetra...@apache.org
   - Jeremy Bauer jrba...@apache.org
   - Kevan Lee Miller ke...@apache.org
   - Luciano Resende lrese...@apache.org
   - Matthias Wessendorf mat...@apache.org
   - Matthew Jason Benson mben...@apache.org
   - Mohammad Nour El-Din mn...@apache.org
   - Roman Stumm romanst...@apache.org
   - Simone Tripodi simonetrip...@apache.org
   - Mark Struberg strub...@apache.org

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Jason Benson
 be appointed to the office of Vice President, Apache BVal, 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 initial Apache BVal PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache BVal Project; and be it further

 RESOLVED, that the Apache BVal Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Bean Validation podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Bean Validation podling encumbered upon the Apache Incubator
 Project are hereafter discharged.
 --
 Thanks
 - Mohammad Nour
 
 Life is like riding a bicycle. To keep your balance you must keep moving
 - Albert Einstein

Re: [VOTE] - Relase Apache Clerezza 0.2-incubating (RC5)

[Tommaso Teofili]

2012/2/3 Reto Bachmann-Gmür r...@apache.org

 On Fri, Feb 3, 2012 at 5:28 AM, ant elder antel...@apache.org wrote:

  On Wed, Feb 1, 2012 at 1:51 PM, Reto Bachmann-Gmür r...@apache.org
  wrote:
   Hello,
  
   While the last release candidate found a lot of acceptance (3 binding
 +1
  in
   the ppmc) it had to be withdrawn because of missing or incorrect NOTICE
  and
   license files. Also the source distribution contained the sources of
  modules
   that are not part of the release profile. The new release candidate
 fixes
   these issues, for that it provides a new module containing the assembly
   descriptor that replicates the directory structure excluding modules
 not
  in
   the release profile.
  
   This is now the fifth vote to release Clerezza parent and all the
  modules in
   the release profile.
  
   A zip with the source distribution and one with the compiled tdb
 launcher
   are available with their signatures at:
  
   http://people.apache.org/~reto/clerezza-release-201202/
  
   In svn the release version is tagged parent-0.2-incubating.
  
   Cheers,
   Reto
 
  I've had a look and the LICENSE file in the binary distribution looks
  good now. The binary distribution is missing the NOTICE file though.
 

 I see that the with the change to the generated NOTICE files the binary
 assembly no longer contains the file. I've created CLEREZZA-682 to address
 this, can we proceed with the release anyway or is this a blocker? (just
 releasing the source version would be fine as well, imho)


 
  The source distribution has a README.txt which says This is a source
  distribution containing different modules to which different notices
  from copyright holders apply, see the NOTICE files in the root folders
  of the individual modules. That might be better to also mention
  licensing, perhaps ...different licenses and notices...see the
  LICENSE and NOTICE files..., i'd probably still vote for it with the
  text as it is though.
 
 I have no problem changing this for the future, but I would like to remark
 that the current information on copyrights and licenses seems more explicit
 than the graduated apache project I looked at (sling and servicemix).


 
  Also remember still my comment from the previous thread - not everyone
  here will be happy with source license doc like this and not all in
  the top LICENSE file so pester people like your mentors to make sure
  you'll get the necessary votes.
 

 While our champion participated in the discussion, unfortunately I got no
 feedback from our mentors (sent mail on private list and added them
 individually as recipient to the last release thread). But weith Tommaso we
 had already an IPMC member vote and I understood you and Bertrand that you
 would support a release after the licensing/notice issues have been fixed.

 The main question seem to me if we can go on with the vote despite the
 missing notice in the binary release candidate and if yes if we should
 exclude the binary from this candidate (and decide only on releasing the
 source distro).


I think the best option would be to fix the NOTICE in binary, fire a new RC
and release the binary stuff too because releasing only the source
package, in my opinion, would be not that convenient in terms of using
Apache Clerezza as devs couldn't take the binary neither from ASF mirrors
nor from Maven Central.
WDYT?

Tommaso



 Cheers,
 Reto


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

Re: [VOTE] Apache OpenNLP as a TLP

[Tommaso Teofili]

+1 (and good luck!)

Tommaso

2012/1/18 Jörn Kottmann kottm...@gmail.com

 Hello everyone,

 the OpenNLP community has voted to graduate and requests that
 the IPMC vote on recommending this resolution to the ASF Board.

 Community graduation vote:
 http://mail-archives.apache.**org/mod_mbox/incubator-**
 opennlp-dev/201112.mbox/%**3c4edd484c.5020...@gmail.com%**3Ehttp://mail-archives.apache.org/mod_mbox/incubator-opennlp-dev/201112.mbox/%3c4edd484c.5020...@gmail.com%3E

 Please cast your vote:
 [ ] +1 to recommend OpenNLP's graduation
 [ ]  0 don't care
 [ ] -1 no, don't recommend yet, (because...)

 Regards,
 Jörn

 

 ## Resolution to create a TLP from graduating Incubator podling

 X. Establish the Apache OpenNLP 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 processing of natural language text
 supported by machine learning 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 OpenNLP Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache OpenNLP Project be and hereby is
 responsible for the creation and maintenance of software
 related to the processing of natural language text
 supported by machine learning; and be it further

 RESOLVED, that the office of Vice President, Apache OpenNLP 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 OpenNLP Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache OpenNLP 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 OpenNLP Project:

 William Silvia co...@apache.org
 Thomas Morton tsmor...@apache.org
 Jason Baldridge jbald...@apache.org
 James Kosin jko...@apache.org
 Jörn Kottmann jo...@apache.org
 Aliaksandr Autayeu auta...@apache.org
 Boris Galitsky bgalit...@apache.org
 Grant Ingersoll gsing...@apache.org
 Benson Margulies bimargul...@apache.org
 Isabel Drost exam...@apache.org

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jörn Kottmann
 be appointed to the office of Vice President, Apache OpenNLP, 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 initial Apache OpenNLP PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache OpenNLP Project; and be it further

 RESOLVED, that the Apache OpenNLP Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator OpenNLP podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator OpenNLP podling encumbered upon the Apache Incubator
 Project are hereafter discharged.


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

Re: [VOTE] Release apache-manifoldcf-sharepoint-3.0-plugin 0.1-incubating

[Tommaso Teofili]

+1

Tommaso

2011/12/29 Karl Wright daddy...@gmail.com

 Hello incubator,

 We've decided to release some of the ManifoldCF server or target
 system plugins with their own versioning and release schedule.  Here's
 the first one.  Please vote +1 if you agree it should be released.
 We've got one vote already (from Jukka, one of our mentors).

 Karl


 -- Forwarded message --
 From: Jukka Zitting jukka.zitt...@gmail.com
 Date: Thu, Dec 15, 2011 at 1:15 PM
 Subject: Re: [RESULT][VOTE] Release
 apache-manifoldcf-sharepoint-3.0-plugin 0.1-incubating
 To: connectors-...@incubator.apache.org


 Hi,

 +1 from me too (binding also for the upcoming IPMC vote)

 I checked the
 apache-manifoldcf-sharepoint-3.0-plugin-0.1-incubating-src.tar.gz
 package with SHA1 checksum 4400b19cf0940bae30778e9fdcb992122ecbc142.
 Without Windows or SharePoint readily at hand I couldn't build the
 package, just statically review it.

 One comment (not blocking) that applies also to the other components
 is that since these components (AFAIUI) don't contain or use any
 crypto code, we should remove the Cryptographic Software Notice
 entries from the README files. Those notices should only be included
 in components referenced in http://www.apache.org/licenses/exports/.

 BR,

 Jukka Zitting

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

Re: [VOTE] Release apache-manifoldcf-solr-4.x-plugin 0.1-incubating

[Tommaso Teofili]

+1

Tommaso

2011/12/29 Karl Wright daddy...@gmail.com

 Sorry - you can find the proposed release package at:
 http://people.apache.org/~kwright.

 On Thu, Dec 29, 2011 at 1:07 PM, Karl Wright daddy...@gmail.com wrote:
  Hello incubator,
 
  We've decided to release some of the ManifoldCF server or target
  system plugins with their own versioning and release schedule.  Here's
  the second one.  Please vote +1 if you agree it should be released.
  We've got one vote already (from Jukka, one of our mentors).
 
  Karl
 
 
  -- Forwarded message --
  From: Jukka Zitting jukka.zitt...@gmail.com
  Date: Thu, Dec 15, 2011 at 12:40 PM
  Subject: Re: [RESULT][VOTE] Release apache-manifoldcf-solr-4.x-plugin
  0.1-incubating
  To: connectors-...@incubator.apache.org
 
 
  Hi,
  +1 from me too (binding also for the upcoming IPMC vote)
  I checked the apache-manifoldcf-solr-4.x-plugin-0.1-incubating-src.tar.gz
  package with SHA1 checksum 84065fe25707beec3b25831a9df56579ad685a50.
  See my comments for the Solr 3.x plugin.
 
  BR,
  Jukka Zitting

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

Re: [VOTE] Release apache-manifoldcf-solr-3.x-plugin 0.1-incubating

[Tommaso Teofili]

+1

Tommaso

2011/12/29 Karl Wright daddy...@gmail.com

 Sorry - you can find the proposed release package at:
 http://people.apache.org/~kwright.

 On Thu, Dec 29, 2011 at 1:08 PM, Karl Wright daddy...@gmail.com wrote:
  Hello incubator,
 
  We've decided to release some of the ManifoldCF server or target
  system plugins with their own versioning and release schedule.  Here's
  the third one.  Please vote +1 if you agree it should be released.
  We've got one vote already (from Jukka, one of our mentors).
 
  Karl
 
 
  -- Forwarded message --
  From: Jukka Zitting jukka.zitt...@gmail.com
  Date: Thu, Dec 15, 2011 at 12:35 PM
  Subject: Re: [RESULT][VOTE] Release apache-manifoldcf-solr-3.x-plugin
  0.1-incubating
  To: connectors-...@incubator.apache.org
 
 
  Hi,
 
  +1 from me too (binding also for the upcoming IPMC vote)
 
  I checked the apache-manifoldcf-solr-3.x-plugin-0.1-incubating-src.tar.gz
  package with SHA1 checksum 14adbae8c05dc589a707208a172901cddd5c19d5.
 
  Some comments, none blocking:
 
  * The release signing guide [1] recommends to have also SHA1 checksums
  for the release.
  * The approach to do an svn checkout as a part of the build is a bit
  troublesome. The build will fail as soon as Lucene rearranges their
  svn tree.
  * Would it make sense to contribute this code directly to Solr instead
  of having it in ManifoldCF? Especially since the code has no direct
  ManifoldCF dependencies.
 
  [1] http://www.apache.org/dev/release-signing.html
 
  BR,
 
  Jukka Zitting

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

Re: [VOTE] Release apache-manifoldcf-0.4-incubating, RC2

[Tommaso Teofili]

+1

Tommaso

2012/1/4 Karl Wright daddy...@gmail.com

 Hello Incubator IPMC,

 Please vote on whether or not to release ManifoldCF 0.4-incubating,
 RC2.  This RC has passed our podling vote and awaits your inspection.
 You can find the artifact at
 http://people.apache.org/~kwright/apache-manifoldcf-0.4-incubating, or
 in svn at
 https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.4-incubating-RC2
 .
  Thanks in advance!

 Karl

Re: [VOTE] Release Apache Accumulo 1.3.5-incubating (rc8)

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/11/29 Eric Newton eric.new...@gmail.com

 This is the first incubator release for Apache Accumulo, with the artifacts
 versioned as 1.3.5-incubating.

 VOTE:

 http://www.mail-archive.com/accumulo-dev@incubator.apache.org/msg00939.html


 RESULT:

 http://www.mail-archive.com/accumulo-dev@incubator.apache.org/msg01038.html


 SVN source tag:

 http://svn.apache.org/viewvc/incubator/accumulo/tags/1.3.5rc8/


 Release artifacts:

 http://people.apache.org/~ecn

 Vote closes in 72 hours.

Re: [VOTE] Release Apache opennlp-1.5.2-incubating-rc6

[Tommaso Teofili]

2011/11/19 Jörn Kottmann kottm...@gmail.com

 Hi all,

 please review and vote on approving the release of Apache OpenNLP.

 The Apache OpenNLP library is a machine learning based toolkit for the
 processing of natural language text.
 It supports the most common NLP tasks, such as tokenization, sentence
 segmentation,
 part-of-speech tagging, named entity extraction, chunking, parsing, and
 coreference resolution.

 We added the missing DISCLAIMER files and updated mentions
 of OpenNLP to be compliant with the branding requirements.

 The OpenNLP community approved the release of opennlp-1.5.2-rc6 in this
 vote thread
 with 5 binding votes and 1 +1 non-binding vote. No other votes were
 received.
 Vote thread:
 http://mail-archives.apache.**org/mod_mbox/incubator-**
 opennlp-dev/20.mbox/%**3C4EC3C861.1050109%40gmail.**com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-opennlp-dev/20.mbox/%3C4EC3C861.1050109%40gmail.com%3E

 The release artifacts and rat reports can be found here:
 http://people.apache.org/~**joern/releases/opennlp-1.5.2-**incubating/rc6/http://people.apache.org/~joern/releases/opennlp-1.5.2-incubating/rc6/

 SVN tag:
 https://svn.apache.org/repos/**asf/incubator/opennlp/tags/**
 opennlp-1.5.2-incubating-rc6/https://svn.apache.org/repos/asf/incubator/opennlp/tags/opennlp-1.5.2-incubating-rc6/

 KEYS file:
 https://svn.apache.org/repos/**asf/incubator/opennlp/tags/**
 opennlp-1.5.2-incubating-rc6/**KEYShttps://svn.apache.org/repos/asf/incubator/opennlp/tags/opennlp-1.5.2-incubating-rc6/KEYS

 Our release contains multiple sub-projects, the rat reports have been
 generated
 for each of these sub-projects.


binaries and source packages look good, unpacked sources and the SVN tag
build flawlessly.
+1
Tommaso



 Many thanks for your support,
 Jörn



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

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Tommaso Teofili]

2011/11/16 Henri Yandell flame...@gmail.com

 On Sun, Nov 13, 2011 at 9:06 AM, Tommaso Teofili
 tommaso.teof...@gmail.com wrote:
  2011/11/11 Henri Yandell flame...@gmail.com
 
  Updating this, half of the items without sign-off in July are now
  signed off. I've updated the list below (though I've not yet added new
  PMCs since June).
 
  Here's the previous email:
 
  On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandell flame...@gmail.com
 wrote:
   Here's a list of the projects in the Incubator who need to sign off
   their copyright item; namely:
  
   Check and make sure that the papers that transfer rights to the ASF
   been received.
It is only necessary to transfer rights for the package, the core
   code, and any
new code produced by the project.  
 
  Here's the latest list:
 
  2008-09-29  olio
  2009-02-09  kato
  2009-02-13  stonehenge
  2009-05-08  ace
  2009-05-13  socialsite
  2009-06-25  wink
  2009-11-08  hise
  2010-01-27  manifoldcf
 
 
  in the recorded grants file I can see:
 
  Software grant from Metacarta, Inc.
   ...
 
  and, as far as I know, this is the required paperwork for ManifoldCF
  (previously knwon as Lucene Connectors Framework).
 
  Please let me know if I'm missing something.

 Need to update your status page to indicate that:

  http://incubator.apache.org/projects/manifoldcf.html


done, it should be fixed now.
Tommaso


  Hen

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

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Tommaso Teofili]

2011/11/11 Henri Yandell flame...@gmail.com

 Updating this, half of the items without sign-off in July are now
 signed off. I've updated the list below (though I've not yet added new
 PMCs since June).

 Here's the previous email:

 On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandell flame...@gmail.com wrote:
  Here's a list of the projects in the Incubator who need to sign off
  their copyright item; namely:
 
  Check and make sure that the papers that transfer rights to the ASF
  been received.
   It is only necessary to transfer rights for the package, the core
  code, and any
   new code produced by the project.  

 Here's the latest list:

 2008-09-29  olio
 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-08  ace
 2009-05-13  socialsite
 2009-06-25  wink
 2009-11-08  hise
 2010-01-27  manifoldcf


in the recorded grants file I can see:

Software grant from Metacarta, Inc.
  ...

and, as far as I know, this is the required paperwork for ManifoldCF
(previously knwon as Lucene Connectors Framework).

Please let me know if I'm missing something.

Tommaso



 2010-05-19  amber
 2010-05-24  zetacomponents
 2010-09-05  nuvem
 2010-11-02  celix
 2010-11-12  kitty
 2010-11-24  stanbol
 2010-12-02  jena
 2010-12-02  opennlp
 2011-06-13  openofficeorg

 Hen

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

Re: incubator is a single group

[Tommaso Teofili]

same here, big +1.
Tommaso

2011/11/11 Jean-Baptiste Onofré j...@nanthrax.net

 Hi guys,

 I second Chris on that point.

 Regards
 JB


 On 11/11/2011 04:37 PM, Mattmann, Chris A (388J) wrote:

 Hi Roy,

 I would be super +1 for this. I think it would really help people out, and
 let those mentoring the podlings and those doing the work manage
 the addition/removal of people to their PPMCs. It would also hopefully
 ease the burden on the PMC chairs and (hopefully) simplify infra.

 Thanks for suggesting this.

 Cheers,
 Chris

 On Nov 10, 2011, at 11:58 PM, Roy T. Fielding wrote:

  Hi folks,

 It has come to my attention that we are wasting resources and
 time trying to manage separate committer lists within infra for
 every podling.  That is something that we can effectively manage
 once a TLP has become self-governing and self-sufficient in its
 interaction with infrastructure.  It is not something that we can
 effectively manage when we have dozens of podlings trying to make
 changes through the incubator chair.

 I *suggest* that incubator change the procedure such that all
 committers (or at least all committers within a single LDAP
 group) have access to all incubator areas and that new people
 simply be requested to only commit within areas for which they
 have been given permission by the podling developers.  That
 will significantly ease everyone's job and allow more direct
 control by podlings for inviting/uninviting their devs.

 Roy

 --**--**
 -
 To unsubscribe, e-mail: 
 general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
 For additional commands, e-mail: 
 general-help@incubator.apache.**orggeneral-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.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~**mattmann/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-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
 For additional commands, e-mail: 
 general-help@incubator.apache.**orggeneral-h...@incubator.apache.org


 --
 Jean-Baptiste Onofré
 jbono...@apache.org
 http://blog.nanthrax.net
 Talend - http://www.talend.com


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

Re: [VOTE] Release Apache opennlp-1.5.2-incubating-rc4

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/11/7 Jörn Kottmann kottm...@gmail.com

 Hi all,

 please review and vote on approving the release of Apache OpenNLP.

 OpenNLP is a machine learning based toolkit for the processing of natural
 language text.
 It supports the most common NLP tasks, such as tokenization, sentence
 segmentation,
 part-of-speech tagging, named entity extraction, chunking, parsing, and
 coreference resolution.

 The OpenNLP community approved the release of opennlp-1.5.2-rc4 in this
 vote thread
 with 4 binding and 1 non-binding +1 votes and we received no 0 or -1 votes:
 http://mail-archives.apache.**org/mod_mbox/incubator-**
 opennlp-dev/20.mbox/%**3C4EB79746.2010908%40gmail.**com%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-opennlp-dev/20.mbox/%3C4EB79746.2010908%40gmail.com%3E

 The release artifacts and rat reports can be found here:
 http://people.apache.org/~**joern/releases/opennlp-1.5.2-**incubating/rc4/http://people.apache.org/~joern/releases/opennlp-1.5.2-incubating/rc4/

 Our release contains multiple sub-projects, the rat reports have been
 generated
 for each of these sub-projects.

 Many thanks for your support,
 Jörn

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

Re: October 2011 Incubator Board Report

[Tommaso Teofili]

Correct,
Hama reported in September, also the 'usual' reminder didn't reach out the
hama-dev@ ML.
Tommaso

2011/10/18 Michael Fitzner fitzner.mich...@googlemail.com

 I think some projects are wrong scheduled for the „October 2011
 Incubator Board Report“ The current schedule plan
 http://wiki.apache.org/incubator/ReportingSchedule shows that projects
 like Etch, Hama, Hcatalog are in the months March, June, September,
 December and not in October. It would be greate if someone could
 correct this in the October report.

 The Etch project had its report in September; see
 http://wiki.apache.org/incubator/September2011 and
 http://incubator.apache.org/clutch.html

 If there was a decision to report in October too, we would like to
 apologise for missing it.

 Thanks
 Michael F. (Apache Etch)

 2011/10/18 Noel J. Bergman n...@devtech.com:
  Most of the general discussion on the Incubator list over the past month
 was
  how to improve the usability of the Incubator web-site.
 
  S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
  scalable, partially fault-tolerant, pluggable platform that allows
  programmers to easily develop applications for processing continuous,
  unbounded streams of data -- was voted to begin Incubation.
 
  Any23 (Anything To Triples) -- a Java library, a Web service and a set of
  command line tools to extract and validate structured data in RDF format
  from a variety of Web documents and markup formats -- was voted to begin
  Incubation.
 
  Apache DirectMemory -- a multi-layered cache implementation featuring
  off-heap memory storage (ala Terracotta BigMemory) to enable caching of
 Java
  objects without degrading JVM performance -- was voted to begin
 Incubation.
 
  Apache Callback (derived from PhonaGap) -- a platform for building native
  (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
  webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML,
 CSS
  and JavaScript -- was voted to begin Incubation.
 
  DeltaCloud is currently voting on graduation from the Incubator.  ACE is
  also discussing graduation.
 
  ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
  (also managed to do a release, though), RAT and WAVE all failed to report
  this month.  The Chair is raising the issue of what to do with these
  projects.
 
  --
 
  Accumulo
 
  Accumulo is a sorted, distributed key/value store based on BigTable's
  design.  Accumulo entered incubation in September 2011.
 
  In the move towards graduation, we must address:
  1. Learning Apache procedures
  2. Creating releases
  3. Building a community
 
  Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware
  of:
  Discussion is ongoing as to whether agreements other than ICLAs are
 needed
  or desirable for people employed by the US government to make
 contributions
  to Apache (see LEGAL-100).
 
  Developments since entering incubation:
  * mailing lists created
  * JIRA created
  * SVN directory and git mirror created
  * accounts for initial committers created
  * ICLAs and Software Grant filed
  * CMS-ready site begun
  * initial code uploaded
  * Jenkins build created
  * ReviewBoard group created
 
 
  ---
 
  ACE
 
  Apache ACE is a software distribution framework that allows you to
 centrally
  manage and distribute software components, configuration data and other
  artifacts to target systems. ACE started incubation on April 24th 2009.
 
  There are currently no issues requiring board or Incubator PMC attention.
 
  Community:
   * We've got a lot of great feedback and patches from the community.
   * There have been talks with the jclouds (we use them) as well as the
  Amdatu (they use us) open source projects.
 
  Software:
   * We now have a REST client API.
   * The management agent has been extended.
   * Karaf features were added.
   * We have a server side resolver based on Apache Felix.
 
  Licensing and other issues:
   * None at the moment.
 
  Things to resolve prior to graduation:
   * We hope this is our very last board report as we think we're ready for
  graduation now!
 
 
  
 
  Ambari
 
  Ambari is monitoring, administration and lifecycle management project for
  Apache Hadoop clusters.
 
   * Incubating since 30 August 2011.
   * Mailing lists created and mentors subscribed.
   * Confluence created.
   * Initial code committed.
   * Site created.
   * Code grant received.
   * Development proceeding actively.
   * RAT added to pom and report is clean.
 
 
  
 
  Any23
 
  Anything To Triples (shortly Any23) defined as a Java library, a Web
 service
  and a set of command line tools to extract and validate structured data
 in
  RDF format from a variety of Web documents and markup formats. Any23 is
 what
  it is informally named an RDF Distiller.
 
  A list of the three most important issues 

Re: [VOTE] Accept Apache Callback for incubation

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/10/11 Jukka Zitting jukka.zitt...@gmail.com

 Hi,

 As discussed, the PhoneGap project would like to enter the Incubator
 under the Apache Callback name (potential alternative names to be
 discussed during incubation). The initial proposal has been well
 received and there are no major open issues, so it's time to vote!

 Thus I'm now calling a formal VOTE on the Apache Callback proposal as
 included below. The proposal is also available at
 http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on
 the PhoneGap wiki, and I'll place a copy for our archives on the
 Incubator wiki as soon as it stops giving me internal server errors.

 Please VOTE:

[ ] +1 Accept Apache Callback for incubation
[ ] -1  Don't accept Apache Callback for incubation because...

 This vote is open for the next 72 hours. Everyone is welcome to
 participate, but only votes from the Incubator PMC members are
 binding.

 Thanks! My vote is +1.

 Best regards,

 Jukka Zitting

 

 Apache Callback Proposal
 

 Abstract
 

 Apache Callback is a platform for building native mobile applications
 using HTML, CSS and JavaScript.

 Proposal
 

 Apache Callback allows web developers to natively target Apple iOS, Google
 Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian
 and Samsung Bada with a single codebase. The Callback APIs are based on
 open web standards. The Callback bridge technology enables access to native
 device capabilities. Utilizing the Callback bridge native plugins allow
 for any type of native access from the embedded webview.

 Background
 --

 Apache Callback is the free software evolution of the popular PhoneGap
 project.

 PhoneGap evolved from a hack that enabled a FFI (Foreign Function
 Interface)
 to an embedded WebView on iOS to a complete suite of tools for tackling
 parity across many mobile device and desktop platforms.

 PhoneGap has always focused on two complementary goals. Our first goal,
 is to see the web as a first class development platform. Not a sandbox
 without a filesystem but a real first class platform that includes access
 to the local system apis, sensors and data, in addition to first class
 tooling such as system debuggers. The second goal of PhoneGap  is for
 the project to cease to exist. This is not a nihilistic sentiment, rather
 we at the PhoneGap project are providing a reference implementation for
 web browsers to assist and guide the standardization process of browser
 APIs.

 The name and trademark of PhoneGap will become the commercial entity for
 the project. The source, code, documentation and related assets will all
 be contributed to the Apache Foundation as Callback.

 The Callback name comes from the event of the same name that is fired
 when the FFI bridge is established.

 Rationale
 -

 The dominate window to the web is quickly becoming devices, mostly phones.
 The manufacturers of devices, creators of mobile operating systems, and
 authors of web browsers are consolidating. (In many cases these are all
 already the same company.) Those stakeholders may see a future for the
 web but their bottom line is not necessarily motivated to participate in
 an open web. It is especially clear that while many of these platforms
 have been seeing some level of strategic neglect in favor of enhanced
 experiences at the price locking developers into their respective
 platforms. The Callback project exists to bring the focus back to an
 open and accessible web.

 Initial Goals
 -

 * License all PhoneGap source code and documentation to the Apache
  Software Foundation. (We already name the Apache license in our CLA.)
 * Setup and standardize the open governance of the Callback project.
 * Rename all assets from PhoneGap to Callback in project src, docs,
  tests and related infrastructure.

 Current Status
 --

 Callback is a mature software project recently shipping 1.0 on July 29,
 2011.

 Meritocracy
 ---

 Callback has always been a project driven by merit and, in a sense, our
 solution is brute force requiring many collaborating developers to
 solve our goals.

 It would be far easier, and perhaps more correct, for the Callback
 project to port a single web browser codebase, and API bindings, across
 platforms but our executable size would be appreciably larger, unacceptably
 so for mobile, and our target abstraction would be only tertiary to
 maintaining a codebase of that size. By relying on the platform browser,
 exposed by the platform SDK, we get a quick win to the browser and only
 have to focus on our bridge. This means the project requires developers
 with proficiency on each platform: collaboration is a natural side effect.

 Community
 -

 The community surrounding Callback is vast, diverse, distributed globally,
 and with all levels of proficiency in software development---the common
 thread of web 

Re: [VOTE] accept DirectMemory as new Apache Incubator podling

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/10/2 Simone Tripodi simonetrip...@apache.org

 Hi all guys,

 I'm now calling a formal VOTE on the DirectMemory proposal located here:

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

 Proposal text copied at the bottom of this email.

 VOTE close on Tuesday, October 4, early 7:30 AM CET.

 Please VOTE:

 [ ] +1 Accept DirectMemory into the Apache Incubator
 [ ] +0 Don't care
 [ ] -1  Don't Accept DirectMemory into the Apache Incubator because...

 Thanks in advance for participating!

 All the best, have a nice day,
 Simo

 P.S. Here's my +1

 http://people.apache.org/~simonetripodi/
 http://www.99soft.org/

 = DirectMemory =

 == Abstract ==
 The following proposal is about Apache !DirectMemory, a Java
 !OpenSource multi-layered cache implementation featuring off-heap
 memory storage (a-la Terracotta !BigMemory) to enable caching of Java
 objects without degrading JVM performance

 == Proposal ==
 !DirectMemory's main purpose is to to act as a second level cache
 (after a heap based one) able to store large amounts of data without
 filling up the Java heap and thus avoiding long garbage collection
 cycles. Although serialization has a runtime cost store/retrieve
 operations are in the sub-millisecond range being pretty acceptable in
 every usage scenario even as a first level cache and, most of all,
 outperforms heap storage when the count of the entries goes over a
 certain amount. !DirectMemory implements cache eviction based on a
 simple LFU (Least Frequently Used) algorythm and also on item
 expiration. Included in the box is a small set of utility classes to
 easily handle off-heap memory buffers.

 == Background ==
 !DirectMemory is a project was born in the 2010 thanks to Raffaele P.
 Guidi initial effort under
 [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already
 licensed under the Apache License 2.0.

 == Rationale ==
 The rationale behind !DirectMemory is bringing off-heap caching to the
 open source world, empowering FOSS developers and products with a tool
 that enables breaking the heap barrier and override the JVM garbage
 collection mechanism collection - which could be useful in scenarios
 where RAM needs are over the usual limits (more than 8, 12, 24gb) and
 to ease usage of off-heap memory in general

 = Current Status =

 == Meritocracy ==
 As a majority of the initial project members are existing ASF
 committers, we recognize the desirability of running the project as a
 meritocracy.  We are eager to engage other members of the community
 and operate to the standard of meritocracy that Apache emphasizes; we
 believe this is the most effective method of growing our community and
 enabling widespread adoption.

 == Core Developers ==
 In alphabetical order:

  * Christian Grobmeier grobmeier at apache dot org
  * Maurizio Cucchiara mcucchiara at apache dot org
  * Olivier Lamy olamy at apache dot org
  * Raffaele P. Guidi raffaele dot p dot guidi at gmail dot com
  * Simone Gianni simoneg at apache dot org
  * Simone Tripodi simonetripodi at apache dot org
  * Tommaso Teofili tommaso at apache dot org

 == Alignment ==
 The purpose of the project is to develop and maintain !DirectMemory
 implementation that can be used by other Apache projects.

 = Known Risks =
 == Orphaned Products ==
 !DirectMemory does not have any reported production usage, yet, but is
 getting traction with developers and being evaluated by potential
 users and thus the risks of it being orphaned are minimal

 == Inexperience with Open Source ==
 All of the committers have experience working in one or more open
 source projects inside and outside ASF.

 == Homogeneous Developers ==
 The list of initial committers are geographically distributed across
 the Europe with no one company being associated with a majority of the
 developers.  Many of these initial developers are experienced Apache
 committers already and all are experienced with working in distributed
 development communities.

 == Reliance on Salaried Developers ==
 To the best of our knowledge, none of the initial committers are being
 paid to develop code for this project.

 == Relationships with Other Apache Products ==
 !DirectMemory fits naturally in the ASF because it could be
 successfully employed together with a large number of ASF products
 ranging from JCS - as a new cache region between the heap and indexed
 file ones, to ORM systems like Cayenne (i.e. replacing current OSCache
 based implementation), Apache JDO and JPA implementations and also
 java based databases (i.e. Derby) and all systems managing large
 amounts of data from Hadoop to Cassandra

 == A Excessive Fascination with the Apache Brand ==
 While the Apache Software Foundation would be a good home for the
 !DirectMemory project it already has some traction and it could live
 on its own - however we see reciprocal benefits for both the ASF and
 the project in adopting the brand to better reach the community

 = Documentation

Re: [VOTE] Add Any23 to the Apache Incubator

[Tommaso Teofili]

 Tripodi simonetripodi at apache dot org
  * Szymon Danielczyk danielczyk.szymon at gmail dot com
  * Tommaso Teofili tommaso at apache dot org

 == Alignment ==
 Main aim of the project is to develop and maintain a fully flavored
 semantic  markup distiller that can be used by other Apache projects that
 need an RDF extraction tool. The Any23 library core is written using the
 following Apache libraries.

  * [[http://commons.apache.org/lang/|Apache Commons Lang]]
  * [[http://hc.apache.org/httpclient-3.x/|Apache Commons HTTP Client]]
  * [[http://commons.apache.org/codec/|Apache Commons Codec]]
  * [[http://tika.apache.org/|Apache Tika]]
  * [[http://commons.apache.org/cli/|Apache Commons CLI]]
  * [[http://poi.apache.org/|Apache POI]]

 The Any23 service is targeted to run within any compliant Servlet
  container like Tomcat.

 = Known Risks =
 == Orphaned Products ==
 The increasing number of Any23 adopters and the raising interest for
 Semantic Web related technologies let us believe that there is a minimal
 risk for this work to being abandoned  from the community. Moreover Any23
 has already been used in production by Sindice.com and  other DERI projects
 for years.

 == Inexperience with Open Source ==
 All of the committers have experience working in one or more open source
 projects inside and outside ASF.

 == Homogeneous Developers ==
 The list of initial committers are geographically distributed across Europe
 with no one company being associated with a majority of the developers.
  Many of these initial developers are experienced Apache committers already
  and all are experienced with working in distributed development
 communities.

 == Reliance on Salaried Developers ==
 To the best of our knowledge, the biggest part of the initial committers is
 being paid to develop code for this project due to the adoption of Any23 in
 their organizations infrastructures. In any case, some of the core
 historical developers (some of them no longer getting paid from the original
 companies behind Any23)  are still committing even if Any23 is not employed
 in their actual organizations. Any23 has already proven its capability to
 attract external developers.

 == Relationships with Other Apache Products ==
 In the last years, other projects have been under ASF incubation process
 relying on the Semantic Web technology stack, such as Apache Clerezza,
 Stanbol and Jena. This could be seen as a proof of the consolidation and the
 adoption growing tendency of such technologies. Apart the specificity of
 those projects, sharing the same underlying stack, Any23 could be employed
 in every projects needing a reliable framework to access structured semantic
 markup. Any23 core could be easily released also as a  [[
 http://wiki.apache.org/nutch/PluginCentral|Apache Nutch Plugin]] and then,
 used to handy fill [[
 http://www.openrdf.org/doc/sesame2/system/ch05.html|SAIL-compliant]]
 triple stores.

 == An Excessive Fascination with the Apache Brand ==
 Even if the Any23 community recognizes the power and the attractiveness  of
 the ASF brand, we are absolutely aware of our already established role in
 the wider Semantic Web developers community. Any23 already proved its
 reliability in closely support all the new specifications coming  from the
 Microformats communities, our major contributors in term of  opened issues
 about new feature requests. Furthermore, we are convinced that we can
 enthusiastically bring inside the ASF new and fresh energies in order to
 improve our visions, insights and knowledge about the other  projects and,
 most important, to have the possibility of enlarge our small  community with
 talented and passionate developers.

 = Documentation =
 Any23 Documentation

  1. [[http://developers.any23.org/|Any23 Project Homepage]]
  1. [[http://code.google.com/p/any23/|Any23 Developer Homepage]]
  1. [[http://any23.org/|Any23 Live Demo]]

 Any23 Related Specifications

  1. [[http://www.w3.org/RDF/|RDF]]
  1. [[http://www.w3.org/TR/html5/|HTML5]]
  1. [[http://www.w3.org/TR/rdfa-syntax/|RDFa]]
  1. [[http://www.w3.org/TR/microdata/|Microdata]]
  1. [[http://microformats.org/|Microformats]]
  1. [[http://www.w3.org/TR/rdf-syntax-grammar/|RDF/XML]]
  1. [[http://www.w3.org/TeamSubmission/turtle/|Turtle]]
  1. [[http://www.w3.org/TR/rdf-testcases/#ntriples|N-Triples]]
  1. [[http://sw.deri.org/2008/07/n-quads/|N-Quads]]

 Any23 Other documentation

  1. [[
 http://www.slideshare.net/dpalmisano/distilling-the-web-of-data-drop-by-drop-with-java|Any23presentation
  on Slideshare]]

 = Initial Source =
 The intial source comprises code developed on [[
 http://code.google.com/p/any23/|GoogleCode]] licensed under the Apache
 License 2.0 (to be contributed under Grant from Giovanni Tummarello for
 Any23).

 = Source and Intellectual Property Submission Plan =
 Source code will be moved from [[
 http://code.google.com/p/any23/|GoogleCode]] space inside the SVN space of
 the podling.

 = External Dependencies

Re: [VOTE] Kalumet to join Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/9/20 Julien Vermillard jvermill...@gmail.com

 +1 (binding)

 On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din
 nour.moham...@gmail.com wrote:
  +1 (binding)
 
  On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com
 wrote:
 
  +1 (non-binding)
 
  Cheers,
  Terri-Lynn Rimmer
  --
  View this message in context:
 http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html
  Sent from the Apache Incubator - General mailing list archive at
 Nabble.com.
 
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 
  --
  Thanks
  - Mohammad Nour
  
  Life is like riding a bicycle. To keep your balance you must keep
 moving
  - Albert Einstein
 
  -
  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] Release ManifoldCF 0.3-incubating?

[Tommaso Teofili]

+1 (binding)
Tommaso



Il giorno 13/set/2011, alle ore 19:33, Karl Wright daddy...@gmail.com ha 
scritto:

 The ManifoldCF community has voted to release ManifoldCF
 0.3-incubating RC1.  Now it is your turn to vote!  You can pick up the
 artifact at http://people.apache.org/~kwright, or if you want to look
 at the svn tag it's at
 https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.3-incubating-RC1.
 
 Thanks!
 Karl
 
 -
 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] Accumulo to join the Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/9/9 Doug Cutting cutt...@apache.org

 It's been a week since the Accumulo proposal was submitted for
 discussion.  A few questions were asked, and the proposal was clarified
 in response.  Sufficient mentors have volunteered.  I thus feel we are
 now ready for a vote.

 The latest proposal can be found at the end of this email and at:

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

 The discussion regarding the proposal can be found at:

  http://s.apache.org/oi

 Please cast your votes:

 [  ] +1 Accept Accumulo for incubation
 [  ] +0 Indifferent to Accumulo incubation
 [  ] -1 Reject Accumulo for incubation

 This vote will close 72 hours from now.

 Thanks,

 Doug

 ---

 = Accumulo Proposal =

 == Abstract ==
 Accumulo is a distributed key/value store that provides expressive,
 cell-level access labels.

 == Proposal ==
 Accumulo is a sorted, distributed key/value store based on Google's
 BigTable design.  It is built on top of Apache Hadoop, Zookeeper, and
 Thrift.  It features a few novel improvements on the BigTable design in
 the form of cell-level access labels and a server-side programming
 mechanism that can modify key/value pairs at various points in the data
 management process.

 == Background ==
 Google published the design of BigTable in 2006.  Several other open
 source projects have implemented aspects of this design including HBase,
 CloudStore, and Cassandra.  Accumulo began its development in 2008.

 == Rationale ==
 There is a need for a flexible, high performance distributed key/value
 store that provides expressive, fine-grained access labels.  The
 communities we expect to be most interested in such a project are
 government, health care, and other industries where privacy is a
 concern.  We have made much progress in developing this project over the
 past 3 years and believe both the project and the interested communities
 would benefit from this work being openly available and having open
 development.

 == Current Status ==

 === Meritocracy ===
 We intend to strongly encourage the community to help with and
 contribute to the code.  We will actively seek potential committers and
 help them become familiar with the codebase.

 === Community ===
 A strong government community has developed around Accumulo and training
 classes have been ongoing for about a year.  Hundreds of developers use
 Accumulo.

 === Core Developers ===
 The developers are mainly employed by the National Security Agency, but
 we anticipate interest developing among other companies.

 === Alignment ===
 Accumulo is built on top of Hadoop, Zookeeper, and Thrift.  It builds
 with Maven.  Due to the strong relationship with these Apache projects,
 the incubator is a good match for Accumulo.

 == Known Risks ==
 === Orphaned Products ===
 There is only a small risk of being orphaned.  The community is
 committed to improving the codebase of the project due to its fulfilling
 needs not addressed by any other software.

 === Inexperience with Open Source ===
 The codebase has been treated internally as an open source project since
 its beginning, and the initial Apache committers have been involved with
 the code for multiple years.  While our experience with public open
 source is limited, we do not anticipate difficulty in operating under
 Apache's development process.

 === Homogeneous Developers ===
 The committers have multiple employers and it is expected that
 committers from different companies will be recruited.

 === Reliance on Salaried Developers ===
 The initial committers are all paid by their employers to work on
 Accumulo and we expect such employment to continue.  Some of the initial
 committers would continue as volunteers even if no longer employed to do
 so.

 === Relationships with Other Apache Products ===
 Accumulo uses Hadoop, Zookeeper, Thrift, Maven, log4j, commons-lang,
 -net, -io, -jci, -collections, -configuration, -logging, and -codec.

 === Relationship to HBase ===
 Accumulo and HBase are both based on the design of Google's BigTable, so
 there is a danger that potential users will have difficulty
 distinguishing the two.  Some of the key areas in which Accumulo differs
 from HBase are discussed below.  It may be possible to incorporate the
 desired features of Accumulo into HBase.  However, the amount of work
 required would slow development of HBase and Accumulo considerably.  We
 believe this warrants a podling for Accumulo at the current time.  We
 expect active cross-pollination will occur between HBase and podling
 Accumulo and it is possible that the codebases and projects will
 ultimately converge.

  Access Labels 
 Accumulo has an additional portion of its key that sorts after the
 column qualifier and before the timestamp.  It is called column
 visibility and enables expressive cell-level access control.
 Authorizations are passed with each query to control what data is
 returned to the user.  The column 

Re: [VOTE] Kafka to join the Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/6/28 Jun Rao jun...@gmail.com

 Hi all,


 Since the discussion on the thread of the Kafka incubator proposal is
 winding down, I'd like to call a vote.

 At the end of this mail, I've put a copy of the current proposal.  Here is
 a link to the document in the wiki:
 http://wiki.apache.org/incubator/KafkaProposal

 And here is a link to the discussion thread:
 http://www.mail-archive.com/general@incubator.apache.org/msg29594.html

 Please cast your votes:

 [  ] +1 Accept Kafka for incubation
 [  ] +0 Indifferent to Kafka incubation
 [  ]  -1 Reject Kafka for incubation

 This vote will close 72 hours from now.

 Thanks,

 Jun

 == Abstract ==
 Kafka is a distributed publish-subscribe system for processing large
 amounts
 of streaming data.

 == Proposal ==
 Kafka provides an extremely high throughput distributed publish/subscribe
 messaging system.  Additionally, it supports relatively long term
 persistence of messages to support a wide variety of consumers,
 partitioning
 of the message stream across servers and consumers, and functionality for
 loading data into Apache Hadoop for offline, batch processing.

 == Background ==
 Kafka was developed at LinkedIn to process the large amounts of events
 generated by that company's website and provide a common repository for
 many
 types of consumers to access and process those events. Kafka has been used
 in production at LinkedIn scale to handle dozens of types of events
 including page views, searches and social network activity. Kafka clusters
 at LinkedIn currently process more than two billion events per day.

 Kafka fills the gap between messaging systems such as Apache ActiveMQ,
 which
 provide low latency message delivery but don't focus on throughput, and log
 processing systems such as Scribe and Flume, which do not provide adequate
 latency for our diverse set of consumers.  Kafka can also be inserted into
 traditional log-processing systems, acting as an intermediate step before
 further processing. Kafka focuses relentlessly on performance and
 throughput
 by not introspecting into message content, nor indexing them on the broker.
  We also achieve high performance by depending on Java's
 sendFile/transferTo
 capabilities to minimize intermediate buffer copies and relying on the OS's
 pagecache to efficiently serve up message contents to consumers. Kafka is
 also designed to be scalable and it depends on Apache ZooKeeper for
 coordination amongst its producers, brokers and consumers.

 Kafka is written in Scala. It was developed internally at LinkedIn to meet
 our particular use cases, but will be useful to many organizations facing a
 similar need to reliably process large amounts of streaming data.
  Therefore, we would like to share it the ASF and begin developing a
 community of developers and users within Apache.

 == Rationale ==
 Many organizations can benefit from a reliable stream processing system
 such
 as Kafka.  While our use case of processing events from a very large
 website
 like LinkedIn has driven the design of Kafka, its uses are varied and we
 expect many new use cases to emerge.  Kafka provides a natural bridge
 between near real-time event processing and offline batch processing and
 will appeal to many users.

 == Current Status ==
 === Meritocracy ===
 Our intent with this incubator proposal is to start building a diverse
 developer community around Kafka following the Apache meritocracy model.
 Since Kafka was open sourced we have solicited contributions via the
 website
 and presentations given to user groups and technical audiences.  We have
 had
 positive responses to these and have received several contributions and
 clients for other languages.  We plan to continue this support for new
 contributors and work with those who contribute significantly to the
 project
 to make them committers.

 === Community ===
 Kafka is currently being used by developed by engineers within LinkedIn and
 used in production in that company. Additionally, we have active users in
 or
 have received contributions from a diverse set of companies including
 MediaSift, SocialTwist, Clearspring and Urban Airship. Recent public
 presentations of Kafka and its goals garnered much interest from potential
 contributors. We hope to extend our contributor base significantly and
 invite all those who are interested in building high-throughput distributed
 systems to participate.  We have begun receiving contributions from outside
 of LinkedIn, including clients for several languages including Ruby, PHP,
 Clojure, .NET and Python.

 To further this goal, we use GitHub issue tracking and branching
 facilities,
 as well as maintaining a public mailing list via Google Groups.

 === Core Developers ===
 Kafka is currently being developed by four engineers at LinkedIn: Neha
 Narkhede, Jun Rao, Jakob Homan and Jay Kreps. Jun has experience within
 Apache as a Cassandra committer and PMC member. Neha has been an active
 

Re: [VOTE] Retire Bluesky Podling

[Tommaso Teofili]

+1

Tommaso

2011/6/28 berndf ber...@apache.org

 Hi everyone,

 this is a vote to retire the Bluesky podling.

 3.5 years into incubation, the podling has not made progress in terms of
 becoming an Apache project. Dev is still done behind closed doors, and
 developers are changing frequently without notifications on the public
 lists. Mentors are M.I.A. Reports are often late. No Apache release was
 every made.

 There were multiple attempts to reboot the podling (Thanks Luciano!)
 without much success.

 So now I'm calling a vote to end Incubation for Bluesky.
 The vote is open at least until 2011-07-02 12:00 UTC.

 [] +1, retire Bluesky for the time being
 [] -0/+0, I'm undecided
 [] -1, I will step up as a mentor, so let's give it another try

 Thanks for voting,

  Bernd

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

Re: [VOTE] Retire Stonehenge

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/6/23 Kevan Miller kevan.mil...@gmail.com

 +1 (binding).

 --kevan
 On Jun 22, 2011, at 12:55 PM, Daniel Kulp wrote:

 
  The Stonehenge project pretty much accomplished what it originally set
 out to
  do and then really didn't find a way to transition to something that is
 longer
  lasting and able to develop a community around it. Lately, there has
 been
  no interest in it as evidence by the last commit being almost a year ago.
  The
  only recent activity on the dev list is about retiring it and notices
 about
  missing board reports.
 
  Please vote for the retiring of the Stonehenge podling:
 
  [] +1 - please retire
  [] +/-0
  [] -1 - please don't retire, because...
 
 
 
  --
  Daniel Kulp
  dk...@apache.org
  http://dankulp.com/blog
  Talend - http://www.talend.com


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

Re: [PROPOSAL] Kafka for the Apache Incubator

[Tommaso Teofili]

Wow, very nice proposal guys!
Tommaso

2011/6/22 Jun Rao jun...@gmail.com

 Hi,

 I would like to propose Kafka to be an Apache Incubator project.  Kafka is
 a
 distributed, high throughput, publish-subscribe system for processing large
 amounts of streaming data.

 Here's a link to the proposal in the Incubator wiki
 http://wiki.apache.org/incubator/KafkaProposal

 I've also pasted the initial contents below.

 Thanks,

 Jun

 == Abstract ==
 Kafka is a distributed publish-subscribe system for processing large
 amounts
 of streaming data.

 == Proposal ==
 Kafka provides an extremely high throughput distributed publish/subscribe
 messaging system.  Additionally, it supports relatively long term
 persistence of messages to support a wide variety of consumers,
 partitioning
 of the message stream across servers and consumers, and functionality for
 loading data into Apache Hadoop for offline, batch processing.

 == Background ==
 Kafka was developed at LinkedIn to process the large amounts of events
 generated by that company's website and provide a common repository for
 many
 types of consumers to access and process those events. Kafka has been used
 in production at LinkedIn scale to handle dozens of types of events
 including page views, searches and social network activity. Kafka clusters
 at LinkedIn currently process more than two billion events per day.

 Kafka fills the gap between messaging systems such as Apache ActiveMQ,
 which
 can provide high-volume messaging systems but lack persistence of those
 messages, and log processing systems such as Scribe and Flume, which do not
 provide adequate latency for our diverse set of consumers.  Kafka can also
 be inserted into traditional log-processing systems, acting as an
 intermediate step before further processing. Kafka focuses relentlessly on
 performance and throughput by not introspecting into message content, nor
 indexing them on the broker.  We also achieve high performance by depending
 on Java's sendFile/transferTo capabilities to minimize intermediate buffer
 copies and relying on the OS's pagecache to efficiently serve up message
 contents to consumers.

 Kafka is written in Scala and depends on Apache ZooKeeper for coordination
 amongst its producers, brokers and consumers.

 Kafka was developed internally at LinkedIn to meet our particular use
 cases,
 but will be useful to many organizations facing a similar need to reliably
 process large amounts of streaming data.  Therefore, we would like to share
 it the ASF and begin developing a community of developers and users within
 Apache.

 == Rationale ==
 Many organizations can benefit from a reliable stream processing system
 such
 as Kafka.  While our use case of processing events from a very large
 website
 like LinkedIn has driven the design of Kafka, its uses are varied and we
 expect many new use cases to emerge.  Kafka provides a natural bridge
 between near real-time event processing and offline batch processing and
 will appeal to many users.

 == Current Status ==
 === Meritocracy ===
 Our intent with this incubator proposal is to start building a diverse
 developer community around Kafka following the Apache meritocracy model.
 Since Kafka was open sourced we have solicited contributions via the
 website
 and presentations given to user groups and technical audiences.  We have
 had
 positive responses to these and have received several contributions and
 clients for other languages.  We plan to continue this support for new
 contributors and work with those who contribute significantly to the
 project
 to make them committers.

 === Community ===
 Kafka is currently being used by developed by engineers within LinkedIn and
 used in production in that company. Additionally, we have active users in
 or
 have received contributions from a diverse set of companies including
 MediaSift, SocialTwist, Clearspring and Urban Airship. Recent public
 presentations of Kafka and its goals garnered much interest from potential
 contributors. We hope to extend our contributor base significantly and
 invite all those who are interested in building high-throughput distributed
 systems to participate.  We have begun receiving contributions from outside
 of LinkedIn, including clients for several languages including Ruby, PHP,
 Clojure, .NET and Python.

 To further this goal, we use GitHub issue tracking and branching
 facilities,
 as well as maintaining a public mailing list via Google Groups.

 === Core Developers ===
 Kafka is currently being developed by four engineers at LinkedIn: Neha
 Narkhede, Jun Rao, Jakob Homan and Jay Kreps. Jun has experience within
 Apache as a Cassandra committer and PMC member. Neha has been an active
 contributor to several projects LinkedIn has open sourced, including Bobo,
 Sensei and Zoie. Jay has experience with open source software as the
 originator of the Project Voldemort project, as well as being active within
 the Hadoop ecosystem community. Jakob is an 

Re: [VOTE] Flume to join the Incubator.

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/6/8 Jonathan Hsieh j...@cloudera.com

 Hi all,

 Since there have been no new conversations on this Flume [PROPOSAL] thread,
 I'd like to call a vote.

 At the end of this mail, I've put a copy of the current proposal.  Here is
 a
 link to the document in the wiki:
 http://wiki.apache.org/incubator/FlumeProposal

 And here is a link to the discussion thread:
 http://www.mail-archive.com/general@incubator.apache.org/msg27722.html

 Please cast your votes:

 [  ] +1 Accept Flume for incubation
 [  ] +0 Indifferent to Flume incubation
 [  ]  -1 Reject Flume for incubation

 This vote will close 72 hours from now.

 Thanks,
 Jon.

 

 = Flume - A Distributed Log Collection System =

 == Abstract ==

 Flume is a distributed, reliable, and available system for efficiently
 collecting, aggregating, and moving large amounts of log data to scalable
 data storage systems such as Apache Hadoop's HDFS.

 == Proposal ==

 Flume is a distributed, reliable, and available system for efficiently
 collecting, aggregating, and moving large amounts of log data from many
 different sources to a centralized data store. Its main goal is to deliver
 data from applications to Hadoop’s HDFS.  It has a simple and flexible
 architecture for transporting streaming event data via flume nodes to the
 data store.  It is robust and fault-tolerant with tunable reliability
 mechanisms that rely upon many failover and recovery mechanisms. The system
 is centrally configured and allows for intelligent dynamic management. It
 uses a simple extensible data model that allows for lightweight online
 analytic applications.  It provides a pluggable mechanism by which new
 sources, destinations, and analytic functions which can be integrated
 within
 a Flume pipeline.

 == Background ==

 Flume was initially developed by Cloudera to enable reliable and simplified
 collection of log information from many distributed sources. It was later
 open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in
 June
 2010. During this time Flume has been formally released five times as
 versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2
 (Nov
 2010), and 0.9.3 (Feb 2011).  These releases are also distributed by
 Cloudera as source and binaries along with enhancements as part of Cloudera
 Distribution including Apache Hadoop (CDH).

 == Rationale ==

 Collecting log information in a data center in a timely, reliable, and
 efficient manner is a difficult challenge but important because when
 aggregated and analyzed, log information can yield valuable business
 insights.   We believe that users and operators need a manageable
 systematic
 approach for log collection that simplifies the creation, the monitoring,
 and the administration of reliable log data pipelines.  Oftentimes today,
 this collection is attempted by periodically shipping data in batches and
 by
 using potentially unreliable and inefficient ad-hoc methods.

 Log data is typically generated in various systems running within a data
 center that can range from a few machines to hundreds of machines.  In
 aggregate, the data acts like a large-volume continuous stream with
 contents
 that can have highly-varied format and highly-varied content.  The volume
 and variety of raw log data makes Apache Hadoop's HDFS file system an ideal
 storage location before the eventual analysis.  Unfortunately, HDFS has
 limitations with regards to durability as well as scaling limitations when
 handling a large number of low-bandwidth connections or small files.
  Similar technical challenges are also suffered when attempting to write
 data to other data storage services.

 Flume addresses these challenges by providing a reliable, scalable,
 manageable, and extensible solution.  It uses a streaming design for
 capturing and aggregating log information from varied sources in a
 distributed environment and has centralized management features for minimal
 configuration and management overhead.

 == Initial Goals ==

 Flume is currently in its first major release with a considerable number of
 enhancement requests, tasks, and issues recorded towards its future
 development. The initial goal of this project will be to continue to build
 community in the spirit of the Apache Way, and to address the highly
 requested features and bug-fixes towards the next dot release.

 Some goals include:
  * To stand up a sustaining Apache-based community around the Flume
 codebase.
  * Implementing core functionality of a usable highly-available Flume
 master.
  * Performance, usability, and robustness improvements.
  * Improving the ability to monitor and diagnose problems as data is
 transported.
  * Providing a centralized place for contributed connectors and related
 projects.

 = Current Status =

 == Meritocracy ==

 Flume was initially developed by Jonathan Hsieh in July 2009 along with
 development team at Cloudera. Developers external to Cloudera provided
 feedback, 

Re: [VOTE] Accept Sqoop for Incubation

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/6/8 arv...@cloudera.com arv...@cloudera.com

 As there are no active discussions on the [PROPOSAL] thread for a few
 days now, I will like to initiate the vote to accept Sqoop as an
 Apache Incubator project. The proposal discussion thread and full text
 of the proposal can be found at the following locations:

 Discussion Thread:
 http://www.mail-archive.com/general@incubator.apache.org/msg27726.html
 Proposal: http://wiki.apache.org/incubator/SqoopProposal

 Please cast your votes:

 [  ] +1 Accept Sqoop for incubation
 [  ] +0 Indifferent to Sqoop incubation
 [  ]  -1 Reject Sqoop for incubation

 This vote will close 72 hours from now.

 Thanks and Regards,
 Arvind Prabhakar

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

Re: [VOTE] Release ManifoldCF 0.2-incubating, RC2

[Tommaso Teofili]

+1
Tommaso

2011/5/17 Grant Ingersoll gsing...@apache.org


 On May 9, 2011, at 4:34 AM, Karl Wright wrote:

  Hi - just to clarify, we did not include the HTTPD extension in the
  release, but it remains available in source control for backwards
  compatibility.  Most people use the Active Directory Authority at the
  moment.  But thank you for compiling it.
 
  As for the RAT report, the skins question is known and a ticket is
  open for that.  The other files are temporary files resulting from
  your test run and I will open a ticket to exclude those from the
  rat-source target.
 
  We've still received zero binding evaluations from incubator for this
  release, FWIW.


 Sorry, I presumed my PPMC vote would count here as well, so +1 (binding)
 from me.
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal]: Libcloud to become a TLP

[Tommaso Teofili]

+1 (binding)
Tommaso

2011/5/14 Tomaz Muraus to...@cloudkick.com

 Hello all,

 Apache Libcloud developers and community thinks we are ready to graduate
 and
 become a top level project.

 Libcloud (http://incubator.apache.org/libcloud/) has entered the incubator
 in late 2009 and so far we have had multiple releases.

 The last version (0.4.2) was released in January. We are currently working
 towards 0.5.0 which is planned to be released in the upcoming week. This
 release is considered as a big one since it will include multiple new
 features (storage  load balancer API), new provider drivers and a lot of
 improvements.

 We have also built a healthy and a diverse community around our project. So
 far we have received (and continue to receive) multiple contributions from
 them.

 Community voting has passed with ten (10) +1's, zero (0) 0's and zero (0)
 -1's. Thread with the results can be found at

 http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser

 Our status file can be found at

 http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/libcloud.xmland
 the resolution is included bellow.

 
 http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser
 
 Thanks,
 Tomaz

 Establish the Apache Libcloud 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 abstracting differences
 between cloud providers 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 Libcloud Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Libcloud Project be and hereby is
 responsible for the creation and maintenance of software
 related to software providing a standard interface to the
 cloud provider APIs; and be it further

 RESOLVED, that the office of Vice President, Apache Libcloud 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 Libcloud Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Libcloud 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 Libcloud Project:

  * Eric Woods (wood...@apache.org)
  * Jed Smith (j...@apache.org)
  * Jeremiah Orem(or...@apache.org)
  * Jerry Chen (je...@apache.org)
  * Roman Bogorodskiy (rbogorods...@apache.org)
  * Tom Davis (t...@apache.org)
  * Tomaz Muraus (to...@apache.org)
  * Paul Querna (pque...@apache.org)

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tomaz Muraus
 be appointed to the office of Vice President, Apache Libcloud, 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 initial Apache Libcloud PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Libcloud Project; and be it further

 RESOLVED, that the Apache Libcloud Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Libcloud podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Libcloud podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

Re: [VOTE] Accept Airavata into the Incubator

[Tommaso Teofili]

+1 (binding)
Good luck!
Tommaso

2011/5/3 Sagara Gunathunga sagara.gunathu...@gmail.com

 + 1 ( Non binding )

 On Tue, May 3, 2011 at 10:14 AM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
  +1 (binding)
 
  Cheers,
  Chris
 
  On May 2, 2011, at 5:32 PM, Ross Gardler wrote:
 
  I would like to call a vote to accept Airavata for entry into the Apache
  Incubator. The proposal thread can be found at [1] and the proposal text
  is at [2]
 
  [ ] +1 Accept Airavata into the incubator
  [ ] -1 Do NOT accept Airavata into the incubator because...
 
  Thanks,
  Ross
 
  [1] http://markmail.org/message/rhdiuwcexalfndim
  [2] http://wiki.apache.org/incubator/AiravataProposal
 
  -
  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.a.mattm...@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
 
 



 --
 Sagara Gunathunga

 Blog - http://ssagara.blogspot.com
 Web - http://people.apache.org/~sagara/

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

Re: [VOTE] Release Apache opennlp-1.5.1-incubating-rc7

[Tommaso Teofili]

+1 (binding)
Cheers,
Tommaso

2011/4/29 Jörn Kottmann kottm...@gmail.com

 Hi all,

 please review and vote on approving our first release of Apache OpenNLP.

 OpenNLP is a machine learning based toolkit for the processing of natural
 language text.
 It supports the most common NLP tasks, such as tokenization, sentence
 segmentation,
 part-of-speech tagging, named entity extraction, chunking, parsing, and
 coreference resolution.

 The OpenNLP community approved the release of opennlp-1.5.1-rc7 in this
 vote thread
 with 4 binding and 2 non-binding +1 votes and we received no 0 or -1 votes:

 http://mail-archives.apache.org/mod_mbox/incubator-opennlp-dev/201104.mbox/%3c4dba8705.8060...@gmail.com%3e

 The release artifacts and rat reports can be found here:
 http://people.apache.org/~joern/releases/opennlp-1.5.1-incubating/rc7/

 Our release contains multiple sub-projects, the rat reports have been
 generated
 for each of these sub-projects. We will try to improved that for our next
 release,
 any hints about that are welcome.

 Many thanks for your support,
 Jörn

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

Re: [VOTE][PROPOSAL] OGNL join the Incubator

[Tommaso Teofili]

+1 (binding)
Tommaso 



Il giorno 23/apr/2011, alle ore 13:57, Simone Tripodi 
simonetrip...@apache.org ha scritto:

 Hi all ASF mates,
 I'm writing to submit a new incubator proposal, Apache OGNL.
 Follows below the proposal; this vote will be open for 72 hours and
 will be closed on April 26th (Tue) at 12:00 am CET.
 Many thanks in advance to everyone will take pat to the vote!
 Have a nice weekend,
 Simo
 
 http://people.apache.org/~simonetripodi/
 http://www.99soft.org/
 
 Apache OGNL
 
 Abstract
 The following proposal is about Apache OGNL, a Java development
 framework for Object-Graph Navigation Language, plus other extras such
 as list projection[1], selection[2] and lambda expressions[3].
 
 Proposal
 OGNL started out as a way to set up associations between UI components
 and controllers using property names. As the desire for more
 complicated associations grew, Drew Davidson created what he called
 KVCL, for Key-Value Coding Language, egged on by Luke Blanshard. Luke
 then reimplemented the language using ANTLR, came up with the new
 name, and, egged on by Drew, filled it out to its current state. Later
 on Luke again reimplemented the language using JavaCC. Further
 maintenance on all the code is done by Drew (with spiritual guidance
 from Luke).
 Today OGNL is maintained by Lukasz Lenart.
 
 Background
 OGNL is a long living project born in the 1997 thanks to Drew Davidson
 initial effort, moved under the OpenSymphony[4] umbrella in June 2005
 or thereabouts, then moved on its own domain on ognl.org[5] that's no
 more maintained, then finally found place on GitHub[6], maintained by
 Lukasz Lenart.
 
 Rationale
 OGNL stands for Object Graph Navigation Language. It is an expression
 and binding language for getting and setting properties of Java
 objects. Normally the same expression is used for both getting and
 setting the value of a property.
 
 Many people have asked exactly what OGNL is good for. Several of the
 uses to which OGNL has been applied are:
 
 * A binding language between GUI elements (textfield, combobox, etc.)
 to model objects. Transformations are made easier by OGNL's
 TypeConverter mechanism to convert values from one type to another
 (String to numeric types, for example).
 * A data source language to map between table columns and a Swing TableModel.
 * A binding language between web components and the underlying model
 objects (WebOGNL, Tapestry, WebWork, WebObjects).
 * A more expressive replacement for the property-getting language
 used by the Apache Commons BeanUtils package or JSTL's EL (which only
 allow simple property navigation and rudimentary indexed properties).
 
 Most of what you can do in Java is possible in OGNL, plus other extras
 such as list projection and selection and lambda expressions.
 
 Current Status
 
 Meritocracy
 As a majority of the initial project members are existing ASF
 committers, we recognize the desirability of running the project as a
 meritocracy.  We are eager to engage other members of the community
 and operate to the standard of meritocracy that Apache emphasizes; we
 believe this is the most effective method of growing our community and
 enabling widespread adoption.
 
 Core Developers
 In alphabetical order:
 
 * Antonio Petrelli apetrelli at apache dot org
 * Christian Grobmeier grobmeier at apache dot org
 * Jesse Kuhnert jkuhnert at apache dot org
 * Jochen Wiedmann jochen at apache dot org
 * Lukasz Lenart lukaszlenart at apache dot org
 * Olivier Lamy olamy at apache dot org
 * Marc Andrew Davidson drewd at apple dot com
 * Maurizio Cucchiara mcucchiara at apache dot org
 * Simone Tripodi simonetripodi at apache dot org
 * Upayavira upayavira at apache dot org
 
 Alignment
 The purpose of the project is to develop and maintain OGNL
 implementation that can be used by other Apache projects.
 
 Known Risks
 Orphaned Products
 Being OGNL widely adopted we believe there is minimal risks of this
 work becoming non-strategic and the contributors are confident that a
 larger community will form within the project in a relatively short
 space of time.
 
 Moreover, OGNL has been already used by the following projects for years:
 
 * Apache Struts;
 * Apache Tapestry;
 * Apache Camel;
 * Apache Tiles;
 * MyBatis (formerly Apache iBATIS);
 * Spring WebFlow.
 
 Inexperience with Open Source
 All of the committers have experience working in one or more open
 source projects inside and outside ASF.
 
 Homogeneous Developers
 The list of initial committers are geographically distributed across
 the USA and Europe with no one company being associated with a
 majority of the developers.  Many of these initial developers are
 experienced Apache committers already and all are experienced with
 working in distributed development communities.
 
 Reliance on Salaried Developers
 To the best of our knowledge, none of the initial committers are being
 paid to develop code for this project.
 
 Relationships with Other Apache Products
 A number of 

Re: [VOTE] Release Hama version 0.2-incubating (second)

[Tommaso Teofili]

Hi sebb,
as you noticed, Hama uses Maven as a build system but, since this was added
recently [1][2], the project main build is still based on Ant, therefore
Hama still has the lib/*.jar versioned in SVN.
Thanks for the hints regarding libraries' versions (but I wouldn't
consider it a blocker) and grobo-testing-junit (I didn't manage to find it
in any repo).
Regards,
Tommaso

[1] : https://issues.apache.org/jira/browse/HAMA-337
[2] : https://issues.apache.org/jira/browse/HAMA-343

p.s.:

I already gave my +1 as Hama mentor

Re: [VOTE] Accept Howl as an Incubator Project

[Tommaso Teofili]

+1
Tommaso

2011/2/23 Alan Gates ga...@yahoo-inc.com

 I would like to call a vote on accepting Howl as an Incubator project.  The
 proposal is available at http://wiki.apache.org/incubator/HowlProposal.
  You can see the discussion from the proposal thread at
 http://tinyurl.com/5w7y9p9.

 Alan.

 --

 Abstract
 Howl is a table and storage management service for data created using
 Apache Hadoop.


 Proposal
 The vision of Howl is to provide table management and storage management
 layers for Apache Hadoop. This includes:

• Providing a shared schema and data type mechanism.
• Providing a table abstraction so that users need not be concerned
 with where or how their data is stored.
• Providing interoperability across data processing tools such as
 Pig, Map Reduce, Streaming, and Hive.

 Background
 Data processors using Apache Hadoop have a common need for table management
 services. The goal of a table management service is to track data that
 exists in a Hadoop grid and present that data to users in a tabular format.
 Such a table management service needs to provide a single input and output
 format to users so that individual users need not be concerned with the
 storage formats that are chosen for particular data sets. As part of having
 a single format, the data will need to be described by one type of schema
 and have a single datatype system.

 Additionally, users should be free to choose the best tools for their use
 cases. The Hadoop project includes Map Reduce, Streaming, Pig, and Hive, and
 additional tools exist such as Cascading. Each of these tools has users who
 prefer it, and there are use cases best addressed by each of these tools.
 Two users on the same grid who need to share data should not be constrained
 to use the same tool but rather should be free to choose the best tool for
 their use case. A table management service that presents data in the same
 way to all of the tools can alleviate this problem by providing interfaces
 to each of the data processing tools.

 There are also a few other features a table management service should
 provide, such as notification of when data arrives.

 A couple of developers at Yahoo! started the project. It is based on the
 Hive MetaStore component. There is good amount of interest in such a service
 expressed from Yahoo!, Facebook, LinkedIn, and, others. We are therefore
 proposing to place Howl in the Apache incubator and to build an open source
 community around it.


 Rationale
 There is a strong need for a table management service, especially for large
 grids with petabytes of data, and where the data volume is increasing by the
 day. Hadoop users need to find data to read and have a place to store  their
 data. Currently users must understand the location of data to read, the
 storage format, compression techniques used, etc. To write data they need to
 understand where on HDFS their data belongs, the best compression format to
 use, how their data should be serialized, etc.

 Most users do not want to be concerned with these issues. They want these
 managed for them.

 Having it as an Apache Open Source project will highly benefit Howl from
 the point of view of getting a large community that currently uses Hadoop
 and the other products built around Hadoop (like Pig, Hive, etc.). Users of
 the Hadoop ecosystem can influence Howl’s roadmap, and contribute to it.
 Looking at it in another way, we believe having Howl as part of the Hadoop
 ecosystem will be a great benefit to the current Hadoop/Pig/Hive community
 too.


 Current Status

 Meritocracy
 Our intent with this incubator proposal is to start building a diverse
 developer community around Howl following the Apache meritocracy model. We
 have wanted to make the project open source and encourage contributors from
 multiple organizations from the start. We plan to provide plenty of support
 to new developers and to quickly recruit those who make solid contributions
 to committer status.


 Community
 Howl is currently being used by developers at Yahoo! and there has been an
 expressed interest from LinkedIn and Facebook. Yahoo! also plans to deploy
 the current version of Howl in production soon. We hope to extend the user
 and developer base further in the future. The current developers and users
 are all interested in building a solid open source community around Howl.

 To work towards an open source community, we have started using the GitHub
 issue tracker and mailing lists at Yahoo! for development discussions within
 our group.


 Core Developers
 Howl is currently being developed by four engineers from Yahoo! - Devaraj
 Das, Ashutosh Chauhan, Sushanth Sowmyan, and Mac Yang. All the engineers
 have deep expertise in Hadoop and the Hadoop Ecosystem in general.


 Alignment
 The ASF is a natural host for Howl given that it is already the home of
 Hadoop, Pig, HBase, Cassandra, and other emerging cloud software projects.
 Howl was 

Re: [VOTE] Accept Lucene.Net for incubation

[Tommaso Teofili]

+1
Tommaso

2011/1/27 Stefan Bodewig bode...@apache.org

 On 2011-01-27, Troy Howard wrote:

  Since posting the Lucene.Net Incubator proposal announcement on Jan
  12th, we now have three mentors signed up and would like to call a
  vote to accept Lucene.Net into the Apache Incubator.

  The proposal is included below and can also be found at:

  http://wiki.apache.org/incubator/Lucene.Net%20Proposal

  Please cast your votes:

  [X] +1 Accept Lucene.Net for incubation
  [ ] +0 Don't care
  [ ] -1 Reject for the following reason:

 +1

 Stefan

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

Re: [PROPOSAL] Lucene.Net return to the Incubator

[Tommaso Teofili]

Same here, all the best to Lucene.Net incubation.
Cheers,
Tommaso

2011/1/13 Simon Willnauer simon.willna...@googlemail.com

 +1 to this proposal - I am happy to see that this worked out and
 Lucene.Net moves forward!

 simon

 On Thu, Jan 13, 2011 at 1:08 AM, Gianugo Rabellino gian...@rabellino.it
 wrote:
  On Wed, Jan 12, 2011 at 2:43 PM, Troy Howard thowar...@gmail.com
 wrote:
  All,
 
  Please review our proposal for moving the Lucene.Net project back to
  the Incubator.
 
  I am happy to support this proposal and signed up as a mentor.
 
  --
  Gianugo Rabellino - gianugo at rabellino dot it
  Blog: http://boldlyopen.com
 
  -
  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