Put in a feedback message for .po(t) commits [#966544]

I'm in the process of writing up a post on how localize.drupal.org changes translation processes, and when that is done, I'd like to get the message out in feedback on commits for module maintainers and translators. Something like:

(for .pot commits): 'Committing .pot files for a project is not needed anymore. http://localize.drupal.org/ analyzes code in each tagged release, and makes text available for translation (and export) automatically. Read more at ...'

(for .po commits): 'The primary source for translations is now http://localize.drupal.org/. Submitting your translations there lets users to download and manage updates of translations much easier while maintaining history and attribution with an easy to use interface. Read more at ...'

BTW the git migration plans include forbidding .po and .pot file commits to version control to avoid the confusion and doubled existence of translations. Not sure how to put that into the above wording, thinking it might be enough to elaborate on the linked page.

Where should I look to provide such a patch? (Further text review is probably required, I just whipped this text up quickly).

Comments

Comment #1

gerhard killesreiter commented 9 November 2010 at 12:03

This would probably need to be added to xcvs-commitinfo.php.

Comment #2

dww

we/he/they

commented 11 November 2010 at 17:30

I'm psyched that we can finally remove translations from CVS. That's fantastic news.

However, I'm not sure adding these warnings is really going to be worth the effort:

A) Lots of people use CVS GUIs, and many GUIs apparently do not display the warning messages and notices that the existing xcvs scripts generate.

B) I doubt people actually read the warnings and notices, even if they're using the CLI or a GUI that displays them. :/

C) I'd prefer not spend any more development time on the xcvs scripts since I'd rather put that energy into the Git migration. The scripts are pretty fragile (the code is ancient). Any changes run a real risk of introducing bugs and failures, and I really don't have the bandwidth for that. I'd rather just not touch those scripts until the Git migration is done and we can remove them. ;)

Will you be a sad panda if I mark this "won't fix" and encourage you to find other ways to attempt to get this news out to project maintainers?

Thanks,
-Derek

Comment #3

gerhard killesreiter commented 11 November 2010 at 17:45

I've given Gabor access to a copy of the xcvs files, if he comes up with something, we should still be able to deploy this.

Comment #4

dww

we/he/they

commented 11 November 2010 at 22:01

The files live in CVS in contributions/modules/cvslog/xcvs, so there's no special "give Gabor access" required. But, I can't help with this. And if y'all break something, don't ask me to fix it. ;)

Good luck,
-Derek