[META] Problems found during click testing localize-7 in Amsterdam

The title for the OG board does not include the language. It is not possible to tell which language you are on by the title. On the live site this was [language] Team. The title regardless of the language you are on on the D7 testing site is Board | [site name]

Here are 2 tabs on the D7 testing site, one the German OG board, the other the Spanish OG board.

For comparison the live site with the same 2 tabs.

Suggested for the new title is to use the 2 letter identifier in the title followed by the location. This will save space in the title of tabbed browsers and allow people to still see where they are.

It was suggested, to changing site name to <strong>Drupal Translations</strong>.

The old title was, [Language name] Team | Translations
example: Team German | Translations

New suggestion is [2 letter language code] - [Location on site] | Drupal Translations

Examples:

For German board:
de - Board | Drupal Translations

For Spanish Export:
es - Export | Drupal Translations

For French Translations:
fr - Translations | Drupal Translations

There are 3 content types for discussion:

• Story
• Wiki Page
• Poll

The only difference between Story and Wiki Page:
The Wiki Page does not reference the author ("created by") .
Other user can not edit wiki pages.

Suggestions:

• Allow all group members to edit wiki pages (enforce revision?)
• Add filter for content type to Board
• Structure Wiki content (book module?)

@SebCorbin: should we promote this effort on localize.drupal.org/news as well as Drupal Planet?

@SebCorbin

Hi Sebastien!

It was good to work with you at the sprint at Drupalcon Amsterdam on localize.drupal.org. I was wondering if you need any more help with click testing or otherwise? Just let me know.

Greetings,

Frederick

Is l.d.o on D7 or D6?

D6 ;(

I need a D7 version of l10n_server, but what is the status about dev version?

Tagging, per drumm in #1424984-42: Port localize.drupal.org to Drupal 7.

Trying to get a handle on release blockers prior to 8.0.0 and what (if anything) the community can do to help things along in preparation of https://events.drupal.org/losangeles2015/sessions/plain-drupal-english-g...

There are a lot of issues identified in the issue summary. How many of those must be resolved prior to doing the upgrade, versus can be fixed after?

Also, is this a place where community members can jump in at LA? If so, could the issue summary be updated with instructions (e.g. where the dev server is, how to get access)?

#2349663: Automatically select a group and hide the field when adding new content and #2349613: Make field og_group_ref required have been updated.

I've confirmed that the patch in #2349693: Missing message after automatically joining a group works, and have added it to the make file for l.d.o.

#2349849: Wiki page is almost = to story page and is not editable by others has now been updated too.

@webchick: the update of l.d.o to Drupal 7 is required for the Drupal 8 release only as much as want to save our face that we are not running one of our sites on a soon to be unsupported 7 year old Drupal release. It has been surprisingly manageable to get new features built on Drupal 6 at least to parse the Drupal 8 APIs for translatable things, but any further site improvements (especially performance) should not happen on a Drupal 6 codebase. The Drupal 8 release especially with its built-in multilingual capabilities should help increase the use of localize.drupal.org a great deal I hope so improvements will be more important than ever.

As for whether people can help at LA, that depends on whether the staging site is properly built at the time. I will not be there to ensure neither have the time before to make sure it happens (on paternity leave until the middle of LA). I am not aware if @sebcorbin is attending either. The actual staging site information is at #1424984: Port localize.drupal.org to Drupal 7. I assume this should be closed when all the Amsterdam issues are resolved (which seems done or close?!) and a new one opened for issues found at LA if testing happens there.

Ok cool, so basically click-through testing of https://localize-7.staging.devdrupal.org/ and/or localize.drupal.org if it's updated by then. That's a great way to help! thanks. :)

Also, is this a place where community members can jump in at LA? If so, could the issue summary be updated with instructions (e.g. where the dev server is, how to get access)?

@webchick: I'll be in LA, so I can help on-site with any questions or queries.

We believe we’ve resolved all of the child issues found in click testing. D7 localize is now ready for another round of click-testing on staging https://localize-7.staging.devdrupal.org - and then hopefully deployment.

Please take another look and let us know if you find any other issues!

Particular attention should be paid to:

• #1666262: Verify permissions after D7 upgrade <- ensuring all activities from the D6 site still work on D7
• #2349587: Revoke ability to customize per group roles/permissions entirely <- making sure that the decision to make group permissions global is okay

We’d like to deploy shortly after DrupalCon LAX if all is well.

Responded on #2349587: Revoke ability to customize per group roles/permissions entirely. Not sure a testing sprint in LA would happen if there is no local lead. Even if I try to post a call for testing on l.d.o/news (syndicated to planet). Would be great to figure out if we can get someone to lead such a sprint. Do you have candidates or should I try and find someone? I raised this on the multilingual team meeting last Wed and nobody volunteered. Not sure who I can convince but I can try if you have no candidates.

Attempting open recruiting at https://twitter.com/gaborhojtsy/status/597695486330560512

@SebCorbin, @opdavies: opened #2487972: [META] Results of testing localize.drupal.org on Drupal 7 in summer 2015 and added testing instructions as well as @SebCorbin's excellent list of what to report when finding issues. Please verify I explained things right. Do we need someone to stand by to hand out one time login links to people or can they log in to staging with their regular name/pass or request a link in email?

The outstanding issues are now tracked in #2487972: [META] Results of testing localize.drupal.org on Drupal 7 in summer 2015.