Where is project ?

I can create it, I thought it was just a generic extension for MEdiaWiki and it is also part of the messagegroup for ALL MediaWiki messages. I has not included as part of Lingua Libre too. Note that most Mediawiki extensions don't have their own "Translating:Page", there are really many (and ti takes time to create them, index them, find relevant identifiers for statistics)!

But nothing prohibit creating a specific page to show statistics for a specific one.

I would suggest however keeping only one page for the UI and its API grouped together. We can still display statistics for both individually, while giving a common description. For now, this was never asked for all the zillions extensions of Mediawiki, which just use the parent page "Translating:MediaWiki". Note that some MediaWiki not created nad managed by Wikimedia, such as Miraheze extensions and BlueSpice extensions, have their own "Translating:Miraheze" and "Translating:BlueSpice" parent page, listing all their subgroups, as they also have a supergroup grouping them all together (and they are not counted in the "MediaWiki (all)" supergroup.

Is there something specific in that extension for Lingua Libre? Or was it developed for specifically Lingua Libre as a component necessary to build the database to be used used by the Signit tool?

Verdy p (talk)17:45, 10 August 2022

Salut Verdy p ! ♥___♥
Several things there make Record Wizard an odd project !

  • It is technically a MediaWiki extension, but it requires a wikibase, Oauth connextion to Commons, which make it a one shot with no vocation to be deployed elsewhere.
  • It is planed (2023) to decouple it from MediaWiki, making it a standalone HTML/CSS/JS Single page app relying on Commons' Wikibase. MediaWiki extension part, out ! It will lighten maintenance and developemnt costs. The texts and translations would stay the same.
  • It works in the field of languages diversity, with language conservationists, activists, so we have higher and wider translations requirements. For those, I/We need a clear landing spot on TranslateWiki so I can redirect mitority speakers to it.

This being stated, we may be in a case where it worth splitting away from Translating:MediaWiki if translation rate stay similar.

Yug (talk)21:07, 10 August 2022

I will create the page just like I did for SignIt.

But the Record Wizard seems tobe usable for any other use in Commons, than just SignIt. Users could as well upload their audio or video records without necessarily feeding the SignIt database.

For example free casts to be used in Wikinews, or recorded lesssons for Wikiversity, or keynote presentations in Wikimania and other meetings, or free musical performances. It's basically just a wizard used to simplify the upload and check that everything is correctly indexed in Commons, and Wikidata. SignIt may need specific categories or data in Wikidata and some format restrictions (such as duration, and synchronization with timed text, and correct identification of the language, or a set of selectable languages for translated subtitles): using external tools is still possible, but they are not necessarily integrated enough with Wikimedia Commons and Wikidata, and many things are manual or lengthy for users, the wizard can automate these steps to avoid basic errors or "boring" syntaxes.

Anyway for now you just have a Mozilla extension. However most users don't have a Mozilla-based browser; most of them use now a Chromium-based browser (including Chrome, Edge, or Vivaldi) or extensions for Safari (MacOS and iPhones). Firefox is fading now, including on Linux even if it is still installed by default in many distribs (but no longer all of them, they already have difficulties to maintain these Mozzilla extensions which have serious security and stability problems). Are you working to port this SignIt extension to Chromium or Safari?

Verdy p (talk)00:00, 11 August 2022

Record Wizard current main application is to upload thousands clean audios (and few videos) words to Commons.

Then, three systems are used to spread an consume those medias :

  1. User:Lingua Libre Bot add those files to relevant Wiktionary pages (fr,oc,shy,ku and wikidata), so users can play them
  2. Downloadable datasets, for developers to create apps.
  3. Lingualibre:Apps, other apps using our medias

We have discussion about futher recordings features for longer texts but we lack human resources to lead those developments.

As for extensions diversification, the Firefox to Chrome adaptation is straight forward. Bu since SignIt is still in active development for i18n and other needed sugar, this diversification is "for later", when the code is truly stable. I haven't investigated Safari yet.

Yug (talk)07:17, 11 August 2022
 

Oh, I'm discovering there is a way to share a landing page for a given sub-project. Example : Record Wizard -> atj. It's just we have to know translatewiki's UI to search properly and find it. I understand better.

This being, and given translatewiki reasonable mindset to avoid project multiplication in order to keep maintenance edits low... It could be best to put both RecordWizard (150 messages) and the new SignIt (~30) under a Lingualibre umbrella. The human-friendly Translating:Lingua Libre SignIt could easily be changed into an umbrella Translating:Lingua Libre group. I could handle 3 sub-section pointing to bug trackers, referent users, link to project-specific translation. With such renaming you can keep the logo and a bunch of things (categorized users). Verdy, what do you think of this approach.

Yug (talk)08:21, 11 August 2022