Need a unique gift idea?
A Pastebin account makes a great Christmas gift
SHARE
TWEET

Untitled

a guest Jan 9th, 2016 760 Never
Upgrade to PRO!
ENDING IN00days00hours00mins00secs
 
  1. -------- Original Message --------
  2. Subject:    Re: The Power of Apple
  3. Date:   Tue, 18 Oct 2011 10:07:56 -0400
  4. From:   Richard Stallman <r...@gnu.org>
  5. Reply-To:   r...@gnu.org
  6. To:     and...@gn.apc.org
  7. References:     <E1REpVN-...@fencepost.gnu.org>
  8. <4E99A7D0...@gn.apc.org> <E1RFAAr-...@fencepost.gnu.org>
  9. <4E9C6639...@gn.apc.org> <E1RFuxT-...@fencepost.gnu.org>
  10. <1318933934.4...@webmail.gn.apc.org>
  11.  
  12.  
  13.  
  14. Here's the info packet about my speeches.  This information is
  15. essential for planning my visit and speech.  Please forward
  16. it to anyone who is interested in organizing a speech for me.
  17.  
  18.  
  19. Please discuss with me what the topic of this speech should be.
  20. We need to decide it together.
  21.  
  22.  
  23. My talks are not technical.  The topics of free software, copyright vs
  24. community, and digital inclusion deal with ethical/political issues
  25. that concern all users of computers.  The topics of GPL version 3 and
  26. software patents are mainly of of interest to people that work with
  27. software.
  28.  
  29.  
  30. My usual speech about the Free Software Movement and GNU takes a
  31. little over 1.5 hours in English, plus time for questions, photos,
  32. distribution of FSF things, and so on.  It is best to allow plenty of
  33. time for questions, because people usually want to ask a lot of
  34. questions.  In total, it is best to allow 2.5 hours.
  35.  
  36. "GNU" is pronounced as one syllable with a hard g,
  37. like "grew" but with n instead of r.
  38.  
  39. The topics I speak about are
  40.  
  41.     Free Software and Your Freedom
  42.     (alternate titles:
  43.      The Free Software Movement and the GNU/Linux Operating System,
  44.      Free Software in Ethics and in Practice)
  45.  
  46.     Copyright vs Community in the Age of Computer Networks
  47.  
  48.     The Danger of Software Patents
  49.  
  50.     The GNU General Public License
  51.       What we've changed in version 3, and why
  52.  
  53.     A Free Digital Society
  54.     (alternate title, What Makes Digital Inclusion Good or Bad?)
  55.  
  56. These topics take about an hour and a quarter in English,
  57. plus time for questions, photos, signatures, etc.  I suggest
  58. allowing at least two hours.
  59.  
  60. Each topic takes substantially longer in other languages.
  61.  
  62. I can also possibly speak about some other topic if you suggest one.
  63.  
  64.  
  65. Abstract:
  66.  
  67. For a speech about Free Software, you can use this abstract:
  68.  
  69.     The Free Software Movement campaigns for computer users' freedom
  70.     to cooperate and control their own computing.  The Free Software
  71.     Movement developed the GNU operating system, typically used together
  72.     with the kernel Linux, specifically to make these freedoms possible.
  73.  
  74. or
  75.  
  76.     Richard Stallman will speak about the goals and philosophy of the
  77.     Free Software Movement, and the status and history of the GNU
  78.     operating system, which in combination with the kernel Linux is
  79.     now used by tens of millions of users world-wide.
  80.  
  81. For Copyright vs Community, you can use this abstract:
  82.  
  83.     Copyright developed in the age of the printing press, and was designed
  84.     to fit with the system of centralized copying imposed by the printing
  85.     press.  But the copyright system does not fit well with computer
  86.     networks, and only draconian punishments can enforce it.
  87.  
  88.     The global corporations that profit from copyright are lobbying
  89.     for draconian punishments, and to increase their copyright powers,
  90.     while suppressing public access to technology.  But if we
  91.     seriously hope to serve the only legitimate purpose of
  92.     copyright--to promote progress, for the benefit of the
  93.     public--then we must make changes in the other direction.
  94.  
  95. For The Danger of Software Patents, you can use this abstract:
  96.  
  97.     Richard Stallman will explain how software patents obstruct
  98.     software development.  Software patents are patents that cover
  99.     software ideas.  They restrict the development of software, so
  100.     that every design decision brings a risk of getting sued.  Patents
  101.     in other fields restrict factories, but software patents restrict
  102.     every computer user.  Economic research shows that they even
  103.     retard progress.
  104.  
  105. For The GNU General Public License
  106.  
  107.     Richard Stallman wrote the first GNU General Public License in
  108.     1989, and version 3 which was completed in 2007.  He will discuss
  109.     the philosophy of the GNU GPL, the changes made in version 3,
  110.     and the reasons for those changes.
  111.  
  112. For A Free Digital Society
  113.  
  114.     Activities directed at ``including'' more people in the use of digital
  115.     technology are predicated on the assumption that such inclusion is
  116.     invariably a good thing.  It appears so, when judged solely by
  117.     immediate practical convenience.  However, if we also judge in terms
  118.     of human rights, whether digital inclusion is good or bad depends on
  119.     what kind of digital world we are to be included in.  If we wish to
  120.     work towards digital inclusion as a goal, it behooves us to make sure
  121.     it is the good kind.
  122.  
  123.  
  124. Brief bio:
  125.  
  126. Richard Stallman launched the free software movement in 1983 and
  127. started the development of the GNU operating system (see www.gnu.org)
  128. in 1984.  GNU is free software: everyone has the freedom to copy it
  129. and redistribute it, with or without changes.  The GNU/Linux system,
  130. basically the GNU operating system with Linux added, is used on tens
  131. of millions of computers today.  Stallman has received the ACM Grace
  132. Hopper Award, a MacArthur Foundation fellowship, the Electronic
  133. Frontier Foundation's Pioneer Award, and the the Takeda Award for
  134. Social/Economic Betterment, as well as several honorary doctorates.
  135.  
  136. (A longer version is available if you want it.)
  137.  
  138.  
  139. Photo:
  140.  
  141. There is a black-and-white photograph of me as a
  142. 5820K Encapsulated Postscript file (http://www.stallman.org/rms-bw.eps)
  143. 3762K JPEG file (http://www.stallman.org/rms-bw.jpeg), and
  144. 5815K TIFF file (http://www.stallman.org/rms-bw.tiff).
  145.  
  146. Other photos can be found on stallman.org.
  147.  
  148.  
  149.  
  150. Asking for the text:
  151.  
  152. I don't write my speeches in advance--that would take too much time.
  153. However, transcripts of my past speeches are available.  If you can
  154. make a transcript of my speech after I give it, that would be quite
  155. useful.
  156.  
  157.  
  158. Breaks:
  159.  
  160. I absolutely refuse to have a break in the middle of my speech.
  161. Once I start, I will go straight through.
  162.  
  163.  
  164. Participation in a larger event:
  165.  
  166. I am selective about the events I participate in.  If you are inviting
  167. me to speak at a larger event, please inform me now of the overall
  168. nature of the event, so I can make an informed decision about whether
  169. to participate.
  170.  
  171. I usually decline to participate in "open source" or "Linux" events.
  172. See http://www.gnu.org/gnu/gnu-linux-faq.html for why it is incorrect
  173. to refer to the operating system as "Linux".
  174.  
  175. "Open source" is the slogan of a position that was formulated as a
  176. reaction against the free software movement.  Those who support its
  177. views have a right to promote them, but I disagree with them and I
  178. want to promote the ideals of free software.  See
  179. http://www.gnu.org/philosophy/free-software-for-freedom.html for more
  180. explanation of the difference.  However, I will agree to participate
  181. in events labeled "Free Software and Open Source", provided that my
  182. speech is not the principal draw of the event.
  183.  
  184.  
  185. Erecting a larger event:
  186.  
  187. If you are thinking of erecting a larger event around my speech, which
  188. includes inviting other speakers to speak before or after me, please
  189. talk with me about the plans for that larger event _before_ inviting
  190. other speakers.  I want to make sure the event entirely supports the
  191. goals and principles I work for, and I want to review the publicity
  192. plans for the event.
  193.  
  194.  
  195. Multiple events:
  196.  
  197. If you would like me to give speeches in other cities, other
  198. institutions, or other events which you are not organizing directly,
  199. please put rms-a...@gnu.org in touch directly with their organizers.
  200. We need to show them this info packet, and we need to discuss various
  201. issues with them just as we discuss the issues of your event with you.
  202. Communication through a middleman is asking for confusion, so please
  203. don't ask us to do that.
  204.  
  205.  
  206. Venues and planning:
  207.  
  208. All my talks are aimed at the general computer-using public.  They are
  209. not technical.  With good, broad publicity, many people will come --
  210. usually hundreds.
  211.  
  212. So don't aim small.  Please plan each speech in a large room, then
  213. plan the publicity to bring people in to fill it.  Please do not
  214. suggest scheduling a "small speech", because that makes no sense as a
  215. goal.  I would always rather reach as many people as I feasibly can.
  216.  
  217. If the speech is at a university, please do the publicity all around
  218. the university.  Don't limit it to your department!  We also want
  219. people from off-campus to come, so please inform local IT businesses,
  220. user groups, and other relevant organizations.
  221.  
  222. We will also want to inform the region's daily newspapers so they can
  223. put the speech in their calendar sections, and anything else we can
  224. think of.  Each additional interested person who comes means an increase
  225. in the results achieved by the speech.
  226.  
  227. Make sure you inform the public that my talk is not technical, so
  228. anyone interested in ethics and use of computers might wish to come.
  229.  
  230.  
  231. Facilities:
  232.  
  233. A microphone is desirable if the room is large.  No other facilities
  234. are needed.  I do not have slides or any sort of presentation
  235. materials.
  236.  
  237. A supply of tea with milk and sugar would be nice.  If it is tea I
  238. really like, I like it without milk and sugar.  With milk and sugar,
  239. any kind of tea is fine.  I always bring tea bags with me, so if we
  240. use my tea bags, I will certainly like that tea without milk or sugar.
  241.  
  242. If I am quite sleepy, I would like two cans or small bottles of
  243. non-diet Pepsi.  (I dislike the taste of coke, and of all diet soda;
  244. also, there is an international boycott of the Coca Cola company for
  245. killing union organizers in Colombia and Guatemala; see
  246. killercoke.org.)  However, if I am not very sleepy, I won't want
  247. Pepsi, because it is better if I don't drink so much sugar.
  248.  
  249.  
  250. Languages:
  251.  
  252. I can speak in English, French, and Spanish.
  253.  
  254. If the audience won't be comfortable with a language I can speak, it
  255. is important to have translation.  However, consecutive translation
  256. is not feasible, because it would more than double the length of the
  257. speech.  Please do not ask me to do that--I will refuse.
  258.  
  259. I have found it works to do simultaneous translation without special
  260. systems: I speak into the ear of the interpreter, and the interpreter
  261. speaks to the microphone.  This avoids the need for special
  262. transmitters and headsets.  However, it does require an interpreter
  263. capable of doing simultaneous translation for more than an hour.
  264. Do not propose doing this with a person whose translation skills
  265. are not adequate for this.
  266.  
  267. Another method is to set up a microphone and speaker system for the
  268. interpreter in a far corner of the room, or a balcony.  If the
  269. speakers are set up suitably, people there can hear the interpreter
  270. well, while people in the front of the room can hear me well.
  271.  
  272. I can try to give a shortened free software speech (about 30 minutes
  273. of material).  With consecutive translation it will take an hour or
  274. more.  I will be forced to omit many important points in the usual
  275. speech.  I do not like to omit so much.
  276.  
  277. If we have simultaneous translation, please make a recording
  278. of the translation.  It will be very useful, and it is easy to do.
  279. Any sound recorder, next to the interpreter, will do it.
  280.  
  281.  
  282. Restricting admission:
  283.  
  284. If you plan to restrict admission to my speech, or charge a fee for
  285. admission, please discuss this with me *personally in advance* to get
  286. my approval for the plan.  If you have imposed charges without my
  287. direct personal approval, I may refuse to do the speech.
  288.  
  289. I'm not categorically against limiting admission or fees, but
  290. excluding people means the speech does less good, so I want to make
  291. sure that the limitations are as small as necessary.  For instance,
  292. you can allow students and low-paid people and political activists to
  293. get in free, even if professionals have to pay.  We will discuss what
  294. to do.
  295.  
  296. Another method, which works very well in some places, is to allow
  297. people to attend gratis but charge for a certificate of attendance.
  298. If the certificate is given by an educational institution, many will
  299. find it useful for career advancement, while the others could enter
  300. gratis.  Whether this would be effective in your country is something
  301. you would need to judge.
  302.  
  303.  
  304. Sponsors:
  305.  
  306. If corporations sponsor my talk, I am willing to include a small
  307. tasteful note of thanks in announcements and brochures, but no more
  308. than that.  There should be no descriptions of their products or
  309. services, and no banners with their names.  If a would-be sponsor
  310. insists on more than that, we have to do without that sponsor.
  311.  
  312. If my speech is part of a pre-existing larger event that I have agreed
  313. to participate in, I can't impose such conditions for the whole event.
  314. However, if banners will be on display next to me while I am speaking,
  315. that is rather obnoxious; if they advertise organizations that I
  316. disapprove of on ethical grounds (which is not unlikely) I would want
  317. to take them down, cover them up, or turn them off during my speech.
  318.  
  319.  
  320. Directing publicity:
  321.  
  322. My main speech topics are not technical.  They are about political
  323. issues regarding the use of software, and anyone concerned about
  324. ethical issues with effects on our daily lives should be concerned
  325. about them.  Thus, when planning to publicize my talk, don't direct
  326. the publicity primarily at computing organizations and computer
  327. science departments.  That would only reach a fraction of the people
  328. who might be interested.  Please also contact political science
  329. departments, economics departments, philosophy departments, music
  330. departments, and student groups interested in freedom and human rights
  331. issues.  Let's aim to make the speech reach as many interested people
  332. as possible.
  333.  
  334. The speech topics of software patents and GPLv3 are of interest
  335. specifically to the IT field, so those you can publicize among IT
  336. contacts.
  337.  
  338.  
  339. Avoiding errors in publicity:
  340.  
  341. The GNU Project constantly struggles against two widespread mistakes
  342. that undermine the effectiveness of our work: calling our work "open
  343. source", and calling the GNU operating system "Linux".  Another very
  344. bad mistake is using the term "intellectual property".
  345.  
  346. The Free Software Movement and the Open Source Movement are like two
  347. political parties in our community.  I founded the Free Software
  348. Movement in 1984 along with the GNU Project; we call our work "free
  349. software" because it is software that respects the users freedom.  The
  350. Open Source Movement was founded, in 1998, specifically to reject our
  351. idealistic philosophy--they studiously avoid talking about freedom.
  352. See http://www.gnu.org/philosophy/free-software-for-freedom.html for
  353. more explanation of the difference between the two movements.
  354.  
  355. So please make sure that all the publicity about the event (web site,
  356. email announcements, conference programs, direct mail, signs, etc),
  357. uses the term "free software", not "open source", when you refer to
  358. work that includes mine.  This includes to the title and descriptions
  359. of my speech, of the session it is in, of the track it is part of, and
  360. of the event itself.
  361.  
  362. Of course, some of these names and descriptions may not refer to this
  363. work at all; for example, if a track or the whole event covers a much
  364. broader topic in which free software is just a small part, its name
  365. may not refer to free software.  That is normal and appropriate.  The
  366. point is not to ask you to refer to this work more often than you
  367. normally would, but that you should describe it accurately whenever
  368. you do refer to it.
  369.  
  370. If other speakers in the same session, track, or event want their work
  371. to be categorized as "open source", that is a legitimate request for
  372. them to make.  In that case, please give "free software" equal mention
  373. with "open source".
  374.  
  375. If you think it is useful to tell people how free software relates to
  376. open source, you can say that "since 1998, another group has used the
  377. term `open source' to describe a related activity."  That will tell
  378. people that my work has a relationship with "open source", which they
  379. may have heard of, without implying it is right to describe my work as
  380. "open source."
  381.  
  382. The other widespread confusion is the idea of a "Linux operating
  383. system".  The system in question, the system that Debian and Red Hat
  384. distribute, the system that tens of millions of people use, is
  385. basically the GNU operating system, with Linux added as the kernel.
  386. When people call the whole system "Linux", they deny us the credit for
  387. our work, and this is not right.  (See
  388. http://www.gnu.org/gnu/linux-and-gnu.html for more explanation.)
  389.  
  390. So please call this combined operating system "GNU/Linux" in all
  391. the publicity, in the titles and description of the session, track,
  392. event, etc., if and when you have reason to refer to it.
  393.  
  394. For similar reasons, please don't use a penguin as a symbol for my
  395. work, or on the posters or notices for my speech.  The penguin stands
  396. for "Linux"; the symbol of GNU is a gnu.  So if you want to use a
  397. graphical image to symbolize GNU or my work, please use a gnu.
  398.  
  399. If you have handled these issues well, nobody who looks at your
  400. material will get the impression that I work on "open source", or that
  401. I support "open source", or that my work is "part of Linux", or that I
  402. participated in the "development of Linux", or that GNU is the name of
  403. "a collection of tools".
  404.  
  405. As for the term "intellectual property", that spreads confusion and
  406. hostile bias.  See http://www.gnu.org/philosophy/words-to-avoid.html
  407. for explanation.  I hope you will decide to reject that expression, as
  408. I do; but in any case, don't use it in connection with my speech.
  409.  
  410. Please do not mention non-free GNU/Linux distros (for instance,
  411. Ubuntu) in the publicity for the event.
  412.  
  413. If you have doubts about a poster or announcement, please ask my
  414. assistant to check it for you, not me.  Send it to rms-a...@gnu.org.
  415.  
  416.  
  417. Selling Free Software, Free Society:
  418.  
  419. Please sell copies of my book of essays, Free Software, Free Society,
  420. if you can.  In the US, Canada, Spain, Italy and Japan, you can obtain
  421. published copies of this book in English, Spanish, Italian, and
  422. Japanese.  You don't need to put up any money to do this.  Please talk
  423. with rms-a...@gnu.org about how to do it.  In the US and Canada, the
  424. FSF will ship you these books.
  425.  
  426. Outside those four countries, please print copies of the book to sell
  427. at the event, if you can.  The English version is available in
  428. http://shop.fsf.org/product/free-software-free-society-2/ (278 pages).
  429. There is also my semiautobiography, Free As In Freedom, in
  430. http://shop.fsf.org/product/free-as-in-freedom-2/ (245 pages).
  431.  
  432. He Spanish version of Free Software, Free Society (318 pages) is in
  433. http://www.gnu.org/philosophy/fsfs/free_software.es.pdf.
  434.  
  435. If you use ordinary copying, and avoid fancy covers and bindings, we
  436. can sell them for two or three times the cost of copying, and they
  437. will still be cheap enough that many people will buy them.  From the
  438. proceeds you will first retain the cost of printing; we can divide the
  439. gains between your organization and the FSF.
  440.  
  441. If you see any obstacle, whatever it is, don't just give up.  Talk
  442. with rms-a...@gnu.org about it!  Most of the problems that might
  443. seem difficult to you, we are already accustomed to solving.  Give us
  444. a chance to overcome the obstacle!
  445.  
  446.  
  447. At the speech:
  448.  
  449. Please put out a pad of paper for people to write down their names and
  450. email addresses if they want to be on the FSF's mailing list.
  451.  
  452.  
  453. Changes of plans:
  454.  
  455. Don't assume that I can still come if you change the date, or even the
  456. hour.  My schedule is tight, and any change may make the plan
  457. impossible.  Please consult with me before making any change, and I
  458. will see what I can do.
  459.  
  460. My assistant cannot approve such changes; you must ask me directly,
  461. and get approval from me directly.  I will certainly be flexible if
  462. there is no obstacle.
  463.  
  464.  
  465. Scheduling other meetings:
  466.  
  467. I have agreed to give a speech for you, and if the press wants to talk
  468. with me, I will do that for the sake of the cause.  However, if you
  469. would like me to give additional speeches or go to additional
  470. meetings, please ask me first.  Please ask me about *each* activity
  471. you would like me to perform.
  472.  
  473. Many people assume that because I am traveling, I am having a
  474. vacation--that I have no other work to do, so I can spend the whole
  475. day speaking or meeting with people.  Some hosts even feel that they
  476. ought to try to fill up my time as a matter of good hospitality.
  477. Alas, it's not that way for me.
  478.  
  479. The fact is, I have no vacations.  (Don't feel sorry for me; idleness
  480. is not something I wish for.)  I have to spend 6 to 8 hours *every
  481. day* doing my usual work, which is responding to email about the GNU
  482. Project and the Free Software Movement.  Work comes in every day for
  483. me, and if I skip it one day, I have to catch up another day.  During
  484. the week I usually fall behind; on weekends I try to catch up.
  485.  
  486. Traveling takes up time, so I will be extra busy during my visit.  And
  487. it might be nice if I could do at least an hour or two of sightseeing
  488. during the visit.  So please ask me *in advance* about *each*
  489. additional speech, meeting, or other activity that would take time.  I
  490. don't mind being asked, and I may say yes, but I also may say no.
  491.  
  492. Remember that an additional speech, even if it is just a one-hour
  493. speech, probably takes up two hours counting questions, autographs,
  494. etc.  And then there is the travel time.
  495.  
  496.  
  497. Interviews:
  498.  
  499. I am glad to give interviews to the press about the GNU system, but
  500. before I do, I want to be sure they will not repeat the two common
  501. mistakes (calling the whole system "Linux" and associating GNU or me
  502. with "open source").  Please explain this, and ask the journalist if
  503. he will agree to call the system "GNU/Linux" in the article, and to
  504. make it clear that our work is "free software" not "open source".
  505. Recommend reading http://www.gnu.org/gnu/linux-and-gnu.html and
  506. http://www.gnu.org/philosophy/free-software-for-freedom.html for
  507. explanations of these issues.  If the journalist agrees, then I agree
  508. to an interview.  Please have this discussion by email, and save the
  509. messages in both directions.
  510.  
  511. Sometimes a journalist gives a response which sounds vaguely
  512. affirmative or sympathetic but its words do not really say "yes".
  513. Examples are "I will do this as much as I can" and "I understand the
  514. distinction."  Such an answer is actually just "maybe", so when you
  515. receive one, please ask for clarification.  If he says that the editor
  516. has the final decision, please respond with "Would you please consult
  517. the editor now, and tell us a firm decision?"
  518.  
  519.  
  520. Recorded interviews for broadcast:
  521.  
  522. It is ok to do these either before or after my speech, and they
  523. usually need to be done one at a time, so I am willing to do them that
  524. way.
  525.  
  526.  
  527. Interviews not for broadcast:
  528.  
  529. Please do not propose to hold these interviews before the conference.
  530. That order wastes my time.  So please propose to hold them AFTER the
  531. conference.
  532.  
  533. Also please ask journalists to *see my speech* before the interview.
  534. My speeches are not technical; they focus on precisely the sort of
  535. philosophical questions that a journalist would probably want to
  536. cover.  If the journalist has not attended my speech, he will probably
  537. start by asking me to answer the same questions that I answer in the
  538. speech.  That is a waste of time for me.
  539.  
  540. If you schedule a press conference or group interview, please *plan
  541. the time of my speech to allow the interview after it*.  It may be a
  542. good idea to find out from journalists what times are good for them,
  543. then schedule the conference, then schedule the speech before it.
  544. This way, they will all be able to get the full picture.
  545.  
  546. It is also ok to have the interviews the day after the speech.
  547. That is another way to have them after the speech rather than before.
  548.  
  549. If the journalists simply cannot do the interview after the speech,
  550. then I will do it before the speech if possible.  But please insist
  551. that they watch or listen to a recording on audio-video.gnu.org of
  552. another speech.
  553.  
  554. It is also a good idea for the journalist to read
  555. http://www.gnu.org/gnu/the-gnu-project.html as well as
  556. http://www.gnu.org/gnu/gnu-linux-faq.html
  557. http://www.gnu.org/philosophy/free-sw.html
  558. http://www.gnu.org/philosophy/categories.html
  559. http://www.gnu.org/philosophy/words-to-avoid.html
  560. http://www.gnu.org/philosophy/compromise.html
  561. http://stallman.org/articles/internet-sharing-license.en.html
  562. http://stallman.org/articles/ebooks.pdf before the interview.  Those
  563. articles provide important background.  This is especially important
  564. for anyone who cannot come to my speech first.
  565.  
  566. Please ask each journalist to agree to make a recording of the
  567. interview.  Written notes tend to simplify, and often lead to
  568. incorrect quotes.
  569.  
  570. I am willing to meet with any number of journalists, but if there are
  571. many, I can't meet all of them individually (it would take too much
  572. time).  So what I will do is give private interviews to 2 or maybe 3
  573. of them, whichever ones you think are most important, and see the rest
  574. of them as a group (i.e. in a press conference).
  575.  
  576. You and your associates can judge better than I do which journalists
  577. and which publications I should focus on.  So I would like you to
  578. advise me about that.  Please try to judge both the importance of the
  579. publication and the merits (intelligence, attention to accuracy,
  580. openness of mind, and absence of bias) of the journalist, if you can.
  581.  
  582.  
  583. Recording my speech:
  584.  
  585. Please do record the speech if you can.  We are always looking for
  586. good recordings of my speeches, both audio and video, to put on line.
  587.  
  588. The GNU Project keeps an on-line audio and video collection of speech
  589. recordings in audio-video.gnu.org.  If you are making an audio or
  590. video recording of my speech, please write to audio...@gnu.org in
  591. advance for advice on how to make a recording that is good for further
  592. use, and subsequently to arrange to install your recording on our
  593. site.
  594.  
  595. When you are making a recording, please *make sure* to tell me when
  596. the tape needs to be changed.  I will pause.  Please help me help you
  597. make the recording complete.
  598.  
  599.  
  600. Recording formats:
  601.  
  602. Please make sure that your recording is not compressed with a
  603. substantially lossy codec (unless it is an Ogg codec).  If we have to
  604. transcode the file, starting from a lower-quality base will reduce the
  605. quality of the result.
  606.  
  607. It is best to provide audio recordings in the original recorded sample
  608. rate, up to 44100Hz.  Monophonic is generally adequate for speech
  609. recordings and saves a lot of space over stereo.
  610.  
  611. For video recordings, please save the master recording, which will
  612. probably be in miniDV format.
  613.  
  614. Please don't transcode recordings from one format to another before
  615. sending to us, unless they have such a high bit rate that files are
  616. impractically large.  If you do need to encode or transcode, please
  617. convert audio to 64Kbps mono Ogg Vorbis (or you could try Ogg Speex),
  618. and convert video to Matroska VP8 or to Ogg Theora with video quality
  619. set to 5 or more.  If you need advice for how to do this, please ask
  620. audio...@gnu.org.
  621.  
  622.  
  623. Putting my speech on the net:
  624.  
  625. If you would like to put my speech on the Internet, or distribute it
  626. in digital form, I insist on using the formats of the free software
  627. community: Ogg Vorbis or Ogg Speex format for audio, and Matroska VP8
  628. (Webm) or Ogg Theora for video.  Please do not distribute my speech in
  629. any other format.
  630.  
  631. Please do not ever broadcast or publish my speeches in formats that
  632. are not good for free software.  I will not speak to make a recording
  633. or broadcast that requires non-free software to be heard or viewed.
  634. Don't use RealPlayer format, or Quicktime, or Windows Media Player
  635. format, or a patented format such as MPEG2, MPEG4, or MP3.
  636.  
  637. This requirement is very important, because if it is not followed,
  638. viewing my speech will require people to do the exact opposite of what
  639. I ask them to do.  The medium's message would contradict my message.
  640.  
  641. Because this is so important, please make sure everyone who might be
  642. involved in broadcasting the event, or who might be directly or
  643. indirectly involved in planning such a broadcast, knows this
  644. requirement in advance of the event.
  645.  
  646. You can get advice and help in distributing Ogg files from Mallory
  647. Knodel <mal...@mayfirst.org>.
  648.  
  649.  
  650. Streaming the speech:
  651.  
  652. Streaming is a kind of Internet distribution, so everything in the
  653. previous section applies.  In particular, you must use only Ogg format
  654. or Matroska VP8 (Webm).
  655.  
  656. If you want to stream my speech but you have not done streaming in Ogg
  657. or VP8 before, don't leave the matter till the last minute.  By then,
  658. it will be too late.  Please try a test session two weeks before the
  659. speech.  That way, if you encounter any problem, there will be time to
  660. resolve it before the speech.
  661.  
  662. If you have previously done streaming using some streaming service and
  663. you can't immediately name the format it uses, chances are it is
  664. unacceptable and I won't let you use it for my speech.  So please
  665. check, two weeks in advance, what format it uses.  If you find it uses
  666. some bad format, you will have time to arrange for ethical streaming.
  667.  
  668. You can get advice and help in Ogg streaming from Mallory Knodel
  669. <mal...@mayfirst.org>.  Please ask two weeks before the event; they
  670. can do it faster faster, but why make their work hectic unnecessarily?
  671. See https://support.mayfirst.org/wiki/live-video-streaming-support for
  672. more info.
  673.  
  674.  
  675. Remote speeches by video connection:
  676.  
  677. I can do a speech remotely through a videoconferencing system.  This
  678. can be done by Internet or by ISDN.  For good quality by Internet, we
  679. need a maximum of 100msec response time for ping between your site and
  680. where I am, and 100kbytes/sec transfer rate.
  681.  
  682. Using two or three ISDN lines gives good quality but the calls cost
  683. money.  If I am at home, there is a facility I can use at no charge;
  684. you would have to pay for the ISDN calls and for the facilities at
  685. your end.  If I am somewhere else (which is true more than half the
  686. time), then we will need to find a videoconferencing facility for me
  687. to use; most likely you will need to pay for that.
  688.  
  689.  
  690. Warning about giveways:
  691.  
  692. You may find companies offering you CD-ROMs, books, fliers or
  693. publicity materials to give away or sell at my speech.  Please check
  694. them before you accept them, to make sure that they don't promote the
  695. very thing that we are working to replace.
  696.  
  697. For instance, the CDs may contain non-free software.  Most distros of
  698. GNU/Linux contain or suggest non-free software in addition to the free
  699. software.  (And most of them call the system "Linux".)  Please check
  700. with me before you allow a CD of GNU/Linux to be distributed at the
  701. event.
  702.  
  703. Books about use of the GNU/Linux system and about GNU programs are
  704. fine if they themselves are also free.  But many of them are non-free
  705. (see http://www.gnu.org/philosophy/free-doc.html).  To see if a book
  706. is free, check the license on the back of the title page.  If it uses
  707. the GNU Free Documentation License, or the Open Publication License
  708. version 1 without options A and B, then it is free.  If it isn't one
  709. of those, please show me the license and I will tell you if it is a
  710. free license.
  711.  
  712. If companies send you publicity materials, please check with me before
  713. giving them out at my speech.
  714.  
  715.  
  716. Flights:
  717.  
  718. The FSF does not pay for my travel, and I can't afford to.  I will
  719. need you to arrange to cover the cost of my traveling to and from your
  720. city (unless I've told you someone else will do it).
  721.  
  722. I am traveling most of the time, and most of my trips include several
  723. stops.  Chances are your city is neither the first nor the last stop
  724. in the trip.  Please don't make assumptions about the itinerary;
  725. instead, please ask me for whatever information you need.
  726.  
  727. Many organizations ask to buy the tickets and send them to me.  I do
  728. not object to that method in principle, but it typically assumes the
  729. trip goes to just one city.  That approach is hard to use for a
  730. multi-destination trip, unless you want to pay for the whole trip.  So
  731. normally I buy the tickets myself and get reimbursed by the various
  732. places I am visiting.  For a multi-destination trip, we will need to
  733. agree on what parts of the travel expenses you should cover.
  734.  
  735. Some organizations feel that hospitality calls for providing me with a
  736. business class ticket.  That is indeed more comfortable, but an
  737. economy class seat is good enough.  Meanwhile, speaking is my main
  738. source of income, and the extra price of a business class ticket would
  739. be a lot more useful for me if I can spend it on something else.  So
  740. if you were thinking of spending extra for business class, how about
  741. if you pay the extra to me as a speaker's fee instead?
  742.  
  743. We should plan for me to arrive (at the site itself, not just at the
  744. airport) at least 24 hours before the speech; that way, even if the
  745. flight is cancelled, there is a good chance I can still arrive in time
  746. for the speech by taking the same flight the next day.
  747.  
  748.  
  749. Lost tickets:
  750.  
  751. If you are not paying me a speaking fee, but you are paying for the
  752. airline tickets, I must insist that you cover the costs if I have to
  753. replace a lost ticket, the fee for changing the ticket if I miss a
  754. flight, or any other surprise expenses associated with my travel to
  755. and from your location.
  756.  
  757. This might seem unfair--if a ticket is lost, it could be my fault.
  758. But my income is not large, and I cannot afford to assume this risk
  759. myself if the event offers me no income.  The frustration I feel when
  760. I suffer such a loss is excruciating.  It is better for me to decline
  761. to travel to a certain place than to take such a risk.
  762.  
  763.  
  764. Bus and train tickets:
  765.  
  766. If you buy bus or train tickets for me, do not give my name!  Big
  767. Brother has no right to know where I travel, or where you travel, or
  768. where anyone travels.  If they arbitrarily demand a name, give a name
  769. that does not belong to any person you know of.  If they will check my
  770. ID before I board the bus or train, then let's look for another way
  771. for me to travel.  (In the US I never use long-distance trains because
  772. of their ID policy.)
  773.  
  774. Don't give them your name either: please pay for the ticket in cash.
  775.  
  776.  
  777. Other expenses:
  778.  
  779. I expect you to cover expenses such as visa fees, fees for mailing my
  780. passport back and forth, taxis to and from the airport, and so on.
  781.  
  782.  
  783. Accommodations:
  784.  
  785. I am willing to stay in a hotel if there is no other way.
  786. Please book the hotel for me and arrange to pay the hotel directly.
  787.  
  788. But please DON'T make a hotel reservation until we have fully explored
  789. other options.  If there is anyone who wants to offer a spare couch, I
  790. would much rather stay there than in a hotel (provided I have a door I
  791. can close, in order to have some privacy).  Staying with someone is
  792. more fun for me than a hotel, and it would also save you money.
  793.  
  794. My distaste for a hotel is less if it does not know my name, but
  795. staying in a house with people is normally more enjoyable than staying
  796. alone.
  797.  
  798. Many countries have a law that hotels must report all guests to the
  799. police.  In most cases, this orwellian policy applies not only to
  800. foreigners like me, but to citizens as well!  The citizens should be
  801. outraged by this, but often they are not.
  802.  
  803. Please call the hotel and ask whether they will demand to see my
  804. passport, and whether they report all their guests to the police.  If
  805. it has this policy, please join me in striking a blow against Big
  806. Brother, by looking for a place I can stay in that doesn't demand to
  807. see my passport, or report my visit to anyone.  If the police want
  808. information about free software, they are welcome to come to my
  809. speech.
  810.  
  811. If you have found a person for me to stay with, please forward this
  812. section and the two following sections to that person.
  813.  
  814.  
  815. Temperature:
  816.  
  817. Above 72 fahrenheit (22 centigrade) I find sleeping quite difficult.
  818. (If the air is dry, I can stand 23 degrees.)  A little above that
  819. temperature, a strong electric fan blowing on me enables me to sleep.
  820. More than 3 degrees above that temperature, I need air conditioning to
  821. sleep.
  822.  
  823. If there is a substantial chance of indoor temperatures too hot for
  824. me, please arrange _in advance_ for me to have what I need.
  825.  
  826. If you are planning for me to stay in a hotel, DO NOT take for granted
  827. that the hotel has air conditioning--or that it will be working when I
  828. arrive.  Some hotels shut off their air conditioning systems for part
  829. of the year.  They often think it is unnecessary in seasons when the
  830. temperature is usually in the mid 20s--and they follow their schedule
  831. like stupid robots even if there is a heat wave.
  832.  
  833. So you must explicitly ask them: "Do you have air conditioning?  Will
  834. it be functioning for the dates XXX-YYY?"
  835.  
  836. In some hotels with central air conditioning, it simply does not work
  837. very well: it can make a room less hot, but can't make it cool.
  838. Before using a hotel that has central air conditioning, find out what
  839. temperature it can actually lower a room to, during the relevant
  840. dates.
  841.  
  842. Or look for a hotel that has a real cooling unit in the room, not a
  843. central system.  Those tend to work well enough, if they are not
  844. broken.
  845.  
  846.  
  847. Pets:
  848.  
  849. I like cats if they are friendly, but they are not good for me; I am
  850. somewhat allergic to them.  This allergy makes my face itch and my
  851. eyes water.  So the bed, and the room I will usually be staying in,
  852. need to be clean of cat hair.  However, it is no problem if there is a
  853. cat elsewhere in the house--I might even enjoy it if the cat is
  854. friendly.
  855.  
  856. Dogs that bark angrily and/or jump up on me frighten me, unless they
  857. are small and cannot reach much above my knees.  But if they only bark
  858. or jump when we enter the house, I can cope, as long as you hold the
  859. dog away from me at that time.  Aside from that issue, I'm ok with
  860. dogs.
  861.  
  862. If you can find a host for me that has a friendly parrot, I will be
  863. very very glad.  If you can find someone who has a friendly parrot I
  864. can visit with, that will be nice too.
  865.  
  866. DON'T buy a parrot figuring that it will be a fun surprise for me.  To
  867. acquire a parrot is a major decision: it is likely to outlive you.  If
  868. you don't know how to treat the parrot, it could be emotionally
  869. scarred and spend many decades feeling frightened and unhappy.  If you
  870. buy a captured wild parrot, you will promote a cruel and devastating
  871. practice, and the parrot will be emotionally scarred before you get it.
  872. Meeting that sad animal is not an agreeable surprise.
  873.  
  874.  
  875. Email:
  876.  
  877. It is very important for me to be able to transfer email between my
  878. laptop and the net, so I can do my ordinary work.  While traveling, I
  879. often need to do the work and the transfer late at night, or in the
  880. morning before a departure.  So please set up a way I can connect to
  881. the net from the place I am staying.
  882.  
  883. I do NOT use browsers, I use the SSH protocol.  If the network
  884. requires a proxy for SSH, I probably can't use it at all.
  885.  
  886. If a hotel says "We have internet access for customers", that is so
  887. vague that it cannot be relied on.  So please find out exactly what
  888. they have and exactly what it will do.  If they have an ethernet, do
  889. they have a firewall?  Does it permit SSH connections?  What
  890. parameters does the user need to specify in order to talk with it?
  891.  
  892. Please check those things directly, or ask the people who actually run
  893. the network.  If you talk with someone who doesn't understand what
  894. "SSH connection" means, or if he doesn't understand the difference
  895. between "Internet" and "web browsing", that person is not competent to
  896. give reliable information.  Don't rely on information from such a
  897. person--talk to someone who knows!
  898.  
  899. For reasons of principle, I am unwilling to identify myself in order
  900. to connect to the Internet.  For instance, if a hotel gives a user
  901. name and password to each room, I won't use that system, since it
  902. would identify me.  I would need some other way to connect.
  903.  
  904. A modem connection is fine if it works, so please verify in advance
  905. that the telephone line you expect me to use has a modular jack and
  906. that it works to call the ISP from that line.  Hotels in Europe and
  907. Asia often have peculiar phone systems; the staff may tell you it is
  908. possible to call an ISP from the hotel *but they may be wrong*.  For
  909. instance, their phone switchboard may not recognize the tones produced
  910. by modems.  The only way to tell for certain is to go to the hotel,
  911. try phoning with a computer from a guest room, and see if it actually
  912. works.  Until you have tested it, don't believe it!
  913.  
  914. My ISP phone numbers are old; I don't know if they will still work.
  915. If you propose I use a modem, please find a number I can call.  It is
  916. best if you lend me a permanent account that someone else uses, one
  917. that will continue working afterward, so that I can use it again if I
  918. come back or use it from other places in the region.  Hotel phone
  919. rates may be high; I expect you to cover them.  However, I normally
  920. connect to the net only for around ten minutes at a time, twice a day,
  921. so the total won't be too big.
  922.  
  923. If I need to use a dialup connection, please cover the costs of the
  924. telephone calls I will need to transfer my email -- especially in a
  925. hotel.  Some hotels charge a lot of money for this.
  926.  
  927. Wireless modems mostly do not work with my machine, so do not plan on
  928. my using one.  I won't refuse to use them if you have an expert who
  929. can make it work, but success is rare.  If it involves loading a
  930. nonfree driver, I will refuse.
  931.  
  932.  
  933. Paying me a reimbursement or a fee:
  934.  
  935. Please pay my reimbursement or fee to me personally; do not pay it to
  936. the FSF.  The FSF and I have completely separate finances, and the FSF
  937. never pays for my travel.  The FSF welcomes donations, but please make
  938. sure that money intended for me is not sent to them, because moving it
  939. afterward would mean accounting headaches as well as extra work.
  940.  
  941. My assistant is not involved with my finances, so she cannot help you
  942. with that issue.  Please send questions about payments to me directly.
  943.  
  944. If you pay me by check, and you're not in the US, make sure to get a
  945. check that lists a corresponding US bank--otherwise it will cost me a
  946. fee to deposit the check.  Please mail the check _in US dollars_ to:
  947.  
  948.     Richard Stallman
  949.     77 Mass Ave rm 32-381
  950.     Cambridge MA 02139
  951.     Phone number: +1-617-253-8830
  952.  
  953. Do not mail it to the FSF!
  954.  
  955. A wire transfer is also a good method of payment.  I will send you the
  956. coordinates; ask if you need them.  The bank you use will charge a
  957. fee, and my bank charges me $10 for each incoming transfer; please add
  958. those fees to the amount, rather than taking them out of what I
  959. receive.
  960.  
  961. If you are outside the US, please convert your currency to dollars in
  962. your bank, then use one of the above methods to pay me the dollars.
  963. My bank gives very bad exchange rates; yours is surely better.
  964.  
  965. Cash is also fine.
  966.  
  967. If you want an invoice, I will be glad to give you one.  Let's work
  968. out what it should say by email before I arrive.  Please also check
  969. before the visit whether you need any other forms, such as tax forms.
  970. I would like to be able to take care of any necessary forms while I am
  971. there, rather than wait till afterward.
  972.  
  973.  
  974. Hospitality:
  975.  
  976. Please pass this section to everyone who will be helping me directly
  977. in any fashion during the visit.
  978.  
  979. It is nice of you to want to be kind to me, but please don't offer
  980. help all the time.  In general I am used to managing life on my own;
  981. when I need help, I am not shy about asking.  So there is no need to
  982. offer to help me.  Moreover, being constantly offered help is actually
  983. quite distracting and tiresome.
  984.  
  985. So please, unless I am in grave immediate danger, please don't offer
  986. help.  The nicest thing you can do is help when I ask, and otherwise
  987. not worry about how I am doing.  Meanwhile, you can also ask me for
  988. help when you need it.
  989.  
  990. One situation where I do not need help, let alone supervision, is in
  991. crossing streets.  I grew up in the middle of the world's biggest
  992. city, full of cars, and I have crossed streets without assistance even
  993. in the chaotic traffic of Bangalore and Delhi.  Please just leave me
  994. alone when I cross streets.
  995.  
  996. In some places, my hosts act as if my every wish were their command.
  997. By catering to my every whim, in effect they make me a tyrant over
  998. them, which is not a role I like.  I start to worry that I might
  999. subject them to great burdens without even realizing.  I start being
  1000. afraid to express my appreciation of anything, because they would get
  1001. it and give it to me at any cost.  If it is night, and the stars are
  1002. beautiful, I hesitate to say so, lest my hosts feel obligated to try
  1003. to get one for me.
  1004.  
  1005. When I'm trying to decide what to do, often I mention things that
  1006. MIGHT be nice to do--depending on more details, if it fits the
  1007. schedule, if there isn't a better alternative, etc.  Some hosts take
  1008. such a tentative suggestion as an order, and try moving heaven and
  1009. earth to make it happen.  This excessive rigidity is not only quite
  1010. burdensome for other people, it can even fail in its goal of pleasing
  1011. me.  If there is a better alternative, I'd rather be flexible and
  1012. choose it instead--so please tell me.  If my tentative suggestion
  1013. imposes a lot of trouble on others, I want to drop it--so please tell
  1014. me.
  1015.  
  1016. When you need to tell me about a problem in a plan, please do not
  1017. start with a long apology.  That is unbearably boring, and unnecessary
  1018. -- conveying useful information is helpful and good, and why apologize
  1019. for that?  So please be practical and go straight to the point.
  1020.  
  1021. If I am typing on my computer and it is time to do something else,
  1022. please tell me.  Don't wait for me to "finish working" first, because
  1023. you would wait forever.  I have to squeeze in answering mail at every
  1024. possible opportunity, which includes whenever I have to wait.  I wait
  1025. by working.  If instead of telling me there is no more need for me to
  1026. wait, you wait for me to stop waiting for you, we will both wait
  1027. forever -- or until I figure out what's happening.
  1028.  
  1029.  
  1030. Dinners:
  1031.  
  1032. If you are thinking of setting up a lunch or dinner for me with more
  1033. than 4 people total, please consider that as a meeting, and discuss it
  1034. with me in advance.  Such meals draw on my strength, just like
  1035. speeches and interviews.  They are not relaxation, they are work.
  1036.  
  1037. I expect to do work during my visit, but there is a limit on the
  1038. amount of work I can handle each day.  So please ask me in advance
  1039. about any large planned meal, and expect me to say no if I have a lot
  1040. of other work already.  If we are having a meal that I did not agree
  1041. to as a large meal, and other people ask if they can join, please tell
  1042. them no.  In both cases, please tell them that I need a chance to
  1043. relax after the other work I will have done.
  1044.  
  1045. Please don't be surprised if I pull out my computer at dinner and
  1046. begin handling some of my email.  I have difficulty hearing when there
  1047. is noise; at dinner, when people are speaking to each other, I usually
  1048. cannot hear their words.  Rather than feel bored, or impose on
  1049. everyone by asking them to speak slowly at me, I do some work.
  1050.  
  1051. Please don't try to pressure me to "relax" instead, and fall behind on
  1052. my work.  Surely you do not really want me to have to work double the
  1053. next day to catch up (assuming I even COULD catch up).  Please do not
  1054. interfere as I do what I need to do.
  1055.  
  1056.  
  1057. Food:
  1058.  
  1059. I do not eat breakfast.  Please do not ask me any questions about
  1060. what I will do breakfast.  Please just do not bring it up.
  1061.  
  1062. I enjoy delicious food, and I like most kinds of cooking if they are
  1063. done well (the exception being that I cannot eat anything very spicy).
  1064. If I am ordering from the menu in a restaurant which has a variety,
  1065. there's no need for you to worry about the question of what I like; I
  1066. will take care of it.
  1067.  
  1068. But if you want to cook for me, or invite me to a restaurant that
  1069. specializes in just one thing, or invite me to dinner with a preset
  1070. menu, you need to know what I dislike:
  1071.  
  1072.    avocado
  1073.    eggplant, usually (there are occasional exceptions)
  1074.    hot pepper
  1075.    olives
  1076.    liver (even in trace quantities)
  1077.    stomach and intestine; other organ meats
  1078.    cooked tuna
  1079.    oysters
  1080.    egg yolk, if the taste is noticeable, except when boiled completely hard
  1081.    many strong cheeses, especially those with green fungus
  1082.    desserts that contain fruit or liqueur flavors
  1083.    sour fruits, such as grapefruit and many oranges
  1084.    beer
  1085.    coffee (though weak coffee flavor can be good in desserts)
  1086.    the taste of alcohol (so I don't drink anything stronger than wine)
  1087.  
  1088. Don't ever try to decide what food I should eat without asking me.
  1089. Never assume that I will surely like a certain dish, merely because
  1090. most people do.  Instead, ask me in advance!
  1091.  
  1092. As long as there are many alternatives to choose from, there will be
  1093. no problem.
  1094.  
  1095.  
  1096. Wine:
  1097.  
  1098. Wine is not very important to me--not like food.  I like some wines,
  1099. depending on the taste, and dislike others, but I don't remember the
  1100. names of wines I have liked, so it is useless to ask me.
  1101.  
  1102. Therefore, if you're having dinner with me, please don't ask me what
  1103. to do about wine.  I can't decide intelligently, and it matters more
  1104. to others than to me.  Have wine or don't, as you prefer; choose it to
  1105. please yourself and the others, not for me.
  1106.  
  1107. If you get a bottle of wine, I will taste it, and if I like the taste,
  1108. I will drink a little, perhaps a glass.
  1109.  
  1110.  
  1111. Restaurants:
  1112.  
  1113. So I like to go to restaurants that are good at whatever kind of food
  1114. they do.  I don't arrive with specific preferences for a kind of food
  1115. to eat--rather, I want to have whatever is good there: perhaps the
  1116. local traditional cuisine, or the food of an immigrant ethnic group
  1117. which is present in large numbers, or something unusual and original.
  1118.  
  1119. So please don't ask me "Where do you want to eat?" or "What kind of
  1120. restaurant do you want to go to?"  I can't make an intelligent
  1121. decision without knowing the facts, and unless I am already familiar
  1122. with the city we're in, I can only get those facts from you.
  1123.  
  1124. The only general thing I can tell you is that what I like or dislike
  1125. about a meal is the sensation of eating the food.  Other things, such
  1126. as the decor of a restaurant, or the view from its windows, are
  1127. secondary.  Let's choose the restaurant based on its food.
  1128.  
  1129. A good approach is to ask around *in advance* among your acquaintances
  1130. to find people who like good food and are familiar with the area's
  1131. restaurants.  They will be able to give good recommendations.
  1132.  
  1133.  
  1134. Sightseeing:
  1135.  
  1136. If I am visiting an interesting city or region, I will probably want
  1137. to do a few hours of sightseeing in between the work.  But don't try
  1138. to plan sightseeing for me without asking me first--I can only spare a
  1139. limited time for it, so I am selective about where to go.  Please
  1140. don't assume I want to see something just because it is customary to
  1141. take visitors there.  That place may be of no interest with me.
  1142. Instead, please tell me about possible places to visit--then I can say
  1143. what I would like.
  1144.  
  1145. I enjoy natural beauty such as mountains and rocky coasts, ancient
  1146. buildings, impressive and unusual modern buildings, and trains.  I
  1147. like caves, and if there is a chance to go caving I would enjoy that.
  1148. (I am just a novice as a caver.)  I often find museums interesting,
  1149. but it depends on the subject.
  1150.  
  1151. I tend to like music that has a feeling of dance in it, but I
  1152. sometimes like other kinds too.  However, I usually dislike the
  1153. various genres that are popular in the US, such as rock, country, rap,
  1154. reggae, techno, and composed American "folk".  Please tell me what
  1155. unusual music and dance forms are present; I can tell you if I am
  1156. interested.  If there is a chance to see folk dancing, I would
  1157. probably enjoy that.
  1158.  
  1159. If there is something else interesting and unique, please tell me
  1160. about it.  Maybe I will be interested.
  1161.  
  1162.  
  1163. More arrangements:
  1164.  
  1165. Once we have a precise date for the speech, my assistant will contact
  1166. you with questions about the arrangements for the trip.  Please
  1167. respond as soon as possible with the information she asks for.
  1168.  
  1169. Please do not ever mail me a file larger than 100k without asking me
  1170. first.  I almost certainly do not want to receive it in that form.  If
  1171. you would like feedback or approval for proposed publicity, please
  1172. talk with rms-assist about it, not with me.  If you want to give me
  1173. data about airplane tickets, please send that info as plain ASCII
  1174. text, not as images or PDFs.  Thank you.
  1175.  
  1176. --
  1177. Dr Richard Stallman
  1178. President, Free Software Foundation
  1179. 51 Franklin St
  1180. Boston MA 02110
  1181. USA
  1182. www.fsf.org  www.gnu.org
  1183. Skype: No way! That's nonfree (freedom-denying) software.
  1184.   Use free telephony http://directory.fsf.org/category/tel/
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top