[Libre-soc-dev] inappropriate content within an RFP response

Luke Kenneth Casson Leighton lkcl at lkcl.net
Thu Aug 29 01:30:02 BST 2024


bob,

below is some of the most dangerous slippery slope comments
i have ever seen.

if your employees are going to set up a "smoke screen" behind
which you can basically violate me, you need to become a
FULL mediator carrying out the role i am responsible for,
allowing me to carry out my FULL duties [whilst "protecting"
the person i suspect has pulled the wool over your eyes]

the MOMENT an accusation of abuse was sent to you, you should
have IMMEDIATELY contacted ME, and simultaneously raised
Brian as an anonymising Mediator through which the Project's
Charter may be enforced.

that is the most critical thing, the rest is just as dangerous
and extremely damaging, yet i cannot spend the time sifting
through it to explain the dangers and accusations behind
each sentence, it is too much.

l.



-----

In response to some recent comments we noted on the issue tracker: as a
grant maker, we should, can and will communicate in confidence with any
individual with whom we have a direct or indirect relationship, especially
when dealing with sensitive matters - which as you will appreciate may
include a whole range of unpleasant situations, including violations of our
code of conduct, health issues, personal and business conflicts, etcetera.

Privacy and discretion are the norm. Being able to speak up against
wrongdoings without fear for repercussion is important for a healthy team
climate, which is turn is critical for the long term success of a project.
Due to the dependency team members intrinsically have on their leadership,
we consider the possibility for us to have direct communication with these
team members essential, in everyone's best interest and non-negotiable. The
possibility to ask questions, flag disagreement as well as signal potential
abuse or conflicts of interest threatening the functioning of a team,
without having to go on public record with their concerns, and without
having to directly confront the person in charge, can help for us to
intervene early - when there is still the possibility to mediate and repair
things. In severe cases it will help avoid or at least minimise damage
inflicted upon team members by project leads or other team members.

We keep high standards in terms of acting kindly and responsibly. We are
committed to maintain discretion and confidentiality unless required for
compliance reasons or explicitly agreed otherwise - and trust our
communication partners to do the same. This open door policy works
bidirectionally: anyone should be able to reach out to us in absolute
confidence, just like we will reach out to when we experience a need. It is
important that all stakeholders are correctly informed, and feel free to
speak up.

We consider it inappropriate for a project lead to make communication
demands towards team members (and to NLnet for that matter). We therefore
kindly request you to transparently share this information with your
collaborators in all the places where public statements to the contrary
were made.

-- 
---
geometry: without it life is pointless
the fibonacci series: easy as 1 1 2 3


More information about the Libre-soc-dev mailing list