Editability for non-apertium developers

[unhammer]

With the old, wiki-based tests, it was possible for people who didn't have apertium/git/developer-knowhow installed – but linguistic knowledge – to check and edit tests in a basic web UI. I didn't even know about this workflow before, but apparantly it happened a lot with the sme pairs. What are the possibilities for making the current regtests editable by non-developer linguists?

• Editing through Github – possible, but gold/input are in different files and it seems very easy to mess up the hashes
• Run apertium-regtest web on a server – possible, but then you have to deal with logins and access
• Some kind of export/import/sync to e.g. wiki – sounds complicated and fragile
• Other ideas?

[TinoDidriksen]

<TinoDidriksen> As for #6, we have beta where all languages/pairs are installed from nightly builds. Can't be that hard to call the same pipes for some regtest-lite auto-PR maker. <Unhammer> like generate some html from latest tests in git, make the gold an editable <input>, a submit button that sends to a github bot

[mr-martian]

So, have a second script or a server mode in the main script (probably the former, imo) that

1. presents the tests
2. gets changes/additions/deletions from the user
3. writes them to the files
4. creates a git commit using credentials in some config file
5. pushes that commit to some branch

The main question that comes to mind is what aspects should be editable in this interface.

I was also wondering how to determine what branch to push to, but that could also be in the server config and just have multiple changes get combined into a single PR.

[unhammer]

The main question that comes to mind is what aspects should be editable in this interface.

I'd say input and gold(s).

[mr-martian]

presumably just golds of the final step?

[unhammer]

Definitely just final step, yes