GroundPlane

joined 7 months ago
[–] [email protected] 2 points 5 months ago

The Irish express solidarity on a regular basis. The anticolonial struggle against the English has made them way closer to Palestinians and other colonized peoples than the rest of Europe.

[–] [email protected] 3 points 5 months ago

Most member states have been in support of Israel. Most egregious being US and Germany, but France is ranking high. Supporting Israel is quite zionist in my opinion

[–] [email protected] 2 points 5 months ago

Literally C/C++. Most used out there. Now if you want to do everything with it, you're in for a long ride. You can do everything on every platform with C. But learning the language is the easy part. The hard part is learning good coding pratices, which library to use and how. Only guides and practice will help you there

[–] [email protected] 2 points 5 months ago
  1. Turning into an executable is compiling as far as C goes. For Python, there probably is something somewhere to wrap a script into a .exe.

  2. For the UI: what matters is the data you generate, not the fluff around it. As the other commenter said, start with a CLI program. You can easily nest several levels of menus if that's your thing. This allows you to have user input. Then for outputs you can do it to a .txt or .md file. Use simple text-based formats. Then once you've got that down you could build a GUI? But tbh I have never built a GUI and I've been programming for 10 years at this point so I can't help you out. There are simple cross-platform libraries you can use out there

[–] [email protected] 7 points 5 months ago

Never in a million years would Switzerland condemn Israel. The state loves Israel. Maybe a strongly worder "please don't kill children in hospitals" was said, but no measures whatsoever were taken

[–] [email protected] 3 points 6 months ago

A balance definitely needs to be struck and I'm hopeful that I am on the right side of it. Thank you for your support, it means a lot

[–] [email protected] 2 points 6 months ago (2 children)

I'm trying to lay a plan in my head where some software parts of the project could be made as graduate projects. If I can get key teachers in on it they could really help out. I'll draft a plan in my head and try to gather people who showed interest here for a meeting once a better-crafted top-level view is set

[–] [email protected] 2 points 6 months ago

Got you. It is a shame that this part of crypto is not more widely publicized, as it is its most interesting use in my eyes.

Still think it can't be the only solution if we want wider reach. To avoid taxes and legal structures, I want to study whether we can interface with projects' available donation options and automatically split a user donation into several. Skipping the "finding the donation option for each project" problem which can be tediously human-solved for a proof of concept, the issue would be whether the process could be easy for the user while not getting obliterated by transaction fees.

There is no need to develop a crypto side since I'm sure a way to interface with Kivach could be found if the other fiat currency problems are solved beforehand.

Thank you for your input, it means a lot.

[–] [email protected] 2 points 6 months ago

It is crucial indeed. That makes the project more of a central donation platform removed from the dev world, but it is simpler as such

[–] [email protected] 3 points 6 months ago

Ideally you would let picky users override every setting and provide fair enough defaults. That includes library donation cascading etc. At the end of the day it seems the core part of the project should be providing fair enough defaults

[–] [email protected] 1 points 6 months ago

SPI is great, didn't know about it. Sadly, it would need more projects in it to be a core pillar of FOSS funding. They are clearly aiming to build something stable and that's good for them. But I feel like their application process is a little too long for simply distributing funds around.

 

We all love FOSS. Lately, many of us have expressed their disarray at hearing stories of maintainers quitting due to a variety of factors. One of these is financial.

While donating to your favorite app developer is something many of you already do, the process can be tedious. We're running all sorts of software on our machines, and keeping an exhaustive list to divide donations to projects is somehow more effort than tinkering with arch btw™.

Furthermore, this tends to ignore library projects. Library maintainers have been all over FOSS-centered media rightly pointing out that their work is largely unnoticed and, you guessed it, undervalued.

What can we do about it? Under a recent Lemmy post, some have expressed support for the following idea:

Create a union of open source maintainers to collect donations and fairly redistribute them to members.

How would this work?

Client-side:

  1. You take some time to list the software you use and want to donate to
  2. You donate whatever amount you want for the whole

Server-side:

  1. Devs register their projects to the union while listing their dependencies
  2. A repartition table is defined by the relevant stakeholders. Models discussed below.
  3. When a user donates, the money is split according to the repartition table

How do we split the money? It could be:

  • Money is split by project. A portion of donations go to maintainers of libraries used by the project.
  • Money is split according to need. Some developers don't need donations because they are on company payroll. Some projects are already well-funded. Some devs are struggling while maintaining widely used libraries (looking at you core-js). Devs log their working time and get paid per hour in proportion of all donations.
  • Any other scheme, as long as it is democratically decided by registered maintainers.

Think of it like a worldwide FOSS worker co-op. You "buy" software from the co-op and it decided what to do with the money.

We "only" need to get maintainers to know about the initiative, get on board and find a way to split the money fairly. I'm sure it will be easy to agree on a split, since any split of existing money will be more satisfactory than splitting non-existent money.

What are your thoughts on this? Would you as a maintainer register? Would you donate as a user? Would you join a collective effort to build this project? Let's discuss this proposition together and find a way to solve that problem so that FOSS can keep thriving!

view more: next ›