This is an automated email from the ASF dual-hosted git repository. hansva pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-hop-website.git
commit 2eb0091ead82c5d6d618cbc779058b9fc4885602 Author: Bart Maertens <[email protected]> AuthorDate: Wed Oct 14 15:57:06 2020 +0200 renamed Project Hop references to Apache Hop --- content/community/contributing.adoc | 6 +++--- .../community/contribution-guides/code-contribution-guide.adoc | 6 +++--- .../contribution-guides/documentation-contribution-guide.adoc | 8 ++++---- content/community/contribution-guides/jira-guide.adoc | 6 +++--- .../contribution-guides/website-contribution-guide.adoc | 2 +- content/community/tools.adoc | 2 +- content/docs/architecture.adoc | 2 +- content/docs/qa.adoc | 10 +++++----- content/docs/roadmap.adoc | 2 +- content/download/download.adoc | 2 +- layouts/partials/header.html | 2 +- site.yml | 8 ++++---- 12 files changed, 28 insertions(+), 28 deletions(-) diff --git a/content/community/contributing.adoc b/content/community/contributing.adoc index 928ea82..8083fb6 100644 --- a/content/community/contributing.adoc +++ b/content/community/contributing.adoc @@ -2,7 +2,7 @@ title: "How To Contribute" --- -Project Hop is developed by an open and friendly community. Everybody is cordially welcome to join the community and contribute to Project Hop. There are several ways to interact with the community and to contribute to Hop including asking questions, filing bug reports, proposing new features, joining discussions on the mailing lists, contributing code or documentation, improving the website, or testing release candidates. +Apache Hop is developed by an open and friendly community. Everybody is cordially welcome to join the community and contribute to Apache Hop. There are several ways to interact with the community and to contribute to Hop including asking questions, filing bug reports, proposing new features, joining discussions on the mailing lists, contributing code or documentation, improving the website, or testing release candidates. == What do you want to do? Contributing to Hop goes beyond writing code for the project. Below, we list different opportunities to help the project: @@ -38,7 +38,7 @@ A release candidate will be announced using our form/twitter and chat. We will t == Further Reading === Submit a Contributor License Agreement -Please submit a contributor license agreement to the Project Hop if you are contributing a lot of code to Project Hop. The following quote from http://www.apache.org/licenses gives more information about the ICLA and CCLA and why they are necessary. +Please submit a contributor license agreement to the Apache Hop if you are contributing a lot of code to Apache Hop. The following quote from http://www.apache.org/licenses gives more information about the ICLA and CCLA and why they are necessary. .Apache Licenses @@ -58,7 +58,7 @@ There is no strict protocol for becoming a committer or PMC member. Candidates f Candidates for new committers are suggested by current committers or PMC members, and voted upon by the PMC. -If you would like to become a committer, you should engage with the community and start contributing to Project Hop in any of the above ways. You might also want to talk to other committers and ask for their advice and guidance. +If you would like to become a committer, you should engage with the community and start contributing to Apache Hop in any of the above ways. You might also want to talk to other committers and ask for their advice and guidance. === What are we looking for in Committers Being a committer means being recognized as a significant contributor to the project (community or technology), and having the tools to help with the development. Committer candidates are community members who have made good contributions over an extended period of time and want to continue their contributions. diff --git a/content/community/contribution-guides/code-contribution-guide.adoc b/content/community/contribution-guides/code-contribution-guide.adoc index 0bb3803..38d16ba 100644 --- a/content/community/contribution-guides/code-contribution-guide.adoc +++ b/content/community/contribution-guides/code-contribution-guide.adoc @@ -2,11 +2,11 @@ title: "Code Contribution Guide" --- -Project Hop is maintained, improved, and extended by code contributions of volunteers. We welcome contributions to Hop, but due to the size of the project and to preserve the high quality of the code base, we follow a contribution process that is explained in this document. +Apache Hop is maintained, improved, and extended by code contributions of volunteers. We welcome contributions to Hop, but due to the size of the project and to preserve the high quality of the code base, we follow a contribution process that is explained in this document. *Please feel free to ask questions at any time*. Either send a message in the dev channel on our chatserver or comment on the Jira issue you are working on. -*IMPORTANT*: Please read this document carefully before starting to work on a code contribution. Follow the process and guidelines explained below. Contributing to Project Hop does not start with opening a pull request. We expect contributors to reach out to us first to discuss the overall approach together. Without consensus with the Hop committers, contributions might require substantial rework or will not be reviewed. +*IMPORTANT*: Please read this document carefully before starting to work on a code contribution. Follow the process and guidelines explained below. Contributing to Apache Hop does not start with opening a pull request. We expect contributors to reach out to us first to discuss the overall approach together. Without consensus with the Hop committers, contributions might require substantial rework or will not be reviewed. <<code-contribution-process>> [%hardbreaks] @@ -52,7 +52,7 @@ anchor:code-contribution-process[Code Contribution Process] == anchor:create-jira-ticket[]Create JIRA Ticket and Reach Consensus -The first step for making a contribution to Project Hop is to reach consensus with the Hop community. This means agreeing on the scope and implementation approach of a change. +The first step for making a contribution to Apache Hop is to reach consensus with the Hop community. This means agreeing on the scope and implementation approach of a change. In most cases, the discussion should happen in Hop’s bug tracker: https://jira.project-hop.org[Jira]. diff --git a/content/community/contribution-guides/documentation-contribution-guide.adoc b/content/community/contribution-guides/documentation-contribution-guide.adoc index 18d9335..c489d40 100644 --- a/content/community/contribution-guides/documentation-contribution-guide.adoc +++ b/content/community/contribution-guides/documentation-contribution-guide.adoc @@ -2,7 +2,7 @@ title: "Documentation Contribution Guide" --- -Good documentation is crucial for any kind of software. This is especially true for sophisticated software systems such as distributed data processing engines like Project Hop. The Project Hop community aims to provide concise, precise, and complete documentation and welcomes any contribution to improve Project Hop’s documentation. +Good documentation is crucial for any kind of software. This is especially true for sophisticated software systems such as distributed data processing engines like Apache Hop. The Apache Hop community aims to provide concise, precise, and complete documentation and welcomes any contribution to improve Apache Hop’s documentation. ==== Our documentation is not yet fully implemented @@ -20,7 +20,7 @@ ideas and contributions are very welcome, come discuss with us on our https://ch == anchor:doc-types[]Types of documentation -Project Hop has multiple types of documentation, each type is directed to a different audience and covers other use cases. We are maintaining a user manual which contains basic and more advanced instructions on how to use and set up Hop. +Apache Hop has multiple types of documentation, each type is directed to a different audience and covers other use cases. We are maintaining a user manual which contains basic and more advanced instructions on how to use and set up Hop. === User manual The goal for the user manual is to give a general feeling to how the application works, which transforms and actions are available and a guide on how to use them. A default template is used to explain how transforms and actions work, an Archetype is included in the repository to use as a template. @@ -34,7 +34,7 @@ This is code documentation and only needed when you want to explore the internal == anchor:obtain-docs[]Obtain the documentation sources -Depending on the type of documentation the project Hop documentation is maintained in the separate git repository as the code base. +Depending on the type of documentation the Apache Hop documentation is maintained in the separate git repository as the code base. === User manual and Technical documentation @@ -97,7 +97,7 @@ We are planning on providing all documentation in multiple languages. We are loo == anchor:submit-doc[]Submit your contribution -Project Hop accepts documentation contributions through the GitHub as Pull Requests. Pull requests are a simple way of offering a patch by providing a pointer to a code branch that contains the changes. +Apache Hop accepts documentation contributions through the GitHub as Pull Requests. Pull requests are a simple way of offering a patch by providing a pointer to a code branch that contains the changes. To prepare and submit a pull request follow these steps. diff --git a/content/community/contribution-guides/jira-guide.adoc b/content/community/contribution-guides/jira-guide.adoc index 7a3114d..e2b7220 100644 --- a/content/community/contribution-guides/jira-guide.adoc +++ b/content/community/contribution-guides/jira-guide.adoc @@ -2,7 +2,7 @@ title: "Jira Guidelines" --- -Jira is the issue tracker that is being used to track all changes and implementation of new code or documentation in Project Hop. This document serves to explain the workflow that is used and what can happen after a ticket has been created. The second purpose is to explain what you need to do to create an complete ticket, doing so helps the developers to understand the request and work on it. +Jira is the issue tracker that is being used to track all changes and implementation of new code or documentation in Apache Hop. This document serves to explain the workflow that is used and what can happen after a ticket has been created. The second purpose is to explain what you need to do to create an complete ticket, doing so helps the developers to understand the request and work on it. [%hardbreaks] . <<create-ticket, Creating a Jira Ticket>> @@ -52,7 +52,7 @@ If possible include a sample pipeline and sample data to reproduce the situation == anchor:workflow[]Hop Jira Workflow -The Jira workflow that is using in the development process of Project Hop is the following. +The Jira workflow that is using in the development process of Apache Hop is the following. image::/img/Jira-Workflow.png[Workflow] @@ -64,7 +64,7 @@ image::/img/Jira-Workflow.png[Workflow] The committer will always add a comment to the ticket stating his reasoning, why the ticket will not be handled -* When a release of Project Hop has finished the committers will go over the backlog and decide which tickets will be added to the following release. These tickets are then added to the ready for development list. Each ticket in this list is linked to a release version and the goal is to add them to the following release. When this list has been created it is not final, following exceptions can occur +* When a release of Apache Hop has finished the committers will go over the backlog and decide which tickets will be added to the following release. These tickets are then added to the ready for development list. Each ticket in this list is linked to a release version and the goal is to add them to the following release. When this list has been created it is not final, following exceptions can occur ** A severe or critical bug has been created, these can get fast tracked and added to a current release ** The reporter wants to work on the issue, when the reporter wants to be contributor for the code the ticket can be added to the current release. A committer will add the contributor to the ticket, the contributor tries to create a pull request in the same time frame as the rest of the developers. diff --git a/content/community/contribution-guides/website-contribution-guide.adoc b/content/community/contribution-guides/website-contribution-guide.adoc index 0989fc5..c72c6a9 100644 --- a/content/community/contribution-guides/website-contribution-guide.adoc +++ b/content/community/contribution-guides/website-contribution-guide.adoc @@ -49,7 +49,7 @@ We are planning on providing the website in multiple languages. We are looking f == anchor:submit-website[]Submit your contribution -Project Hop accepts website contributions through the GitHub as Pull Requests. Pull requests are a simple way of offering a patch by providing a pointer to a code branch that contains the changes. +Apache Hop accepts website contributions through the GitHub as Pull Requests. Pull requests are a simple way of offering a patch by providing a pointer to a code branch that contains the changes. To prepare and submit a pull request follow these steps. diff --git a/content/community/tools.adoc b/content/community/tools.adoc index cc0f90c..407e860 100644 --- a/content/community/tools.adoc +++ b/content/community/tools.adoc @@ -37,7 +37,7 @@ Artifactory is a storage location for artifacts that are created by maven. Each Artifactyory can be found https://artifactory.project-hop.org[here] == anchor:sonarcloud[]Sonarcloud -Sonarcloud is a platform that does code checks and validates the quality of your code. The goal of project hop is to create solid clean code, Sonarcloud helps us achieve this goal. Currently it does not look good yet but we are still in a stage where we are refactoring and cleaning up the Hop code base. +Sonarcloud is a platform that does code checks and validates the quality of your code. The goal of Apache Hop is to create solid clean code, Sonarcloud helps us achieve this goal. Currently it does not look good yet but we are still in a stage where we are refactoring and cleaning up the Hop code base. You can take a look at the status of our project https://sonarcloud.io/dashboard?id=hop[here] diff --git a/content/docs/architecture.adoc b/content/docs/architecture.adoc index c2a2133..0783709 100644 --- a/content/docs/architecture.adoc +++ b/content/docs/architecture.adoc @@ -8,5 +8,5 @@ Doing this, Hop aims to have a minimal installation footprint and wants to be st The way these goals are chased is by allowing orchestration workloads, defined in the broadest possible sense, to be defined as metadata. This metadata can then be expressed in various ways like an XML or JSON document, a database of any type or indeed a graphical user interface. The user interfaces delivered by this project needs to cover 100% of all functionality, removing the need for external editors or tools. -Project Hop decided to use a single metadata interface for all expressions of metadata. This interface is called the MetaStore. +Apache Hop decided to use a single metadata interface for all expressions of metadata. This interface is called the MetaStore. Once orchestration metadata is defined we offer tools to execute locally, remotely, debug and so on. diff --git a/content/docs/qa.adoc b/content/docs/qa.adoc index 5abdab3..b87ca31 100644 --- a/content/docs/qa.adoc +++ b/content/docs/qa.adoc @@ -3,13 +3,13 @@ title: "Q&A" --- * Is this a fork? -** Yes this is a fork, in the sense that we used Kettle 8.2.0.7 as a starting point for Project Hop. Project Hop wants to used that as a starting point to explore the future of data integration. Check out the link:../roadmap/[Roadmap] and link:../architecture/[Architecture] sections. +** Yes this is a fork, in the sense that we used Kettle 8.2.0.7 as a starting point for Apache Hop. Apache Hop wants to used that as a starting point to explore the future of data integration. Check out the link:../roadmap/[Roadmap] and link:../architecture/[Architecture] sections. * Is this a hostile fork? -** By all means no! Kettle will remain a stable and trustworthy platform for data integration. Project Hop is a way to decouple the risk of experimentation and refactoring from the stability needs of Pentaho Data Integration. As such we’ve invited Hitachi Vantara to contribute to Project Hop, just like we invite every individual in the entire Kettle and data engineering community to contribute. We sincerely hope that cool innovations from this project will find its way into other codeb [...] +** By all means no! Kettle will remain a stable and trustworthy platform for data integration. Apache Hop is a way to decouple the risk of experimentation and refactoring from the stability needs of Pentaho Data Integration. As such we’ve invited Hitachi Vantara to contribute to Apache Hop, just like we invite every individual in the entire Kettle and data engineering community to contribute. We sincerely hope that cool innovations from this project will find its way into other codebas [...] * Will Hop remain open source? -** Hop is and will always be open source. Project Hop will start incubation with the Apache Software Foundation as soon as this is possible. This means when the code is different enough from the existing Kettle codebase and when a certain stability in and size of the project team has been reached. -* Can I contribute to Project Hop? +** Hop is and will always be open source. Apache Hop will start incubation with the Apache Software Foundation as soon as this is possible. This means when the code is different enough from the existing Kettle codebase and when a certain stability in and size of the project team has been reached. +* Can I contribute to Apache Hop? ** link:../../community/contributing/[Contributing] -* What are the plans for Project Hop +* What are the plans for Apache Hop ** link:../roadmap/[Roadmap] diff --git a/content/docs/roadmap.adoc b/content/docs/roadmap.adoc index 745963e..b814b77 100644 --- a/content/docs/roadmap.adoc +++ b/content/docs/roadmap.adoc @@ -15,5 +15,5 @@ On a very high level here are the things we want to do: ** Make it easier to find Transforms or Tasks you need. ** Create a generic metastore browser for all objects in one location while at the same time making extensive use of editors of metastore elements in the locations where they’re needed. This does away with the complete left hand side of the Spoon user interface giving more screen real-estate for the Pipelines and Workflows. (**done**) ** tbd -* Create new documentation for every Transform and Task shipped with project Hop. This documentation needs to be stored in git along with the code and should allow us to generate HTML for offline inclusion or a PDF if needed. (**done**) +* Create new documentation for every Transform and Task shipped with Apache Hop. This documentation needs to be stored in git along with the code and should allow us to generate HTML for offline inclusion or a PDF if needed. (**done**) * Create integration tests for every Transform or Task shipped so we can guard compatibility from release to release. diff --git a/content/download/download.adoc b/content/download/download.adoc index e62e0a1..8acb541 100644 --- a/content/download/download.adoc +++ b/content/download/download.adoc @@ -2,7 +2,7 @@ title: "Download" --- -There is no official release of project hop yet, but you can take a look at the latest build of our software. +There is no official release of Apache Hop yet, but you can take a look at the latest build of our software. **Preview release 0.30 https://artifactory.project-hop.org/artifactory/hop-releases-local/org/hop/hop-assemblies-client/0.30/hop-assemblies-client-0.30.zip[here]** diff --git a/layouts/partials/header.html b/layouts/partials/header.html index ac35760..546d6a1 100644 --- a/layouts/partials/header.html +++ b/layouts/partials/header.html @@ -4,7 +4,7 @@ <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <link rel="icon" type="image/png" href="{{ "favicon-196x196.png" | relURL }}" sizes="196x196"> - <meta name="application-name" content="Project Hop"> + <meta name="application-name" content="Apache Hop (Incubating)"> <link rel="manifest" href="{{ "site.webmanifest" | relURL }}"> <title>{{ block "title" . }}{{ .Title }} - {{ .Site.Title }}{{ end }}</title> <link rel="canonical" href="{{ .RelPermalink }}"> diff --git a/site.yml b/site.yml index b83ac49..9593150 100644 --- a/site.yml +++ b/site.yml @@ -1,5 +1,5 @@ site: - title: Project Hop + title: Apache Hop (Incubating) url: https://hop.apache.org start_page: manual::index.adoc keys: @@ -7,13 +7,13 @@ site: content: sources: - - url: [email protected]:project-hop/hop-doc.git + - url: [email protected]:apache/incubator-hop-docs.git branches: master start_path: /hop-user-manual/ - - url: [email protected]:project-hop/hop-doc.git + - url: [email protected]:apache/incubator-hop-docs.git branches: master start_path: /hop-tech-manual/ - - url: [email protected]:project-hop/hop-doc.git + - url: [email protected]:apache/incubator-hop-docs.git branches: master start_path: /hop-dev-manual/
