GitHub user sramazzina added a comment to the discussion: 2.17 Roadmap and goals
Hi @dave-csc I agree with you that project inheritance is lacking of many
things and is one of the functionalities that we would like to seen completed.
I personally think, the same as you, that a complete set of project's objects
must be inherited and so pipelines and workflows. We tried to work on an custom
project's plugin version (I'm a fan of separated plugins to try to extend Hop
capabilities) trying to reach what you are asking for and what we really wanted
too and we reached interesting points (sorry for my bad english). But when we
come to the _"extended" ${PROJECT_HOME} folder_ concept (and we dived into that
struggling a lot on this) needed to inherit pipelines and workflows, it became
a more complicated thing with a deep impact on the core libraries that of
course wasn't possible.
I personally disagree on leveraging on Git capabilities to try to extend Hop
projects, with things like submodules. First of all because I personally love
the idea that this must happen without any technicality. The major our selling
point in our proposition is that Hop is a user tool that hides technicalities
for peoples that are using it and customers loves this idea. Then because most
of our client's users are functional people that isn't aware about how to work
with git or similar things.
Apart from this answer, for my two cents related to this very useful post I'm
waiting to collect feedbacks from my team during the day of today and then I
will add our thoughts below.
GitHub link:
https://github.com/apache/hop/discussions/5980#discussioncomment-14934425
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
