"BF"?

I'm specifically talking about the "CSSU problem". Which has never been discussed in the CSSU's proper mailing list (maemo-developers) nor a clear statement of "we had this problem". MAG was missing but there were then various back channel ways of trying to resolve the problem: that the Garage account for uploading new packages was linked to his RSA key. CSSU needs to identify how such gatekeeper processes should work; especially for "Stable".

There was a workaround, changing the Garage account to one shared between trusted people (with some process to say who is actually uploading it) is workable.

The approach of allocating work to X-Fade (and I accept his self-criticism of spending too much time on apps.formeego.org - we need to have the time allocated to maemo.org maintenance used and prioritised more transparently) seems to be the community (through SD69) seeming to organise occasional meetings (I was sure there was more than one) and throw tasks at X-Fade without any public prioritisation. I don't want to defend the situation, but I can quite clearly see how both "sides" are to blame: how can anyone be expected to prioritise the work properly in that situation?

Some of the problems could even be addressed within the community: all the code for maemo.org is open source and if anyone really needed to, they could scratch their own itch. And then the task for X-Fade is to support them in that and deploy the change, rather than write it himself amongst a set of tasks.