FY2026 » FY26 Admin Task » FY26 Weekly Meeting

Summary:
-------
Updates:

• Completed - Install the bitnami package for Redmine and configure Redmine to use as an external issue tracker for GitLab - Task #244: [DevOps] Install the bitnami package for Redmine and configure Redmine to use as an external issue tracker for GitLab

Issues:

• Postponed(Review) - Drafting and Reviewing the ATAG Development Plan - Task #238: [Dev-ATAG plan] Drafting and Reviewing the ATAG Development Plan
• Delayed - Architecture and Functional Design of ATAG Packages - Task #239: [Dev-ATAG] Architecture and Functional Design of ATAG Packages

To do:

• Create a 2F-140 package that recognizes an object (paper crane), grasp, and moves it. - Task #242: [Dev] Create a 2F-140 package that recognizes an object (paper crane), grasp, and moves it.

--------------
Updates:

• DevOps related task management - Task Group #243: [DevOps] DevOps related task management

• Completed - Install the bitnami package for Redmine and configure Redmine to use as an external issue tracker for GitLab - Task #244: [DevOps] Install the bitnami package for Redmine and configure Redmine to use as an external issue tracker for GitLab

This task involved installing Redmine and configuring the GitLab integration, as requested by the DepOps TF last week. Of course, this task became unnecessary as the direction for DevOps tools was decided at last week's XELA SW team alignment follow-up meeting.
However, I would like to share a few things I learned through the Redmine installation and integration process.
1. Since the Bitnami Remine package is no longer supported, I used the Debian Redmine image provided by Docker Hub. It appears that Bitnami is focusing on solutions optimized for cloud-native environments since being acquired by VMWare.
2. The GitLab and Redmine integration was configured in three ways:
a. Push event triggers are sent to Redmine via Webhook settings in GitLab, and Redmine performs mirror repo updates using the gitlab_hook plugin.
b. The URL for Redmine was set up via External Issues Integration in GitLab.
c. Issues are referenced in both GitLab and Redmine through commit messages.
Although we will not be using it since the SW team's standard was finalized last week, my personal opinion is that it would be good to maintain the GitLab and Redmine settings for experimental use if possible.

Issues:

• Postponed(Review) - Drafting and Reviewing the ATAG Development Plan - Task #238: [Dev-ATAG plan] Drafting and Reviewing the ATAG Development Plan
• Delayed - Architecture and Functional Design of ATAG Packages - Task #239: [Dev-ATAG] Architecture and Functional Design of ATAG Packages

The ATAG Dev plan review has been postponed until after the company's software development strategy is established. I expect it will likely proceed this week. Additionally, the ATAG design task has been rescheduled due to the review postponement.

To do:

• Task Group #191: [Dev] MoveIt Pro Application development

• Task #233: [Dev] Create a Web UI Interface of uSkin for Allegro hand v4 curved visualization for the MoveIt Pro Env

• Create a 2F-140 package that recognizes an object (paper crane), grasp, and moves it. - Task #242: [Dev] Create a 2F-140 package that recognizes an object (paper crane), grasp, and moves it.

This week, I will review the development of BT to add object recognition capabilities to the 2F Gripper Config package by applying MoveIt Pro's CLIPSeg model. Additionally, I will create and deliver a brief explanatory document regarding the demo video to be shared with Picknik. That's all for my side.

CLIP-based Segmentation (CLIP-based Segmentation) is an open-vocabulary model that utilizes OpenAI's CLIP model to segment objects within an image using only a text prompt.