search

ros-industrial / ros_industrial_issues

Repository for tracking common ROS-Industrial issuses.
3 stars 4 forks source link

WRID20 candidates #69

Closed gavanderhoorn closed 4 years ago

gavanderhoorn commented 4 years ago

Use this issue to suggest other topics, subjects and issues for consideration in the wrid20 run this year.

gavanderhoorn commented 4 years ago

@fmauch: FYI.

fmauch commented 4 years ago

From a ur_robot_driver I would throw in the following issues:

gavanderhoorn commented 4 years ago

for these specifically I have a few ideas.

The MSA v2 does some strange things I would like to avoid, so this will require some manual work.

We should not use the Gazebo-support created by the MSA v2 for instance.

This will take 5 mins for someone familiar with MoveIt and how things are "ideally" done, but may take quite some back-and-forth for someone with less experience.

As fixing the MoveIt configs is one of the last things part of ros-industrial/universal_robot#448, I'm probably going to claim this for myself -- even though I might not get to it before or on WRID20.

schornakj commented 4 years ago

Do additional repos need to be explicitly added to the WRID2020 project in order for their issues to show up on the project board?

ipa-nhg commented 4 years ago

@schornakj yes, as linked repositories. If you don't have rights for that, list here the missed ones and we will add them.

fmauch commented 4 years ago

As I'm not overly familiar with github features: Is there any chance we can get the https://github.com/UniversalRobots/Universal_Robots_ROS_Driver repo to the board? As far as I understood the docs it has to be done on the project board's side. Is this possible as the repo lives in another organization's namespace? Will it be enough, if I tag the respective issues with awrid20 label?

gavanderhoorn commented 4 years ago

Is there any chance we can get the https://github.com/UniversalRobots/Universal_Robots_ROS_Driver repo to the board? As far as I understood the docs it has to be done on the project board's side. Is this possible as the repo lives in another organization's namespace? Will it be enough, if I tag the respective issues with awrid20 label?

No. That's not possible.

Only repositories in the ros-industrial organisation can be linked to the project board.

gavanderhoorn commented 4 years ago

@fmauch: what we can do is add a Note to the board (so that's not an issue). But then the content of the node would be a reference to the issue.

I'll do that for the issues you referenced.

Looks like either @cardboardcode or @Briancbn came up with that work-around.

fmauch commented 4 years ago

Cool, that looks promising :-)

gavanderhoorn commented 4 years ago

@schornakj: would you want the yak repositories to be linked to the board?

gavanderhoorn commented 4 years ago

@fmauch: the only downside is that changes in the status of the cards will not be reflected in the timeline of the issue (ie: you won't see automatic updates of the status (unassigned, in progress, etc).

So that requires a bit more manual work to manage those cards.

schornakj commented 4 years ago

@schornakj yes, as linked repositories. If you don't have rights for that, list here the missed ones and we will add them.

@schornakj: would you want the yak repositories to be linked to the board?

Sorry for the late reply. Yes, if we could link yak and yak_ros that would be excellent.

e: I tagged some issues that fit the WRID2020 theme, so let me know if I need to do something different to link the issues to the board.

gavanderhoorn commented 4 years ago

@schornakj wrote:

Sorry for the late reply. Yes, if we could link yak and yak_ros that would be excellent.

Done.

e: I tagged some issues that fit the WRID2020 theme, so let me know if I need to do something different to link the issues to the board.

Could you please use the formatting for the label as specced here (colour, label and description)? That way the issues you label will show up in the automated search, making things much easier to manage.

mpowelson commented 4 years ago

Are we adding noether or was that decided to be too obscure? There are a few relatively low hanging fruit issues on there that seem like good candidates.

gavanderhoorn commented 4 years ago

@mpowelson wrote:

Are we adding noether or was that decided to be too obscure? There are a few relatively low hanging fruit issues on there that seem like good candidates.

I'd be happy to have noether on the list.

It's up to you.

mpowelson commented 4 years ago

I would add it. Either way I will probably work on it.

gavanderhoorn commented 4 years ago

If you could add some cards for the issues you'd like to be part of WRID20, that would be appreciated.

Edit: forgot that noether is actually here on ros-industrial.

I've linked it to the board.

If you could mark some issues, we can add them to the board.

Please use the formatting for the label as specced here (colour, label and description)? That way the issues you label will show up in the automated search, making things much easier to manage.

schornakj commented 4 years ago

Could you please use the formatting for the label as specced here (colour, label and description)? That way the issues you label will show up in the automated search, making things much easier to manage.

Did it!

mpowelson commented 4 years ago

@gavanderhoorn I don't think I can label things since I am not a maintainer on that repo. I can comment on them though.

gavanderhoorn commented 4 years ago

Oh, that's unfortunate.

I can allow you to label issues. Would that work?

Edit: could you check whether you can now manage labels and issues?

mpowelson commented 4 years ago

@gavanderhoorn Yes it looks like I can now. Thanks.

Edit: Though I don't know that I can add new labels. I can use existing ones though like wrid19

gavanderhoorn commented 4 years ago

Just added the new one.

Please also make sure to add those labelled issues to the board. You should be able to do that.

gavanderhoorn commented 4 years ago

Closing as WRID20 was already 2 months ago.