[Proposal] I18n Contributor Guide doc folder to follow documentation structure
Hello team, I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1]. How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure? With many thanks, /Ian [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migrat... [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
Basically +1. I would like to raise a question whether it makes sense to move all contents to contributor/. Some contents are for the infra and/or i18n admin. They might fit into admin/. The i18n repo is different from other repositories, so the categories of contributor, admin, and user might be different. At least I believe our current contents should be categorized. Thought? 2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello team,
I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1].
How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure?
With many thanks,
/Ian
[1]
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migrat... [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Another question. What is the main motivation behind this proposal? If all contents fit into "contributor", "contributor" directory just will add another extra path. 2018年10月28日(日) 19:27 Akihiro Motoki <amotoki@gmail.com>:
Basically +1. I would like to raise a question whether it makes sense to move all contents to contributor/. Some contents are for the infra and/or i18n admin. They might fit into admin/. The i18n repo is different from other repositories, so the categories of contributor, admin, and user might be different. At least I believe our current contents should be categorized.
Thought?
2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello team,
I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1].
How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure?
With many thanks,
/Ian
[1]
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migrat... [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Yeah, that was also my first reaction. A restructured, more standardized I18n guide would be good. But before we have to define for us, who is user, who is administrator and who is contributor (in the direction of translation or contributor to I18n tools). And nevertheless before that we have to finish the developement of the project doc translation pipelines, that depends mostly on me. kind regards Frank Am 2018-10-28 11:29, schrieb Akihiro Motoki:
Another question. What is the main motivation behind this proposal?
If all contents fit into "contributor", "contributor" directory just will add another extra path.
2018年10月28日(日) 19:27 Akihiro Motoki <amotoki@gmail.com>:
Basically +1. I would like to raise a question whether it makes sense to move all contents to contributor/.
Some contents are for the infra and/or i18n admin. They might fit into admin/. The i18n repo is different from other repositories, so the categories of contributor, admin, and user might be different. At least I believe our current contents should be categorized.
Thought?
2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello team,
I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1].
How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure?
With many thanks,
/Ian
[1]
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migrat...
[2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
My main motivation on this proposal is : I think placing this script: https://review.openstack.org/#/c/613752/ to some repo(s) under I18n team governance would be so great and I want to centralize such a script into openstack/i18n repository currently. I understand that defining each section on the document into admin, user, and contributor would give burden to I18n people, but this might be a good start point to define cores with more fine-grained manner (FYI: http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.2... ). Frank Kloeker wrote on 10/30/2018 4:22 PM:
Yeah, that was also my first reaction. A restructured, more standardized I18n guide would be good. But before we have to define for us, who is user, who is administrator and who is contributor (in the direction of translation or contributor to I18n tools). And nevertheless before that we have to finish the developement of the project doc translation pipelines, that depends mostly on me.
We are the same team - I will try to cooperate with you, and please help I18n team PTL, I18n members :) With many thanks, /Ian
kind regards
Frank
Am 2018-10-28 11:29, schrieb Akihiro Motoki:
Another question. What is the main motivation behind this proposal?
If all contents fit into "contributor", "contributor" directory just will add another extra path.
2018年10月28日(日) 19:27 Akihiro Motoki <amotoki@gmail.com>:
Basically +1. I would like to raise a question whether it makes sense to move all contents to contributor/.
Some contents are for the infra and/or i18n admin. They might fit into admin/. The i18n repo is different from other repositories, so the categories of contributor, admin, and user might be different. At least I believe our current contents should be categorized.
Thought?
2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello team,
I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1].
How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure?
With many thanks,
/Ian
[1]
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migrat...
[2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (3)
-
Akihiro Motoki
-
Frank Kloeker
-
Ian Y. Choi