Pierre-Yves Lapersonne
Software crafter and digital punker keen on open source, iOS and Android apps. Interested in software ecodesign, privacy and accessibility too. pylapersonne.info
- 34 Posts
- 16 Comments
Pierre-Yves Lapersonne@programming.devMto
Opensource@programming.dev•Which collaborative localization service would you recommend?
2·7 months agoI do not know if the solutions I listed below are open source ; however as an open source contributor I am used to work with some tools depending to choice of the projects:
About credits, I don’t think these tools exposes in some automated way the contributors identities. However, nothing prevents you to use these web UI tools to find who contributed and list people for example in your CONTRIBUTORS files. Another way could be to edit the automated commits these tools submit to your Git repos by adding credits to the translators (with for example Co-authored-by field).
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Liste of non-AI licenses in a GitHub repository
3·11 months agoNot sure of that, maybe we need some case law or update on existing copyleft licenses. Source code generated with GenAI tool, even if their model have been trained with corpora of copyleft sources, are not (yet) considered as derivative works. What a pitty.
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Liste of non-AI licenses in a GitHub repository
3·11 months agoCould be interesting. Non-free and current GenAI tools violate copyright, we may consider some evolutions of copyfarleft licenses to forbid such use of source code in these types of tools.
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Liste of non-AI licenses in a GitHub repository
2·11 months agoAnd nice comment spotted there: https://fosstodon.org/@geraldew/113849843708286036
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Liste of non-AI licenses in a GitHub repository
51·11 months agoJust wanted to share for the common knowledge and the debate as I already saw here some “post open source” and content about rubbish licenses like SSPL or BSL 😉
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Flutter has been forked to Flock
6·1 year agoWow, you mean that Flock 😅
Pierre-Yves Lapersonne@programming.devMto
Opensource@programming.dev•Release v0.1.29 · komorebi - "Tiling Window Management for Windows" (non-FLOSS, see comments)
2·1 year agoThe project here is not under an open source license as defined by the 10 criteria of the Open Source Initiative. There is the only acceptable definition of what is open source today, and you can refer to it by clicking on this hyperlink: https://opensource.org/osd
The publication will be deleted as out of topic.
Pierre-Yves Lapersonne@programming.devMto
Opensource@programming.dev•Rustdesk No security audit, not even in roadmap
21·1 year agoPlease explain and answer the concerns as voiced by the community ; without more detail man can think your are a troll, a bot, or someone generated this answer using GentAI tools.
Your answer is not accurate as it does not bring useful details to the community which have legitimate concerns.
In addition the mentioned GitHub repository in a first sight does not contain mandatory files like CONTRIBUTING or SECURITY which does not help user be confident and have less concerns. Moreover, as the reproducibility of builds is not easy to prove event for FLOSS projects, you cannot rely on that point about open source approach. It does not seem that you are using either Dependabot, Renovate or Snyk to ensure the security of the software.
You should really bring details and make the community less worried and more confident instead of bringing that type of answers.
Next ones of that type might be removed ; the community is not dedicated to open source washing.
Pierre-Yves Lapersonne@programming.devOPto
Git@programming.dev•A simple cheat sheet for Git
1·1 year agoI agree but the solution used for the blog hosting does not expose anything to have a nice rendering of the commands. In addition, using the time to write the command helps to understand and remember. But I agree it could be upsetting.
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Can I Take This Issue? Some ideas about issues management in OS projects
1·1 year agoQuite strange, I have my last publications posted here downvoted without any comment, and I don’t know why. This is kind of unfair because FMPOV it is just hyperlinks maybe interesting or useful, at least for me and other people I know. But it’s the life, it’s social networks, it’s people and I don’t care that much ✌️ Please, leave comments instead ✌️
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•How to Create a Code of Conduct for an Open-Source Project
2·1 year agoQuite strange, I have my last publications posted here downvoted without any comment, and I don’t know why. This is kind of unfair because FMPOV it is just hyperlinks maybe interesting or useful, at least for me and other people I know. But it’s the life, it’s social networks, it’s people and I don’t care that much ✌️ Please, leave comments instead ✌️
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing | TechCrunch
1·1 year agoFYI, spotted the issue and updated it ;) https://github.com/mlemgroup/mlem/issues/1311
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing | TechCrunch
1·1 year agoOk, you are ight, fixed the publication and will dig deeper with my Lemmy app to check if an improvement can be done :) Thanks!
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing | TechCrunch
1·1 year agoSorry, not used to my Lemmy client, still not found how to do that. Quite a newbie, I will take more care next times. Thank you for your comment.
Pierre-Yves Lapersonne@programming.devOPMto
Opensource@programming.dev•Happy software freedom day!
1·1 year agoThank you for your comment 😅










So abandon open source and move to “post open source” or ethical source might be a (sad) solution.