openerp-brazil-team team mailing list archive
-
openerp-brazil-team team
-
Mailing list archive
-
Message #00078
Fwd: Brazilian Portuguese Localization Project (by Fabien Pinckaers)
Olá Pessoal,
A comunicação realmente é ume excelente forma de esclarecimento. (Again ...
leaving and learning).
Bem, em resposta a minha consulta ao Fabien (OpenERP), ele gentilmente
colocou a disposição uma grande quantidade de informação para nossa
análise.
Eu enviei uma pequena resposta ao Fabien dizendo dos motivos pelo qual parei
de trabalhar no TinyERP no passado (para dar uma satisfação) e coloquei
alguns questionamentos a respeito do fechamento do nosso Projeto (... NÃO DO
TIME...) sugerido por ele. Quando ele responder eu posto neste tópico.
Também questionei sobre a colaboração na tradução usando o Rosetta (online)
o qual eu acho muito lento pelo tempo de refresh de cada página. Aliás vou
colocar aqui em inglês mesmo este trecho da minha resposta (para a
compreensão de vocês sobre a minha crítica) :
... "Regarding translation in Rosetta, I personally think that it is very
hard to translate about 500 or 1000 terms in Rosetta (online). It has a slow
approach. I would like if we had some other way to do it offline. Today I
use to group a lot of .po files (Portuguese-Portugal, Portuguese-Brasil and
even Spanish) in a database for reference and I use KBabel to translate a
new file very fast this way. ..."
É isso aí pessoal, no mais ele forneceu muitas instruções e apontou que em
breve deve fazer um guia sobre contribuições ao projeto.
Eu aguardo vocês processarem esta informação e solicito que discutamos sobre
a melhor forma de contribuição que podemos dar para o projeto.
Um abraço,
--
Joe Bertoli Pimentel
joe.b.pimentel@xxxxxxxxx
---------- Forwarded message ----------
From: Fabien Pinckaers <fp@xxxxxxxxxxx>
Date: Tue, Mar 31, 2009 at 4:42 AM
Subject: Re: Brazilian Portuguese Localization Project
To: Joe Pimentel <joe.b.pimentel@xxxxxxxxx>
Hello,
Thanks for your email.
I was a tinyerp user that has done some work in the past regarding
> translation of TinyERP to Brazilian Portuguese.
> This work has stopped as TinyERP becomes OpenERP.
>
Can you explain me why did you stopped your work when we have renamed Tiny
ERP to Open ERP ?
So, I decided to create the OpenERP Brazilian Portuguese Localization
> (pt_BR) (https://launchpad.net/openerp.pt-br-localiz) and the driver team
> OpenERP Brazil Team (https://launchpad.net/~openerp-brazil-team<https://launchpad.net/%7Eopenerp-brazil-team>)
> - now a 10+ people team.
>
I set your team as driver for pt_BR translations of openobject:
https://translations.launchpad.net/+groups/openobject-translators
We use structured permissions on Launchpad's Rosetta to control quality, it
means:
* Your group can change translations of any term
* Contributor (not in the group) can propose improvements for modifications
and translate directly for untranslated terms
* Propositions of improvements should be reviewed by your team.
For new modules, I think it's better to develop them in addons-extra
directly.
For the developments of modules, I think it's better to integrate them in
the addons-extra branch directly. I added you in the openerp-commiter team
so that you can commit in addons-extra. Tell me if I must add others people.
Our goal is to accept people in commiters once they have developed at least
2 modules.
You can also commit modules in addons-community is you want that everyone
commit in them, not only commiters.
Now we have an repository at our project that looks like a mirror of the
> structure from OpenERP and OpenObject projects to host only the modified
> files. The objective is to control changes done by the team and to have a
> place to share allowing team validation over the work done before we submit
> it to OpenERP Quality Team.
>
It's better to develop directly in addons-extra or addons-community. Doing
too much branch becomes unmanageable. I attach a file that describe on we
would like to work to synchronize efforts. I will prepare a slideshow based
on this file. (it's still in draft and some parts are not working yet)
As a summary:
* Develop directly in addons-community or addons-extra
* Do your own branch only if you don't have commit access (for example if
you plan to change the Open ERP server, which is a branch maintained by the
quality team)
For instance: one of our work in the last month was to translate the some
> of the base and sales (missing translation) terms.
>
These translations must be in Rosetta, not in the modules. We move
periodically all terms in Rosetta's launchpad translation system to Open ERP
modules.
But now we want to know the best way to collaborate with OpenERP by
> translating and developing localizated modules and ask you if we can
> associate our project to OpenERP and OpenObject projects (like other
> localization projects had done).
>
As I said, I think it's better
I will try to finish a clean slideshow based on the attached document by the
end of this week. We will contact contributors one by one after to
re-organise the way to work.
As I said, it's better to not create a project but commit directly in
branches and in launchpad translation's engine. Check if you can do that and
close your project. We use projects for very big new developments, like: Web
Client, Touchscreen Point of Sale, ... We consider that translations or
localisation must be contributions on the main project, not a separate
project. (this can be driven by dedicated teams in launchpad)
Tell me if you have any problem,
Thanks for contacting me,
It seems it's urgent that we publish a good way of working,
--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
Great Achievements Start With Tiny Investments
-- Marty, 2005
Slide Community
===============
Introduction
The Open Object community is full of smart people that
contributes and help others. This document explains how
you can join us, learn new things, and give back when you can.
Table of Content
Get Involved
Join Teams
Learn With Documentations
Manage Translations
Develop Your Modules
Promote Your Contributions
Open Object Organisation
Launchpad (devs)
Code Branches
Bug Tracker
Goals and Milestones
Specifications
Translations
Software
Documentation
Website
Promoting Your Work
Planet
OpenERP.tv
General Organisation
Wiki
Communicating
Forum
Mailing List
IRC - Chat
Learning
***** Learning *****
Get Involved
The fastest way to learn Open ERP is to keep in touch with the
community. We use two channels to organise discussions:
* Forum : http://openobject.com/forum
* IRC : irc://irc.freenode.net/#openobject
The forum is connected to the mailing list, the fastest way to
discuss is to [subscribe to the mailing list].
Learn by Reading
Open ERP has a good documentation, we suggest you to read it.
You can get it on http://doc.openerp.com
If you notice mistakes, unclear topics or typos in the documentation,
you can leave a comment in each section, these comments will be
integrated
by authors in future versions of the documentation.
Keep in Touch with OO
If you want to keep in touch with new features, you should
read the [Open Object planet]. We maintain two planets:
* The [Open ERP planet] is dedicated to commercial announces,
* The [Open Object planet] is open to any contributor and announce.
You can also subscribe to the planet [RSS feed].
***** Join Teams *****
Organisation in Teams
We use teams on launchpad to organise activities and group of
contributors.
We manage several teams:
* Developers: community, commiter, quality
* Experts:
* Translators: [...]
You can join a team after having [created an account] on launchpad.
Developer Teams
Developments are managed by three teams:
* [Quality Team] : they have direct access to the stable/official branch,
* [Open ERP Commiters] : developers that can commit in addons-extra
modules,
* [Open ERP Community] : open access to every one, to work on shared
branches.
We use a meritocracy system where the quality team approve new commiters.
You can apply to join the commiter group after having published some
modules on launchpad.
Expert Teams
Experts are people having a great knowledge in some management area. You
can assign a bug or a blueprint (specification) to an expert team if you
need feedback. Please don't contact them for questions, most of the
members
are managers with only a few spare time.
* Team 1
* Team 2
* Team 2
Translator Teams
Quality of the translations are managed by [translation teams |
https://translations.launchpad.net/+groups/openobject-translators]
with a contribution reviewing process. You can join a team.
If you want to create a new team for a new language, create a team on
Launchpad and contact the [quality team] to be responsible of this
language.
Normal contributors can suggest improvements, members
of the translation teams can change the translated values.
***** Read Documentations *****
The main documentation website is http://doc.openerp.com. This
documentation
is built using RST and [Sphinx]. The sources used to produce this website
are
on bazaar. To download them:
bzr branch lp:openobject-doc
To contribute, commit your modification into this branch directly. To do
this, you must be in the openerp-community team. The documentation
website
is rebuilt every night.
We also use [Launchpad's Answers] for the FAQ.
***** Manage Translations *****
Open ERP Translation
Translations of the software are organised on launchpad, by modules:
https://translations.launchpad.net/openobject
[translation.png]
Open ERP Translation
Translate on launchpad and export your translation from Launchpad.
Avoid translating in Open ERP directly, it's more complex for
contributions
and future maintenance.
[translation_screenshot.png]
Website Translation
If you want to help us to translate the OpenERP.com website, please
contact
fp AT openerp.com
Documentation Translations
All our translated versions of the documentation are in the
lp:openobject-doc
project. Our tools to manage translations of the documentations are also
in
this branch.
These tools manage translated versions based on the english one. If the
english
documentation changes, we just have to retranslate paragraphs that
changed to
resynchronize translations.
To rebuild translated versions:
XXXX.YYYY.sh
***** Develop Your Modules *****
Using Bazaar
We use the distributed version control system [Bazaar] to manage
developments
on Open ERP.
We suggest you to read the [bazaar
tutorial|http://doc.bazaar-vcs.org/bzr.dev/en/mini-tutorial/index.html]
before developping on Open ERP. On Windows, you can use the [TortoiseBzr]
GUI.
We strongly suggest every contributor to host all your developments on
the
launchpad infrastructure to easily collaborate and share.
Developing Modules
If you plan to develop new features, develop them as Open ERP modules. If
you
are a contributor, commit your modules in this branch:
[lp:~openerp-commiter/openobject-addons/trunk-extra-addons]
If you are not a commiter, you should develop in this branch:
[lp:~openerp-community/openobject-addons/trunk-addons-community]
The current development branch is called trunk. But you can also commit
on a specific version of Open ERP like 5.0. To commit on Launchpad, you
must [create an account], join the [community team] and [upload your ssh
public key].
Contributing in the kernel
If you want to propose improvements in the kernel, do your own branch of
the
server or the clients, push it to launchpad and activate "Propose for
merging"
in your branch definition on the launchpad web interface.
The quality team will review your work and merge your branch if your
proposition is clean.
Branches Management
All developments must be done DIRECTLY in the official branches, avoid
doing
branches for your contributions, it's unmanageable:
* Server: lp:openobject-server
* GTK Client: lp:openobject-client
* Web Client: lp:openobject-client-web
* Main Addons: lp:openobject-addons
* Extra Addons: lp:~openerp-commiter/openobject-addons/trunk-extra-addons
* Community Addons:
lp:~openerp-commiter/openobject-addons/trunk-addons-community
Do branches only if:
* You want to experiment new things without breaking the main branch
* You don't have write access to the branch ou plan to modify (propose
for merging after)
Example: Commiters
Members of the commiter team should develop their modules directly in
the branch [addons-extra]. So that we have a central repository of all
current efforts.
If they plan to change the core of Open Object (server, client, main
addons),
they can branch the main branch and do a proposal for merging once the
work
is done.
Example: Community
New contributors should develop their modules directly in the branch
[addons-commmunity]. After having proved they can develop on Open ERP,
they
can apply to join the commiter team.
Modules may evolves from community-addons to commiter-addons once we
start
doing professional maintenance on the module. (on new versions)
Specifications of new features
To describe specification of new features, we use [launchpad's
blueprints].
Use it if you want to clearly describe big changes to apply on Open ERP.
Blueprints and wishlists are planified versions after versions (goals).
Series and Milestones
We create series for each version of Open ERP: 4.2, 5.0, 5.2. We also use
a
serie called trunk for the current development branch. A serie can have
several
milestones: June 2008, July 2009, 5.0-RC1, 5.0-RC2. We create minimum one
milestone every month.
All new developments are applied in the trunk serie. On stable series
(those with
a number), we can only apply bugfixes.
Bugs, blueprints and wishlists are assigned to different series for the
planification
of improvements in Open ERP. (goals)
Bug Tracker
We use the [launchpad's bugtracker] to manage bugs and features requests.
Features requests are bugs tagged as wishlist.
All bugfixes must be applied in the current stable version of Open ERP.
We
merge bugfixes from the stable branch to the trunk one.
New features must always be applied in the trunk branch, not in the
stable
one. (exception for dedicated modules).
Doing Quality
lerem estas
To develop quality modules, you should be aware of the [development
guidelines].
You can also use the base_module_quality module to test your module.
***** Promoting Your Developments *****
Communicate Yourself
To promote your work, you should create a personnal blog and subscribe it
on the [Open Object planet]. To subscribe your blog, send an email to
nva AT openerp.com. Then, write blog entries and tag them with
"openobject"
label. They will appear on the planet automatically.
We suggest you to not only communicate on finished modules but also in
your
plans to develop new modules. This can lead ideas and contributions from
the community for your module.
You can also announce new modules in the forum.
Generate Module Documentation
To generate the documentation of your module, you can use the module
called
base_module_doc_rst. It generates the .rst files to be included in the
documentation, based on the content of your __terp__.py file and module.
Communication on Open ERP
Every week, we will select the best blogs on Open Object and push them to
the Open ERP planet and newsletter.
Slide Community
===============
Introduction
The Open Object community is full of smart people that
contributes and help others. This document explains how
you can join us, learn new things, and give back when you can.
Table of Content
Get Involved
Join Teams
Learn With Documentations
Manage Translations
Develop Your Modules
Promote Your Contributions
Open Object Organisation
Launchpad (devs)
Code Branches
Bug Tracker
Goals and Milestones
Specifications
Translations
Software
Documentation
Website
Promoting Your Work
Planet
OpenERP.tv
General Organisation
Wiki
Communicating
Forum
Mailing List
IRC - Chat
Learning
***** Learning *****
Get Involved
The fastest way to learn Open ERP is to keep in touch with the
community. We use two channels to organise discussions:
* Forum : http://openobject.com/forum
* IRC : irc://irc.freenode.net/#openobject
The forum is connected to the mailing list, the fastest way to
discuss is to [subscribe to the mailing list].
Learn by Reading
Open ERP has a good documentation, we suggest you to read it.
You can get it on http://doc.openerp.com
If you notice mistakes, unclear topics or typos in the documentation,
you can leave a comment in each section, these comments will be integrated
by authors in future versions of the documentation.
Keep in Touch with OO
If you want to keep in touch with new features, you should
read the [Open Object planet]. We maintain two planets:
* The [Open ERP planet] is dedicated to commercial announces,
* The [Open Object planet] is open to any contributor and announce.
You can also subscribe to the planet [RSS feed].
***** Join Teams *****
Organisation in Teams
We use teams on launchpad to organise activities and group of contributors.
We manage several teams:
* Developers: community, commiter, quality
* Experts:
* Translators: [...]
You can join a team after having [created an account] on launchpad.
Developer Teams
Developments are managed by three teams:
* [Quality Team] : they have direct access to the stable/official branch,
* [Open ERP Commiters] : developers that can commit in addons-extra modules,
* [Open ERP Community] : open access to every one, to work on shared branches.
We use a meritocracy system where the quality team approve new commiters.
You can apply to join the commiter group after having published some
modules on launchpad.
Expert Teams
Experts are people having a great knowledge in some management area. You
can assign a bug or a blueprint (specification) to an expert team if you
need feedback. Please don't contact them for questions, most of the members
are managers with only a few spare time.
* Team 1
* Team 2
* Team 2
Translator Teams
Quality of the translations are managed by [translation teams | https://translations.launchpad.net/+groups/openobject-translators]
with a contribution reviewing process. You can join a team.
If you want to create a new team for a new language, create a team on
Launchpad and contact the [quality team] to be responsible of this
language.
Normal contributors can suggest improvements, members
of the translation teams can change the translated values.
***** Read Documentations *****
The main documentation website is http://doc.openerp.com. This documentation
is built using RST and [Sphinx]. The sources used to produce this website are
on bazaar. To download them:
bzr branch lp:openobject-doc
To contribute, commit your modification into this branch directly. To do
this, you must be in the openerp-community team. The documentation website
is rebuilt every night.
We also use [Launchpad's Answers] for the FAQ.
***** Manage Translations *****
Open ERP Translation
Translations of the software are organised on launchpad, by modules:
https://translations.launchpad.net/openobject
[translation.png]
Open ERP Translation
Translate on launchpad and export your translation from Launchpad.
Avoid translating in Open ERP directly, it's more complex for contributions
and future maintenance.
[translation_screenshot.png]
Website Translation
If you want to help us to translate the OpenERP.com website, please contact
fp AT openerp.com
Documentation Translations
All our translated versions of the documentation are in the lp:openobject-doc
project. Our tools to manage translations of the documentations are also in
this branch.
These tools manage translated versions based on the english one. If the english
documentation changes, we just have to retranslate paragraphs that changed to
resynchronize translations.
To rebuild translated versions:
XXXX.YYYY.sh
***** Develop Your Modules *****
Using Bazaar
We use the distributed version control system [Bazaar] to manage developments
on Open ERP.
We suggest you to read the [bazaar
tutorial|http://doc.bazaar-vcs.org/bzr.dev/en/mini-tutorial/index.html]
before developping on Open ERP. On Windows, you can use the [TortoiseBzr] GUI.
We strongly suggest every contributor to host all your developments on the
launchpad infrastructure to easily collaborate and share.
Developing Modules
If you plan to develop new features, develop them as Open ERP modules. If you
are a contributor, commit your modules in this branch:
[lp:~openerp-commiter/openobject-addons/trunk-extra-addons]
If you are not a commiter, you should develop in this branch:
[lp:~openerp-community/openobject-addons/trunk-addons-community]
The current development branch is called trunk. But you can also commit
on a specific version of Open ERP like 5.0. To commit on Launchpad, you
must [create an account], join the [community team] and [upload your ssh
public key].
Contributing in the kernel
If you want to propose improvements in the kernel, do your own branch of the
server or the clients, push it to launchpad and activate "Propose for merging"
in your branch definition on the launchpad web interface.
The quality team will review your work and merge your branch if your
proposition is clean.
Branches Management
All developments must be done DIRECTLY in the official branches, avoid doing
branches for your contributions, it's unmanageable:
* Server: lp:openobject-server
* GTK Client: lp:openobject-client
* Web Client: lp:openobject-client-web
* Main Addons: lp:openobject-addons
* Extra Addons: lp:~openerp-commiter/openobject-addons/trunk-extra-addons
* Community Addons: lp:~openerp-commiter/openobject-addons/trunk-addons-community
Do branches only if:
* You want to experiment new things without breaking the main branch
* You don't have write access to the branch ou plan to modify (propose for merging after)
Example: Commiters
Members of the commiter team should develop their modules directly in
the branch [addons-extra]. So that we have a central repository of all
current efforts.
If they plan to change the core of Open Object (server, client, main addons),
they can branch the main branch and do a proposal for merging once the work
is done.
Example: Community
New contributors should develop their modules directly in the branch
[addons-commmunity]. After having proved they can develop on Open ERP, they
can apply to join the commiter team.
Modules may evolves from community-addons to commiter-addons once we start
doing professional maintenance on the module. (on new versions)
Specifications of new features
To describe specification of new features, we use [launchpad's blueprints].
Use it if you want to clearly describe big changes to apply on Open ERP.
Blueprints and wishlists are planified versions after versions (goals).
Series and Milestones
We create series for each version of Open ERP: 4.2, 5.0, 5.2. We also use a
serie called trunk for the current development branch. A serie can have several
milestones: June 2008, July 2009, 5.0-RC1, 5.0-RC2. We create minimum one
milestone every month.
All new developments are applied in the trunk serie. On stable series (those with
a number), we can only apply bugfixes.
Bugs, blueprints and wishlists are assigned to different series for the planification
of improvements in Open ERP. (goals)
Bug Tracker
We use the [launchpad's bugtracker] to manage bugs and features requests.
Features requests are bugs tagged as wishlist.
All bugfixes must be applied in the current stable version of Open ERP. We
merge bugfixes from the stable branch to the trunk one.
New features must always be applied in the trunk branch, not in the stable
one. (exception for dedicated modules).
Doing Quality
To develop quality modules, you should be aware of the [development guidelines].
You can also use the base_module_quality module to test your module.
***** Promoting Your Developments *****
Communicate Yourself
To promote your work, you should create a personnal blog and subscribe it
on the [Open Object planet]. To subscribe your blog, send an email to
nva AT openerp.com. Then, write blog entries and tag them with "openobject"
label. They will appear on the planet automatically.
We suggest you to not only communicate on finished modules but also in your
plans to develop new modules. This can lead ideas and contributions from
the community for your module.
You can also announce new modules in the forum.
Generate Module Documentation
To generate the documentation of your module, you can use the module called
base_module_doc_rst. It generates the .rst files to be included in the
documentation, based on the content of your __terp__.py file and module.
Communication on Open ERP
Every week, we will select the best blogs on Open Object and push them to
the Open ERP planet and newsletter.
Follow ups
