Ideas of things to do before first release

[JPcode05]

Right now Tenacity is still in its development stage, and we are nowhere near a beta release yet. But we still need to prepare for the final release, which is just around the corner. I've got a roadmap prepared below.

1. Tenacity should not have a Facebook page or Discord server. Discord users should try Matrix and IRC. We also have Twitter and the fediverse.

2. Should we also try YouTube, as well as Odysee and PeerTube for official tutorials and stuff, under CC-BY-SA?

3. Tenacity should have a manual at manual.tenacityaudio.org, powered by MediaWiki, just like Audacity.

4. Many people don't want to sign up for GitHub or use a Sourcehut mailing list if all they want to do is get help on the program. Audacity has a forum at forum.audacityteam.org, and Tenacity should too, powered by Discourse.

5. Tenacity should have a complete website with the Tenacity logo, inspired by audacityteam.org but without ANY trackers or use of WordPress. The website shall be FOSS under https://git.sr.ht/~tenacity/tenacityaudio.org

6. Anything "Audacity" anywhere in the source code such as AudacityApp.cpp (Use Tenacity.Project in AudacityApp.cpp #465) must be changed to Tenacity. Become independent!

I can't wait to see the success Tenacity will have, and I wonder how well it's going to beat Audacity.

Also, here's Key the Cat, our mascot for Tenacity. (Made by Semisol)

                 /\_/\
        ________(' - ')
  _____(              )
 /     (______________)
 '     | |          | |
       | |          | |  hello
       '"'          '"'

Official comments

From Semisol:

Also see: 0.1.0 milestone

Small issues:
Read more...

[Semisol]

Also see: 0.1.0 milestone

Small issues:

1. Mediawiki is too heavy on servers, so it will be a big blow in our budget, which is not what we want.
2. We plan on making a Discourse forum soon, if possible.

[Be-ing]

We could use a static site generator or Sphinx rather than Mediawiki.

[JPcode05]

There's DokuWiki, a lightweight alternative to MediaWiki. Audacity also uses a very old version of MediaWiki, as I can tell from the design.

[Semisol]

If possible can we use a static generator?
Git and patches would work well.

[JPcode05]

If possible can we use a static generator?
Git and patches would work well.

This reminds me of Microsoft Docs. They're also done on GitHub, so this seems practical just using a static site generator.

Static site generators will also allow for bundling an offline manual with the program, as Audacity did.

[Be-ing]

I suggest setting up a Discourse forum but not opening it for registration until we have a first release so we aren't overwhelmed with support requests.

[nbsp]

Many people don't want to sign up for GitHub or use a Sourcehut mailing list if all they want to do is get help on the program. Audacity has a forum at forum.audacityteam.org, and Tenacity should too, powered by Discourse.

If many people don't want to sign up for GitHub, shouldn't we use a solution that doesn't require setting up any account? A mailing list, to me, seems like the most obvious and simple solution.

or use a Sourcehut mailing list if all they want to do is get help on the program.

I don't even understand what this argument is. Using a mailing list doesn't require searching through the (arguably confusing) archives -- in fact, it doesn't require using the Web at all. Most of the usual sourcehut-specific arguments don't apply here either. For all intents and purposes, a mailing list is a forum.

Regardless, I don't understand the need for both a mailing list and a Discourse forum, when they serve exactly the same purpose. I don't know why this Discussions tab is still open.

[sosasees]

I just made a Splash Screen design with Key:

Original Inkscape SVG file (zipped, Light and Dark designs as different Layers):
splash.svg.zip

Just like the other Tenacity Assets made before this, it's licensed under CC-BY-4.0.

Not only I should be attrbuted to these splash screen designs if used,
but also @Semisol because I inserted the tenacity mascot Key who was made by @Semisol.

---

This design is inspired by

• @Semisol's tenacity mascot Key
• @akleja's tenacity logo
• my Tenacity webpage design,
  which was inspired by the tenacity logo and the original Tenacity website.

[sosasees]

Thanks for letting me know.
I had previously completely missed that I should always write "Tenacity Community" instead of "Tenacity Team".
This will be very useful in many future contributions.

[nbsp]

I personally like how the splash screen looks now. Simple, short, not overwhelming you with information.

[Paul-Licameli]

Are you implying a false claim of copyright to the inherited code from Audacity that you re-use as GPL licensees only?

[leio]

Audacity authors are part of Tenacity Community in this sense, the more exact details are found in the about dialog right now. Perhaps "Tenacity Contributors" would have covered it better in this sense.
Copyright notice is just that - a notice, that in very limited circumstances may improve the standing of copyright claims in a court of law, for when the Audacity authors code is being violated as well, but probably doesn't make any difference whatsoever (if a notice is there or not). There's Berne Convention for that. IANAL.

Personally I was only pointing out tenacityteam vs a readable thing, any copyright notice stuff can go away from a splash screen completely, as far as I'm concerned. Maybe it should just be a "by MaintainingGroup" kind of thing, but it being the same name, not some big company, it's kind of redundant and imo lets just remove it from splash screen? (and under that, I mean remove it from a design proposal that isn't even in use in the application so far as far as I know)

[sosasees]

I also think that the copyright notice should stay in the "About" page.