Onboard Google Translate Connector to Axon-ivy market

[TuDoanQuang46]

Hi, I've just created a market-product that I'd like to publish into the official axonivy-market. Can you fork it and review my cool product? https://github.com/TuDoanQuang46/google-translate-connector

---

⚠️ do not remove this section, but leave it to track the reviewer's work.

Review Tasks

Product Domain

• [x] product successfully installs into the Axon Ivy Designer
• [x] product parts are marked as Connector or Demo
• [x] the product projects contains documentation to explain the functionality or use-case: e.g. Process-Notes, Input-Parameter descriptions, Meta-Comments on variables.yaml definitions ...
• [x] the product readme fits into the market landscape @andreasbalsiger
• [x] all mandatory setup steps to run the Demo are documented in the setup section of the [myProduct]/product/Readme.md .

Technical Solution

Coherent

• [x] Common group-id for all artifacts <groupId>[org.arcme|com.axonivy].[util|connector].[product-name]<groupId>
• [x] Common artifact-id prefix: <artifactId>msgraph[-product|test|demo]</artifactId>
• [x] Html-Dalogs depend on suggested 'frame' template
• [x] Github actions + maven-build runs as outlined in market-product template

Maintainable

• [x] Dependent third-party infrastructure (e.g. Database, MavenRepos) is available: public accessible instance or shared as code (e.g. Docker, docker-compose)
• [x] Tests are implemented that verify, that the product actually runs
• [x] Additional libraries (e.g. Maven dependencies) are lightweight: not duplicating libaries of the Axon.ivy Classpath Container.
• [x] Depends on standard Axon Ivy features and does not light-heartedly re-introduce forks of existing solutions (e.g. Job-Framework). Our goal is to integrate also third-parties into existing: Enginge-Cockpit-View, Log-Channels, Monitoring features, ...
• [x] Uses latest ivy-environment: e.g. process-files and used project-build-plugin match the ivyProject version.
• [x] Product is re-usable without the need to unpack and customize it for standard use-cases: crucial settings can be overriden with well documented config/variables.yaml

[ivy-rew]

started the technical review https://github.com/axonivy-market/google-translate-connector/pull/1

[ivy-rew]

technical review is done: the connector is good to go from a technical standpoint. thanks a lot for the contribution @TuDoanQuang46 . Can you shortly share whether there is a team involved in keeping the product stable in the future? or is there an active project which will have the lead on this connector? or who should be invited to the new repo on the axonivy-market?

can you give a short feedback on this new connector @andreasbalsiger ? would like to have this connector officially listed on market.axonivy.com? Is the currenct product description ok to be re-used as template for the official market listing? https://github.com/axonivy-market/google-translate-connector/blob/master/google-translate-connector-product/README.md

[ivy-jhi]

Hi @ivy-rew, @TuDoanQuang46 is member of team Bolt. So either team Bolt will take care or maybe our presales colleagues. So please invite team Bolt and Presales.

Thx!

[ivy-rew]

Hi @ivy-rew, @TuDoanQuang46 is member of team Bolt. So either team Bolt will take care or maybe our presales colleagues. So please invite team Bolt and Presales.

Thx!

Thanks a lot Johannes for clarifying the responsibilities. Within the axonivy-market org the team-bolt is not formally defined. We can create one, but I assume that there won't be frequent maintenance required for this product, so it might be an overhead to re-define that team in advance.

So I added you as "maintainer", in order that you can invite further contributors on this repo. And @TuDoanQuang46 as 'writable' developer... so you guys are able to maintain the repo on your own. .... of course you can still involve me on pull-requests for reviews if you like, but there is no formal requirement to do so.

[ivy-rew]

one more thing @TuDoanQuang46 , it would help if you delete your personal repository https://github.com/TuDoanQuang46/google-translate-connector in order to make PRs simpler. Otherwise PRs are by default suggested to be merged back into your origin repo. As you now have write access in the axonivy-market repo, you could directly work on this one. still any third-party can create private forks from the new market repo and contribute back to it.

[andreasbalsiger]

Hey @ivy-rew : this would be my additional bullet points in the readme:

• Is based on Google's REST API specification.
• Translates text and html files.
• Gives you the power of Google Translate features.

[ivy-rew]

thanks for your feedback @andreasbalsiger , just added your points to the readme: https://github.com/axonivy-market/google-translate-connector/pull/4/files

next and final step I'll take:

• [x] create PR on axonivy-market/market for this new product, so that it will be listed in the public market https://github.com/axonivy-market/market/pull/292

[ivy-rew]

The connector is live in a first version: https://market.axonivy.com/google-translate#tab-description Thanks for all your work @TuDoanQuang46 , @ivy-jhi & @andreasbalsiger