Re: [VOTE] Retire the Climate Model Data Analyzer Podling

[Hadrian Zbarcea]

+1

Hadrian

On 02/02/2017 07:20 PM, John D. Ament wrote:

All,

Due to the lack of progress made by the CMDA podling I am calling a vote to
retire them.  A discussion and vote thread [1] have occurred on the
podling's lists.  It was confirmed that development activities happen
outside the ASF.

I'm considering this a 72 hour lazy consensus vote since 3 IPMC members
voted +1 on the podling's list.  My +1 is implied due to the fact that I've
been monitoring them and am calling this vote.

John

[1]:
https://lists.apache.org/thread.html/ac4de53d2b16afb91142449d7832f6713f54eb9a1fd2d9c6c3efaffb@%3Cdev.cmda.apache.org%3E



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

Re: [VOTE] Graduate TinkerPop from Incubator

[Hadrian Zbarcea]

+1 (mentor and ipmc)

Hadrian

On 04/05/2016 07:11 AM, Stephen Mallette wrote:

The Apache TinkerPop community has discussed graduation to a top level
project and achieved consensus:

https://s.apache.org/PKhX

Please vote on the resolution that follows to graduate Apache TinkerPop
from incubator to top level project. This vote will be open for at least 72
hours.

Thanks,

Stephen Mallette on behalf of the Apache TinkerPop PPMC

==
X. Establish the Apache TinkerPop 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 a graph computing framework for graph
databases and graph analytic systems

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

RESOLVED, that the Apache TinkerPop Project be and hereby is
responsible for the creation and maintenance of software
related to a graph computing framework for graph databases
and graph analytic systems.

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

* Daniel Gruno 
* Daniel Kuppitz 
* James Thornton 
* Hadrian Zbarcea 
* Marko Rodriguez 
* Stephen Mallette 
* Ted Wilmes 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen Mallette
be appointed to the office of Vice President, Apache TinkerPop, 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 TinkerPop 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 TinkerPop Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator TinkerPop 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: [RESULT][VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

Hi,

A bit of status. Most of the infrastructure is created. The Jira space 
is waiting for a reboot of the system and will only be available next 
Tue. The git repo is however available and we can start the code grant 
process (by litbit, whom afaik owns the IP). Committers should continue 
to submit the iclas and subcribe to lists.


The project needs to submit a report to the incubator quarterly (monthly 
for the first 3 mo). I took the liberty tho submit the report for this 
month [1], but I expect one or more committers to step up (the ASF is a 
meritocracy) and take care (with help) of admin duties. Once most 
everybody subscribes to the list, such communication should happen on 
the (mailing) lists.


Best,
Hadrian

[1] https://wiki.apache.org/incubator/February2016


On 02/01/2016 12:51 AM, Tony Faustini wrote:

Hi Hadrian, thanks for setting this all up. I have already sent in my ICLA and 
I hope that the other contributors will follow this week. We are working on our 
corporate CLA and that too should be in place soon. We are excited about the 
creation of this community and we look forward to others participating.

Again thanks for setting  up the iota polling we hope this will become a 
vibrant community of interest for many individuals and corporations alike.

-Tony


On Jan 31, 2016, at 4:40 PM, Hadrian Zbarcea  wrote:

Hi Tony, Reza,

I found time this weekend to setup the iota podling. The proposal is now listed 
in the index or proposals [1]. The project status page [2] is setup and listed 
in the incubator list [3]. I will maintain the status page in the early phases. 
I created an issue for infra to create the project resources [4] (mailing 
lists, git repo, etc). This should not take long.

Please review the incubation policy on setting up a new podling [5]. What 
you'll need to do (or complete, because I think you already started) is the 
CLAs (individual and corporate), orientation (it really helps) and the code 
grant and IP clearance.

Feel free to get in touch with me as necessary to coordinate. It'll get easier 
once the mailing list are created.

Best,
Hadrian


[1] https://wiki.apache.org/incubator/ProjectProposals
[2] http://incubator.apache.org/projects/iota.html
[3] http://incubator.apache.org/projects/
[4] https://issues.apache.org/jira/browse/INFRA-11168
[5] 
http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling





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

Re: [RESULT][VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

Hi Tony, Reza,

I found time this weekend to setup the iota podling. The proposal is now 
listed in the index or proposals [1]. The project status page [2] is 
setup and listed in the incubator list [3]. I will maintain the status 
page in the early phases. I created an issue for infra to create the 
project resources [4] (mailing lists, git repo, etc). This should not 
take long.


Please review the incubation policy on setting up a new podling [5]. 
What you'll need to do (or complete, because I think you already 
started) is the CLAs (individual and corporate), orientation (it really 
helps) and the code grant and IP clearance.


Feel free to get in touch with me as necessary to coordinate. It'll get 
easier once the mailing list are created.


Best,
Hadrian


[1] https://wiki.apache.org/incubator/ProjectProposals
[2] http://incubator.apache.org/projects/iota.html
[3] http://incubator.apache.org/projects/
[4] https://issues.apache.org/jira/browse/INFRA-11168
[5] 
http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling




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

Re: [VOTE] Accept Beam into the Apache Incubator

[Hadrian Zbarcea]

elix Cheung[felixche...@apache.org]
  * Ajay Yadava [ajay.ya...@inmobi.com]
  * Liang Chen  [chenliang...@huawei.com]
  * Renaud Richardet[renaud (at) apache (dot) org]
  * Bakey Pan   [bakey1...@gmail.com]
  * Andreas Neumann [a...@apache.org]
  * Suresh Marru[sma...@apache.org]
  * Hadrian Zbarcea [hzbar...@gmail.com]

== Affiliations ==

The initial committers are from six organizations. Google developed
Dataflow and the Dataflow SDK, data Artisans developed the Flink runner,
and Cloudera (Labs) developed the Spark runner.

  * Cloudera
   * Tom White
  * Data Artisans
   * Aljoscha Krettek
   * Kostas Tzoumas
   * Maximilian Michels
   * Stephan Ewen
  * Google
   * Ben Chambers
   * Dan Halperin
   * Davor Bonaci
   * Frances Perry
   * James Malone
   * Kenneth Knowles
   * Luke Cwik
   * Tyler Akidau
   * Robert Bradshaw
  * PayPal
   * Amit Sela
  * Slack
   * Josh Wills
  * Talend
   * Jean-Baptiste Onofré

== Sponsors ==

=== Champion ===

  * Jean-Baptiste Onofre [jbono...@apache.org]

=== Nominated Mentors ===

  * Jean-Baptiste Onofre   [jbono...@apache.org]
  * Jim Jagielski  [j...@apache.org]
  * Venkatesh Seetharam[venkat...@apache.org]
  * Bertrand Delacretaz[bdelacre...@apache.org]
  * Ted Dunning[tdunn...@apache.org]

=== Sponsoring Entity ===

The Apache Incubator


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



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

Re: [DISCUSS] Apache Dataflow Incubator Proposal

[Hadrian Zbarcea]

Hi Bertrand,

Your suggested name only has an entropy of 0.19153. You may consider 
adding a special character or two :). To standardize (every company 
seems to like this lately) we may consider using SHA-256 for our project 
names. Being of fixed length it will help Sally in her templates for 
press releases.


Sorry, couldn't resit :)
Hadrian


On 01/28/2016 06:25 AM, Bertrand Delacretaz wrote:

On Thu, Jan 28, 2016 at 11:41 AM, Serge Huber  wrote:

...Please ignore my last message, I missed the fact that a project was already 
existing
with the name “Arrow”...


Hehe, that's the risk when using common names, with about 200 projects
here. Naming your project sdkjhkjhsdfxyhs is safer in this respect but
has other disadvantages.

-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

Re: [DISCUSS] Apache Beam Incubator Proposal (was Apache Dataflow Incubator Proposal)

[Hadrian Zbarcea]

Hi JB,

I was on the fence, because there are already so many contributors and 
one can contribute without being on the proposal. But then, because this 
proposal is impressive in the level of support received, I thought I'd 
throw my hat in as well (because I really see myself actually 
contributing code). So if you don't mind add me to the proposal too.


It is quite unique and interesting to see one project with such 
overwhelming support in the incubator.


Cheers,
Hadrian


On 01/27/2016 12:25 PM, Jean-Baptiste Onofré wrote:

Hi James,

As discussed together, I like the name. Let me update the proposal wiki.

Thanks !
Regards
JB

On 01/27/2016 06:22 PM, James Malone wrote:

Hi everyone,

Based on the feedback concerning naming, we would like to rename the
proposal and the project. We want to do this early to ensure we don't
disrupt the project based on naming. To that end, the name we propose to
use is:

Apache Beam

The name Beam is based on a joining of Batch and strEAM to showcase the
unified nature of the model and tools. We also wanted to select a name
which is simple, memorable, and also not already in use.

Best,

James

On Fri, Jan 22, 2016 at 2:07 AM, Jean-Baptiste Onofré 
wrote:


It makes perfect sense, and it's something that we already discussed.

Thanks James and Marvin.

@James, yes, we are going to deal with that together, not a problem at
all. I agree that renaming should happen now.
As discussed, we should be back with a new name early next week.

I'm happy to see the discussion now (and thanks again Marvin for details
and always helpful messages): it's exactly the purpose of sending the
discussion thread on the incubator mailing list.

Thanks guys !

Regards
JB


On 01/22/2016 02:19 AM, James Malone wrote:


Thank you for such a detailed response Marvin!

Everything you mention makes a lot of sense. Needless to say, we don't
want
to squander cycles, break any rules, or throw velocity into disarray
all
due to a name.

To that end, I am going to work with JB to amend the proposal with
respect
to renaming. I'm also going to clarify a name change would be an
immediate-term to-do item so it does not block creation creation of
lists,
repositories, and so on.

Best,

James

I am going to work with JB to amend the proposal to indicate

On Thu, Jan 21, 2016 at 9:30 AM, Marvin Humphrey

wrote:

On Wed, Jan 20, 2016 at 3:30 PM, James Malone

 wrote:


If we need to rename, we would ideally choose a new name, change the
project name at that time, and start our refactoring with that new
name.


Is


is acceptable for us to flag a name change as something we need to
do as


a


near-term (1st month) item in incubation (if accepted)? If a
rename is
required I'd like to add it to our to-do roadmap but also not
block our
proposal on a renaming. I ask so we can address this concern in
the best
way possible.



That's acceptable.  Project naming issues do not block entry into the
Incubator, they block graduation from the Incubator.

Because "dataflow" is descriptive, it will be hard to defend as
a trademark.  The Wikipedia article on trademark distinctiveness
explains
things well:

  https://en.wikipedia.org/wiki/Trademark_distinctiveness

A weak mark both increases the amount of volunteer effort that goes
into dealing with infringement cases and makes bad outcomes more
likely.
It is not an absolute requirement that Apache projects have defensible
names,
but painful past experience has taught us that mishandled branding can
deal
surprising amounts of damage to a project community.

But beyond that, the issue of "Google Cloud Dataflow" vs. "Apache
Dataflow" is
a blocker.  One or the other will have to be renamed, and since the
software
is being donated but apparently not the brand, it sounds like renaming
the
prospective Apache project will be required and you should add that
task
to
your roadmap.

Changing names in the middle of incubation is disruptive because it
requires
renaming infrastructure resources, impacting both the Apache
Infrastructure
team and also the podling's developer and user communities.  My
suggestion
would be that immediately after the VOTE to enter incubation
concludes,
you
only create a dev mailing list and deal with the renaming immediately,
delaying the creation of other resources until after the renaming is
resolved.
However, the exact plan is something you can work out with your
Mentors.

Marvin Humphrey

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






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

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

[RESULT][VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

Vote passes with:
[10] +1 - amareshwari, jmclean, hthomann, humbedooh, sterling, jbonofre, 
jhyde, venkatesh, jamestaylor, hadrian

[ 3] +1 - (non-binding)
[ 0]  0 -
[ 0] -1 -

Congrats to the iota community and welcome to the ASF. I will work with 
the iota community and our infra to get the project set up in the incubator.


Cheers,
Hadrian

On 01/16/2016 03:40 PM, Hadrian Zbarcea wrote:

The vote is as usually open for at least 72 hours.

Here's my +1.

Hadrian


On 01/16/2016 03:12 PM, Hadrian Zbarcea wrote:

Hi,

The iota proposal [1] (initially Tempo) was proposed about 6 weeks ago.

Because of the naming conflict that would have likely required to change
name at graduation, the project name was changed to "Apache iota" (the
greek letter), which resonates better with the IoT field the project
targets and passed a summary podling name search.

The code was made available in December for our review and answers on
the general@ list have been answered.

We think it's time to move to the next step, a formal vote. Therefore...

Please cast your vote to:
[] +1 - accept Apache iota as a new incubating project
[]  0 - not sure
[] -1 - do not accept the Apache iota project (because: ...)

Thanks,
Hadrian


[1] https://wiki.apache.org/incubator/IotaProposal
[2] https://en.wikipedia.org/wiki/Iota


-

iota Proposal

Abstract

The Apache Foundation has been very successful in bringing together key
software components that have enabled people to interact with each other
via a variety of content platforms and it will no doubt continue to do
so. At the same time modern society is becoming increasingly dependent
on devices that interact with each other and with people. The amount of
data that will be produced by devices will be orders of magnitude
greater than what has been produced by humans in the past. In addition,
the orchestration of devices and people will be an important area of
growth for the foreseeable future. This new dynamic will eventually
become manifest in a growing number of Apache projects that enable this
to occur. Our wish is to contribute to this movement by contributing the
iota system to the Open Source Community via the Apache Foundation.
Apache iota is an open platform to interconnect any and all devices,
sensors, people, and applications, henceforth referred to as points,
through a scalable, secure, and modular architecture, enabling
applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a global
company orchestrating millions of devices and people across different
continents. Either way you face the same fundamental problem; namely,
how do you manage many points in a secure robust and meaningful manner?
Apache iota is an open source software system that enables homeowners
and global companies to download a software system that provides secure
and robust orchestration.

The iota system consists of a variety of components:

A basic but extensible desktop
An extensible mechanism for capturing data from a variety of sources
A set of translators that feed the data capture mechanism and a
framework for the development of additional translators
A secure means of moving data using digital envelopes based on symmetric
and asymmetric encryption and decryption via Apache Kafka
Optionally maintaining data encrypted in a datastore
Support for a variety of data repositories
Authentication and authorization using OAuth2
Secure APIs for access to data and the system information
User management
Device management
Automated software upgrades via Salt
Configuration management
Robust basic infrastructure based on Apache Mesos that enables
scalability
Dockerized applications
Background

We are in the midst of a revolution in which the Internet of Things
(IoT) is poised to impact the development of our society in ways we can
not even begin to imagine. Unfortunately, we know of no coherent OSS
(Open Source Software) solution that can harness the potentialities of
this increasingly important trend. Manufacturers of IoT devices, both in
the consumer and industrial spaces, continue to develop proprietary
systems. Apache iota is an open source IoT system that creates an open
source solution enabling the orchestration of IoT devices that brings
the benefits of OSS to this space. Apache iota was initially developed
by Litbit and is deployed in a growing number of Industrial contexts,
especially in the context of Data Center Infrastructure.

Rationale

Apache iota is a general platform for orchestrating IoT devices in both
consumer and industrial contexts. It is complementary to the existing
Apache projects and is itself built using of a number of Apache
projects. Bringing iota into Apache is very beneficial to both the
Apache community and the IoT community.

The rapid growth of IoT need

Re: [VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

I want to encourage more IPMC members to cast a vote, in case this 
thread went unnoticed.


Cheers,
Hadrian

On 01/16/2016 03:40 PM, Hadrian Zbarcea wrote:

The vote is as usually open for at least 72 hours.

Here's my +1.

Hadrian


On 01/16/2016 03:12 PM, Hadrian Zbarcea wrote:

Hi,

The iota proposal [1] (initially Tempo) was proposed about 6 weeks ago.

Because of the naming conflict that would have likely required to change
name at graduation, the project name was changed to "Apache iota" (the
greek letter), which resonates better with the IoT field the project
targets and passed a summary podling name search.

The code was made available in December for our review and answers on
the general@ list have been answered.

We think it's time to move to the next step, a formal vote. Therefore...

Please cast your vote to:
[] +1 - accept Apache iota as a new incubating project
[]  0 - not sure
[] -1 - do not accept the Apache iota project (because: ...)

Thanks,
Hadrian


[1] https://wiki.apache.org/incubator/IotaProposal
[2] https://en.wikipedia.org/wiki/Iota


-

iota Proposal

Abstract

The Apache Foundation has been very successful in bringing together key
software components that have enabled people to interact with each other
via a variety of content platforms and it will no doubt continue to do
so. At the same time modern society is becoming increasingly dependent
on devices that interact with each other and with people. The amount of
data that will be produced by devices will be orders of magnitude
greater than what has been produced by humans in the past. In addition,
the orchestration of devices and people will be an important area of
growth for the foreseeable future. This new dynamic will eventually
become manifest in a growing number of Apache projects that enable this
to occur. Our wish is to contribute to this movement by contributing the
iota system to the Open Source Community via the Apache Foundation.
Apache iota is an open platform to interconnect any and all devices,
sensors, people, and applications, henceforth referred to as points,
through a scalable, secure, and modular architecture, enabling
applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a global
company orchestrating millions of devices and people across different
continents. Either way you face the same fundamental problem; namely,
how do you manage many points in a secure robust and meaningful manner?
Apache iota is an open source software system that enables homeowners
and global companies to download a software system that provides secure
and robust orchestration.

The iota system consists of a variety of components:

A basic but extensible desktop
An extensible mechanism for capturing data from a variety of sources
A set of translators that feed the data capture mechanism and a
framework for the development of additional translators
A secure means of moving data using digital envelopes based on symmetric
and asymmetric encryption and decryption via Apache Kafka
Optionally maintaining data encrypted in a datastore
Support for a variety of data repositories
Authentication and authorization using OAuth2
Secure APIs for access to data and the system information
User management
Device management
Automated software upgrades via Salt
Configuration management
Robust basic infrastructure based on Apache Mesos that enables
scalability
Dockerized applications
Background

We are in the midst of a revolution in which the Internet of Things
(IoT) is poised to impact the development of our society in ways we can
not even begin to imagine. Unfortunately, we know of no coherent OSS
(Open Source Software) solution that can harness the potentialities of
this increasingly important trend. Manufacturers of IoT devices, both in
the consumer and industrial spaces, continue to develop proprietary
systems. Apache iota is an open source IoT system that creates an open
source solution enabling the orchestration of IoT devices that brings
the benefits of OSS to this space. Apache iota was initially developed
by Litbit and is deployed in a growing number of Industrial contexts,
especially in the context of Data Center Infrastructure.

Rationale

Apache iota is a general platform for orchestrating IoT devices in both
consumer and industrial contexts. It is complementary to the existing
Apache projects and is itself built using of a number of Apache
projects. Bringing iota into Apache is very beneficial to both the
Apache community and the IoT community.

The rapid growth of IoT needs to be harnessed in the Open Source
Community. We believe the Apache Foundation is a great fit as the
long-term home for iota, as it provides an established process for
community-driven development and decision making by consensus. This 

Re: [VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

The vote is as usually open for at least 72 hours.

Here's my +1.

Hadrian


On 01/16/2016 03:12 PM, Hadrian Zbarcea wrote:

Hi,

The iota proposal [1] (initially Tempo) was proposed about 6 weeks ago.

Because of the naming conflict that would have likely required to change
name at graduation, the project name was changed to "Apache iota" (the
greek letter), which resonates better with the IoT field the project
targets and passed a summary podling name search.

The code was made available in December for our review and answers on
the general@ list have been answered.

We think it's time to move to the next step, a formal vote. Therefore...

Please cast your vote to:
[] +1 - accept Apache iota as a new incubating project
[]  0 - not sure
[] -1 - do not accept the Apache iota project (because: ...)

Thanks,
Hadrian


[1] https://wiki.apache.org/incubator/IotaProposal
[2] https://en.wikipedia.org/wiki/Iota


-

iota Proposal

Abstract

The Apache Foundation has been very successful in bringing together key
software components that have enabled people to interact with each other
via a variety of content platforms and it will no doubt continue to do
so. At the same time modern society is becoming increasingly dependent
on devices that interact with each other and with people. The amount of
data that will be produced by devices will be orders of magnitude
greater than what has been produced by humans in the past. In addition,
the orchestration of devices and people will be an important area of
growth for the foreseeable future. This new dynamic will eventually
become manifest in a growing number of Apache projects that enable this
to occur. Our wish is to contribute to this movement by contributing the
iota system to the Open Source Community via the Apache Foundation.
Apache iota is an open platform to interconnect any and all devices,
sensors, people, and applications, henceforth referred to as points,
through a scalable, secure, and modular architecture, enabling
applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a global
company orchestrating millions of devices and people across different
continents. Either way you face the same fundamental problem; namely,
how do you manage many points in a secure robust and meaningful manner?
Apache iota is an open source software system that enables homeowners
and global companies to download a software system that provides secure
and robust orchestration.

The iota system consists of a variety of components:

A basic but extensible desktop
An extensible mechanism for capturing data from a variety of sources
A set of translators that feed the data capture mechanism and a
framework for the development of additional translators
A secure means of moving data using digital envelopes based on symmetric
and asymmetric encryption and decryption via Apache Kafka
Optionally maintaining data encrypted in a datastore
Support for a variety of data repositories
Authentication and authorization using OAuth2
Secure APIs for access to data and the system information
User management
Device management
Automated software upgrades via Salt
Configuration management
Robust basic infrastructure based on Apache Mesos that enables scalability
Dockerized applications
Background

We are in the midst of a revolution in which the Internet of Things
(IoT) is poised to impact the development of our society in ways we can
not even begin to imagine. Unfortunately, we know of no coherent OSS
(Open Source Software) solution that can harness the potentialities of
this increasingly important trend. Manufacturers of IoT devices, both in
the consumer and industrial spaces, continue to develop proprietary
systems. Apache iota is an open source IoT system that creates an open
source solution enabling the orchestration of IoT devices that brings
the benefits of OSS to this space. Apache iota was initially developed
by Litbit and is deployed in a growing number of Industrial contexts,
especially in the context of Data Center Infrastructure.

Rationale

Apache iota is a general platform for orchestrating IoT devices in both
consumer and industrial contexts. It is complementary to the existing
Apache projects and is itself built using of a number of Apache
projects. Bringing iota into Apache is very beneficial to both the
Apache community and the IoT community.

The rapid growth of IoT needs to be harnessed in the Open Source
Community. We believe the Apache Foundation is a great fit as the
long-term home for iota, as it provides an established process for
community-driven development and decision making by consensus. This is
exactly the model we want for future iota development.

Initial Goals

Move the existing codebase to Apache
Integrate with the Apache developmen

[VOTE] Accept the iota project into the Apache Incubator

[Hadrian Zbarcea]

act and introduce license checking into the 
build and release process (for instance integrating Apache Rat).


iota has used 0MQ for some types of internal messaging, and 0MQ is 
licensed under the GNU Lesser General Public License. We are in the 
process of making the iota messaging layer pluggable, and plan to use 
Netty (which is licensed under Apache License v2) as our default 
messaging plugin (while keeping 0MQ as an optional plugin).


Cryptography

We do not expect iota to be a controlled export item due to the use of 
encryption. iota enables encryptions via a digital envelope using:


RSA 128 Bits
AES 128 Bits
Required Resources

Mailing lists

iota-user
iota-dev
iota-commits
iota-private (with moderated subscriptions)
Subversion Directory

Git is the preferred source control system: git://git.apache.org/iota

Issue Tracking

JIRA iota (IOTA)

Initial Committers

Rutvij Clerk 
Miron Costant 
Tony Faustini 
Reza Hajebi 
Amirhossein Jabbari < amirhossein at litbit dot com>
Shahin Mowzoon 
Scott Noteboom < notebooms at litbit dot com>
Sydney Noteboom 
Omkar Prabhu 
Bill Salter 
Don Shields 
Affiliations

Rutvij Clerk - Litbit
Miron Costant - Litbit
Tony Faustini - Litbit
Reza Hajebi - Litbit
Amirhossein Jabbari - Litbit
Shahin Mowzoon - Litbit
Scott Noteboom - Litbit
Sydney Noteboom - Litbit
Shailesh Patel - e2logy
Omkar Prabhu - Litbit
Bill Salter - Envise
Don Shields - Litbit
Sponsors

Champion

Hadrian Zbarcea 


Nominated Mentors

Sterling Hughes 
Daniel Gruno 
Justin Mclean 
Hadrian Zbarcea 


Sponsoring Entity

The Apache Incubator

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

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

Hi Tony,

I did rename the proposal page to IotaProposal [1].
Looks like there is enough interest and a lot of positive feedback to 
move to a vote. If no objection I will start it tomorrow.


Cheers,
Hadrian

[1] https://wiki.apache.org/incubator/IotaProposal


On 01/14/2016 05:19 PM, Tony Faustini wrote:

Hi Hadrian, I have made the changes to the Tempo proposal relative to it’s 
renaming as iota. The changes are in the proposal itself I don’’t think I can 
rename the top-level project name from Tempo to iota (let me know if I can or 
should). If anything else needs to be done please let me know.
Thanks
-Tony


On Jan 11, 2016, at 5:35 PM, Hadrian Zbarcea  wrote:

With a bit of delay due to the Holidays season, I think it's time to continue 
this thread.

The code has been available for a while to mentors and those who requested. I 
assume the mentors did take a look at it, I certainly did. The code looks clean 
and the idea sound. Plus the IoT field is one that matures fast and I consider 
a good fit for ASF technologies.

There is the outstanding issue of changing the name as it seems unlikely to graduate as 
Tempo. There is a proposal to incubate it under the "iota" name (whatever the 
capitalization). Tony, if you could update the proposal to reflect that (or whatever name 
you choose) it'd be great. After that, assuming no other objections or concerns, I would 
suggest starting a vote.

Cheers,
Hadrian


On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:

Hi Tony!

Has there been any activity around this proposal? I find it really interesting,
and just like Hadrian I really would love to see the code on GitHub (although
it is NOT a pre-requisite to being consider for ASF Incubator).

Thanks,
Roman.

P.S. Greetings from your past life managing JavaStudio ;-)


On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea  wrote:

Hi Tony,

It is a very interesting proposal and I would like to help out as well. I do
have a bit of experience of the IoT field, both part of my ASF contributions
and other work I did. I volunteer to be a mentor or champion. Looks like one
of your understated goals is to grow a community and I agree the ASF is the
right place for that.

You mentioned the code being available on github, but I couldn't find it
where I thought it could be [1]. Would it be possible to make the code
available to potential mentors? I think it would speed up the process and
you would get more support faster.

There were also a number of positive answers to your email on the incubator
list, but you were not cc'ed, so if you're not subscribed to the list you
might have missed them.

It's a great idea, thanks for considering the ASF incubator and it could
have great success given the growth of IoT.

Best Regards,
Hadrian

[1] https://github.com/litbit



On 12/02/2015 03:34 PM, Tony Faustini wrote:


To: general@incubator.apache.org

Hi All, Litbit is an enterprise IoT company comprised of individuals
that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel,
Cisco Systems and 365 Main. We are working with some of the world's
leading companies providing them with an enterprise IoT platform. We
value the open source community and the way it is changing enterprise
software. We are eager to build an open source community around Tempo
which powers RhythmOS our commercial offering.

Thanks
-Tony Faustini (Litbit Co)


Tempo - A Proposal for Apache Incubator

Abstract

The Apache Foundation has been very successful in bringing together
key software components that have enabled people to interact with each
other via a variety of content platforms and it will no doubt continue
to do so.  At the same time modern society is becoming increasingly
dependent on devices that interact with each other and with people.
The amount of data that will be produced by devices will be orders of
magnitude greater than what has been produced by humans in the past.
In addition, the orchestration of devices and people will be an
important area of growth for the foreseeable future. This new dynamic
will eventually become manifest in a growing number of Apache projects
that enable this to occur. Our wish is to contribute to this movement
by contributing the Tempo system to the Open Source Community via the
Apache Foundation. Tempo is an open platform to interconnect any and
all devices, sensors, people, and applications, henceforth referred to
as points, through a scalable, secure, and modular architecture,
enabling applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a
global company orchestrating millions of devices and people across
different continents.  Either way you face the same fundamental
problem; namely, how do you manage many points in a secure robust and
meaningful manner?  Tempo i

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

hadrian@minotaur:~$ ls -al Tempo.zip
-rw-r--r--  1 hadrian  hadrian  739185 Dec 19 16:45 Tempo.zip

Available to anybody who can access the host above.

Cheers,
Hadrian


On 01/14/2016 07:21 PM, P. Taylor Goetz wrote:

May I have access to the source code as well?

-Taylor


On Jan 11, 2016, at 8:35 PM, Hadrian Zbarcea  wrote:

With a bit of delay due to the Holidays season, I think it's time to continue 
this thread.

The code has been available for a while to mentors and those who requested. I 
assume the mentors did take a look at it, I certainly did. The code looks clean 
and the idea sound. Plus the IoT field is one that matures fast and I consider 
a good fit for ASF technologies.

There is the outstanding issue of changing the name as it seems unlikely to graduate as 
Tempo. There is a proposal to incubate it under the "iota" name (whatever the 
capitalization). Tony, if you could update the proposal to reflect that (or whatever name 
you choose) it'd be great. After that, assuming no other objections or concerns, I would 
suggest starting a vote.

Cheers,
Hadrian



On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:
Hi Tony!

Has there been any activity around this proposal? I find it really interesting,
and just like Hadrian I really would love to see the code on GitHub (although
it is NOT a pre-requisite to being consider for ASF Incubator).

Thanks,
Roman.

P.S. Greetings from your past life managing JavaStudio ;-)



On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea  wrote:
Hi Tony,

It is a very interesting proposal and I would like to help out as well. I do
have a bit of experience of the IoT field, both part of my ASF contributions
and other work I did. I volunteer to be a mentor or champion. Looks like one
of your understated goals is to grow a community and I agree the ASF is the
right place for that.

You mentioned the code being available on github, but I couldn't find it
where I thought it could be [1]. Would it be possible to make the code
available to potential mentors? I think it would speed up the process and
you would get more support faster.

There were also a number of positive answers to your email on the incubator
list, but you were not cc'ed, so if you're not subscribed to the list you
might have missed them.

It's a great idea, thanks for considering the ASF incubator and it could
have great success given the growth of IoT.

Best Regards,
Hadrian

[1] https://github.com/litbit




On 12/02/2015 03:34 PM, Tony Faustini wrote:

To: general@incubator.apache.org

Hi All, Litbit is an enterprise IoT company comprised of individuals
that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel,
Cisco Systems and 365 Main. We are working with some of the world's
leading companies providing them with an enterprise IoT platform. We
value the open source community and the way it is changing enterprise
software. We are eager to build an open source community around Tempo
which powers RhythmOS our commercial offering.

Thanks
-Tony Faustini (Litbit Co)


Tempo - A Proposal for Apache Incubator

Abstract

The Apache Foundation has been very successful in bringing together
key software components that have enabled people to interact with each
other via a variety of content platforms and it will no doubt continue
to do so.  At the same time modern society is becoming increasingly
dependent on devices that interact with each other and with people.
The amount of data that will be produced by devices will be orders of
magnitude greater than what has been produced by humans in the past.
In addition, the orchestration of devices and people will be an
important area of growth for the foreseeable future. This new dynamic
will eventually become manifest in a growing number of Apache projects
that enable this to occur. Our wish is to contribute to this movement
by contributing the Tempo system to the Open Source Community via the
Apache Foundation. Tempo is an open platform to interconnect any and
all devices, sensors, people, and applications, henceforth referred to
as points, through a scalable, secure, and modular architecture,
enabling applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a
global company orchestrating millions of devices and people across
different continents.  Either way you face the same fundamental
problem; namely, how do you manage many points in a secure robust and
meaningful manner?  Tempo is an open source software system that
enables homeowners and global companies to download a software system
that provides secure and robust orchestration.

The Tempo system consists of a variety of components:

- A basic but extensible desktop
- An extensible mechanism for capturing data from a variety of sources
- A set of translators that fe

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

With a bit of delay due to the Holidays season, I think it's time to 
continue this thread.


The code has been available for a while to mentors and those who 
requested. I assume the mentors did take a look at it, I certainly did. 
The code looks clean and the idea sound. Plus the IoT field is one that 
matures fast and I consider a good fit for ASF technologies.


There is the outstanding issue of changing the name as it seems unlikely 
to graduate as Tempo. There is a proposal to incubate it under the 
"iota" name (whatever the capitalization). Tony, if you could update the 
proposal to reflect that (or whatever name you choose) it'd be great. 
After that, assuming no other objections or concerns, I would suggest 
starting a vote.


Cheers,
Hadrian


On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:

Hi Tony!

Has there been any activity around this proposal? I find it really interesting,
and just like Hadrian I really would love to see the code on GitHub (although
it is NOT a pre-requisite to being consider for ASF Incubator).

Thanks,
Roman.

P.S. Greetings from your past life managing JavaStudio ;-)


On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea  wrote:

Hi Tony,

It is a very interesting proposal and I would like to help out as well. I do
have a bit of experience of the IoT field, both part of my ASF contributions
and other work I did. I volunteer to be a mentor or champion. Looks like one
of your understated goals is to grow a community and I agree the ASF is the
right place for that.

You mentioned the code being available on github, but I couldn't find it
where I thought it could be [1]. Would it be possible to make the code
available to potential mentors? I think it would speed up the process and
you would get more support faster.

There were also a number of positive answers to your email on the incubator
list, but you were not cc'ed, so if you're not subscribed to the list you
might have missed them.

It's a great idea, thanks for considering the ASF incubator and it could
have great success given the growth of IoT.

Best Regards,
Hadrian

[1] https://github.com/litbit



On 12/02/2015 03:34 PM, Tony Faustini wrote:


To: general@incubator.apache.org

Hi All, Litbit is an enterprise IoT company comprised of individuals
that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel,
Cisco Systems and 365 Main. We are working with some of the world's
leading companies providing them with an enterprise IoT platform. We
value the open source community and the way it is changing enterprise
software. We are eager to build an open source community around Tempo
which powers RhythmOS our commercial offering.

Thanks
-Tony Faustini (Litbit Co)


Tempo - A Proposal for Apache Incubator

Abstract

The Apache Foundation has been very successful in bringing together
key software components that have enabled people to interact with each
other via a variety of content platforms and it will no doubt continue
to do so.  At the same time modern society is becoming increasingly
dependent on devices that interact with each other and with people.
The amount of data that will be produced by devices will be orders of
magnitude greater than what has been produced by humans in the past.
In addition, the orchestration of devices and people will be an
important area of growth for the foreseeable future. This new dynamic
will eventually become manifest in a growing number of Apache projects
that enable this to occur. Our wish is to contribute to this movement
by contributing the Tempo system to the Open Source Community via the
Apache Foundation. Tempo is an open platform to interconnect any and
all devices, sensors, people, and applications, henceforth referred to
as points, through a scalable, secure, and modular architecture,
enabling applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a
global company orchestrating millions of devices and people across
different continents.  Either way you face the same fundamental
problem; namely, how do you manage many points in a secure robust and
meaningful manner?  Tempo is an open source software system that
enables homeowners and global companies to download a software system
that provides secure and robust orchestration.

The Tempo system consists of a variety of components:

- A basic but extensible desktop
- An extensible mechanism for capturing data from a variety of sources
- A set of translators that feed the data capture mechanism and a
framework for the development of additional translators
- A secure means of moving data using digital envelopes based on
symmetric and asymmetric encryption and decryption via Apache Kafka
- Optionally maintaining data encrypted in a datastore
- Support for a variety of data repositories
- 

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

The logic is that the project afaik is not open source and the code not 
publicly available. Until the project is accepted in the incubator I see 
it fair to respect its current private status.


The code was provided to the ASF in good faith by litbit. I will note 
that it wasn't Tony's express request to keep it private, it was my 
recommendation and promise. I stand by it. If we intent to make it 
public we should at least ask Tony/litbit first.


Cheers,
Hadrian

On 12/30/2015 01:51 PM, Ted Dunning wrote:

On Wed, Dec 30, 2015 at 10:48 AM, Hadrian Zbarcea 
wrote:


The code was already made available. Since the project is not yet accepted
in the incubator, we thought it best to not publish it.



What is the logic behind that decision?



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

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

Hi Roman,

The code was already made available. Since the project is not yet 
accepted in the incubator, we thought it best to not publish it. Because 
you expressed interest I sent you a private mail with the code location.


Tony needs to decide on the proposed name, it is unlikely that the 
project will be able to graduate with the current name. Mentors are 
expected to take a look at the code. Once these tasks are completed 
we'll come back for a vote in the incubator.


Happy New Year,
Hadrian


On 12/26/2015 08:01 PM, Roman Shaposhnik wrote:

On Sat, Dec 26, 2015 at 4:43 PM, Tony Faustini  wrote:

Hi Roman, yes there has been activity. I sent Hadrian the source code to
review and share with others who are interested in being mentors. Our plan
is to make it public via Github or Bitbucket. We are also reviewing the name
‘Tempo’ as there may be a issue with TempoIQ (https://www.tempoiq.com/). We
have several other names that might even be better than Tempo. If you are
interested in seeing the source code Hadrian can make it available to you.
We will work on the GitHub public version right after the holidays.


Great! There's no rush -- I'll wait for your code to appear on GitHub.

Just don't forget to update the text on the Incubator wiki with
the GitHub URL. That's how we're tracking your updates.


Great that you remember JavaStudio that’s a project that Oracle should
consider making OpenSource.


Indeed! And I'd love to see it go ASF ;-)

Thanks,
Roman.

-
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 Fineract into Apache Incubator

[Hadrian Zbarcea]

+1 (binding)

Good luck!
Hadrian

On 12/10/2015 04:21 AM, Ross Gardler wrote:

I would like to call a vote on accepting the Fineract project into the Apache 
Incubator. The proposal is pasted below and posted at 
http://wiki.apache.org/incubator/FineractProposal

The vote will run for at least 72hrs

[ ] +1 Accept Fineract into the Apache Incubator
[ ] +/-0 Fine, go ahead
[ ] -1 Do not accept Fineract because [your fully justified reason for 
objection]

Thanks,
Ross

= Fineract Proposal =

== Abstract ==

Fineract (\’fīn-,ə-ˌrakt\: A hypercube for digital financial services) is an 
open source system for core banking as a platform. Fineract provides a 
reliable, robust, and affordable solution for entrepreneurs, financial 
institutions, and service providers to offer financial services to the world’s 
2 billion under and unbanked.

== Proposal ==

The aim of this proposal is to bring the Mifos X codebase and community under 
the Apache Software Foundation (ASF) umbrella in order to help coordinate the 
development effort of the growing number of organizations which contribute to 
it, and give it the confidence of the neutral, transparent, and open source 
governance policy of the ASF.

The name Mifos X will remain the property of the Mifos Initiative (a US based 
501(c)(3)) and will be used for a specific distribution of the Fineract code. 
All development efforts of the Mifos Initiative will be transferred to the 
Fineract project.

== Background ==

Mifos X is a mature and robust platform that provides loan, savings, and 
business management functionality based on market proofed requirements. The 
project was started in 2006 at the Grameen Foundation, initially creating the 
Generation One  solutions of Mifos 1 and Mifos 2, the industry’s first open 
source and web-based MIS, to support the Joint Liability Group (JLG) lending 
methodology created by Mohammed Yunus, which gained him and the Grameen Bank 
the Nobel Peace Prize for his financial work in 2006.

In 2011 the independent Mifos Initiative, a 501(c)(3), was founded with two 
goals:
  1. Create the Generation Two solution Mifos X,  an extensible API-driven 
platform purpose built for Financial Inclusion
2. Build and govern an open source community of users, developers, and service 
providers committed to using Mifos X for Financial Inclusion.

Since then a worldwide community of users, partners, and volunteers has grown 
that utilizes, develops, and supports Mifos X. More than 40 partners from 
Africa, India, China, South-East Asia and Latin America, with over 120 
deployments and 3.5 million clients, have enhanced the platform based on 
regional requirements and national regulatories.

== Rationale ==

Financial Inclusion - providing financial services to the world’s 2 billion 
under and unbanked, enabling them to become a part of the global economy - 
requires an affordable, reliable, scalable, and robust solution.

The adoption of mobile solutions and digital financial services is increasing 
at an incredible pace and has led to an influx of new innovators, financial 
institutions, and service providers into the Financial Inclusion space and into 
the Mifos community which is growing at an accelerating rate year-over-year 
since 2012.

Our rationale for joining the ASF is that as an Apache project we can better 
manage the growth and governance of our community and provide the community the 
confidence of sustainable long-term open source management, which strengthens 
their commitment and continues the growth of our vibrant, diverse community, 
collectively innovating around a single codebase, sharing the social mission to 
eliminate poverty.

== Initial Goals ==

The initial goals of the Fineract transition under the ASF umbrella are to 
establish a new home for an already fully functioning project, and also make 
sure that the entire development community governs itself in the Apache Way.

In addition, we will ensure:
1. All dependencies are compliant with the Apache License and the ASFs 
licensing policies.
 a. To become compliant a refactoring of the reporting module is necessary 
to be able to swap out the Pentaho Reporting Engine. This work will be 
undertaken during incubation.
  2. Ongoing development based on our collaboratively established 2016 roadmap, 
and bring the process into the Apache Way.
3. Creating releases per Apache guidelines.

== Current Status ==

=== Meritocracy ===

We already have attributes of meritocracy embedded in our community.
  * We have a developer email list which identifies active community members 
who then become committers .
* On the user email list new features are introduced and discussed, forming the 
product roadmap, and prioritization is based on merit and need.
* We have successfully graduated 13 Google Summer of Code interns, many of whom 
have become long-term committers and developers to the project.

=== Community ===

There are more than a hundred developers within an active developer m

[PODLINGNAMESEARCH] Tempo - will there be issues using this name?

[Hadrian Zbarcea]

This is an issue for trademarks actually. For the reason Tony described 
I assume the podling should look for a more suitable name.


Advice appreciated.
Hadrian

On 12/04/2015 03:03 PM, Tony Faustini wrote:

Hi all,  as part of the due diligence for the TempoProposal we need to see if the 
name ’Tempo’ is viable. I did a search of the US Trademark Electronic Search System 
(TESS) and found 188 live uses of this name as well as a Google Search. The most 
interesting one that emerged and that is directly related to this technology space 
was a Chicago based start-up called TempoIQ see 
https://www.crunchbase.com/organization/tempo#/entity 
. It would be good to 
get the Apache Legal team perspective on this. I didn’t do an International search on 
the name yet but will do so if needed.

Thanks
-Tony





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

Re: [PORPOSAL] Fineract

[Hadrian Zbarcea]

Please add me as a mentor as well. I have significant experience in the 
financial industry and I am very interested in seeing this project be a 
wild success.


Thanks,
Hadrian


On 12/04/2015 02:31 AM, Markus Geiß wrote:

Hey all,

hope this finds you well.

We, the Mifos community, want to propose our project for incubation.

Please find the proposal below.

= Fineract Proposal =

== Abstract ==

Fineract (\’fīn-,ə-ˌrakt\: A hypercube for digital financial services) is
an open source system for core banking as a platform. Fineract provides a
reliable, robust, and affordable solution for entrepreneurs, financial
institutions, and service providers to offer financial services to the
world’s 2 billion under and unbanked.

== Proposal ==

The aim of this proposal is to bring the Mifos X codebase and community
under the Apache Software Foundation (ASF) umbrella in order to help
coordinate the development effort of the growing number of organizations
which contribute to it, and give it the confidence of the neutral,
transparent, and open source governance policy of the ASF.

The name Mifos X will remain the property of the Mifos Initiative (a US
based 501(c)(3)) and will be used for a specific distribution of the
Fineract code. All development efforts of the Mifos Initiative will be
transferred to the Fineract project.

== Background ==

Mifos X is a mature and robust platform that provides loan, savings, and
business management functionality based on market proofed requirements. The
project was started in 2006 at the Grameen Foundation, initially creating
the Generation One  solutions of Mifos 1 and Mifos 2, the industry’s first
open source and web-based MIS, to support the Joint Liability Group (JLG)
lending methodology created by Mohammed Yunus, which gained him and the
Grameen Bank the Nobel Peace Prize for his financial work in 2006.

In 2011 the independent Mifos Initiative, a 501(c)(3), was founded with two
goals:
  1. Create the Generation Two solution Mifos X,  an extensible API-driven
platform purpose built for Financial Inclusion
  2. Build and govern an open source community of users, developers, and
service providers committed to using Mifos X for Financial Inclusion.

Since then a worldwide community of users, partners, and volunteers has
grown that utilizes, develops, and supports Mifos X. More than 40 partners
from Africa, India, China, South-East Asia and Latin America, with over 120
deployments and 3.5 million clients, have enhanced the platform based on
regional requirements and national regulatories.

== Rationale ==

Financial Inclusion - providing financial services to the world’s 2 billion
under and unbanked, enabling them to become a part of the global economy -
requires an affordable, reliable, scalable, and robust solution.

The adoption of mobile solutions and digital financial services is
increasing at an incredible pace and has led to an influx of new
innovators, financial institutions, and service providers into the
Financial Inclusion space and into the Mifos community which is growing at
an accelerating rate year-over-year since 2012.

Our rationale for joining the ASF is that as an Apache project we can
better manage the growth and governance of our community and provide the
community the confidence of sustainable long-term open source management,
which strengthens their commitment and continues the growth of our vibrant,
diverse community, collectively innovating around a single codebase,
sharing the social mission to eliminate poverty.

== Initial Goals ==

The initial goals of the Fineract transition under the ASF umbrella are to
establish a new home for an already fully functioning project, and also
make sure that the entire development community governs itself in the
Apache Way.

In addition, we will ensure:
  1. All dependencies are compliant with the Apache License and the ASFs
licensing policies.
 a. To become compliant a refactoring of the reporting module is
necessary to be able to swap out the Pentaho Reporting Engine. This work
will be undertaken during incubation.
  2. Ongoing development based on our collaboratively established 2016
roadmap, and bring the process into the Apache Way.
  3. Creating releases per Apache guidelines.

== Current Status ==

=== Meritocracy ===

We already have attributes of meritocracy embedded in our community.
  * We have a developer email list which identifies active community members
who then become committers .
  * On the user email list new features are introduced and discussed,
forming the product roadmap, and prioritization is based on merit and need.
  * We have successfully graduated 13 Google Summer of Code interns, many of
whom have become long-term committers and developers to the project.

=== Community ===

There are more than a hundred developers within an active developer mailing
list. We have a large and growing installed base of users (financial
institutions) and a diverse eco-system of regional service partners 

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Hadrian Zbarcea]

Hi Tony,

It is a very interesting proposal and I would like to help out as well. 
I do have a bit of experience of the IoT field, both part of my ASF 
contributions and other work I did. I volunteer to be a mentor or 
champion. Looks like one of your understated goals is to grow a 
community and I agree the ASF is the right place for that.


You mentioned the code being available on github, but I couldn't find it 
where I thought it could be [1]. Would it be possible to make the code 
available to potential mentors? I think it would speed up the process 
and you would get more support faster.


There were also a number of positive answers to your email on the 
incubator list, but you were not cc'ed, so if you're not subscribed to 
the list you might have missed them.


It's a great idea, thanks for considering the ASF incubator and it could 
have great success given the growth of IoT.


Best Regards,
Hadrian

[1] https://github.com/litbit


On 12/02/2015 03:34 PM, Tony Faustini wrote:

To: general@incubator.apache.org

Hi All, Litbit is an enterprise IoT company comprised of individuals
that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel,
Cisco Systems and 365 Main. We are working with some of the world's
leading companies providing them with an enterprise IoT platform. We
value the open source community and the way it is changing enterprise
software. We are eager to build an open source community around Tempo
which powers RhythmOS our commercial offering.

Thanks
-Tony Faustini (Litbit Co)


Tempo - A Proposal for Apache Incubator

Abstract

The Apache Foundation has been very successful in bringing together
key software components that have enabled people to interact with each
other via a variety of content platforms and it will no doubt continue
to do so.  At the same time modern society is becoming increasingly
dependent on devices that interact with each other and with people.
The amount of data that will be produced by devices will be orders of
magnitude greater than what has been produced by humans in the past.
In addition, the orchestration of devices and people will be an
important area of growth for the foreseeable future. This new dynamic
will eventually become manifest in a growing number of Apache projects
that enable this to occur. Our wish is to contribute to this movement
by contributing the Tempo system to the Open Source Community via the
Apache Foundation. Tempo is an open platform to interconnect any and
all devices, sensors, people, and applications, henceforth referred to
as points, through a scalable, secure, and modular architecture,
enabling applications to generate analysis, create actions and/or add
intelligence to their behaviors and patterns.

Proposal

Perhaps you are a homeowner configuring the interaction between your
family and all the smart devices in your home. Or you might be a
global company orchestrating millions of devices and people across
different continents.  Either way you face the same fundamental
problem; namely, how do you manage many points in a secure robust and
meaningful manner?  Tempo is an open source software system that
enables homeowners and global companies to download a software system
that provides secure and robust orchestration.

The Tempo system consists of a variety of components:

- A basic but extensible desktop
- An extensible mechanism for capturing data from a variety of sources
- A set of translators that feed the data capture mechanism and a
framework for the development of additional translators
- A secure means of moving data using digital envelopes based on
symmetric and asymmetric encryption and decryption via Apache Kafka
- Optionally maintaining data encrypted in a datastore
- Support for a variety of data repositories
- Authentication and authorization using oAuth2
- Secure APIs for access to data and the system information
- User management
- Device management
- Automated software upgrades via Salt
- Configuration management
- Robust basic infrastructure based on Apache Mesos that enables scalability
- Dockerized applications

Background

We are in the midst of a revolution in which the Internet of Things
(IoT) is poised to impact the development of our society in ways we
can not even begin to imagine. Unfortunately, we know of no coherent
OSS (Open Source Software) solution that can harness the
potentialities of this increasingly important trend. Manufacturers of
IoT devices, both in the consumer and industrial spaces, continue to
develop proprietary systems. Tempo is an open source IoT system that
creates an open source solution enabling the orchestration of IoT
devices that brings the benefits of OSS to this space. Tempo was
initially developed by Litbit and is deployed in a growing number of
Industrial contexts, especially in the context of Data Center
Infrastructure.

Rationale

Tempo is a general platform for orchestrating IoT devices in both
consumer and industrial contexts. It is complementary to the e

[QUESTION] Rewriting history

[Hadrian Zbarcea]

Probably a bad subject in the context of other things going on :).

Apache Brooklyn is faced with the tasks of migrating it's repo(s) post 
graduation and there are some very large *pre-incubation* artifacts in 
the git repo that we would like removed.


The question was asked on general@ [1] many moons ago, but received no 
answer (the original thread [1] indicates the offenders). We'd like to 
use this occasion to split the git repo into multiple smaller once (more 
naturally tailored to the project), so one idea would be, I think, to 
leave incubator-brooklyn.git as is and just extract what we need 
(everything except the large binaries) in new repos. Note: afaiui, those 
artifacts we're never part of an ASF release.


I am not sure what would be acceptable per ASF (intensely debated) policies.

Thoughts?
Hadrain


[1] 
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3c556f0973.7030...@cloudsoftcorp.com%3E


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

Re: Kalumet retirement steps

[Hadrian Zbarcea]

I think the rest of the contributions come from Olivier Lamy another ASFer.

+1 to your your proposal for a resolution.

Cheers,
Hadrian

On 11/19/2015 04:21 PM, Marvin Humphrey wrote:

Thanks for speaking up, folks.

Based on the information in this thread, I plan to resolve the
copyright issue on Kalumet's podling status page with a resolution
date of today.

Technically, I have only received reassurances that the codebase is
"almost exclusively" work that originates with one individual who has
an ICLA on file; what we really need to know in order to check that
box is that *all* of the code without exception is OK.

If anyone objects to resolving the copyright issue, either because
they are aware of actual uncleared code within Kalumet's repo, or
because they are uncomfortable with my assumption that all the code is
clear, please say so.

Marvin Humphrey

On Thu, Nov 19, 2015 at 5:09 AM, Jean-Baptiste Onofré  wrote:

Hi Hadrian and Marvin,

I replied on the kalumet mailing list.

It's not a problem at all that the Kalumet's code remain on svn.

Sorry for the delay guys.

Regards
JB


On 11/19/2015 05:44 AM, Hadrian Zbarcea wrote:


Hi Marvin,

As far as I remember, Kalumet is almost exclusively the work of JB
Onofre who is an ASF member, therefore I don't see a problem.

That said I think it's best to wait a bit and let JB speak up. I cc'ed
him, just to make sure he notices this thread.

Cheers,
Hadrian

On 11/18/2015 05:29 PM, Marvin Humphrey wrote:


On Sun, Nov 15, 2015 at 6:56 PM, Marvin Humphrey
 wrote:


The copyright checkbox for Kalumet is marked with a question mark,
which I
interpret as "not checked off":

  http://incubator.apache.org/projects/kalumet#Copyright

A successful incubating release would have settled the issue, but I
did some
research and it seems that while the Kalumet podling attempted an
incubating
release of their 0.6 branch, it doesn't look like it was ever officially
completed.

If the copyright status cannot be resolved, I will have to delete
`trunk`,
`tags`, and `branches` from
<https://svn.apache.org/repos/asf/incubator/kalumet>.

Can someone provide a definitive answer on whether it is OK for
Kalumet's code
to remain visible in svn?



I'll give this a couple more days.  If no one has spoken up by then, I
will proceed with deleting the code from svn.

Marvin Humphrey

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



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.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



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

Re: Kalumet retirement steps

[Hadrian Zbarcea]

Hi Marvin,

As far as I remember, Kalumet is almost exclusively the work of JB 
Onofre who is an ASF member, therefore I don't see a problem.


That said I think it's best to wait a bit and let JB speak up. I cc'ed 
him, just to make sure he notices this thread.


Cheers,
Hadrian

On 11/18/2015 05:29 PM, Marvin Humphrey wrote:

On Sun, Nov 15, 2015 at 6:56 PM, Marvin Humphrey  wrote:


The copyright checkbox for Kalumet is marked with a question mark, which I
interpret as "not checked off":

 http://incubator.apache.org/projects/kalumet#Copyright

A successful incubating release would have settled the issue, but I did some
research and it seems that while the Kalumet podling attempted an incubating
release of their 0.6 branch, it doesn't look like it was ever officially
completed.

If the copyright status cannot be resolved, I will have to delete `trunk`,
`tags`, and `branches` from
.

Can someone provide a definitive answer on whether it is OK for Kalumet's code
to remain visible in svn?


I'll give this a couple more days.  If no one has spoken up by then, I
will proceed with deleting the code from svn.

Marvin Humphrey

-
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: [RESULT][VOTE] Graduate Apache Brooklyn from incubator (corrected)

[Hadrian Zbarcea]

Please find below the corrected version of the proposed resolution:
 * corrected first paragraph to agree with the 3rd
 * added last paragraph (releasing incubator)
 * corrected before last paragraph (migration task)

Since I am getting paranoid, a nod from other pairs of eyes would be 
highly appreciated.


Looking forward to an uneventful graduation,
Hadrian


X. Establish the Apache Brooklyn 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 a software framework for modeling,
monitoring and managing cloud applications through autonomic
blueprints.

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

RESOLVED, that the Apache Brooklyn Project be and hereby is
responsible for the creation and maintenance of a software
framework for modeling, monitoring and managing cloud
applications through autonomic blueprints; and be it further

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

* Aled Sage 
* Alex Heneveld 
* Andrea Turli 
* Andrew Kennedy 
* Ciprian Ciubotariu 
* Hadrian Zbarcea 
* Richard Downer 
* Sam Corbett 
* Svetoslav Neykov 

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

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



On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:

Vote passes with:

+1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
+1 - 2 non-binding
-1 - 0

We will submit the proposal below to the board for approval (including
jbonofre and olamy in the PMC).

Many thanks again to our mentors and the incubator in general for the
guidance.

Hadrian




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

Re: Not just yet

[Hadrian Zbarcea]

Hi John,

I was a reply to your message, but it was not pointed at you. Seriously. 
Maybe the "curious" part a bit, because you asked. We know however from 
experience that there are many other people who are curious what happens 
when unusual events like this take place and even a few, as I called 
them "conspiracy theorists".


Normally I wouldn't write such a reply, but I wanted to take the 
opportunity to also point the positive (because the negatives are so 
often debated at length), which is the fact that board actually was 
accommodating and offered the opportunity for correction. Just to paint 
a clearer picture of the *people* behind board@.


So concerns like the ones you raised are, from my point of view, very 
welcome. Especially as they come in the right tone. They create 
opportunities for learning for lurkers.


Cheers,
Hadrian


On 10/22/2015 11:13 AM, John D. Ament wrote:

On Oct 22, 2015 8:05 AM, "Hadrian Zbarcea"  wrote:


For the curious and conspiracy theorists :) let me complete the picture.

I did actually attend the board meeting as I usually do and the board was

gracious enough to give me a couple of minutes to correct the resolution.
Unfortunately, whimsy wouldn't save the corrected resolution, for a reason
I don't yet understand. I went a second round with svn, but ran out of time.


Looks like I got the graduation gods really angry. This is not what a

podling should expect from an ASF member.

I'll assume that this was pointed to me.  If your email was clearer I
wouldn't have been confused about scope.  I apologize for any concerns this
raised.

Note that I never said you needed a revote.  It wasn't clear that this came
out of the board, in the past when we had failed graduations it never made
it back to the incubator.



Hadrian

On 10/22/2015 07:03 AM, John D. Ament wrote:


Ah ha.  It wasn't clear from the original email this happened during the
board meeting.  Now I get it.
On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:


On Wed, Oct 21, 2015 at 7:58 PM, John D. Ament 
wrote:


I think that's my point.  Those two weeks should be used to get

incubator

approval.  If you wait 4 weeks you don't graduate until December.



The Incubator isn't going to vote again.  The text of the graduation
resolution from an Incubator recommendation is advisory and the Board
often modifies it. (The Incubator gets the text wrong embarrassingly
often.)  The Board passing a resolution to establish a TLP is the
crucial step from the standpoint of the Foundation as a corporate
entity.

It's regrettable that the glitch was not caught until there was little
time left during today's meeting, but resolutions are powerful tools
and it's important to get the language right. The Foundation's bylaws
constrain the Board's ability to act -- it's not supposed to be easy.

Marvin Humphrey

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






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





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

Re: Not just yet

[Hadrian Zbarcea]

For the curious and conspiracy theorists :) let me complete the picture.

I did actually attend the board meeting as I usually do and the board 
was gracious enough to give me a couple of minutes to correct the 
resolution. Unfortunately, whimsy wouldn't save the corrected 
resolution, for a reason I don't yet understand. I went a second round 
with svn, but ran out of time.


Looks like I got the graduation gods really angry. This is not what a 
podling should expect from an ASF member.


Hadrian

On 10/22/2015 07:03 AM, John D. Ament wrote:

Ah ha.  It wasn't clear from the original email this happened during the
board meeting.  Now I get it.
On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:


On Wed, Oct 21, 2015 at 7:58 PM, John D. Ament 
wrote:


I think that's my point.  Those two weeks should be used to get incubator
approval.  If you wait 4 weeks you don't graduate until December.


The Incubator isn't going to vote again.  The text of the graduation
resolution from an Incubator recommendation is advisory and the Board
often modifies it. (The Incubator gets the text wrong embarrassingly
often.)  The Board passing a resolution to establish a TLP is the
crucial step from the standpoint of the Foundation as a corporate
entity.

It's regrettable that the glitch was not caught until there was little
time left during today's meeting, but resolutions are powerful tools
and it's important to get the language right. The Foundation's bylaws
constrain the Board's ability to act -- it's not supposed to be easy.

Marvin Humphrey

-
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

Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[Hadrian Zbarcea]

The resolution to graduate Apache Brooklyn out of the incubator was 
tabled due to a procedural issue. This has nothing to do with the code 
or the community.


The reason was an editorial error on my side, I used the wrong template 
and the last paragraph releasing the incubator from its responsibilities 
was missing from the resolution. It is unfortunate that nobody caught 
that, but the error is completely mine.


We will resubmit in 4 weeks.

Million apologies,
Hadrian

On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:

Vote passes with:

+1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
+1 - 2 non-binding
-1 - 0

We will submit the proposal below to the board for approval (including
jbonofre and olamy in the PMC).

Many thanks again to our mentors and the incubator in general for the
guidance.

Hadrian


On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E





X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
     * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.


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

Re: Draft Report October 2015 - please review

[Hadrian Zbarcea]

tor.apache.org/guides/releasemanagement.html

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

   None beyond the above-mentioned.

How has the community developed since the last report?

   - Mailing list traffic has significantly increased from 60-80
 messages/month in April-July to 171 in August and 227 in September. Some
 of that could be JIRA integration, but we still have 17 unique human
 authors now, up from 13 in July.
   - Increasing participation in our biweekly community syncs. We now get
 around 7-11 participants, up from the 5-8 we were getting in May-July.
 See minutes at: http://s.apache.org/8kF

   - Wiki: Ruth has done a wonderful job populating and organizing the wiki
 from our scattered docs. Now we have 24 wiki pages describing use cases,
 architecture, installation/configuration, administration, and the REST
 API. https://cwiki.apache.org/confluence/display/MYRIAD/Myriad+Home
   - Website under development, with awesome Myriad logo.
 https://issues.apache.org/jira/browse/MYRIAD-144 preview at
 http://klucar.github.io/myriad-site/
   - We started a #myriad IRC channel on Freenode, and are in the process of
 integrating it with ASFBot.
 https://issues.apache.org/jira/browse/INFRA-10485
   - Well-attended talk by Mohit and Santosh at MesosCon.
 https://www.youtube.com/watch?v=lU2VE08fOD4
   - Swapnil, Sarjeet, and Mitra won 1st place in freestyle category at docker
 global hack day for docker based multi-tenant YARN/Myriad clusters.
 https://blog.docker.com/2015/09/docker-global-hack-day-3-winners/

How has the project developed since the last report?

   - Finally got the SGA from Paypal and migrated our source to Apache git!
 Still need to figure how to integrate it into our commit workflow.
   - Resolved 14 JIRAs: http://s.apache.org/3dc
   - Merged the following PRs (from the old github repo)
   * Multi-project build changes (PR#108)
   * Improved unit testing (PR#112)
   * Myriad Logo update (PR#113)
   * Dynamically configurable NM Ports (PR#102)
   * Fine-grained scaling (PR#91)
   * Upgrade to Hadoop 2.7 (PR#116)
   * Complete Myriad HA Implementation (PR#123)
   * Run MyriadExecutor as NodeManager AuxService (PR#118,123)

Date of last release:

   Santosh will release manage the Myriad 0.1.0 release, our first release
   under Apache. We created a 0.1.0 version tag in JIRA, and targeted some
   pre-release issues for Apache copyright/namespace changes. We'll try to
   merge in some outstanding PRs, but there are no other feature blockers, so
   we hope to cut our first release candidate this month.

When were the last committers or PMC members elected?

   - One new committer has been privately nominated and voted in, awaiting
 IPMC Board approval. Then he/she still has to accept the invitation.
   - Another is in the midst of voting this week.

Signed-off-by:

   [ ](myriad) Benjamin Hindman
   [ ](myriad) Danese Cooper
   [ ](myriad) Ted Dunning
   [ ](myriad) Luciano Resende

Shepherd/Mentor notes:





ODF Toolkit

Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents

Shepherd/Mentor notes:

   Rob Weir (robweir):

 No report submitted, though I did remind the PPMC.   I sense some "report
 fatigue" since they missed the July report deadline, submitted then in
 time for August, but lacked a mentor sign off, and then submitted again in
 September and did get sign off.

   Drew Farris (drew):

 Kudos to robweir activity as a mentor, however this project could use
 another mentor. Generally little traffic or activity.


OpenAz

Tools and libraries for developing Attribute-based Access Control (ABAC)
Systems in a variety of languages.

OpenAz has been incubating since 2015-01-20.

Three most important issues to address in the move towards graduation:

   1. Confirm 1.0.0 as the first release
   2. Get website up to attract more attention
   3. Vote to confirm if any JIRA's are needed to be closed for 1st release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

   None

How has the community developed since the last report?

   n/a

How has the project developed since the last report?

   Preparing for v1.0.0 release

Date of last release:

   -XX-XX

When were the last committers or PMC members elected?

   no new since initial

Signed-off-by:

   [ ](openaz) Emmanuel Lecharny
   [ ](openaz) Colm O Heigeartaigh
   [ ](openaz) Hadrian Zbarcea

Shepherd/Mentor notes:

   P. Taylor Goetz (ptgoetz):

 The OpenAz report is pretty sparse and has not been signed off
 by any of the podling's mentors. dev@ mailing list activity is
 extremely low (15 messages in the past 3 months). I would recommend
 the top priority be for the project to expa

[RESULT][VOTE] Graduate Apache Brooklyn from incubator

[Hadrian Zbarcea]

Vote passes with:

+1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
+1 - 2 non-binding
-1 - 0

We will submit the proposal below to the board for approval (including 
jbonofre and olamy in the PMC).


Many thanks again to our mentors and the incubator in general for the 
guidance.


Hadrian


On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E




X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
     * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.


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

Re: [VOTE] Graduate Apache Brooklyn from incubator

[Hadrian Zbarcea]

+1 from me too.
Hadrian

On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E




X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
     * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.


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

Re: [VOTE] Graduate Apache Brooklyn from incubator

[Hadrian Zbarcea]

Ack
   * Olivier Lamy 

Thanks,
Hadrian


On 09/29/2015 08:15 PM, Olivier Lamy wrote:

+1 (binding)
I'd like to remain on PMC and try to help in the future.

Olivier

On 29 September 2015 at 00:06, Hadrian Zbarcea  wrote:


This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E



X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
     * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.







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

Re: [VOTE] Graduate Apache Brooklyn from incubator

[Hadrian Zbarcea]

Ack. We will add
  * Jean-Baptiste Onofré 

as a PMC member in the final resolution.

Hadrian


On 09/29/2015 08:28 AM, Jean-Baptiste Onofré wrote:

By the way, I would like to stay PMC on Brooklyn and try to help.

Regards
JB

On 09/29/2015 12:54 PM, Jean-Baptiste Onofré wrote:

+1 (binding)

Regards
JB

On 09/28/2015 04:06 PM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E






X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
     * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and
hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.

-
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 Apache Brooklyn from incubator

[Hadrian Zbarcea]

In hindsight, the cc: to dev@brooklyn created more confusion. This is 
the incubator vote. I think we should drop the cc: to dev@ (kept it for 
this email, to make sure Joe sees it).


Thanks,
Hadrian

On 09/29/2015 07:49 AM, Joe Brockmeier wrote:

On Mon, Sep 28, 2015, at 10:06 AM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...


+1 (binding)

Best,

jzb



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

Re: [VOTE] Accept Unomi into the Apache Incubator

[Hadrian Zbarcea]

+1 (binding)
Hadrian

On 09/23/2015 05:14 AM, Jean-Baptiste Onofré wrote:

Hi all,

following the discussion about Unomi, I would like to call a vote for
accepting Unomi as a new incubator project.

The proposal text is included below, and available on the wiki:
http://wiki.apache.org/incubator/UnomiProposal

The discussion thread about Unomi is available here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C36A4090C-7444-4A20-8C85-3C7B990D9502%40jahia.com%3E


The vote is open for 72 hours:

[ ] +1 accept Unomi in the Incubator
[ ] ±0
[ ] -1 (please give reason)

Thanks,
Regards
JB
--

= Apache Unomi incubation proposal =
== Abstract ==
Unomi is a reference implementation of the OASIS Context Server
specification currently being worked on by the OASIS Context Server
Technical Committee. It provides a high-performance user profile and
event tracking server.

== Proposal ==
The server is a data management platform that provides real-time user
profile and event storage as well as a rule engine and fully featured
REST+JSON interfaces which make integration with very different systems
easier.

One of the main objectives of this implementation is to be modular and
flexible enough to relatively easily build integration into systems such
as CMS, WCM, CRM or even ERP. Built using Apache Karaf and
ElasticSearch, it is designed to also be easily clusterable to address
high-traffic scenarios where lots of profile data will need to be
updated at a high frequency.

== Background ==
Unomi was built from scratch to serve as a reference implementation for
the OASIS Context Server proposal. It has been developed by Jahia Software.

It initially served as a test-bed while working on the specifics of the
new proposal, to make sure that the concepts being discussed and decided
would make sense in an actual implementation. At the same time, Jahia,
one of the companies involved in the standardization work, needed a
basis to build their new Marketing Factory product, so it made a lot of
sense to start this way. Thanks to a lot of work done in the standard,
the implementation was produced relatively quickly and this made it
possible to build a commercial product on top of this implementation
that will be released in Winter 2015. This implies that the core of the
commercial product being proposed here will undergo a full set of QA
tests, including and scalability tests.

Another important objective was to provide a platform that deals with
user data in an “ethical” way, in order to make the usage of personal
data more transparent and to improve privacy. Through the work in the
standard and this open source implementation, it is the hope of the
original designers that it will be easier for all users of this
technology to fully understand how the data is being used and what type
of control is exercised over it. A transparent usage of customer data
could become, in the near future, a key tool to keep customer loyalty.
Companies would then be able to leverage digital marketing frameworks
capabilities such as Unomi, but, as a fair - and quite possibly legally
mandatory - counterpart, should allow end users to understand the data
being used, as well as the way it is used, in order to give them more
control over which data to share or to anonymise.

The purpose is to bring Jahia Marketing Factory codebase into the Apache
Software Foundation (ASF) in order to build a vibrant, diverse and
self-governed open source community around the technology. Jahia will
continue to market and sell Jahia Marketing Factory based on Unomi.
Unomi and Jahia Marketing Factory will be managed separately. This
proposal covers the Unomi source code (mainly written in Java), Unomi
documentation and other materials currently available on GitHub. Unomi
is our primary choice for a name of the project.

== Rationale ==
Building highly scalable, performant and flexible personalization
architectures requires major efforts. The complexities of requirements,
integrations and use cases is directly related to the number of users,
and Apache projects usually get a lot of visibility and usage. Therefore
it was a goal from the start to share this project with the ASF, as it
is believed this is the best way to achieve the true potential of this
codebase, to make it highly visible and continually improve on its
design and implementation to make it the best tool for the job for a
wide variety of use cases.

The project, as it sits a bit higher than usual BigData frameworks,
could be used a front-end to a lot of existing Apache project that could
be integrated to help deliver more power into the platform. For example
Unomi doesn’t currently include machine learning but it could very well
be expanded to include a module that would use Apache Mahout. In the
same way, for the persistence layer, an already existing Service
Provider Interface could be used to provide other backends such as HDFS,
Cassandra, Solr or any other.

== Initial Goals ==
Our initial

[VOTE] Graduate Apache Brooklyn from incubator

[Hadrian Zbarcea]

This is the Incubator vote to decide if Apache Brooklyn should graduate 
from the Incubator. Please see the proposed resolution below.


See also discuss thread [1]. Mentors were invited to join the future TLP 
PMC on request. Invitation is open until this vote is closed.


This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E




X. Establish the Apache Brooklyn 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 tools that help automate various
administrative tasks or information lookup activities.

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

RESOLVED, that the Apache Brooklyn Project be and hereby is
responsible for the creation and maintenance of a software
framework for modeling, monitoring, and managing cloud
applications through autonomic blueprints; and be it further

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

* Aled Sage 
* Alex Heneveld 
* Andrea Turli 
* Andrew Kennedy 
    * Ciprian Ciubotariu 
* Hadrian Zbarcea 
* Richard Downer 
* Sam Corbett 
* Svetoslav Neykov 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
is tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Brooklyn Project.

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

Re: [DISCUSS] Apache Brooklyn graduation as TLP

[Hadrian Zbarcea]

Looks like there are no issues or concerns. I will start the formal vote.

Cheers,
Hadrian


On 09/24/2015 01:26 PM, Hadrian Zbarcea wrote:

The Brooklyn community and project made significant advances in the past
months and believes it is ready to graduate as a top-level project.

The Apache Brooklyn is very active. The PPMC doubled in size and
increased diversity in the past year. A few release candidates and two
very solid final releases in the past few months. There were
presentations about Brooklyn at at least 3 big conferences I attended
this year (including ApacheCon in Austin). Talks about Brooklyn are
scheduled at ApacheCon EU in Budapest next week, it would be great to
use the occasion and venue to announce the graduation plans.

A vote passed unanimously on the dev@ list (7 +1 votes). Please find
below references to the graduation preparation artifacts:
* discussion on dev list [1]
* vote thread [2]
* approved podling name search [3]
* incubation status [4]
* proposed resolution below

We believe Apache Brooklyn is ready to become a top-level
project and if the IPMC agree we will move to a formal vote. There are a
few more items to be updated on the project status page during the next
couple of days.

Many thanks to the mentors and the IPMC for the support,
Hadrian


[1]
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C55F4C48B.2050906%40gmail.com%3E

[2]
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C56004B52.3030408%40gmail.com%3E

[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-82
[4] http://incubator.apache.org/projects/brooklyn.html



X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

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

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

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

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
 * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.



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

[DISCUSS] Apache Brooklyn graduation as TLP

[Hadrian Zbarcea]

The Brooklyn community and project made significant advances in the past 
months and believes it is ready to graduate as a top-level project.


The Apache Brooklyn is very active. The PPMC doubled in size and 
increased diversity in the past year. A few release candidates and two 
very solid final releases in the past few months. There were 
presentations about Brooklyn at at least 3 big conferences I attended 
this year (including ApacheCon in Austin). Talks about Brooklyn are 
scheduled at ApacheCon EU in Budapest next week, it would be great to 
use the occasion and venue to announce the graduation plans.


A vote passed unanimously on the dev@ list (7 +1 votes). Please find 
below references to the graduation preparation artifacts:

* discussion on dev list [1]
* vote thread [2]
* approved podling name search [3]
* incubation status [4]
* proposed resolution below

We believe Apache Brooklyn is ready to become a top-level
project and if the IPMC agree we will move to a formal vote. There are a 
few more items to be updated on the project status page during the next 
couple of days.


Many thanks to the mentors and the IPMC for the support,
Hadrian


[1] 
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C55F4C48B.2050906%40gmail.com%3E
[2] 
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C56004B52.3030408%40gmail.com%3E

[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-82
[4] http://incubator.apache.org/projects/brooklyn.html



X. Establish the Apache Brooklyn 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 tools that help automate various
administrative tasks or information lookup activities.

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

RESOLVED, that the Apache Brooklyn Project be and hereby is
responsible for the creation and maintenance of a software
framework for modeling, monitoring, and managing cloud
applications through autonomic blueprints; and be it further

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

* Aled Sage 
* Alex Heneveld 
* Andrea Turli 
* Andrew Kennedy 
* Ciprian Ciubotariu 
* Hadrian Zbarcea 
* Richard Downer 
* Sam Corbett 
* Svetoslav Neykov 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
is tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Brooklyn Project.


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

Re: [NOTICE] Brooklyn PPMC += Sam Corbett

[Hadrian Zbarcea]

Thanks Marvin!
Hadrian

On 09/11/2015 10:36 PM, Marvin Humphrey wrote:

On Fri, Sep 11, 2015 at 7:24 PM, Hadrian Zbarcea  wrote:

Samuel James Corbett (sjcorbett) was voted as PPMC member for Apache
Brooklyn. That took place more than a year ago, but nowhere do I find a
record of the notice to general@. There was an issue with the mail servers
that month (07/2014) but not sure how related.

Vote thread result:
msgid: 53b2cd8d.4060...@gmail.com

If I am mistaken, this notice is redundant.


Notices of PPMC committer/PPMC votes should go to private@incubator,
not general@incubator.  The IPMC was in fact notified at the end of
June 2014.

Cheers,

Marvin Humphrey

-
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

[NOTICE] Brooklyn PPMC += Sam Corbett

[Hadrian Zbarcea]

Samuel James Corbett (sjcorbett) was voted as PPMC member for Apache 
Brooklyn. That took place more than a year ago, but nowhere do I find a 
record of the notice to general@. There was an issue with the mail 
servers that month (07/2014) but not sure how related.


Vote thread result:
msgid: 53b2cd8d.4060...@gmail.com

If I am mistaken, this notice is redundant.

Hadrian

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

Re: [VOTE] Release Apache Brooklyn 0.8.0-incubating [rc2]

[Hadrian Zbarcea]

+1 (binding)

More details with my vote on the community thread. This release 
completes the package migration to org.apache.brooklyn.* and 
incorporates the feedback from the previous release vote.


Great work guys!
Hadrian

On 09/09/2015 09:32 AM, Alex Heneveld wrote:


This is to call for a vote for the release of Apache Brooklyn
0.8.0-incubating.


The Apache Brooklyn community have voted in favour of making this release:

Vote thread:

https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C55E9C778.80907%40CloudsoftCorp.com%3E


Result email:

https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201509.mbox/%3C55F02D46.4070904%40CloudsoftCorp.com%3E


We now ask the IPMC to vote on this release.

This release comprises of a source code distribution, and a
corresponding binary distribution, and Maven artifacts.

The source and binary distributions, including signatures, digests, etc.
can be found at:

https://dist.apache.org/repos/dist/dev/incubator/brooklyn/apache-brooklyn-0.8.0-incubating-rc2


The artifact SHA-256 checksums are as follows:

   948a299b620f0dc49558701898c519f61aca20605e968b6fa6a0ef7db429389d
*apache-brooklyn-0.8.0-incubating-rc2-bin.tar.gz
   63a16993180b40a3f866582a32f0a48744aeafa5472bbb9f397330dfccbf41c9
*apache-brooklyn-0.8.0-incubating-rc2-bin.zip
   f8989790caf92c02baeffb69180ae0a2fdbb4e05629eb6c8fe6b82f10d4d2b03
*apache-brooklyn-0.8.0-incubating-rc2-src.tar.gz
   1b7e6777cb5d8f75af846166d2e82d352e5344a14ed3c47df01b2a9f9bea3ea0
*apache-brooklyn-0.8.0-incubating-rc2-src.zip

The Nexus staging repository for the Maven artifacts is located at:

https://repository.apache.org/content/repositories/orgapachebrooklyn-1009

All release artifacts are signed with the following key:

 https://people.apache.org/keys/committer/heneveld.asc

KEYS file available here:

https://dist.apache.org/repos/dist/release/incubator/brooklyn/KEYS


The artifacts were built from git commit ID
aaf97039ab33c2b489479fe9fd2c21732731c277:

https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git;a=commit;h=aaf97039ab33c2b489479fe9fd2c21732731c277



Please vote on releasing this package as Apache Brooklyn 0.8.0-incubating.
The vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Brooklyn 0.8.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...


Best,
Alex




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

[NOTICE] Brooklyn PPMC += Ciprian Ciubotariu

[Hadrian Zbarcea]

Ciprian Ciubotariu was voted as PPMC member for Apache Brooklyn.

Vote thread result:
msgid: 55e8f909.9070...@gmail.com

Please advise if any issues or objections, otherwise we send the 
official invite after the 72 hour period has passed.


Hadrian

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

Re: [VOTE] Release Apache Brooklyn 0.7.0-incubating [rc1]

[Hadrian Zbarcea]

Hi Cedric,

It's dug down somewhere in my memories, I bet somebody like Marvin or 
Roman or Ted could quickly pull out their magic hats the authoritative 
link. There ore other projects that release in non-asf packages (e.g. 
geronimo specs in javax.*) for very good reasons. I don't know what and 
how applies to your concrete Groovy situation. While there are 
exceptions, my understanding is that it's a pretty strong requirement.


The rationale has something to do, iirc, with the fact that we cannot 
release code in packages for which we don't own the domain and would 
create confusion and possibly conflicts for downstream users. If I am 
wrong, hopefully somebody will correct me.


Cheers,
Hadrian



On 07/22/2015 10:21 AM, Cédric Champeau wrote:

* renaming of packages from brooklyn.* to org.apache.brooklyn.* will be
required for graduation, I strongly encourage that step to be taken care of
in the next release.


Where is such a requirement described? As far as I understand, package
names are best suited if they start with org.apache.*, but it's not a
strong requirement. If it is, then it would basically mean that Groovy
(the podling I am member of) would never go out of incubation, because
of our binary backwards compatibility requirements.

-
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 Apache Brooklyn 0.7.0-incubating [rc1]

[Hadrian Zbarcea]

Hi Justin,

Being part of the maven archetype, these are the templates to 
"quickstart" a user with a project using brooklyn. Such projects would 
not be licensed to the ASF, but we could also say that it's then their 
business to update the copyright header. I am kinda neutral on this one, 
but I guess this would be the explanation for the missing headers.


Cheers,
Hadrian


On 07/22/2015 10:08 AM, Justin Mclean wrote:

Hi,

+1 binding

I checked the source release.
- release contains incubating
- signatures and hashed good
- DISCLAIMER exists
- LICENSE and NOTICE good (a few minor issues)
- no unexpected binary files
- some source files are missing headers (see 
/usage/archetypes/quickstart/src/brooklyn-sample/src/test/java/com/acme/sample/brooklyn/sample/app/*.java)
- can compile from source

Minor issues:
- LICENCE is missing standard appendix
- probably no need for the full text of MIT and BSD as the short version is 
preferred and already used
- LICENSE is missing:
riak (see 
./software/nosql/src/main/resources/brooklyn/entity/nosql/riak/vm.args + others)
normalize.css (see 
./sandbox/mobile-app/src/main/webapp/assets/mobile/libs/mcasimir-mobile-angular-ui-be39011/dist/css/mobile-angular-ui-base.css)
mobileangular-ui (see 
./sandbox/mobile-app/src/main/webapp/assets/mobile/libs/mcasimir-mobile-angular-ui-be39011/dist/js/mobile-angular-ui.js)
r.js (see ./usage/jsgui/src/build/requirejs-maven-plugin/r.js)
angular (see 
./sandbox/mobile-app/src/main/webapp/assets/mobile/libs/angular-1.2.19)

I didn’t have time to check the connivence binaries.

Thanks,
Justin


-
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 Apache Brooklyn 0.7.0-incubating [rc1]

[Hadrian Zbarcea]

+1

I already voted in the PPMC vote, I am pasting below my findings.

Cheers,
Hadrian

--
Excellent work on the release Richard.

* tested the binaries on Linux, they work fine, although not my focus; 
the ASF releases code as source, so I focused more on the source distro

* downloading, building from source works fine, all tests pass
* started the webui (binary and source distro), it works, looks great 
found no issues
* licensing looks ok, although it requires more work which I would 
strongly suggest to be fixed for the next release
 i. there should be not license (LICENSE, NOTICE, DISCLAIMER) in test 
directories, I already submitted a PR for that
 ii. LICENSE files should be consolidated into one place (./LICENSE) 
and diffs taken care of (e.g. list of jars from 
./usage/dist/src/main/license/LICENSE is lost everywhere else)
 iii. Due to the dependency on bouncycastle, I suspect that a statement 
re: cryptography [1] may be necessary. I can look into it if that's ok 
with you.
* renaming of packages from brooklyn.* to org.apache.brooklyn.* will be 
required for graduation, I strongly encourage that step to be taken care 
of in the next release.
* the brooklyn-install.sh gave me a ton of grief, I had to tail the log 
to figure out what's going on, had to punch in a password a zillion 
times; I ended up setting NOPASSWD:ALL in my sudoers to somewhat 
alleviate the annoyance.




On 07/22/2015 02:49 AM, Richard Downer wrote:

This is to call for a vote for the release of Apache Brooklyn
0.7.0-incubating.

The Apache Brooklyn community have voted in favour of making this release:
Vote thread:
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201507.mbox/%3CCABQFKi1WapCMRUqQ93E7Qow5onKgL3nyG3HW9Cse7vo%2BtUChRQ%40mail.gmail.com%3E
Result email:
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201507.mbox/%3CCABQFKi2aJHHfXGC0xsMFU0odfB5X6FF5xhpHbs93%2BNfS-fNRZw%40mail.gmail.com%3E

We now ask the IPMC to vote on this release.

This release comprises of a source code distribution, and a corresponding
binary distribution, and Maven artifacts.

The source and binary distributions, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/brooklyn/apache-brooklyn-0.7.0-incubating-rc1

The artifact SHA-256 checksums are as follows:
c3b5c581f14b44aed786010ac7c8c2d899ea0ff511135330395a2ff2a30dd5cf
*apache-brooklyn-0.7.0-incubating-rc1-bin.tar.gz
cef49056ba6e5bf012746a72600b2cee8e2dfca1c39740c945c456eacd6b6fca
*apache-brooklyn-0.7.0-incubating-rc1-bin.zip
8069bfc54e7f811f6b57841167b35661518aa88cabcb070bf05aae2ff1167b5a
*apache-brooklyn-0.7.0-incubating-rc1-src.tar.gz
acd2229c44e93e41372fd8b7ea0038f15fe4aaede5a3bcc5056f28a770543b82
*apache-brooklyn-0.7.0-incubating-rc1-src.zip

The Nexus staging repository for the Maven artifacts is located at:
https://repository.apache.org/content/repositories/orgapachebrooklyn-1004

All release artifacts are signed with the following key:
https://people.apache.org/keys/committer/richard.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/brooklyn/KEYS

The artifacts were built from Git commit ID
24a23c5a4fd5967725930b8ceaed61dfbd225980
https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git;a=commit;h=24a23c5a4fd5967725930b8ceaed61dfbd225980


Please vote on releasing this package as Apache Brooklyn 0.7.0-incubating.

The vote will be open for at least 72 hours.
[ ] +1 Release this package as Apache Brooklyn 0.7.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...


Thanks,
Richard Downer



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

Re: [VOTE] TinkerPop 3.0.0.M9-incubating Release

[Hadrian Zbarcea]

+1

Could incubator members please find some time to take a look at this 
release so the vote could be closed, one way or another?


Thanks,
Hadrian

On 06/01/2015 11:45 AM, Marko Rodriguez wrote:

Hello general@incubators,

After 3 rounds of "3.0.0.M9-incubating-rc" releases the last couple of weeks, 
the participating vendors articulated their confidence in Apache TinkerPop providing an 
M9 release. The dev@tinkerpop vote passed with:

PMC: +1 (4), 0 (0), -1 (0)  -- one from mentor.

While Apache only recognizes the votes of the PMC, I think it is important to 
express the thoughts of the wider community given that TinkerPop is leveraged 
in the products of various graph system vendors.

Committers: +1 (1), 0 (0), -1 (0)
Vendors: +1 (3), 0 (0), -1 (0)

The VOTE thread(s) can be found here:

http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201505.mbox/%3CBBB00949-FFA0-4455-8F0E-3703771CC219%40gmail.com%3E
 (original but thread got broken -- use "next" till end)

http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201506.mbox/%3C70C3F6DE-CDF6-475F-9EC9-6ED08175BB2D%40gmail.com%3E
 (tally email)



TinkerPop now asks Incubator to VOTE on the release.

The release artifacts can be found at this location:

https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.0.0.M9-incubating/

The source distribution is provided by:
apache-tinkerpop-3.0.0.M9-incubating-source-release.zip

Two binary distributions are provided for user convenience:
apache-gremlin-console-3.0.0.M9-incubating-distribution.zip
apache-gremlin-server-3.0.0.M9-incubating-distribution.zip

The online docs can be found here:
http://tinkerpop.incubator.apache.org/docs/3.0.0.M9-incubating/ (user 
docs)

http://tinkerpop.incubator.apache.org/javadocs/3.0.0.M9-incubating/core/ (core 
javadoc)

http://tinkerpop.incubator.apache.org/javadocs/3.0.0.M9-incubating/full/ (full 
javadoc)

The tag in Apache Git can be found here:

https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=909977bdc8aa606c9762310af27dc4a20e83bd41

The release notes are available here:

https://github.com/apache/incubator-tinkerpop/blob/master/CHANGELOG.asciidoc#tinkerpop-300m9-release-date-may-26-2015

The [VOTE] will be open for the next 72 hours --- closing Thursday (June 4) at 
10:00am MST.

Thank you very much for your time and effort on TinkerPop,
Marko.

http://markorodriguez.com



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

Re: [VOTE] Accept CommonsRDF into the Apache Incubator

[Hadrian Zbarcea]

+1
Hadrian

On 02/27/2015 02:19 PM, Lewis John Mcgibbney wrote:

Hi general@,

Over the last while a number of individuals have been putting together a
proposal and gathering interest in proposing Commons RDF for acceptance
into the Apache Incubator. Having worked our way through the Incubator
documentation checklists -
http://incubator.apache.org/guides/proposal.html#formulating, we are now
brining this proposal back to the general@ list.

Commons RDF is a set of interfaces for the RDF 1.1 concepts that can be
used to expose common RDF-1.1 concepts using common Java interfaces. The
current CommondRDFProposal document can be found at -
https://wiki.apache.org/incubator/CommonsRDFProposal

This thread is therefore aimed at obtaining general consensus from the
incubator community on whether the proposal document is suitable and
whether the project as described should begin an incubation period at
Apache.

The VOTE is therefore as follows

[ ] +1 I am happy with Commons RDF entering incubation
[ ] +0/-0 I am neither yay or nay
[ ] -1 I am not happy with this proposal because

The VOTE will be open for at least 72 hours.

p.s. Here is my +1 PPMC binding



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

Re: Software Grants for GitHub Projects...

[Hadrian Zbarcea]

Matt, you're saying the same thing, except it's not one individual but 
two [1] (spmallette + okram) , who own the vast majority of the IP. They 
also claim to be in the possession of CLAs from the other contributors.


The problem was not insufficient data to substantiate claims, but TMI. 
Secretary@ pushed back for that clear reason, the proposal for 
resubmission addressed that. If secretary@ will have additional concerns 
(including forwarding to legal@), we'll address them as they come.


Hadrian

[1] https://github.com/tinkerpop/tinkerpop3/graphs/contributors


On 02/02/2015 09:53 AM, Matt Franklin wrote:

On Mon Feb 02 2015 at 8:09:43 AM Hadrian Zbarcea  wrote:


On 02/01/2015 03:19 PM, Benson Margulies wrote:

On Sun, Feb 1, 2015 at 2:12 PM, John D. Ament 

wrote:

On Sun Feb 01 2015 at 1:05:10 AM Alex Harui  wrote:


On 1/31/15, 9:09 AM, "Benson Margulies"  wrote:


On Sat, Jan 31, 2015 at 11:32 AM, Matt Franklin
 wrote:

On Sat Jan 31 2015 at 11:22:15 AM Benson Margulies

wrote:


On Sat, Jan 31, 2015 at 10:55 AM, James Carman
 wrote:

Are there guidelines for these "usual considerations"?

For all the small stuff, the safe path is to get an ICLA from each
committer, and an email message positively stating an intent to

donate

the code.

Yes, this is the safest approach; but, may not be necessary for

changes

that do not represent significant IP.  For instance, our projects

accept

minor contributions through JIRA, without an ICLA.

There's a critical distinction here. Once you have released a product
under the Apache license, people can contribute new things to it under
the terms of the license. The license has very specific language: if
you take code from us, and then send us a contribution (email, JIRA,
github PR, carrier pigeon) that is a derivative of what you took, you
are granting the code to the Foundation.

That doesn't help with the initial import of a project from github or
bitbucket or Jupiter or Mars; none of those contributions met the
criteria in the license of sending a contribution back to the
Foundation, because the code wasn't here in the first place.

Just curious, what if the code was under AL but not at Apache?


The license is pretty clear about this:

*5. Submission of Contributions*. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work by

You

to the Licensor shall be under the terms and conditions of this License,
without any additional terms or conditions. Notwithstanding the above,
nothing herein shall supersede or modify the terms of any separate

license

agreement you may have executed with Licensor regarding such

Contributions.

So basically, anything you contribute back is assumed to be under the
Apache license, unless you (the author) say otherwise or there's some

other

license in play (The apache license doesn't supersede other licenses).

Of

course you should consult with legal counsel before making any
contributions though.  I think to Benson's point, The ASF requires that

any

incoming code was put in under that license agreement or there's a SGA
stating the prior license can be converted.

Note the phrase, "intentionally submitted for inclusion in the Work by
You _to the Licensor_". Who is the licensor for a body of work not at
Apache? The process has to start with a clear ownership of copyright
-- the licensor. The purpose of the SGA, I think, is to get a clear
answer to that question. You might be able to argue that a particular
github repo is made up of an initial work with a single owner, and
then contributions to it under the terms of the AL. In which case,
you'd just need an SGA from that original single owner. IANAL.



My understanding is that the Licensor is whomever claims to be 'it'. As
long ans the claimant produces documentation to substantiate the claim
that we can accept, we should be good. I don't see a need/requirement
for the Licensor to necessarily be a legal organization. That is if it's
not one single owner but a small group of contributors/owners, that
should be ok too.


My understanding is that the licensor must be able to own the copyright,
thus a legal entity (company or individual).

IMO, we should either take the acceptance of Tinkerpop as a Licensor to
legal@ or we just ask anyone who has contributed signifiant IP to sign an
ICLA with new copyright assignment.



IANAL, $0.02,
Hadrian





-
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: Software Grants for GitHub Projects...

[Hadrian Zbarcea]

On 02/01/2015 03:19 PM, Benson Margulies wrote:

On Sun, Feb 1, 2015 at 2:12 PM, John D. Ament  wrote:

On Sun Feb 01 2015 at 1:05:10 AM Alex Harui  wrote:



On 1/31/15, 9:09 AM, "Benson Margulies"  wrote:


On Sat, Jan 31, 2015 at 11:32 AM, Matt Franklin
 wrote:

On Sat Jan 31 2015 at 11:22:15 AM Benson Margulies

wrote:


On Sat, Jan 31, 2015 at 10:55 AM, James Carman
 wrote:

Are there guidelines for these "usual considerations"?

For all the small stuff, the safe path is to get an ICLA from each
committer, and an email message positively stating an intent to donate
the code.


Yes, this is the safest approach; but, may not be necessary for changes
that do not represent significant IP.  For instance, our projects accept
minor contributions through JIRA, without an ICLA.

There's a critical distinction here. Once you have released a product
under the Apache license, people can contribute new things to it under
the terms of the license. The license has very specific language: if
you take code from us, and then send us a contribution (email, JIRA,
github PR, carrier pigeon) that is a derivative of what you took, you
are granting the code to the Foundation.

That doesn't help with the initial import of a project from github or
bitbucket or Jupiter or Mars; none of those contributions met the
criteria in the license of sending a contribution back to the
Foundation, because the code wasn't here in the first place.

Just curious, what if the code was under AL but not at Apache?


The license is pretty clear about this:

*5. Submission of Contributions*. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work by You
to the Licensor shall be under the terms and conditions of this License,
without any additional terms or conditions. Notwithstanding the above,
nothing herein shall supersede or modify the terms of any separate license
agreement you may have executed with Licensor regarding such Contributions.

So basically, anything you contribute back is assumed to be under the
Apache license, unless you (the author) say otherwise or there's some other
license in play (The apache license doesn't supersede other licenses). Of
course you should consult with legal counsel before making any
contributions though.  I think to Benson's point, The ASF requires that any
incoming code was put in under that license agreement or there's a SGA
stating the prior license can be converted.

Note the phrase, "intentionally submitted for inclusion in the Work by
You _to the Licensor_". Who is the licensor for a body of work not at
Apache? The process has to start with a clear ownership of copyright
-- the licensor. The purpose of the SGA, I think, is to get a clear
answer to that question. You might be able to argue that a particular
github repo is made up of an initial work with a single owner, and
then contributions to it under the terms of the AL. In which case,
you'd just need an SGA from that original single owner. IANAL.


My understanding is that the Licensor is whomever claims to be 'it'. As 
long ans the claimant produces documentation to substantiate the claim 
that we can accept, we should be good. I don't see a need/requirement 
for the Licensor to necessarily be a legal organization. That is if it's 
not one single owner but a small group of contributors/owners, that 
should be ok too.


IANAL, $0.02,
Hadrian





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

Re: [VOTE] Recommend retirement for NPanday poddling

[Hadrian Zbarcea]

+1 to retire. The half full aspect is that it looks like people are 
doing something more useful with their time.


Hadrian


On 01/21/2015 05:19 PM, jan i wrote:

+1 Even though I do not like to see a podling end like this, but life
support has to be terminated at a point.

rgds
jan i

On Wednesday, January 21, 2015, Roman Shaposhnik  wrote:


This is a vote on recommending a retirement option
for the NPanday poddling.

It comes on the hills of the general consensus of
the NPanday community and its mentors that
retirement is the only viable path at this point:
 http://markmail.org/thread/litmh5wmwbclrk6n
 http://s.apache.org/Efn

NPanday entered incubator on 13th of August 2010:
http://incubator.apache.org/projects/npanday.html
Up until 2012 the poddling was doing reasonably well,
producing two releases and adding mentors and
committers. Starting from 2012 the community started
to dwindle and no further releases were produced.
Starting from 2014 the poddling really struggled to
regain vitality despite of numerous attempts to help
by Brett Porter and Konstantin Boudnik. The most
visible attempt was in July/August 2014 and resulted in
a spur of JIRA and ML activity, but couldn't be sustained
without direct involvement of Brett and Konstantin:
 https://wiki.apache.org/incubator/August2014
Starting from September the poddling was back to
the usual levels:
 http://mail-archives.apache.org/mod_mbox/incubator-npanday-dev/
 http://mail-archives.apache.org/mod_mbox/incubator-npanday-commits/
 http://mail-archives.apache.org/mod_mbox/incubator-npanday-users/
while missing Incubator reports:
 https://wiki.apache.org/incubator/November2014
 https://wiki.apache.org/incubator/December2014
and having absolutely 0 commits coming into the repository.
It now appears that that all of the PPMC has been disengaged
and the user community for the project is pretty much non existent.

IPMC has been monitoring the situation all throughout 2014:
http://markmail.org/message/3sbwfpedosyqzqhn
http://markmail.org/message/c2fbokolyujki3gl
http://markmail.org/thread/3ttavmqnq5s6pe74
http://markmail.org/message/bxelz5ati2hofe4y
and at this point it feels like the most production option would
be to recommend retirement of the poddling. Should
the VOTE pass, Konstantin and myself are volunteering
to take care of the poddling retirement mechanics.

Vote will run for at least 72 hours (to 1/26/14, noon PST).

[ ] +1 Recommend retiring NPanday poddling from the Incubator.
[ ] +/-0 Don't care, but...
[ ] -1 Don't recommend retiring NPanday poddling from the Incubator
because ...

Thanks,
Roman.

-
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

[VOTE][Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]

[Hadrian Zbarcea]

+1

From the conversation with Marko, he intended to submit this as a 
formal vote, but didn't use the regular voting template.


Voting will remain open until at least January 15, 2015 18:00 ET.

Cheers,
Hadrian


On 01/09/2015 11:35 AM, Marko Rodriguez wrote:

Hello everyone,

Over the last 2 weeks, TinkerPop's proposal has been worked on with 
support from:

* David Nalley (champion)
* Rich Bowen (mentor)
* Hadrian Zbarcea (mentor)
* Daniel Gruno (mentor)
* Marko Rodriguez (submitting on behalf of TinkerPop)

We feel it is now in prime shape from submission to vote. Enjoy!.
(URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal)



A. Abstract

TinkerPop <http://tinkerpop.com/> is a graph computing framework 
written in Java. A graph 
<http://en.wikipedia.org/wiki/Graph_%28mathematics%29> is a data 
structure composed of vertices and edges and is useful for modeling 
complex domains with arbitrary relations (edges, links, lines) between 
entities (vertices, objects, dots). TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> provides a core API that 
graph system vendors can implement. There are various types of graph 
systems including in-memory graph libraries, OLTP graph databases, and 
OLAP graph processors (see On Graph Computing 
<http://markorodriguez.com/2013/01/09/on-graph-computing/> for more 
information). Once the core interfaces are implemented, the underlying 
graph system can be queried using the graph traversal language Gremlin 
and processed withTinkerPop 
<https://wiki.apache.org/incubator/TinkerPop>-enabled algorithms. For 
many, TinkerPop <https://wiki.apache.org/incubator/TinkerPop> is seen 
as the JDBC 
<http://en.wikipedia.org/wiki/Java_Database_Connectivity> of the graph 
computing community.



B. Proposal

TinkerPop <https://wiki.apache.org/incubator/TinkerPop> was formed in 
2009 and is currently in the milestone series of 3.0.0. From the 
start, TinkerPop <https://wiki.apache.org/incubator/TinkerPop> has 
provided its software open source and free to use for which ever 
reason (commercial or otherwise). Initially the license was BSD, but 
as of TinkerPop3 <https://wiki.apache.org/incubator/TinkerPop3>, the 
license was changed to Apache2. The TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> team is composed of 
developers, evangelists, and representatives from graph system vendors 
(see TinkerPop Contributors 
<http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors> for 
more information). TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> has done its best to 
remain vendor agnostic and works closely with all vendors to ensure 
that the constructs within TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> are able to accommodate 
the requirements of the underlying graph system. To date, 12 
"TinkerPop <https://wiki.apache.org/incubator/TinkerPop> recognized" 
graph system vendors provide TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> implementations. We 
believe that by joining The Apache Software Foundation, our vendors, 
users, and contributors will feel more comfortable in terms of legal 
protected, in terms of wider-adoption, and in terms of project stability.



C. Background

TinkerPop <https://wiki.apache.org/incubator/TinkerPop> has had 
steady, active development since 2009 when it was founded. Over the 
years, the Gremlin query language within TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> has been adopted by 
various JVM languages and as such, there exists Gremlin-Groovy, 
Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript 
<https://wiki.apache.org/incubator/JavaScript>, and the like. In many 
ways, Gremlin is seen as a traversal style that can be readily adopted 
within the programming constructs of the developer's native language 
--- both on and off the JVM. TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> is not bound to the JVM 
in that developers wishing to interact with a TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop>-enabled graph system can 
leverage Gremlin Server which provides "over the wire" communication 
as well as the entry point for non-JVM language bindings. TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> is being used is 
production graph-based applications around the world and is only 
getting better with age.



D. Rationale

The graph computing space has grown over the years to encompass 
numerous graph database and graph processing systems. TinkerPop 
<https://wiki.apache.org/incubator/TinkerPop> was created as a 
unifying framework for interoperability, language standardization, and 
data model standardization. This framework makes it simple to "plug 
and play" the back-end graph implementation without affecting the 
developer's 

Re: [VOTE] [PROPOSAL] Accept OpenAz (Access Control Tools) into the Apache Incubator

[Hadrian Zbarcea]

+1.

I made some cosmetic changes to the list of committers and mentors. It 
should be clear now.


Hadrian


On 01/05/2015 02:04 PM, Hal Lockhart wrote:

I added a comma and the word "and" to the Mentors section. The Mentors are:

Emmanuel Lécharny, Colm O hEigeartaigh and Hadrian Zbarcea

Do you see any other formatting errors?

Hal


-Original Message-
From: Roman Shaposhnik [mailto:ro...@shaposhnik.org]
Sent: Monday, January 05, 2015 1:24 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] [PROPOSAL] Accept OpenAz (Access Control Tools)
into the Apache Incubator

Hi!

can you please fix the formatting issues? For example, I can't even
tell the exact list of mentors you're proposing.

Thanks,
Roman.

On Mon, Jan 5, 2015 at 10:15 AM, Hal Lockhart 
wrote:

I call a vote to accept OpenAz as a new Incubator project.

The proposal can be found here:
https://wiki.apache.org/incubator/OpenAZProposal

and is included below in this email.

Voting will remain open until at least January 20, 2015 23:00 ET.

Hal Lockhart

-

-

-

Abstract

OpenAz is a project to create tools and libraries to enable the

development of Attribute-based Access Control (ABAC) Systems in a
variety of languages. In general the work is at least consistent with
or actually conformant to the OASIS XACML Standard.

Proposal

Generally the work falls into two categories: ready to use tools

which implement standardized or well understood components of an ABAC
system and design proposals and proof of concept code relating to less
well understood or experimental aspects of the problem.

Much of the work to date has revolved around defining interfaces

enabling a PEP to request an access control decision from a PDP. The
XACML standard defines an abstract request format in xml and protocol
wire formats in xaml and json, but it does not specify programmatic
interfaces in any language. The standard says that the use of XML (or
JSON) is not required only the semantic equivalent.

The first Interface, AzAPI is modeled closely on the XACML defined

interface, expressed in Java. One of the goals was to support calls to
both a PDP local to the same process and a PDP in a remote server.
AzAPI includes the interface, reference code to handle things like the
many supported datatypes in XACML and glue code to mate it to the open
source Sun XACML implementation.

Because of the dependence on Sun XACML (which is XACML 2.0) the

interface was missing some XACML 3.0 features. More recently this was
corrected and WSo2 has mated it to their XACML 3.0 PDP. Some work was
done by the JPMC team to support calling a remote PDP. WSo2 is also
pursuing this capability.

A second, higher level interface, PEPAPI was also defined. PEPAPI is

more intended for application developers with little knowledge of
XACML. It allows Java objects which contain attribute information to be
passed in. Conversion methods, called mappers extract information from
the objects and present it in the format expected by XACML. Some
implementers have chosen to implement PEPAPI directly against their
PDP, omitting the use of AzAPI. Naomaru Itoi defined a C++ interface
which closely matches the Java one.

Examples of more speculative work include: proposals for registration

and dispatch of Obligation and Advice handlers, a scheme called AMF to
tell PIPs how to retrieve attributes and PIP code to implement it,
discussion of PoC code to demonstrate the use of XACML policies to
drive OAuth interations and a proposal to use XACML policies to express
OAuth scope.

AT&T has recently contributed their extensive XACML framework to the

project.

The AT&T framework represents the entire XACML 3.0 object set as a

collection of Java interfaces and standard implementations of those
interfaces. The AT&T PDP engine is built on top of this framework and
represents a complete implementation of a XACML 3.0 PDP, including all
of the multi-decision profiles. In addition, the framework also
contains an implementation of the OASIS XACML 3.0 RESTful API v1.0 and
XACML JSON Profile v1.0 WD 14. The PEP API includes annotation
functionality, allowing application developers to simply annotate a
Java class to provide attributes for a request. The annotation support
removes the need for application developers to learn much of the API.

The AT&T framework also includes interfaces and implementations to

standardize development of PIP engines that are used by the AT&T PDP
implementation, and can be used by other implementations built on top
of the AT&T framework. The framework also includes interfaces and
implementations for a PAP distributed cloud infrastructure of PDP nodes
that includes support for policy distribution and pip configurations.
This PAP infrastructure includes a web application administrative
console that contains a XACML 3.0 policy editor, attribute dictionary

Re: Request edit karma for wiki

[Hadrian Zbarcea]

Thanks Marvin, all set.
Hadrian

On 01/05/2015 08:24 PM, Marvin Humphrey wrote:

On Mon, Jan 5, 2015 at 3:32 PM, Hadrian Zbarcea  wrote:

For some reason HadrianZbarcea can no longer edit the wiki. Could somebody
please grant me access.

That wiki ID wasn't listed in ContributorsGroup, nor in
Administrators.  I've added it to ContributorsGroup.


Please verify the @a.o address for the account.

I'm not sure how to do that.  So long as you can log in, though, I
believe adding you to ContributorsGroup suffices and no further action
is necessary.  Even logged in, you would not have been able to edit
the wiki before; you should be able to now.

Cheers,

Marvin Humphrey

-
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: Podlings should be in charge of their mentors (was: Incubator report sign-off)

[Hadrian Zbarcea]

Makes sense :)
Hadrian

On 01/05/2015 06:41 PM, Benson Margulies wrote:

Back in 2013, I suggested asking the Champion to accept a very clear
level of reporting responsibility: to write a sentence or two _every
month_ or find someone else to do it. That's one person whom I wanted
to ask to sign up, for the duration of an incubation, to pay enough
attention to be able to report a basic heartbeat.

?


On Mon, Jan 5, 2015 at 3:57 PM, Upayavira  wrote:


On Mon, Jan 5, 2015, at 08:18 PM, jan i wrote:

On 5 January 2015 at 20:06, Alan D. Cabrera  wrote:


On Jan 5, 2015, at 10:26 AM, jan i  wrote:


On Monday, January 5, 2015, Alan D. Cabrera > wrote:


On Jan 5, 2015, at 9:21 AM, Roman Shaposhnik 

wrote:

The tracking part is easy, though. What's difficult is the part
that would require us to do something with poddlings put
on hold. Unless we come up with clear exit criteria for
this new state -- I don't think we're solving any real problems
here.

There’s no silver bullet here, if a podling cannot whip up a mentor it’s
because:
the podling is not popular and should probably be retired anyway, being
put on hold will provide impetus for the podling to seek out a new venue
there are not enough mentors
There is no way to magically solve the latter.


You mean popular within the pool of mentors (IPMC), the project can still
be popular on several other scales.

I’m not speaking of popularity of mentors; I regret that choice of words.
I am stating that active and healthy podlings seem to have no trouble
attracting active mentors.

The converse seems to be true.  Unhealthy podlings seem to attract mentors
who have signed up out of pity and subsequently go MIA.


I agree with the last part, I still have to see mentors volunteer for
small
active and healthy projects which might not be main road. Of course it
depends on how active and healthy is defined, but as an example my little
project Corinthia barely managed to get 2 mentors, while in the same time
span we got 3 committers.


Before anyone replies, I understand this is not a hard and fast rule but
an imperfect qualitative observation on my part.

Anyway, active and responsible mentors will eventually get to all podlings.


I might lack experience, but why do more active mentors guarantee that

the

podling will be a better TLP ?

I’m not sure who’s making that assertion.


Well its because I cannot see why a podling need more than 1 active
mentor
at all timeshaving multiple is fine, to cover each other, but it
should
not take more than 1 mentor to learn a podling, what it needs to
understand. The suggestion implicit says 2 mentors is the minimum needed
for at podling to become a successful TLP.



We try to solve the problem of mentors not being active but adding more
volume. I don't believe that is the right cure.

We’re not adding volume.  The volume is already there.  We’re just making
the state of affairs more explicit and transparent and adding culpability
for MIA mentors.


Do we have a rule today that a podling needs at least 2 active mentors
(if
we have that, then we would not have a problem with sign offs, or a lot
of
dead podlings), at least I have not seen itthat is what I mean by
adding volume.

If just 1 mentor is active and sign off the reports, then I do not see
the
problem.




I do agree with bernard that it is the podling that should ask for
helpbut the IPMC should solve it.,

Yes, it should help solve problems but if there are no mentors available
there are no mentors available.


Then the IPMC should not have accepted the podling in the first place!

It is simply not fair to make the life of a podling, depending on whether
or not we have mentors available (REMARK after accepting the proposal) !
If
the podling have a healthy community and are active, we cannot and should
not close it down, just because we have a mentor problem.

To me telling a podling it cannot grow its community nor make releases,
is
the same as closing it down.

Jan,

 From an idealistic perspective, you are completely right. Apache should,
once a project has been accepted, provide the support needed.

The reality is that, given the ASF's volunteer nature, that simply won't
always work.

I'd much rather we be clear with projects right up front, saying
something like:

"To join the Incubator, you need one or more mentors. To get to
graduation, you will need the support of those mentors. If mentors
become unavailable, you will need to seek replacements. Unless you have
already learned the ways of the ASF and are ready to graduate, you will
need to keep engaged with your mentors. If possible, engage in the wider
ASF, and develop connections with others who might be in a position to
assist with mentorship should one or all of your current mentors become
unable to fulfill the role. "

This is, actually, what happens, and I'd much rather we just said it
like that :-)

Upayavira

-
To unsubscribe, e-m

Request edit karma for wiki

[Hadrian Zbarcea]

For some reason HadrianZbarcea can no longer edit the wiki. Could 
somebody please grant me access. Please verify the @a.o address for the 
account.


Thanks,
Hadrian


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

Re: Reflections from the outgoing Chair

[Hadrian Zbarcea]

On 01/01/2015 08:32 PM, Benson Margulies wrote:

I'd like to raise a topic directly related to the succession. To
start, three cheers for Roman for all his hard work!



cheers += 3;




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

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Hadrian Zbarcea]

I followed the thread and tried to stay away, because there's a lot of 
potential for noise.


If the IPMC were to take a vote on the tinkerpop proposal today it would 
not pass. At the very least it's incomplete. Engaging in a conversation 
on this list to finalize it is, imho, not the most productive way of 
using everybody's time and it could get confusing. For that reason the 
best course of action is for you, the podling, to choose at least 3 
mentors who you think would provide good guidance and mentorship. You 
want to grow a strong community relatively fast, graduate from 
incubation and get more familiar with the Apache Way (I assume those who 
suggested to you to become an ASF project understand the benefits well). 
You already have a few experienced ASF members who offered their help as 
mentors. Talk to David, you have an excellent champion now, ask him to 
help you choose your mentors. Then pester your mentors and ask them what 
you want to know. Make sure you understand what you sign up for by 
moving the project governance to ASF. Next step, finalize the proposal 
and only then continue this discussion. It'll be more targeted and 
things will go faster.


My $0.02,
Hadrian



On 12/29/2014 03:30 PM, Rich Bowen wrote:



On 12/17/2014 02:09 PM, Marko Rodriguez wrote:

Hello,

My name is Marko A. Rodriguez and am a co-founder of TinkerPop
(http://tinkerpop.com). There has been positive pressure on us (both
internally and externally) to move TinkerPop to The Apache Foundation.
This email contains our proposal and I, on behalf of TinkerPop, thank
you for spending your time reading it.



After catching up on the conversation, and reading a little bit about 
your project and community, I would be honored if you would consider 
my offer to be a Mentor for your project.



--Rich




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

Re: Incubator report sign-off

[Hadrian Zbarcea]

+1

On 12/29/2014 09:15 AM, Rich Bowen wrote:
This is what happens when I write email like this and then go for two 
weeks off of work. Catching up ...


On 12/19/2014 01:10 PM, Roman Shaposhnik wrote:

First of all,*my*  expectation is that multiple mentors on the project
are more of redundancy or HA consideration. IOW, my expectation that
a project needs to have at least one active mentor at all times, but
it doesn't have to be the same person. Thus, I expect at least a signle
sign-off on the report and I don't mind if it ends up being a single one
too much.


You make a good point. I have been critical, of late, of projects that 
have N mentors, and only 1 or 2 mentors sign off on a report. However, 
I think you may have changed my perspective here, and I appreciate 
your insight.




Second biggest expectation that I have is that mentors are extension
of the IPMC, not part of the poddling. They are akin to professors or
faculty members -- they are not part of the student body. As such
we, as IPMC are accountable to make sure that mentors perform
their duties. My expectation is that it is as unfair to ask poddling to
actively pursue mentors who are missing in action as it would
be unfair to ask students to hire detectives to hunt down professors
who don't show up for class. What is fair, is to provide poddlings
with a semi-format feedback channel for IPMC to monitor things
like mentors MIA.


Agreed.

Presumably, projects with no signoff are sent back to report again, 
with a scolding note to the MIA mentors. As mentioned elsewhere, we 
don't want to punish the podling for underperforming mentors.






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

Re: Incubator report sign-off

[Hadrian Zbarcea]

On 12/29/2014 09:40 AM, Rich Bowen wrote:



On 12/22/2014 11:42 AM, Roman Shaposhnik wrote:

Hi!

before answering Ross' proposal, I'd like to remark that I was holding
off on replying to see whether viewpoints that we haven's seen before
would emerge. It seems that they didn't. It seems that we're still 
limited

by the following options wrt. resolving mentors AWOL issues:
 1. get rid of IPMC altogether and move to the pTLP model
 2. make this a poddling issue: if a poddling fails to hunt down ALL
 the mentors for a sign-off -- reject its report


-0.5 to punishing podlings for the failings of mentors. That would 
really suck.


Why not? They get "punished" anyway by the results. This is to me a fail 
fast mechanism. I think they should understand early on in the 
incubation projects what's expected of them and what they should expect 
from the ASF, among other things mentoring. Maybe they made a poor 
choice early on to chose mentors that don't fit their needs. They can 
then ping the mentors first and ask for more involvement, and if that 
doesn't happen, well, change mentors. Or maybe something changed in the 
personal life of the mentor that prevents them from providing effective 
mentorship (and say they didn't get to notify the podling). Same thing. 
In the end what matters are the results. If we emphasized that this is 
not about punishing or assigning blame, but about providing podlings 
with the support they need and we signed up to provide, it would be ok, 
I think.


My $0.02,
Hadrian

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

Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Hadrian Zbarcea]

+1 (binding)


On 12/19/2014 12:29 AM, Roman Shaposhnik wrote:

Following the discussion earlier:
 http://s.apache.org/kTp

I would like to call a VOTE for accepting
Zeppelin as a new Incubator project.

The proposal is available at:
 https://wiki.apache.org/incubator/ZeppelinProposal
and is also attached to the end of this email.

Vote is open until at least Sunday, 21th December 2014,
23:59:00 PST

[ ] +1 Accept Zeppelin into the Incubator
[ ] ±0 Indifferent to the acceptance of Zeppelin
[ ] -1 Do not accept Zeppelin because ...

Thanks,
Roman.

== Abstract ==
Zeppelin is a collaborative data analytics and visualization tool for
distributed, general-purpose data processing systems such as Apache
Spark, Apache Flink, etc.

== Proposal ==
Zeppelin is a modern web-based tool for the data scientists to
collaborate over large-scale data exploration and visualization
projects. It is a notebook style interpreter that enable collaborative
analysis sessions sharing between users. Zeppelin is independent of
the execution framework itself. Current version runs on top of Apache
Spark but it has pluggable interpreter APIs to support other data
processing systems. More execution frameworks could be added at a
later date i.e Apache Flink, Crunch as well as SQL-like backends such
as Hive, Tajo, MRQL.

We have a strong preference for the project to be called Zeppelin. In
case that may not be feasible, alternative names could be: “Mir”,
“Yuga” or “Sora”.

== Background ==
Large scale data analysis workflow includes multiple steps like data
acquisition, pre-processing, visualization, etc and may include
inter-operation of multiple different tools and technologies. With the
widespread of the open source general-purpose data processing systems
like Spark there is a lack of open source, modern user-friendly tools
that combine strengths of interpreted language for data analysis with
new in-browser visualization libraries and collaborative capabilities.

Zeppelin initially started as a GUI tool for diverse set of
SQL-over-Hadoop systems like Hive, Presto, Shark, etc. It was open
source since its inception in Sep 2013. Later, it became clear that
there was a need for a greater web-based tool for data scientists to
collaborate on data exploration over the large-scale projects, not
limited to SQL. So Zeppelin integrated full support of Apache Spark
while adding a collaborative environment with the ability to run and
share interpreter sessions in-browser

== Rationale ==
There are no open source alternatives for a collaborative
notebook-based interpreter with support of multiple distributed data
processing systems.

As a number of companies adopting and contributing back to Zeppelin is
growing, we think that having a long-term home at Apache foundation
would be a great fit for the project ensuring that processes and
procedures are in place to keep project and community “healthy” and
free of any commercial, political or legal faults.

== Initial Goals ==
The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. This includes moving
all infrastructure that we currently maintain, such as: a website, a
mailing list, an issues tracker and a Jenkins CI, as mentioned in
“Required Resources” section of current proposal.
Once this is accomplished, we plan for incremental development and
releases that follow the Apache guidelines.
To increase adoption the major goal for the project would be to
provide integration with as much projects from Apache data ecosystem
as possible, including new interpreters for Apache Hive, Apache Drill
and adding Zeppelin distribution to Apache Bigtop.
On the community building side the main goal is to attract a diverse
set of contributors by promoting Zeppelin to wide variety of
engineers, starting a Zeppelin user groups around the globe and by
engaging with other existing Apache projects communities online.


== Current Status ==
Currently, Zeppelin has 4 released versions and is used in production
at a number of companies across the globe mentioned in Affiliation
section. Current implementation status is pre-release with public API
not being finalized yet. Current main and default backend processing
engine is Apache Spark with consistent support of SparkSQL.
Zeppelin is distributed as a binary package which includes an embedded
webserver, application itself, a set of libraries and startup/shutdown
scripts. No platform-specific installation packages are provided yet
but it is something we are looking to provide as part of Apache Bigtop
integration.
Project codebase is currently hosted at github.com, which will form
the basis of the Apache git repository.

=== Meritocracy ===
Zeppelin is an open source project that already leverages meritocracy
principles.  It was started by a handfull of people and now it has
multiple contributors, although as the number of contribution grows we
want to build a diverse developer and user community that is govern

Re: [DISCUSS] [PROPOSAL] Zeppelin for Apache Incubator

[Hadrian Zbarcea]

+1

Hadrian


On 12/18/2014 11:54 PM, Konstantin Boudnik wrote:

And again - big +1: I think the whole data stack will benefit from it.

On Sat, Dec 13, 2014 at 05:18PM, Roman Shaposhnik wrote:

Hi,

I would like to propose Zeppelin as an Apache Incubator
project:
 https://wiki.apache.org/incubator/ZeppelinProposal

Please let me know what do you think and feel free to
volunteer as additional mentors for the project.

The easiest way to get to see what this project looks like
in action would be this demo:
 https://www.youtube.com/watch?v=_PQbVH_aO5E

Thanks,
Roman.

== Abstract ==
Zeppelin is a collaborative data analytics and visualization tool for
distributed, general-purpose data processing systems such as Apache
Spark, Apache Flink, etc.

== Proposal ==
Zeppelin is a modern web-based tool for the data scientists to
collaborate over large-scale data exploration and visualization
projects. It is a notebook style interpreter that enable collaborative
analysis sessions sharing between users. Zeppelin is independent of
the execution framework itself. Current version runs on top of Apache
Spark but it has pluggable interpreter APIs to support other data
processing systems. More execution frameworks could be added at a
later date i.e Apache Flink, Crunch as well as SQL-like backends such
as Hive, Tajo, MRQL.

We have a strong preference for the project to be called Zeppelin. In
case that may not be feasible, alternative names could be: “Mir”,
“Yuga” or “Sora”.

== Background ==
Large scale data analysis workflow includes multiple steps like data
acquisition, pre-processing, visualization, etc and may include
inter-operation of multiple different tools and technologies. With the
widespread of the open source general-purpose data processing systems
like Spark there is a lack of open source, modern user-friendly tools
that combine strengths of interpreted language for data analysis with
new in-browser visualization libraries and collaborative capabilities.

Zeppelin initially started as a GUI tool for diverse set of
SQL-over-Hadoop systems like Hive, Presto, Shark, etc. It was open
source since its inception in Sep 2013. Later, it became clear that
there was a need for a greater web-based tool for data scientists to
collaborate on data exploration over the large-scale projects, not
limited to SQL. So Zeppelin integrated full support of Apache Spark
while adding a collaborative environment with the ability to run and
share interpreter sessions in-browser

== Rationale ==
There are no open source alternatives for a collaborative
notebook-based interpreter with support of multiple distributed data
processing systems.

As a number of companies adopting and contributing back to Zeppelin is
growing, we think that having a long-term home at Apache foundation
would be a great fit for the project ensuring that processes and
procedures are in place to keep project and community “healthy” and
free of any commercial, political or legal faults.

== Initial Goals ==
The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. This includes moving
all infrastructure that we currently maintain, such as: a website, a
mailing list, an issues tracker and a Jenkins CI, as mentioned in
“Required Resources” section of current proposal.
Once this is accomplished, we plan for incremental development and
releases that follow the Apache guidelines.
To increase adoption the major goal for the project would be to
provide integration with as much projects from Apache data ecosystem
as possible, including new interpreters for Apache Hive, Apache Drill
and adding Zeppelin distribution to Apache Bigtop.
On the community building side the main goal is to attract a diverse
set of contributors by promoting Zeppelin to wide variety of
engineers, starting a Zeppelin user groups around the globe and by
engaging with other existing Apache projects communities online.


== Current Status ==
Currently, Zeppelin has 4 released versions and is used in production
at a number of companies across the globe mentioned in Affiliation
section. Current implementation status is pre-release with public API
not being finalized yet. Current main and default backend processing
engine is Apache Spark with consistent support of SparkSQL.
Zeppelin is distributed as a binary package which includes an embedded
webserver, application itself, a set of libraries and startup/shutdown
scripts. No platform-specific installation packages are provided yet
but it is something we are looking to provide as part of Apache Bigtop
integration.
Project codebase is currently hosted at github.com, which will form
the basis of the Apache git repository.

=== Meritocracy ===
Zeppelin is an open source project that already leverages meritocracy
principles.  It was started by a handfull of people and now it has
multiple contributors, although as the number of contribution grows we
want to build a diverse developer and user commu

Re: [VOTE] Release Apache Brooklyn 0.7.0-M2-incubating [rc4]

[Hadrian Zbarcea]

+1 (binding).
Too late for the PPMC vote, sorry.

Findings:
1. Keys verify ok.
2. Notice, license files, copyright statements ok (see #7)
3. Build from source distro without running tests ok (fixed from 
previous rc)

4. Build from source distro and running tests ok (fixed from previous rc)
5. Sources are in the "brooklyn" package, need to move to 
"org.apache.brooklyn" (known).

6. Does work with other tests/environments I use.

7. (minor) the LICENSE file in root dir of the distro is different than 
all others. The 3 title lines are spaces and left aligned. Kinda weird 
and ugly, maybe something to take care of in the next release.


Great job,
Hadrian


On 12/18/2014 11:42 AM, Richard Downer wrote:

This is to call for a vote for the source release of Apache Brooklyn
0.7.0-M2-incubating.


Call for votes on d...@brooklyn.incubator.apache.org:
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201412.mbox/%3CCABQFKi1P58JJhsgCzXGeW6_fpwHt1imttHENtYPERAgM0nWTGg%40mail.gmail.com%3E

Result of vote on d...@brooklyn.incubator.apache.org:
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201412.mbox/%3CCABQFKi0hrAOkQh1wtke-nQsxxNyVXKqnJXVvsNU5EchAHcxhNw%40mail.gmail.com%3E

One of the votes on d...@brooklyn.incubator.apache.org is from IPMC
member Chip Childers, and I understand that his vote will carry
forward to this IPMC vote.

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/brooklyn/apache-brooklyn-0.7.0-M2-incubating-rc4

The Git commit ID is 94b42b85e80efd817f951326238864e37edc2cb0
https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git;a=commit;h=94b42b85e80efd817f951326238864e37edc2cb0

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/richard.asc
https://people.apache.org/keys/committer/chipchilders.asc

Checksums of apache-brooklyn-0.7.0-M2-incubating-rc4.tar.gz:
MD5: a30cbc287f4d72b983e9c08c2074690f
SHA1: f573c49e36d806d1fbc8349b03ea5ffd1ec01751
SHA256: e3c2a844c5816db2c0ac4ae6c6d9c43a64dc51c98546589f14413baf98fad2cb

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/brooklyn/KEYS

Please vote on releasing this package as Apache Brooklyn 0.7.0-M2-incubating.

The vote will be open for 72 hours.
[ ] +1 Release this package as Apache Brooklyn 0.7.0-M2-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...


Thanks,
Richard Downer

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




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

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Hadrian Zbarcea]

A tad longer answer is that the immutable rules are meant to protect the 
Apache Way, because we believe that healthy communities produce health 
code. The ASF is a steward of communities that are themselves stewards 
of code. The incubation process is meant to benefit the project, allow 
new committers to get familiar with the social and legal 
responsibilities associated with public releases, code governance, IP, 
licensing, etc. Your case is slightly different because you're 
experienced already with most of these aspects.


The champion and mentors are there to help you through the process. They 
are volunteers who work to become eventually useless, at which point the 
project graduates out of the incubator.


I hope this (and the links below) help(s),
Hadrian

[1] http://incubator.apache.org/learn/theapacheway.html
[2] http://theapacheway.com/
[3] http://www.apache.org/foundation/how-it-works.html


On 12/18/2014 11:48 AM, Ross Gardler (MS OPEN TECH) wrote:

Marko,

I note that you currently do not have a champion and that you have listed IBM 
as the sponsor, with two individuals names who (to the best of my knowledge) 
are not ASF committers. I suggest these are the first things you need to 
address in your proposal. Find a champion who can help you understand what the 
Apache Way is and why IBM is not a sponsor (Sam is certainly an excellent 
candidate to help you with that if he is willing).

To your specific points below, since Sam has already responded to your points, 
I'll keep my response short. Moving your primary project resources to the ASF 
is not a negotiable item. There are many reasons for this. Your champion is 
responsible for ensuring you understand the reasoning behind this.

When a project comes to the ASF it comes for the Apache Way. That means projects that 
choose to come here need to adopt the Apache Way in its entirety, not "just 
enough" to be an Apache project.

That being said, there are very few immutable rules in the Apache Way, much of 
it is social structure an practices. But there are a few things that are 
designed to protect that social structure, this a non-negotiable (at least 
outside of the ASF membership who, over time, tweak the rules).

Ross

-Original Message-
From: Marko Rodriguez [mailto:okramma...@gmail.com]
Sent: Thursday, December 18, 2014 8:16 AM
To: general@incubator.apache.org; jfarr...@apache.org
Cc: Sam Ruby
Subject: Re: [Proposal] TinkerPop: A Graph Computing Framework

Hello Jake,

When talking with Sam Ruby (cc:d) we voiced our concerns about moving all of 
our infrastructure over to The Apache Foundation. In particular, our GitHub 
presence and our public user-mailing list (i.e. tech support mailing list). I 
have articulated our concerns in the freshly updated proposal.

https://wiki.apache.org/incubator/TinkerPopProposal
Please see "W. Mailing Lists", "Y. Git Repository", and "X. 
Subversion Directory".

Sam Ruby had stated that using GitHub for source control is an accepted practice now. We can (though would 
prefer not to) move our issue tracking to JIRA. Again, we have all been using GitHub issue tracking for 5 
years and are comfortable with its interface. Likewise, we can (though would prefer not to), move our user 
mailing list to Apache's mail list system. If a distinction is made between "user mailing list" 
(tech support) and "contributor mailing list" (governance), we can (and would prefer) to move over 
our "TinkerPop Contributors" mailing list to ASF as this is where all the 
legal/political/governance discussion occur and should be under the purview of ASF.

Thoughts?,
Marko.

http://markorodriguez.com

On Dec 17, 2014, at 7:42 PM, Jake Farrell  wrote:


Hey Marko
Thank you for posting the proposal to the wiki. The proposal has the
requested infra for issues, wiki, mailing lists, and scm all still at
github. These sections will have to be edited to bring everything over
to ASF hardware. Please take a look at other proposals listed for an
idea and if you have any questions please let us know

Thanks
-Jake

On Wed, Dec 17, 2014 at 7:56 PM, Marko Rodriguez

wrote:

Hello everyone,

I have put the proposal on the wiki page.

https://wiki.apache.org/incubator/TinkerPopProposal

As requested by Roman, I updated the Affiliations section. Note that
I would love to tweak more but there is a 1 minute turn around time
when I hit 'preview' or 'save changes' on the wiki. It started
driving me mad so I stopped.

Please advise on desired edits and I will do so. Moreover, I will
make things much cleaner once the wiki interface speeds up (hopefully
its just a 'burp' in the software right now).

Finally, I will review the individuals who noted they would like to
"champion" or "mentor" TinkerPop. I will read more about them, what
these roles are, and provide thoughts to this thread once I fully
grasp the situation.

Thank you again,
Marko.

http://markorodriguez.com

On Dec 17, 2014, at 5:25 PM, Henry Saputra 

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Hadrian Zbarcea]

Hi Marko,

Take a look at the incubator guide [1] for submitting proposals, in 
particular the section explaining the role of the champion [2] and 
mentors [3]. You already have 2 ASF members who offered to help as 
champions and more than 3 three who offered to mentor. If you have 
somebody in particular in mind who didn't offer yet, you could contact 
that person directly and ask. It may not be a bad idea to involve the 
existing community in the selection.


Then you'd need to post on the wiki and incrementally refine the 
proposal to include the feedback you'll get on this thread. Roman 
already mentioned the affiliations section. The champion and mentors 
will help. The next step will be to submit the proposal for a formal 
vote and then... the fun begins, uhm, continues.


Cheers,
Hadrian

[1] http://incubator.apache.org/guides/proposal.html
[2] http://incubator.apache.org/guides/proposal.html#template-champion
[3] http://incubator.apache.org/guides/proposal.html#template-mentors


On 12/17/2014 06:28 PM, Marko Rodriguez wrote:

Hello Roman,

First off, thank you everyone for your positive reception. I have been sending 
over your comments to our contributors mailing list to give everyone a stoke.


As one of Giraph devs I really like the idea of having TinkerPop in ASF.

Excellent. Note that we have Gremlin working over Giraph in TinkerPop3 -- part 
of Hadoop-Gremlin.
http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#_olap_hadoop_gremlin
Also, note that Avery Ching is a TinkerPop-Contributor … so its a nice happy 
family.


A few questions/points:
   * could you please post the proposal to:
 https://wiki.apache.org/incubator/TinkerPop Proposal
  (let me know your wiki ID if you don't have enough karma)

I just created an account and my ID is MarkoRodriguez. Can you give me edit 
permissions please?
https://wiki.apache.org/incubator/TinkerPopProposal?action=edit


   * do you guys have a champion and initial set of mentors in mind?

This is what I don't understand. I was on a call with Sam Ruby (cc:d) when the final decision to 
submit the proposal to The Apache Foundation was made. I believe he said something along the lines 
of: "If no one wants to be a champion for you, I can do it." (or perhaps he said 
"mentor").


   * could you please fill out affiliations section?

I can do that when I put the proposal on the wiki. Apologies, I misunderstood 
what that section was asking for. I understand now.

Thank you everyone for your time,
Marko.

http://markorodriguez.com




Thanks,
Roman.

On Wed, Dec 17, 2014 at 11:09 AM, Marko Rodriguez  wrote:

Hello,

My name is Marko A. Rodriguez and am a co-founder of TinkerPop
(http://tinkerpop.com). There has been positive pressure on us (both
internally and externally) to move TinkerPop to The Apache Foundation. This
email contains our proposal and I, on behalf of TinkerPop, thank you for
spending your time reading it.

Take care,
Marko.

http://markorodriguez.com





A. Abstract

TinkerPop is a graph computing framework written in Java --
http://tinkerpop.com. TinkerPop started in 2009 and is currently in the
milestone series of 3.0.0.  Graph system vendors such as in-memory graph
libraries, OLTP graph databases, and OLAP graph processors can provide a
TinkerPop implementation
(http://markorodriguez.com/2013/01/09/on-graph-computing/). Once the core
TinkerPop interfaces are implemented, the underlying graph system can be
queried using the graph traversal language Gremlin. TinkerPop was designed
to be used at any scale and as such, can be leveraged by both single-server
and multi-machine compute clusters. For many, TinkerPop is seen as the JDBC
of the graph computing community
(http://en.wikipedia.org/wiki/Java_Database_Connectivity).

B. Proposal

Since its inception in 2009, TinkerPop has been open source, free to use.
Initially the license was BSD, but as of TinkerPop3, the license is Apache2.
The TinkerPop team is composed of developers as well as representatives from
numerous graph system vendors
(http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors).
TinkerPop has done its best to remain vendor agnostic and works closely with
vendors to ensure that the constructs within TinkerPop are able to
accommodate the requirements of the underlying graph system. To date, over
12 graph system vendors provide TinkerPop implementations. We believe that
by joining The Apache Foundation, our vendors, users, and contributors will
feel more comfortable in terms of legal protected, in terms of
wider-adoption, and in terms of project stability.

C. Background

TinkerPop was founded in 2009 and has had steady, active development since.
Over the years, the Gremlin query language within TinkerPop has been adopted
by various JVM languages and as such, there exists Gremlin-Groovy,
Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript, and the like. In many
ways, Gremlin is seen as a traversal language st

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Hadrian Zbarcea]

Not surprisingly, there is already some positive feedback. If you don't 
already have a champion in mind, I'd be happy to help in that role as well.


Hadrian


On 12/17/2014 03:26 PM, Hadrian Zbarcea wrote:

+1

Hi Marko,

Thanks for your proposal. I followed and used tinkerpop for a long 
time and it is indeed a brilliant open source project. I think I 
understand the motivation to move the project governance to the ASF 
and it makes sense. I volunteer to be a mentor, should the project be 
accepted (which I am confident of, knowing the merits of your 
project). You'll need at least 3 mentors and a champion as well (do 
you have any ASF member in mind for that role?). The proposal needs a 
tiny bit of work as well.


Good luck,
Hadrian


On 12/17/2014 02:09 PM, Marko Rodriguez wrote:

Hello,

My name is Marko A. Rodriguez and am a co-founder of TinkerPop 
(http://tinkerpop.com). There has been positive pressure on us (both 
internally and externally) to move TinkerPop to The Apache 
Foundation. This email contains our proposal and I, on behalf of 
TinkerPop, thank you for spending your time reading it.


Take care,
Marko.

http://markorodriguez.com





*A. Abstract*

TinkerPop is a graph computing framework written in Java -- 
http://tinkerpop.com <http://tinkerpop.com/>. TinkerPop started in 
2009 and is currently in the milestone series of 3.0.0.  Graph system 
vendors such as in-memory graph libraries, OLTP graph databases, and 
OLAP graph processors can provide a TinkerPop implementation 
(http://markorodriguez.com/2013/01/09/on-graph-computing/). Once the 
core TinkerPop interfaces are implemented, the underlying graph 
system can be queried using the graph traversal language Gremlin. 
TinkerPop was designed to be used at any scale and as such, can be 
leveraged by both single-server and multi-machine compute clusters. 
For many, TinkerPop is seen as the JDBC of the graph computing 
community (http://en.wikipedia.org/wiki/Java_Database_Connectivity).


*B. Proposal*

Since its inception in 2009, TinkerPop has been open source, free to 
use. Initially the license was BSD, but as of TinkerPop3, the license 
is Apache2. The TinkerPop team is composed of developers as well as 
representatives from numerous graph system vendors 
(http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors). 
TinkerPop has done its best to remain vendor agnostic and works 
closely with vendors to ensure that the constructs within TinkerPop 
are able to accommodate the requirements of the underlying graph 
system. To date, over 12 graph system vendors provide TinkerPop 
implementations. We believe that by joining The Apache Foundation, 
our vendors, users, and contributors will feel more comfortable in 
terms of legal protected, in terms of wider-adoption, and in terms of 
project stability.


*C. Background*

TinkerPop was founded in 2009 and has had steady, active development 
since. Over the years, the Gremlin query language within TinkerPop 
has been adopted by various JVM languages and as such, there exists 
Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript, 
and the like. In many ways, Gremlin is seen as a traversal language 
style that can be readily adopted by developers --- on and off the 
JVM. TinkerPop is not bound to the JVM in that developers wishing to 
interact with a TinkerPop-enabled graph system can leverage Gremlin 
Server which provides "over the wire" communication as well as the 
entry point for non-JVM language bindings. TinkerPop is being used is 
production graph-based applications around the world and is only 
getting better with age.


*D. Rationale*

The graph computing space has grown over the years to encompass 
numerous graph database and graph processing systems. TinkerPop was 
created as a unifying framework for interoperability, language 
standardization, and data model standardization.  This framework 
makes it simple to "plug and play" the back-end graph implementation 
without affecting the developer's code. This is analogous to the way 
in which JDBC allows users to swap relational databases while keeping 
the same programming interface. TinkerPop also brings together OLTP 
systems (graph databases) and OLAP systems (graph processors) by 
providing a single query language, Gremlin, for executing graph 
algorithms transparently over either type of system.  Finally, 
TinkerPop unifies single-machine systems and distributed systems, 
presenting an identical user experience within the boundaries of the 
computational space and time constraints of the underlying graph system.


*E. Initial Goals*

The goal of this proposal is to migrate TinkerPop to The Apache 
Foundation to 1.) get more exposure to the project and 2.) legally 
protect the developers and contributors of TinkerPop.


*F. Current Status*

TinkerPop is planning to release TinkerPop 3.0.0.GA early 2015 -- 
January o

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Hadrian Zbarcea]

+1

Hi Marko,

Thanks for your proposal. I followed and used tinkerpop for a long time 
and it is indeed a brilliant open source project. I think I understand 
the motivation to move the project governance to the ASF and it makes 
sense. I volunteer to be a mentor, should the project be accepted (which 
I am confident of, knowing the merits of your project). You'll need at 
least 3 mentors and a champion as well (do you have any ASF member in 
mind for that role?). The proposal needs a tiny bit of work as well.


Good luck,
Hadrian


On 12/17/2014 02:09 PM, Marko Rodriguez wrote:

Hello,

My name is Marko A. Rodriguez and am a co-founder of TinkerPop 
(http://tinkerpop.com). There has been positive pressure on us (both 
internally and externally) to move TinkerPop to The Apache Foundation. 
This email contains our proposal and I, on behalf of TinkerPop, thank 
you for spending your time reading it.


Take care,
Marko.

http://markorodriguez.com





*A. Abstract*

TinkerPop is a graph computing framework written in Java -- 
http://tinkerpop.com . TinkerPop started in 
2009 and is currently in the milestone series of 3.0.0.  Graph system 
vendors such as in-memory graph libraries, OLTP graph databases, and 
OLAP graph processors can provide a TinkerPop implementation 
(http://markorodriguez.com/2013/01/09/on-graph-computing/). Once the 
core TinkerPop interfaces are implemented, the underlying graph system 
can be queried using the graph traversal language Gremlin. TinkerPop 
was designed to be used at any scale and as such, can be leveraged by 
both single-server and multi-machine compute clusters. For many, 
TinkerPop is seen as the JDBC of the graph computing community 
(http://en.wikipedia.org/wiki/Java_Database_Connectivity).


*B. Proposal*

Since its inception in 2009, TinkerPop has been open source, free to 
use. Initially the license was BSD, but as of TinkerPop3, the license 
is Apache2. The TinkerPop team is composed of developers as well as 
representatives from numerous graph system vendors 
(http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors). TinkerPop 
has done its best to remain vendor agnostic and works closely with 
vendors to ensure that the constructs within TinkerPop are able to 
accommodate the requirements of the underlying graph system. To date, 
over 12 graph system vendors provide TinkerPop implementations. We 
believe that by joining The Apache Foundation, our vendors, users, and 
contributors will feel more comfortable in terms of legal protected, 
in terms of wider-adoption, and in terms of project stability.


*C. Background*

TinkerPop was founded in 2009 and has had steady, active development 
since. Over the years, the Gremlin query language within TinkerPop has 
been adopted by various JVM languages and as such, there exists 
Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript, 
and the like. In many ways, Gremlin is seen as a traversal language 
style that can be readily adopted by developers --- on and off the 
JVM. TinkerPop is not bound to the JVM in that developers wishing to 
interact with a TinkerPop-enabled graph system can leverage Gremlin 
Server which provides "over the wire" communication as well as the 
entry point for non-JVM language bindings. TinkerPop is being used is 
production graph-based applications around the world and is only 
getting better with age.


*D. Rationale*

The graph computing space has grown over the years to encompass 
numerous graph database and graph processing systems. TinkerPop was 
created as a unifying framework for interoperability, language 
standardization, and data model standardization.  This framework makes 
it simple to "plug and play" the back-end graph implementation without 
affecting the developer's code. This is analogous to the way in which 
JDBC allows users to swap relational databases while keeping the same 
programming interface. TinkerPop also brings together OLTP systems 
(graph databases) and OLAP systems (graph processors) by providing a 
single query language, Gremlin, for executing graph algorithms 
transparently over either type of system.  Finally, TinkerPop unifies 
single-machine systems and distributed systems, presenting an 
identical user experience within the boundaries of the computational 
space and time constraints of the underlying graph system.


*E. Initial Goals*

The goal of this proposal is to migrate TinkerPop to The Apache 
Foundation to 1.) get more exposure to the project and 2.) legally 
protect the developers and contributors of TinkerPop.


*F. Current Status*

TinkerPop is planning to release TinkerPop 3.0.0.GA early 2015 -- 
January or February. We would like to release TinkerPop 3.0.0.GA under 
The Apache Foundation.


*G. Meritocracy*

Anyone is welcome to join TinkerPop as a contributor. If an individual 
provides successful code updates, documentation updates, etc. then 
they are asked 

Re: Need an additional Mentor for the OpenAz Project

[Hadrian Zbarcea]

I volunteer to help as a mentor.

Cheers,
Hadrian
hadrian@a.o

On 12/15/2014 01:22 PM, Hal Lockhart wrote:

The OpenAz Project currently has two mentors, but we need at least one more. Is 
there anyone who would be willing to join us?

The proposal is here:

https://wiki.apache.org/incubator/OpenAZProposal

Thanks in advance,

Hal

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




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

Re: [PROPOSAL] NiFi for Incubation

[Hadrian Zbarcea]

Sounds exciting. I have a couple of questions:

1. Is there a code grant? I assume so, the proposal states that the 
project is active since 2006. What I could find [1] doesn't seem to be it.

2. What is the overlap with Apache Camel (if any)?

Cheers,
Hadrian


[1] https://github.com/Nifi


On 11/19/2014 09:02 PM, Joe Witt wrote:

Hello,


I would like to propose NiFi as an Apache Incubator Project.

In addition to the copy provided below the Wiki version of the
proposal can be found here:
http://wiki.apache.org/incubator/NiFiProposal

Thanks

Joe


= NiFi Proposal =

== Abstract ==
NiFi is a dataflow system based on the concepts of flow-based programming.

== Proposal ==
NiFi supports powerful and scalable directed graphs of data routing,
transformation, and system mediation logic.  Some of the high-level
capabilities and objectives of NiFi include:
   * Web-based user interface for seamless experience between design,
control, feedback, and monitoring of data flows
   * Highly configurable along several dimensions of quality of service
such as loss tolerant versus guaranteed delivery, low latency versus
high throughput, and priority based queuing
   * Fine-grained data provenance for all data received, forked,
joined, cloned, modified, sent, and ultimately dropped as data reaches
its configured end-state
   * Component-based extension model along well defined interfaces
enabling rapid development and effective testing

== Background ==
Reliable and effective dataflow between systems can be difficult
whether you're running scripts on a laptop or have a massive
distributed computing system operated by numerous teams and
organizations.  As the volume and rate of data grows and as the number
of systems, protocols, and formats increase and evolve so too does the
complexity and need for greater insight and agility.  These are the
dataflow challenges that NiFi was built to tackle.

NiFi is designed in a manner consistent with the core concepts
described in flow-based programming as originally documented by J.
Paul Morrison in the 1970s.  This model lends itself well to visual
diagramming, concurrency, componentization, testing, and reuse.  In
addition to staying close to the fundamentals of flow-based
programming, NiFi provides integration system specific features such
as: guaranteed delivery; back pressure; ability to gracefully handle
backlogs and data surges; and an operator interface that enables
on-the-fly data flow generation, modification, and observation.

== Rationale ==
NiFi provides a reliable, scalable, manageable and accountable
platform for developers and technical staff to create and evolve
powerful data flows.  Such a system is useful in many contexts
including large-scale enterprise integration, interaction with cloud
services and frameworks, business to business, intra-departmental, and
inter-departmental flows.  NiFi fits well within the Apache Software
Foundation (ASF) family as it depends on numerous ASF projects and
integrates with several others.  We also anticipate developing
extensions for several other ASF projects such as Cassandra, Kafka,
and Storm in the near future.

== Initial Goals ==
   * Ensure all dependencies are compliant with Apache License version
2.0 and all that all code and documentation artifacts have the correct
Apache licensing markings and notice.
   * Establish a formal release process and schedule, allowing for
dependable release cycles in a manner consistent with the Apache
development process.
   * Determine and establish a mechanism, possibly including a
sub-project construct, that allows for extensions to the core
application to occur at a pace that differs from the core application
itself.

== Current Status ==
=== Meritocracy ===
An integration platform is only as good as its ability to integrate
systems in a reliable, timely, and repeatable manner.  The same can be
said of its ability to attract talent and a variety of perspectives as
integration systems by their nature are always evolving.  We will
actively seek help and encourage promotion of influence in the project
through meritocracy.

=== Community ===
Over the past several years, NiFi has developed a strong community of
both developers and operators within the U.S. government.  We look
forward to helping grow this to a broader base of industries.

=== Core Developers ===
The initial core developers are employed by the National Security
Agency and defense contractors.  We will work to grow the community
among a more diverse set of developers and industries.

=== Alignment ===
 From its inception, NiFi was developed with an open source philosophy
in mind and with the hopes of eventually being truly open sourced.
The Apache way is consistent with the approach we have taken to date.
The ASF clearly provides a mature and effective environment for
successful development as is evident across the spectrum of well-known
projects.  Further, NiFi depends on numerous ASF libraries and
projects including; Active

Re: [VOTE] Apache Sirona as an incubated project

[Hadrian Zbarcea]

+1 (binding)
Hadrian

On 10/08/2013 09:29 PM, Olivier Lamy wrote:

Hi,
Since discussion about the Sirona seems done, I'd like to call a vote
for Sirona to become an incubated project.

The proposal is pasted below, and also available at:
https://wiki.apache.org/incubator/SironaProposal

Let's keep this vote open for three business days.

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


## page was renamed from MonitoringProposal
= Apache Sirona =

== Abstract ==

Apache Sirona aims to provide a simple but extensible monitoring
solution for Java applications.

Apache Sirona provides two kind of components :

   * Apache Sirona Core to provide a base framework for
monitoring/recording a Java application.

   * Default based plugins

   * Apache Sirona base reporting web application (provide a basic
reporting on recorded figures).

== Background ==

Currently, Apache Sirona source is hosted in Apache Commons Sandbox
scm. The development has begun few years ago but goes to dormant
statut.

== Rationale ==

Currently users who need some monitoring need to use some non Open
Source solutions or GPL solutions. The goal is to provide a solution
based on the Apache License.

== Initial Goals ==

Apache Sirona doesn't have any release currently. The initial goal of
this project will be to build community in the spirit of the "Apache
Way", and to address new features and bug-fixes of the first releases.

=== Current Status ===

Intent of the proposal is to build a diverse community of developers
around Sirona. Sirona started in the Apache Commons Sandbox, driven in
the spirit of open source and we would like to continue in this spirit
by, for example, encouraging contributors from a variety of
organizations.

=== Community ===

Apache Sirona stakeholders desire to expand the user and developer
base of Apache Sirona further in the future

== Known Risks ==

=== Orphaned Products ===

Sirona is a new product. So without community adoption the risks of it
being orphaned exist.

=== Inexperience with Open Source ===

The code has been developed in Apache Commons Sandbox mostly by Romain
Manni-Bucau and Olivier Lamy who intimately familiar with the Apache
model for open-source development and is experienced with working with
new contributors.

=== Homogeneous Developers ===

The initial set of committers is from a small set of organizations.
However, we expect that once approved for incubation, the project will
attract new contributors from diverse organizations and will thus grow
organically. The participation of developers from several different
organizations in the mailing list is a strong indication for this
assertion.

=== Reliance on Salaried Developers ===

It is expected that Apache Sirona will be developed on salaried and
volunteer time.

=== Relationships with Other Apache Products ===

Apache Sirona depends upon other Apache Projects: Velocity and various
Apache Commons components and build systems like Maven.

=== A Fascination with the Apache Brand ===

The reason for joining Apache is to foster a healthy community of
contributors and consumers around the project. This is facilitated by
ASF and that is the primary reason we would like Apache Sirona to
become an Apache project.

== Documentation ==

Docs: http://commons.apache.org/sandbox/commons-monitoring/

== Initial Source ==

https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk

== Source and Intellectual Property Submission Plan ==

The initial source is already Apache 2.0 licensed.

== External Dependencies ==

The required external dependencies are all Apache License or
compatible licenses. Following components with non-Apache licenses are
enumerated :

== Cryptography ==

Apache Sirona does not depend upon any cryptography tools or libraries.

== Required Resources ==

=== Mailing lists ===

* sirona-private (with moderated subscriptions)

* sirona-dev

* sirona-commits

* sirona-user

== Subversion Directory ==

https://svn.apache.org/repos/asf/incubator/sirona

== Issue Tracking ==

JIRA Sirona (key: SIRONA)

== Other Resources ==

The existing code already has unit and integration tests so we would
like to use Jenkins instance to run them whenever a new patch is
submitted. This can be added after project creation.

== Initial Committer ==

* Romain Manni-Bucau (rmannibu...@apache.org)

* Jean-Louis Monteiro (jlmonte...@apache.org)

* Fred Zhang (no ASF account)

* Fabrice Bacchella (no ASF account)

* Christian Grobmeier (grobme...@apache.org)

== Affiliations ==

* Olivier Lamy, Ecetera

* Fred Zhang, Ecetera

== Sponsors ==

=== Champion ===

* Olivier Lamy (ol...@apache.org)

=== Nominated Mentors ===

* Olivier Lamy (ol...@apache.org)

* Henri Gomez (hgo...@apache.org)

* Jean-Baptiste Onofré (jbono...@apache.org)

* Tammo van Lessen (va...@apache.org)

* Mark Struberg (strub...@apache.org)



Thanks



-
To unsubsc

Re: [PROPOSAL] Knox Hadoop Gateway Project

[Hadrian Zbarcea]

+1 on the idea.
+1 (strong) on the need to increase diversity.

I would suggest to open a bit the scope of the project to target other 
apache projects that act as services. I know it was mentioned, but it 
sounded to me more like a possibility than a focus.


I would also volunteer as a committer and, if you prefer, mentor. I 
assume it would be possible to take a peek at the code grant in the 
coming days.


Cheers,
Hadrian

On 02/11/2013 10:10 AM, Bertrand Delacretaz wrote:

On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
 wrote:
...

=== Nominated Mentors ===

Owen O’Malley (omalley AT apache DOT org)
Mahadev Konar (mahadev AT apache DOT org)
Alan Gates (gates AT apache DOT org)
Devaraj Das (ddas AT apache DOT org)

...

Considering all initial committers are from hortonworks, I'd like to
see affiliations for mentors as well - or at least indicate which
mentors are *not* affiliated with hortonworks.

-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

Re: [DISCUSS] Apache Mayhem proposal

[Hadrian Zbarcea]

Simone,

You may want to update the Confluence and Jira spaces to ONAMI as well.

I think Confluence is getting out of commission soon, CMS may be the 
better option?!


Hadrian

On 11/11/2012 01:01 PM, Simone Tripodi wrote:

moreover, "Onami" rhymes "Olamy" :)

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


On Sun, Nov 11, 2012 at 4:41 PM, Olivier Lamy  wrote:

2012/11/11 Simone Tripodi :

Yesterday in the night (EU time) Christian Grobmeier and I, while
chatting about psychology and philosophy, thought about the name
"Onami", it comes from a Zen story[1].

WDYT?

good idea !


best,
-Simo

[1] http://www.101zenstories.com/index.php?story=8

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


On Sun, Nov 11, 2012 at 11:15 AM, Ioannis Canellos  wrote:

How about 5hem?

--
Ioannis Canellos


On Friday, 9 November 2012 at 6:48 μ.μ., Simone Tripodi wrote:


Please ignore that proposal, the world is already full of projects
with that name :(

looks like I have issues about originality, lately...

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 
(mailto:general-unsubscr...@incubator.apache.org)
For additional commands, e-mail: general-h...@incubator.apache.org 
(mailto:general-h...@incubator.apache.org)







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





--
Olivier Lamy
Talend: http://coders.talend.com
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



-
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] Approve Openmeetings (Incubating) release

[Hadrian Zbarcea]

+1 (binding)

I went through the artifacts and everything looks in order.
Hadrian

On 07/23/2012 06:03 AM, Alexei Fedotov wrote:

The Openmeetings community voted on and has approved a proposal to release
Openmeetings 2.0. Pursuant to the Releases section of the Incubation
Policy and with the endorsement of two of our mentors we would now
like to request the permission of the Incubator PMC to publish the
release on the Download page.

Please vote by 26 July 10 AM GMT

Thanks,
Alexei

Proposal:
http://markmail.org/message/aahmijcb5dsjlxiv

Vote result:
http://markmail.org/message/azenwwlcfhnxmysf

Download page:
http://www.apache.org/dist/incubator/openmeetings

Releases section of the Incubation Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

Demos & Kittens
http://markmail.org/message/oqj3eko732rx2cgy



On Mon, Jul 23, 2012 at 11:50 AM, Alexei Fedotov
 wrote:


Jukka, thanks for explaining.

Ross, Andrus,
would you please consider voting for the Openmeetings release? We are stuck 
with insufficient number of votes. Thanks!

Incubator folks,
Don't allow another little cute kitten and fluffy puppy die by missing Apache 
Openmeetings (Incubating) release:
http://demo.openmeetings.de/openmeetings/
http://demo.dataved.ru/openmeetings/

You are mostly welcome to support our release here
http://markmail.org/message/azenwwlcfhnxmysf


--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095



On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting  wrote:


Hi,

On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov
 wrote:

The release vote have successfully passed and forwarded to general@
list [1]. What should be our next step? Have we got Incubator PMC
approval? Can we proceed with wider distribution?


See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
for the Incubator policy on releases. You're almost done, just an
extra approval vote on general@ is still needed (and since you already
have two mentor +1s, you only need one more IPMC member to vote for
the release).

BR,

Jukka Zitting

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





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



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

Re: [VOTE] CloudStack for Apache Incubator

[Hadrian Zbarcea]

at the CloudStack will have to follow the export 
control procedures described at http://www.apache.org/dev/crypto.html. When the 
CloudStack was previously registered with BIS the open source version qualified 
for the TSU exception.

The CloudStack uses https to communicate to XenServer and vCenter. ssh and scp 
are used between the Management Server and hypervisor hosts as well.

The CloudStack stores an MD5 hash of user password data. The CloudStack uses 
MySQL encryption to store some data in an encrypted fashion.

The CloudStack stores a pair of API public/secret keypairs for users. This is 
done using javax.crypto.KeyGenerator with HMAC-SHA-1.

The CloudStack does not specify key lengths explicitly. It uses SSH, SCP and 
lets them negotiate encryption.

The CloudStack provides a public HTTP-based API to provision and deprovision 
VPN users. The CloudStack has internal Java-based abstractions for managing VPN 
users. This Java software makes private API calls to another system, which will 
then provision the VPN user in the VPN software on that other system. The 
actual set up of the VPN session is done using L2TP/IPSec.

As mentioned earlier the CloudStack includes software to build and later deploy 
Debian-based virtual machines. These VMs are stripped down versions of Debian 
that include encryption sufficient for ssh/scp, https, and IPSec VPN to work. 
The CloudStack does not include the source for these VMs. The maximum encrypted 
throughput of the VPN has not been determined.

Required Resources

Mailing Lists

We request mailing lists to match the mailing lists currently in use, plus the 
recommended private list. These are:

 cloudstack-private: for confidential PPMC discussion
 cloudstack-dev: for development discussions
 cloudstack-user: for administrator and discussions

Subversion Directory

The CloudStack has used git for approximately two years. We understand that there is a 
"prototype" git server available. We request an allocation on this git server. 
We believe this will be less disruptive to the committers than a change to SVN.

We request "/repos/asf/incubator/cloudstack".

Issue Tracking

We would like an allocation for Jira. CloudStack uses bugzilla today, but we have been 
planning a move to Jira for some time. We request that the project name be 
"CloudStack".

Other Resources

The CloudStack Project includes several websites. Donation of these websites 
was discussed in the IP submission plan. We would like to engage in discussion 
on the logistics of this.

Initial Committers

In the past few months several new developers have joined the Citrix CloudStack 
team. We are recommending that only the developers with several months of 
experience with CloudStack join as initial committers. The Project will then 
follow the meritocratic process to enable the newer team members to become 
committers. We believe this will be a good exercise for us as we transition to 
an Apache development model in the Project.

The list of initial committers follows. At this time none of the initial 
committers has a CLA on file with ASF.

 Abhinandan Prateek, abhinandan.prateek.at.citrix.com
 Alena Prokharchyk, alena.prokharchyk.at.citrix.com
 Alex Huang,alex.huang.at.citrix.com
 Anthony Xu, xuefei.xu.at.citrix.com
 Brian Federle, brian.federle.at.citrix.com
 Chiradeep Vittal, chiradeep.vittal.at.citrix.com
 David Nalley, david.nalley.at.citrix.com
 Edison Su, edison.su.at.citrix.com
 Frank Zhang, frank.zhang.at.citrix.com
 Janardhana Reddy, janardhana.reddy.at.citrix.com
 Jessica Tomechak, jessica.tomechak.at.citrix.com
 Jessica Wang, jessica.wang.at.citrix.com
 Kelven Yang, kelven.yang.at.citrix.com
 Kevin Kluge, kevin.kluge.at.citrix.com
 Kishan Kavala, kisha.kavala.at.citrix.com
 Murali Reddy, murali.reddy.at.citrix.com
 Nitin Mehta, nitin.mehta.at.citrix.com
 Prachi Damle, prachi.damle.at.citrix.com
 Sam Robertson, sam.robertson.at.citrix.com
 Sheng Yang, sheng.yang.at.citrix.com
 Sonny Chhen, sonny.chhen.at.citrix.com
 Will Chan, will.chan.at.citrix.com

Affiliations

The initial committers are all affiliated with Citrix Systems.

Sponsors

Champion

Jim Jagielski

Nominated Mentors

Jim Jagielski, Daniel Kulp, Alex Karasulu, Olivier Lamy, Brett Porter, Mohammad 
Nour, Matt Hogstrom

Sponsoring Entity

We request that the Incubator sponsor this effort.



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



--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator

[Hadrian Zbarcea]

Fiar enough. That being the case, I would like to join as a committer 
(there are enough great mentors already).


Cheers,
Hadrian


On 04/09/2012 12:15 AM, Kevin Kluge wrote:

Hi Hadrian, yes, we have been discussing this.  There are a number of options 
today that make the system easier to develop against than it might seem. It's 
possible to have a single node cloud with KVM, where the CloudStack management 
server and KVM host are the same server.   With XenServer or XCP you can work 
with a two node system.  Or you can have  a VM for the management server and a 
physical host for the hypervisor.   There is also a XenServer API simulator 
available, which would allow development with XenServer with just two VMs (one 
for the management server and one for the XenServer simulator).   CloudStack 
developers have used these environments for most development to date.

We have also developed a software simulator.  This simulator emulates 
hypervisor hosts under management through a single process.  Although it was 
originally built for scalability testing, it should be possible to use it for 
development and functional testing as well.  We have been thinking this would 
be the best way to enable the larger community to easily develop and test 
against CloudStack long term.  This should work today, but there are no good 
docs on how to set it up, nor do we have much experience with it in this 
context.  This is something we need to do to help the new community members 
engage (or we need some intrepid community members to try it and document the 
successful path).

We have also discussed donating and/or hosting build and test infrastructure 
for pending commits to the project.  This would be a public system test 
environment.   Our automated test tools can take a cloud description in JSON 
and implement it, provided the hosts and storage are already provisioned (e.g., 
via PXE boot).  While we have some good building blocks, we need to improve the 
automated system tests and implement some glue code to provide a process that 
can be driven from a web UI.   If this is what the community needs I think we 
will be able to provide the hardware.  In terms of timing I am more concerned 
about the test development and glue to make it all work than the hardware 
acquisition, and I believe this is a few months away.

-kevin




-Original Message-
From: Hadrian Zbarcea [mailto:hzbar...@gmail.com]
Sent: Friday, April 06, 2012 6:49 PM
To: general@incubator.apache.org
Subject: Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator

I find the proposal interesting too. I gave it a lot of though and I am
considering getting involved as well. I have a question however for the
proponents and supporters of the project.

What makes this project different than (almost) all the other ASF projects is
that it has a high(er) barrier to entry in terms of hardware requirements. The
reality is that such a project has little chances of becoming a viable
competitor in the industry without strong support from companies like Citrix
(and I salute their commitment). Will such resources be made available to the
whole community, how was this envisioned?

Thanks,
Hadrian



On 04/04/2012 04:22 PM, Mohammad Nour El-Din wrote:

On Wed, Apr 4, 2012 at 10:20 PM, Alex Karasulu

wrote:



On Wed, Apr 4, 2012 at 8:55 PM, Matt Hogstrom

wrote:



The proposal looks good.  I'm excited that the community is looking
to grow at the ASF.  I'm working on similar technology in my day job
at IBM and am interested in getting involved.  Happy to mentor if
you need, although, it has quite a large list now as I look at the Wiki.



The number of mentors should not be an issue. As stated before, in
other threads, the number of mentors is unbounded and AOO has 8 as an

example.


The perspective podling should not feel that the list is too long -
more mentors and interest is a good thing. We have much to do, the
project is not small, and it would be nice to see the community
gracefully pass thru incubation as fast as posible in accordance with
incubator standards. More mentors might help in this regard.



Indeed




--
Best Regards,
-- Alex







--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.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



--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project

[Hadrian Zbarcea]

+1
Hadrian

On 04/02/2012 05:10 AM, Andy Seaborne wrote:

This is a call for vote to graduate the Apache Jena podling from Apache
Incubator to be a top level project.

Jena entered incubation in November 2010. The project has added two new
committers and PPMC members, made several releases and has a diverse
committer base. The user and development communities are active. The
PPMC has indicated [1,2,3] that it believes the project is ready to
graduate as a top-level project with the resolution draft below.

We ask that the IPMC approve this graduation request though this VOTE.

[1] Vote: http://s.apache.org/jena-graduation-vote
[2] Result: http://s.apache.org/jena-graduation
[3] Request for comments:
http://mail-archives.apache.org/mod_mbox/incubator-general/201203.mbox/%3C5C4A33CB-B122-43A8-B082-CBD63B526DE7%40cray.com%3E


On behalf of the Apache Jena PPMC,

Andy

-

[ ] +1 Recommend to the ASF Board that Apache Jena Proposal
is ready to graduate to being a top level project.
[ ] 0
[ ] -1 Do not graduate Apache Jena because ...

The vote will be tallied no earlier than:

Thursday April 5th, at 23:59 UTC.

-

X. Establish the Apache Jena 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 accessing, storing, querying,
publishing and reasoning with semantic web data while
adhering to relevant W3C and community standards.

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

RESOLVED, that the Apache Jena Project be and hereby is
responsible for the creation and maintenance of software
related to accessing, storing, querying,
publishing and reasoning with semantic web data while
adhering to relevant W3C and community standards;
and be it further

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

* Andy Seaborne (andy)
* Benson Marguilies (bimargulies)
* Chris Dollin (chrisdollin)
* Damian Steer (damian)
* Dave Reynolds (der)
* Ian Dickinson (ijd)
* Paolo Castagna (castagna)
* Rob Vesse (rvesse)
* Stephen Allen (sallen)

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Seaborne
be appointed to the office of Vice President, Apache Jena, 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 Jena 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 Jena Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Jena 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



--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator

[Hadrian Zbarcea]

I find the proposal interesting too. I gave it a lot of though and I am 
considering getting involved as well. I have a question however for the 
proponents and supporters of the project.


What makes this project different than (almost) all the other ASF 
projects is that it has a high(er) barrier to entry in terms of hardware 
requirements. The reality is that such a project has little chances of 
becoming a viable competitor in the industry without strong support from 
companies like Citrix (and I salute their commitment). Will such 
resources be made available to the whole community, how was this envisioned?


Thanks,
Hadrian



On 04/04/2012 04:22 PM, Mohammad Nour El-Din wrote:

On Wed, Apr 4, 2012 at 10:20 PM, Alex Karasulu  wrote:


On Wed, Apr 4, 2012 at 8:55 PM, Matt Hogstrom  wrote:


The proposal looks good.  I'm excited that the community is looking to
grow at the ASF.  I'm working on similar technology in my day job at IBM
and am interested in getting involved.  Happy to mentor if you need,
although, it has quite a large list now as I look at the Wiki.



The number of mentors should not be an issue. As stated before, in other
threads, the number of mentors is unbounded and AOO has 8 as an example.

The perspective podling should not feel that the list is too long - more
mentors and interest is a good thing. We have much to do, the project is
not small, and it would be nice to see the community gracefully pass thru
incubation as fast as posible in accordance with incubator standards. More
mentors might help in this regard.



Indeed




--
Best Regards,
-- Alex







--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project

[Hadrian Zbarcea]

+1

On 02/26/2012 11:03 AM, Robert Burrell Donkin wrote:

The graduation guide[1] recommends that the Rat community demonstrates
it's willingness to govern itself through a free VOTE before asking the
IPMC to approve graduation. So, here it is :-)

See [2] for a draft of the charter, excluding the list of initial
committers. Unless anyone jumps into this thread, I'll assume that the
current list of committers would be fine. Please read, review and jump
in - but this is a vote on the principle of graduating now.

This VOTE is open to all, and I'll tally this no early than Wednesday,
29 Feb 2012 17:00 UTC.

Robert

--8<---
[ ] +1 the RAT community feels ready to graduate as Apache Creadur
[ ] +0
[ ] -0
[ ] -1 Do not graduate RAT at this time
---


[1] http://incubator.apache.org/guides/graduation.html#toplevel
[2] Suggested Draft Charter:

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 comprehension and
auditing of software distributions 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 Creadur Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Creadur Project be and hereby is
responsible for the creation and maintenance of open-source
software related to the comprehension and auditing of software
distributions for distribution at no charge to the public

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

...

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell
Donkin be appointed to the office of Vice President, Apache
Creadur, 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 Creadur 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 Creadur Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator RAT 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



--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [VOTE] Graduate Apache Rave as TLP

[Hadrian Zbarcea]

+1 (binding)
Hadrian

On 02/27/2012 07:26 AM, Ate Douma wrote:

Hi IPMCers and Incubator community,

Apache Rave entered the Incubator almost 1 year ago on March 1st 2011.
Since then Rave provided 7 incubator releases, added 3 more
committers/PPMC members, and shows a steady growth of community and
interest in general.
Diversity is great, as is the collaboration between the project members
and with the community as a whole.

The Rave PPMC decided it is now time to consider graduation from the
Incubator and held a community vote which was accepted unanimous and
includes the support of the 4 Rave Mentors [1].

I therefore now request the IPMC to vote on recommending the graduation
of Rave with the below resolution [2] to the ASF Board.

Please cast your votes:

[ ] +1 to recommend graduation of Apache Rave as TLP
[ ] +0 don't care.
[ ] -1 no, don't recommend yet, because ...

This vote will be open for 72 hours.

Regards, Ate

[1] http://s.apache.org/TBH

[2] https://issues.apache.org/jira/browse/RAVE-428, and copied below:

X. Establish the Apache Rave 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 widgets-based, web-and-social
mashup platform 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 Rave Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Rave Project be and hereby is
responsible for the creation and maintenance of software
related to a widgets-based, web-and-social mashup platform;
and be it further

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

* Ard Schrijvers 
* Ate Douma 
* Bas Zoetekouw 
* Gerald Guo 
* Hadrian Zbarcea 
* Jasha Joachimsthal 
* Jesse Ciancetta 
* Joost van Dijk 
* Maarten Kremers 
* Marlon Pierce 
* Matt Franklin 
* Niels van Dijk 
* Okke Harsta 
* Raminder Singh 
* Ross Gardler 
* Sander van der Waal 
* Scott Wilson 
* Sean Cooper 
* Suresh Marru 
* Tony Carlucci 
* Unico Hommes 
* Venkat Mahadevan 
* Woonsan Ko 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matt Franklin
be appointed to the office of Vice President, Apache Rave, 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 Rave 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 Rave Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Rave 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



--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

-
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

[Hadrian Zbarcea]

+1 (binding)
Hadrian

On 02/08/2012 09:39 AM, Mohammad Nour El-Din wrote:

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
- Carlos Vara Callau
- David Jencks
- Donald Woods
- Gerhard Petracek
- Jeremy Bauer
- Kevan Lee Miller
- Luciano Resende
- Matthias Wessendorf
- Matthew Jason Benson
- Mohammad Nour El-Din
- Roman Stumm
- Simone Tripodi
- Mark Struberg

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.


--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

[jira] [Commented] (PODLINGNAMESEARCH-5) Establish Whether "Apache Rave" would be a Suitable Name

[Hadrian Zbarcea (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193273#comment-13193273
 ] 

Hadrian Zbarcea commented on PODLINGNAMESEARCH-5:
-

Cannot edit the issue, somebody who can could move my findings in the relevant 
sections above. As a note, the research about is fairly complete and matches my 
findings (thanks Matt). The only extra things I found are below:

http://en.wikipedia.org/wiki/Rave_%28disambiguation%29
 * nothing software related

Software:
 * Medidata Rave (http://www.mdsol.com/products/rave_overview.htm)
 * http://www.workrave.org/
 * http://www.raveyrave.com/

TESS (http://www.uspto.gov/trademarks/index.jsp) - 344 Records(s)
 * good summary above; I went through most of the applications, nothing else 
that raised a flag

OHIM (http://oami.europa.eu/ows/rw/pages/index.en.do) - 25 results
 * interactive visualization display systems; computer hardware for use in 
creating, manipulating and interacting with virtual environments
 * computer software; development: software for the creation, modification, and 
testing of real time graphical displays
 * controller, apparatus for recording and playback of audio and visual, 
data-processing equipment and computers; ... (German - probably gaming related)
 * computer hardware and software for verification of hardware, computer chips, 
circuit boards and integrated circuits...
 * and a bunch unrelated others...

> Establish Whether "Apache Rave" would be a Suitable Name
> 
>
> Key: PODLINGNAMESEARCH-5
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-5
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Matt Franklin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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

Fwd: [NOTICE] Account created: Sean David Cooper (secooper)

[Hadrian Zbarcea]

Looks like I don't have sufficient karma to do it myself. Could someone 
with karma please give 'secooper' svn rights for the rave project?


Requested change in [1]:
-rave=ard,ate,hadrian,rgardler,scottbw,unico,upayavira,woonsan,mfranklin,jcian,carlucci,svanderwaal,mpierce,raminder,zhguo,smarru,cthings,mkremers,bas,joostvandijk,oharsta,jasha
+rave=ard,ate,hadrian,rgardler,scottbw,unico,upayavira,woonsan,mfranklin,jcian,carlucci,svanderwaal,mpierce,raminder,zhguo,smarru,cthings,mkremers,bas,joostvandijk,oharsta,jasha,secooper

[1] 
https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template


Many thanks,
Hadrian


 Original Message 
Subject: [NOTICE] Account created: Sean David Cooper (secooper)
Date: Fri, 18 Nov 2011 21:53:09 + (UTC)
From: r...@apache.org
Reply-To: priv...@incubator.apache.org, r...@apache.org
To: priv...@incubator.apache.org
CC: r...@apache.org

Hi,

The account 'secooper' was created for Sean David Cooper as requested
by this PMC.  The account has been added to the 'incubator' Unix group
as well as the 'committers' Unix group for you.

Please grant additional karma to the projects in your domain
you wish the user to have commit to.

Only PMC chairs (and, for podlings, also Infrastructure volunteers) can
grant karma.  If needed, please post to the general@/dev@/private@ list
of your project asking for someone with sufficient karma to grant access
to 'secooper'.


The Apache Infrastructure Team

-
To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
For additional commands, e-mail: private-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 ACE from the Apache Incubator

[Hadrian Zbarcea]

+1 (binding)
Hadrian

On 11/17/2011 05:42 AM, Marcel Offermans wrote:

In my opinion, ACE is ready to begin the process of graduating from the Apache 
Incubator to a Top Level Project.

Since joining the incubator in in May 2009 we've added 4 new committers (12 in 
total now) from diverse organizations and did a release in May this year to 
demonstrate we follow the Apache guidelines. We've shown an ability to 
self-govern using accepted Apache practices and ACE continues to attract new 
contributors and users.

The first step is to vote as a community, demonstrating that ACE is ready and 
willing to graduate. Once this vote is succesful we create a board resolution 
proposal or Charter and start a vote on the general incubator list. The full 
process is described at 
http://incubator.apache.org/guides/graduation.html#toplevel

The vote is open for at least 72 hours.

Greetings, Marcel




--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

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

Re: [VOTE] Release Apache Rave 0.3-incubating

[Hadrian Zbarcea]

+1 (again), binding


Hadrian

On 09/15/2011 08:49 AM, Franklin, Matthew B. wrote:

-Original Message-
From: Hadrian Zbarcea [mailto:hzbar...@gmail.com]
Sent: Thursday, September 15, 2011 8:45 AM
To: rave-...@incubator.apache.org
Subject: Re: Ping: [VOTE] Release Apache Rave 0.3-incubating

+1. If not too late.


Not too late if you send it to the general@incubator list :)




Hadrian

On 09/13/2011 03:07 AM, Ate Douma wrote:

A week has passed since this vote started and but still no feedback so far.

Possibly it was drowned by the Accumulo discussions, but now that has
passed...

It would be very appreciated if one or more of the IPMC members could
spare a little time to review this podling release candidate, and cast a
vote on it.
(we still need one +1 extra from IPMC on this to pass)

Kind regards,

Ate

On 09/05/2011 03:01 PM, Franklin, Matthew B. wrote:

This is the second incubator release for Apache Rave, with the
artifacts being versioned as 0.3-incubating.

We are requesting at least one IPMC member vote, as we have already
received 2 binding IPMC +1 votes during the release voting on rave-dev -
VOTE: http://goo.gl/VH5ok
RESULT: http://goo.gl/b9hxh

Release notes:
https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-

incubating/CHANGELOG



SVN source tag (r1163402):
https://svn.apache.org/repos/asf/incubator/rave/rave-master-

pom/tags/0.3-incubating/



SVN source tag (r1163411):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.3-incubating/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapacherave-002/

Source releases:
https://repository.apache.org/content/repositories/orgapacherave-

002/org/apache/rave/rave-master/0.3-incubating/rave-master-0.3-
incubating-source-release.zip


https://repository.apache.org/content/repositories/orgapacherave-

002/org/apache/rave/rave-project/0.3-incubating/rave-project-0.3-
incubating-source-release.zip



Demo Artifacts
http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-

incubating-bin.tar.gz


http://people.apache.org/builds/incubator/rave/0.3-incubating/rave-0.3-

incubating-bin.zip



PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS

Vote open for 72 hours.

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





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

Re: [Vote]: Libcloud to become a TLP

[Hadrian Zbarcea]

+1 (binding)


On May 16, 2011, at 1:42 AM, Tomaz Muraus wrote:

> OK, sorry for the confusion, but apparently I need to open a separate voting
> thread so here it is.
> 
> Here is also a list of people who have already voted +1 in the proposal
> thread which can be found at
> http://mail-archives.apache.org/mod_mbox/incubator-general/201105.mbox/%3cbanlktikhycoedn3r9o41ohmgj1hs41d...@mail.gmail.com%3E
> :
> 
> - Paul Querna
> - Chris Mattmann
> - Joe Schaefer (binding)
> - Davanum Srinivas (binding)
> - Mohammad Nour El-Din
> - Alan D. Cabrera
> - Tommaso Teofili (binding)
> - Mark Struberg (binding)
> - Luciano Resende (binding)
> 
> 
> 
> 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.


-
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

[Hadrian Zbarcea]

+1 (binding)

Hadrian


On Apr 29, 2011, at 6:35 AM, Jörn Kottmann wrote:

> 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
> 


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

Re: Erlend Garåsen, voted to be a committer for ManifoldCF, still waiting for an Apache account

[Hadrian Zbarcea]

You need to ask the new committer for a preferred user id (it'll be part of his 
apache email address) and send an request to r...@apache.org. All is explained 
here [1].

[1] http://www.apache.org/dev/pmc.html#newcommitter

Cheers,
Hadrian


On Apr 26, 2011, at 5:04 PM, Karl Wright wrote:

> Hi folks,
> 
> About 3 weeks ago I cc'd the results of the ManifoldCF PPMC vote on
> Erlend to priv...@incubator.apache.org, as per the instructions, but
> he still has not received any communication about an Apache account
> and is thus blocked from doing committer related activities.  Is there
> some process that we missed?
> 
> 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][PROPOSAL] OGNL join the Incubator

[Hadrian Zbarcea]

+1 

Hadrian


On Apr 23, 2011, at 7:57 AM, Simone Tripodi wrote:

> 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 
> * Christian Grobmeier 
> * Jesse Kuhnert 
> * Jochen Wiedmann 
> * Lukasz Lenart 
> * Olivier Lamy 
> * Marc Andrew Davidson 
> * Maurizio Cucchiara 
> * Simone Tripodi 
> * Upayavira 
> 
> 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 existing ASF projects already benefit from OGNL
> implementation, including Apache Struts, Apache Tapestry, Apache Tiles
> and Apache Camel. It is hoped that members of those projects will be
> i

Re: [PROPOSAL] Apache Rave project

[Hadrian Zbarcea]

Troy, I am not really sure what your point is. So you believe that:
> I think the 'Known Risks' section in the proposal enumerates that
> pretty clearly, so I won't repeat it.

... yet you raise an objection for somebody else who might think otherwise?
Is that because you anticipate an objection and you want to prevent that by 
suggesting a solution that my prevent the objection to occur in the first place?
> [...] My statements were meant to speak to
> the folks who think otherwise, as a reasonable compromise (assuming
> Bill's stance, and anyone who is quietly in agreement, is to not allow
> it into the Incubator).

Why not let the guys who have an objection speak for themselves?

Regarding Bill's message, I didn't see him raising an objection, just making a 
valid point.
Ate explained already both that it was addressed and the rationale for the 
wording in the proposal.

> I don't think my vote counts for much, but I'm a +1. ;)
Well, the vote is on now.

If I misunderstood your intentions I am sorry, but they are not very clear.


Cheers,
Hadrian



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

Re: [VOTE] Accept Rave into the Incubator

[Hadrian Zbarcea]

the initial contributed code can be seen here:
> * MITRE: [[http://code.google.com/p/osec|OpenSocial Enterprise Container]]
> * SURFnet: [[https://portal.surfconext.nl|SURFConext Portal]]; 
> [[https://wiki.surfnetlabs.nl/display/surfconextdev/Technical+Design|SURFconext
>  technical design]]
> * [[http://www.collab-ogce.org|OGCE]] 
> [[http://www.collab-ogce.org/ogce/index.php/OGCE_Gadget_Container|OGCE Gadget 
> Container]]
> 
> Because this project will create new code, we will not have any documentation 
> on first starting. It is likely however that partial documentation can be 
> reused from either codebases.
> 
> 
> == Initial Source ==
> 
> The initial source will be made up of three contributions, namely:
> * [[http://code.google.com/p/osec/source|MITRE OpenSocial Enterprise 
> Container - Source]]
> * SURFnet SURFconext Portal - This source will be brought into the Incubator 
> as SURFnets contribution
> * OGCE: Gadget Container code is part of the 
> [[http://sourceforge.net/projects/ogce/develop|OGCE SourceForge Site]]. See 
> [[http://www.collab-ogce.org/ogce/index.php/Portal_download|the portal 
> download page]] for SVN instructions.
> 
> 
> == Source and Intellectual Property Submission Plan ==
> 
> 
>  Hippo 
> 
> The code to be offered by Hippo is already open source and Apache Licensed.
> 
> 
>  The MITRE Corporation 
> 
> The code offered by The MITRE Corporation is already open source and Apache 
> Licensed.
> 
> 
>  SURFnet SURFConext Portal 
> 
> This source will be brought into the Incubator as SURFnets contribution; 
> initial project members have already been given access for evaluation 
> purposes.
> 
> 
>  Open Gateway Computing Environments 
> 
> The OGCE will contribute its Gadget Container code, which is Apache licensed 
> and available from !SourceForge, with current dependencies and their licenses 
> described below.
> Other OGCE software efforts are not covered by this incubator proposal and 
> are not included in the code contribution.
> 
> 
> == Dependencies on other Apache Projects ==
> 
> * Apache Shindig
> * Apache Tomcat
> * Apache Tiles
> * Apache !HttpComponents
> * Apache Commons
> * Apache Log4J
> * Apache Maven
> * Apache Ant
> 
> 
> == Cryptography ==
> 
> There is no cryptography in the code at this time.
> 
> OGCE has requirements to support security for Computational Grids and Clouds. 
> Although the code will not have any cryptographic implementations, in the 
> future there will be dependencies on external cryptographic libraries. Before 
> committing any cryptographic dependencies, the process listed at 
> http://www.apache.org/dev/crypto.html will be followed.
> 
> 
> == Required Resources ==
> 
> 
> === Mailing lists ===
> 
> * rave-dev
> * rave-commits
> * rave-private (moderated subscriptions)
> 
> 
> === Subversion Directory ===
> 
> * http://svn.apache.org/repos/asf/incubator/rave
> 
> 
> === Issue Tracking ===
> 
> We intend to make use of Jira for issue tracking.
> 
> Proposed JIRA key: JIRA-RAVE
> 
> 
> === Other Resources ===
> 
> None right now.
> 
> 
> == Initial Committers ==
> 
> Names of initial committers with affiliation and current ASF status:
> * Ate Douma (Hippo), Apache Member, id: ate
> * Unico Hommes (Hippo), Apache Committer, id: unico
> * Ard Schrijvers (Hippo), Apache Committer, id: ard
> * Woonsan Ko (Hippo), Apache Committer, id: woonsan
> * Matt Franklin (MITRE, osec)
> * Jesse Ciancetta (MITRE, osec)
> * Tony Carlucci (MITRE, osec)
> * Ross Gardler (OSS Watch), Apache Member, id: rgardler
> * Sander van der Waal (OSS Watch)
> * Scott Wilson (University of Bolton), Apache Committer, id: scottbw
> * Hadrian Zbarcea (independent), Apache Member, id: hadrian
> * Marlon Pierce (Pervasive Technology Institute Indiana University, OGCE)
> * Raminderjeet Singh (Pervasive Technology Institute Indiana University, OGCE)
> * Zhenhua Guo (Pervasive Technology Institute Indiana University, OGCE)
> * Suresh Marru (Pervasive Technology Institute Indiana University, OGCE)
> * Niels van Dijk (SURFNET, SURFConext)
> * Maarten Kremers (SURFNET, SURFConext)
> * Bas Zoetekouw (SURFNET, SURFConext)
> * Joost van Dijk (SURFNET, SURFConext)
> * Okke Harsta (Zilverline, SURFConext)
> 
> 
> == Sponsors ==
> 
> 
> === Champion ===
> 
> * Ate Douma
> 
> 
> === Nominated Mentors ===
> 
> * Ate Douma
> * Sylvain Wallez
> * Upayavira
> * Ross Gardler
> * Hadrian Zbarcea
> 
> 
> === Sponsoring Entity ===
> 
> * Apache Incubator Project
> 
> 
> == Appendix A: External Dependencies ==
&

Re: [PROPOSAL] Apache Rave project

[Hadrian Zbarcea]

That was discussed a few times in the past month while we were working on the 
proposal.
I believe that's fairly clear to everybody. The project starts with code grants 
from the organizations mentioned.

Hadrian

On Feb 23, 2011, at 2:49 PM, William A. Rowe Jr. wrote:

> On 2/21/2011 5:18 PM, Ate Douma wrote:
>> 
>> The Apache Rave project proposal is a joined effort of Hippo, the MITRE 
>> Corporation, the
>> Open Gateway Computing Environments project (OGCE), the SURFnet SURFConext 
>> Portal project,
>> OSS Watch, and several other individuals.
> 
> Keep in mind that only individuals participate at Apache, sometimes
> independently, sometimes as employees, but ASF projects are collaborations
> of developers (and docs and users, but principally of developers).  This
> might be part of the reason for some [dis]quiet to the proposal.
> 
> -
> 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 Howl as an Incubator Project

[Hadrian Zbarcea]

+1.

The name can be changed until graduation. 

Hadrian

On Feb 23, 2011, at 10:59 AM, Kevan Miller wrote:

> 
> On Feb 23, 2011, at 4:55 AM, Alex Karasulu wrote:
> 
>> +1
>> 
>> However there might be a name conflict with the Howl transaction log over at
>> object web here:
>> 
>>  http://howl.ow2.org/
>> 
>> Originally from the title, I immediately thought the
>> proposal was for OW's HOWL implementation to enter the incubator.
> 
> Agreed about the name conflict. I made the same assumption. 
> 
> Here's my +1.
> 
> --kevan
> -
> 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