Glad to hear that. I make a lot of use of timers in my C++ nodes and
it will be nice to have a supported means of doing that in Python
nodes as well.

So, before committing this particular source file I'll put a BSD
header on it, with (c) 2011 WG and also a pointer to the nabble
archive of this thread and credit to Tim. Once this capability is in
rospy the file will come out of my codebase.

Sound ok?

Pat

On Wed, Feb 2, 2011 at 3:44 PM, Ken Conley <kwc@willowgarage.com> wrote:
> On Wed, Feb 2, 2011 at 3:41 PM, Patrick Bouffard
> <bouffard@eecs.berkeley.edu> wrote:
>> P.S. What's the etiquette on using someone's code from a mailing list
>> posting in one's own BSD-licensed project? :) Some form of attribution
>> of course, but is it okay to slap a BSD license header on a source
>> file containing said code? Is it okay if it says (c) 2011 UC Regents
>> just like all my other headers?
>
> This code will eventually make it to rospy, but we're busy with
> Diamondback.  It should be (c) Willow Garage with a BSD license, in
> this case.
>
>  - Ken
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>