https://bugs.kde.org/show_bug.cgi?id=423171
--- Comment #12 from Claudius Ellsel <claudius.ell...@live.de> --- (In reply to Luigi Toscano from comment #10) > (In reply to Claudius Ellsel from comment #9) > > (In reply to Luigi Toscano from comment #8) > > > (In reply to Claudius Ellsel from comment #7) > In the list archives, and this can be improved (probably in the workboard of > the Localization project). But it has been mentioned in that ticket. Alright. I was thinking about documenting every need in one place. Thus there can be consenseus reached and interested people would not have to scrape together the relevant information. I will put together some first version soon. > > > Switching the underlying storage is not a problem: the people who works > > > with > > > it are fine with subversion, the people who want a graphical system don't > > > care about what it is about. This is not to say that it can't be changed, > > > but it is the very last step, after a lot of automation is in place. > > > > I care about what the version control system is about. Also it might limit > > possible web-based solutions since I read on the mailing list that not all > > support SVN (weblate seems to do so, though). It might also be beneficial to > > switch to git (GitLab) first before adding a web-based interface. > > The most promising solution (weblate) seems to work with svn. I still > consider this not a blocker for the first evaluation. I fully agree. I just wanted to point out that while it is mostly independent of the web-based translation interface introduction, it still might be beneficial. And it might save some work to do that together so one does not have to first adapt a web-based solution to the SVN workflow and soon have to change that to git. But I am fine any way. If it is faster and more staightforward to just do it with the SVN backend, no problem. > > > A non-free software is out of question. > > > > Since this is a drastic statement affecting the possibile solutions pretty > > much, can you link a source for that policy? > > Not that I'm aware of, but no one ever considered using a non-hosted FLOSS > solution for repository. No vendor lock in, I think that's the basic. Alright. I also understand that way of thinking and with weblate there is seems to be a nice FLOSS solution available, so that is fine. > The workflow can be improved (the flattening itself is already a small > breaking change). Nothing I personally said conflicts with this. Alright. > > I was mainly complaining about not finding any documentation that explains > > how to easily get started with contribution. I just wanted to fix a small > > error and did not find any documentation explaining me what steps I need to > > do to fix that. I ended up filing a bug report here since I did not see me > > fixing it myself in a reasonable amount of time. > > For the record, I forgot to answer about this. Your original issue, if I > understand it correctly, was about a fix. Right now the solution is: file a > bug against the i18n product, your language as component. > > Regarding contributions: the place again should be the workboard of the > Localization project. Some of the points I explained above are missing. > Automation first, then let's move forward. Alright, I will look into adding that to the current documentation. Ideally in the future that can be improved so I can easily fix those things myself. (In reply to Luigi Toscano from comment #11) > I forgot to mention this presentation from Akademy 2017 in Almeria, which > summarizes the full status: > https://conf.kde.org/en/akademy2017/public/events/377 Thanks, I had a short look. Unfortunately that topic seems to be pretty complicated, so I will most likely need a more thorough look and read the documentation in more detail. Currently I still don't fully understand the current workflow. -- You are receiving this mail because: You are watching all bug changes.
