search

w3c / translation-management

Workflow to manage volunteer translations of W3C documents
https://www.w3.org/Consortium/Translation/
31 stars 19 forks source link

Manage shortname change #11

Open dontcallmedom opened 5 years ago

dontcallmedom commented 5 years ago

The proposed new translation workflow proposes to create repository names for translations based on the shortname of the spec under translation.

But these shortnames can change - the translation workflow should accommodate for that possibility.

StefanSTS commented 5 years ago

Hello Dom,

are we talking about names and "folders" like REC-rdfa-core-20120607

Having a repository for REC-rdfa-core-20120607 will be fine. Sorting it by year like it's done until now will keep the folder structure a bit easier to overlook.

2012/REC-rdfa-core-20120607

Sorting it via technology area might be not so quickly to find.

That the names changes from CR, PR and so on should be fine. Having it like rdfa-core-20120607-REC would make it easier to sort by technology, but I guess there are other nice filtering methods.

dontcallmedom commented 5 years ago

I was talking about the names of the github repositories where the translations would be hosted. My current thinking is that they would be à la "rdfa-core.fr" (i.e. non dated) - the linkage to a specific dated version would be managed separately.

Likewise, my expectation is that in most cases, people wouldn't go through github to find the relevant repo (or translation), but would instead use the translation page we're working on rebuilding in W3C. That translation page would indeed provide different filtering methods (with details still TBD)