Recurring expenses (e.g. server fees), i.e. “things we must pay*”. Current examples : servers, domain names
Fixed / occasional expenses (e.g. going to events), i.e. “things we may choose to pay for”. Current examples : going to talks / event, communication, goodies, hardware for tests
Paying people
There seem to be a consensus to accept donations to cover recurring and fixed expenses. There’s less consensus on paying people, accepting sponsorship/subventions and building our own structure. The rest of the discussion talks essentially about how shall we accept donations.
Having our own structure vs. relying on an existing structure ?
Having our own structure is high-cost (in term of time and energy) and does not appear necessary to find a way to accept donations. We essentially discussed Librepay and Framasoft as existing intermediate platforms/structure.
Decision: ask framasoft to open a stripe sub-account for us, and to reactivate the previous librepay account. If possible the librepay amounts will be transferred on the stripe framasoft account. We will reevaluate the situation next year if needed (at least in 12 month). The money will be allocated to fund recurring expenses and fixed expenses. The question about paying people will be treated separately. This decision should be sent to the council (on contrib@).
Discussions at FOSDEM and Framasoft GA
Framasoft willing to support / promote the project as part of Contributopia, for instance likely to help us to provide infrastructure to gather donations. There are some projects / ideas floating around for the comings years. Framasky’s work on apps is to be stopped though, since that was part of the Degooglisons campaign (?) and the work is mostly done.
Discussions with Internet Cube people at FOSDEM. ju has no plan to maintain the internet cube apps (hotspot and vpnclient). The activity of the project is relatively low and it’s highly wishable to organize a meeting in the coming weeks to discuss the future of the project.
Discussion with Lunar at FOSDEM about the FCC, and about nixOS and guix which brings interesting feature to build robust automated, reproducible adminsys setups.
Broken apps mostly because of weird php stuff ? They’re working when manually installing them, so maybe an issue with the LXC https://i.imgur.com/TPzKWrZ.png
Following discussion, we should extract the ‘Referrer-Policy’ from server.tpl into a specific PR
Merge it and do a testing, just be careful about this specific header (expected to break some apps?), maybe release a stable for all headers except this one until apps are fixed upstream.
Not really, I don’t think anybody who attended knows about it. Could you elaborate on why you think it could fit our need ? Would you be okay attending the next meeting to talk a bit about it ?