I skimmed the translation page. That seems like a good start.

https://trisquel.info/en/wiki/website-translations

We should probably have regular team meetings and/or council meetings. Even if this meant at certain intervals. Like weekly prior to the run up to a release. This way we could make sure the pages were translated before the official release. Working alongside Rubén makes more sense than doing translations after the fact.

Small teams could probably be contacted by a team lead whose responsibility it would be to confirm the translation team(s) are doing the translations and report back to the council any problems/changes/etc.

This brings up another good point. As far as I know we don't really have an official roadmap. That's ok. But we should document in a calendar/wiki when, where, and who is responsible for what aspects. I was looking at the documentation and noticed something was written up for 4.0. Wow- is that an old release. Again maybe a documentation lead / lead coordinator can take this responsibility and update that.

Then either automate the emails to alert translator and others of upcoming obligations (translation prior to a release for instance). This would give people time figure out when they will have time. As opposed to translators maybe or maybe not knowing a release was even made available. And then users having to wait even longer for the translations.

I have gone and added a wiki page here:

https://trisquel.info/en/wiki/proposed-policies-procedures-solutions


What problems did I leave out of that? What solutions are bad/or what solutions might be better? Whom should we put into the proposed leadership slots? Which posts should we eliminate? There are probably too many posts right now. There aren't going to be enough people to fill them all. Maybe we can merge some.


I'll let others edit and add themselves (or others) in some of the spots. The list of below volunteers can be used as a basis. The descriptions of people are taken from this forum so if anything is badly worded/offensive please fix it. I wrote that out without much thought or intention to publish as is publicly. Use it like 'scrap paper'.


Reply via email to