Questions for the Technical Advisory Board - 2

Elections
选举

Williams then posed a question to his fellow TAB members: with the (recently closed) TAB election, what do they want to see next year? What should the TAB be looking at? And for the non-TAB audience members: what conversations can the TAB drive that would help you in your work?

随后，Williams 向其他 TAB 成员提出了一个问题：随着（刚刚结束的）TAB 选举，大家希望明年看到什么？TAB 接下来应该关注哪些事情？同时他也向非 TAB 的听众提问：TAB 可以推动哪些讨论，能够对你们的实际工作有所帮助？

Levin opined that the TAB is at its best when it's boring: it only becomes exciting when something's going wrong. Williams said that he thought the TAB should be helping people figure out how to talk about kernel deadlines and schedules to their management chains: "Some of you promise kernel deadlines — does there need to be a discussion about that? Can the TAB help?"

Levin 认为，当 TAB 显得“无聊”的时候，反而是它运作得最好的状态；只有在出问题时，它才会变得“刺激”。Williams 表示，他认为 TAB 应该帮助大家思考，如何向管理层沟通内核的截止时间和开发计划：“你们中有些人会对内核的交付期限作出承诺——这件事是不是需要好好讨论一下？TAB 能不能帮上忙？”

Cook thought that was an interesting topic, and maybe worthy of an extension to the contribution maturity model document. A member of the audience asked about a specific case that he had run into trying to add LLVM code-coverage (llvm-cov) build-options: the kernel already supports gcov and kcov, but llvm-cov offered some non-overlapping features that he needed. The maintainer saw that there was (potentially) a lot of common support code between gcov, kcov, and llvm-cov, and told him to go away and refactor things to have a single code-coverage interface, instead of just adding llvm-cov into things. Ojeda agreed that this kind of situation was definitely a place where the TAB could help manage expectations on