# Call for Action: ROS Answers Migration Account Association

**URL:** <https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037>\
**Category:** ROS General\
**Created:** [June 20, 2023, 10:56pm UTC](https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037 "2023-06-20T22:56:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 20, 2023, 10:56pm UTC](https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037/1 "2023-06-20T22:56:07Z")

</div>

Continuing the discussion from [ROS and Gazebo Answers Migration to Robotics Stack Exchange Process](http://discourse.ros.org/t/ros-and-gazebo-answers-migration-to-robotics-stack-exchange-process/31494/11):

Reminder: Please take a minute to associate your ROS and Gazebo Answers accounts with your Stack Exchange account using this form:

> **[ROS + Gazebo Answers Stack Exchange User Association](https://forms.gle/kyjwqn3nopexHDr29)**
>
> This form is to be used to associate UserIDs between answers.ros.org answers.gazebosim.org and Robotics Stack Exchange to support the migration of content. See more at TODO LINK

> [@ROS and Gazebo Answers Migration to Robotics Stack Exchange Process](https://discourse.openrobotics.org/t/ros-and-gazebo-answers-migration-to-robotics-stack-exchange-process/31494/11):
>
> Maybe it would make sense to already disable posting new questions on ROS and Gazebo Answers, and refer to R.SE to post new questions?

We’re planning to do a coordinated transition where we mark the site read only and then begin the transition at that time. In the mean time, we ask everyone to take a few minutes to help fill in any answers before the site is marked read only.

We’re still working out technical details and will announce the timeline when the details are worked out.

---

<div class="post-metadata">

**Author:** ![peci1](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/peci1/32/10145_2.png) [@peci1](https://discourse.openrobotics.org/u/peci1)\
**Post date:** [June 21, 2023, 4:55am UTC](https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037/2 "2023-06-21T04:55:42Z")

</div>

Will the migrated questions get a special tag on SE? It might help to see if the migration was successful…

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 21, 2023, 9:12pm UTC](https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037/3 "2023-06-21T21:12:36Z")

</div>

Thanks for the suggestion. I don’t think that the tag will be worth using 20% of the available tags for this. (Stack Exchange only allows 5 tags). We will be including a header with acknowledgement of the original source and author which should be easily searchable. And we will have full tracability between each the original posts and their migrated content too. We will be looking at the best way to setup redirects for that as well.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/ros/original/3X/b/6/b607ee3cc8e908b1b613bd74a683d749fea635a1.svg) [@system](https://discourse.openrobotics.org/u/system)\
**Post date:** [July 21, 2023, 9:13pm UTC](https://discourse.openrobotics.org/t/call-for-action-ros-answers-migration-account-association/32037/4 "2023-07-21T21:13:32Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.