-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-06-04 15:32, Andrej N. Gritsenko wrote: > Martin Bagge have written on Monday, 4 June, at 14:18: >> On 2012-06-04 12:12, Andrej N. Gritsenko wrote: >>> Probably you don't read pcmanfm-develop mailing list a lot. :) >> Care to link the relevant message? I guess I need to adjust my >> schedule. > http://sourceforge.net/mailarchive/message.php?msg_id=28420018
18th of November last year. I repsonded to that one the day after indeed. Was that really what you was referring to? "I'm not able to give a nice time table or release schedule since I have to find some spare time for coding. I, however, have did my best to at least define some clear goals for 1.0 release in this bug list. There will be no change in strings/translations, or UI." No time table and no planned changes to strings. This is not a freeze announcement. And I don't think a six month string freeze will ever be planned. We usually leave two/three weeks as freezes. Maximum. If I can vote in such a decision in the future I would prefer it to be no more than that. A freeze is bad for development pace and should be kept to a minimum. >> I am very sorry for missing out on answers, if you were expecting >> any answers please help me in finding those messages. I probably >> just skipped them as not needing any action. > > Last one was Message-ID: <[email protected]> (in > the archive: > http://sourceforge.net/mailarchive/message.php?msg_id=29341363) I > clearly said it needs translators activity. :) translators != translator coordinator Sorry but I do this distinction. What would have triggered anything would have been "this needs to be released ASAP" from pcman, then I would have done the usual PO file sync, I am sure you have seen those committs in the git log. >> Translations should not be in the tracker. I have all those mails >> stacked to "later when I get time to poke with them" aka "never". >> Use the Pootle server, we stopped pulling translations from the >> tracker almost more than two years ago. > > I've registered on pooltle. I wanted to queue my changes there but > THERE WAS NO CHOICES found - the site says 100% is done and nothing > to ever do. Either add a possibility to add corrections to any of > completed translations or don't overwrite Git changes. Otherwise it's > weird to refuse any contributions into translations, it will push out > many people who was interested to help as soon they find out their > help not wanted. And also I _highly_ dislike Web-based translation > engine, it's a _huge_ inconvenience for me. Give possibility either > to send you changes via e-mail or push it into some kind of Git. I guess I need to be detailed about my workflow for you to understand what I meant. Admittedly it was a bit sloppy described. If you are sure that there will never be a change in the file in the Pootle server you can always work via git. No problem. The problem startas when you push things from git and somebody else changes the same thing in the Pootle server and git fails to merge it. My mother tounge is Swedish, I do manage to work with Norweigan, Danish and German but all other languages are years away from me and because of this I can not do merges of translations. The solution was that we honor work done in Pootle and I will always use the change in Pootle (as long as it was not OLD++ to begin with). If this process doesn't suite you and you convince the community that we need another process I will not object at all but as long as you are the only one supporting the idea that "I am doing it wrong"[1] I will just ignore the request. Use git if you like, be careful, communicate with your fellow translators and merge with master as much as you like. I will continue to use Pootle as master server for translations until further notice. If web based translations are better or worse than anything I leave to other to judge. The interesting thing is that we actually have some active contributors in this field and they generally don't complain. I send the announcement about time frames to update strings every now and then. It looks like it works, even thought you claim it doesn't and that it pushes people out of contributing. So when we do a release it generally looks like this. 1. Update the master. 2. Sync POT file. 3. Sync PO files with POT file. 4. Send announcement with time period to last translator+translation [email protected] 5. Wait the time period out. 6. Commit any left over work (even though the translators should take care of that problem themselves.... hourly update of sloppyness: http://lxde.bsnet.se/~brother/l10n_status.txt ) 7. Make sure the build is still working as expected. 8. Bump version string. 9. Tag. 10. Make dist file. 11. Upload file to sf.net 12. Blog the release notes and link to git log entries. If you don't like the web UI but don't want to git push you can still do offline translations by fetching the file from the Pootle server and then just upload it to the server. Yes you need to upload it using the web interface but it's as close to the workflow that it doesn't show any differences really. The files are located here: http://pootle.lxde.bsnet.se/export/lxde/ The git clone exposed there is updated every hour. Download the po file, update it, login to pootle and then navigate to the po directory and select upload in the bottom left and then do not forget to go to the review tab and click the commit to vcs link to get it pushed to the master server. Actions needed now. - release plan for libfm/pcmanfm. - pcman? I'll get back on this in some days. - is the l10n coordination of LXDE/pcmanfm broken? - if yes: who want to take over correct it? (not me) [1] This broken scheme has been working more than two years. I am not sure what problem you have seen from it, resetted translations has happened less than ten times in that time frame. See the git log. - -- brother http://sis.bthstudent.se -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJPzMCxAAoJEJbdSEaj0jV795EIALUrQA++vgPMDAgpRoLBaFeq MMErcPqObW1QUeIE2xHdCG7XV98H0vkNJ5Mdo6cbx9xZaI4xBw9KLY6DNkWgIPu+ dMnJsyq+7lUdHOTLTODUxNw+FHgkIPcRMXmFZ6VL9jGkOLs54zLNYgr42gkR7l35 buDvvg7TzI6WNQfiugaDoj6+a7Mcsmx8R/j/rX8At+EyY4CA2Kfc/2alfXUGJvzl b+++z6i7gEsZSOySFplEpEsw5Q/39h73rdKLTAISoVn6UnBIYssv2lyexApOkxhP vTHTEFhoR4KdSbk9Dwdbar3UpTRGfiwDOXu2OAWbzs6X+U0H4t9fhNFzEW23n1k= =hRdg -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Pcmanfm-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop
