Comment 12 for bug 327259

@Antony, @xrg

"if we refactor some part of the code or introduce new code we SHOULD use
nice and correctly named variables"
-> Well, you might still have a chance to avoid creating yet a new typo /
bad concept for all your future v6 customers that will use your new v6
project_long_term module:
https://bugs.launchpad.net/openobject-addons/+bug/625428

I hope OpenERP SA is aware how important it is to put it all on new release
to avoid introducing new typos that would drag development for years if
missed.

I also emphasis this is very important to have correct English and
conventions in your code on the contrary: don't neglect the seduction factor
(or on the contrary repulsion) your code can have with your developers
community. You are trying to develop in the US, right? How will US engineers
react when they will read childs or datas? Well chances are they would run
away and stick with frameworks that look more appealing on the surface. Look
at the Ruby on Rails success (not a small thing, it's slowly taking over all
the J2EE stack), well a large part of the success is due to the high quality
of the framework + excellent conventions (including naming ones) that
seduced a large community of advanced developers. History also tells us that
many excellent European open source softwares also failed to become
mainstream due to poor English.

2010/11/11 Antony Lesuisse <email address hidden>

> @xrg, @Geoff Gardiner, That is exactly the policy i want enforce:
>
> - User exposed strings MUST be correct english.
> - Variables names are just symbols used by programmers and we wont rename
> them for the sake of it
> - But, if we refactor some part of the code or introduce new code we SHOULD
> use nice and correctly named variables and it is allowed to rename stupid
> varnames.
>
> --
> "Children" not "childs"
> https://bugs.launchpad.net/bugs/327259
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: Confirmed
> Status in OpenObject Web Client: Confirmed
> Status in OpenObject Server: Confirmed
>
> Bug description:
> English is not my mother tongue, so forgive me if I'm wrong, but : very
> often on OpenERP we see "childs" written instead of "children" and that's
> wrong.
> You can find field names, in help texts, and in the documentation.
>
> One problem with that is that our English/American users surely won't find
> it professional looking.
>
> Initially this bug also mentioned spelling errors in the code but now
> that's Bug #673087.
>
>
>
>
>