From 67ddd4808e66640e15cb7f2221e75d1b37480c9f Mon Sep 17 00:00:00 2001 From: wilder Date: Sat, 6 Aug 2022 15:35:23 +0000 Subject: [PATCH] =?UTF-8?q?Update=20autres=20formats/Finalisation=5Fcit?= =?UTF-8?q?=C3=A9=5Fdes=5Fsciences=5F=5Fobsolete=5F.odt,=20autres=20format?= =?UTF-8?q?s/Finalisation=5Fcit=C3=A9=5Fdes=5Fsciences=5F=5Fobsolete=5F.pd?= =?UTF-8?q?f,=20autres=20formats/Organisation.odt,=20autres=20formats/Orga?= =?UTF-8?q?nisation.pdf,=20autres=20formats/Recevoir=5FRichard=5FStallman.?= =?UTF-8?q?odt,=20autres=20formats/Recevoir=5FRichard=5FStallman.pdf,=20au?= =?UTF-8?q?tres=20formats/R=C3=A9ponse=5F=C3=A0=5Fla=5FCit=C3=A9=5Fdes=5FS?= =?UTF-8?q?ciences.odt,=20autres=20formats/R=C3=A9ponse=5F=C3=A0=5Fla=5FCi?= =?UTF-8?q?t=C3=A9=5Fdes=5FSciences.pdf,=20autres=20formats/URLs=5Fdes=5Fp?= =?UTF-8?q?ads=5F-=5Fconf=C3=A9rence=5FRMS.md,=20autres=20formats/lieux=5F?= =?UTF-8?q?pour=5Fla=5Fconf=C3=A9rence=5Fde=5FRMS.odt,=20autres=20formats/?= =?UTF-8?q?lieux=5Fpour=5Fla=5Fconf=C3=A9rence=5Fde=5FRMS.pdf,=20lieux=5Fp?= =?UTF-8?q?our=5Fla=5Fconf=C3=A9rence=5Fde=5FRMS.md,=20finalisation=20cit?= =?UTF-8?q?=C3=A9=20des=20sciences.md,=20Recevoir=5FRichard=5FStallman.md,?= =?UTF-8?q?=20r=C3=A9ponse=5F=C3=A0=5Fla=5FCit=C3=A9=5Fdes=5FSciences.md,?= =?UTF-8?q?=20organisation.md=20Deleted=20README.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 92 - Recevoir_Richard_Stallman.md | 1864 +++++++++++++++++ ...nalisation_cité_des_sciences__obsolete_.odt | Bin ...nalisation_cité_des_sciences__obsolete_.pdf | Bin .../Organisation.odt | Bin .../Organisation.pdf | Bin .../Recevoir_Richard_Stallman.odt | Bin .../Recevoir_Richard_Stallman.pdf | Bin .../Réponse_à_la_Cité_des_Sciences.odt | Bin .../Réponse_à_la_Cité_des_Sciences.pdf | Bin .../URLs_des_pads_-_conférence_RMS.md | 0 .../lieux_pour_la_conférence_de_RMS.odt | Bin .../lieux_pour_la_conférence_de_RMS.pdf | Bin finalisation cité des sciences.md | 218 ++ lieux_pour_la_conférence_de_RMS.md | 228 ++ organisation.md | 740 +++++++ réponse_à_la_Cité_des_Sciences.md | 165 ++ 17 files changed, 3215 insertions(+), 92 deletions(-) delete mode 100644 README.md create mode 100644 Recevoir_Richard_Stallman.md rename Finalisation_cité_des_sciences__obsolete_.odt => autres formats/Finalisation_cité_des_sciences__obsolete_.odt (100%) rename Finalisation_cité_des_sciences__obsolete_.pdf => autres formats/Finalisation_cité_des_sciences__obsolete_.pdf (100%) rename Organisation.odt => autres formats/Organisation.odt (100%) rename Organisation.pdf => autres formats/Organisation.pdf (100%) rename Recevoir_Richard_Stallman.odt => autres formats/Recevoir_Richard_Stallman.odt (100%) rename Recevoir_Richard_Stallman.pdf => autres formats/Recevoir_Richard_Stallman.pdf (100%) rename Réponse_à_la_Cité_des_Sciences.odt => autres formats/Réponse_à_la_Cité_des_Sciences.odt (100%) rename Réponse_à_la_Cité_des_Sciences.pdf => autres formats/Réponse_à_la_Cité_des_Sciences.pdf (100%) rename URLs_des_pads_-_conférence_RMS.md => autres formats/URLs_des_pads_-_conférence_RMS.md (100%) rename lieux_pour_la_conférence_de_RMS.odt => autres formats/lieux_pour_la_conférence_de_RMS.odt (100%) rename lieux_pour_la_conférence_de_RMS.pdf => autres formats/lieux_pour_la_conférence_de_RMS.pdf (100%) create mode 100644 finalisation cité des sciences.md create mode 100644 lieux_pour_la_conférence_de_RMS.md create mode 100644 organisation.md create mode 100644 réponse_à_la_Cité_des_Sciences.md diff --git a/README.md b/README.md deleted file mode 100644 index c5feb52..0000000 --- a/README.md +++ /dev/null @@ -1,92 +0,0 @@ -# Evénementiel - - - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://git.a-lec.org/a-lec/commissions/communication/evenementiel.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://git.a-lec.org/a-lec/commissions/communication/evenementiel/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. diff --git a/Recevoir_Richard_Stallman.md b/Recevoir_Richard_Stallman.md new file mode 100644 index 0000000..8b31213 --- /dev/null +++ b/Recevoir_Richard_Stallman.md @@ -0,0 +1,1864 @@ + +Here's the info packet about my speeches. This information is + +essential for planning my visit and speech. Please forward + +it to anyone who is interested in organizing a speech for me. + + + +Please discuss with me what the topic of this speech should be. + +We need to decide it together. + + + +My talks are not technical. The topics of free software, copyright vs + +community, and digital inclusion deal with ethical/political issues + +that concern all users of computers. The topics of GPL version 3 and + +software patents are mainly of of interest to people that work with + +software. + + + +My usual speech about the Free Software Movement and GNU takes a + +little over 1.5 hours in English, plus time for questions, photos, + +distribution of FSF things, and so on. It is best to allow plenty of + +time for questions, because people usually want to ask a lot of + +questions. In total, it is best to allow 2.5 hours. + +"GNU" is pronounced as one syllable with a hard g, + +like "grew" but with n instead of r. + +The topics I speak about are + + Free Software and Your Freedom + + (alternate titles: + + The Free Software Movement and the GNU/Linux Operating System, + + Free Software in Ethics and in Practice) + + Copyright vs Community in the Age of Computer Networks + + The Danger of Software Patents + + The GNU General Public License + + What we've changed in version 3, and why + + A Free Digital Society + + (alternate title, What Makes Digital Inclusion Good or Bad?) + +These topics take about an hour and a quarter in English, + +plus time for questions, photos, signatures, etc. I suggest + +allowing at least two hours. + +Each topic takes substantially longer in other languages. + +I can also possibly speak about some other topic if you suggest one. + + + +Abstract: + +For a speech about Free Software, you can use this abstract: + + The Free Software Movement campaigns for computer users' freedom + + to cooperate and control their own computing. The Free Software + + Movement developed the GNU operating system, typically used together + + with the kernel Linux, specifically to make these freedoms possible. + +or + + Richard Stallman will speak about the goals and philosophy of the + + Free Software Movement, and the status and history of the GNU + + operating system, which in combination with the kernel Linux is + + now used by tens of millions of users world-wide. + +For Copyright vs Community, you can use this abstract: + + Copyright developed in the age of the printing press, and was designed + + to fit with the system of centralized copying imposed by the printing + + press. But the copyright system does not fit well with computer + + networks, and only draconian punishments can enforce it. + + The global corporations that profit from copyright are lobbying + + for draconian punishments, and to increase their copyright powers, + + while suppressing public access to technology. But if we + + seriously hope to serve the only legitimate purpose of + + copyright--to promote progress, for the benefit of the + + public--then we must make changes in the other direction. + +For The Danger of Software Patents, you can use this abstract: + + Richard Stallman will explain how software patents obstruct + + software development. Software patents are patents that cover + + software ideas. They restrict the development of software, so + + that every design decision brings a risk of getting sued. Patents + + in other fields restrict factories, but software patents restrict + + every computer user. Economic research shows that they even + + retard progress. + +For The GNU General Public License + + Richard Stallman wrote the first GNU General Public License in + + 1989, and version 3 which was completed in 2007. He will discuss + + the philosophy of the GNU GPL, the changes made in version 3, + + and the reasons for those changes. + +For A Free Digital Society + + Activities directed at ``including'' more people in the use of digital + + technology are predicated on the assumption that such inclusion is + + invariably a good thing. It appears so, when judged solely by + + immediate practical convenience. However, if we also judge in terms + + of human rights, whether digital inclusion is good or bad depends on + + what kind of digital world we are to be included in. If we wish to + + work towards digital inclusion as a goal, it behooves us to make sure + + it is the good kind. + + + +Brief bio: + +Richard Stallman launched the free software movement in 1983 and + +started the development of the GNU operating system (see www.gnu.org) + +in 1984. GNU is free software: everyone has the freedom to copy it + +and redistribute it, with or without changes. The GNU/Linux system, + +basically the GNU operating system with Linux added, is used on tens + +of millions of computers today. Stallman has received the ACM Grace + +Hopper Award, a MacArthur Foundation fellowship, the Electronic + +Frontier Foundation's Pioneer Award, and the the Takeda Award for + +Social/Economic Betterment, as well as several honorary doctorates. + +(A longer version is available if you want it.) + + + +Photo: + +There is a black-and-white photograph of me as a + +5820K Encapsulated Postscript file ([http://www.stallman.org/rms-bw.eps)](http://www.stallman.org/rms-bw.eps)) + +3762K JPEG file ([http://www.stallman.org/rms-bw.jpeg)](http://www.stallman.org/rms-bw.jpeg)), and + +5815K TIFF file ([http://www.stallman.org/rms-bw.tiff)](http://www.stallman.org/rms-bw.tiff)). + +Other photos can be found on stallman.org. + + + +Asking for the text: + +I don't write my speeches in advance--that would take too much time. + +However, transcripts of my past speeches are available. If you can + +make a transcript of my speech after I give it, that would be quite + +useful. + + + +Breaks: + +I absolutely refuse to have a break in the middle of my speech. + +Once I start, I will go straight through. + + + +Participation in a larger event: + +I am selective about the events I participate in. If you are inviting + +me to speak at a larger event, please inform me now of the overall + +nature of the event, so I can make an informed decision about whether + +to participate. + +I usually decline to participate in "open source" or "Linux" events. + +See [http://www.gnu.org/gnu/gnu-linux-faq.html](http://www.gnu.org/gnu/gnu-linux-faq.html) for why it is incorrect + +to refer to the operating system as "Linux". + +"Open source" is the slogan of a position that was formulated as a + +reaction against the free software movement. Those who support its + +views have a right to promote them, but I disagree with them and I + +want to promote the ideals of free software. See + +[http://www.gnu.org/philosophy/free-software-for-freedom.html](http://www.gnu.org/philosophy/free-software-for-freedom.html) for more + +explanation of the difference. However, I will agree to participate + +in events labeled "Free Software and Open Source", provided that my + +speech is not the principal draw of the event. + + + +Erecting a larger event: + +If you are thinking of erecting a larger event around my speech, which + +includes inviting other speakers to speak before or after me, please + +talk with me about the plans for that larger event \_before\_ inviting + +other speakers. I want to make sure the event entirely supports the + +goals and principles I work for, and I want to review the publicity + +plans for the event. + + + +Multiple events: + +If you would like me to give speeches in other cities, other + +institutions, or other events which you are not organizing directly, + +please put rms-a...@gnu.org in touch directly with their organizers. + +We need to show them this info packet, and we need to discuss various + +issues with them just as we discuss the issues of your event with you. + +Communication through a middleman is asking for confusion, so please + +don't ask us to do that. + + + +Venues and planning: + +All my talks are aimed at the general computer-using public. They are + +not technical. With good, broad publicity, many people will come -- + +usually hundreds. + +So don't aim small. Please plan each speech in a large room, then + +plan the publicity to bring people in to fill it. Please do not + +suggest scheduling a "small speech", because that makes no sense as a + +goal. I would always rather reach as many people as I feasibly can. + +If the speech is at a university, please do the publicity all around + +the university. Don't limit it to your department! We also want + +people from off-campus to come, so please inform local IT businesses, + +user groups, and other relevant organizations. + +We will also want to inform the region's daily newspapers so they can + +put the speech in their calendar sections, and anything else we can + +think of. Each additional interested person who comes means an increase + +in the results achieved by the speech. + +Make sure you inform the public that my talk is not technical, so + +anyone interested in ethics and use of computers might wish to come. + + + +Facilities: + +A microphone is desirable if the room is large. No other facilities + +are needed. I do not have slides or any sort of presentation + +materials. + +A supply of tea with milk and sugar would be nice. If it is tea I + +really like, I like it without milk and sugar. With milk and sugar, + +any kind of tea is fine. I always bring tea bags with me, so if we + +use my tea bags, I will certainly like that tea without milk or sugar. + +If I am quite sleepy, I would like two cans or small bottles of + +non-diet Pepsi. (I dislike the taste of coke, and of all diet soda; + +also, there is an international boycott of the Coca Cola company for + +killing union organizers in Colombia and Guatemala; see + +killercoke.org.) However, if I am not very sleepy, I won't want + +Pepsi, because it is better if I don't drink so much sugar. + + + +Languages: + +I can speak in English, French, and Spanish. + +If the audience won't be comfortable with a language I can speak, it + +is important to have translation. However, consecutive translation + +is not feasible, because it would more than double the length of the + +speech. Please do not ask me to do that--I will refuse. + +I have found it works to do simultaneous translation without special + +systems: I speak into the ear of the interpreter, and the interpreter + +speaks to the microphone. This avoids the need for special + +transmitters and headsets. However, it does require an interpreter + +capable of doing simultaneous translation for more than an hour. + +Do not propose doing this with a person whose translation skills + +are not adequate for this. + +Another method is to set up a microphone and speaker system for the + +interpreter in a far corner of the room, or a balcony. If the + +speakers are set up suitably, people there can hear the interpreter + +well, while people in the front of the room can hear me well. + +I can try to give a shortened free software speech (about 30 minutes + +of material). With consecutive translation it will take an hour or + +more. I will be forced to omit many important points in the usual + +speech. I do not like to omit so much. + +If we have simultaneous translation, please make a recording + +of the translation. It will be very useful, and it is easy to do. + +Any sound recorder, next to the interpreter, will do it. + + + +Restricting admission: + +If you plan to restrict admission to my speech, or charge a fee for + +admission, please discuss this with me *personally in advance* to get + +my approval for the plan. If you have imposed charges without my + +direct personal approval, I may refuse to do the speech. + +I'm not categorically against limiting admission or fees, but + +excluding people means the speech does less good, so I want to make + +sure that the limitations are as small as necessary. For instance, + +you can allow students and low-paid people and political activists to + +get in free, even if professionals have to pay. We will discuss what + +to do. + +Another method, which works very well in some places, is to allow + +people to attend gratis but charge for a certificate of attendance. + +If the certificate is given by an educational institution, many will + +find it useful for career advancement, while the others could enter + +gratis. Whether this would be effective in your country is something + +you would need to judge. + + + +Sponsors: + +If corporations sponsor my talk, I am willing to include a small + +tasteful note of thanks in announcements and brochures, but no more + +than that. There should be no descriptions of their products or + +services, and no banners with their names. If a would-be sponsor + +insists on more than that, we have to do without that sponsor. + +If my speech is part of a pre-existing larger event that I have agreed + +to participate in, I can't impose such conditions for the whole event. + +However, if banners will be on display next to me while I am speaking, + +that is rather obnoxious; if they advertise organizations that I + +disapprove of on ethical grounds (which is not unlikely) I would want + +to take them down, cover them up, or turn them off during my speech. + + + +Directing publicity: + +My main speech topics are not technical. They are about political + +issues regarding the use of software, and anyone concerned about + +ethical issues with effects on our daily lives should be concerned + +about them. Thus, when planning to publicize my talk, don't direct + +the publicity primarily at computing organizations and computer + +science departments. That would only reach a fraction of the people + +who might be interested. Please also contact political science + +departments, economics departments, philosophy departments, music + +departments, and student groups interested in freedom and human rights + +issues. Let's aim to make the speech reach as many interested people + +as possible. + +The speech topics of software patents and GPLv3 are of interest + +specifically to the IT field, so those you can publicize among IT + +contacts. + + + +Avoiding errors in publicity: + +The GNU Project constantly struggles against two widespread mistakes + +that undermine the effectiveness of our work: calling our work "open + +source", and calling the GNU operating system "Linux". Another very + +bad mistake is using the term "intellectual property". + +The Free Software Movement and the Open Source Movement are like two + +political parties in our community. I founded the Free Software + +Movement in 1984 along with the GNU Project; we call our work "free + +software" because it is software that respects the users freedom. The + +Open Source Movement was founded, in 1998, specifically to reject our + +idealistic philosophy--they studiously avoid talking about freedom. + +See [http://www.gnu.org/philosophy/free-software-for-freedom.html](http://www.gnu.org/philosophy/free-software-for-freedom.html) for + +more explanation of the difference between the two movements. + +So please make sure that all the publicity about the event (web site, + +email announcements, conference programs, direct mail, signs, etc), + +uses the term "free software", not "open source", when you refer to + +work that includes mine. This includes to the title and descriptions + +of my speech, of the session it is in, of the track it is part of, and + +of the event itself. + +Of course, some of these names and descriptions may not refer to this + +work at all; for example, if a track or the whole event covers a much + +broader topic in which free software is just a small part, its name + +may not refer to free software. That is normal and appropriate. The + +point is not to ask you to refer to this work more often than you + +normally would, but that you should describe it accurately whenever + +you do refer to it. + +If other speakers in the same session, track, or event want their work + +to be categorized as "open source", that is a legitimate request for + +them to make. In that case, please give "free software" equal mention + +with "open source". + +If you think it is useful to tell people how free software relates to + +open source, you can say that "since 1998, another group has used the + +term `open source' to describe a related activity." That will tell + +people that my work has a relationship with "open source", which they + +may have heard of, without implying it is right to describe my work as + +"open source." + +The other widespread confusion is the idea of a "Linux operating + +system". The system in question, the system that Debian and Red Hat + +distribute, the system that tens of millions of people use, is + +basically the GNU operating system, with Linux added as the kernel. + +When people call the whole system "Linux", they deny us the credit for + +our work, and this is not right. (See + +[http://www.gnu.org/gnu/linux-and-gnu.html](http://www.gnu.org/gnu/linux-and-gnu.html) for more explanation.) + +So please call this combined operating system "GNU/Linux" in all + +the publicity, in the titles and description of the session, track, + +event, etc., if and when you have reason to refer to it. + +For similar reasons, please don't use a penguin as a symbol for my + +work, or on the posters or notices for my speech. The penguin stands + +for "Linux"; the symbol of GNU is a gnu. So if you want to use a + +graphical image to symbolize GNU or my work, please use a gnu. + +If you have handled these issues well, nobody who looks at your + +material will get the impression that I work on "open source", or that + +I support "open source", or that my work is "part of Linux", or that I + +participated in the "development of Linux", or that GNU is the name of + +"a collection of tools". + +As for the term "intellectual property", that spreads confusion and + +hostile bias. See [http://www.gnu.org/philosophy/words-to-avoid.html](http://www.gnu.org/philosophy/words-to-avoid.html) + +for explanation. I hope you will decide to reject that expression, as + +I do; but in any case, don't use it in connection with my speech. + +Please do not mention non-free GNU/Linux distros (for instance, + +Ubuntu) in the publicity for the event. + +If you have doubts about a poster or announcement, please ask my + +assistant to check it for you, not me. Send it to rms-a...@gnu.org. + + + +Selling Free Software, Free Society: + +Please sell copies of my book of essays, Free Software, Free Society, + +if you can. In the US, Canada, Spain, Italy and Japan, you can obtain + +published copies of this book in English, Spanish, Italian, and + +Japanese. You don't need to put up any money to do this. Please talk + +with rms-a...@gnu.org about how to do it. In the US and Canada, the + +FSF will ship you these books. + +Outside those four countries, please print copies of the book to sell + +at the event, if you can. The English version is available in + +[http://shop.fsf.org/product/free-software-free-society-2/](http://shop.fsf.org/product/free-software-free-society-2/) (278 pages). + +There is also my semiautobiography, Free As In Freedom, in + +[http://shop.fsf.org/product/free-as-in-freedom-2/](http://shop.fsf.org/product/free-as-in-freedom-2/) (245 pages). + +He Spanish version of Free Software, Free Society (318 pages) is in + +[http://www.gnu.org/philosophy/fsfs/free\_software.es.pdf](http://www.gnu.org/philosophy/fsfs/free\_software.es.pdf). + +If you use ordinary copying, and avoid fancy covers and bindings, we + +can sell them for two or three times the cost of copying, and they + +will still be cheap enough that many people will buy them. From the + +proceeds you will first retain the cost of printing; we can divide the + +gains between your organization and the FSF. + +If you see any obstacle, whatever it is, don't just give up. Talk + +with rms-a...@gnu.org about it! Most of the problems that might + +seem difficult to you, we are already accustomed to solving. Give us + +a chance to overcome the obstacle! + + + +At the speech: + +Please put out a pad of paper for people to write down their names and + +email addresses if they want to be on the FSF's mailing list. + + + +Changes of plans: + +Don't assume that I can still come if you change the date, or even the + +hour. My schedule is tight, and any change may make the plan + +impossible. Please consult with me before making any change, and I + +will see what I can do. + +My assistant cannot approve such changes; you must ask me directly, + +and get approval from me directly. I will certainly be flexible if + +there is no obstacle. + + + +Scheduling other meetings: + +I have agreed to give a speech for you, and if the press wants to talk + +with me, I will do that for the sake of the cause. However, if you + +would like me to give additional speeches or go to additional + +meetings, please ask me first. Please ask me about *each* activity + +you would like me to perform. + +Many people assume that because I am traveling, I am having a + +vacation--that I have no other work to do, so I can spend the whole + +day speaking or meeting with people. Some hosts even feel that they + +ought to try to fill up my time as a matter of good hospitality. + +Alas, it's not that way for me. + +The fact is, I have no vacations. (Don't feel sorry for me; idleness + +is not something I wish for.) I have to spend 6 to 8 hours *every + +day* doing my usual work, which is responding to email about the GNU + +Project and the Free Software Movement. Work comes in every day for + +me, and if I skip it one day, I have to catch up another day. During + +the week I usually fall behind; on weekends I try to catch up. + +Traveling takes up time, so I will be extra busy during my visit. And + +it might be nice if I could do at least an hour or two of sightseeing + +during the visit. So please ask me *in advance* about *each* + +additional speech, meeting, or other activity that would take time. I + +don't mind being asked, and I may say yes, but I also may say no. + +Remember that an additional speech, even if it is just a one-hour + +speech, probably takes up two hours counting questions, autographs, + +etc. And then there is the travel time. + + + +Interviews: + +I am glad to give interviews to the press about the GNU system, but + +before I do, I want to be sure they will not repeat the two common + +mistakes (calling the whole system "Linux" and associating GNU or me + +with "open source"). Please explain this, and ask the journalist if + +he will agree to call the system "GNU/Linux" in the article, and to + +make it clear that our work is "free software" not "open source". + +Recommend reading [http://www.gnu.org/gnu/linux-and-gnu.html](http://www.gnu.org/gnu/linux-and-gnu.html) and + +[http://www.gnu.org/philosophy/free-software-for-freedom.html](http://www.gnu.org/philosophy/free-software-for-freedom.html) for + +explanations of these issues. If the journalist agrees, then I agree + +to an interview. Please have this discussion by email, and save the + +messages in both directions. + +Sometimes a journalist gives a response which sounds vaguely + +affirmative or sympathetic but its words do not really say "yes". + +Examples are "I will do this as much as I can" and "I understand the + +distinction." Such an answer is actually just "maybe", so when you + +receive one, please ask for clarification. If he says that the editor + +has the final decision, please respond with "Would you please consult + +the editor now, and tell us a firm decision?" + + + +Recorded interviews for broadcast: + +It is ok to do these either before or after my speech, and they + +usually need to be done one at a time, so I am willing to do them that + +way. + + + +Interviews not for broadcast: + +Please do not propose to hold these interviews before the conference. + +That order wastes my time. So please propose to hold them AFTER the + +conference. + +Also please ask journalists to *see my speech* before the interview. + +My speeches are not technical; they focus on precisely the sort of + +philosophical questions that a journalist would probably want to + +cover. If the journalist has not attended my speech, he will probably + +start by asking me to answer the same questions that I answer in the + +speech. That is a waste of time for me. + +If you schedule a press conference or group interview, please *plan + +the time of my speech to allow the interview after it*. It may be a + +good idea to find out from journalists what times are good for them, + +then schedule the conference, then schedule the speech before it. + +This way, they will all be able to get the full picture. + +It is also ok to have the interviews the day after the speech. + +That is another way to have them after the speech rather than before. + +If the journalists simply cannot do the interview after the speech, + +then I will do it before the speech if possible. But please insist + +that they watch or listen to a recording on audio-video.gnu.org of + +another speech. + +It is also a good idea for the journalist to read + +[http://www.gnu.org/gnu/the-gnu-project.html](http://www.gnu.org/gnu/the-gnu-project.html) as well as + +[http://www.gnu.org/gnu/gnu-linux-faq.html](http://www.gnu.org/gnu/gnu-linux-faq.html) + +[http://www.gnu.org/philosophy/free-sw.html](http://www.gnu.org/philosophy/free-sw.html) + +[http://www.gnu.org/philosophy/categories.html](http://www.gnu.org/philosophy/categories.html) + +[http://www.gnu.org/philosophy/words-to-avoid.html](http://www.gnu.org/philosophy/words-to-avoid.html) + +[http://www.gnu.org/philosophy/compromise.html](http://www.gnu.org/philosophy/compromise.html) + +[http://stallman.org/articles/internet-sharing-license.en.html](http://stallman.org/articles/internet-sharing-license.en.html) + +[http://stallman.org/articles/ebooks.pdf](http://stallman.org/articles/ebooks.pdf) before the interview. Those + +articles provide important background. This is especially important + +for anyone who cannot come to my speech first. + +Please ask each journalist to agree to make a recording of the + +interview. Written notes tend to simplify, and often lead to + +incorrect quotes. + +I am willing to meet with any number of journalists, but if there are + +many, I can't meet all of them individually (it would take too much + +time). So what I will do is give private interviews to 2 or maybe 3 + +of them, whichever ones you think are most important, and see the rest + +of them as a group (i.e. in a press conference). + +You and your associates can judge better than I do which journalists + +and which publications I should focus on. So I would like you to + +advise me about that. Please try to judge both the importance of the + +publication and the merits (intelligence, attention to accuracy, + +openness of mind, and absence of bias) of the journalist, if you can. + + + +Recording my speech: + +Please do record the speech if you can. We are always looking for + +good recordings of my speeches, both audio and video, to put on line. + +The GNU Project keeps an on-line audio and video collection of speech + +recordings in audio-video.gnu.org. If you are making an audio or + +video recording of my speech, please write to audio...@gnu.org in + +advance for advice on how to make a recording that is good for further + +use, and subsequently to arrange to install your recording on our + +site. + +When you are making a recording, please *make sure* to tell me when + +the tape needs to be changed. I will pause. Please help me help you + +make the recording complete. + + + +Recording formats: + +Please make sure that your recording is not compressed with a + +substantially lossy codec (unless it is an Ogg codec). If we have to + +transcode the file, starting from a lower-quality base will reduce the + +quality of the result. + +It is best to provide audio recordings in the original recorded sample + +rate, up to 44100Hz. Monophonic is generally adequate for speech + +recordings and saves a lot of space over stereo. + +For video recordings, please save the master recording, which will + +probably be in miniDV format. + +Please don't transcode recordings from one format to another before + +sending to us, unless they have such a high bit rate that files are + +impractically large. If you do need to encode or transcode, please + +convert audio to 64Kbps mono Ogg Vorbis (or you could try Ogg Speex), + +and convert video to Matroska VP8 or to Ogg Theora with video quality + +set to 5 or more. If you need advice for how to do this, please ask + +audio...@gnu.org. + + + +Putting my speech on the net: + +If you would like to put my speech on the Internet, or distribute it + +in digital form, I insist on using the formats of the free software + +community: Ogg Vorbis or Ogg Speex format for audio, and Matroska VP8 + +(Webm) or Ogg Theora for video. Please do not distribute my speech in + +any other format. + +Please do not ever broadcast or publish my speeches in formats that + +are not good for free software. I will not speak to make a recording + +or broadcast that requires non-free software to be heard or viewed. + +Don't use RealPlayer format, or Quicktime, or Windows Media Player + +format, or a patented format such as MPEG2, MPEG4, or MP3. + +This requirement is very important, because if it is not followed, + +viewing my speech will require people to do the exact opposite of what + +I ask them to do. The medium's message would contradict my message. + +Because this is so important, please make sure everyone who might be + +involved in broadcasting the event, or who might be directly or + +indirectly involved in planning such a broadcast, knows this + +requirement in advance of the event. + +You can get advice and help in distributing Ogg files from Mallory + +Knodel . + + + +Streaming the speech: + +Streaming is a kind of Internet distribution, so everything in the + +previous section applies. In particular, you must use only Ogg format + +or Matroska VP8 (Webm). + +If you want to stream my speech but you have not done streaming in Ogg + +or VP8 before, don't leave the matter till the last minute. By then, + +it will be too late. Please try a test session two weeks before the + +speech. That way, if you encounter any problem, there will be time to + +resolve it before the speech. + +If you have previously done streaming using some streaming service and + +you can't immediately name the format it uses, chances are it is + +unacceptable and I won't let you use it for my speech. So please + +check, two weeks in advance, what format it uses. If you find it uses + +some bad format, you will have time to arrange for ethical streaming. + +You can get advice and help in Ogg streaming from Mallory Knodel + +. Please ask two weeks before the event; they + +can do it faster faster, but why make their work hectic unnecessarily? + +See [https://support.mayfirst.org/wiki/live-video-streaming-support](https://support.mayfirst.org/wiki/live-video-streaming-support) for + +more info. + + + +Remote speeches by video connection: + +I can do a speech remotely through a videoconferencing system. This + +can be done by Internet or by ISDN. For good quality by Internet, we + +need a maximum of 100msec response time for ping between your site and + +where I am, and 100kbytes/sec transfer rate. + +Using two or three ISDN lines gives good quality but the calls cost + +money. If I am at home, there is a facility I can use at no charge; + +you would have to pay for the ISDN calls and for the facilities at + +your end. If I am somewhere else (which is true more than half the + +time), then we will need to find a videoconferencing facility for me + +to use; most likely you will need to pay for that. + + + +Warning about giveways: + +You may find companies offering you CD-ROMs, books, fliers or + +publicity materials to give away or sell at my speech. Please check + +them before you accept them, to make sure that they don't promote the + +very thing that we are working to replace. + +For instance, the CDs may contain non-free software. Most distros of + +GNU/Linux contain or suggest non-free software in addition to the free + +software. (And most of them call the system "Linux".) Please check + +with me before you allow a CD of GNU/Linux to be distributed at the + +event. + +Books about use of the GNU/Linux system and about GNU programs are + +fine if they themselves are also free. But many of them are non-free + +(see [http://www.gnu.org/philosophy/free-doc.html)](http://www.gnu.org/philosophy/free-doc.html)). To see if a book + +is free, check the license on the back of the title page. If it uses + +the GNU Free Documentation License, or the Open Publication License + +version 1 without options A and B, then it is free. If it isn't one + +of those, please show me the license and I will tell you if it is a + +free license. + +If companies send you publicity materials, please check with me before + +giving them out at my speech. + + + +Flights: + +The FSF does not pay for my travel, and I can't afford to. I will + +need you to arrange to cover the cost of my traveling to and from your + +city (unless I've told you someone else will do it). + +I am traveling most of the time, and most of my trips include several + +stops. Chances are your city is neither the first nor the last stop + +in the trip. Please don't make assumptions about the itinerary; + +instead, please ask me for whatever information you need. + +Many organizations ask to buy the tickets and send them to me. I do + +not object to that method in principle, but it typically assumes the + +trip goes to just one city. That approach is hard to use for a + +multi-destination trip, unless you want to pay for the whole trip. So + +normally I buy the tickets myself and get reimbursed by the various + +places I am visiting. For a multi-destination trip, we will need to + +agree on what parts of the travel expenses you should cover. + +Some organizations feel that hospitality calls for providing me with a + +business class ticket. That is indeed more comfortable, but an + +economy class seat is good enough. Meanwhile, speaking is my main + +source of income, and the extra price of a business class ticket would + +be a lot more useful for me if I can spend it on something else. So + +if you were thinking of spending extra for business class, how about + +if you pay the extra to me as a speaker's fee instead? + +We should plan for me to arrive (at the site itself, not just at the + +airport) at least 24 hours before the speech; that way, even if the + +flight is cancelled, there is a good chance I can still arrive in time + +for the speech by taking the same flight the next day. + + + +Lost tickets: + +If you are not paying me a speaking fee, but you are paying for the + +airline tickets, I must insist that you cover the costs if I have to + +replace a lost ticket, the fee for changing the ticket if I miss a + +flight, or any other surprise expenses associated with my travel to + +and from your location. + +This might seem unfair--if a ticket is lost, it could be my fault. + +But my income is not large, and I cannot afford to assume this risk + +myself if the event offers me no income. The frustration I feel when + +I suffer such a loss is excruciating. It is better for me to decline + +to travel to a certain place than to take such a risk. + + + +Bus and train tickets: + +If you buy bus or train tickets for me, do not give my name! Big + +Brother has no right to know where I travel, or where you travel, or + +where anyone travels. If they arbitrarily demand a name, give a name + +that does not belong to any person you know of. If they will check my + +ID before I board the bus or train, then let's look for another way + +for me to travel. (In the US I never use long-distance trains because + +of their ID policy.) + +Don't give them your name either: please pay for the ticket in cash. + + + +Other expenses: + +I expect you to cover expenses such as visa fees, fees for mailing my + +passport back and forth, taxis to and from the airport, and so on. + + + +Accommodations: + +I am willing to stay in a hotel if there is no other way. + +Please book the hotel for me and arrange to pay the hotel directly. + +But please DON'T make a hotel reservation until we have fully explored + +other options. If there is anyone who wants to offer a spare couch, I + +would much rather stay there than in a hotel (provided I have a door I + +can close, in order to have some privacy). Staying with someone is + +more fun for me than a hotel, and it would also save you money. + +My distaste for a hotel is less if it does not know my name, but + +staying in a house with people is normally more enjoyable than staying + +alone. + +Many countries have a law that hotels must report all guests to the + +police. In most cases, this orwellian policy applies not only to + +foreigners like me, but to citizens as well! The citizens should be + +outraged by this, but often they are not. + +Please call the hotel and ask whether they will demand to see my + +passport, and whether they report all their guests to the police. If + +it has this policy, please join me in striking a blow against Big + +Brother, by looking for a place I can stay in that doesn't demand to + +see my passport, or report my visit to anyone. If the police want + +information about free software, they are welcome to come to my + +speech. + +If you have found a person for me to stay with, please forward this + +section and the two following sections to that person. + + + +Temperature: + +Above 72 fahrenheit (22 centigrade) I find sleeping quite difficult. + +(If the air is dry, I can stand 23 degrees.) A little above that + +temperature, a strong electric fan blowing on me enables me to sleep. + +More than 3 degrees above that temperature, I need air conditioning to + +sleep. + +If there is a substantial chance of indoor temperatures too hot for + +me, please arrange \_in advance\_ for me to have what I need. + +If you are planning for me to stay in a hotel, DO NOT take for granted + +that the hotel has air conditioning--or that it will be working when I + +arrive. Some hotels shut off their air conditioning systems for part + +of the year. They often think it is unnecessary in seasons when the + +temperature is usually in the mid 20s--and they follow their schedule + +like stupid robots even if there is a heat wave. + +So you must explicitly ask them: "Do you have air conditioning? Will + +it be functioning for the dates XXX-YYY?" + +In some hotels with central air conditioning, it simply does not work + +very well: it can make a room less hot, but can't make it cool. + +Before using a hotel that has central air conditioning, find out what + +temperature it can actually lower a room to, during the relevant + +dates. + +Or look for a hotel that has a real cooling unit in the room, not a + +central system. Those tend to work well enough, if they are not + +broken. + + + +Pets: + +I like cats if they are friendly, but they are not good for me; I am + +somewhat allergic to them. This allergy makes my face itch and my + +eyes water. So the bed, and the room I will usually be staying in, + +need to be clean of cat hair. However, it is no problem if there is a + +cat elsewhere in the house--I might even enjoy it if the cat is + +friendly. + +Dogs that bark angrily and/or jump up on me frighten me, unless they + +are small and cannot reach much above my knees. But if they only bark + +or jump when we enter the house, I can cope, as long as you hold the + +dog away from me at that time. Aside from that issue, I'm ok with + +dogs. + +If you can find a host for me that has a friendly parrot, I will be + +very very glad. If you can find someone who has a friendly parrot I + +can visit with, that will be nice too. + +DON'T buy a parrot figuring that it will be a fun surprise for me. To + +acquire a parrot is a major decision: it is likely to outlive you. If + +you don't know how to treat the parrot, it could be emotionally + +scarred and spend many decades feeling frightened and unhappy. If you + +buy a captured wild parrot, you will promote a cruel and devastating + +practice, and the parrot will be emotionally scarred before you get it. + +Meeting that sad animal is not an agreeable surprise. + + + +Email: + +It is very important for me to be able to transfer email between my + +laptop and the net, so I can do my ordinary work. While traveling, I + +often need to do the work and the transfer late at night, or in the + +morning before a departure. So please set up a way I can connect to + +the net from the place I am staying. + +I do NOT use browsers, I use the SSH protocol. If the network + +requires a proxy for SSH, I probably can't use it at all. + +If a hotel says "We have internet access for customers", that is so + +vague that it cannot be relied on. So please find out exactly what + +they have and exactly what it will do. If they have an ethernet, do + +they have a firewall? Does it permit SSH connections? What + +parameters does the user need to specify in order to talk with it? + +Please check those things directly, or ask the people who actually run + +the network. If you talk with someone who doesn't understand what + +"SSH connection" means, or if he doesn't understand the difference + +between "Internet" and "web browsing", that person is not competent to + +give reliable information. Don't rely on information from such a + +person--talk to someone who knows! + +For reasons of principle, I am unwilling to identify myself in order + +to connect to the Internet. For instance, if a hotel gives a user + +name and password to each room, I won't use that system, since it + +would identify me. I would need some other way to connect. + +A modem connection is fine if it works, so please verify in advance + +that the telephone line you expect me to use has a modular jack and + +that it works to call the ISP from that line. Hotels in Europe and + +Asia often have peculiar phone systems; the staff may tell you it is + +possible to call an ISP from the hotel *but they may be wrong*. For + +instance, their phone switchboard may not recognize the tones produced + +by modems. The only way to tell for certain is to go to the hotel, + +try phoning with a computer from a guest room, and see if it actually + +works. Until you have tested it, don't believe it! + +My ISP phone numbers are old; I don't know if they will still work. + +If you propose I use a modem, please find a number I can call. It is + +best if you lend me a permanent account that someone else uses, one + +that will continue working afterward, so that I can use it again if I + +come back or use it from other places in the region. Hotel phone + +rates may be high; I expect you to cover them. However, I normally + +connect to the net only for around ten minutes at a time, twice a day, + +so the total won't be too big. + +If I need to use a dialup connection, please cover the costs of the + +telephone calls I will need to transfer my email -- especially in a + +hotel. Some hotels charge a lot of money for this. + +Wireless modems mostly do not work with my machine, so do not plan on + +my using one. I won't refuse to use them if you have an expert who + +can make it work, but success is rare. If it involves loading a + +nonfree driver, I will refuse. + + + +Paying me a reimbursement or a fee: + +Please pay my reimbursement or fee to me personally; do not pay it to + +the FSF. The FSF and I have completely separate finances, and the FSF + +never pays for my travel. The FSF welcomes donations, but please make + +sure that money intended for me is not sent to them, because moving it + +afterward would mean accounting headaches as well as extra work. + +My assistant is not involved with my finances, so she cannot help you + +with that issue. Please send questions about payments to me directly. + +If you pay me by check, and you're not in the US, make sure to get a + +check that lists a corresponding US bank--otherwise it will cost me a + +fee to deposit the check. Please mail the check \_in US dollars\_ to: + + Richard Stallman + + 77 Mass Ave rm 32-381 + + Cambridge MA 02139 + + Phone number: +1-617-253-8830 + +Do not mail it to the FSF! + +A wire transfer is also a good method of payment. I will send you the + +coordinates; ask if you need them. The bank you use will charge a + +fee, and my bank charges me $10 for each incoming transfer; please add + +those fees to the amount, rather than taking them out of what I + +receive. + +If you are outside the US, please convert your currency to dollars in + +your bank, then use one of the above methods to pay me the dollars. + +My bank gives very bad exchange rates; yours is surely better. + +Cash is also fine. + +If you want an invoice, I will be glad to give you one. Let's work + +out what it should say by email before I arrive. Please also check + +before the visit whether you need any other forms, such as tax forms. + +I would like to be able to take care of any necessary forms while I am + +there, rather than wait till afterward. + + + +Hospitality: + +Please pass this section to everyone who will be helping me directly + +in any fashion during the visit. + +It is nice of you to want to be kind to me, but please don't offer + +help all the time. In general I am used to managing life on my own; + +when I need help, I am not shy about asking. So there is no need to + +offer to help me. Moreover, being constantly offered help is actually + +quite distracting and tiresome. + +So please, unless I am in grave immediate danger, please don't offer + +help. The nicest thing you can do is help when I ask, and otherwise + +not worry about how I am doing. Meanwhile, you can also ask me for + +help when you need it. + +One situation where I do not need help, let alone supervision, is in + +crossing streets. I grew up in the middle of the world's biggest + +city, full of cars, and I have crossed streets without assistance even + +in the chaotic traffic of Bangalore and Delhi. Please just leave me + +alone when I cross streets. + +In some places, my hosts act as if my every wish were their command. + +By catering to my every whim, in effect they make me a tyrant over + +them, which is not a role I like. I start to worry that I might + +subject them to great burdens without even realizing. I start being + +afraid to express my appreciation of anything, because they would get + +it and give it to me at any cost. If it is night, and the stars are + +beautiful, I hesitate to say so, lest my hosts feel obligated to try + +to get one for me. + +When I'm trying to decide what to do, often I mention things that + +MIGHT be nice to do--depending on more details, if it fits the + +schedule, if there isn't a better alternative, etc. Some hosts take + +such a tentative suggestion as an order, and try moving heaven and + +earth to make it happen. This excessive rigidity is not only quite + +burdensome for other people, it can even fail in its goal of pleasing + +me. If there is a better alternative, I'd rather be flexible and + +choose it instead--so please tell me. If my tentative suggestion + +imposes a lot of trouble on others, I want to drop it--so please tell + +me. + +When you need to tell me about a problem in a plan, please do not + +start with a long apology. That is unbearably boring, and unnecessary + +-- conveying useful information is helpful and good, and why apologize + +for that? So please be practical and go straight to the point. + +If I am typing on my computer and it is time to do something else, + +please tell me. Don't wait for me to "finish working" first, because + +you would wait forever. I have to squeeze in answering mail at every + +possible opportunity, which includes whenever I have to wait. I wait + +by working. If instead of telling me there is no more need for me to + +wait, you wait for me to stop waiting for you, we will both wait + +forever -- or until I figure out what's happening. + + + +Dinners: + +If you are thinking of setting up a lunch or dinner for me with more + +than 4 people total, please consider that as a meeting, and discuss it + +with me in advance. Such meals draw on my strength, just like + +speeches and interviews. They are not relaxation, they are work. + +I expect to do work during my visit, but there is a limit on the + +amount of work I can handle each day. So please ask me in advance + +about any large planned meal, and expect me to say no if I have a lot + +of other work already. If we are having a meal that I did not agree + +to as a large meal, and other people ask if they can join, please tell + +them no. In both cases, please tell them that I need a chance to + +relax after the other work I will have done. + +Please don't be surprised if I pull out my computer at dinner and + +begin handling some of my email. I have difficulty hearing when there + +is noise; at dinner, when people are speaking to each other, I usually + +cannot hear their words. Rather than feel bored, or impose on + +everyone by asking them to speak slowly at me, I do some work. + +Please don't try to pressure me to "relax" instead, and fall behind on + +my work. Surely you do not really want me to have to work double the + +next day to catch up (assuming I even COULD catch up). Please do not + +interfere as I do what I need to do. + + + +Food: + +I do not eat breakfast. Please do not ask me any questions about + +what I will do breakfast. Please just do not bring it up. + +I enjoy delicious food, and I like most kinds of cooking if they are + +done well (the exception being that I cannot eat anything very spicy). + +If I am ordering from the menu in a restaurant which has a variety, + +there's no need for you to worry about the question of what I like; I + +will take care of it. + +But if you want to cook for me, or invite me to a restaurant that + +specializes in just one thing, or invite me to dinner with a preset + +menu, you need to know what I dislike: + + avocado + + eggplant, usually (there are occasional exceptions) + + hot pepper + + olives + + liver (even in trace quantities) + + stomach and intestine; other organ meats + + cooked tuna + + oysters + + egg yolk, if the taste is noticeable, except when boiled completely hard + + many strong cheeses, especially those with green fungus + + desserts that contain fruit or liqueur flavors + + sour fruits, such as grapefruit and many oranges + + beer + + coffee (though weak coffee flavor can be good in desserts) + + the taste of alcohol (so I don't drink anything stronger than wine) + +Don't ever try to decide what food I should eat without asking me. + +Never assume that I will surely like a certain dish, merely because + +most people do. Instead, ask me in advance! + +As long as there are many alternatives to choose from, there will be + +no problem. + + + +Wine: + +Wine is not very important to me--not like food. I like some wines, + +depending on the taste, and dislike others, but I don't remember the + +names of wines I have liked, so it is useless to ask me. + +Therefore, if you're having dinner with me, please don't ask me what + +to do about wine. I can't decide intelligently, and it matters more + +to others than to me. Have wine or don't, as you prefer; choose it to + +please yourself and the others, not for me. + +If you get a bottle of wine, I will taste it, and if I like the taste, + +I will drink a little, perhaps a glass. + + + +Restaurants: + +So I like to go to restaurants that are good at whatever kind of food + +they do. I don't arrive with specific preferences for a kind of food + +to eat--rather, I want to have whatever is good there: perhaps the + +local traditional cuisine, or the food of an immigrant ethnic group + +which is present in large numbers, or something unusual and original. + +So please don't ask me "Where do you want to eat?" or "What kind of + +restaurant do you want to go to?" I can't make an intelligent + +decision without knowing the facts, and unless I am already familiar + +with the city we're in, I can only get those facts from you. + +The only general thing I can tell you is that what I like or dislike + +about a meal is the sensation of eating the food. Other things, such + +as the decor of a restaurant, or the view from its windows, are + +secondary. Let's choose the restaurant based on its food. + +A good approach is to ask around *in advance* among your acquaintances + +to find people who like good food and are familiar with the area's + +restaurants. They will be able to give good recommendations. + + + +Sightseeing: + +If I am visiting an interesting city or region, I will probably want + +to do a few hours of sightseeing in between the work. But don't try + +to plan sightseeing for me without asking me first--I can only spare a + +limited time for it, so I am selective about where to go. Please + +don't assume I want to see something just because it is customary to + +take visitors there. That place may be of no interest with me. + +Instead, please tell me about possible places to visit--then I can say + +what I would like. + +I enjoy natural beauty such as mountains and rocky coasts, ancient + +buildings, impressive and unusual modern buildings, and trains. I + +like caves, and if there is a chance to go caving I would enjoy that. + +(I am just a novice as a caver.) I often find museums interesting, + +but it depends on the subject. + +I tend to like music that has a feeling of dance in it, but I + +sometimes like other kinds too. However, I usually dislike the + +various genres that are popular in the US, such as rock, country, rap, + +reggae, techno, and composed American "folk". Please tell me what + +unusual music and dance forms are present; I can tell you if I am + +interested. If there is a chance to see folk dancing, I would + +probably enjoy that. + +If there is something else interesting and unique, please tell me + +about it. Maybe I will be interested. + + + +More arrangements: + +Once we have a precise date for the speech, my assistant will contact + +you with questions about the arrangements for the trip. Please + +respond as soon as possible with the information she asks for. + +Please do not ever mail me a file larger than 100k without asking me + +first. I almost certainly do not want to receive it in that form. If + +you would like feedback or approval for proposed publicity, please + +talk with rms-assist about it, not with me. If you want to give me + +data about airplane tickets, please send that info as plain ASCII + +text, not as images or PDFs. Thank you. + +-- + +Dr Richard Stallman + +President, Free Software Foundation + +51 Franklin St + +Boston MA 02110 + +USA + +www.fsf.org www.gnu.org + +Skype: No way! That's nonfree (freedom-denying) software. + + Use free telephony [http://directory.fsf.org/category/tel/](http://directory.fsf.org/category/tel/) diff --git a/Finalisation_cité_des_sciences__obsolete_.odt b/autres formats/Finalisation_cité_des_sciences__obsolete_.odt similarity index 100% rename from Finalisation_cité_des_sciences__obsolete_.odt rename to autres formats/Finalisation_cité_des_sciences__obsolete_.odt diff --git a/Finalisation_cité_des_sciences__obsolete_.pdf b/autres formats/Finalisation_cité_des_sciences__obsolete_.pdf similarity index 100% rename from Finalisation_cité_des_sciences__obsolete_.pdf rename to autres formats/Finalisation_cité_des_sciences__obsolete_.pdf diff --git a/Organisation.odt b/autres formats/Organisation.odt similarity index 100% rename from Organisation.odt rename to autres formats/Organisation.odt diff --git a/Organisation.pdf b/autres formats/Organisation.pdf similarity index 100% rename from Organisation.pdf rename to autres formats/Organisation.pdf diff --git a/Recevoir_Richard_Stallman.odt b/autres formats/Recevoir_Richard_Stallman.odt similarity index 100% rename from Recevoir_Richard_Stallman.odt rename to autres formats/Recevoir_Richard_Stallman.odt diff --git a/Recevoir_Richard_Stallman.pdf b/autres formats/Recevoir_Richard_Stallman.pdf similarity index 100% rename from Recevoir_Richard_Stallman.pdf rename to autres formats/Recevoir_Richard_Stallman.pdf diff --git a/Réponse_à_la_Cité_des_Sciences.odt b/autres formats/Réponse_à_la_Cité_des_Sciences.odt similarity index 100% rename from Réponse_à_la_Cité_des_Sciences.odt rename to autres formats/Réponse_à_la_Cité_des_Sciences.odt diff --git a/Réponse_à_la_Cité_des_Sciences.pdf b/autres formats/Réponse_à_la_Cité_des_Sciences.pdf similarity index 100% rename from Réponse_à_la_Cité_des_Sciences.pdf rename to autres formats/Réponse_à_la_Cité_des_Sciences.pdf diff --git a/URLs_des_pads_-_conférence_RMS.md b/autres formats/URLs_des_pads_-_conférence_RMS.md similarity index 100% rename from URLs_des_pads_-_conférence_RMS.md rename to autres formats/URLs_des_pads_-_conférence_RMS.md diff --git a/lieux_pour_la_conférence_de_RMS.odt b/autres formats/lieux_pour_la_conférence_de_RMS.odt similarity index 100% rename from lieux_pour_la_conférence_de_RMS.odt rename to autres formats/lieux_pour_la_conférence_de_RMS.odt diff --git a/lieux_pour_la_conférence_de_RMS.pdf b/autres formats/lieux_pour_la_conférence_de_RMS.pdf similarity index 100% rename from lieux_pour_la_conférence_de_RMS.pdf rename to autres formats/lieux_pour_la_conférence_de_RMS.pdf diff --git a/finalisation cité des sciences.md b/finalisation cité des sciences.md new file mode 100644 index 0000000..ffa4311 --- /dev/null +++ b/finalisation cité des sciences.md @@ -0,0 +1,218 @@ + +*Orga - finalisations + + + +Ce document comprend les dernières finalisations à voir entre : + + neox, wilder, Richard Stallman et David Forgeron + + + +# A discuter entre nous + +Planning + + * 13h - 15h : installation (stand + conf), formation, simulation + * Demander si possibilité de venir avant 13h (voir carrément le matin) + * Si on à le temps : aider Parinux dans son Install Party + * 15h - 17h : conférence + * 17h - 18h : Q/A + * 18h - 19h : on range et on discute + + + + +Interactions avec les autres associations + + * Si le temps le permet, nous aiderons Parinux dans son Install Party de 14h à 15h. + * L'AFUL est normalement présente (Odile et Jean-Yves) pour nous aider dans l'installation et l'animation le stand + + +Ressources humaines + + * Qui au stand ? => quelqu'un de a-lec à tout moment + * Qui à la réal ? => 2 personnes et neox pour la montée en compétence + * Qui pour transmettre les questions à RMS ? + * Qui pour introduire RMS ? + * Qui sera le contact de M. Forgeron ? + + +Valider l'orga des Q/A + + * Questions des auditeurs à Richard : + * par micro + * par papiers écrits gros + * Doit on lui faire parvenir les questions en amont ? + * NON + + +Billets de train ou d'avion à prévoir (en cours) + + + +Hébergement : chez Antoine + + + +Quels type de tables / chaises (hautes ou basses) nous souhaitons installer pour le stand ET la conf ? + +neox voit avec RMS pour la conf + +à réfléchir pour le stand + + + +Se mettre d'accord avec RMS sur : + +nom de la conf + + * + +sujet de la conf + + * Les principes du logiciel libre et la différence entre libre et open source + * Les compagnies qui disent faire du logiciel libre mais font de l'open source pour contrôler les utilisateurs + * Le capitalisme de surveillance qui profite de l'open source et les enjeux pour l'avenir + * Le matériel dont la conception est libre : free hardware design + * demandes spéciales : + * thé, lait, sucre, pepsi (a confirmer) + * bloc note et stylo pour la mailing list (a confirmer) + * micro cravate + + + * ... + + +# A envoyer à David Forgeron + + + +disposons-nous de notre propre instance peertube, où comptons-nous utiliser une instance publique ? + + * la notre si elle fonctionne + * si elle fontionne pas, on utilisera probablement celle de framatube + + +quelles-sont les modalités techniques requises par peertube pour le direct ? + + * flux OBS + + +RMS à-t-il formulé des demandes spécifiques quand à l'organisation de la conférence ? + + * Port du masque fortement conseillé pour tous les auditeurs pour se protéger (lui-même a une santé fragile) + * Ventilation + * Enregistrement et diffusion ok (attention à prévoir un accès sans javascript) + * point hébergement et voyage (voir avec le CA) + * besoin de table et chaise + * ordinateur + tableau / écran pour projeter des diapos + * si possible microphone qui s'attache à la chemise (ne pas avoir à le tenir dans les mains) + * utilisation de papiers pour poser des questions (problèmes auditifs) + + + + + + +Combien de participants physiques ? (pour le parking gratuit) + +neox estime ce nombre à grand max 10 + +demander aux membres via la mailing list "membres" + +(Le mieux c'est de de mettre un lien vers un pad et leur demander d'écrire leur nom pour éviter l'avalanche d'emails) + + + +Envoyer un mail à M. Forgeron avec les indications importantes : + +titre de la conférence + +horaires + +les sujets abordés + +les specificités a aborder ou elements graphiques a partager. + +De leur côté, ils nous mettront dans la liste des partenaires. + + + +Demander la charte pour bien les nommer dans nos communications (nom, logo, etc) + + + + + +Lui donner les horaires définitifs (matin ou aprèm) + +- de la rencontre avec lui a la cité + +- de la conf + +- de l'install / désinstall du matériel + +- des temps de batement + + + + + +# A recevoir de la part de M. Forgeron + +combien de temps avant l'ouverture on a pour l'install ? + +(Plus on a de temps mieux c'est) + + + +Les trotinettes sont-elles permises ? + + + +RMS est-il accepté ? + + + +# entretien avec Nicolas Thierry + +Considératins : + +pas le meme public que la Cité + +demarcher du public potentiellement + + + +Logistique + +il doit trouver quelqu'un pour organiser cela : + + trouver une salle + +Il va envoyer quelques mails et contacts en région parisienne + + + +amphi ~100-150 voir 400 places + + + +Nous aiderons pour + +install-desinstall + +accueillir des gens + +stand + + + +peut etre pas le temps de mobiliser tout ca + +evenement en parallele de samuel les 2,3,4,5 + +possible captation vidéo + +jitsi box diff --git a/lieux_pour_la_conférence_de_RMS.md b/lieux_pour_la_conférence_de_RMS.md new file mode 100644 index 0000000..0328fb9 --- /dev/null +++ b/lieux_pour_la_conférence_de_RMS.md @@ -0,0 +1,228 @@ + +# Cité des Sciences + +2022-05-13 - wilder contacte la Cité des Sciences + +- échange avec le secrétariat : ne connaissent ni le libre, ni les communs, ni RMS + +- redirection vers Hadrien Palluy, IDEM + +- redirection vers David Forgeron, qui me propose un entretien téléphonique + + + +2022-05-18 - wilder à un entretien téléphonique avec David Forgeron + +- présentations mutuelles + +- explication du besoin + +- Favorable mais doit demander la permission d'inviter RMS en amont + + + +2022-05-21 - RMS à un imprévu à 17h (réunion FSF) + +- wilder tente de joindre la Cité plusieurs fois en vain + +- wilder laisse un message à M. Forgeron + +- neox tente de voir si possibilité d'héberger RMS chez le président du CA + + + +2022-05-22 - RMS maintient les dates originelles, plus d'imprévu + +- neox prévient wilder de la situation + +- wilder s'excuse de la gène occasionnée auprès de M. Forgeron + + + +2022-05-23 - refus de M. Forgeron + +- Après échange avec sa hierarchie, M. Forgeron décline notre proposition + +- raison : RMS Gate + +- La Cité des Sciences reste ouverte à d'autres propositions + + + +2022-05-24 - Appel du CA + +- le CA envoie un email afin de faire appel à cette décision + + + +2022-05-25 - Réponse de M. Forgeron à l'Appel du CA + +- M. Forgeron remonte les arguments du CA à sa hierarchie + +- M. Forgeron nous demande de contacter M. Laurent Ricard (son n+1) + +- Le CA contact M. Laurent Ricard + + + +2022-05-XX - Réponse de M. Ricard à l'Appel du CA + +- + + + +------------------------------------------------------ + + + +# Université Paris Cité (ex Paris 7) + +2022-05-23 - wilder à contacté M. Di Costa + +- en attente de sa réponse + +2022-05-24 - wilder à contacté la Directrice du département informatique + +- ils ne peuvent pas me donner le numéro de téléphone de M. Di Costa + +- ils ne peuvent pas lui transmettre de message + +- personne ne peut prendre la décision à sa place + +2022-05-27 - relance de wilder + +- j'ai relancé M. Di Costa + +2022-05-XX - réponse de M. Di Costa + +- + + + +------------------------------------------------------ + + + +# Université Paris Sud + +2022-05-23 - wilder à contacté M. Nicolas Thiery (sur recommendation d'Odile Bénassy) + +- explication du besoin par téléphone + +- mail récapitulatif qu'il à partagé à son entourage + +2022-05-25 - retour de M. Thiery + +- plusieurs emails faisant part du fait que le RMS gate est un serieux handicap + +- Odile Bénassy confirme que la "communauté du libre" fait de la pensée unique + +2022-05-XX - retour positif d'un des contacts de M. Thiery + +- + + + +------------------------------------------------------ + + + +# Salle de conférence à proximité de la Gard du Nord + +2022-05-23 - wilder à contacté M. Thomas Watanabe (sur recommendation de Jean-Yves Jeannas) + +- En attente de sa réponse + +2022-05-27 - wilder à relancé Thomas Watanabe + +- j'ai relancé M. Watanabe + +2022-05-27 - wilder obtient un entretien téléphonique avec M. Watanabe + +- je lui explique notre besoin + +- on échange brièvement au sujet de la polémique RMS + +- je lui fait un mail récapitulatif l'enjoignant à partager à toute personnes susceptible de nous aider + +- il va voir ce qu'il peut faire mais ne garantit rien + +2022-05- - réponse de M. Watanabe + +- + + + +------------------------------------------------------ + + + +# L'Anticafé du Beaubourg + +2022-05-25 - wilder à trouvé un lieu gratuit (!) sur Paris + +- j'ai expliqué notre besoin à Neo Nomade pour obtenir l'anticafé (35 places) + +- en attente de réponse + +[https://www.neo-nomade.com/espace/4081/cafe-coworking-paris-anticafe-beaubourg](https://www.neo-nomade.com/espace/4081/cafe-coworking-paris-anticafe-beaubourg) + +2022-05-XX - réponse de Neo Nomade + +- + + + +------------------------------------------------------ + + + +# Salon Libre en Communs + +2022-05-23 - Jérôme a proposé sur le salon "Libres en communs" où il y a plus de monde, l'idée de faire appel à une mairie prêtant une salle. + +2022-05-23 - Proposition d'un des membres + +- + + + +------------------------------------------------------ + + + +# CNRS + +2022-05-23 - Jérôme a demandé à un copain qui travaille au CNRS. + +- en attente de retour + +2022-05-XX - retour de l'ami en question + +- + + + +------------------------------------------------------ + +Maisons de la Vie Associative et Citoyenne de Paris + +2022-05-26 - wilder à contacté toutes les maisons de la vie associative et citoyenne de paris + +2022-05-XX - Réponse + +- + + + +------------------------------------------------------ + + + +# Université de Nanterre + +2022-05-31 - wilder contacte l'UFR informatique de l'Université de Nanterre + + + + diff --git a/organisation.md b/organisation.md new file mode 100644 index 0000000..f3df4b0 --- /dev/null +++ b/organisation.md @@ -0,0 +1,740 @@ + +**Organisation du 4 juin 2022** + +# RÉCAP + +## Qu'est-ce qui se passe ? + +Richard Stallman, le fondateur de la Free Software Foundation, sera de passage à Paris entre le 1er et le 4 juin. + +A cette occasion, il nous a proposé de dédier l'une de ses journées de conférences à Libre en Communs ! + + + +## Pourquoi ce pad ? + +Afin que tout le monde puisse participer, je vous propose de formuler vos suggestions sur ce pad, comme par exemple : + + * des propositions sur l'organisation + * des associations / personnes à inviter : + * des suggestions d'activités + * des questions pour M. Stallman + + +C'est pour nous l'opportunité d'organiser un événement mémorable dans l'histoire de notre jeune association qui compte aujourd'hui 28 membres, alors n'hésitez pas a participer :) + + + +# Recueil de propositions + +## Réponses de RMS + +Demandes spéciales: + + * Port du masque fortement conseillé pour tous les auditeurs pour se protéger (lui-même a une santé fragile) + * Ventilation + * Enregistrement et diffusion ok (attention à prévoir un accès sans javascript) + * sujet (voir 4.3) + * point hébergement et voyage (voir avec le CA) + * besoin de l'écran pour la première partie de conférence (diapos) + * besoin de table et chaise + * si possible microphone qui s'attache à la chemise (ne pas avoir à le tenir dans les mains) + * utilisation de papiers pour poser des questions (problèmes auditifs) + + +## Autres suggestions + +### Jean-Yves JEANNAS de l'AFUL + +Je peux animer ou participer à une table ronde si vous voulez. J'ai aussi quelques ateliers/conférences/animations disponibles, sur le Libre ou les communs numériques. Je peux aussi trouver d'autres intervenants. + +Ou juste faire de la publicité. + + + +# Logistique + +## Recherche de lieu + + * ~~Université Paris 7 ? (Courriel envoyé à R. Di Cosmo)~~ + * ~~Espace Saint-Martin (payant) fermé le 4 juin~~ + * ~~Cité des Sciences : en attente de retour de notre 'appel'~~ + * ~~Maison de la Recherche (54 Rue de Varenne, 75007 Paris)~~ + * ~~Centre de conférence VERSO (52 Rue de la Victoire, 75009 Paris)~~ + * ~~Le Deux Cent Cinquante Trois (253 Rue du Faubourg Saint-Martin, 75010 Paris)~~ + * **VALIDÉ : ESPACE VINCI (25 Rue des Jeûneurs, 75002 Paris)** + + +## Participants + + * Jean-Yves JEANNAS de l'AFUL : OK + * Parinux : OK + * Odile Bénassy (AFUL/FSF) : OK + * Bastien Guerry : OK si disponible + * Membres de Libre en Communs + + +## Accès au lieu + + * Métro Bonne nouvelle ou Grands boulevards + + +## Le stand Libre en Communs + +Cette section décrit le stand que l'association tiendra lors de l'événement. + +Sur les tables, on trouvera : + + * des dépliants Chalec + * des autocollants + * des formulaires d'adhésion + * des formulaires de don + + +Quelque part : + + * bannière Libre en Communs (Avons-nous une ou plusieurs bannières? Ne faut-il pas mettre une bannière à proximité du pupitre ou en tout cas dans le périmètre dans lequel sera le conférencier? une seule bannière) + + +Matériel fourni par le lieu ? + + + + * Chaises + * Tables + * Micro-cravate + * Video-projecteur et écran + * Connexion internet (wifi) + filaire + * ~~Caméra 360~~ + + +Animateurs du stand : + + * il faut quelqu'un qui reste sur le stand pour accueillir et répondre aux questions + * volontaire(s) : + + + + +# Déroulement de l'après-midi + +## Installation du matériel : 13h30 + +Il faudra préparer la salle de conférence pour RMS. Doivent être présents et fonctionnels : + + * PC, rétroprojecteur et câbles + * micro cravate pour RMS, micro classique pour la salle, haut parleurs et câbles +abaisser le bon nombre de sièges si nécessaire + +prendre en main le contrôle de la salle : + + * éclairage, son, climatisation + * sièges, volets, portes, fond blanc +Effectuer une simulation de la présentation + +Lors des Questions / Réponses, prévoir une personne dont le rôle est de : + + * transmettre le papier sur lequel la question est écrite à RMS + + + + +## Petits ateliers + +Faire vivre le stand - quelqu'un doit y rester + +Nous nous relaierons pour qu'a tout moment quelqu'un soit présent + + + +## Conférence de RMS : 15h00 + +Cette conférence de Richard Stallman aura pour sujet les *Libertés du logiciel et du matériel.* + + + +## Questions / Réponses pour RMS + +Utilisation de petits papiers et/ou du micro pour les faire passer. + +Note : RMS a des problèmes d'audition, l'écrit semble une meilleure idée + + + +### Questions: + +1. Technique + +1.1. Peut-on imaginer un ou plusieurs noyaux qui fonctionneraient avec GNU? + + => Il y'a déja: Exemple: Guix qui supporte HURD et GNU/Linux, mais peut être que la question est plus large que juste supporter plusieurs noyaux. + + A noter que la glibc supporte déjà 2 noyaux (HURD et Linux) et peut potentiellement en supporter plus (il y-a des patches pour au moins 1 noyau BSD). Dans ce cas il faut aussi voir ce qui change au niveau compatibilité des applications quand on change de noyau et garde la même libc. + + Pour les noyaux BSD, Hyperbola (et peut être d'autres distributions GNU/Linux?) travaillent sur utiliser un noyau BSD avec la glibc (pour une compatibilitée acrue avec les logiciels libres existants). + +1.2. Quelles seraient les pistes pour favoriser l'émergence du matériel libre? + + + +2. Société + +2.1. Le logiciel Libre peut-il être un vecteur de paix entre les individus? + +2.2. Est-ce que les 4 libertés incluent la notion d'éthique dans le rapport entre les fournisseurs de service et les utilisateurs? + +2.3. Comment réussir à diffuser l'usage du logiciel libre dans les écoles, les associations et les organismes internationaux? + +2.4. Le logiciel Libre a-t-il une ambition universelle intemporelle lui permettant d'aller au-delà des tendances politiques qui risquent de créer des murailles entre les différentes communautés libristes internationales? + +2.5. Comment sensibiliser les populations qui n'acceptent plus les guerres informationnelles des puissances d'argent et qui veulent construire un monde en adéquation avec des valeurs de partage et de développement durable? + +2.6. Comment promouvoir le logiciel libre auprès des populations qui s'intéressent aux monnaies libres, à l'habitat écologique, et à un mode de vie moins destructeur pour notre environnement? + +2.7. Peut-on imaginer le logiciel libre comme un moyen d'une révolution pacifique qui construirait un monde en parallèle du monde que nous ne voulons plus et qui pourrait disparaître de lui-même? + +2.8. Le logiciel libre peut-il être une solution pour ne pas subir ou pour réduire les effets d'une surveillance de masse qui semble s'accentuer sur la dernière decennie en France? + +2.9. La recherche et le Logiciel Libre? + + -> Exemples: INRIA: coq, cocinelle, sagemath etc? + + * -> très intéressant si Bastien Guerry peut venir + -> Importance croissante du code qui est utile dans la recherche et la publication en libre? + + -> Recherches économiques ou sociologiques sur le logiciel libre? (Democratizing innovation, Benjamin Mako Hill) ? + + + + + +3. Economie + +3.1. Quel(s) modèle(s) économique(s) pour le logiciel Libre? + +3.2. L'arrivée des cryptomonnaies permettra-t-elle l'emergence de modèles économiques alternatifs viables pour les acteurs du libre ? + +3.3. Quelle est la différence entre logiciel libre et open-source? A qui profite la confusion? + + Quelles stratégies peut on mettre en oeuvre face à l'open-source? Quelles stratégies éviter? + + -> Peut on récupérer une partie de l'Open Source? + + -> Pas mal de monde dit Open Source mais entend libre à la place + + -> Certains projets communautaires pourraient potentiellement changer de terminologie + +3.4 Collaborations fructueuses entre les projets 100% libres et moins libres + + Exemple: Coreboot et Libreboot (jusqu'à ce que libreboot disparaisse au profit d'osboot) + + => Quelles stratégies communes mettre en oeuvre (upstreamer dans Coreboot par exemple)? + + => Comment arriver à négocier entre 2 projets au niveau de la communication + + (Coreboot pourrait faire plus la pub que c'est pas 100% libre et libreboot pourrait renvoyer + + vers Coreboot pour tout ce qui n'est pas supporté)? + + Exemple opposé: Guix et distributions dérivées (l'upstream est Guix). + + => Tentions entre l'usage et le 100% libre + + + +4. Futur + +4.1. Quel avenir pour le logiciel libre? + + + + 5. Éducation + +5.1. Identifier les difficultés qui limitent un accès populaire massif au logiciel libre. (enfermement culturel, technicité, diffusion spécialisée, communautarisme,...) + + + +# Communication + +Cette section décrit les communications qui devront être effectuées ainsi que les canaux associés. + + + +## Réseaux sociaux + +### Fedivers/Mastodon + + * 1 toot au plus tôt pour annoncer + * 1 toot la veille + * 1 toot le jour J + + +[https://toot.a-lec.org/@a\_lec/108398236117267924](https://toot.a-lec.org/@a\_lec/108398236117267924) + + + + * Libre en Communs vous propose de rencontrer Richard Stallman, le père du logiciel libre, lors d'une conférence le 4 juin prochain avec pour sujet les Libertés du logiciel et du matériel \o/ + * + + * La conférence aura lieu le 4 juin de 15h00 à 18h00 à l'Espace Vinci au 25 Rue des Jeûneurs à Paris et sera diffusée en flux direct sur [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + * + + * L'entrée est gratuite dans la limite des places disponibles, alors n'hésitez-pas ! + * + + * #rms #libre #matériel #logiciellibre #communs + + +### Messagerie XMPP + +Message dans salons xmpp : sécurité et vie privée, membres, Chalec, Libre en Communs, auto-hébergement + +1 toot la veille devrait suffire pour pas spammer + + + + * Bonjour tout le monde ! + * + + * L'association Libre en Communs vous propose de rencontrer Richard Stallman, le fondateur du mouvement du logiciel libre, lors d'une conférence qui aura lieu le 4 juin prochain \o/ + * + + * Ce sera l'occasion pour vous d'en savoir plus sur les enjeux et les défis que doivent relever les acteurs du logiciel et du matériel libres en 2022. + * Une session de Questions / Réponses est également au planning, et vous permettra d'échanger directement avec M. Stallmann ! + * + + * L'événement se tiendra à l'Espace Vinci (Paris) et l'entrée sera gratuite ! + * Une retransmission en direct sera également disponible sur notre instance Peertube. + * + + * Enfin, pensez à porter le masque, en raison de l'âge et de la santé de notre invité, qui a formulé ce souhait. + * + + * C'est quand ? + * La conférence aura lieu le 4 juin de 15h00 à 17h00. + * La session de querstions / réponses aura lieu de 17h à 18h. + * + + * C'est où ? + * **Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris** + * Infos pratiques : [https://formeret.fr/nos-espaces/espace-vinci/](https://formeret.fr/nos-espaces/espace-vinci/) + * Également diffusé en flux direct sur [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + * + + * Contenu + * La conférence aura pour sujet les *Libertés du logiciel et du matériel* + * + + * + + * + +## Articles + +### LinuxFR [MODERATION] + + * Conférence "Les libertés du logiciel et du matériel" avec Richard Stallman + * + + * L'association Libre en Communs vous propose de rencontrer Richard Stallman, ~~le père du logiciel libre~~ le fondateur du mouvement du logiciel libre, lors d'une conférence qui aura lieu le 4 juin 2022 de 15h à 18h à l'Espace Vinci ~~(Pairs)~~ 25 Rue des Jeûneurs, 75002 Paris + * + + * En effet, nous sommes en 2022 et le monde du libre doit faire face à de nouvelles menaces de taille : logiciel libre et logiciel open source diffèrent à bien des égards et pourtant, la confusion n'a jamais été aussi grande. Les GAFAM voient en l'open source le moyen de conquérir un nouveau marché d'utilisateurs, et n'hésitent pas à dépenser des milliards pour cela. + * + + * Pour ce qui est du matériel, des solutions commencent à voir le jour, et des labels, tels que RYF, pour la compatibilité avec les logiciels libres, apparaissent. Toutefois, la présence d'Intel ME dans tous les nouveaux ordinateurs grand public remet en question les fondements mêmes du logiciel libre et pose la question du matériel libre. + * + + * Vous l'aurez compris, cette conférence sera l'occasion pour vous de mettre à jour vos connaissances sur le sujet et cerise sur le gâteau : une session de questions / réponses avec Richard Stallman est au planning ! + * + + * L'entrée est gratuite, et l'événement est retransmis en direct sur Peertube, alors, n'hésitez-pas ! + * Enfin, pensez à porter le masque, en raison de l'âge et de la santé de notre invité, qui a formulé ce souhait. + * + + * C'est quand ? + * La conférence aura lieu le 4 juin de 15h00 à 17h00. + * La session de querstions / réponses aura lieu de 17h à 18h. + * + + * C'est où ? + * **Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris** + * Infos pratiques : [https://formeret.fr/nos-espaces/espace-vinci/](https://formeret.fr/nos-espaces/espace-vinci/) + * Également diffusé en flux direct sur [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + * + + * Contenu + * La conférence aura pour sujet les *Libertés du logiciel et du matériel* + + +Liens en entête d'article LinuxFR : + + * [https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + * ~~ ~~[https://en.wikipedia.org/wiki/Open-source\_hardware](~~https://en.wikipedia.org/wiki/Open-source\_hardware~~) + * [https://www.fsf.org/](https://www.fsf.org/) + * [https://www.a-lec.org/](https://www.a-lec.org/) + * [https://www.agendadulibre.org/events/25354](https://www.agendadulibre.org/events/25354) + * [https://stallman.org/](https://stallman.org/) + + + + +### FSF + + * Talk with Richard Stallman at the "Libre en Conférences" Paris event + * + + * The french non profit "Libre en Communs" wants you to join Richard Stallman for a talk that will take place on June 4th 2022 at "Espace Vinci" (Paris, FRANCE). + * + + * We're 2022 and the Free Software Movment have to overcoe new challenges : Open source misses the point of Free Software, yet the ambiguity has never been no high. GAFAM know this and spend bilions on Open Source in order to conquer a new market. + * + + * Regarding Free Hardware, new products emerged along with certifications, such as RYF, which ensures lthe compatibility with Free Software. In the meantime, any new mainstream computers ships with Intel ME by default. This threat seriously impacts the very basis of Free Software and emphasizes the ever growing need for Free Hardware. + * + + * Don't miss this opportunity to catch up with the latest developments on the subject and, icing on the cake, you'll also have the chance the ask questions to Richard Stallman during the 1 hour long Q/A ! + * + + * Entry is free and the event is live broadcasted on the non-profit Peertube instance. All welcome ! + * Please don't forget your masks, for M. Stallman is considered a person at hiher risk from coronavirus. + * + + * When ? + * The talk will be on June 4th from 3PM to 5PM. + * The Q/A session will be from 5PM to 6PM. + * + + * Where ? + * **Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris** + * Access : [https://formeret.fr/nos-espaces/espace-vinci/](https://formeret.fr/nos-espaces/espace-vinci/) + * Direct broadcast link : [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + * + + * Contents: + * The subject of the talk will be "Software and hardware Freedoms" + + +## Agendas + +### Agenda du Libre [PUBLIÉE] + +Lien : [https://www.agendadulibre.org/events/25354](https://www.agendadulibre.org/events/25354) + + + +### Agenda militant + + + +Lien : + + + +## Page sur a-lec [PUBLIÉE] + +[https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + + + +Rendez-vous : "Les libertés du logiciel et du matériel" avec Richard Stallman + + + + * L'association Libre en Communs vous propose de rencontrer Richard Stallman, le ~~père~~ fondateur du mouvement du logiciel libre, lors d'une conférence qui aura lieu le 4 juin prochain de 15h à 18h à L'espace Vinci, 25 Rue des Jeûneurs, 75002 Paris + * + + * Nous sommes en 2022 et les acteurs du libre doivent relever de nouveaux défis. Sur le plan logiciel, la confusion entre libre et open source n'a jamais été aussi grande, l'occasion pour les GAFAM de capter un nouveau marché. Sur le plan matériel, l'introduction d'Intel ME redistribue les cartes et vient bousculer les acquis en termes de matériel. + * + + * Cette conférence, bien nommée "Les libertés du logiciel et du matériel", sera l'occasion de vous mettre à jour vos connaissances sur le sujet et cerise sur le gâteau : une session de questions / réponses avec Richard Stallman est au planning ! + * + + * L'événement se tiendra à l'Espace Vinci (Paris) et l'entrée sera gratuite ! + * Une retransmission en direct sera également disponible sur notre instance Peertube. + * + + * Enfin, pensez à porter le masque, en raison de l'âge et de la santé de notre invité, qui a formulé ce souhait. + * + + * En résumé... + * C'est quand ? + * La conférence aura lieu le 4 juin de 15h00 à 17h00. + * La session de querstions / réponses aura lieu de 17h à 18h. + * + + * C'est où ? + * **Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris** + * Infos pratiques : [https://formeret.fr/nos-espaces/espace-vinci/](https://formeret.fr/nos-espaces/espace-vinci/) + * Également diffusé en flux direct sur [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + + + * + + * Contenu + * La conférence aura pour sujet les *Libertés du logiciel et du matériel :* + + + + + + +## Courriels + +### Courriel aux membres [ENVOYÉ] + +Destinataires : membres, CA, Jean-Yves Jeannas, Odile Benassy, Bastien Guerry + + * + + * Bonjour, + * Nous avons le plaisir de vous annoncer que la conférence avec Richard Stallman aura bien lieu ! + * L'événement se tiendra le samedi 4 juin 2022, à l'Espace Vinci (Paris) de 15h à 18h. + * L'entrée est gratuite et pour ceux qui ne peuvent pas se déplacer, une retransmission en direct sera disponible sur notre instance Peertube : + * [https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe](https://video.chalec.org/w/5Y338qZDJvBakEDmoY4jDe) + * Ce sera l'occasion pour vous d'en savoir plus sur les enjeux et les défis que doivent relever les acteurs du logiciel et du matériel libres en 2022. + * Enfin, la dernière heure sera dédiée à une session de questions / réponses et vous permettra d'échanger directement avec Richard Stallman. + * Pensez à porter le masque, en raison de l'âge et de la santé de notre invité, qui a formulé ce souhait. + * Tous les détails ici : [https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + * N'hésitez pas à partager ce message autour de vous, afin de toucher un maximum de monde ! + * Librement, + + +### Courriel d'information [ENVOYÉ] + +Destinataires : ~~AFUL~~, Parinux, chatons.org, NextInpact, developpez.com, Korben + + + +Faire un texte d'information (reprendre l'article LinuxFR) et l'envoyer. + + + +Objet : Conférence de Richard Stallman « Liberté du logiciel et du matériel » le 4 juin 2022 + + + + * Bonjour, + * + + * L'association Libre en Communs reçoit Richard Stallman le 4 juin 2022 à l'Espace Vinci (Paris) pour une conférence intitulée « Libertés du logiciel et du matériel ». + * + + * Conférence de Richard Stallman : « Libertés du logiciel et du matériel » + * Le 4 juin 2022 à 15h + * Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris + * Entrée gratuite, port du masque fortement recommandé + * + + * Nous serions ravis que vous en fassiez la promotion en partageant ce lien : + * [https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + * + + * Richard Stallman est le fondateur du mouvement du logiciel libre, de la Free Software Foundation et du projet GNU. + * + + * Libre en Communs est une association à but non lucratif reconnue d'intérêt général qui fait la promotion du logiciel libre, des communs et des valeurs associées. + * + + * Librement, + + + + + + +### Courriel d'invitation [ENVOYÉ] + +Destinataires : UFRs : Nicolas Thiery, Thomas Watanabe, Brahim Boughezala, Samuel Lelièvre, Roberto DiCosmo + + + +Faire un texte d'invitation (reprendre l'article LinuxFR) et l'envoyer. + + + +Objet : Invitation à la conférence de Richard Stallman « Liberté du logiciel et du matériel » le 4 juin 2022 + + + +L'association Libre en Communs a le plaisir de vous inviter à la conférence de Richard Stallman « Liberté du logiciel et du matériel » le 4 juin 2022 à l'Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris. + + + + * Conférence de Richard Stallman : « Libertés du logiciel et du matériel » + * Le 4 juin 2022 à 15h + * Espace Vinci, 25 Rue des Jeûneurs, 75002 Paris + * Entrée gratuite, port du masque fortement recommandé +* + + + +[https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + + + +Richard Stallman est le fondateur du mouvement du logiciel libre, de la Free Software Foundation et du projet GNU. + + + +Libre en Communs est une association à but non lucratif reconnue d'intérêt général qui fait la promotion du logiciel libre, des communs et des valeurs associées. + + + +Librement, + + + + + +## Ce qui a été fait + + * toot.a-lec.org : [https://toot.a-lec.org/@a\_lec/108398245780767273](https://toot.a-lec.org/@a\_lec/108398245780767273) + * linuxfr.org (dépêche) [x] en attente modération + * XMPP [x] + * Agenda du Libre : [https://www.agendadulibre.org/events/25354](https://www.agendadulibre.org/events/25354) + * Agenda Militant [ ] en attente modération + * Page Libre en Communs [x] [https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html](https://www.a-lec.org/libre-en-conf-04062022-richard-stallman-libertes-du-logiciel-et-du-materiel.html) + * courriel aux membres + liste [x] + * forum.chatons.org [x] [https://forum.chatons.org/t/conference-de-richard-stallman-liberte-du-logicel-et-du-materiel-le-4-juin-2022/3637](https://forum.chatons.org/t/conference-de-richard-stallman-liberte-du-logicel-et-du-materiel-le-4-juin-2022/3637) + * NextInpact [x] ils vont répondre sur contact@a-lec.org + * Developpez.com [x] + * Korben [x] + * AFUL [x] + * FSF [x] ils vont répondre sur contact@a-lec.org + * Parinux [x] + * UFRs [x] + * UFR Informatique de l'Université Paris Diderot [x] + * UFR d'Informatique De Paris VI [x] + * Cité des Sciences [x] + * invitation membres du gouvernement ROFL [ ] + * c'est qui le ministre du numérique ? -> Bruno Lemaire cf [https://fr.wikipedia.org/wiki/Ministre\_charg%C3%A9\_du\_Num%C3%A9rique](https://fr.wikipedia.org/wiki/Ministre\_charg%C3%A9\_du\_Num%C3%A9rique) + * invitation DINUM [x] + * invitation sénateur OUZOULIAS [X] très actif pour les logiciels libres dans les lois, [https://www.senat.fr/senateur/ouzoulias\_pierre19593h.html](https://www.senat.fr/senateur/ouzoulias\_pierre19593h.html) p.ouzoulias@senat.fr TODO Cpm je fais un courriel personnalisé FAIT + * invitation CNIL [x] + * invitaiton Pôle synaptique [ ] + * invitation Mozilla France [x] + * invitation FFDN [x] + * invitation Mediapart [x] + * invitation Blast [x] + * invitation Charlie [x] + * invitation Le Parisien [x] + * invitation Epsiloon [x] ils vont répondre sur contact@a-lec.org + * invitation Pirate Mag [x] + * invitation Parti Pirate [x] ils vont répondre sur contact@a-lec.org + * invitation Octopus (boite de libriste) [x] + * invitation Debian France [x] + * invitation journaliste Marc Rees [https://mastodon.social/@Marcrees](https://mastodon.social/@Marcrees) [ ] + * invitation Stéphane Bortzmeyer [https://mastodon.gougere.fr/@bortzmeyer](https://mastodon.gougere.fr/@bortzmeyer) [x] + * invitation Wikimédia France [x] + * invitation InterHop [x] + * invitation LaMouette (asso LibreOffice) [x] [https://lamouette.org/association/nous-contacter](https://lamouette.org/association/nous-contacter) + * invitation Nos Oignons (noeud tor) [x] + * invitation OpenStreetMap France [x] + * invitation ZDNet [x] + * invitation Isabelle Attard (ex députée) + * invitation réseau Libre entreprise [https://www.libre-entreprise.org/](https://www.libre-entreprise.org/) [x] + * invitation Framasoft [x] + * invitation école 42 [x] + * invitation association 42l [x] [https://42l.fr/Contact](https://42l.fr/Contact) contact@42l.fr + * invitation Ecole du Logiciel Libre [x] + * invitation FrenchTech [x] [https://lafrenchtech.com/fr/contacter/](https://lafrenchtech.com/fr/contacter/) + * invitation Station F [x] [https://stationf.co/contact](https://stationf.co/contact) + * invitation Enercoop [x] + * invitation Henri Verdier [ ] ambassadeur pour le numérique, auteur d'un rapport très progressif + * invitation Benjamin Bayart [x] + * invitation CPU [x] émission de radio [https://cpu.dascritch.net/](https://cpu.dascritch.net/) + * invitation France Culture [x] émission Le meilleur des mondes, [https://www.radiofrance.fr/franceculture/podcasts/le-meilleur-des-mondes/le-meilleur-des-mondes-du-vendredi-29-avril-2022-5686300](https://www.radiofrance.fr/franceculture/podcasts/le-meilleur-des-mondes/le-meilleur-des-mondes-du-vendredi-29-avril-2022-5686300) + + + + +Note pour plus tard : créer sur nuage un carnet d'adresse privé. Bonne idée + + + + + + + +# Jour J + +## Équipe + + * assistant rms : neox + Jérôme + * accueil public : Jean + * animateur du stand Libre en Communs + * porte-micro question du public + * gestion de la vidéo : Nicolas-Alexandre + * photographe : + * retranscription de la conférence (?) : wilder + + +## Courses + + * ~~bouteilles d'eau petit format~~ Une fontaine à eau est à notre disposition \o/ + * tablette de chocolat (Côté d'or ?) + * 2 canette Pepsi fraîches + + + + +# BILAN : Axes d'améliorations + + + +ne pas hésiter à communiquer abondamment sur Mastodon : + + * une semaine avant + * la veille au soir + * le jour même au matin + * juste avant l'événement + * juste après l'événement +SON + + * s'asurer de disposer d'un micro DE QUALITE + * Enregistrer au téléphone au cas où le micro viendrait à couper +VIDEO + + * prévoir des alternatives à notre instance Peertube, prêtes à être utilisées sur le champ en cas de problème technique + * privilégier le 720p pour les petites connexions +COMMUNAUTE + + * prévoir un chat et communiquer dessus EN AMONT + * communiquer sur les problèmes techniques et leur résolution + * répondre aux questions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/réponse_à_la_Cité_des_Sciences.md b/réponse_à_la_Cité_des_Sciences.md new file mode 100644 index 0000000..7d0bd1e --- /dev/null +++ b/réponse_à_la_Cité_des_Sciences.md @@ -0,0 +1,165 @@ + +*Réponse à la Cité des Sciences + +# Cité des Sciences + +Bonjour, + + + +Désolé de ne pas être revenu vers vous plus tôt, mais il a fallu que j'échange pas mal avec mes collègues et ma hiérarchie à ce sujet. + + + +Après discussions, nous allons décliner votre proposition d'accueillir Richard Stallman. Nous ne remettons absolument pas en cause l'impact qu'il a eu sur le logiciel libre dont il est à l'origine du cadre juridique et conceptuel. Cependant, universcience, en tant qu'établissement public, ne peut pas être associé à ses prises de positions, ce serait contraire à l'image que l'établissement souhaite véhiculer auprès de ses visiteurs. + +J'ai bien conscience que tout n'est pas binaire, mais en tant qu'établissement public, nous nous devons d'être exemplaire sur un certain nombre de sujets, que ce soit vis-à-vis de nos tutelles que vis-à-vis de nos visiteurs et visiteuses. + + + +Ceci dit, nous sommes tout à fait ouverts pour d'autres collaborations avec votre association. + + + +En vous souhaitant une bonne journée. + + + +David Forgeron + + + +# Notre réponse + +Bonjour Monsieur, + + + +Merci pour votre réponse. + + + +Nous regrettons, bien sûr, votre décision et **souhaiterions mieux connaitre les raisons** pour lesquelles les prises de positions de Monsieur Richard Stallman vous ont fait décider, en tant qu'établissement public, de surseoir à cette conférence. + + + +Il nous semble que justement, l'établissement public que vous êtes et dont la mission principale est de diffuser la connaissance scientifique au grand public est parfaitement bien placé pour porter un débat sur les enjeux du logiciel libre. + + + +Le logiciel libre, depuis son origine, ne s'est pas développé dans un contexte apaisé. Il constitue même une réaction face aux agissements de nombreux fabricants et développeurs qui ont ouvertement donné priorité à leurs intérêts au détriment de ceux des consommateurs. + +Cependant, dans le cas d'une ressource (commune) aussi fondamentale que l'accès au langage et aux outils de programmation, les enjeux dépassent encore ceux que les organisations de consommateurs défendent habituellement. + + + +L'intérêt scientifique du travail de Monsieur Richard Stallman n'est plus à démontrer et notre association (récemment reconnue d'interêt général) est également porteuse de projets orientés vers les biens communs. + + + +Monsieur Richard Stallman a été victime de campagnes de diffamation et de Cancel Culture. Vous trouverez plus d'information à ce sujet au travers d'un site internet créé pour expliquer le déroulé des évènements ([https://stallmansupport.org/)](https://stallmansupport.org/)) et un article de Loïc Dachary ([https://blog.dachary.org/2020/02/10/how-the-cancel-culture-was-leveraged-against-rms/)](https://blog.dachary.org/2020/02/10/how-the-cancel-culture-was-leveraged-against-rms/)). + + + +Nous ne pensons pas qu'il y ait là matière à lui refuser la parole. + + + +Nous nous permettons de vous rappeler que les innovateurs ont toujours fait l'objet de polémiques et que c'est dans un tel contexte que Jean Perrin, le fondateur du Palais de la Découverte, la maison mère dont vous êtes issus, a courageusement défendu des positions alors révolutionnaires. + + + +Les combats comme celui-là sont la raison même de votre existence. Il se sont bien sûr déplacés en un siècle et il est, plus que jamais, décisif pour les générations que vous avez à instruire, de les repérer, de les comprendre et de promouvoir le débat public. + +Ce rôle est d'autant plus visible quand il s'agit du partage de la connaissance et de l'impact des inégalités de l'éducation sur nos libertés. + + + +Quelle image souhaitez-vous avoir auprès de vos visiteurs ? Y a-t-il un débat qui soit plus au cœur de leurs intérêts et des vôtres ? + + + +À la lumière de ces éléments, nous réitérons donc notre souhait de connaitre les raisons pour lesquelles les prises de positions de Monsieur Richard Stallman vous ont fait craindre pour "l'image de votre établissement". + + + +Nous pensons, pour notre part, qu'il s'agit d'une mauvaise appréciation de la situation et nous tenons prêts, si vous changez d'avis, à poursuivre sur l'organisation initialement envisagée. + + + +Le plus librement du monde, + + + +Le Conseil d'Administration de Libre en Communs + + + + + +# Brouillons + +----------------------------------------------------------------------------------------------------------------------------------- + +Citations de Jean Perrin : + + * La science remplace du visible compliqué par de l'invisible simple. + * + + + +----------------------------------------------------------------------------------------------------------------------------------- + + + +[, en 1910 (ref ???), une position alors révolutionnaire : l'existence des atomes.] + + + +Nous ne pensons donc pas que vous ne portez d'intérêt qu'aux combats d'arrière-garde mais que, bien au contraire, vous incarnez + + + +Oui. Je trouve que vous avez bien arrangé les choses. + +Il faut laisser passer une nuit, peut-être, relire un peu Jean Perrin. + +Si on trouve une belle citation... C'était quelqu'un de bien ! + +Ça me ferait plaisir de leur envoyer une de ses phrases dans les dents ! + +Perrin aurait été là, il les aurait virés ! Sûr ! + + + +A 18h54, après relecture, ça me va. (afk !) + + + +[https://fr.wikipedia.org/wiki/Jean\_Perrin](https://fr.wikipedia.org/wiki/Jean\_Perrin) + + + +Il faudrait prendre appui (citer) les prises de position de jean Perrin (et des autres scientifiques qui l'entourent) dans l'affaire Dreyfus. + +... En 1921, au cours d'une cérémonie à l'Opéra en hommage à Marie Curie, Jean Perrin prononce un discours dans lequel il expose pour la première fois ce que devrait être une politique scientifique pour la France. Il estime que le développement de la science est indispensable au progrès humain et économique. + + + +extrait de : [https://www.palais-decouverte.fr/fileadmin/fileadmin\_Palais/fichiersContribs/au-programme/evenements/nouveau-palais/brochure\_Palais\_FR2025.pdf](https://www.palais-decouverte.fr/fileadmin/fileadmin\_Palais/fichiersContribs/au-programme/evenements/nouveau-palais/brochure\_Palais\_FR2025.pdf) + + + +Fort de son héritage, le Palais de la découverte entend relever le défi d’une science + +ancrée dans son temps. À sa réouverture en 2025, le Palais de la découverte parlera + +de la science contemporaine aux publics de son temps, au moyen d’une proposition + +revisitée, adaptée à l’évolution des sciences elles-mêmes, aux pratiques cultu- + +relles et aux nouveaux usages. + + + +Ils écrivent ça... Si nous ne sommes pas concernés, qui l'est ?!