[wp-meta] [Making WordPress.org] #4252: De-prioritize plugin changelog translation

[Making WordPress.org]

#4252: De-prioritize plugin changelog translation
--------------------------------------+---------------------
 Reporter:  Nao                       |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by garrett-eclipse):

 Replying to [comment:9 dd32]:
 > Changelog data may not be as important to those who can translate (and
 therefore read multiple languages) but it certainly would be valuable to
 those who can't (Or are not as fluent at) read English.
 >
 > To me, a proposal to split changelogs into a separate project is almost
 a request to cease translations of them entirely.
 > I'm aware that's not the intention here, but it certainly feels like it
 is.
 >
 > I do agree that keeping ten years of changelogs is useless though, and
 translating those old logs is a waste of everyone's time.
 >
 > From a technical perspective, anything is possible, but segregating it
 into a new protect would add a fair bit of hidden extra logic and code,
 it's not as simple as it may first appear.
 >
 > I think I'd rather invest in better tooling, perhaps where the priority
 tagging is more effective than it currently is, perhaps stats of
 percentage of high priority strings are translated rather than focusing on
 full projects, etc.
 > #1078 is something that could help greatly with translating the readmes,
 but probably also increase the approval workload.

 Thanks @dd32, I tend to agree with you there. Segregation very well may
 end in abandonment which would be negative as many users find the most
 recent changelog entries to be very useful in determining if they should
 upgrade and how thorough their testing prior to upgrade needs to be.

 An additional thought might be along your priority tagging route is to
 introduce a lower priority than low which applies to changelog entries 1+
 years old which would keep the more recent changes slightly higher
 priority as they're more useful to translate while those ancient version
 strings aren't as useful to users anymore.

 Appreciate you addressing those changelog priorities already.

 Cheers

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4252#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org