[RESULT][VOTE] Graduate Apache Hop as TLP

2021-12-08 Thread Bart Maertens
Hi All,

The vote to graduate Apache Hop as a TLP is now closed.

The results of the voting are listed below:

Binding votes: 6 +1 votes, no 0 or -1 votes.
- Julian Hyde
- Kevin Ratnasekera
- Dave Fisher
- Francois Papon
- Furkan Kamaci
- Willem Jiang

Non binding: 4 +1 votes, no 0 or -1 votes
- Goson zhang
- Kent Yao
- Zhang Yonglun
- Young Seung (Andrew) Ko

The [VOTE] thread can be found at [1].

Please let us know if any next steps in the graduating process are required
before the resolution can be submitted to the board [2].

[1] https://lists.apache.org/thread/zt1yg1ozjs9chlr9gxmvml1r4ys4gjqn
[2]
https://incubator.apache.org/guides/graduation.html#submission_of_the_resolution_to_the_board

Regards,
Bart


Re: [VOTE] Graduate Apache Hop (Incubating) as a TLP

2021-12-08 Thread Bart Maertens
Thanks, everyone! This vote is now closed.
We'll send out the vote results in a new email.

Regards,
Bart



On Wed, Dec 8, 2021 at 11:05 AM Andrew Ko  wrote:

> +1 (non-binding)
>
> Good luck !!
>
> On Wed, Dec 8, 2021 at 4:44 PM Willem Jiang 
> wrote:
>
> > +1 (binding).
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Dec 3, 2021 at 2:38 AM Bart Maertens 
> > wrote:
> > >
> > > Hi Incubator Community,
> > >
> > > After a discussion[1] with and vote by[2] the Hop community, we have
> > > discussed Apache Hop's graduation in the general@incubator [DISCUSS]
> > > thread[3], where no major issues were raised.
> > >
> > > With no objections brought up in the discussion, we would like to
> proceed
> > > with the voting process.
> > >
> > > Here is the official request to vote to graduate the Apache Hop project
> > as
> > > a TLP.
> > >
> > > Please provide your vote as one of the following options:
> > >
> > > [ ] +1 - Recommend graduation of Apache Hop as a TLP
> > >
> > > [ ]  0 - I don't feel strongly about it, but don't object
> > >
> > > [ ] -1 - Do not recommend the graduation of Apache Hop because…
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > The Hop community achievements since Hop joined the Incubator in
> > September
> > > 2020:
> > > - over 3200 commits by 28 contributors
> > > - 4 releases (0.60, 0.70, 0.99, 1.0)
> > > - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers
> (mentors
> > > and PPMC members excluded)
> > > - diverse committers and PPMC, with regular contributions from at
> least 5
> > > different companies/institutes
> > > - Apache Hop website[4]
> > > - dev conversations at d...@hop.apache.org
> > > - assessed ourselves against the Apache Project maturity matrix[5] and
> > > didn't find any issues.
> > >
> > >
> > > [1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
> > > [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> > > [3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
> > > [4] https://hop.incubator.apache.org/
> > > [5] https://hop.apache.org/community/incubator/
> > >
> > > 
> > >
> > > Establish the Apache Hop Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > a Project Management Committee charged with the creation and
> maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a platform for data orchestration.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Hop Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Hop Project be and hereby is responsible for
> > > the creation and maintenance of software related to a platform for data
> > > orchestration; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> > > have primary responsibility for management of the projects within the
> > > scope of responsibility of the Apache Hop 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 Hop Project:
> > >
> > > * Bart Maertens 
> > > * Brandon Jackson 
> > > * Dave Campen 
> > > * Francois Papon 
> > > * Hans Van Akelyen 
> > > * Julian Hyde 
> > > * Kevin Ratnasekera 
> > > * Matt Casters 
> > > * Nicolas Adment 
> > > * Sergio Ramazzina 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> > > appointed to the office of Vice President, Apache Hop, to serve in
> > > accordance with and subject to the direction of the Board of Directors
> > > and the Bylaws of the Foundation until

Re: [VOTE] Graduate Apache Hop (Incubating) as a TLP

2021-12-02 Thread Bart Maertens
Hi Julian,

I missed that, my apologies.
This vote is now closed, a new vote[1] is started

[1] https://lists.apache.org/thread/zt1yg1ozjs9chlr9gxmvml1r4ys4gjqn

Regards,
Bart

On Thu, Dec 2, 2021 at 6:01 PM Julian Hyde  wrote:

> Bart,
>
> The typo in the resolution that (I believe) Sebb pointed out is still
> present. In the following, “A” should be “a” and “.” should be deleted:
>
> > RESOLVED, that the Apache Hop Project be and hereby is responsible for
> > the creation and maintenance of software related to A platform for data
> > orchestration.; and be it further
>
>
> Can you please fix it and re-start the vote?
>
> Julian
>
> > On Dec 2, 2021, at 5:57 AM, Bart Maertens  wrote:
> >
> > Hi Incubator Community,
> >
> > After a discussion[1] with and vote by[2] the Hop community, we have
> > discussed Apache Hop's graduation in the general@incubator [DISCUSS]
> thread
> > [3], where no major issues were raised.
> >
> > With no objections brought up in the discussion, we would like to proceed
> > with the voting process.
> >
> > Here is the official request to vote to graduate the Apache Hop project
> as
> > a TLP.
> >
> > Please provide your vote as one of the following options:
> >
> > [ ] +1 - Recommend graduation of Apache Hop as a TLP
> >
> > [ ]  0 - I don't feel strongly about it, but don't object
> >
> > [ ] -1 - Do not recommend the graduation of Apache Hop because…
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > To summarize a few of the community's achievements:
> >
> > The Hop community achievements since Hop joined the Incubator in
> September
> > 2020:
> > - over 3200 commits by 28 contributors
> > - 4 releases (0.60, 0.70, 0.99, 1.0)
> > - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
> > and PPMC members excluded)
> > - diverse committers and PPMC, with regular contributions from at least 5
> > different companies/institutes
> > - Apache Hop website[4]
> > - dev conversations at d...@hop.apache.org
> > - assessed ourselves against the Apache Project maturity matrix[5] and
> > didn't find any issues.
> >
> >
> > [1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
> > [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> > [3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
> > [4] https://hop.incubator.apache.org/
> > [5] https://hop.apache.org/community/incubator/
> >
> > 
> >
> > Establish the Apache Hop Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a platform for data orchestration.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Hop Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Hop Project be and hereby is responsible for
> > the creation and maintenance of software related to A platform for data
> > orchestration.; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> > have primary responsibility for management of the projects within the
> > scope of responsibility of the Apache Hop 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 Hop Project:
> >
> > * Bart Maertens 
> > * Brandon Jackson 
> > * Dave Campen 
> > * Francois Papon 
> > * Hans Van Akelyen 
> > * Julian Hyde 
> > * Kevin Ratnasekera 
> > * Matt Casters 
> > * Nicolas Adment 
> > * Sergio Ramazzina 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> > appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
> > migration and rationalization of the Apache Incubator Hop podling; and
> > be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Hop podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


[VOTE] Graduate Apache Hop (Incubating) as a TLP

2021-12-02 Thread Bart Maertens
Hi Incubator Community,

After a discussion[1] with and vote by[2] the Hop community, we have
discussed Apache Hop's graduation in the general@incubator [DISCUSS]
thread[3], where no major issues were raised.

With no objections brought up in the discussion, we would like to proceed
with the voting process.

Here is the official request to vote to graduate the Apache Hop project as
a TLP.

Please provide your vote as one of the following options:

[ ] +1 - Recommend graduation of Apache Hop as a TLP

[ ]  0 - I don't feel strongly about it, but don't object

[ ] -1 - Do not recommend the graduation of Apache Hop because…

The VOTE will remain open for at least 72 hours.

The Hop community achievements since Hop joined the Incubator in September
2020:
- over 3200 commits by 28 contributors
- 4 releases (0.60, 0.70, 0.99, 1.0)
- 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
and PPMC members excluded)
- diverse committers and PPMC, with regular contributions from at least 5
different companies/institutes
- Apache Hop website[4]
- dev conversations at d...@hop.apache.org
- assessed ourselves against the Apache Project maturity matrix[5] and
didn't find any issues.


[1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
[2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
[3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
[4] https://hop.incubator.apache.org/
[5] https://hop.apache.org/community/incubator/



Establish the Apache Hop Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a platform for data orchestration.

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

RESOLVED, that the Apache Hop Project be and hereby is responsible for
the creation and maintenance of software related to a platform for data
orchestration; and be it further

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

* Bart Maertens 
* Brandon Jackson 
* Dave Campen 
* Francois Papon 
* Hans Van Akelyen 
* Julian Hyde 
* Kevin Ratnasekera 
* Matt Casters 
* Nicolas Adment 
* Sergio Ramazzina 

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

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


[VOTE] Graduate Apache Hop (Incubating) as a TLP

2021-12-02 Thread Bart Maertens
Hi Incubator Community,

After a discussion[1] with and vote by[2] the Hop community, we have
discussed Apache Hop's graduation in the general@incubator [DISCUSS] thread
[3], where no major issues were raised.

With no objections brought up in the discussion, we would like to proceed
with the voting process.

Here is the official request to vote to graduate the Apache Hop project as
a TLP.

Please provide your vote as one of the following options:

[ ] +1 - Recommend graduation of Apache Hop as a TLP

[ ]  0 - I don't feel strongly about it, but don't object

[ ] -1 - Do not recommend the graduation of Apache Hop because…

The VOTE will remain open for at least 72 hours.

To summarize a few of the community's achievements:

The Hop community achievements since Hop joined the Incubator in September
2020:
- over 3200 commits by 28 contributors
- 4 releases (0.60, 0.70, 0.99, 1.0)
- 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
and PPMC members excluded)
- diverse committers and PPMC, with regular contributions from at least 5
different companies/institutes
- Apache Hop website[4]
- dev conversations at d...@hop.apache.org
- assessed ourselves against the Apache Project maturity matrix[5] and
didn't find any issues.


[1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
[2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
[3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
[4] https://hop.incubator.apache.org/
[5] https://hop.apache.org/community/incubator/



Establish the Apache Hop Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a platform for data orchestration.

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

RESOLVED, that the Apache Hop Project be and hereby is responsible for
the creation and maintenance of software related to A platform for data
orchestration.; and be it further

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

* Bart Maertens 
* Brandon Jackson 
* Dave Campen 
* Francois Papon 
* Hans Van Akelyen 
* Julian Hyde 
* Kevin Ratnasekera 
* Matt Casters 
* Nicolas Adment 
* Sergio Ramazzina 

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

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


Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-11-30 Thread Bart Maertens
Thanks for your input, Julian and Bertrand!
Unless there's anything else that needs to be discussed, I guess we can
close this [DISCUSS] thread, start a vote to graduate Hop without Ricardo
on the PMC, and vote him in after graduation.

Regards,
Bart

On Mon, Nov 29, 2021 at 9:14 PM Julian Hyde  wrote:

> Thanks for doing the research, Bertrand. That thread describes a case
> (from 2019) that is virtually identical to this one.
>
> I recommend Hop does the same as that case: remove that person’s name from
> the resolution, and vote them in as a PMC member after graduating. Since
> the effect is the same, they can do that without requiring a vote on
> dev@hop.
>
> For the record, my reading of the thread is that resolutions MAY include
> non-Apache people but the candidate project removed the non-Apache people
> from the resolution in order to accommodate limitations in the tooling.
>
> Julian
>
>
> > On Nov 29, 2021, at 9:12 AM, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
> >
> > Hi,
> >
> > On Mon, Nov 29, 2021 at 5:56 PM Julian Hyde 
> wrote:
> >> ...Let’s just assume that it’s OK to include people with non-Apache
> email addresses in the graduation resolution...
> >
> > I don't think that's the case, in previous similar cases Board members
> > asked for the resolutions to be modified to avoid including non-apache
> > email addresses [1].
> >
> > it's very easy for the PMC to fix that as soon as it's created, by
> > voting in the "missing" member. To me that's the safe option here.
> >
> > -Bertrand
> >
> > [1] https://lists.apache.org/thread/v7b1l27zf1xbkm45y8ryzs6pc0dwcl9g
> > (accessible to PMC chairs and ASF Members)
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-11-26 Thread Bart Maertens
Do I get it correctly that the announcements on the users and dev lists are
mainly advice for future releases?
There's not a lot we can do about previous releases at this point, there
doesn't seem to be any documentation about release announcements, and this
feedback was never brought up when we went through the release process for
the (4!) releases we did.

Regarding Ricardo Gouvea as a PMC member who currently is not a committer:
Sebbs feedback conflicts with the advice from our mentor Julian.
Can the IPMC point us to any documentation that states all initial PMC
members need to be podling committers, can we onboard Ricardo when the PMC
is established, or can you clarify the correct approach to handle this?

Regards,
Bart



On Fri, Nov 26, 2021 at 3:54 PM sebb  wrote:

> On Fri, 26 Nov 2021 at 14:35, Matt Casters
>  wrote:
> >
> > We're simply following the advice given here and by our mentors.  We
> didn't
> > send an announcement mail in the beginning and then we did based on your
> > valuable feedback.   If we need to copy the announcement of our releases
> to
> > other mailing lists we can easily do so.
>
> It is important to let users and developers know as well.
> They may not be subscribed to the general announce list.
> BTW, for the developer Hop list, a more detailed email may be appropriate.
>
> Also you have not addressed the issue of the non-ASF committer.
> I suspect there will be some issues with setting up the PMC if this is
> not fixed.
>
> >
> >
> >
> > On Fri, Nov 26, 2021 at 3:05 PM sebb  wrote:
> >
> > > On Fri, 26 Nov 2021 at 12:06, Matt Casters
> > >  wrote:
> > > >
> > > > Hi Sebb,
> > > >
> > > > Google found the announcement mails, for example [1] and [2].
> > >
> > > Not sure how I missed those.
> > > However, AFAICT they were not announced on general@incubator nor on
> > > any of the podling lists.
> > >
> > > > As for Ricardo: he is indeed not a committer (yet) but an advisor to
> the
> > > > project.  His insights as an educator have been very valuable and is
> in
> > > the
> > > > process of becoming a committer.  Our mentor Julian informed us that
> > > (and I
> > > > quote) "There’s no rule that the initial PMC can consist only of
> people
> > > who
> > > > were committers in the podling".
> > >
> > > That is rather different from including people who are not yet ASF
> > > committers.
> > >
> > > AFAIK, most of the Infra and Whimsy tooling assumes that PMC members
> > > have ASF ids.
> > >
> > > > All the best,
> > > > Matt
> > > >
> > > > [1]
> > > >
> > >
> http://mail-archives.apache.org/mod_mbox/www-announce/202108.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-9ff3db74f16d3e6f41d2f3ab4f35ecde94c43...@announce.apache.org%3E
> > > > [2]
> > > >
> > >
> http://mail-archives.apache.org/mod_mbox/www-announce/202110.mbox/%3cpony-5f4f7c3ea0e95da19b9d17390cc7ff00d42fdf75-03d88d76819f10519156908b4369a9b7e1979...@announce.apache.org%3E
> > > >
> > > >
> > > > On Fri, Nov 26, 2021 at 12:41 PM sebb  wrote:
> > > >
> > > > > On Fri, 26 Nov 2021 at 07:15, Bart Maertens  >
> > > wrote:
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > After a discussion[1] with and vote by[2] the Hop community, we
> > > believe
> > > > > > Apache Hop (Incubating) is ready
> > > > > > to graduate as a TLP, and we'd like to bring it up in discussion
> > > with the
> > > > > > IPMC.
> > > > > >
> > > > > > The Hop community achievements since Hop joined the Incubator in
> > > > > September
> > > > > > 2020:
> > > > > > - close to 3200 commits by 28 contributors
> > > > > > - 4 releases(0.60, 0.70, 0.99, 1.0)
> > > > >
> > > > > However, it looks like none of these releases was ever announced.
> > > > >
> > > > > I could not find announce emails on:
> > > > > general@incubator.a.o
> > > > > *@hop.a.o
> > > > > announce@apache.o
> > > > >
> > > > > Announcements are an important part of releases, so I would expect
> to
> > > > > find some examples.
> > > > >
> > > > > > - 5 mentors, 6 PPMC member

[DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-11-25 Thread Bart Maertens
Hi All,

After a discussion[1] with and vote by[2] the Hop community, we believe
Apache Hop (Incubating) is ready
to graduate as a TLP, and we'd like to bring it up in discussion with the
IPMC.

The Hop community achievements since Hop joined the Incubator in September
2020:
- close to 3200 commits by 28 contributors
- 4 releases(0.60, 0.70, 0.99, 1.0)
- 5 mentors, 6 PPMC members(mentors excluded) and 8 committers(mentors and
PPMC members excluded)
- diverse committers and PPMC, with regular contributions from at least 5
different companies/institutes
- Apache Hop website[3]
- dev conversations at d...@hop.apache.org
- assessed ourselves against the Apache Project maturity matrix[4] and
didn't find any issues.

The topics that were discussed in the earlier [DISCUSS] thread[5] have been
resolved:
- old releases have been cleaned up
- self-assessment is available[4]
- Whimsy licensing issue is WiP (licensing is ok, the missing yaml file was
added)
- project description in the resolution was rewritten
- an old pre-incubator website was removed[6]

[1]
https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
[2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
[3] https://hop.incubator.apache.org/
[4] https://hop.apache.org/community/incubator/
[5] https://lists.apache.org/thread/jj46blkwrhf0l31srtzo5j5dcv7zsqz3
[6] http://52.214.20.244

Please see the proposed board resolution below and let us know what you
think.

The discussion will remain open for at least 72 hours.

--

Establish the Apache Hop Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a platform for data orchestration.

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

RESOLVED, that the Apache Hop Project be and hereby is responsible for
the creation and maintenance of software related to A platform for data
orchestration.; and be it further

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

* Bart Maertens 
* Brandon Jackson 
* Dave Campen 
* Francois Papon 
* Hans Van Akelyen 
* Julian Hyde 
* Kevin Ratnasekera 
* Matt Casters 
* Nicolas Adment 
* Ricardo Gouvea 
* Sergio Ramazzina 

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

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


Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-10-28 Thread Bart Maertens
Hi Justin, All,

The server mentioned as [1] was an old test server that has been shut down.
The other issues mentioned earlier in this thread have been taken care of
as well.

We'll start a discussion about (P)PMC membership, do a community vote on
the graduation and start a new [DISCUSS] thread here.
Please let us know if there are any other steps or items we need to take
into account.

Regards,
Bart

[1] http://52.214.20.244


On Tue, Oct 19, 2021 at 8:16 AM Justin Mclean 
wrote:

> Hi,
>
> I look a look at the project and noticed some thing re the PMC makeup:
> - Some of your proposed PMC members are existing PPMC member but are not
> signed up to the project private mailing list
> - The project has not voted any PPMC members.
> - Could some of the existing committers be consider PMC members?
>
> I’m also curious to what is this site and why it exits? [1]
>
> Thanks,
> Justin
>
>
> 1. http://52.214.20.244
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-10-16 Thread Bart Maertens
Hi Julian, All,

The older release artifacts[1] are removed and the download page[2] is
updated. Only the latest 1.0 release is still available.
The missing hop.yml file[3] has been added.

We'll discuss and update the resolution description over the next few days.

We skipped the community vote because the graduation guide[4] mentions
"This VOTE is not a requirement but is recommended". We assumed the
positive feedback about graduation we got from our mentors in an earlier
thread on the dev mailing list[5] and in the context of the 1.0 release[6]
was sufficient.
We can of course still organize the vote if necessary.

[1] https://dist.apache.org/repos/dist/release/incubator/hop/
[2] https://hop.apache.org/download/
[3]
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/hop.yml
[4] https://incubator.apache.org/guides/graduation.html
[5]
https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
[6]
https://lists.apache.org/thread.html/ra12672123f1b20dd61de8146e670b4e0f00b00031658dd9a5271%40%3Cdev.hop.apache.org%3E

Regards,
Bart

On Sat, Oct 16, 2021 at 2:34 AM Julian Hyde  wrote:

> I agree with Craig; the description of the project in the resolution
> definitely needs some work.
>
> I noticed that the project has not held formal vote for graduation on
> dev@hop. I’ll remind the project that they need to have that vote before
> proceeding to a vote on general@incubator.
>
> Julian
>
>
> > On Oct 15, 2021, at 12:54 PM, Craig Russell 
> wrote:
> >
> > Hi,
> >
> > I'd strongly suggest that you improve the wording of the resolution
> "related to short for the Hop Orchestration Platform". It's barely
> parseable.
> >
> > Perhaps make it simpler by removing the entire text after "related to
> short for the Hop Orchestration Platform...easily used by other software"
> and replacing it with "related to Java-based data orchestration tools".
> >
> > Warm regards,
> > Craig
> >
> >> On Oct 15, 2021, at 3:02 AM, Bart Maertens  wrote:
> >>
> >> Hi All,
> >>
> >> After a discussion with the community[1], we believe Apache Hop
> (Incubating) is ready for graduation to a TLP, and we'd like to bring it up
> in discussion with the IPMC.
> >>
> >> The Hop community achievements since Hop joined the Incubator in
> September 2020:
> >>
> >> - over 3000 commits by 27 contributors
> >> - 4 releases (0.60, 0.70, 0.99, 1.0)
> >> - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers
> (mentors and PPMC members excluded)
> >> - diverse committers and PPMC, with regular contributions from at least
> 4 different companies/institutes
> >> - Apache Hop website[2]
> >> - dev conversations at d...@hop.apache.org
> >> - assessed ourselves against the Apache Project maturity matrix[3] and
> didn't find any issues.
> >>
> >> [1]
> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
> >> [2] https://hop.incubator.apache.org/
> >> [3]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> >>
> >> Please see the proposed board resolution below and let us know what you
> think.
> >>
> >> The discussion will remain open for at least 72 hours.
> >>
> >>
> -
> >>
> >> Establish the Apache Hop Project
> >>
> >> WHEREAS, the Board of Directors deems it to be in the best interests of
> >> the Foundation and consistent with the Foundation's purpose to establish
> >> a Project Management Committee charged with the creation and maintenance
> >> of open-source software, for distribution at no charge to the public,
> >> related to short for the Hop Orchestration Platform. Written completely
> >> in Java it aims to provide a wide range of data orchestration tools,
> >> including a visual development environment, servers, metadata analysis,
> >> auditing services and so on. As a platform, Hop also wants to be a
> >> reusable library so that it can be easily reused by other software.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Hop Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> >> the creation and maintenance of

[DISCUSS] Graduate Apache Hop (Incubating) as a TLP

2021-10-15 Thread Bart Maertens
Hi All, 

After a discussion with the community[1], we believe Apache Hop (Incubating) is 
ready for graduation to a TLP, and we'd like to bring it up in discussion with 
the IPMC.

The Hop community achievements since Hop joined the Incubator in September 
2020: 

- over 3000 commits by 27 contributors
- 4 releases (0.60, 0.70, 0.99, 1.0)
- 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors and 
PPMC members excluded)
- diverse committers and PPMC, with regular contributions from at least 4 
different companies/institutes
- Apache Hop website[2]
- dev conversations at d...@hop.apache.org 
- assessed ourselves against the Apache Project maturity matrix[3] and didn't 
find any issues.   

[1] 
https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
[2] https://hop.incubator.apache.org/
[3] https://community.apache.org/apache-way/apache-project-maturity-model.html

Please see the proposed board resolution below and let us know what you think.

The discussion will remain open for at least 72 hours.

-

Establish the Apache Hop Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to short for the Hop Orchestration Platform. Written completely
in Java it aims to provide a wide range of data orchestration tools,
including a visual development environment, servers, metadata analysis,
auditing services and so on. As a platform, Hop also wants to be a
reusable library so that it can be easily reused by other software.

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

RESOLVED, that the Apache Hop Project be and hereby is responsible for
the creation and maintenance of software related to short for the Hop
Orchestration Platform. Written completely in Java it aims to provide a
wide range of data orchestration tools, including a visual development
environment, servers, metadata analysis, auditing services and so on. As
a platform, Hop also wants to be a reusable library so that it can be
easily reused by other software; and be it further

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

 * Bart Maertens  
 * Brandon Jackson
 * Francois Papon 
 * Hans Van Akelyen   
 * Hiromu Hota
 * Julian Hyde
 * Kevin Ratnasekera  
 * Matt Casters   
 * Maximilian Michels 
 * Nicolas Adment 
 * Tom Barber 

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

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

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



Re: [VOTE] Release Apache Hop (incubating) 0.99-rc3

2021-06-21 Thread Bart Maertens
Hi Justin,

We only used a small part of the code (sql parsing) in that repository, and
that code has been removed.
A discussion[1] was started to replace the code that was removed with a new
implementation.

[1]:
https://lists.apache.org/thread.html/rfa656bd35ea5aa15c1ff51b3061a9f527f53cacd20f65f03922c32e0%40%3Cdev.hop.apache.org%3E

Regards,
Bart



On Mon, Jun 21, 2021 at 2:18 AM Justin Mclean 
wrote:

> Hi,
>
> This release has less changes than I expected. I thought the issue
> discussed in the last release involve 100 or 1000’s of files? Just checking
> - have all the files from that un-donated repo been removed?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-13 Thread Bart Maertens
Hi,

What I don't get about this whole discussion is that we already had 169 hpl
and hwf files in the 0.70 release, and these files weren't even mentioned
in the reviews.
Now that we have about 400 hpl/hwf files in the 0.99 release, this
is/becomes an issue.
I'm sure we'll sort this out, but if this was detected and discussed sooner
(0.70), that could have saved us all a lot of time, energy and, quite
frankly, frustration.

Maybe even more importantly, how do we know our current code base doesn't
have any other problems that may only pop up in future releases?

Regards,
Bart

On Sat, Jun 12, 2021 at 10:35 PM Matt Casters
 wrote:

> After thinking about it some more I really believe strongly that our
> developers should have an easy time adding more integration tests.  It's
> really critical to our project in the longer term.
> Manually editing XML files to copy/paste an ASF header in there can not be
> part of that experience.  It's simply out of the question.
> I don't see the same requirement for other Apache projects that have .avro
> or .parquet files as part of their test-suites.  The obvious reason being
> that folks are not really opening up these file formats with a text
> editor... just like we never do this with .hpl/.hwf files.  So we're just
> being punished for having chosen an XML format.
>
> Since we've exhausted all other possibilities I'll start the discussion on
> dev to move to a different file format for our metadata.
>
> All the best,
> Matt
>
> On Sat, Jun 12, 2021 at 2:09 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > I'm a little confused, and I may be missing some context here. If the
> work
> > a part of an ASF project, why do you need to include a copyright
> statements
> > anywhere? If the code is not part of the project then we do need to know
> > the license and copyright owner. While this might be a good place to
> > include it, it would still also need to go in the LICENSE file, so that a
> > duplication of work and something that could easily get out of sync.
> >
> > IMO (and there may be there ways of dealing with this) just get the
> > contributors to sign ICLAs so there no issue with their contributions and
> > there’s no issues with the contents of the LICENSE file or indeed
> licensing.
> >
> > Kind Regards,
> > Justin
>
>
>
> --
> Neo4j Chief Solutions Architect
> *✉   *matt.cast...@neo4j.com
> ☎  +32486972937
>


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-12 Thread Bart Maertens
Hi,

What Matt was pointing at is to include a  (or , but
let's forget about that for now) element in the XML documents that the hpl
and hwf files are.

We could do this by including an option in Hop Gui (our visual IDE that
generates the hpl and hwf files) to include the ASF header for the
integration test and sample hpl and hwf files.

Outside of our code repository, users could use that functionality to
include their own header or copyright to the hpl and hwf files they create.
Those files would never end up in our repository, so that is out of scope
for this discussion.

Regards,
Bart




On Sat, Jun 12, 2021 at 2:09 PM Justin Mclean 
wrote:

> Hi,
>
> I'm a little confused, and I may be missing some context here. If the work
> a part of an ASF project, why do you need to include a copyright statements
> anywhere? If the code is not part of the project then we do need to know
> the license and copyright owner. While this might be a good place to
> include it, it would still also need to go in the LICENSE file, so that a
> duplication of work and something that could easily get out of sync.
>
> IMO (and there may be there ways of dealing with this) just get the
> contributors to sign ICLAs so there no issue with their contributions and
> there’s no issues with the contents of the LICENSE file or indeed licensing.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [MENTORS] missing reports and signoffs

2021-01-10 Thread Bart Maertens
Hi Justin,

The Hop podling report is available and has been signed off by our mentors
[1].
Let me know if you need anything else from us.

[1]: https://cwiki.apache.org/confluence/display/INCUBATOR/January2021#hop

Regards,
Bart



On Mon, Jan 11, 2021 at 1:20 AM Justin Mclean 
wrote:

> Hi,
>
> The report will be submitted on Wednesday.
>
> The following reports are missing:
> BlueMarlin
> brpc
> Hop
> Livy
> PonyMail
> Wayang
> Weex
>
> The following still need mentor sign off:
> Liminal
> Milagro
> YuniKorn
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>