Hello everyone, As Mirko mentioned, we think that the sections you will be writing for the book will be good subjects for defensive publications.
Densive publications are like anti-patents. They are used to protect ideas and innovative hacks *against* subsequent patent filing. So with a little bit of extra work, you could kill two birds with one stone: your documentation will not only be useful for other developers and users, it can also be turned into something useful against software patents! If you are interested, feel free to drop in #linuxdefenders on freenode’s IRC servers. ↪ 2014-08-10 Sun 18:57, Mirko Boehm <mi...@kde.org>: > Hugo is in CC in this email. Hugo, you might want to introduce > your self and subscribe to the mailing list. [X] Done. I’m an attorney in training at the Paris Bar currently working with Linux Defenders for OIN. I have been involved with the Free Software Foundation Europe since 2009, including in its legal team¹ and I also lead the ToS;DR project² (“Terms of Service; Didn’t Read”). So I’ve been involved in free software for quite some time already, which should hopefully help me understand what your documentation describes and allow me to help and guide you on making it fit for a defensive publication! 1. https://fsfe.org/legal 2. https://tosdr.org I’m looking forward to working with you and hearing about new features ☺ Best regards, -- Hugo Roy LinuxDefenders.org
pgpS7JbsIWtBa.pgp
Description: PGP signature
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
