Notices by Richard Levitte (levitte@mastodon.nu)

@ploum @lou_de_sel @allius

Euh ouai... mais là, on arrive à un autre problème: comment est-ce que empêche quelqu'un de voter deux fois (et recevoir deux noms de ce genre)?

@allius @ploum
Aussi, comme les comptes sont décentralisés, tricher devient difficile à cause du nombre total de volontaires, répendus dans le pays entier.

@allius @ploum
Je ne sais pas comment ça fonctionne où tu es. En Suède, les fonctionnaires qui comptent les votes sont des membres volontaires de la société qui ont seulement besoin de savoir lire et savoir compter, et un moment d'éducation quelques jours avant pour apprendre comment tout ça fonctionne ensemble. C'est vraiment tout. Si tu le voulais (et que t'étais citoyen suédois), tu pourrais le faire, sans question.

>

@allius @ploum
Même si tout le monde a accès aux lignes de code, ce n'est quand même pas accessible pour tout le monde. "je n'y connais pas grand chose en programmation" le démontre clairement ! Seulement ça rend le vote électronique difficile à vérifier, car tout le monde doit donc faire confiance à une minorité de gens.

@ploum
Personally, I've come to the conclusion that CLA are pretty much bullshit.

We have other tools for provenance, with the Sign-off trailer in commit messages. Maintainers need to pay attention either way, and in that respect, the Sign-off trailers in front of you are just as easy to deal with as any commit author.

As for increasing the freedom of the maintainers, the creates a power imbalance which isn't very palatable when you thinkg about it.

@ploum
It all really depends what you want a CLA for.

Some want it primarily to increase their own freedom over the project, like license changes.

Some want it primarily for assurance of provenance.

Some want it only from the maintainers (I know that exactly this has been argued for in Apache circles), which then essentially constitutes a permanent sign-off on everything they do.

@ploum
On the subject of license changes, BTW... this is also something to carefully think about.

I'm coming from the perspective that there's a project license, and then there are licenses in each file. They do not have to be the same, all that's needed is that they are compatible.

@ploum
So for the example I see you mention, changing the project license from GPL to AGPL, I actually think that you can change the _project_ license, just as long as the license in each file remains unchanged, and as long as license compatibility remains.

@ryanc
Ooohhh... Ya know, I both agree and don't agree. I'd rather leave it at that, yeah?

@ryanc
For the time, it wasn't too bad. What's amazing is that it hasn't yet been replaced...

@lanodan @drewdevault
I would say that your scenario (4) should be deemed like (2), just with added passive aggressivity (which makes matters worse in my book)...

@mrundkvist
There's a difference though. Even without feeding it, there is still an algorithm making choices for you. In a record store (good enough to have a bit more than just the blandly popular records), you were the algorithm.

If you want to make a tangible parallel, a radio station running the "top of the list" hits is much closer to Spotify with an unfed algo.