https://wiki.openstack.org/w/api.php?action=feedcontributions&feedformat=atom&user=DaisyOpenStack - User contributions [en]2026-06-29T14:01:44ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Interop_Challenge&diff=150709Interop Challenge2017-02-06T02:57:48Z<p>Daisy: /* China Chapter Meeting Information */</p>
<hr />
<div>== Interop Challenge ==<br />
"Status: Making decisions on workloads second round Interop Challenge (as of Dec 7, 2016)''<br />
<br />
=== Scope ===<br />
{|<br />
|-<br />
| [[File:InteropKeynote.JPG|200px|thumb|left|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<small>Barcelona Summit Keynote</small>]] ||The interop challenge was started in July 2016 to create a set of common workloads/tests to be executed across multiple OpenStack distributions and/or cloud deployment models. The participants in this challenge will work together to prove once and for all that OpenStack-Powered clouds are interoperable. <br /><br /><br />
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off] <br /><br /><br />
OpenStack Barcelona Summit Interoperability Challenge: [https://www.openstack.org/videos/video/openstack-interoperability-challenge-running-unmodified-apps-in-any-openstack-cloud OpenStack Keynote Video] <br />
|} <br /><br />
Project repository: <br /><br />
https://github.com/openstack/interop-workloads<br /><br />
https://git.openstack.org/cgit/openstack/interop-workloads<br /><br />
<br />
Project launch pad: <br /><br />
https://launchpad.net/interop-workloads <br /><br />
<br />
Bug tracking: <br /><br />
https://bugs.launchpad.net/interop-workloads <br/><br />
<br />
=== Duration ===<br />
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation. The OpenStack Summit Barcelona has marked the complettion of this phase. Please see pictures and videos of the effort by clicking on the links in the Scope section.<br /><br />
The expanded team is now working on the second round of challenge to provide even more work loads to test more OpenStack functions. The workloads will be show cased in Summit Boston in the spring of 2017.<br />
<br />
=== Meeting Information ===<br />
Schedule: Wednesdays at 1400 UTC<br />
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-5</nowiki></code><br />
Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/<br />
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&iso=20170208T14&p1=%3A Wednesday, February 8th, 2017 at 1400 UTC]'''<br/><br />
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-08 2017-02-08]'''<br />
'''Agenda'''<br />
* see the etherpad <br />
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-01 2017-02-01]<br />
<br />
==== China Chapter Meeting Information ====<br />
Schedule: Wednesdays at 0130 UTC<br />
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-5</nowiki></code><br />
Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/<br />
'''Next Meeting: [https://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+China+Chapter+Meeting+&iso=20170208T0130&p1=1440&ah=1 Wednesday, February 8th, 2017 at 0130 UTC]'''<br/><br />
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-china-meeting-2017-02-08 2017-02-08]'''<br/><br />
'''Agenda'''<br />
* see the etherpad<br />
<br />
=== Communication methods ===<br />
* Members will meet regularly using the OpenStack InterOP Working Group channel (#openstack-meeting-5) on IRC<br />
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg Interop Working Group Mailing List] and add the [interop] tag to the subject of messages related to the interop challenge.<br />
* The team may also have discussions in Gerrit on specific tools/workloads<br />
<br />
=== Milestones ===<br />
{| class="wikitable"<br />
|-<br />
! Milestone !! Goal !! References !! Status<br />
|-<br />
| 1 || ''Create interop challenge and team'' || || ''Completed''<br />
|-<br />
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' || || ''Completed''<br />
|-<br />
| 3 || Execute tests, resolve/document any issues, and share results || || ''Completed''<br />
|-<br />
| 4 || Create read-out for Interop Challenge || || Completed<br />
|-<br />
| 5 || Share findings at the OpenStack Summit in Barcelona || || Completed<br />
|-<br />
| 6 || Defining new work loads for Boston summit || || Pending<br />
|-<br />
|}<br />
<br />
=== How to Join ===<br />
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag "[interop]" in the subject line. Please identify one business and technical leader from your organization in the introductory email. Welcome aboard!<br />
<br />
Current Participants Alphabetical Order<br />
<br />
{| class="wikitable"<br />
|-<br />
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner<br />
|-<br />
| AT&T || Kilo || LAMPstack tested with Ansible || Success || || Elise Eiden <br />
|-<br />
| Canonical || Mitaka and Newton || LAMP and Dockerswarm ||Sucess || || Mark Baker<br />
|-<br />
| Cisco || Liberty || || Success || Rohit Agarwalla || Rohit Agarwalla<br />
|-<br />
| Fujitsu || Icehouse and Kilo || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler <br />
|-<br />
| HPE || Mitaka || RefStack Pass. Tested with Ansible || Success || Ghe Rivero || Simon McCartney<br />
|-<br />
| Huawei || Juno || DockerSwarm tested with Terraform, LAMPStack tested with Ansible || Success || Jichun Liu(Huawei) || Zhenyu Zheng||<br />
|-<br />
| DT OTC (public cloud) || Juno || LAMPStack tested with Ansible || Success || ||Daniela Ebert ||<br />
|-<br />
| IBM || Liberty and Mitaka || || Success || Tong Li (IBM) || Tong Li (IBM)<br />
|-<br />
| Linaro || Newton on AArch64 || || Success || Gema Gomez (Linaro) || Gema Gomez ||<br />
|-<br />
| Mirantis || Mitaka || || Success || Craig Peters (Mirantis) ||Craig Peters cpeters@mirantis.com<br />
|-<br />
| Intel Corporation, OSIC || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares<br />
|-<br />
| OVH || Juno/Kilo || || Success || Tong Li (IBM) || Damien Rannou (OVH)<br />
|-<br />
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler<br />
|-<br />
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado<br />
|-<br />
| SUSE || Liberty and Mitaka || Tested with Ansible || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder<br />
|-<br />
| VMware || Mitaka || || Success || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||<br />
|-<br />
| DreamHost || Mitaka || LAMPstack Ansible || Success || || Stefano Maffuli<br />
|-<br />
|}<br />
<br />
=== Scripts/Tools used for Interop Challenge ===<br />
The interop challenge requires that we use common testing scripts and validation methods across multiple clouds. The team has agreed to post all scripts to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository since the templates/scripts used for the Interop Challenge are also useful outside of this context and could serve as examples on how to use various tools to deploy applications on OpenStack-Powered Clouds.<br />
<br />
The current list of proposed tooling includes:<br />
* Ansible<br />
* Terraform<br />
* OpenStack Heat<br />
<br />
The current list of workloads includes:<br />
* LAMP (Linux, Apache, MySQL, PHP) Stack<br />
* Dockerswarm-coreos<br />
* NFV<br />
<br />
==== How to Propose/Submit new tools/workloads ====<br />
Any participating member of the Interop Challenge can submit additional scripts/workloads for review by the team. The script to leverage the new tool and/or deploy the new workload should be posted to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository. Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].<br />
<br />
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: "[interop] New tool/workload proposal: <code>brief description</code>" and provide a link to the code review page for the change along with an overview of the tool or where people can find more information. The proposal will be reviewed by the team and, if necessary, added to the agenda for an upcoming meeting.<br />
<br />
==== Doodle Pool Results ====<br />
A doodle pool was conducted in the month of December 2016. The pool was openeded on 12/01/2016 and closed on 12/14/2016. The pool was to decide what kind of workload the community will work on in the next interop challenge. The decision has been made to develop Kubernetes and NFV workloads. Here is the pool results: <br /><br />
[[ File:Doodlepoolresults.png|400px ]]<br />
<br />
==== Directory Structure ====<br />
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib<br />
Directory structure is proposed below:<br />
/heat - use heat template to create workload<br />
lampstack<br />
dockerswarm-coreo<br />
...<br />
/terraform - use terraform to create workload<br />
lampstack<br />
dockerswarme-coreos<br />
...<br />
/xxx - use xxx to create workload<br />
<br />
=== Test Candidate Process ===<br />
(Proposed; subject to change after 08-10-2016 meeting)<br />
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)<br />
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)<br />
** We may need to talk about the content of each work load, use lamp stack as an example.<br />
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?<br />
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?<br />
* LAMP stack workload (created by Tong Li/IBM)<br />
** https://review.openstack.org/#/c/351879/ <br />
** Currently developed using terraform to deploy workload, looking into Ansible<br />
* HEAT template (submitted by Craig Sterrett & Leong/Intel) <br />
** https://review.openstack.org/#/c/351799/<br />
<br />
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )<br />
<br />
=== RefStack Testing and Results Upload ===<br />
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst<br />
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.<br />
<br />
<br />
Once tests are run, test results can be uploaded to the official [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.<br />
*RefStack team highly recommends to upload test results with signatures and not anonymously. By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.<br />
<br />
<br />
For Interop Challenge, DefCore team recommends to run complete API tests (not just the must-pass tests). Following is the command to run the tests:<br />
./refstack-client test -c <Path of the tempest configuration file to use> -v<br />
<br />
<br />
For questions, please contact us at IRC channels #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]<br />
<br />
=== Where/How to Share Test Results ===<br />
Rather than collecting binary "pass/fail" results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not. Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with "[interop-challenge] Workload Results" in the subject line.<br />
<br />
<br />
1.) Your name: <br />
2.) Your email: <br />
3.) Reporting on behalf of Company/Organization: <br />
4.) Name and version (if applicable) of the product you tested:<br />
5.) Version of OpenStack the product uses: <br />
6.) Link to RefStack results for this product: <br />
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)<br />
A.) Did the workload run successfully? <br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. <br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)<br />
A.) Did the workload run successfully? <br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. <br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
9.) Workload 3: NFV (URL TBD)<br />
A.) Did the workload run successfully? <br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.<br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
<br />
Here's a fictional example of what the email template might look like when filled out:<br />
<br />
1.) Your name: Jane Doe <br />
2.) Your email: jdoe@supercoolsoftware.com <br />
3.) Reporting on behalf of Company/Organization: XYZ, Inc.<br />
4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5<br />
5.) Version of OpenStack the product uses: Liberty<br />
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d <br />
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)<br />
A.) Did the workload run successfully? No<br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
<br />
"Error in fetching the floating IP's: no floating IP addresses available"<br />
<br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. <br />
<br />
SuperCoolCloud doesn't use floating IP addresses. Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.<br />
<br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
<br />
Not very. Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says "if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead").<br />
<br />
8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)<br />
A.) Did the workload run successfully? Yes<br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
<br />
N/A<br />
<br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. <br />
<br />
N/A<br />
<br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
<br />
N/A<br />
<br />
9.) Workload 3: NFV (URL TBD)<br />
A.) Did the workload run successfully? Yes<br />
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened. <br />
<br />
N/A<br />
<br />
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.<br />
<br />
N/A<br />
<br />
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?<br />
<br />
N/A</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=122425Meetings/I18nTeamMeeting2016-03-17T03:16:44Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meeting ===<br />
UTC 1300, March 17<br />
* Mitaka translation updates<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
=== 4th Feb ===<br />
* Discussion: statistic data and ATC<br />
* Follow up with translation check website<br />
* Open discussions<br />
==== 7th January ====<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 17th December ====<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: remove from Transifex ?<br />
* Open discussions<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=122249CrossProjectLiaisons2016-03-15T08:40:42Z<p>Daisy: /* I18n */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Sergey Kraynev || skraynev<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) || jroll (dtantsur)<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || lane_kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kyle Mestery || mestery<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Nikhil Komawar || nikhil_k<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Constanze Kratel || constanze <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || || <br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Mitsuhiro SHIGEMATSU || pshige<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Magnum || || <br />
|-<br />
| Manila || || <br />
|-<br />
| Mistral || || <br />
|-<br />
| Murano || Ekaterina Chernova || katyafervent <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Joe Gordon or Michael Still || Jog0 or mikal<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k<br />
<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Nikhil Manchanda || SlickNik<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Cinder || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki<br />
|-<br />
| Telemetry || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Heat || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| || Brent Eagles || beagles || Nova liaison for Neutron<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| Sahara / Heat || || ||<br />
|-<br />
| || Vitaly Gridnev || vgridnev || Sahara liaison for Heat<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Adam Gandelman || adam_g<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || Tyr Johanson || tyr<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Magnum || Adrian Otto || adria̠n_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Serg Melikyan || smelikyan<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Craig Vyvial || cp16net<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=121662I18nTeam/team/zh cn2016-03-04T06:27:22Z<p>Daisy: </p>
<hr />
<div>[[Category:I18n]]<br />
= 简体中文翻译团队 =<br />
== 联系方式 ==<br />
协调人: 郭迎春。联系方式：IRC ID "Daisy"或者[mailto:guoyingc@cn.ibm.com 发邮件]给她 <br />
<br />
IRC channel: #openstack-i18n<br />
<br />
微信组: 添加微信好友 "daisy-ycguo", 她会把您加到中文翻译团队的微信组中。<br />
<br />
== 如何加入 ==<br />
见 [http://docs.openstack.org/developer/i18n/official_translator.html Steps to become a OpenStack translator]<br />
<br />
== 翻译工作指南 ==<br />
=== 标点 ===<br />
* 基本上，除了圆括号和省略号保持不变外，都该改成汉语的全角标点。<br />
* 英语的 , 可能对应逗号或者顿号。<br />
* 英语的 . 可能对应句号、分号或者逗号（分句）。<br />
=== 空格 ===<br />
* 在汉字和英文字符、阿拉伯数字之间应加入空格<br />
<br />
== 可用参考 ==<br />
* [http://wiki.ubuntu.org.cn/TranslatorsGuideline#.E6.A0.BC.E5.BC.8F.E8.A6.81.E6.B1.82 Ubuntu 简体中文小组工作指南]<br />
* [https://repo.anthonos.org/misc/l10n/zh_CN_l10n.pdf AOSC 翻译指南]<br />
<br />
== 术语 ==<br />
=== 不翻译使用英文的术语 ===<br />
在翻译过程中，下列术语仍然使用英文形式，不需要翻译。因为我们没有找到合适的中文词汇来描述。<br />
* Overlay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=119551CrossProjectLiaisons2016-02-29T08:55:39Z<p>Daisy: /* I18n */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Sergey Kraynev || skraynev<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) || jroll (dtantsur)<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || lane_kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kyle Mestery || mestery<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Nikhil Komawar || nikhil_k<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Constanze Kratel || constanze <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Mike Perez || thingee <br />
|-<br />
| Congress || || <br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Mitsuhiro SHIGEMATSU || pshige<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Magnum || || <br />
|-<br />
| Manila || || <br />
|-<br />
| Mistral || || <br />
|-<br />
| Murano || Ekaterina Chernova || katyafervent <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Joe Gordon or Michael Still || Jog0 or mikal<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k<br />
<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Nikhil Manchanda || SlickNik<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Nova || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || || <br />
|-<br />
| Horizon || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Neutron || || <br />
|-<br />
| Swift || || <br />
|-<br />
| Ceilometer || || <br />
|-<br />
| Heat || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| || Brent Eagles || beagles || Nova liaison for Neutron<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| Sahara / Heat || || ||<br />
|-<br />
| || Vitaly Gridnev || vgridnev || Sahara liaison for Heat<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Adam Gandelman || adam_g<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || Tyr Johanson || tyr<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Magnum || Adrian Otto || adria̠n_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Serg Melikyan || smelikyan<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Craig Vyvial || cp16net<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}</div>Daisyhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=110395CrossProjectLiaisons2016-02-25T10:22:06Z<p>Daisy: /* I18n */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Sergey Kraynev || skraynev<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) || jroll (dtantsur)<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || lane_kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kyle Mestery || mestery<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Nikhil Komawar || nikhil_k<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Constanze Kratel || constanze <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Mike Perez || thingee <br />
|-<br />
| Congress || || <br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Mitsuhiro SHIGEMATSU || pshige<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Magnum || || <br />
|-<br />
| Manila || || <br />
|-<br />
| Mistral || || <br />
|-<br />
| Murano || Ekaterina Chernova || katyafervent <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Joe Gordon or Michael Still || Jog0 or mikal<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k<br />
<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Nikhil Manchanda || SlickNik<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
* The liaison should be a core reviewer for the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Nova || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || || <br />
|-<br />
| Horizon || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Neutron || || <br />
|-<br />
| Swift || || <br />
|-<br />
| Ceilometer || || <br />
|-<br />
| Heat || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| || Brent Eagles || beagles || Nova liaison for Neutron<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| Sahara / Heat || || ||<br />
|-<br />
| || Vitaly Gridnev || vgridnev || Sahara liaison for Heat<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Adam Gandelman || adam_g<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || Tyr Johanson || tyr<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Magnum || Adrian Otto || adria̠n_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Serg Melikyan || smelikyan<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Craig Vyvial || cp16net<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}</div>Daisyhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=110359CrossProjectLiaisons2016-02-25T09:18:29Z<p>Daisy: </p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Sergey Kraynev || skraynev<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) || jroll (dtantsur)<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || lane_kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kyle Mestery || mestery<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Nikhil Komawar || nikhil_k<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Constanze Kratel || constanze <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Mike Perez || thingee <br />
|-<br />
| Congress || || <br />
|-<br />
| Designate || || <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Mitsuhiro SHIGEMATSU || pshige<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Magnum || || <br />
|-<br />
| Manila || || <br />
|-<br />
| Mistral || || <br />
|-<br />
| Murano || Ekaterina Chernova || katyafervent <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Joe Gordon or Michael Still || Jog0 or mikal<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || || <br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Andrey Pavlov || AndreyPavlov<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k<br />
<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Nikhil Manchanda || SlickNik<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for <br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Nova || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Glance || || <br />
|-<br />
| Horizon || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Neutron || || <br />
|-<br />
| Swift || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| || Brent Eagles || beagles || Nova liaison for Neutron<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| Sahara / Heat || || ||<br />
|-<br />
| || Vitaly Gridnev || vgridnev || Sahara liaison for Heat<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Adam Gandelman || adam_g<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || Tyr Johanson || tyr<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Magnum || Adrian Otto || adria̠n_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Serg Melikyan || smelikyan<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Craig Vyvial || cp16net<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=105507I18nTeam/team/zh cn2016-02-23T05:46:34Z<p>Daisy: </p>
<hr />
<div>[[Category:I18n]]<br />
= 简体中文翻译团队 =<br />
== 联系方式 ==<br />
协调人: 郭迎春。联系方式：IRC ID "Daisy"或者[mailto:guoyingc@cn.ibm.com 发邮件]给她 <br />
<br />
IRC channel: #openstack-i18n<br />
<br />
微信组: 添加微信好友 "daisy-ycguo", 她会把您加到中文翻译团队的微信组中。<br />
<br />
== 如何加入 ==<br />
见 [http://docs.openstack.org/developer/i18n/official_translator.html Steps to become a OpenStack translator]<br />
<br />
== 术语 ==<br />
=== 不翻译使用英文的术语 ===<br />
在翻译过程中，下列术语仍然使用英文形式，不需要翻译。因为我们没有找到合适的中文词汇来描述。<br />
* Overlay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=104546I18nTeam/team/zh cn2016-02-19T07:04:16Z<p>Daisy: /* Chinese Translation Team */</p>
<hr />
<div>[[Category:I18n]]<br />
= Chinese Translation Team =<br />
== Contact information ==<br />
Coordinator: Mail to [mailto:guoyingc@cn.ibm.com Ying Chun Guo (Daisy)]<br />
<br />
IRC channel: #openstack-i18n<br />
<br />
Wechat group: Add Wechat "daisy-ycguo", then Daisy will add you to our group.<br />
<br />
== How to join ==<br />
See [http://docs.openstack.org/developer/i18n/official_translator.html Steps to become a OpenStack translator]<br />
<br />
== Glossary ==<br />
=== Not translated glossaries ===<br />
While translating, those glossaries will keep their English format and will not be translated. Because we don't find appropriate Chinese words to describe them.<br />
* Overlay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=104545I18nTeam/team/zh cn2016-02-19T07:02:38Z<p>Daisy: /* Contact information */</p>
<hr />
<div>[[Category:I18n]]<br />
= Chinese Translation Team =<br />
== Contact information ==<br />
Coordinator: Mail to [mailto:guoyingc@cn.ibm.com Ying Chun Guo (Daisy)]<br />
IRC channel: #openstack-i18n<br />
Wechat group: Add Wechat "daisy-ycguo", then Daisy will add you to our group.<br />
<br />
== How to join ==<br />
Register an ID in www.transifex.com, and then send the ID to [mailto:guoyingc@cn.ibm.com Daisy] with a short introduction.<br />
<br />
== How to contribute ==<br />
You can join below work items:<br />
* [https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/openstack-ops/ Operation Guide] Chinese translation<br />
* Horizon Chinese translation<br />
<br />
== Glossary ==<br />
=== Not translated glossaries ===<br />
While translating, those glossaries will keep their English format and will not be translated. Because we don't find appropriate Chinese words to describe them.<br />
* Overlay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=102982Meetings/I18nTeamMeeting2016-02-03T14:38:37Z<p>Daisy: /* Next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meeting ===<br />
UTC 0600, Feb 4<br />
* Discussion: statistic data and ATC<br />
* Follow up with translation check website<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 7th January ====<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 17th December ====<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: remove from Transifex ?<br />
* Open discussions<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=102981Meetings/I18nTeamMeeting2016-02-03T14:37:53Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meeting ===<br />
* Discussion: statistic data and ATC<br />
* Follow up with translation check website<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 7th January ====<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 17th December ====<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: remove from Transifex ?<br />
* Open discussions<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=VirtualSprints&diff=101894VirtualSprints2016-01-22T07:46:02Z<p>Daisy: </p>
<hr />
<div>The OpenStack project holds its various virtual sprints on '''IRC''', in the <code><nowiki>#openstack-sprint</nowiki></code> channel on Freenode. Virtual sprints provide an opportunity for people from all over the world to come together and focus for a short period of time on a subset of code, bugs, and reviews. Everyone is encouraged to participate.<br />
<br />
Please post sprints in reverse chronological order.<br />
<br />
For in person OpenStack sprints, visit the [https://wiki.openstack.org/wiki/Sprints Sprints] page.<br />
<br />
== Schedule of Upcoming OpenStack Virtual Sprints ==<br />
<br />
=== Title of Sprint ===<br />
* Date of Sprint<br />
* Duration of Sprint<br />
* Contact name of Sprint Organizer<br />
* IRC channel for sprint (use of #openstack-sprint is encouraged)<br />
* Etherpad link for details and in sprint work<br />
* Voice Conferencing: https://wiki.openstack.org/wiki/Infrastructure/Conferencing<br />
<br />
=== I18n Team Virtual Midcycle Sprint ===<br />
* Date: January 29-30-31, 2016<br />
* Duration: 48 hours since UTC 1330 on January 29<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Ying Chun Guo (Daisy)<br />
* See [https://etherpad.openstack.org/p/i18n-mitaka-virtualsprint etherpad] for details<br />
<br />
=== Puppet OpenStack ===<br />
* January 25-26-27, 2016<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Emilien Macchi (EmilienM)<br />
* See [https://etherpad.openstack.org/p/puppet-happy-new-year-2016 etherpad] for details<br />
<br />
=== Ironic Virtual Mitaka Midcycle ===<br />
* '''Details TBD'''<br />
* February 16-18, 2016<br />
* Duration of Sprint<br />
* Jim Rollenhagen (jroll)<br />
* IRC channel: #openstack-sprint<br />
* Etherpad link for details and in sprint work<br />
* Voice Conferencing: https://wiki.openstack.org/wiki/Infrastructure/Conferencing<br />
<br />
== Previous OpenStack Virtual Sprints ==<br />
<br />
=== Infra "holiday party" knowledge transfer virtual sprint ===<br />
* Date: Friday December 18th<br />
* Duration: 24 hours beginning 00:00 utc<br />
* Contact: Anita Kuno (anteaya)<br />
* IRC channel for sprint: #openstack-sprint<br />
* Etherpad: https://etherpad.openstack.org/p/infra-holiday-party-2015<br />
* Description: Since we can't get together in the same physical location I thought it might be nice to try to have a festive gathering online. This event is for folks who self-identify as part of the infra team.<br />
<br />
=== Nova API Document Virtual Sprint ===<br />
* Date: Dec 8. 2015<br />
* Duration: 2 Days<br />
* Contact: Alex Xu (irc: alex_xu)<br />
* IRC channel for sprint: #openstack-nova<br />
* Etherpad: https://etherpad.openstack.org/p/nova-v2.1-api-doc , ML: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079220.html<br />
<br />
=== Oslo Documentation Sprint ===<br />
* Date: September 24-45, 2015<br />
* Length: Two days<br />
* Contact: Davanum Srinivas (dims)<br />
* IRC: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Etherpad: https://etherpad.openstack.org/p/oslo-liberty-virtual-doc-sprint<br />
<br />
=== Puppet OpenStack ===<br />
* Date: September 2-4, 2015<br />
* Length: Three days<br />
* Contact: Emilien Macchi (EmilienM) <br />
* IRC: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Etherpad: https://etherpad.openstack.org/p/puppet-liberty-mid-cycle<br />
<br />
=== Installation guide conversion from DocBook to RST ===<br />
* Date: 15 UTC on July 22 to 15 UTC on July 24<br />
* Length: Two days<br />
* Contacts: Karin Levenstein (KLevenstein) and Matt Kassawara (Sam-I-Am)<br />
* IRC: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Etherpad: https://etherpad.openstack.org/p/installguide-rst-virtual-sprint (includes guidance on how to participate)<br />
<br />
=== Ceilometer Virtual Mid-Cycle ===<br />
* Date: Thursday and Friday July 9 & 10 2015<br />
* For more information contact Chris or Prad in IRC: cdent, prad<br />
* Agenda in progress, will emerge at [[Meetings/Ceilometer/Liberty Virtual Mid-Cycle|Liberty Virtual Mid-Cycle]]<br />
* Everyone welcome to participate<br />
<br />
=== OpenStack Common-CI Solution ===<br />
* Date Wednesday July 8 1600 UTC<br />
* Sprint will run for 48 hours<br />
* Lead (to contact for more information): Ramy Asselin (asselin)<br />
* IRC: <code><nowiki>#openstack-sprint</nowiki></code><br />
* See [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html] for spec details<br />
* Etherpad (includes guidance on how to participate): https://etherpad.openstack.org/p/common-ci-sprint<br />
<br />
=== OpenStack Project Team Guide ===<br />
* Thursday June 18 - Friday June 19<br />
* Sprint will run for 48 hours<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Thierry Carrez (ttx)<br />
* Etherpad (includes guidance on how to participate): https://etherpad.openstack.org/p/project-team-guide<br />
<br />
=== OpenStack Networking Guide Neutron-Docs ===<br />
* Thursday April 23, 2015 at 1600 UTC<br />
* Sprint will run for 24 hours<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Edgar Magana (emagana)<br />
* See [https://wiki.openstack.org/wiki/NetworkingGuide/TOC] for networking guide details<br />
* Etherpad (includes guidance on how to participate): [https://etherpad.openstack.org/p/networking-guide]<br />
<br />
=== OpenStack Dashboard AngularJS ===<br />
* Wednesday February 18, 2015 at 2000 UTC -- 23:30 UTC<br />
* Tentative repeat on Thursday<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): David Lyle (david-lyle)<br />
* Etherpad (includes guidance on how to participate): https://etherpad.openstack.org/p/horizon-kilo-virtual-sprint<br />
<br />
=== OpenStack infra puppet module split ===<br />
* Wednesday January 28, 2015 at 1500 UTC<br />
* Sprint will run for 24 hours<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Ramy Asselin (asselin)<br />
* See [http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet-modules.html] for spec details<br />
* Etherpad (includes guidance on how to participate): [https://etherpad.openstack.org/p/puppet-module-split-sprint]<br />
<br />
=== OpenStack third-party CI documentation ===<br />
* Wednesday January 21, 2015 at 1600 UTC<br />
* Sprint will run for 48 hours<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Kurt Taylor (krtaylor)<br />
* Etherpad (includes guidance on how to participate): [https://etherpad.openstack.org/p/third-party-ci-documentation]<br />
<br />
=== OpenStack infra-manual ===<br />
* Monday December 1 - 2, 2014 at 1500 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20140425T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])<br />
* Sprint will run for 48 hours<br />
* IRC channel: <code><nowiki>#openstack-sprint</nowiki></code><br />
* Lead (to contact for more information): Anita Kuno (anteaya)<br />
* See [http://lists.openstack.org/pipermail/openstack-dev/2014-November/049993.html email accouncement] for details<br />
* Etherpad (includes guidance on how to participate): https://etherpad.openstack.org/p/infra-manual-sprint-December-2014<br />
<br />
<br />
[[Category: Resources]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=100630Meetings/I18nTeamMeeting2016-01-07T03:41:54Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 7th January at 0600 UTC<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 17th December ====<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: remove from Transifex ?<br />
* Open discussions<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=99876Meetings/I18nTeamMeeting2015-12-17T03:06:18Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 17th December at 1300 UTC<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: remove from Transifex ?<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=99804Meetings/I18nTeamMeeting2015-12-16T16:15:38Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 17th December at 1300 UTC<br />
* Status update: Liberty installation guide translation<br />
* Discussion: Midcycle spring/virtual spring<br />
* Discussion: how to handle Transifex ?<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=99750Meetings/I18nTeamMeeting2015-12-16T08:18:51Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 17th December at 1300 UTC<br />
* Discussion: MidCycle Spring?<br />
* Status update: Liberty installation guide translation<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=99749Meetings/I18nTeamMeeting2015-12-16T08:18:05Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 17th December at 1300 UTC<br />
* Discussion: MidCycle Spring?<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=99748Meetings/I18nTeamMeeting2015-12-16T08:17:34Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 3th December at 0600 UTC<br />
* Discussion: MidCycle Spring?<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 3th Dec ====<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=BugTriage&diff=99178BugTriage2015-12-09T06:18:43Z<p>Daisy: /* Task 1: Confirm new bugs (anyone) */</p>
<hr />
<div>These are the bug triaging tasks, in descending order of priority. Some tasks are accessible to everyone, while some others require bug supervisor rights (usually limited to core teams). Before you start triaging, please learn everything on how we use [[Bugs]] !<br />
<br />
== Task 1: Confirm new bugs (anyone) ==<br />
<br />
When someone files a bug, its state is set to ''New''. The most important step in bug triaging is to provide feedback on that bug and make sure it's a genuine bug.<br />
<br />
Lists for: [https://bugs.launchpad.net/nova/+bugs?field.status=NEW&field.importance=UNDECIDED Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status=NEW&field.importance=UNDECIDED Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status=NEW&field.importance=UNDECIDED Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status=NEW&field.importance=UNDECIDED Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status=NEW&field.importance=UNDECIDED Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status=NEW&field.importance=UNDECIDED Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status=NEW&field.importance=UNDECIDED Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status=NEW&field.importance=UNDECIDED Tempest],<br />
[https://bugs.launchpad.net/heat/+bugs?field.status=NEW&field.importance=UNDECIDED Heat]<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status=NEW&field.importance=UNDECIDED Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status=NEW&field.importance=UNDECIDED Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status=NEW&field.importance=UNDECIDED Documentation],<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status=NEW&field.importance=UNDECIDED API Docs]<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status=NEW&field.importance=UNDECIDED API Docs]<br />
[https://bugs.launchpad.net/openstack-i18n/+bugs?field.status=NEW&field.importance=UNDECIDED Translations]<br />
<br />
Graphs for bug counts: http://status.openstack.org/bugday/<br />
<br />
* If the bug description is incomplete or the report is lacking the information necessary to reproduce the issue, you should ask the reporter to provide missing information, and set the bug status to ''Incomplete''<br />
* If the bug report contains enough information, you can reproduce it (or it looks valid), then you should set its status to ''Confirmed''<br />
* If the bug has security implications, you should set the security flag (under "This report is public" on the top right)<br />
* If the bug affects a specific area covered by an [[BugTags|official tag]], you should set the tag. For example, if the bug is likely to be quite easy to solve, add the ''low-hanging-fruit'' tag<br />
<br />
While they are at it, people with bug supervisors rights can complete task 2 for the same bug.<br />
<br />
== Task 2: Prioritize confirmed bugs (bug supervisors) ==<br />
<br />
When someone files a bug, its importance is set to ''Undecided''. Setting importance is pretty critical as it allows to prioritize all the rest of the work correctly.<br />
<br />
Lists for: [https://bugs.launchpad.net/nova/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Tempest],<br />
[https://bugs.launchpad.net/heat/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Heat],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status=CONFIRMED&field.importance=UNDECIDED Ironic],<br />
<br />
Graphs for: [http://webnumbr.com/nova-confirmed-undecided Nova]<br />
<br />
* Based on the bug information, set priority to:<br />
** ''Critical'' if the bug prevents a key feature from working properly (regression) for all users (or without a simple workaround) or result in data loss<br />
** ''High'' if the bug prevents a key feature from working properly for some users (or with a workaround)<br />
** ''Medium'' if the bug prevents a secondary feature from working properly<br />
** ''Low'' if the bug is mostly cosmetic<br />
** ''Wishlist'' if the bug is not really a bug, but rather a welcome change in behavior<br />
* If the bug contains the solution, or a patch, set the bug status to ''Triaged''<br />
* please note, milestone is generally under the control of the project drivers, and is usually used only for release blocking bugs<br />
<br />
== Task 3: Solve inconsistencies (anyone) ==<br />
<br />
Some bugs might end up in an incorrect state. You should fix:<br />
<br />
=== New bugs with a priority set ===<br />
<br />
Status should be set to ''Confirmed'' (or ''In progress'' if an assignee is set):<br />
<br />
Lists for: [https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST Documentation],<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=NEW&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST API Docs]<br />
<br />
=== In progress bugs without an assignee ===<br />
<br />
An assignee should bet set, or the bug should return to ''Confirmed'' status:<br />
<br />
Lists for: [https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none Documentation],<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=INPROGRESS&assignee_option=none API Docs]<br />
<br />
== Task 4: Review incomplete bugs (anyone) ==<br />
<br />
Incomplete bugs should be reassessed regularly.<br />
<br />
Lists for: [https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE Documentation],<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE API Docs]<br />
<br />
* If the reporter provided the requested answer: bug status should be set to ''Confirmed''<br />
* If the reporter did provide information, but more detail is required: ask for missing information<br />
* If the reporter did not answer within 2 weeks: Politely remind the reporter to provide missing information, for example:<br />
<br />
<pre><nowiki><br />
We cannot solve the issue you reported without more information. Could you please provide the requested information ?<br />
</nowiki></pre><br />
<br />
* If the reporter did not answer the reminder for another 4 weeks: Set the bug status to ''Invalid'' with a comment, for example:<br />
<br />
<pre><nowiki><br />
This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.<br />
</nowiki></pre><br />
<br />
== Task 5: Review stale ''In Progress'' bugs (anyone) ==<br />
<br />
Make sure ''In Progress'' bugs are actually in progress. Unassign them and set them back to ''New'' status and "Undecided" importance if not.<br />
<br />
Look at first hits in the following lists:<br />
[https://bugs.launchpad.net/nova/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any Documentation],<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?orderby=date_last_updated&field.status%3Alist=INPROGRESS&assignee_option=any API Docs]<br />
<br />
== Task 6: Review bugs with a patch (bug supervisors) ==<br />
<br />
Some bugs are filed with an attached patch. We should review if the patch looks indeed like a patch, and if yes, set the bug status to ''Triaged'' to show that it comes with a likely solution, ready to be implemented.<br />
<br />
Lists for:<br />
[https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on Ironic]<br />
<br />
== Task 7: Review Critical/High bugs (bug supervisors) ==<br />
<br />
We should review all ''Critical'' and ''High'' bugs to make sure they are still relevant and properly prioritized.<br />
<br />
Lists for:<br />
[https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH Documentation]<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH API Docs]<br />
<br />
Graphs:<br />
[http://webnumbr.com/nova-critical-bugs Nova Critical bugs]<br />
<br />
== Task 8: Review Medium/Low bugs (bug supervisors) ==<br />
<br />
We should review all ''Medium'' and ''Low'' bugs to make sure they are still relevant and properly prioritized.<br />
<br />
Lists for:<br />
[https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW Documentation]<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW API Docs]<br />
<br />
== Task 9: Deprecate old wishlist bugs (bug supervisors) ==<br />
<br />
We should review all ''Wishlist'' bugs to make sure they are still relevant. Old wishlist bugs (created more than a year ago) should be reviewed to see if they were not accidentally implemented or improperly prioritized. If they really are wishlist items that nobody seems to be interested in implementing, they can be closed as "Opinion" to reduce bug list clutter. You can use the following message:<br />
<br />
<pre><nowiki><br />
This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. This bug can be reopened (set back to "New") if someone decides to work on this.<br />
</nowiki></pre><br />
<br />
Lists for:<br />
[https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Nova],<br />
[https://bugs.launchpad.net/swift/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Swift],<br />
[https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Cinder],<br />
[https://bugs.launchpad.net/glance/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Glance],<br />
[https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Keystone],<br />
[https://bugs.launchpad.net/horizon/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Horizon],<br />
[https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Neutron],<br />
[https://bugs.launchpad.net/tempest/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Tempest],<br />
[https://bugs.launchpad.net/oslo/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Oslo],<br />
[https://bugs.launchpad.net/ironic/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Ironic],<br />
[https://bugs.launchpad.net/openstack-manuals/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST Documentation]<br />
[https://bugs.launchpad.net/openstack-api-site/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance=WISHLIST API Docs]<br />
<br />
== Task 10: Celebrate! ==<br />
<br />
If you've reached this step, have a beer, it's on me.</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=98949I18nTeam/team/zh cn2015-12-07T07:31:02Z<p>Daisy: /* Not translated glossaries */</p>
<hr />
<div>[[Category:I18n]]<br />
= Chinese Translation Team =<br />
== Contact information ==<br />
Coordinator: [mailto:guoyingc@cn.ibm.com Ying Chun Guo (Daisy)]<br />
<br />
Mail list:[mailto:openstack-cn-translators@googlegroups.com openstack-cn-translators@googlegroups.com]<br />
<br />
Website:<br />
<br />
== How to join ==<br />
Register an ID in www.transifex.com, and then send the ID to [mailto:guoyingc@cn.ibm.com Daisy] with a short introduction.<br />
<br />
== How to contribute ==<br />
You can join below work items:<br />
* [https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/openstack-ops/ Operation Guide] Chinese translation<br />
* Horizon Chinese translation<br />
<br />
== Glossary ==<br />
=== Not translated glossaries ===<br />
While translating, those glossaries will keep their English format and will not be translated. Because we don't find appropriate Chinese words to describe them.<br />
* Overlay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=98948I18nTeam/team/zh cn2015-12-07T07:30:40Z<p>Daisy: </p>
<hr />
<div>[[Category:I18n]]<br />
= Chinese Translation Team =<br />
== Contact information ==<br />
Coordinator: [mailto:guoyingc@cn.ibm.com Ying Chun Guo (Daisy)]<br />
<br />
Mail list:[mailto:openstack-cn-translators@googlegroups.com openstack-cn-translators@googlegroups.com]<br />
<br />
Website:<br />
<br />
== How to join ==<br />
Register an ID in www.transifex.com, and then send the ID to [mailto:guoyingc@cn.ibm.com Daisy] with a short introduction.<br />
<br />
== How to contribute ==<br />
You can join below work items:<br />
* [https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/openstack-ops/ Operation Guide] Chinese translation<br />
* Horizon Chinese translation<br />
<br />
== Glossary ==<br />
=== Not translated glossaries ===<br />
While translating, those glossaries will keep their English format and will not be translated. Because we don't find appropriate Chinese words to describe them.<br />
* Overylay</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=98510Meetings/I18nTeamMeeting2015-12-02T09:35:46Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 3th December at 0600 UTC<br />
* Discussion: Bug management process in Launchpad<br />
* Discussion: Glossary management process<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 19th Nov ====<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
==== 5th Nov ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
==== 20th August ====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=97236Meetings/I18nTeamMeeting2015-11-18T08:52:50Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 19th December at 1300 UTC<br />
* Status update and issues collection of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 5th December ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
==== 20th August ====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=97235Meetings/I18nTeamMeeting2015-11-18T08:50:28Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 19th December at 1300 UTC<br />
* Status update of the work items<br />
* Discussion: how to manage I18n related bug reports ?<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 5th December ====<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
==== 20th August ====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team&diff=96712I18nTeam/team2015-11-13T05:59:06Z<p>Daisy: /* Local Translation Teams */</p>
<hr />
<div>= Local Translation Teams =<br />
<br />
*[[I18nTeam/team/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/team/ca|Catalan]]<br />
*[[I18nTeam/team/zh_cn|Simplified Chinese]]<br />
*Traditional Chinese<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/team/en_au|English (Australia)]]<br />
*[[I18nTeam/team/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/team/hi|Hindi]]<br />
*[[I18nTeam/team/ja|Japanese]]<br />
*[[I18nTeam/team/ko_KR|Korean]]<br />
*[[I18nTeam/team/pl|Polish]]<br />
*[[I18nTeam/team/pa_IN|Punjabi]]<br />
*[[I18nTeam/team/ru|Russian]]<br />
*[[I18nTeam/team/es|Spanish]]<br />
*Vietnamese<br />
*Bahasa Indonesia<br />
*[[I18nTeam/team/th|Thai]]<br />
*Turkish<br />
* [[i18nTeam/team/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team&diff=96711I18nTeam/team2015-11-13T05:56:55Z<p>Daisy: </p>
<hr />
<div>= Local Translation Teams =<br />
<br />
*[[I18nTeam/team/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/team/ca|Catalan]]<br />
*[[I18n/team/team/zh_cn|Simplified Chinese]]<br />
*Traditional Chinese<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/team/en_au|English (Australia)]]<br />
*[[I18nTeam/team/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/team/hi|Hindi]]<br />
*[[I18nTeam/team/ja|Japanese]]<br />
*[[I18nTeam/team/ko_KR|Korean]]<br />
*[[I18nTeam/team/pl|Polish]]<br />
*[[I18nTeam/team/pa_IN|Punjabi]]<br />
*[[I18nTeam/team/ru|Russian]]<br />
*[[I18nTeam/team/es|Spanish]]<br />
*Vietnamese<br />
*Bahasa Indonesia<br />
*[[I18nTeam/team/th|Thai]]<br />
*Turkish<br />
* [[i18nTeam/team/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam&diff=96382I18nTeam2015-11-11T06:20:52Z<p>Daisy: </p>
<hr />
<div>__NOTOC__<br />
= The I18n Team = <!--T:1--><br />
[[File:Translation.svg|right|150px]]<br />
Internationalization is essential to make OpenStack ubiquitous. The mission of OpenStack I18n team is to make OpenStack ubiquitously accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for high quality translations.<br />
<br />
<!--T:2--><br />
''"Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text."'' - from wikipedia.<br />
<br />
<!--T:3--><br />
The OpenStack I18n team will take responsible for the I18n and L10n of OpenStack. Our work will include:<br />
* Translation of documentations, messages, websites, and etc.<br />
* Translation platform maintenance and enhancements<br />
* I18n test<br />
<br />
= Contributing = <!--T:4--><br />
I18n team welcome any kinds of contribution.<br />
<br />
== Contribute to translations == <!--T:5--><br />
If you want to help the translations, firstly you may want to [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no become an official translator and join your language team]. Go to [https://translate.openstack.org translation website] to start translation then. You could find the translation jobs in the home page or contact with the coordinators.<br />
<br />
<!--T:6--><br />
If you cannot find your local team, you can request to [[I18nTeam/CreateLocalTeam|create a local translation team]].<br />
<br />
<!--T:7--><br />
If you want to report translation errors, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad and report bugs. Mark bugs with a tag "'''translation'''".<br />
<br />
<!--T:8--><br />
There are three different roles in a translation team.<br />
* [[I18nTeam/Management|Coordinator]]: a privileged member in a translation team who can help in team management tasks, such as approving new members and reviewing contributions to that language. We also have task coordinators for specific tasks.<br />
* [[Documentation/Translation#Contribute_as_a_translator|Member (Translator)]] : a person who can submit translations.<br />
* [[Documentation/Translation#Contribute_as_a_reviewer|Reviewer]]: a person who can proofread translations and mark them as reviewed.<br />
<br />
== Contribute to translation tools == <!--T:9--><br />
Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag "'''tools'''".<br />
<br />
== Fix I18n bugs == <!--T:10--><br />
If you want to help to report or fix I18n bugs of OpenStack, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad. Mark bugs with a tag "'''i18n'''".<br />
<br />
= Getting in touch = <!--T:11--><br />
<br />
<!--T:12--><br />
* Mailing List<br />
** We use [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n@lists.openstack.org] as the mailing list.<br />
* IRC<br />
** We all hang out on #openstack-i18n IRC channel on freenode.<br />
* Team Meeting<br />
** The I18n team meets bi-weekly on Thursdays at alternating times.<br />
** Please see [[Meetings/I18nTeamMeeting]]<br />
<br />
= Local Translation Teams = <!--T:13--><br />
Lead: Ying Chun "Daisy" Guo (Daisy on IRC)<br />
<br />
<!--T:14--><br />
*[[I18nTeam/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/ca|Catalan]]<br />
*[[I18n/team/zh_cn |Simplified Chinese]]<br />
*[[I18n/team/zh_tw |Traditional Chinese]]<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/en_au|English (Australia)]]<br />
*[[I18nTeam/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/hi|Hindi]]<br />
*[[I18nTeam/ja|Japanese]]<br />
*[[I18nTeam/team/ko_KR|Korean]]<br />
*[[I18nTeam/pl|Polish]]<br />
*[[I18nTeam/pa_IN|Punjabi]]<br />
*[[I18nTeam/ru|Russian]]<br />
*[[I18nTeam/es|Spanish]]<br />
*Vietnamese<br />
*[[I18nTeam/id|Bahasa Indonesia]]<br />
*[[I18nTeam/th|Thai]]<br />
*[[I18nTeam/tr_TR|Turkish]]<br />
* [[i18nTeam/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]<br />
----<br />
[[category: Horizontal_Team]]<br />
[[Category:I18n]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/CreateLocalTeam&diff=96381I18nTeam/CreateLocalTeam2015-11-11T06:16:06Z<p>Daisy: </p>
<hr />
<div><translate><br />
[[Category:I18n]]<br />
= Create a Local Translation Team =<br />
OpenStack I18n team is a team to coordinate all language translations and the cooperation between I18n team and development teams. Usually, OpenStack I18n team have work plans. Local translation teams could follow I18n team's work plans. But as a local translation team, your team also have the right to decide your own work items and the priorities.<br />
<br />
<br />
If you want to create a local translation team and you want to be the coordinator, please follow below steps:<br />
# Following this [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no wiki page] to register an ID in the translation website. <br />
# Write an email to "openstack-i18n@lists.openstack.org" to introduce yourself and the language team you want to create, together with your ID in Transifex.<br />
# When your request is approved, add an item in "[[I18nTeam#Local_Translation_Teams|Local Translation Teams]]" in the wiki page, create a wiki page under page /I18nTeam ( for example, I18nTeam/zh_cn ) to introduce your team, with below information at least: the contact information, the web page, and the work items.<br />
<br />
Then your locale translation team is created successfully. You can enroll more people to join and start your translation works.<br />
<br />
Don't forget to work with [[OpenStackUserGroups|your local user group]] coordinator and the [[Community/AmbassadorProgram|OpenStack Ambassadors]] to raise awareness and gather members :)<br />
</translate></div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/CreateLocalTeam&diff=96380I18nTeam/CreateLocalTeam2015-11-11T06:13:19Z<p>Daisy: </p>
<hr />
<div>[[Category:I18n]]<br />
<translate><br />
= Create a Local Translation Team =<br />
OpenStack I18n team is a team to coordinate all language translations and the cooperation between I18n team and development teams. Usually, OpenStack I18n team have work plans. Local translation teams could follow I18n team's work plans. But as a local translation team, your team also have the right to decide your own work items and the priorities.<br />
<br />
<br />
If you want to create a local translation team and you want to be the coordinator, please follow below steps:<br />
# Following this [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no wiki page] to register an ID in the translation website. <br />
# Write an email to "openstack-i18n@lists.openstack.org" to introduce yourself and the language team you want to create, together with your ID in Transifex.<br />
# When your request is approved, add an item in "[[I18nTeam#Local_Translation_Teams|Local Translation Teams]]" in the wiki page, create a wiki page under page /I18nTeam ( for example, I18nTeam/zh_cn ) to introduce your team, with below information at least: the contact information, the web page, and the work items.<br />
<br />
Then your locale translation team is created successfully. You can enroll more people to join and start your translation works.<br />
<br />
Don't forget to work with [[OpenStackUserGroups|your local user group]] coordinator and the [[Community/AmbassadorProgram|OpenStack Ambassadors]] to raise awareness and gather members :)<br />
</translate></div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam&diff=96150I18nTeam2015-11-10T06:23:30Z<p>Daisy: </p>
<hr />
<div>__NOTOC__<br />
<translate><br />
= The I18n Team = <!--T:1--><br />
[[File:Translation.svg|right|150px]]<br />
Internationalization is essential to make OpenStack ubiquitous. The mission of OpenStack I18n team is to make OpenStack ubiquitously accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for high quality translations.<br />
<br />
<!--T:2--><br />
''"Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text."'' - from wikipedia.<br />
<br />
<!--T:3--><br />
The OpenStack I18n team will take responsible for the I18n and L10n of OpenStack. Our work will include:<br />
* Translation of documentations, messages, websites, and etc.<br />
* Translation platform maintenance and enhancements<br />
* I18n test<br />
<br />
= Contributing = <!--T:4--><br />
I18n team welcome any kinds of contribution.<br />
<br />
== Contribute to translations == <!--T:5--><br />
If you want to help the translations, firstly you may want to [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no become an official translator and join your language team]. Go to [https://translate.openstack.org translation website] to start translation then. You could find the translation jobs in the home page or contact with the coordinators.<br />
<br />
<!--T:6--><br />
If you cannot find your local team, you can request to [[I18nTeam/CreateLocalTeam|create a local translation team]].<br />
<br />
<!--T:7--><br />
If you want to report translation errors, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad and report bugs. Mark bugs with a tag "'''translation'''".<br />
<br />
<!--T:8--><br />
There are three different roles in a translation team.<br />
* [[I18nTeam/Management|Coordinator]]: a privileged member in a translation team who can help in team management tasks, such as approving new members and reviewing contributions to that language. We also have task coordinators for specific tasks.<br />
* [[Documentation/Translation#Contribute_as_a_translator|Member (Translator)]] : a person who can submit translations.<br />
* [[Documentation/Translation#Contribute_as_a_reviewer|Reviewer]]: a person who can proofread translations and mark them as reviewed.<br />
<br />
== Contribute to translation tools == <!--T:9--><br />
Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag "'''tools'''".<br />
<br />
== Fix I18n bugs == <!--T:10--><br />
If you want to help to report or fix I18n bugs of OpenStack, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad. Mark bugs with a tag "'''i18n'''".<br />
<br />
= Getting in touch = <!--T:11--><br />
<br />
<!--T:12--><br />
* Mailing List<br />
** We use [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n@lists.openstack.org] as the mailing list.<br />
* IRC<br />
** We all hang out on #openstack-i18n IRC channel on freenode.<br />
* Team Meeting<br />
** The I18n team meets bi-weekly on Thursdays at alternating times.<br />
** Please see [[Meetings/I18nTeamMeeting]]<br />
<br />
= Local Translation Teams = <!--T:13--><br />
Lead: Ying Chun "Daisy" Guo (Daisy on IRC)<br />
<br />
<!--T:14--><br />
*[[I18nTeam/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/ca|Catalan]]<br />
*[[I18n/team/zh_cn |Simplified Chinese]]<br />
*[[I18n/team/zh_tw |Traditional Chinese]]<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/en_au|English (Australia)]]<br />
*[[I18nTeam/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/hi|Hindi]]<br />
*[[I18nTeam/ja|Japanese]]<br />
*[[I18nTeam/team/ko_KR|Korean]]<br />
*[[I18nTeam/pl|Polish]]<br />
*[[I18nTeam/pa_IN|Punjabi]]<br />
*[[I18nTeam/ru|Russian]]<br />
*[[I18nTeam/es|Spanish]]<br />
*Vietnamese<br />
*[[I18nTeam/id|Bahasa Indonesia]]<br />
*[[I18nTeam/th|Thai]]<br />
*[[I18nTeam/tr_TR|Turkish]]<br />
* [[i18nTeam/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]<br />
</translate><br />
----<br />
[[category: Horizontal_Team]]<br />
[[Category:I18n]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/zh_cn&diff=96148I18nTeam/team/zh cn2015-11-10T06:22:42Z<p>Daisy: Daisy moved page I18nTeam/zh cn to I18nTeam/team/zh cn: I18nTeam will be translated</p>
<hr />
<div>[[Category:I18n]]<br />
= Chinese Translation Team =<br />
== Contact information ==<br />
Coordinator: [mailto:guoyingc@cn.ibm.com Ying Chun Guo (Daisy)]<br />
<br />
Mail list:[mailto:openstack-cn-translators@googlegroups.com openstack-cn-translators@googlegroups.com]<br />
<br />
Website:<br />
<br />
== How to join ==<br />
Register an ID in www.transifex.com, and then send the ID to [mailto:guoyingc@cn.ibm.com Daisy] with a short introduction.<br />
<br />
== How to contribute ==<br />
You can join below work items:<br />
* [https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/openstack-ops/ Operation Guide] Chinese translation<br />
* Horizon Chinese translation</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/zh_cn&diff=96149I18nTeam/zh cn2015-11-10T06:22:42Z<p>Daisy: Daisy moved page I18nTeam/zh cn to I18nTeam/team/zh cn: I18nTeam will be translated</p>
<hr />
<div>#REDIRECT [[I18nTeam/team/zh cn]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/team/ko_KR&diff=96146I18nTeam/team/ko KR2015-11-10T06:20:32Z<p>Daisy: Daisy moved page I18nTeam/ko KR to I18nTeam/team/ko KR: I18nTeam will be translated</p>
<hr />
<div>[[Category:I18n]]<br />
<br />
= Korean Translation Team =<br />
<br />
=== Contact information ===<br />
* Coordinator: [mailto:gang.sungjin@gmail.com Sungjin Kang]<br />
* Website: [https://www.facebook.com/groups/openstack.kr/ Korean User Group for Facebook]<br />
* 메일링: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-ko<br />
** 메일링 리스트는 꼭 가입해주셨으면 합니다. 메일링으로 모든걸 주고 받을 생각입니다.<br />
* irc: freenode.net #openstack-ko<br />
<br />
=== 번역 관련 내용 ===<br />
* 코드네임은 그냥 영문 그대로 사용해주세요.<br />
* 단어가 한국어로 대치되는 경우에는 그 단어를 사용하지만, 정확하지 않으시다면 번역하지 않고 원문 그대로 놔두셔도 됩니다. <br />
* [[단어집]]을 확인해주세요.<br />
** 수정보다는 추가를 해주시고, 수정하실때는 수정을 하는 이유에 대해서 코멘트를 남겨주세요.<br />
<br />
=== 번역 사이트 ===<br />
* Zanata : https://translate.openstack.org/<br />
<br />
# 번역을 시작하기 전에, '''[http://docs.openstack.org/infra/manual/developers.html#account-setup 컨트리뷰터 라이선스 동의서에 동의]'''를 해야 합니다. ([https://review.openstack.org/static/cla.html ''OpenStack 개인 컨트리뷰터 라이선스 동의서''에 대한 전체 텍스트 미리보기]를 원하는 경우 먼저 살펴볼 수 있습니다.)<br />
#* 노트: 단지 번역만을 하고자 하는 경우에는, 간단히 말하자면, [https://www.openstack.org/join/ OpenStack Foundation에 가입 ("Foundation Member" 선택)] 및 [http://docs.openstack.org/infra/manual/developers.html#sign-the-appropriate-individual-contributor-license-agreement 적절한 개인 컨트리뷰터 라이선스 동의에 서명]을 필요로 합니다.<br />
# 사용자 ID를 Zanata에 등록<br />
## [https://translate.openstack.org Zanata 서버]로 이동합니다.<br />
## "Log in" 버튼을 클릭합니다.<br />
## OpenStack ID가 없는 경우, [https://www.openstack.org/join/register 여기서 생성합니다].<br />
##* 노트: 업무 이메일로 등록하는 것을 권장하는데, 회사에 기여를 하는데 도움을 줄 수 있기 때문입니다. 원하지 않는 경우에는, 개인 이메일을 사용해도 괜찮습니다.<br />
## OpenStack ID로 로그인한 후에, 프로필 채우기에 대한 요청이 있을 것입니다.<br />
# 번역팀에 가입 요청<br />
## 상단에서 "Languages" 를 클릭하면, 모든 언어 목록이 나타날 것입니다.<br />
## 번역하고자 하는 언어를 클릭하면, 해당 언어 페이지가 보일 것입니다.<br />
## 오른쪽 "..."을 클릭하고, "Request to join team"을 선택합니다.<br />
## 자신에 대한 간략한 소개를 입력하고, "Additional information"에는 이름을 입력한 후, "Send message"를 클릭합니다.<br />
# 요청이 수락되면, 이메일 확인을 받을 것입니다. 이후 번역을 시작할 수 있을 것입니다.<br />
<br />
=== 이것만큼은 지켜주세요 ===<br />
<br />
* '''리뷰어를 원하시는 분은 코디네이터에게 [mailto:gang.sungjin@gmail.com 메일]을 보내주세요.'''<br />
* 주요 프로젝트의 콘솔 메시지나 에러 메시지는 번역안합니다.<br />
** 번역을 한다고해도, 콘솔에서는 보이지 않는 문제와 함께, 에러가 발생했을때 검색하는데 어려움이 있습니다.<br />
** 단, Horizon의 경우엔 error까지 번역해주시면됩니다.<br />
* 맞춤법 검사를 부탁드리겠습니다.<br />
<br />
=== 진행중인 것 ===<br />
<br />
* Zanata 메인에 작성된 내용에 따라 진행합니다.<br />
* 간간히 Release가 될때마나 간단한 번역을 진행합니다.<br />
* 그리고 Horizon의 경우, 끊임없이 번역하니 시간나실때마다 번역안된 문구가 있을때마다 추가해주시면됩니다.<br />
<br />
=== 번역 완료된 문서 ===<br />
# API 문서 : http://developer.openstack.org/ko_KR/api-guide/quick-start/<br />
## 이전 API 문서 (<Liberty): http://docs.openstack.org/ko_KR/api/quick-start/content/index.html</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/ko_KR&diff=96147I18nTeam/ko KR2015-11-10T06:20:32Z<p>Daisy: Daisy moved page I18nTeam/ko KR to I18nTeam/team/ko KR: I18nTeam will be translated</p>
<hr />
<div>#REDIRECT [[I18nTeam/team/ko KR]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/zh-cn&diff=96145I18nTeam/zh-cn2015-11-10T06:17:34Z<p>Daisy: Created page with "= The I18n Team = 150px 国际化对OpenStack至关重要。OpenStack国际化团队的使命是提供高质量的翻译，同时也会增强Ope..."</p>
<hr />
<div>__NOTOC__<br />
= The I18n Team =<br />
[[File:Translation.svg|right|150px]]<br />
国际化对OpenStack至关重要。OpenStack国际化团队的使命是提供高质量的翻译，同时也会增强OpenStack软件本身的国际化功能，维护翻译平台，和管理翻译流程，以此使得OpenStack能够广泛的被各种语言背景的人群访问。<br />
<br />
''"Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text."'' - from wikipedia.<br />
<br />
The OpenStack I18n team will take responsible for the I18n and L10n of OpenStack. Our work will include:<br />
* Translation of documentations, messages, websites, and etc.<br />
* Translation platform maintenance and enhancements<br />
* I18n test<br />
<br />
= Contributing =<br />
I18n team welcome any kinds of contribution.<br />
<br />
== Contribute to translations ==<br />
If you want to help the translations, firstly you may want to [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no become an official translator and join your language team]. Go to [https://translate.openstack.org translation website] to start translation then. You could find the translation jobs in the home page or contact with the coordinators.<br />
<br />
If you cannot find your local team, you can request to [[I18nTeam/CreateLocalTeam|create a local translation team]].<br />
<br />
If you want to report translation errors, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad and report bugs. Mark bugs with a tag "'''translation'''".<br />
<br />
There are three different roles in a translation team.<br />
* [[I18nTeam/Management|Coordinator]]: a privileged member in a translation team who can help in team management tasks, such as approving new members and reviewing contributions to that language. We also have task coordinators for specific tasks.<br />
* [[Documentation/Translation#Contribute_as_a_translator|Member (Translator)]] : a person who can submit translations.<br />
* [[Documentation/Translation#Contribute_as_a_reviewer|Reviewer]]: a person who can proofread translations and mark them as reviewed.<br />
<br />
== Contribute to translation tools ==<br />
Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag "'''tools'''".<br />
<br />
== Fix I18n bugs ==<br />
If you want to help to report or fix I18n bugs of OpenStack, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad. Mark bugs with a tag "'''i18n'''".<br />
<br />
= Getting in touch =<br />
<br />
* Mailing List<br />
** We use [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n@lists.openstack.org] as the mailing list.<br />
* IRC<br />
** We all hang out on #openstack-i18n IRC channel on freenode.<br />
* Team Meeting<br />
** The I18n team meets bi-weekly on Thursdays at alternating times.<br />
** Please see [[Meetings/I18nTeamMeeting]]<br />
<br />
= Local Translation Teams =<br />
Lead: Ying Chun "Daisy" Guo (Daisy on IRC)<br />
<br />
*[[I18nTeam/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/ca|Catalan]]<br />
*[[I18n/team/zh_cn |Simplified Chinese]]<br />
*[[I18n/team/zh_tw |Traditional Chinese]]<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/en_au|English (Australia)]]<br />
*[[I18nTeam/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/hi|Hindi]]<br />
*[[I18nTeam/ja|Japanese]]<br />
*[[I18nTeam/ko_KR|Korean]]<br />
*[[I18nTeam/pl|Polish]]<br />
*[[I18nTeam/pa_IN|Punjabi]]<br />
*[[I18nTeam/ru|Russian]]<br />
*[[I18nTeam/es|Spanish]]<br />
*Vietnamese<br />
*[[I18nTeam/id|Bahasa Indonesia]]<br />
*[[I18nTeam/th|Thai]]<br />
*[[I18nTeam/tr_TR|Turkish]]<br />
* [[i18nTeam/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]<br />
----<br />
[[category: Horizontal_Team]]<br />
[[Category:I18n]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Translations:I18nTeam/1/zh-cn&diff=96144Translations:I18nTeam/1/zh-cn2015-11-10T06:17:33Z<p>Daisy: Created page with "= The I18n Team = 150px 国际化对OpenStack至关重要。OpenStack国际化团队的使命是提供高质量的翻译，同时也会增强Ope..."</p>
<hr />
<div>= The I18n Team =<br />
[[File:Translation.svg|right|150px]]<br />
国际化对OpenStack至关重要。OpenStack国际化团队的使命是提供高质量的翻译，同时也会增强OpenStack软件本身的国际化功能，维护翻译平台，和管理翻译流程，以此使得OpenStack能够广泛的被各种语言背景的人群访问。</div>Daisyhttps://wiki.openstack.org/w/index.php?title=I18nTeam/zh-cn&diff=96143I18nTeam/zh-cn2015-11-10T06:14:41Z<p>Daisy: Created page with "国际化团队"</p>
<hr />
<div>__NOTOC__<br />
= The I18n Team =<br />
[[File:Translation.svg|right|150px]]<br />
Internationalization is essential to make OpenStack ubiquitous. The mission of OpenStack I18n team is to make OpenStack ubiquitously accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for high quality translations.<br />
<br />
''"Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text."'' - from wikipedia.<br />
<br />
The OpenStack I18n team will take responsible for the I18n and L10n of OpenStack. Our work will include:<br />
* Translation of documentations, messages, websites, and etc.<br />
* Translation platform maintenance and enhancements<br />
* I18n test<br />
<br />
= Contributing =<br />
I18n team welcome any kinds of contribution.<br />
<br />
== Contribute to translations ==<br />
If you want to help the translations, firstly you may want to [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&redirect=no become an official translator and join your language team]. Go to [https://translate.openstack.org translation website] to start translation then. You could find the translation jobs in the home page or contact with the coordinators.<br />
<br />
If you cannot find your local team, you can request to [[I18nTeam/CreateLocalTeam|create a local translation team]].<br />
<br />
If you want to report translation errors, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad and report bugs. Mark bugs with a tag "'''translation'''".<br />
<br />
There are three different roles in a translation team.<br />
* [[I18nTeam/Management|Coordinator]]: a privileged member in a translation team who can help in team management tasks, such as approving new members and reviewing contributions to that language. We also have task coordinators for specific tasks.<br />
* [[Documentation/Translation#Contribute_as_a_translator|Member (Translator)]] : a person who can submit translations.<br />
* [[Documentation/Translation#Contribute_as_a_reviewer|Reviewer]]: a person who can proofread translations and mark them as reviewed.<br />
<br />
== Contribute to translation tools ==<br />
Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag "'''tools'''".<br />
<br />
== Fix I18n bugs ==<br />
If you want to help to report or fix I18n bugs of OpenStack, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad. Mark bugs with a tag "'''i18n'''".<br />
<br />
= Getting in touch =<br />
<br />
* Mailing List<br />
** We use [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n@lists.openstack.org] as the mailing list.<br />
* IRC<br />
** We all hang out on #openstack-i18n IRC channel on freenode.<br />
* Team Meeting<br />
** The I18n team meets bi-weekly on Thursdays at alternating times.<br />
** Please see [[Meetings/I18nTeamMeeting]]<br />
<br />
= Local Translation Teams =<br />
Lead: Ying Chun "Daisy" Guo (Daisy on IRC)<br />
<br />
*[[I18nTeam/pt_BR|Portuguese (Brazil)]]<br />
*[[I18nTeam/ca|Catalan]]<br />
*[[I18n/team/zh_cn |Simplified Chinese]]<br />
*[[I18n/team/zh_tw |Traditional Chinese]]<br />
*Czech<br />
*Dutch (Netherlands)<br />
*[[I18nTeam/en_au|English (Australia)]]<br />
*[[I18nTeam/fr|French]]<br />
*German: [[German_Translation_Dictionary|German translation dictionary]]<br />
*[[I18nTeam/hi|Hindi]]<br />
*[[I18nTeam/ja|Japanese]]<br />
*[[I18nTeam/ko_KR|Korean]]<br />
*[[I18nTeam/pl|Polish]]<br />
*[[I18nTeam/pa_IN|Punjabi]]<br />
*[[I18nTeam/ru|Russian]]<br />
*[[I18nTeam/es|Spanish]]<br />
*Vietnamese<br />
*[[I18nTeam/id|Bahasa Indonesia]]<br />
*[[I18nTeam/th|Thai]]<br />
*[[I18nTeam/tr_TR|Turkish]]<br />
* [[i18nTeam/CDACTeam|Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi]]<br />
----<br />
[[category: Horizontal_Team]]<br />
[[Category:I18n]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Translations:I18nTeam/Page_display_title/zh-cn&diff=96142Translations:I18nTeam/Page display title/zh-cn2015-11-10T06:14:40Z<p>Daisy: Created page with "国际化团队"</p>
<hr />
<div>国际化团队</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=95503Meetings/I18nTeamMeeting2015-11-04T11:21:42Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 5th December at 0600 UTC<br />
* Highlights of discussions in Tokyo<br />
* Review: Mitaka plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
==== 20th August ====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
==== 3rd September ====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=95498Meetings/I18nTeamMeeting2015-11-04T09:51:26Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 5th December at 0600 UTC<br />
* Review: Mitaka plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 15th October ====<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
==== 1st October ====<br />
* Open discussions<br />
==== 20th August ====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
==== 3rd September ====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92640Meetings/I18nTeamMeeting2015-10-15T12:48:20Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Discussion: document translation plan (15 minutes)<br />
* Stackalytics (translation activity metrics) : Go Austin! (10 minutes)<br />
* Translation check site (dashboard) (10 minutes )<br />
* Get rid of Openstack projects in transfix.com ? (10 minutes )<br />
* Versioning of installation guide (10 minutes )<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92637Meetings/I18nTeamMeeting2015-10-15T12:43:58Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Discussion: document translation plan<br />
* Stackalytics (translation activity metrics) : Go Austin!<br />
* Translation check site (dashboard)<br />
* Get rid of Openstack projects in transfix.com ?<br />
* Versioning of installation guide<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92636Meetings/I18nTeamMeeting2015-10-15T12:43:38Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Discussion: document translation plan<br />
* Stackalytics (translation activity metrics) : Go Austin!<br />
* translation check site (dashboard)<br />
* get rid of Openstack projects in transfix.com ?<br />
* Versioning of installation guide<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92477Meetings/I18nTeamMeeting2015-10-14T07:08:41Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Discussion: document translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92476Meetings/I18nTeamMeeting2015-10-14T07:04:15Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Review of Liberty translation<br />
* Discussion: document translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92475Meetings/I18nTeamMeeting2015-10-14T07:01:13Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Discussion: document translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92470Meetings/I18nTeamMeeting2015-10-14T05:57:38Z<p>Daisy: /* Next meetings */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 1300 UTC<br />
* Next translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92469Meetings/I18nTeamMeeting2015-10-14T05:56:01Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 0600 UTC<br />
* Next translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ====<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisyhttps://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=92468Meetings/I18nTeamMeeting2015-10-14T05:55:17Z<p>Daisy: /* Agenda for next meeting */</p>
<hr />
<div>[[Category: I18n]]<br />
[[Category: Meetings]]<br />
<br />
= Weekly I18n team meeting =<br />
If you're interested in [[I18nTeam|internationalization]], we hold public meetings on the first and the third Thursdays every month in <code><nowiki>#openstack-meeting</nowiki></code>. <br />
<br />
If you want to attend but the time is not friendly to you, please email to [mailto:guoyingc@cn.ibm.com Daisy].<br />
<br />
* Week 1: 06:00 UTC<br />
** Paris 08:00, Thur<br />
** Warsaw 08:00, Thur<br />
** Moscow 09:00, Thur<br />
** New Delhi 11:30, Thur<br />
** Beijing 14:00, Thur<br />
** Seoul 15:00, Thur<br />
** Tokyo 15:00, Thur<br />
** Vancouver 23:00, Wed<br />
<br />
* Week 3: 13:00 UTC<br />
** Paris 15:00, Thur<br />
** Warsaw 15:00, Thur<br />
** Moscow 16:00, Thur<br />
** New Delhi 18:30, Thur<br />
** Beijing 21:00, Thur<br />
** Seoul 22:00, Thur<br />
** Tokyo 22:00, Thur<br />
** Vancouver 06:00, Thur<br />
<br />
== Agenda for next meeting ==<br />
=== Next meetings ===<br />
Meeting time: Thursday, 15th October at 0600 UTC<br />
* Next translation plan<br />
* Open discussions<br />
<br />
=== Last meetings ===<br />
==== 1st October ===<br />
* Open discussions<br />
===== 20th August =====<br />
Meeting time: Thursday, 20th August at 1300 UTC<br />
* I18n sessions in Tokyo summit<br />
* Open discussions<br />
===== 3rd September =====<br />
Meeting time: Thursday, 3rd September at 0600 UTC<br />
* Zanata status and QA<br />
* Liberty translation plan and QA<br />
* Open discussions<br />
==== 17th September ====<br />
Meeting time: Thursday, 17th September at 1300 UTC<br />
* Collect issues/questions for Zanata and Liberty translation<br />
* Discussion: IBM contributions<br />
* Open discussions<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>Daisy