Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Jaideep Dhok]

+1 (non-binding)

Thanks,
Jaideep

On Fri, Dec 19, 2014 at 11:50 AM, Hyunsik Choi  wrote:
>
> +1 (binding)
>
> On Friday, December 19, 2014, 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 some

Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Hyunsik Choi]

+1 (binding)

On Friday, December 19, 2014, 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

Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Henry Saputra]

+1

On Thu, Dec 18, 2014 at 9:29 PM, 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 wa

Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Sharad Agarwal]

+1 (non-binding)

On Fri, Dec 19, 2014 at 10:59 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
> p

Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Ted Dunning]

+1 (binding)



On Thu, Dec 18, 2014 at 9:29 PM, 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
> prin

Re: Volunteer to Shepherd

[Roman Shaposhnik]

On Thu, Dec 18, 2014 at 7:53 PM, Marvin Humphrey  wrote:
> On Thu, Dec 18, 2014 at 7:33 PM, P. Taylor Goetz  wrote:
>
>> I’d like to volunteer to help out as a shepherd.
>
> Super! I hope you find the experience broadening.

Huge +1 to that! We are always in need of shepherds.

Thanks,
Roman.

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

[VOTE] Accept Zeppelin into the Apache Incubator

[Roman Shaposhnik]

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 governed
by the "Apache way". Users and new contributors will be treated 

Re: [VOTE] Graduate Samza from the Incubator

[Ted Dunning]

+1 (binding)

On Thu, Dec 18, 2014 at 8:54 PM, Konstantin Boudnik  wrote:
>
> +1 (binding)
>
> On Fri, Dec 12, 2014 at 03:54PM, Jakob Homan wrote:
> > Restarting vote having fixed resolution detail, dastardly AWOL paragraph
> breaks
> > and removed nod to increased diversity in introduction.
> >
> > The Samza podling community has voted to graduate from the Incubator.
> >
> > The vote passed with 17 +1s and no -1s or +/-0s.
> >
> > Binding +1s x 10 : Jakob, Chinmay, Yan, Chris Riccomini, Sriram,
> > Zhijie, Martin, Roman, Garry, Chris Douglas
> > Non-binding +1s x 7: Claudio, TJ, Robert, Roger, Danny, Jon, Yi
> >
> > Links to votes and discussions:
> > http://s.apache.org/samzaGradResult
> > http://s.apache.org/samzaGradDiscuss
> >
> > Samza has been incubating for a bit more than a year.  In that time
> > the community has:
> > * Completed two Incubator-approved releases
> > * Opened nearly 500 JIRAs
> > * Added five new committers/PMC members.
> >
> > This thread is to vote on the graduation resolution Samza has
> > approved.  It will run for at least 96 hours (to Tuesday, 12/22 4pm
> > PST, the extra day to accommodate the weekend and holiday schedule).
> >
> > [ ] +1 Graduate Apache Samza from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Samza from the Incubator because ...
> >
> > Here's my binding vote: +1.
> >
> > -Jakob
> >
> > 
> > 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 low-latency, distributed processing of streaming data.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC),
> > to be known as the "Apache Samza Project", be and hereby is established
> > pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Samza Project be and hereby is responsible for
> > the creation and maintenance of software related to low-latency,
> > distributed processing of streaming data; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Samza" 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 Samza Project, and to
> > have primary responsibility for management of the projects within the
> scope
> > of responsibility of the Apache Samza 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 Samza Project:
> >
> > * Chinmay Soman 
> > * Chris Riccomini 
> > * Garry Turkington 
> > * Jakob Homan 
> > * Jay Kreps 
> > * Martin Kleppman 
> > * Sriram Subramanian 
> > * Yan Fang 
> > * Zhijie Shen 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris Riccomini be
> > appointed to the office of Vice President, Apache Samza, 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 Samza Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Samza
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Samza podling encumbered upon the Apache Incubator Project are
> > hereafter discharged.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

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

[Roman Shaposhnik]

Thank you to all who contributed to the dissuasion! I think
I took all of the feedback into account and will start a formal
vote in a minute.

Thanks,
Roman.

On Thu, Dec 18, 2014 at 9:09 PM, Hadrian Zbarcea  wrote:
> +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, applicati

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: [DISCUSS] [PROPOSAL] Zeppelin for Apache Incubator

[Timothy Chen]

+1 (non-binding).

Agree it's a good addition to the stack.

Tim

On Thu, Dec 18, 2014 at 8: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, 

Re: [VOTE] Graduate Samza from the Incubator

[Konstantin Boudnik]

+1 (binding)

On Fri, Dec 12, 2014 at 03:54PM, Jakob Homan wrote:
> Restarting vote having fixed resolution detail, dastardly AWOL paragraph 
> breaks
> and removed nod to increased diversity in introduction.
> 
> The Samza podling community has voted to graduate from the Incubator.
> 
> The vote passed with 17 +1s and no -1s or +/-0s.
> 
> Binding +1s x 10 : Jakob, Chinmay, Yan, Chris Riccomini, Sriram,
> Zhijie, Martin, Roman, Garry, Chris Douglas
> Non-binding +1s x 7: Claudio, TJ, Robert, Roger, Danny, Jon, Yi
> 
> Links to votes and discussions:
> http://s.apache.org/samzaGradResult
> http://s.apache.org/samzaGradDiscuss
> 
> Samza has been incubating for a bit more than a year.  In that time
> the community has:
> * Completed two Incubator-approved releases
> * Opened nearly 500 JIRAs
> * Added five new committers/PMC members.
> 
> This thread is to vote on the graduation resolution Samza has
> approved.  It will run for at least 96 hours (to Tuesday, 12/22 4pm
> PST, the extra day to accommodate the weekend and holiday schedule).
> 
> [ ] +1 Graduate Apache Samza from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Samza from the Incubator because ...
> 
> Here's my binding vote: +1.
> 
> -Jakob
> 
> 
> 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 low-latency, distributed processing of streaming data.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Samza Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Samza Project be and hereby is responsible for
> the creation and maintenance of software related to low-latency,
> distributed processing of streaming data; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Samza" 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 Samza Project, and to
> have primary responsibility for management of the projects within the scope
> of responsibility of the Apache Samza 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 Samza Project:
> 
> * Chinmay Soman 
> * Chris Riccomini 
> * Garry Turkington 
> * Jakob Homan 
> * Jay Kreps 
> * Martin Kleppman 
> * Sriram Subramanian 
> * Yan Fang 
> * Zhijie Shen 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chris Riccomini be
> appointed to the office of Vice President, Apache Samza, 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 Samza Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Samza
> podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Samza 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
> 


signature.asc
Description: Digital signature

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

[Konstantin Boudnik]

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

Re: Votes for git repos - commit id vs tag

[Konstantin Boudnik]

Good point!

On Thu, Dec 18, 2014 at 01:58PM, John D. Ament wrote:
> All,
> 
> I was looking through the incubator site and I don't see anything definite.
> 
> Whenever a podling goes for a vote, and they include a git tag in their
> vote message, it's typically asked to change to a commit id.  It seems to
> me this is done for the reproducible builds concept.  Tags are mutable, and
> therefore could be changed and rebuilding a tag could give you a different
> result.
> 
> So, is this the right understanding? Do we want to ask podlings to always
> submit a git commit id?  If so, is there a place in the website we can
> clarify this?
> 
> Thanks,
> 
> John


signature.asc
Description: Digital signature

Re: Volunteer to Shepherd

[Marvin Humphrey]

On Thu, Dec 18, 2014 at 7:33 PM, P. Taylor Goetz  wrote:

> I’d like to volunteer to help out as a shepherd.

Super! I hope you find the experience broadening.

> I’ve taken the liberty of adding myself to shepherds.json file.

Extra bonus JFDI points!!

Marvin Humphrey

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

Volunteer to Shepherd

[P. Taylor Goetz]

Dear IPMC members,

I’d like to volunteer to help out as a shepherd. 

I’ve taken the liberty of adding myself to shepherds.json file.  If there are 
any objections, feel free to revert the commit.

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

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

[Reto Gmür]

On Thu, Dec 18, 2014 at 4:28 PM, Sam Ruby  wrote:
>
> On 12/18/2014 11:16 AM, Marko Rodriguez wrote:
>
>> 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.
>>
>
> Let's split that into two pieces.
>
> Git is a DVCS, which means that it can be at multiple places.  Using git
> for source control is an accepted practice at the ASF now.  GitHub can be
> one of the places.
>

The important aspect I think is that the one who pushes should endorse all
new commits including those by other developers. Automatically transferring
code from another place could only be an option if it can be ensured that
only committers can be push to that repository.

>From the ASF perspective, GitHub is a mirror.  From GitHub's perspective,
> the ASF is a mirror.
>
> None of this means that you can't use pull requests.  Examples:
>
> https://github.com/apache/spark/pulls
> https://github.com/deltacloud/deltacloud-core/pulls
> https://github.com/apache/camel/pulls
>
> (These just happen to be the top three hits on a Google search for "apache
> github pull requests").
>

I don't find an example for "apache github issues", I guess infra could
enable it. A problem with allowing Github issues is how to close them when
no commit would otherwise be needed (as in WONT FIX). I don't know how this
is done for pull-requests that are not accepted.

Cheers,
Reto


>
>  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.
>>
>
> The current tinkerpop mailing lists are indeed quite active.  I believe it
> would be possible for an ASF mailing list to be subscribed to each of these
> and satisfy ASF requirements in this manner.
>
>  Thoughts?,
>> Marko.
>>
>
> - Sam Ruby
>
>  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 
 wrote:

  No way, Marko! This is AWESOME!!
>
> As many people had mentioned before, you need Champion who is Apache
>
 member and mentors who are member of Incubator PMCs.

>
> And please do follow the format of the proposal as Hadrian mentioned in
>
 his reply.

>
> So excited!
>
> - Henry
>



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

Fwd: [CANCEL][VOTE] make PPMC == committers

[jan i]

No vote should be made without the full backing and understanding of the
community.

See below.

rgds
jan I.

Ps. I do think we have a podling
-- Forwarded message --
From: jan i 
Date: 18 December 2014 at 19:09
Subject: Re: [CANCEL][VOTE] make PPMC == committers
To: "priv...@corinthia.incubator.apache.org" <
priv...@corinthia.incubator.apache.org>

Hi

Relevant and severe concern about the content of vote and the following
implicantions have been raised, including -1 with a (in my opinion) valid
reason.

Therefore the vote is cancelled, and I will start a discussion on dev@ how
the PPMC works should be discussed by the full community, of course not
violating the bylaws of asf.

It seems the words I used have not been clear enough, so I will reformulate
the vote for the discussion, making clear we do NOT change any voting rules
(which to a large extend is something we cannot do).

Thanks to those who have replied.

rgds
jan i.


<--- REMOVED corinthia private list content -->

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

[Rob Vesse]

To clarify on Daniel's comments this does not mean that pull requests
cannot be merged

You can have Infra set up ASF integration with GitHub such that pull
requests trigger emails to your projects dev list, those emails contain
instructions on how to pull and merge the request into your local ASF
based working copy.  You then simply push to the ASF repo and if you've
said "Closes #1" (or whatever the exact wording is - again the email tells
you) then the pull request is automatically closed over on GitHub

See 
https://blogs.apache.org/infra/entry/improved_integration_between_apache_an
d

As for moving other infrastructure the Jena project (which I am involved
in) went through a similar exercise of migrating large amounts of external
infrastructure to the ASF when moving to the ASF and the Jena project.
Yes it was painful for a time but it is worth doing and as others have
pointed out there are sound reasons behind it.

It is really not that hard to migrate a mailing list from one platform to
another in our experience.  In the Jena project we kept the external
mailing lists open for the first 6 months or so and just sent regular
reminders asking people to move to the ASF mailing lists.  After that
period we closed the external list to new subscriptions and continued
sending the regular reminders for another 6 months or so, after that we
closed the external list entirely to new posts so it served only as a
historical archive.  Over time this allowed us to gracefully migrate users
to the new infrastructure by giving them plenty of notice and information
about what was happening and this didn't require huge amounts of effort on
our part.

Rob

On 18/12/2014 16:36, "Daniel Gruno"  wrote:

>
>On 2014-12-18 17:28, Sam Ruby wrote:
>> On 12/18/2014 11:16 AM, Marko Rodriguez wrote:
>>> 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.
>>
>> Let's split that into two pieces.
>>
>> Git is a DVCS, which means that it can be at multiple places. Using
>> git for source control is an accepted practice at the ASF now.  GitHub
>> can be one of the places.
>>
>> From the ASF perspective, GitHub is a mirror.  From GitHub's
>> perspective, the ASF is a mirror.
>No, from GitHub's perspective, ASF is the canonical source. There is no
>way to twist this into anything else.
>It says right on every single Apache GitHub mirror that it is "Mirrored
>from http://git.apache.org/...";.
>
>You cannot merge pull requests from GitHub via GitHub, that's simply not
>going to work, and it should be plenty clear to everyone by now why that
>is the case.
>
>With regards,
>Daniel.
>>
>> None of this means that you can't use pull requests.  Examples:
>>
>> https://github.com/apache/spark/pulls
>> https://github.com/deltacloud/deltacloud-core/pulls
>> https://github.com/apache/camel/pulls
>>
>> (These just happen to be the top three hits on a Google search for
>> "apache github pull requests").
>>
>>> 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.
>>
>> The current tinkerpop mailing lists are indeed quite active.  I
>> believe it would be possible for an ASF mailing list to be subscribed
>> to each of these and satisfy ASF requirements in this manner.
>>
>>> Thoughts?,
>>> Marko.
>>
>> - Sam Ruby
>>
>>> 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,
>
>

Re: [Proposal] TinkerPop: A Graph Computing Framework

[David Nalley]

On Thu, Dec 18, 2014 at 11:36 AM, Daniel Gruno  wrote:
>
> On 2014-12-18 17:28, Sam Ruby wrote:
>>
>> On 12/18/2014 11:16 AM, Marko Rodriguez wrote:
>>>
>>> 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.
>>
>>
>> Let's split that into two pieces.
>>
>> Git is a DVCS, which means that it can be at multiple places. Using git
>> for source control is an accepted practice at the ASF now.  GitHub can be
>> one of the places.
>>
>> From the ASF perspective, GitHub is a mirror.  From GitHub's perspective,
>> the ASF is a mirror.
>
> No, from GitHub's perspective, ASF is the canonical source. There is no way
> to twist this into anything else.
> It says right on every single Apache GitHub mirror that it is "Mirrored from
> http://git.apache.org/...";.
>
> You cannot merge pull requests from GitHub via GitHub, that's simply not
> going to work, and it should be plenty clear to everyone by now why that is
> the case.
>

Because people new to the ASF won't be familiar I'll reiterate the
some of the infra concerns issues:

The ASF cares deeply about (and has a responsibility to deal with)
code provenance. The committer and author records in git itself are
relatively fungible, so the canonical record is the push records that
record when, what account, what IP address, etc. At present, Github
does not expose those, and has expressed concerns about privacy issues
in exposing those records to us. We have discussed with them multiple
times the issues that we see as a concern, and we haven't yet found a
way to overcome them.

Other folks have other concerns - but that's the current 'big issue'
from an infrastructure perspective. (there are others like
programmatically managing access control to hundreds of repos that
isn't tied to our authn/z systems, getting real commit messages, etc.
- but that's likely something that could be conquered. )

We also realize that Github is huge locus for developers, and
particularly developers working on OSS. To that end, we maintain
mirrors on github, and a number of projects make use of pull requests
and issues in the workflow, and to non-committers it gives the
appearance that everything happens on Github. (and in reality 90%
does). We have built API interaction to capture PR comments and other
actions and send those on to a mailing list - so that we retain a
history of all of that information locally. (Github has no real SLA to
open source projects who get services for free, and there's important
provenance information in PRs, tickets, comments as well)

Every few months this comes up - and from a pragmatic side,
Infrastructure would love to 'outsource' maintaining a git service to
someone who offers an incredibly nice service and does so for free;
but we haven't solved all of the problems that go along with it.

In general, moving project websites, mailing lists, and revision
control to the ASF is not negotiable. Most of the other aspects the
project can make decisions on themselves. If you have concerns or
questions, I am sure folks like Sam can answer them all, but I am
happy to make myself available to talk through things with you.

--David

-
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

[Ross Gardler (MS OPEN TECH)]

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 
>> wrote:
>> 
>>> No way, Marko! This is AWESOME!!
>>> 
>>> As many people had mentioned before, you need Champion who is Apache
>> member and mentors who are member of Incubator PMCs.
>>> 
>>> And please do follow the format of the proposal as Hadrian mentioned 
>>> in
>> his reply.
>>> 
>>> So excited!
>>> 
>>> - Henry
>> 
>> 


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

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

[Richard Downer]

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

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Daniel Gruno]

On 2014-12-18 17:28, Sam Ruby wrote:

On 12/18/2014 11:16 AM, Marko Rodriguez wrote:

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.


Let's split that into two pieces.

Git is a DVCS, which means that it can be at multiple places. Using 
git for source control is an accepted practice at the ASF now.  GitHub 
can be one of the places.


From the ASF perspective, GitHub is a mirror.  From GitHub's 
perspective, the ASF is a mirror.
No, from GitHub's perspective, ASF is the canonical source. There is no 
way to twist this into anything else.
It says right on every single Apache GitHub mirror that it is "Mirrored 
from http://git.apache.org/...";.


You cannot merge pull requests from GitHub via GitHub, that's simply not 
going to work, and it should be plenty clear to everyone by now why that 
is the case.


With regards,
Daniel.


None of this means that you can't use pull requests.  Examples:

https://github.com/apache/spark/pulls
https://github.com/deltacloud/deltacloud-core/pulls
https://github.com/apache/camel/pulls

(These just happen to be the top three hits on a Google search for 
"apache github pull requests").



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.


The current tinkerpop mailing lists are indeed quite active.  I 
believe it would be possible for an ASF mailing list to be subscribed 
to each of these and satisfy ASF requirements in this manner.



Thoughts?,
Marko.


- Sam Ruby


http://markorodriguez.com

On Dec 17, 2014, at 7:42 PM, Jake Farrell mailto:jfarr...@apache.org>> 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 mailto:okramma...@gmail.com>>
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 
wrote:


No way, Marko! This is AWESOME!!

As many people had mentioned before, you need Champion who is Apache

member and mentors who are member of Incubator PMCs.


And please do follow the format of the proposal as Hadrian 
mentioned in

his reply.


So excited!

- Henry







-
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

[Sam Ruby]

On 12/18/2014 11:16 AM, Marko Rodriguez wrote:

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.


Let's split that into two pieces.

Git is a DVCS, which means that it can be at multiple places.  Using git 
for source control is an accepted practice at the ASF now.  GitHub can 
be one of the places.


From the ASF perspective, GitHub is a mirror.  From GitHub's 
perspective, the ASF is a mirror.


None of this means that you can't use pull requests.  Examples:

https://github.com/apache/spark/pulls
https://github.com/deltacloud/deltacloud-core/pulls
https://github.com/apache/camel/pulls

(These just happen to be the top three hits on a Google search for 
"apache github pull requests").



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.


The current tinkerpop mailing lists are indeed quite active.  I believe 
it would be possible for an ASF mailing list to be subscribed to each of 
these and satisfy ASF requirements in this manner.



Thoughts?,
Marko.


- Sam Ruby


http://markorodriguez.com

On Dec 17, 2014, at 7:42 PM, Jake Farrell mailto:jfarr...@apache.org>> 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 mailto:okramma...@gmail.com>>
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 
wrote:


No way, Marko! This is AWESOME!!

As many people had mentioned before, you need Champion who is Apache

member and mentors who are member of Incubator PMCs.


And please do follow the format of the proposal as Hadrian mentioned in

his reply.


So excited!

- Henry







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

RE: Votes for git repos - commit id vs tag

[Dennis E. Hamilton]

+1 on including commit ID (or SVN revision number) along with any tag (or SVN 
tag/branch) for convenience.

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Thursday, December 18, 2014 05:58
To: general@incubator.apache.org
Subject: Votes for git repos - commit id vs tag

All,

I was looking through the incubator site and I don't see anything definite.

Whenever a podling goes for a vote, and they include a git tag in their
vote message, it's typically asked to change to a commit id.  It seems to
me this is done for the reproducible builds concept.  Tags are mutable, and
therefore could be changed and rebuilding a tag could give you a different
result.

So, is this the right understanding? Do we want to ask podlings to always
submit a git commit id?  If so, is there a place in the website we can
clarify this?

Thanks,

John


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

Re: Votes for git repos - commit id vs tag

[jan i]

On Thursday, December 18, 2014, John D. Ament  wrote:

> All,
>
> I was looking through the incubator site and I don't see anything definite.
>
> Whenever a podling goes for a vote, and they include a git tag in their
> vote message, it's typically asked to change to a commit id.  It seems to
> me this is done for the reproducible builds concept.  Tags are mutable, and
> therefore could be changed and rebuilding a tag could give you a different
> result.
>
> So, is this the right understanding? Do we want to ask podlings to always
> submit a git commit id?  If so, is there a place in the website we can
> clarify this?


+1 to using git commit id. we have a guide for podling releases that would
be a good place.

rgds
jan i

>
> Thanks,
>
> John
>


-- 
Sent from My iPad, sorry for any misspellings.

Re: [Proposal] TinkerPop: A Graph Computing Framework

[Marko Rodriguez]

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 
>> wrote:
>> 
>>> No way, Marko! This is AWESOME!!
>>> 
>>> As many people had mentioned before, you need Champion who is Apache
>> member and mentors who are member of Incubator PMCs.
>>> 
>>> And please do follow the format of the proposal as Hadrian mentioned in
>> his reply.
>>> 
>>> So excited!
>>> 
>>> - Henry
>> 
>> 

Votes for git repos - commit id vs tag

[John D. Ament]

All,

I was looking through the incubator site and I don't see anything definite.

Whenever a podling goes for a vote, and they include a git tag in their
vote message, it's typically asked to change to a commit id.  It seems to
me this is done for the reproducible builds concept.  Tags are mutable, and
therefore could be changed and rebuilding a tag could give you a different
result.

So, is this the right understanding? Do we want to ask podlings to always
submit a git commit id?  If so, is there a place in the website we can
clarify this?

Thanks,

John

Re: Release procedures for a newly graduated podling

[Bertrand Delacretaz]

Hi,

On Thu, Dec 18, 2014 at 12:24 PM, Stephan Ewen  wrote:
> ...We are preparing a new release just now and are unsure which protocols to
> follow, because we are somewhat in between incubation and TLP now (the
> infrastructure is still set up for an incubator podling):...

You are a TLP indeed, this is effective as soon as the board approves
the resolution, which we did yesterday.

So go ahead and release like a TLP would - if your infrastructure is
not moved yet that might get in the way for some things, but there's
no need for DISCLAIMER or Incubator PMC approval anymore.

Happy TLPing!

-Bertrand

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

Release procedures for a newly graduated podling

[Stephan Ewen]

Hello!

The Apache Flink project has just been graduated by the board (we are very
excited about this and celebrating today :-) ).

We are preparing a new release just now and are unsure which protocols to
follow, because we are somewhat in between incubation and TLP now (the
infrastructure is still set up for an incubator podling):

  - Should we follow the procedures of an incubator podling, where the IPMC
must approve the release, and all artifacts contain the "incubating"
keyword, the release the the DISCLAIMER file, ...?

  - Or should we drop the "incubating" keyword, DISCLAIMER not give the
release candidate to the IPMC for approval?

Thanks for helping us!

Greetings,
Stephan

[RESULT][VOTE] accept corinthia into incubator

[jan i]

Sorry for the noise, seems I closed the vote in a new thread.

rgds
jan i.


On 7 December 2014 at 16:17, Daniel Gruno  wrote:
>
> +1 (binding)
>
> I believe the critical questions by ipmc members have been answered.
>
> On 2014-12-02 18:25, jan i wrote:
>
>> +1 (binding)
>>
>> rgds
>> jan i.
>>
>> On 2 December 2014 at 18:08, jan i  wrote:
>>
>>  Hi
>>>
>>> As champion for corinthia, I hereby ask for a vote on accepting corinthia
>>> into incubator.
>>>
>>> It seems the discussion have died out, in reality most of the discussion
>>> has been through private mails and IRC/hipchat (which disturbes me). As a
>>> result the proposal is now more clear about what the project is and what
>>> it
>>> isnt.
>>>
>>> We have added a committer and a mentor during the discussion period.
>>>
>>> The proposal is available in
>>> http://wiki.apache.org/incubator/CorinthiaProposal
>>> >> >
>>>
>>> Remark the vote is for revision #60 (the newest).
>>> Proposal is added as text to the bottom of this mail.
>>>
>>> Please vote
>>> +1 for accepting corinthia into incubator
>>> 0 for dont care
>>> -1 for not accepting corinthia into incubator (please add a reason).
>>>
>>> Vote is open until Sunday december 7, 23:30 UTC. If needed the period can
>>> be prolonged.
>>>
>>> Thanks for your vote.
>>> on behalf of project corinthia
>>> jan i.
>>>
>>>
>>> = PROPOSAL TEXT ===
>>>
>>> #pragma section-numbers 2
>>>
>>> = Corinthia Podling Proposal =
>>>
>>> == Abstract ==
>>>
>>> Corinthia is a toolkit for converting between and editing common office
>>> file formats, with an initial focus on word processing. It is designed to
>>> cater for multiple classes of platforms - desktop, web, and mobile - and
>>> relies heavily on web technologies such as HTML, CSS, and JavaScript for
>>> representing and manipulating documents. The toolkit is small, portable,
>>> and flexible, with minimal dependencies. The target audience is
>>> developers
>>> wishing to include office viewing, conversion, and editing functionality
>>> into their applications.
>>>
>>> The file format conversion library is implemented in highly-portable C,
>>> and can be easily embedded in native applications, with bindings for
>>> other
>>> programming languages planned. The library allows two-way conversion
>>> between different formats, and avoids irreversible loss of content or
>>> formatting unsupported in a target format by updating the source format
>>> in
>>> a way that makes only the minimal changes necessary.
>>>
>>> The editing library is implemented in Java''Script, and runs in a
>>> browser runtime - either an actual web browser, or a web view
>>> embedded in a native app. It follows the philosophy of responsive design,
>>> popular on the web, where layout of a document is automatically adapted
>>> to
>>> suit the screen size and orientation, enabling the same content to be
>>> viewed on mobile phones, tablets, and desktop systems. All layout is
>>> handled by the browser's own engine; the editor works solely with the
>>> document's HTML structure and CSS styles. Currently the editor only
>>> operates in an embedded web view, but we plan to have it run in all major
>>> web browsers, and provide a clean API for easy integration into various
>>> native apps.
>>>
>>> Importantly, Corinthia document viewing and editing is on the
>>> intermediate
>>> form (HTML & CSS), limited to common, widely-supported features.
>>> Corinthia
>>> is not a comprehensive substitute for format-specific authoring, editing,
>>> and final-form printing/production software. It is intended to
>>> complement,
>>> not compete with, major office suites.
>>>
>>> Identification and confirmation of inter-convertible features of
>>> different
>>> formats for dependable import and export involves development of
>>> extensive
>>> test documents in the different formats.  There is profiling of the
>>> extent
>>> to which standardized formats are supported in practice, with
>>> identification of deviations and implementation-dependent choices that
>>> impact convertibility.
>>>
>>> == Proposal ==
>>>
>>> The goal of Corinthia is to provide a responsive design editor as well as
>>> a toolkit that enacts a defined conversion between different office
>>> document formats. Responsive design fits the layout as needed, tablet or
>>> desktop. The editor is a lightweight editor - an extension and not a
>>> replacement for the desktop editor.
>>>
>>> Many office document programs claim to read/write to the ISO open
>>> standards for office documents, Open''Document Format (ODF) and
>>> Office
>>> Open XML (OOXML), but do not document which parts are left unimplemented.
>>> Furthermore, the standards have a large number of "implementation
>>> defined"
>>> parts, making real-world congruence chancy. The Corinthia toolkit wants
>>> to
>>> put this unacknowledged aspect into the open and provide "compliance
>>> sheets" for