[Libre-soc-dev] Fwd: Request for payment for 2021-02-052: The Libre-SOC Gigabit Router

whygee at f-cpu.org whygee at f-cpu.org
Tue Aug 20 22:50:38 BST 2024


On 2024-08-20 10:30, Luke Kenneth Casson Leighton via Libre-soc-dev 
wrote:
> ---------- Forwarded message ----------
> From: <dashboard at nlnet.nl>
> Date: Tuesday, August 20, 2024
<snip>
> We consider it inappropriate for a project lead to make communication
> demands towards team members (and to NLnet for that matter).

That part confuses me the most,
and brings anxiety.

This raises a crucial question
(and this is *not* addressed to Luke).
What can a "project lead" do, ask and not do ?
And who decides this, in our context, and enforces it ?
And without the possibility to enforce communication,
if at least to clarify any situation and prevent confused
(and misleading) "back channels", how can a leader... *lead* ?
How can the developers feel "as a team", remain confident
that they all work toward a common, agreed goal ?
Where is it all codified, where is the "constitution" ?
I remember that I have agreed to a "sort of code of conduct"
that can be summarised as "be a good person".
But it seems that the NLnet framework requires something else,
and not being a recipient, I have not read a formal contracts.

It feels to me that NLnet tries to enforce "something"
but is not totally open about what. It wants to protect "something".
What I have read so far is "carefully
phrased and politically correct" declarations
of intentions without even going into any detail,
nothing is coming from the heart, everything is calculated.
This leaves a bitter taste of FUD because "nobody can know".
Keeping the team in the dark effectively kills the project.
I see Luke's endless efforts to remedy this yet the more
he tries, the more NLnet.. evades. But who am I to be
entitled to know private negociations ?

If I wanted to play the backchannel and backstabbing game,
I'd be a career engineer/manager at a big company.
I'm heartbroken by the current situation and I wonder
what will remain of this project, what will be its legacy
and what parts will be reused by other projects.

It must not have been done in vain.

yg



More information about the Libre-soc-dev mailing list