Pootle FS .lang test

These are the tasks that we want anticipate admins doing on the .lang backend. Which need to be tested by Translate and Mozilla.

1. Change on Pootle

   1. Single user adds a translation - commit is attributed to author and pushed by Pootle bot
   2. Two users add translations within 5 minute Window - commit should be Pootle bot with two authors in commit message.

2. Change on github

   1. Single change - Pootle should pull this in and credit correctly
   2. Two user change, even if different commits - different files and each user should be attributed correctly. Same file and last user is attributed.

3. Remove file from github - removed from Pootle

4. Add file to github - added to Pootle

5. Header changes

   1. Make a file ## active ## on github - should sync to Pootle correctly. Then translate on Pootle - should sync back to FS. Check that header still have ## active ##.
   2. Do the above in reverse to deactivate. Remove ## active ##, sync up to Pootle, translate, sync down to FS. Check that file is still inactive.
   3. Test other tags, ## tag ##, also ## NOTE might be updated (start from a demo server, then move to the official dev server) - check that roundtrip does not lost any of these.

6. More detailed unit changes

   1. Make a suggestion - nothing should sync
   2. Accept a suggestion - unit should sync

7. Change order of units - Pootle gets new order

8. Add new unit - Pootle gets new unit

Snags

Add anything here that's a bug/wishlist item: