Replace references to audacityteam.org

[abb128]

The README, CODE_OF_CONDUCT, and many source files contain references to audacityteam.org webpages and email addresses. These should probably be changed.

[n0toose]

I'd suggest that we keep the Code of Conduct completely intact for the time being.

[amrithmmh]

it has refernce for audacity website,forum, wiki. Should we first make a new website, forum, wiki ?

[web3Gurung]

I had the same question!

Also, should we really remove the email addresses?

Another doubt, I saw this url (http://bugzilla.audacityteam.org), so should it be removed or edited to "http://bugzilla.tenacityteam.org"? Since I doubt, we have a bugzilla page with tenacityteam.org / tenacityaudio.org.

[JPcode05]

Well, if people want to view the old Audacity stuff (because there were a lot of questions asked on the old forum), we should provide links just in case.

[kanissh]

Does the occurrence of the name Audacity needs to change to Tenacity in those files?

[Tc-001]

Could probably replace them to a tenacity url, but make the server disay a placeholder/stub page, with links to both audacity and tenacity resources. In the future the docs could be crawled or stub loads logged in some way to slowly populate with actual info

[emabrey]

See #175

Weblate integration will make modification of the gettext strings containing this URL easy.

[web3Gurung]

Is someone working on this issue? I can change the references from "Audacity" to "Tenacity" only in the comments since I dont want to break the code. Let me know if it has to be done!

[nbsp]

Is someone working on this issue? I can change the references from "Audacity" to "Tenacity" only in the comments since I dont want to break the code. Let me know if it has to be done!

There isn't any PR linked to this issue, so I'm assuming no one's working on it.

[web3Gurung]

Alright, I'll work on this issue for this weekend. I'll only be working on modifying the comments which says "Audacity" to "Tenacity".

[web3Gurung]

Not sure, but seems like this commit has fixed the issue.

[n0toose]

@emabrey We need further feedback, what steps does a person have to make (the ones further than just replacing the parameters of XO() functions)?

[emabrey]

@emabrey We need further feedback, what steps does a person have to make (the ones further than just replacing the parameters of XO() functions)?

The XO functions are doing a map lookup, where what you pass is a key. If you change the key in only one place, the values (translations) won't follow. If you want to update the content of an XO you need to do so for every locale (PO files).

[humrochagf]

No need to do this work manually, you can just change it at the XO() call and then cd into locale dir and run ./update_po_files.sh so the translation extension will handle the string matching and its mapping into the translation files.

I tried it locally and it's working, the only issue is that there's a long time the PO files weren't updated, so the diff with the previously added and changed strings is quite big.

My recommendation is to merge the latest updates from the translation files that come from weblate (so you don't get a huge conflict to solve) then right after, run the update_po_files.sh to update everything that was already changed, and then start working on changing the XO() string updates so you can get cleaner diffs.

Also, the update_po_files.sh could be added into the pull_request pipeline to prevent this accumulation of updates to be made to the PO files.

[n0toose]

@humrochagf Thank you so much for looking into this for us, you really saved us from a lot of trouble and hesitation here.

[humrochagf]

no problem, glad to be able to help 😁