Q to candidates: reporting frequency
Dear candidates, what do you think it's the appropriate frequency for
reporting back to the project about what the DPL is doing?
Certainly, reporting often is time consuming and divert time from
actually *doing* stuff, rather than documenting what has been done. But
OTOH reporting seldomly ends up giving the impression that the DPL isn't
doing much except to those that, for whatever reason, end up interacting
(privately) with him/her. Where do you think is the sweet spot in this
spectrum?
Cheers.
--
Stefano Zacchiroli . zack@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader . OSI Board Director . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
Reply to: