Hi all,
I also agree on 'A platform for data orchestration'
Cheers
Sergio
Il 15/11/2021 06:10, Julian Hyde ha scritto:
In my opinion, for mission statements, less is more. So I’m going to whittle
this down to the bone and y’all should holler if I take it too far.
So, some other ideas for what could go:
I’m glad you took out ‘implemented in Java’ (because we don’t want to prevent
ourselves from moving to other languages).
Take out 'visual development' (because it is implied by wanting to make the
tool approachable to all skill levels, and we don’t want to preclude
code-driven approaches).
Take out the origin of the name '(Hop Orchestration Platform)’. It’s history,
not mission.
Take out the ‘aims to’. As Yoda says, ’there is no try’.
Take out ‘complete’ (who wants an incomplete platform?)
I wouldn’t add a mention of plugins. All platforms support plugins!
I think that ’testing and deployment’ and ‘auditing’ are implied (somewhat) by
‘complex orchestration and lifecycle requirements'
So, we’re down to this:
Hop lets people of various skill levels
be productive in even the most complex data engineering and data
orchestration projects.
Hop is a platform that spans the entire project life cycle.
Wordsmithing gets this down to:
Hop is a platform for data engineering, easy for novice
users but scaling to projects with complex orchestration
and lifecycle requirements.
The text has to follow “related to”, so the above becomes
a tool and platform for data engineering, easy for novice
users but scaling to projects with complex orchestration
and lifecycle requirements
FWIW, Calcite’s mission statement was
parsing and planning queries on data in a
wide variety of formats
Hive’s was
parallel analysis of large data sets
Kafka’s was
a distributed publish/subscribe stream
processing framework
So, can we cut Hop’s statement down any further? Say
an intuitive and productive tool for data engineers
or
a platform for data orchestration
Julian
[1] https://whimsy.apache.org/board/minutes/Calcite.html#2015-10-21
<https://whimsy.apache.org/board/minutes/Calcite.html#2015-10-21>
[2] https://whimsy.apache.org/board/minutes/Hive.html#2010-09-22
<https://whimsy.apache.org/board/minutes/Hive.html#2010-09-22>
[3] https://whimsy.apache.org/board/minutes/Kafka.html#2012-11-21
<https://whimsy.apache.org/board/minutes/Kafka.html#2012-11-21>
On Nov 14, 2021, at 7:50 AM, Nicolas ADMENT <[email protected]> wrote:
Hi Bart,
The mission statement looks good! I would eventually just add the notion
that it can be easily customized with plugins.
*Hop is a complete and customizable platform that covers the entire project
life cycle.*
Cheers,
Nicolas
Le dim. 14 nov. 2021 à 08:44, Bart Maertens <[email protected]> a
écrit :
Hi All,
Any thoughts on this as an updated mission statement?
Hop (Hop Orchestration Platform) aims to let people of various skill levels
be productive in even the most complex data engineering and data
orchestration projects.
Hop aims to be a complete platform that spans the entire project life
cycle, from visual development over testing and deployment to auditing and
analysis.
Regards,
Bart
On Wed, Nov 10, 2021 at 9:06 PM Julian Hyde <[email protected]>
wrote:
The next step will be an internal vote to let the community decide if
they
think Apache Hop (Incubating) is ready to graduate as a Top Level
Project.
If I recall correctly, the vote is typically on the text of the
graduation
proposal. Included in that text are the initial PMC and chair (done) but
also the mission statement of the project. Formally, we need to agree the
values <Name> and <Mission statement> to substitute into the template.
Bart’s previous message to the IPMC had the variables <Name> = “Hop” and
<Mission statement> = "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.”
substituted into the template
Establish the Apache <Name> 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 clear mission statement>
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache <Name> Project", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED,that the Apache <Name> Project be and hereby is
responsible for the creation and maintenance of software
related to <same mission statement>.
RESOLVED, that the office of "Vice President, Apache <Name>" 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 <Name> Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache <Name> 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 <Name> Project:
<< here, list out each PMC member, in the format of
* First Last <apache email>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that <Elected VP> be
appointed to the office of Vice President, Apache <Name>, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache <Name> PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache <Name> Project; and be it further
RESOLVED, that the Apache <Name> Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
<Name> podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator <Name> podling encumbered upon the Apache Incubator
Project are hereafter discharged.
In my opinion the current mission statement is too long and should be
tightened up.
Julian
