Jonathon, 2018-04-26 1:46 GMT+02:00 toki <[email protected]>:
> > > >I'm only sad that we are not part of the discussion when we are highly > concerned. > > That probably has as much to do with where and when the discussions are > held, as anything else. > > Oliver is pretty good about providing the agenda, along with the date, > time, and place of the Documentation Team Meetings. EG: 2018-04-25 19:00 > CET https://meet.jit.si/tdfdocteam agenda at > https://pad.documentfoundation.org/p/documentation you miss the point. Changing help (documentation project) and UI (UX project) is not a self-enclosed thing. This is one of the biggest open source projects and changes in code (and UI and documentation) affect not only many community members participating in the project on different tasks, but millions of users. So we do need to copy or thoroughly adapt some of the "corporate" workflow magic and make this process a road to success, not to chaos. Those teams can and should discuss its "structural", "perspective" changes with the l10n teams. So no, all localizers should not join those two projects and their jitsi sessions, but there must be a workflow where such changes, when already thought through by its native team, get discussed with l10n teams (who are not just localizers, translators, but in most cases promoters of LO in their countries/languages/cultures and can offer a lot of advice what might not be good for their language/cultural environment/law requirements) - before they get introduced. So we need such a forum/discussion point in development process. I often remember the OOo days where every upcoming bigger feature had a webpage (a kind of a wiki page in the Sun web subworld) made by the developers, where they wrote about what they will be doing, why that is needed, how they intend to do it and there was also a screenshot of a mock-up or final UI window etc. This way a feature could be discussed with others before a lot of hard work was being done and people reading it could improve ideas and goals and that is why those features did not need so much polishing later. This iterative method of trial by error in the LO development is not a problem in itself, if this project would not need localization and if there would not be millions of users (i.e. with menus changing all the time in the last few major releases and documentation hardly following them all) - but all this iterative changing (that does lead to better and better results, no doubt about it) in the end hits the l10n teams and makes their members feel like Sisyphus. Lp, m. -- To unsubscribe e-mail to: [email protected] Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
