Hi @cornouws, all,
thanks for sharing your thoughts, which helps to make this initially quite vague topic more specific and thus also easier to reply to.
I was initially hesitating to comment here since I have only joined the TDF team recently and have the impression that I am lacking a lot of the experience/background that would be needed to understand what problems this proposal is trying to address. And, honestly, I still don’t really see that from reading the discussion so far either.
Could you possibly share (either here or in private) a few examples of what problems such a policy would have prevented in the past in your opinion?
Some thoughts/questions on single aspects mentioned during the discussion so far:
Having clear processes and properly handling frictions generally sounds like something desirable of course.
When looking at distinctive roles, I think it’s also essential to be aware that one person can have multiple roles within the project, and to clarify what role the suggested policy is meant to apply to.
In particular, since most staff members are also trustees/TDF members: Is that policy meant for their role as staff members (let’s say “what they do during the time they are paid for by TDF”) only or also for their role as TDF trustees (“what they do as project members in their free time”)?
I lack the background/experience to judge whether there’s a need to more clearly define how BoD interacts with staff members in their role as such. (Maybe an upcoming draft might give more clarity here.)
In any case, I would be very concerned if a new policy was trying to affect how staff members can act in their role as TDF trustees (“in their free time”), and so far cannot see any reason why staff members should be treated differently here than other trustees. (See also @ilmari’s questions in Asking your input! - #69 by ilmari that go in the same direction.)
Asking a colleague colleague first in case of doubt sounds like a good advice, and is actually an advice I was given by a colleague when starting in my new role in the TDF team. (Whether a new policy is needed for this is another question.)
I pretty much agree with what @Sweetshark and @stragu have written on that before (Asking your input! - #38 by Sweetshark and Asking your input! - #47 by stragu ).
That sounds interesting and I’m sure that finding (better) ways to handle conflicts would be for the benefit of all.
@cornouws in Asking your input! - #74 by cornouws :
I would say generally yes. But again, I would like to emphasize that this should in my opinion only apply to what these people do during the time for which they are actually paid by TDF, not what they do in their free time. (I would assume that this is the same for people working for ecosystem companies.)
@cornouws in Asking your input! - #65 by cornouws
With the initial idea being that input and new ideas are to be brought up primarily in the initial phase (i.e. before the draft policy is written): Will it then still be possible to add new ideas at this stage as well, so that those that don’t find the time to do so beforehand still have the chance for these to be included just as well? (to take into account the original idea of gathering broad input from everybody)
Best regards,
Michael