Bug#575482: Propose to NMU icoutils
Hi Helge, hi Colin, Helge Kreutzmann: Colin Watson wrote: While I can and do often deal with forwarding patches of various kinds upstream, I'm afraid I'm only willing to do this when I think I'll be able to effectively respond to any feedback the upstream maintainer might have. In the case of translations I generally can't do this, and it's very much better for the translator to be in direct contact with upstream. I perfectly understand. Thanks for providing the contact information, I'm sure Chris will respond. Ok. I will update this translation and send it to upstream. Kind regards, Chris
Bug#575482: Propose to NMU icoutils
Hello Colin, On Wed, Jan 09, 2019 at 12:19:22PM +, Colin Watson wrote: > On Wed, Jan 09, 2019 at 11:20:03AM +0100, Helge Kreutzmann wrote: > > On Tue, Jan 08, 2019 at 09:53:31PM +, Colin Watson wrote: > > If you have an upstream first policy, it would be sensible > > (considering your users and the translators investing time and > > proofreading people doing the same) to at least inform the submitter > > (and the BTS) about it. Ideally you would forward it to upstream as > > translators usually do not have the intrinsic knowledge of how > > upstream works as you have as maintainer. > > Surely it's always the case that translations should go as far upstream > as possible? I find it surprising that this isn't something translators > would be aware of as a general practice. I work on cases where the translation is only carried in Debian, so this is not an ideal situation but does occur. > CCing Chris; could you please send this translation upstream (noting > that Helge made some updates, so grab the current version from the > archive) so that it can be incorporated and maintained there? The > upstream homepage is at https://www.nongnu.org/icoutils/ and includes > contact information; IME Frank is generally pretty responsive. Thanks for the pointer. Chris: I did not change your translation but only the patch included in the package, i.e. the header and the changelog entry. > > Alternatively (or if you are kind) you could already forward it > > upstream. > > While I can and do often deal with forwarding patches of various kinds > upstream, I'm afraid I'm only willing to do this when I think I'll be > able to effectively respond to any feedback the upstream maintainer > might have. In the case of translations I generally can't do this, and > it's very much better for the translator to be in direct contact with > upstream. I perfectly understand. Thanks for providing the contact information, I'm sure Chris will respond. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#575482: Propose to NMU icoutils
On Wed, Jan 09, 2019 at 11:20:03AM +0100, Helge Kreutzmann wrote: > On Tue, Jan 08, 2019 at 09:53:31PM +, Colin Watson wrote: > > I'm sorry for not noticing this earlier, but I really can't say that I ^^^ > > would have accepted this. Translations need to go upstream or they > > Sorry, the bug was report 2010, i.e. almost 9 years ago. There was not > a single response in the BTS. Yes, I did apologise above for not responding. > If you have an upstream first policy, it would be sensible > (considering your users and the translators investing time and > proofreading people doing the same) to at least inform the submitter > (and the BTS) about it. Ideally you would forward it to upstream as > translators usually do not have the intrinsic knowledge of how > upstream works as you have as maintainer. Surely it's always the case that translations should go as far upstream as possible? I find it surprising that this isn't something translators would be aware of as a general practice. > > cannot be maintained effectively. Is there some reason why this > > translation hasn't been sent upstream for integration into a new > > upstream release instead of pushing it into Debian? > > I don't know, I'm not the translator so you would have to ask Chris > about it. He is very active and involved in quite a few projects, in > other projects he accepted working on upstream. So it would be best to > contact him with as much information as possible how to best get it > upstreamed. CCing Chris; could you please send this translation upstream (noting that Helge made some updates, so grab the current version from the archive) so that it can be incorporated and maintained there? The upstream homepage is at https://www.nongnu.org/icoutils/ and includes contact information; IME Frank is generally pretty responsive. > Alternatively (or if you are kind) you could already forward it > upstream. While I can and do often deal with forwarding patches of various kinds upstream, I'm afraid I'm only willing to do this when I think I'll be able to effectively respond to any feedback the upstream maintainer might have. In the case of translations I generally can't do this, and it's very much better for the translator to be in direct contact with upstream. -- Colin Watson [cjwat...@debian.org]
Bug#575482: Propose to NMU icoutils
Hello Colin, On Tue, Jan 08, 2019 at 09:53:31PM +, Colin Watson wrote: > On Thu, Dec 13, 2018 at 10:23:48PM +0100, Helge Kreutzmann wrote: > > I propose to NMU icoutils to solve the long standing translation bug > > 575482. > > > > You can find my proposed updates at > > http://www.helgefjell.de/data/icoutils_0.32.3-2.1.debian.tar.xz > > http://www.helgefjell.de/data/icoutils_0.32.3-2.1.dsc > > > > I would prefer if you could add this to your next MU, but if I don't > > hear from you I would upload this NMU early January. > > > > If you have any questions do not hesitate to ask. > > I'm sorry for not noticing this earlier, but I really can't say that I > would have accepted this. Translations need to go upstream or they Sorry, the bug was report 2010, i.e. almost 9 years ago. There was not a single response in the BTS. If you have an upstream first policy, it would be sensible (considering your users and the translators investing time and proofreading people doing the same) to at least inform the submitter (and the BTS) about it. Ideally you would forward it to upstream as translators usually do not have the intrinsic knowledge of how upstream works as you have as maintainer. If such an information would have been stored in the BTS I would not have invested the time dealing with it. Furthermore I pinged you (i.e. the bug) on November 25th and December 13th, both with no response and icoutils had a "LowNMU" mark. So to reach the freeze I proceeded. So if you have any objections (which is fine) it would save all parties quite some time if you raised them as early as possible. > cannot be maintained effectively. Is there some reason why this > translation hasn't been sent upstream for integration into a new > upstream release instead of pushing it into Debian? I don't know, I'm not the translator so you would have to ask Chris about it. He is very active and involved in quite a few projects, in other projects he accepted working on upstream. So it would be best to contact him with as much information as possible how to best get it upstreamed. Alternatively (or if you are kind) you could already forward it upstream. The po framework takes care that it is used as long as it is reasonably current (usually 80%) and mixes in the updated english strings. So there is no risk for users seeing outdated strings (only some english ones) and integrations of translations, even if poorly maintained, is of little risk. (Especially since only a subset of users will choose them). Btw. I updated the patch compared to the version you cited (but naturally did not change the file name) so either grab the version from the archive or redownload. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#575482: Propose to NMU icoutils
On Thu, Dec 13, 2018 at 10:23:48PM +0100, Helge Kreutzmann wrote: > I propose to NMU icoutils to solve the long standing translation bug > 575482. > > You can find my proposed updates at > http://www.helgefjell.de/data/icoutils_0.32.3-2.1.debian.tar.xz > http://www.helgefjell.de/data/icoutils_0.32.3-2.1.dsc > > I would prefer if you could add this to your next MU, but if I don't > hear from you I would upload this NMU early January. > > If you have any questions do not hesitate to ask. Hi, I'm sorry for not noticing this earlier, but I really can't say that I would have accepted this. Translations need to go upstream or they cannot be maintained effectively. Is there some reason why this translation hasn't been sent upstream for integration into a new upstream release instead of pushing it into Debian? -- Colin Watson [cjwat...@debian.org]
Bug#575482: Propose to NMU icoutils
Hello Collin, I propose to NMU icoutils to solve the long standing translation bug 575482. You can find my proposed updates at http://www.helgefjell.de/data/icoutils_0.32.3-2.1.debian.tar.xz http://www.helgefjell.de/data/icoutils_0.32.3-2.1.dsc I would prefer if you could add this to your next MU, but if I don't hear from you I would upload this NMU early January. If you have any questions do not hesitate to ask. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
