Nov 04 10:56 2017, Jeff Smith wrote to Markus Reschke:
JS> I know and realize that the tasks are specified. But that does not JS> establish a candidates attitude or outlook on what (s)he want to JS> see.
>> Vote wisely!
JS> Given sufficient input that would be my goal.
I don't know what other FTSC members are thinking about transparency, but it could be a good idea to open the FTSC echo (read only?), so that voters can assess the candidate's performance. That would be much better than candidates only telling voters what they intend to do (newcomers still would have to, of course).
My personal intention is to have proper documentation with clear definitions. Too often I've stumbled across defintions allowing ambiguous interpretations when I was trying to find out how to implement a feature. mfreq and nl2binkd are some of my projects. And for the husky project I've also submitted several bug fixes and code for new features.
