I figured it was about time we had a thread for the admin. tasks needed
for 2.0 (such as Manual, Translations, web site), instead of scattered
in different threads, so here goes...
| From Bill Wharrie <
[hidden email]>
| Wed, 4 Nov 2009 19:40:29 -0500
| Subject: [Audacity-devel] Large commit coming -- VS project will need updating
> On 4-Nov-09, at 7:15 PM, Martyn Shaw wrote:
>
> > Manual is great! We need more hands on that! In my opinion it does
> > not have to be perfect for 2.0...
A break from "tradition", and it won't be perfect (that's one of the
"consequences to be suffered" of "sticking to a date", and of the limited
notice given of that date. :=). It will be as good as can be without
everyone getting hernias on the way there:=) And we've been aiming
higher than before, I think, too.
The Manual will definitely need a "disclaimer".
I've now sent Ed and Vidyashakar details of their accounts on the
Manual, as they kindly offered to help. Thanks!
> ... but obviously not have majorshortcomings.
What's there is presentable visually, mostly not yet fully checked over
for correct content, but likely to be "pretty good" from what I've seen.
If it wasn't for Bill and John, we'd be nowhere near. Thanks, both.
Any "consistency" problems such as "all pages in a section presenting
content in the same way" will have to be left for post 2.0. Content
matters more.
There are definite gaps (whole pages or sections), mostly because
they need specialist technical input from the authors of those parts of
the program. Off the top of my head, Compressor, Truncate Silence and
Plot Spectrum would be examples. Phil's told me he hopes to help with
some of that soon. We may need to keep track of those special cases
here.
"Accessibility" is missing but I hope David Bailes will be able to deal
with that. Let us know if you are still on track with that, please David.
> > I'm not doing 'manual' stuff.
I couldn't rule out your being asked for some specific help for one or two
bits.
One specific about the compressor. You said you could take out the
yellow threshold line for 2.0. Would you like to do that? It would help
documentation and support issues arising from the "pinned to upper
right" change.
As to what I might do, I'd given myself the job of approving pages for
release, and updating FAQ and Quick Help. Don't know. Still have loads
of Audacity e-mail to do every day before starting to read here. I'll make
a stab at Quick Help. FAQ may not be updated. I think "approving" could
be done more cursorily than I'd have liked (that's something others on
Team might be able to help with). But with the "disclaimer", I suppose
we don't have to worry "too" much.
> > I remember now that I thought about marking any pages about 'linking'
> > as 'not for the included manual'. Are there any and how do we mark
> > them as such, I don't recall.
>
> James had some input on that, and here's what it looks like:
>
>
http://manual.audacityteam.org/index.php?title=Label_Tracks#Linking_labels_with_audio_tracks>
> Similar alert boxes whenever the manual refers to linking.
I agree with Martyn that a "1.3.10 Beta" with "linking on" makes no
sense in the current position. Instead of the alert saying "It is
available in the beta versions of Audacity for 1.3.x and later", I
suggest when we release 2.0 we say "It was last available in 1.3.9
Beta" and give them a link.
> As I recall, the decision was made not to hide the sections as there
> will likely be some 1.3.x users referring to the manual, plus we'll
> want it included once the next 2.x beta with linking enabled is
> released.
>
> But Gale is the one to talk to about these kinds of policy decisions.
> I'm just a worker drone. ;-)
Or James, if he has the time. Online will see the text with the explanation
that linking is only in Beta. The manual dump will exclude it.
*Translations*
Translations of the Manual are ongoing, using the ad-hoc system of
adding a locale suffix to each page. No translations will be complete,
(or were expected to be), though a group of French translators were
hoping to complete had we more time than we now do.
Post 2.0, I hope we will get more interest in translating the Manual. If so,
we should revisit if we can have a better "system" such as language
subdomains, and automated indications of whether a translated version
of a given page is available.
Software translations aren't too badly off for the most important languages
as far as I can see. But we should declare a string freeze and give
translators a chance to do their job at the earliest opportunity. If the string
freeze is still a little way off, shouldn't we warn translators now what's
going on? Shall I do that, or Richard, maybe?
Gale
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
