s/on stream/by voice/

1 files changed, 5 insertions, 5 deletions

diff --git a/2021/talks/maintainers.md b/2021/talks/maintainers.md
index d0c96b95..9a30d47b 100644
--- a/2021/talks/maintainers.md
+++ b/2021/talks/maintainers.md
@@ -27,11 +27,11 @@ Pad:
 -   Q2: (Maybe answer this last, if time permits) How did you come to start using Org?
     -   A: Bastien started with his own library BHL and was introduced/invited to contribute to Org by Carsten.
 -   Q3: You have recently overseen a major transition for org mode maintenance, what would you advise for other teams that are preparing for transitions so that processes can be maintained with minimal disruption? How do we take processes that were originally maintained by a single person to one maintained by multiple people?
-    -   A: (Probably answered on stream.)
+    -   A: (Probably answered by voice.)
 -   Q4: What do you think about the latest Orgdown thing? (Yes, it's me, Karl :-) )
-    -   A: (Probably answered on stream.)
+    -   A: (Probably answered by voice.)
 -   Q5: Could you settle this "Org" vs "Org-mode" vs "orgmode" vs ... once and for all (i.e. which one, capitalized how, and where)? :)
-    -   A: (Probably answered on stream.)
+    -   A: (Probably answered by voice.)
 -   Q6: Does this mean that you do not need to be technical to be(come) a maintainer? Would that really work?
     -   A: The co-maintainer could be a person with less technical background.
 -   Q7: If time — what does the day of the orgmode maintainer look like? Lots of hours of work every day? Spread out?
@@ -39,14 +39,14 @@ Pad:
 -   Q8: Thanks for the hard work.  Which place is the right place to request a dark mode for orgmode.org website ?
     -   A: write an email to the Org-mode team. This seems to be a reasonable request.
 -   Q9:  Do you think having centralized roles for people to carry out certain tasks such as documentation across multiple areas would be a constructive approach to inviting new maintainers (in contrast to "every person take an issue of their own choosing", which leaves parts of maintenance and documentation neglected)? From personal experience, sometimes it can be easier for those to be told "hey, we need this area maintanined, or a focus on contribution to this particular area". If we take a page from Catalonian Spain of the early 1900's, even the most decentralized organizations have to dedicate certain persons to specific tasks. Sorry for the long winded question.
-    -   A: (Probably answered on stream.)
+    -   A: (Probably answered by voice.)
 -   Q10:  I think org has and may potentially greatly influence Emacs development.  If you would tend to agree, do you have places where you feel Emacs need to "pull back" harder, to incluence org?  Key areas where org is clearly "leading the way"?
     -   A: "Org is to Emacs was Emacs is to computer systems"
 -   Q11: Could you expound a little on what's happening with contrib ... I'm a little confused.   Mechanics/technical. 
     -   (Karl: Do you mean technically "how to migrate" or the background why this happened? I personally did the conversion this week. I got the separate repository (or package) and had to do more local "use-packages" (the way of loading elisp files in my setup) and that's it. The hard thing was to find out which error refers to which org file to load separately.)  Thanks.  Seems like time for bankrupcy again :-/.
     -   A: contrib = stuff that didn't go to Emacs (copyright assignment not necessary). This was not a clean solution because it was mixed with copyright-transferred files in the same repository. New contrib goes now to "non-GNU" which is a clear separation according to copyright assignments. The way to install Org is via Org MELPA and contrib for Non-GNU MELPA. YES.  THANKS.
 -   Q12: (Maybe not a question, just an observation) I like the analogy to gardening.  FOSS projects seem much like community gardens.  Also, shepherding seems like an apt analogy; I could imagine files having "shepherds"  :)
-    -   A: (Probably answered on stream.)
+    -   A: (Probably answered by voice.)
 -   Q13: Has splitting contrib actually reduced maintenance load? Is it too soon to tell? (I have found that splitting repos ultimately increases maintenance overhead due to multiplying release overhead etc.)
     -   A: It is clearly easier now and less confusing for contributors. org-contrib is soon to die: packages will be moved to their own packages since contrib was founded when there was no packaging around. 
 -   Q14:  So was BHL the basis for org-export?