API review

Proposer: Tully Foote

Present at review:

Question / concerns / comments

The current services are:

Should any be removed before release?

  • Ken: the only services in the list that I can personally conceive of as standard are Empty, PolledImage, and StringString. PolledImage only has a temporary role in our system, at least until we do polled topics.

  • Josh: The only thing I think should be in std_srvs is Empty. I can't think of any compelling use-case for generic StringString, UInt32String, etc.

  • Eric: We should definitely boot the robot services (e.g. PolledStereoCloud and StaticMap), and PolledImage depends in std_msgs/Image, which is also moving out of std into robot, so logically and dependency-wise that doesn't make sense to keep here. For the basic type pairs, I think we either want to have something like a complete set or not include them. This makes std_srvs very small, and I would propose removing it and having packages that create services define them.

Meeting agenda

  • std_srvs - Should it even exist?

To be filled out by proposer based on comments gathered during API review period

Conclusion

Package status change mark change manifest)

  • /!\ Action items that need to be taken.

  • {X} Major issues that need to be resolved

  • /!\ Remove all but empty srv

Resolution: API conditionally cleared


Wiki: std_srvs/Reviews/2009-02-06_API_Review (last edited 2009-08-14 20:54:54 by localhost)