No objections have been raised.

I edited: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+To+Work+With+CloudStack+Documentation
to make mention of this convention

The patches have been applied by Joe:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=18d7595292f336093e5c586b544d911f5a70ac5d
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=400d29be850cd16ba1fd155dc6bfa78e7a75df27

-Sebastien

On Dec 10, 2012, at 5:00 AM, Kimihiko Kitase wrote:

> +1
> 
> -----Original Message-----
> From: Kelceydamage@bbits [mailto:kel...@bbits.ca] 
> Sent: Saturday, December 08, 2012 2:37 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS][DOCS] Conventions for docbook xml filenames to be 
> ready for translation
> 
> +1 agreed. 
> 
> Sent from my iPhone
> 
> On Dec 7, 2012, at 9:23 AM, sebastien <run...@gmail.com> wrote:
> 
>> Hi,
>> 
>> A few of us have been looking at translation of the documentation using 
>> transifex.
>> To automate the pushing and pulling of source files and translations from 
>> our source code to the transifex site, we need to follow some basic 
>> guidelines for filenames of docbook xml files that we create in /docs/en-US.
>> 
>> I would like use to vote/agree on:
>> 
>> 1-basename needs to be less or equal to 50 characters in length (<=50)
>> 
>> For instance, these files don't follow the proposed convention:
>> loadbalancer-policy-port-forwarding-rule-usage-record-format.xml
>> ongoing-configuration-of-external-firewalls-loadbalancer.xml
>> troubleshooting-dataloss-on-exported-primary-storage.xml
>> troubleshooting-maintenance-mode-not-working-on-vCenter.xml
>> 
>> 2-basename cannot contain dots (no 4.0 in the basename for instance).
>> 
>> For instance, these files don't follow the proposed convention:
>> added-API-commands-4.0.xml
>> Book_Info_Release_Notes_4.0.xml
>> changed-apicommands-4.0.xml
>> 
>> Regards,
>> 
>> PS: assuming nobody objects, I already submitted a review request that 
>> corrects the existing filenames to make us fully "compliant" with transifex.
>> 
>> -Sebastien

Reply via email to