<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Hi Mick:</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">I agree that what's important to the end user is feature and function, not version/release number as such. Certainly incremental releases (like the difference between 2.2.1 and 2.2.2) don't typically merit an update
to the documentation. But here we're talking essentially about the delta between an initial stable release (1.1) and a release some years later (2.x); and having nearly completed the revision I can say that about 40% of the functionality is new altogether,
and much of the rest has new GUI look/feel and arrangement, and/or is found in a new place in the main menu system than in the first release. When and if the time comes, we'll see what the delta is between 2.x and 3.x; but I'm guessing a new revision of the
FM would be appropriate then too. Meanwhile users of the newly-revised book will at least know they are dealing with the Audacity feature-set as of late 2017.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Matt</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of Mick Chesterman <M.Chesterman@mmu.ac.uk><br>
<b>Sent:</b> Wednesday, January 10, 2018 2:26 AM<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</font>
<div> </div>
</div>
<div lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Hi there,
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Regarding not including version numbers.
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">It’s not a strong opinion but it’s based on some software which changes version a lot but not necessarily function.
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">In that case it can mean the process of patching up docs and just making small changes where there is new functionality is harder, or may appear harder as
an editor may think they need to update the whole manual which might be too big a job for them to take on, or at least to finish.
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">In any case I would trust your judgement on this for the Audacity manuals.
</span><i><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:#44546A"></span></i></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Thx
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Mick</span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> Discuss [mailto:discuss-bounces@lists.flossmanuals.net]
<b>On Behalf Of </b>M R<br>
<b>Sent:</b> 08 January 2018 06:19<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<div id="x_divtagdefaultwrapper">
<p><span style="font-family:"Calibri",sans-serif; color:black">Mick:</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">Ok, this is well underway, though it's going to take some time as there is fairly major delta between Audacity 1.x and 2.2, with a great deal of feature rearranging and many outright new features, which
I'm having to spin up on through a mix of experimentation and appeal to the audacity org documentation. But it's exactly the sort of practice I wanted, and I need it now so the rewrite will move ahead with all deliberate speed. I haven't tackled the tutorials
part yet, and can't swear that I'll keep the original tasks exactly as they were, but all the basic chapter subjects will certainly be preserved. </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">Btw, I'm not completely sold on the idea of eliminating all references to release/version numbers, which currently appear at the start of each chapter and a few other places. If someone tried
to use the current manual and didn't realize it was years out of date, they'd be lost in some fairly important ways. Clearly the need for this kind of update is burdensome, and I wouldn't advocate it in the Floss context for more than maybe first-order versions
(ie 1.x vs 2.x), but I'm not seeing any good purpose to burying the delta itself. Can you share your thinking on this?</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">best,</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">Matt</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri",sans-serif; color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="x_divRplyFwdMsg">
<p class="x_MsoNormal"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of Mick Chesterman <<a href="mailto:M.Chesterman@mmu.ac.uk">M.Chesterman@mmu.ac.uk</a>><br>
<b>Sent:</b> Sunday, January 7, 2018 1:35 AM<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:black">
</span></p>
<div>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
</div>
</div>
<div>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Hi Matt,
</span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">That sounds good,
</span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Unfortunately as I migrated 95% of the books in from the last system, I'm down as the owner for all of those. </span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">I would say that where possible it would be good to take out references to software version numbers when we come across them.
</span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Thanks</span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Mick</span></p>
<p class="x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_MsoNormal" align="center" style="text-align:center; background:white">
<span style="font-family:"Calibri",sans-serif; color:#212121">
<hr size="2" width="98%" align="center">
</span></div>
<div id="x_x_divRplyFwdMsg">
<p class="x_MsoNormal" style="background:white"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of M R <<a href="mailto:matrobnew@hotmail.com">matrobnew@hotmail.com</a>><br>
<b>Sent:</b> 06 January 2018 01:11<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:#212121">
</span></p>
<div>
<p class="x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:#212121"> </span></p>
</div>
</div>
<div>
<div id="x_x_divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Actually I see it was Ryan who started the substantive updating in June, so I guess my question below is addressed to Ryan (hi Ryan) as much as Mick. </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Matt </span></p>
<p class="x_MsoNormal" style="margin-bottom:12.0pt; background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_MsoNormal" align="center" style="text-align:center; background:white">
<span style="font-family:"Calibri",sans-serif; color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="x_x_divRplyFwdMsg">
<p class="x_MsoNormal" style="background:white"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of M R <<a href="mailto:matrobnew@hotmail.com">matrobnew@hotmail.com</a>><br>
<b>Sent:</b> Friday, January 5, 2018 6:09 PM<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:black">
</span></p>
<div>
<p class="x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
</div>
</div>
<div>
<div id="x_x_x_divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Hi Mick:</span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">One of your many hats here seems to be owner of the Audacity book. In that capacity, I wonder what you'd like to see done next with that book as it currently stands. It
looks like back in June of last year you did some preliminary work to acknowledge the then-current version 2.1.3 (we're now at 2.2.1), but as far as I can tell most of the extant screenshots and feature discussions throughout the book (other than the installation
stuff you worked on) still refer to 1.x. So would it be useful for me to just start working chapter by chapter to update screenshots and (where necessary) feature discussions to 2.2.x? I wouldn't be doing anything other than updating within the existing
framework, and no fancy innovations like screen vids </span><span style="font-family:"Segoe UI Symbol",sans-serif; color:black">😊</span><span style="font-family:"Calibri",sans-serif; color:black"> Just addressing the delta from 1.x. What do you think?</span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Matt</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">"Before acting on this email or opening any attachments you should read the Manchester Metropolitan University email disclaimer available on its website
<a href="http://www.mmu.ac.uk/emaildisclaimer">http://www.mmu.ac.uk/emaildisclaimer</a> "
</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>