- OpenStack-I18n - lists.openstack.org

IRC Meeting
by Ying Chun Guo 17 Jun '15

17 Jun '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on June 18th. I'm going to cover following topics: * Review translation terminologies * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

French User Guide publication
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi fdot, I noticed draft "fr/user-guide" link is broken[1]. Do you know what is the present situation? [1] http://docs.openstack.org/draft/draft-index.html Reagards, KATO Tomoyuki

3 4

Turkish translation
by Hüseyin Çotuk 16 Jun '15

16 Jun '15

Dear All, My name is Huseyin Cotuk, and i have been using OpenStack for more than 3 years in production. I am working for the Turkish government and we operate an OpenStack cloud for governmental institutions, universities, other research institutes and internal projects. Currently we have more than 4000 cpu cores, 500 TBytes of storage and so on. I am head of cloud department at TUBITAK ULAKBIM in Turkey, and while OpenStack Days Istanbul yesterday, we met with Jonathan and Lauren. We talked about our projects and i promised for the Turkish translation of OpenStack dashboard for the Turkish community. My organization TUBITAK ULAKBIM is also coordinating national operating system (Pardus), and we already have a translation team for this OS. We will work together with this translation team, and my team will review the translations after OS team finishes. My transifex id is huseyincotuk and the project name is openstack_turkish. I am looking forward to hearing from you. Best regards, Huseyin

3 3

Thought on String Freeze
by Akihiro Motoki 16 Jun '15

16 Jun '15

Hi I18N folks, # Congratulation for the official I18N project!! I first thought to send this mail to the dev list, but it seems better to share my thought in the I18N folks first. Problems ========== I am feeling that String Freeze does not work well in the past several releases.There are several I think we should not apply String Freeze for projects for which not so many translators work on. As far as I understand, Horizon and documentations are targets for most translations in the past several releases. On the other hands, core reviewers of projects other than Horizon and docs (including keystone) were taking care of String Freeze exception WELL. My Proposal ============= Considering the current status, I think we should limit "String Freeze" only to projects which translators are interested in. My idea is to declare projects we would like to enable "String Freeze" just after Liberty-3 is cut. By doing so, other projects no longer need to take care of String Freeze exception. (Note that the freeze date of the documentation projects are different and we can apply some different policy on documentations). Thought? I cannot join the team meeting tomorrow due to LinuxCon/CloudOpen Japan, but I hope you will share your thought on this topic. Thanks, Akihiro

2 2

Fwd: [openstack-dev] [horizon][i18n] Ordering of PO files
by Tom Fifield 09 Jun '15

09 Jun '15

-------- Forwarded Message -------- Subject: [openstack-dev] [horizon][i18n] Ordering of PO files Date: Mon, 8 Jun 2015 17:28:39 -0600 From: Thai Q Tran <tqtran(a)us.ibm.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Hi folks, In the midst of shifting to angular, we are making use of babel for extracting messages. This would then allow us to write a custom extractor for angular templates. Here's the patch that compare PO files: https://review.openstack.org/#/c/189502/ It looks worse than reality, if you compare the django vs babel makemessages, they are nearly identical, only the ordering is different. Which leads me to my next point. If the ordering of the translatable strings are not the same, how does that affect translation (if at all)?

1 0

I18n team working sessions in Vancouver
by Ying Chun Guo 05 Jun '15

05 Jun '15

Hello, all We had a great day yesterday. There were two I18n team working sessions. People from Japanese, Frech, Russian, Polish, Chinese and Chinese Taiwan team attended. Key persons from Doc team, infra team, and Horizon dev team joined the discussions too. We made good progress with glossaries, document translations, string freeze, tool migration, and etc. More details could be found in the etherpad pages [1] [2]. Yet our translators still want more face to face communications. So I organize an ad hoc meeting on Wednesday afternoon, only for translators. If you are translators and in Vancouver summit now, come to join the ad hoc meeting. The place is at a round table outside the Room 1, East Building at the Vancouver Convention Centre. The time is from 2:05pm to 5:05pm on Wednesday, May 21st. I will sit there and wait for you to join. I created an Etherpad page for us to track the discussion. Feel free to add the topics you want to cover. https://etherpad.openstack.org/p/vancouver-translation-team-workshop Thank you. Best regards Ying Chun Guo (Daisy) [1] https://etherpad.openstack.org/p/Vancouver-I18n-WG-session [2] https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session

3 5

I18n team, OpenStack Project Team!
by Ying Chun Guo 04 Jun '15

04 Jun '15

Hello, all I'm pleased to announce that I18n team is approved by TC to become a OpenStack Project Team. We are now under the authority of the OpenStack Technical Committee. In return, we could get some space and time to discuss our future development at the Design Summits. Our contributors could vote in the Technical Committee election. This is a great milestone after I18n team was created. Next, we need to figure out the criteria of our core members and active members, which might be different from dev team. We will initialize the core team, then grow the team and increase the contributions. Let's work together to make it a successful team. Best regards Ying Chun Guo (Daisy)

11 12

IRC meeting tomorrow
by Ying Chun Guo 03 Jun '15

03 Jun '15

Hello, team There are several responses to the mail "Review IRC meeting time"[1]. I don't see objections. So let's use them from now on. I hope active team members could have chances to join the discussion at least once a month. If these two time slots are not suitable for you, please let me know. We could still adjust the meeting times in the future. Tomorrow, we will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on June 4th. Following topics would be covered: * Briefing of I18n meetings in Vancouver summit * Criteria of I18n core members and active members * Open discussions Hope to talk to you then. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-June/001107.html

1 0

Review IRC meeting time
by Ying Chun Guo 02 Jun '15

02 Jun '15

Hello, team I would like to review our IRC meeting time. Now we are using UTC 0800 and we meet on every first and third Thursday. I18n team have people from all over the world. Some people would like to use their day time, and some people prefer to use their evening time. I want to change to two time slots for the meetings. We use them alternately. Hope every team member could find a suitable time to join the team meeting. I suggest below two time slots: 1. The first Thursday every month UTC 6am, Thur Paris 08am, Thur Warsaw 08am, Thur Moscow 09am, Thur New Delhi 11:30am, Thur Beijing 14pm, Thur Seoul 15pm, Thur Tokyo 15pm, Thur Vancouver 23pm, Wed 2. The third Thursday every month UTC 13pm, Thur Paris 15pm, Thur Warsaw 15pm, Thur Moscow 16am, Thur New Delhi 18:30am, Thur Beijing 21pm, Thur Seoul 22pm, Thur Tokyo 22pm, Thur Vancouver 06am, Thur Please let me know which time slot works for you. Or if neither works for you, please suggest a time. Thank you. Best regards Ying Chun Guo (Daisy)

4 3

Re: [Openstack-i18n] Specialty teams connecting to translation team
by Ying Chun Guo 21 May '15

21 May '15

Sorry, wrong wiki link in my last email. It is https://wiki.openstack.org/wiki/I18nTeam/docs-translation Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2015/05/22 01:42:18: > From: Ying Chun Guo/China/IBM > To: Anne Gentle <annegentle(a)justwriteclick.com> > Cc: "openstack-docs(a)lists.openstack.org" <openstack- > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Date: 2015/05/22 01:42 > Subject: Re: [Openstack-i18n] Specialty teams connecting to translation team > > Thank you, Anne. > > We use a wiki page to track the status of documentation: > https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… > > I hope specialty team leads could keep an eye on this table. > If there is any changes of your documents, like, changing from > stable to unstable, changing from unstable to stable, > let the translation team know by sending an email to openstack-i18n > mailing list. > So that we could make a translation plan for your documents. > > Thanks. > Best regards > Ying Chun Guo (Daisy) > > Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2015/05/22 01:35:14: > > > From: Anne Gentle <annegentle(a)justwriteclick.com> > > To: "openstack-docs(a)lists.openstack.org" <openstack- > > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 2015/05/22 01:35 > > Subject: [Openstack-i18n] Specialty teams connecting to translation team > > > > Hi all, > > I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who > > leads the i18N efforts for OpenStack. She would like each specialty > > team lead to connect with the i18N team to communicate the amount of > > change expected so that they can evaluate the timing of translation, > > and how much is done that can be translated. > > > > We also had a session with the i18N team and want to work on more > > communication with each team, and I think the specialty team leads > > are a great way to start that effort. > > > > Thoughts or ideas? Let us know. > > Thanks, > > Anne > > > > -- > > Anne Gentle > > annegentle@justwriteclick.com_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Magnum, magnumclient translations?
by Andreas Jaeger 14 May '15

14 May '15

The magnum project wants to enable translation, see https://review.openstack.org/#/c/182835/ and https://review.openstack.org/#/c/182848/ Is there any guideline from the translation team which projects get translation enabled? I know that enabling translation does not mean, something gets translated - Davanum, keep that in mind ;) Btw. magnum is an OpenStack project that provides a set of services for management of application containers in a multi-tenant cloud environment. And so far we've enabled all projects in the OpenStack project. Only the last months this was not done with each new project moving under the big tent. I'll review the requests today or tomorrow and will setup transifex for the team unless I hear otherwise from the translation team, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Update on Dogri, Konkani, Manipuri, Sanskrit, Santali
by Tom Fifield 14 May '15

14 May '15

Hi all, I just wanted to let you know that Transifex has added Dogri, Konkani, Manipuri, Sanskrit and Santali to their site's code repository, and will update the code of the live site (so we can use them) before the end of this month. Regards, Tom

2 4

Horizon translation check site
by KATO Tomoyuki 14 May '15

14 May '15

Hi team, Motoki-san, We did not have Horizon translation check site for Kilo release cycle from my understanding. We previously discussed this topic in this ML. Do we have a conclusion? Need more discussion? Thanks, KATO Tomoyuki

3 2

Separating User Guides
by Andreas Jaeger 13 May '15

13 May '15

FYI, we're separating the User Guides again into two directories. Once this is done, we will have again user-guide and user-guide-admin resources. I will copy over all content from the current user-guides to these and then remove the user-guides. Patch series: https://review.openstack.org/#/q/status:open+project:openstack/openstack-ma… Docs discussion: http://lists.openstack.org/pipermail/openstack-docs/2015-May/006581.html Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 1

I18n team working sessions in Vancouver summit
by Ying Chun Guo 11 May '15

11 May '15

Hello, We have 2 working sessions in Vancouver summit. They are: * Translation team working session [1] * Building translation platform [2] The first session is for discussions related with our translations. The second session is for discussions related with moving to Zanata. I18n team members who would go to Vancouver summit are strongly recommended to attend these sessions. You can edit Etherpad pages to add the topics you want to discuss. The links to Etherpad pages are: https://etherpad.openstack.org/p/Vancouver-I18n-WG-session https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session Hope to see you in Vancouver. Thank you. Best regards Ying Chun Guo (Daisy) [1] https://openstacksummitmay2015vancouver.sched.org/event/f008932bfc685abe742… [2] https://openstacksummitmay2015vancouver.sched.org/event/83ceed4873820c889e7…

1 0

website translation
by KATO Tomoyuki 10 May '15

10 May '15

Hi team, I want to translate website "www.openstack.org" as whole as possible. However, I don't understand how website are maintained. So, I will investigate. Are you interested in website translation? Does anyone help me? My Requirement(priority): 1. automatically periodic (eg:every 1H) update translation 2. use Transifex(/Zanata) for translation tool -> need to generate pot files It is easy to translate for translator. Thanks, KATO Tomoyuki

2 2

IRC meeting tomorrow
by Ying Chun Guo 06 May '15

06 May '15

Hello team I would use tomorrow's IRC meeting to prepare for the Vancouver summit meetings. People who would go to Vancouver are strongly desired to show up. Following topics would be covered: * Agenda of I18n team meetings in Vancouver summit * Open discussions Hope to see you in IRC channel of #openstack-meeting at 0800 UTC. Best regards Ying Chun Guo (Daisy)

1 0

Persian translate
by کاربرخوب لینوکس 29 Apr '15

29 Apr '15

Salam Hello I am Contributing some project to translate to farsi such as debian , ... I like to start and Contribute open stack translation for persian users. Thanks

2 1

Decreasing size of PO files
by Andreas Jaeger 23 Apr '15

23 Apr '15

Our PO files contain information about location (filename and line numbers) as well as untranslated strings. Dolph suggested to me recently to import into projects only the *translated* strings and I did some investigation and implementation. I don't expect this to have any negative impact but wanted to inform you and ask for feedback. We will continue to push the full location information to transifex and leave it in the POT files that are stored in each repository. Thus if you download a file from transifex, you have all location information. During the import from transifex into the OpenStack git repositories, our scripts remove the location information as well as any untranslated strings thus reducing the files to import significantly. This also reduces the change of an import significantly since a line number change will not cause many location information to be updated. The gettext tools we use can cope fine with this smaller PO file since it contains everything that is needed - just nothing more ;) Also, it's easy to rebuild the full PO file from the date in the repository using the msgmerge command: msgmerge POT-FILE PO-FILE -o FULL-PO-FILE As a first step, I have made this change for documentation projects like openstack-manuals only: https://review.openstack.org/176313 If this works as expected, I plan to do it for other projects as well. Please review and tell me if you have any further ideas or if I overlooked something, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

Final call for Horizon translations for Kilo
by Akihiro Motoki 23 Apr '15

23 Apr '15

Hi all! Horizon RC1 was just shipped yesterday. This means we are now in the deep string freeze and no string changes are expected. I hope you all keep your translations up-to-date in time. I would like to share some important topics with you. TRANSIFEX RESOURCE: Liberty development cycle is now open. You will see resource names with Liberty. For Kilo translation, please translate the resources whose names have "Kilo". IMPORTANT DATE: The final translation import is planed on Apr 23. I talked with David, Horizon PTL and the above date works for Horizon team. I don't set the exact time of the deadline, but I will do the final import in the day of Apr 23 (UTC timezone). Please don't bother me on the deadline:-) IMPORT CRITERIA: I would like to set the criteria to import to 90% completion rate (as we discussed before), OR language coordinator request. Horizon now covers various new services and in some case translation rate does not work, so I would like to honor language coordinator decision. Daisy and the team, does it make sense? If not, please start a new thread to discuss this topic. Thanks, Akihiro

3 8

Draft Documents published, next steps with draft publishing and RST translation
by Andreas Jaeger 19 Apr '15

19 Apr '15

As part of the draft publishing spec [1], we now publish all draft documents to docs.openstack.org/drafts. To read or review, go to http://docs.openstack.org/draft/draft-index.html Translation team, as part of this, the draft-i18n-manuals.html page has been removed, the content is in draft-index.html now. Next steps are moving draft language guides also to /draft/ For this, let's merge [2], release openstack-doc-tools 0.25 and then I'll adjust and remove the script changes from [3] and [4]. The script changes in [3] and [4] are part of the openstack-doc-tools patch [2] and give you the chance to review the patches and scripts independently. Andreas [1] http://specs.openstack.org/openstack/docs-specs/specs/kilo/draft-publishing… [2] https://review.openstack.org/175190 [3] https://review.openstack.org/#/c/162424/ [4] https://review.openstack.org/#/c/175157/ -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Status of the RST Documentation Toolchain
by Tom Fifield 16 Apr '15

16 Apr '15

Hi, Andreas, Daisy, Motoki-san and myself have just had an impromptu hour-long discussion regarding the Status of the RST Documentation Toolchain, particularly its translation components. This meeting was spurred on by the email to the i18n mailing list announcing the pending removal of docbook user guides, and all present acknowledged the meeting would have been great if it had happened sooner :) This is the brief summary! 1. Everyone involved wants to make translators happy, and hopes that the process of moving to RST can deliver an improved toolchain 2. There has been inadequate communication between the documentation team and the i18n team regarding requirements and timelines during this process and we will strive to improve this 3. Previous statement that RST-based docs would not be published without agreement on the translation toolchain was acknowledged 4. Based on the user guide example, about 50% of existing translated strings (1943 vs 943) need to be re-translated with the current conversion process 5. Noone on the i18n team had yet the opportunity to assess the strings produced by the RST in a fuller guide and problems weren't picked up with initial version of guides in the playground folder 6. Daisy in particular hasn't been able to log in to transifex today to check the new user guide. We are currently using the standard Sphinx translation tools, though, there was some definite concern over the quality of the strings produced by the RST, including: 1. Strings that should have been trivially updated during conversion from docbook without human interaction needed (eg **string**\n) 2. Strings that are entirely markup (eg :ref:`Boot_instance_from_image_and_attach_non-bootable_volume`) 3. Strings that contain significant amounts of markup 4. Strings that contain markup characters that are unusual for translations, eg backticks, asterisks 5. Strings that contain markup where placeholders were previously used 6. ... this list is incomplete and comes only from what amotoki and fifieldt saw during the meeting - the broader i18n community has not yet been asked for feedback outside of Andreas' recent email 7. There is an open issue about how to fix problems like the above. 1. Andreas stated that not maintaining our own custom scripts is a good aim, and some of the issues above could be handled with a one time fix at conversion time 2. Daisy & Tom stated that they preferred such issues to be fixed in the toolchain 3. Just looking at the "** STRING **" issue, it's 70 strings but a quick proof of concept didn't result in fixing the issue - we haven't worked out why yet. 4. The current toolchain is difficult to modify, since it relies on an upstream component that is used by multiple projects, meaning post processing and pre-processing are the only real approach we have 5. It could be complicated to use post-processing and pre-processing to implement fixes for issues beyond the trivially updated string example in the current toolchain 8. There is an open question about whether it is possible to deliver an improved i18n experience with the current toolchain 9. There is not yet agreement that the current documentation toolchain is meeting the needs of the i18n team Based on the meeting, and especially the fact that due to inadequate communication the i18n team (inc Daisy) has not yet had the opportunity to assess the RST documentation toolchain fully, I would propose that the removal of existing guides and publication of RST guides be delayed until that's happened. We suggest that Daisy does an initial assessment and arrange a meeting to discuss next steps as soon as possible.There are many things we can fix with the the toolchain any time after publication, however it is important that we assess what needs to be done and ensure that we can actually feasibly deliver an improved experience for our translations, as well as our doc team. Regards, Tom

6 11

北京约克仪器公司上海
by 谈辛海 15 Apr '15

15 Apr '15

wxawryvz 16:56:58 2015/4/15

1 0

IRC meeting tomorrow
by Ying Chun Guo 15 Apr '15

15 Apr '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. Following topics will be covered: * rst document translation discussion with doc team * Final push on Horizon translation There is a wiki page [1] highlighting typical rst markups used by openstack manuals. Please go through it before the meeting. Thank you. Best regards Ying Chun Guo (Daisy) [1]https://wiki.openstack.org/wiki/I18nTeam/rst-markups

1 0

What's Up Doc? Apr 10 2015
by Anne Gentle 12 Apr '15

12 Apr '15

Hi all, As you probably saw from PTL nominations last week, I'm happy to hand the docs PTL baton to Lana Brindley! I loved leading this group and thank you all for supporting me. Thank you Lana for your willingness to lead. I'm still here to bring us to the Kilo release, so this week's What's Up Doc brings sharp focus requests to everyone to work on docs. These are the top priorities that we all need to work on - devs, writers, testers, gaters, everyone. 1. Bug triaging and fixing, especially for openstack-manuals. There are nearly 300 DocImpact bugs logged that we need developers to circle back to. With nearly 600 bugs overall, we need lots of focus here. To that end, I propose we hold a bug triage day. I'll send details in a separate email. 2. Install Guide testing and reviewing. The Install Guide team has a published spec that will help reviewers see what's changing with the Kilo Install guide: http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kil… Join them for weekly meetings Tuesdays at at 13:00 UTC (8:00 AM US CDT) in Google Hangout: https://plus.google.com/hangouts/_/calendar/a2FyaW4ua2F0aG9kZUBnbWFpbC5jb20… If you do nothing else but these two focus areas we'll be in good shape. There are other activities going on leading up to Vancouver but those two are top priorities. _RST Migration_ We are working to resolve translation tool expectations with the i18N team. I want to publish the RST-based English End User Guide and Admin User Guide once we're all comfortable with the way forward. Daisy will discuss the implications at the next i18N team meeting Thursday at 0800 UTC, and we'll implement and communicate the plan. _Networking Guide_ Next on the list is Networking Guide testing and reviewing. The Networking Guide team has a talk in Vancouver and needs to get their guide in shape for publishing. The neutron team is holding a doc day April 23. Please join in -- they'll post details in their notes. _First App Tutorial_ There's also the First Application Tutorial that needs to finish the spec and needs an editing cleanup prior to publishing. Ideally that will happen before Vancouver, we need to get it to the finish line. _HA Guide_ With everything else going on we need an updated spec for the HA Guide - the wiki page isn't enough. Based on this week's doc team meeting it sounds like that can go to RST as well but we need it in the spec so we can plan and cross-coordinate with the other priorities leading up to Vancouver. _Vancouver Summit _ The docs team has four Fishbowl time slots, 2 Workroom slots, and 1 Meetup allocated now. If you'd like to discuss a cross-project idea, please use the form to suggest new ideas: http://goo.gl/forms/S69HM6XEeb. You can see the current suggestions already posted here: https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5l… Lana or I will send out an etherpad in the next week or so with topic suggestions for our allocation. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

3 3