It would be great to get some help in cleaning things up. As you can see from the backlog of pull requests, we have a bit of a bottleneck. But I hope to spend some time cleaning things up between now and Jan 2018.

In terms of backward compatibility: several people (including me) use this package for teaching and so backwards compatibility (eg, with Python 2.7) is useful.

Ok cool, but when I said breaking backwards compatibility I didn't mean python, I meant reorganizing and renaming some bits. For example, statefbk has a "ctrb" function and your StateSpace class just takes "*args" and then you unpack that to at most five values.

Anyway, do you have another channel of communication, besides the issue tracker and mailinglist?

General rules for compatibility: if an example or unit test breaks, it probably requires some discussion since people may be using that feature. For things in the matlab module, we try to maintain consistency with MATLAB calling conventions.

Current channels for communication are github and the mailing list, with the issue tracker preferred.

That's easy enough, I'll just keep the pull requests small and manageable.

PR #171 addresses some of the docstring issues listed above.
PR #163 contains some discussion about backward compatibility.
Closing this issue since there are no further actions required.