XSF Discussion - 2023-03-27

Besides this could be interesting : https://sovereigntechfund.de/en/applications/

> Selection criteria > ... open implementations of communication protocols ... ✏

Arne: thx, will investigate

Dear members, today I got to know of the Sovereign Tech Fund of the German Federal Ministry for Economic Affairs and Climate Action. I think this is a very valuable fund and can really support XMPP on a holistic basis and I would strong advocate to apply for it. Below I will call for your input. https://sovereigntechfund.de/en/applications/ What is it about? > The Sovereign Tech Fund invests in the development, improvement and maintenance of open digital base technologies worldwide. Applications can be submitted on an ongoing basis. > The Sovereign Tech Fund invests in open digital base technologies that are vital to the development of other software or enable digital networking. We invest in projects that benefit and strengthen the open source ecosystem. Examples include libraries for programming languages, package managers, open implementations of communication protocols, administration tools for developers, digital encryption technologies, and more. > The activities listed in the application must be related to developing or maintaining open digital base technologies. Development is our primary focus, although security audits, conference attendance, and other community-based events can be included in the application should they be necessary. I think this very much suits XMPP as a protocol. Within this context I would like to call for your ideas what we can fund with it (150.000 EUR minimum). As said it can be about writing XEPs, but also conferences, infrastructure, events and participation of conferences. Highly worth to give this a try. So, what can you think of? https://pad.nixnet.services/K-DVXLFUSxaF4liewf0Smw Cheers

$150k pays for a lot of XEPs

Infinity XEPs if my math based on cost per XEP up to now is correct

how many XEPs do we need to take over the world?

that money is quickly spent, believe me 🙂 I would also apply for rather 500.000 EUR

its not only about xep

Curious to see how the application looks like, if you need a well defined plan on how to spend it, etc.. But sounds great!

To create such a plan please put all your wet dreams into the pad

if we really require it

Extended a bit, will keep adding more as I get to think about it 🙂

perfect!

I think the chances are high for the XSF

Without drastically expanding what the XSF does in ways that have been proposed and rejected before I can't think of a single thing (or multiple things) we could use anywhere near that much money for, but looking forward to reading suggestions from others :)

put all the wet dreams into gpt4 for it to produce the grant application

we could expand XSF to include a reference implementation for XMPP IM, that seems like a de facto way to produce protocols these days, no? ;)

sending one dev to a conference can cost 6000€

L29Ah - if you think its meaningful put it on the lsit

how many XEPs does a dev at a conference produce?

3.14

> we could expand XSF to include a reference implementation for XMPP IM, that seems like a de facto way to produce protocols these days, no? ;) That's been proposed before, I think literally everyone was against it, for example

How many XEPs would a dev dev if devs dev'd XEPs?

(imagine picking one reference implementation without pissing off a substantial % of XSF members)

yeah i expected this

maybe a libxmpp then?

In rust right?

oh right

But then all the other lang devs will be sad

> moparisthebest: > 2023-03-27 10:34 (GMT+02:00) > (imagine picking one reference implementation without pissing off a substantial % of XSF members) proposing is different that deciding

just do it. also think if what xeps we need to rivse and a significant amount of people will support it

mod_rest?

emus: I could help writing a good text for the application. I would suggest adding all ideas together and the current state with all it's possibilities. Also mentioning where and for what it is and can be used. This > (imagine picking one reference implementation without pissing off a substantial % of XSF members) would be avoided then

Arne: thanks