Dolibarr ERP CRM Wiki - User contributions [en]

BrasilTaxes

2015-11-18T14:35:32Z

Saxa: /* Products */

= Taxes in Brasil =

Work In Progress

See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm

* The information here may be not 100% correct, or it may not work on 100% of the cases. I wrote this according to my experience based on real life situations.

== Taxes on product sales ==

All products sold in Brasil usually have the following taxes applied.

* Federal taxes
II - Import duties , applied in case of an imported product.
IPI - Tax on Industrialized products
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* State taxes
ICMS - It is a equivalent of the VAT in Europe or TAX in USA. But its calculated included in the price.
ICMS-ST - This is a tax applied when you sell from state to state.

== Taxes on service sales ==

* Federal taxes
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* Municipal taxes
ISS - Tax on services

== How it works ==

=== Products ===
Usually a product is classified according to the NCM number, which is a Common number used for tax rates and based of the Harmony System with the first four digits. NCM means Common Nomenclature of MERCOSUL. This number defines the rate of taxes used on a certain product, it defines if it has Import Duties and
values for other taxes. You can find the NCM number on the following site:

www4 receita fazenda gob br /simulador

Accessing this site you put in the NCM number the number of yuor product and you will get in return the values of each tax applied to that product.

Example:
NCM 8431.49.29 - Spare parts for heavy construction machines.
II = 0 %
IPI = 5 %
PIS = 2,10 %
COFINS = 15,37 %

The calculation will be based on a USD.100,00 value. The base of all the imported products is the value of the product + the freight cost up to the Brasilian port. We will suppose that the above mentioned value have already the freight included and it is CIF destination port.

USD / BRL ratio as of writing is 1 USD = 3,8336 BRL which gives us the following values:

USD 100 = BRL 383,36 as base.
II = 0 % = 0,00 BRL
IPI = 5 % = 19,17 BRL
PIS = 2,10 % = 8,05 BRL
COFINS = 15,37 % = 58,92 BRL

It gives us a total of federal taxes of BRL 86,14 , which have to be summed to the BRL 383,36.

State taxes are applied over the base value with the federal taxes. This results in a BRL 469,50 as base, on which
we have to apply the 17% of ICMS tax for the Bahia state.

BRL 469,50 x 17% = BRL 79,815

This gives us a total of BRL 549,315 as a total of the product.

=== Services ===

BrasilTaxes

2015-11-18T14:34:40Z

Saxa: /* Products */

= Taxes in Brasil =

Work In Progress

See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm

* The information here may be not 100% correct, or it may not work on 100% of the cases. I wrote this according to my experience based on real life situations.

== Taxes on product sales ==

All products sold in Brasil usually have the following taxes applied.

* Federal taxes
II - Import duties , applied in case of an imported product.
IPI - Tax on Industrialized products
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* State taxes
ICMS - It is a equivalent of the VAT in Europe or TAX in USA. But its calculated included in the price.
ICMS-ST - This is a tax applied when you sell from state to state.

== Taxes on service sales ==

* Federal taxes
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* Municipal taxes
ISS - Tax on services

== How it works ==

=== Products ===
Usually a product is classified according to the NCM number, which is a Common number used for tax rates and based of the Harmony System with the first four digits. NCM means Common Nomenclature of MERCOSUL. This number defines the rate of taxes used on a certain product, it defines if it has Import Duties and
values for other taxes. You can find the NCM number on the following site:

www4 receita fazenda gob br /simulador

Accessing this site you put in the NCM number the number of yuor product and you will get in return the values of each tax applied to that product.

Example:
NCM 8431.49.29 - Spare parts for heavy construction machines.

II = 0 %
IPI = 5 %
PIS = 2,10 %
COFINS = 15,37 %

The calculation will be based on a USD.100,00 value. The base of all the imported products is the value of the product + the freight cost up to the Brasilian port. We will suppose that the above mentioned value have already the freight included and it is CIF destination port.

USD / BRL ratio as of writing is 1 USD = 3,8336 BRL which gives us the following values:

USD 100 = BRL 383,36 as base.
II = 0 % = 0,00 BRL
IPI = 5 % = 19,17 BRL
PIS = 2,10 % = 8,05 BRL
COFINS = 15,37 % = 58,92 BRL

It gives us a total of federal taxes of BRL 86,14 , which have to be summed to the BRL 383,36.

State taxes are applied over the base value with the federal taxes. This results in a BRL 469,50 as base, on which
we have to apply the 17% of ICMS tax for the Bahia state.

BRL 469,50 x 17% = BRL 79,815

This gives us a total of BRL 549,315 as a total of the product.

=== Services ===

BrasilTaxes

2015-11-18T14:18:18Z

Saxa:

= Taxes in Brasil =

Work In Progress

See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm

* The information here may be not 100% correct, or it may not work on 100% of the cases. I wrote this according to my experience based on real life situations.

== Taxes on product sales ==

All products sold in Brasil usually have the following taxes applied.

* Federal taxes
II - Import duties , applied in case of an imported product.
IPI - Tax on Industrialized products
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* State taxes
ICMS - It is a equivalent of the VAT in Europe or TAX in USA. But its calculated included in the price.
ICMS-ST - This is a tax applied when you sell from state to state.

== Taxes on service sales ==

* Federal taxes
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* Municipal taxes
ISS - Tax on services

== How it works ==

=== Products ===
Usually a product is classified according to the NCM number, which is a Common number used for tax rates and based of the Harmony System with the first four digits. NCM means Common Nomenclature of MERCOSUL. This number defines the rate of taxes used on a certain product, it defines if it has Import Duties and
values for other taxes. You can find the NCM number on the following site:

www4 receita fazenda gob br /simulador

Accessing this site you put in the NCM number the number of yuor product and you will get in return the values of each tax applied to that product.

Example: 8431.49.29 - Spare parts for heavy construction machines.

II = 0 %
IPI = 5 %
PIS = 2,10 %
COFINS = 15,37 %

The calculation will be based on a USD.100,00 value. The base of all the imported products is the value of the product + the freight cost up to the Brasilian port. We will suppose that the above mentioned value have already the freight included and it is CIF destination port.

USD / BRL ratio as of writing is 1 USD = 3,8336 BRL which gives us the following values:

USD 100 = BRL 383,36 as base.
II = 0 % = 0,00 BRL
IPI = 5 % = 19,17 BRL
PIS = 2,10 % = 8,05 BRL
COFINS = 15,37 % = 58,92 BRL

It gives us a total of federal taxes of BRL 86,14 , which have to be summed to the BRL 383,36.

State taxes are applied over the base value with the federal taxes. This results in a BRL 469,50 as base, on which
we have to apply the 17% of ICMS tax for the Bahia state.

BRL 469,50 x 17% = BRL 79,815

This gives us a total of BRL 549,315 as a total of the product.

=== Services ===

BrasilTaxes

2015-11-18T13:59:16Z

Saxa:

= Taxes in Brasil = WIP

See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm

* The information here may be not 100% correct, or it may not work on 100% of the cases. I wrote this according to my experience based on real life situations.

== Taxes on product sales ==

All products sold in Brasil usually have the following taxes applied.

* Federal taxes
II - Import duties , applied in case of an imported product.
IPI - Tax on Industrialized products
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* State taxes
ICMS - It is a equivalent of the VAT in Europe or TAX in USA. But its calculated included in the price.
ICMS-ST - This is a tax applied when you sell from state to state.

== Taxes on service sales ==

* Federal taxes
PIS - Social Integration Program tax.
COFINS - Contribution for financement of Social Security.

* Municipal taxes
ISS - Tax on services

BrasilTaxes

2015-11-18T13:21:42Z

Saxa: Created page with "== Taxes in Brasil == See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm"

== Taxes in Brasil ==

See this page for the listing of all the taxes which exist in Brasil: www dot senado dot gov dot br/noticias/jornal/cidadania/impostos/not03.htm

List of modules id

2015-10-10T02:56:53Z

Saxa:

[[Category:Core]]
{{TemplateDocDevEn}}
{{TemplateDocDevEs}}
{{TemplateDocDevFr}}

{{Flag en}} This page list all reserved modules numbers / ID. If you build or want to build your own modules (like this [[:Category:Complementary_modules|complementary module]]), you should take an ID range here.

{{Flag fr}} Cette page recense tous les numéros / ID réservés de modules. Si vous avez réalisé ou voulez réaliser vos propres modules (comme les [[:Category:Modules complémentaires|modules complémentaires suivant]]), vous devriez prendre une plage d'ID ici.

{{Flag sp}} Esta página contiene un listado de todos los id reservados para los módulos. Si ha creado o quiere realizar sus propios módulos, (como estos [[:Category:Módulos_complementarios|módulos complementarios]]), deberá reservarse un rango de ID aquí.

= ID 0 - 99999 =
{{Flag en}} Reserved for Dolibarr's internal modules.

{{Flag fr}} Réservé aux modules internes de Dolibarr.

{{Flag sp}} Reservado a los módulos internos de Dolibarr.

= ID 100000 - 499999 =
{{Flag en}} Reserved area for editors in need for an ID range. You can edit this page to add your own range (limited to 1000 values per editor)

{{Flag fr}} Zone réservé aux éditeurs qui ont besoin d'une plage d'ID spécifiques. Vous pouvez modifier cette page pour réserver votre plage (limité à 1000 valeurs par éditeur)

{{Flag sp}} Área reservada para los partners que necesiten un rango de ID. Puede modificar esta página para reservar su rango (limitado a 1000 valores por editor)

* ID 100000 - 100999: OpenThink (http://www.openthink.be)
* ID 101000 - 101999: NLTechno (http://www.nltechno.com)
* ID 102000 - 102999: Tiaris (http://www.tiaris.fr)
* ID 103000 - 103999: Open-concept.pro (http://www.open-concept.pro)
* ID 104000 - 104999: ATM Consulting (http://www.atm-consulting.fr)
* ID 105000 - 105999: GPC.solutions
* ID 106000 - 106999: PHPASSO
* ID 107000 - 107999: TecLib (http://www.teclib.com) / Auguria (http://www.auguria.net)
* ID 108000 - 108999: ETHICWEB
* ID 109000 - 109999: Aplose
* ID 110000 - 110999: Aternatik
* ID 111000 - 111999: Asset IT (www.assetit.ch)
* ID 112000 - 112999: Aarboard AG (www.aarboard.ch)
* ID 113000 - 113999: Alexandre Spangaro
* ID 114000 - 114999: Iceleaf OÜ
* ID 115000 - 115999: 2A2C Conseil - Cyril ZEKSER
* ID 116000 - 116999: *********** Free, put your name to reserve
* ID 117000 - 117999: *********** Free, put your name to reserve
* ID 118000 - 118999: *********** Free, put your name to reserve
* ID 119000 - 119999: Manuel Berrocal - Absolacom
* ID 120000 - 120999: Régis Houssin (http://www.inodbox.com)
* ID 130000 - 130999: Technicks ICT (http://www.technicks.eu)
* ID 140000 - 140999: Altairis
* ID 150000 - 150999: Jeffinfo
* ID 160000 - 160999: Charles-François BENKE (http://www.patas-monkey.com)
* ID 190000 - 190999: Diciannove (http://19.coop)
* ID 199000 - 199999: RFMS
* ID 200000 - 200999: Noxiome
* ID 201000 - 201999: Sasa Ostrouska (saxa)
* ID 202000 - 202999: *********** Free, put your name to reserve
* ID 203000 - 203999: *********** Free, put your name to reserve
* ID 204000 - 204999: *********** Free, put your name to reserve
* ID 205000 - 205999: Kreiz IT
* ID 300000 - 300999: AtooNet (http://www.atoo-net.com)
* ID 400000 - 400999: 2byte.es (http://www.2byte.es)
* ID 401000 - 401999: B&D Informática
* ID 402000 - 402999: Marcos García de La Fuente (marcosgdf)
* ID 403000 - 403999: Sergibyte (http://www.sergibyte.com)
* ID 404000 - 404999: Aikhan
* ID 405000 - 405999: AIME (http://www.aime.mx)
* ID 420000 - 420099: BBS Concept

= ID > 500000 =
{{Flag en}} If you don't already have reserved ids and need some, please don't use hazardous number and use a number higher than 500000, but it is better to ask a wiki account, and reserve your own range by editing the 100000 - 499999 range (1000 ids maximum per partner).

{{Flag fr}} Si vous n'avez pas de numéros réservés et en avez besoin, n'utilisez pas de chiffres au hasard et utilisez une valeur supérieure à 500000, toutefois, il est préférable d'obtenir un compte wiki, et réserver vous-même votre plage en ajoutant votre entrée dans la zone 100000 - 499999 (pas plus de 1000 numéros par partenaire).

{{Flag sp}} Si no dispone de número reservado y necesita, no use cifras redondeadas y usa un valor superior a 500000. Si tiene una cuenta wiki, puede reservarse usted mismo sus id añadiendo su entrada en la zona 100000 - 499999 (no más de 1000 id por partner).

ReleaseProcess

2014-12-23T18:05:49Z

Saxa: /* Archives */

= Dolibarr release process =

This document is a '''draft'''.

The intention is to document what needs to be done to release Dolibarr.

RD: ''I intend to use it as a base to revamp the whole releasing process.''

== Officialy maintained ==

=== Descriptor ===

* [http://pad.asp-software.org Portable Application Description]

=== Archives ===

* Gziped tar archive

''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''

''SO: In my opinion it would be even better if we could use .tar.xz''

* Zipped archive

RD: ''I'd build it from the tarball''

=== Distribution packages ===

RD: ''I'd make these from the release tarball.''

==== RPM ====

RD: ''Can't all of these be unified?''

LD: ''This is what Generic below is for but specific versions are needed for distro integration''

RD: ''I think that Debian integration is ongoing, what about other distros?''

''Isn't this the distribution package maintainer responsibility, not the release managers?''

* Generic
* Fedora

RD: ''RedHat?''

* Mandriva

RD: ''Is this really needed? I mean who still uses mandriva these days?''

* OpenSuse

==== DEB ====

* Debian

RD: ''Ubuntu?''

=== Installers ===

* Windows (DoliWamp, exe)

RD: ''This one is the most involved. We need a better spec of the process.''

== '''Not''' officially maintained ==

RD: ''Need volunteers?''

These packages are not officially maintained but are in the source tree. Maybe we'd want to have them work one day or another.

* [http://www.apsstandard.org APS]
* MacOS X installer (DoliMamp, dmg)
* [https://github.com/edumbill/doap/wiki DOAP]

RD: ''Is this even a package format?''

* Doxygen (Developer documentation)

RD: ''Again, not a package format, but this should certainly be published somewhere for each released version''

* Launchpad (https://launchpad.net/dolibarr)

RD: ''Ubuntu packages and build system?''

* Live CD

RD: ''Really? What for? Demos? Looks overkill''

* [https://build.opensuse.org/project/show/Application:ERP:Dolibarr OpenSuse build system]

RD: ''This one is pretty cool. Looks like we could leverage its capabilities to automate the builds of our Linux distribution packages.'' ''Credentials needed''

* Virtualmin installer
* Proxmox Appliance

== Tentative process ==

=== Early announcement ===

# Post to dolibarr-dev intention to package. Ask testers to test. Ask translators to update their translations. Fix release date allowing at least ''one'' week for people to do their tasks.

=== Building ===

# Update version numbers in source code, ChangeLog and PAD files
# Commit and Tag version

RD: ''Better be a [http://git-scm.com/book/en/Git-Basics-Tagging#Signed-Tags signed tag]''

<ol start="3" style="list-style-type: decimal;">
<li>Checkout tag to a test directory</li>
<li>Play unit tests</li>
<li>Play UI tests</li></ol>

If all is OK

<ol start="6" style="list-style-type: decimal;">
<li>Checkout tag to a build directory</li>
<li>Clean build directory (i.e. remove stuff that won't go into release. Includes devolopment tools, samples, test results, git repo itself, etc.)</li>
<li>Fix rights</li>
<li>TAR reference release</li></ol>

RD: ''We should also generate checksums''

RD: ''Add a GPG signature?''

<ol start="10" style="list-style-type: decimal;">
<li>ZIP release</li>
<li>RPM releases</li>
<li>DEB realease</li>
<li>Windows installer release</li></ol>

=== Testing ===

* ?

=== Pushing ===

# Tag to central repository

RD: ''Credentials needed. This won't get along with a pull request!''

<ol start="2" style="list-style-type: decimal;">
<li>Packages, Artifacts (Checksum(s), signature(s)…), ChangeLog and PAD files to dolibarr.org (/home/dolibarr/wwwroot/files)</li></ol>

RD: ''Credentials needed''

<ol start="3" style="list-style-type: decimal;">
<li>Packages to [http://sourceforge.net/projects/dolibarr/ Sourceforge.net]</li></ol>

RD: ''Credentials needed''

RD: ''Can be automated: [https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download doc]''

=== Verifiing ===

* ?

RD: ''This is where checksums comes in handy''

=== Releasing ===

# Craft announcement message

RD: ''The message template should be in the repo''

<ol start="2" style="list-style-type: decimal;">
<li>Post announcement as a news on dolibarr.org</li></ol>

RD: ''Credentials needed''

<ol start="2" style="list-style-type: decimal;">
<li>Send announcement on Social Networks</li></ol>

* [https://plus.google.com/+DolibarrOrg Google+]
* [http://www.twitter.com/dolibarr Twitter]
* [http://www.facebook.com/dolibarr Facebook]

RD: ''Credentials needed''

RD: ''Should all be automated through their respective APIs''

<ol start="3" style="list-style-type: decimal;">
<li>Send announcement on Mailing lists</li></ol>

dolibarr-user, dolibarr-dev, dolibarr-foundation

<ol start="4" style="list-style-type: decimal;">
<li>Send announcement on Forum</li></ol>

RD: ''This should be a sticky in the appropriate category (which?)''

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version on this wiki</li></ol>

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version in [http://doliforge.org Doliforge]</li></ol>

RD: ''Credentials needed''

== Misc. Questions ==

===RD===
* More projects are moving to tar.xz releases, shan't we join the boat?
* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.
LD: More then 80% of users prefer to use installer, and 60% of dowload are for wamp installer, so we must keep native distribution packages.
* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's
* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]
* Is there other announcements to be made?
* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?
LD: No, it would be better to have only php tools.

== Misc. Notes ==

* Directory structure for resulting binaries should be:
<pre>.
├── generic
├── package_aps
├── package_debian-ubuntu
├── package_mac
├── package_rpm_generic
├── package_rpm_mandriva
├── package_rpm_opensuse
├── package_rpm_redhat-fedora
└── package_windows
</pre>
* We need to define the versionning and naming conventions as well as the branching system

ReleaseProcess

2014-12-23T18:05:27Z

Saxa: /* Archives */

= Dolibarr release process =

This document is a '''draft'''.

The intention is to document what needs to be done to release Dolibarr.

RD: ''I intend to use it as a base to revamp the whole releasing process.''

== Officialy maintained ==

=== Descriptor ===

* [http://pad.asp-software.org Portable Application Description]

=== Archives ===

* Gziped tar archive

''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''
''SO: In my opinion it would be even better if we could use .tar.xz''

* Zipped archive

RD: ''I'd build it from the tarball''

=== Distribution packages ===

RD: ''I'd make these from the release tarball.''

==== RPM ====

RD: ''Can't all of these be unified?''

LD: ''This is what Generic below is for but specific versions are needed for distro integration''

RD: ''I think that Debian integration is ongoing, what about other distros?''

''Isn't this the distribution package maintainer responsibility, not the release managers?''

* Generic
* Fedora

RD: ''RedHat?''

* Mandriva

RD: ''Is this really needed? I mean who still uses mandriva these days?''

* OpenSuse

==== DEB ====

* Debian

RD: ''Ubuntu?''

=== Installers ===

* Windows (DoliWamp, exe)

RD: ''This one is the most involved. We need a better spec of the process.''

== '''Not''' officially maintained ==

RD: ''Need volunteers?''

These packages are not officially maintained but are in the source tree. Maybe we'd want to have them work one day or another.

* [http://www.apsstandard.org APS]
* MacOS X installer (DoliMamp, dmg)
* [https://github.com/edumbill/doap/wiki DOAP]

RD: ''Is this even a package format?''

* Doxygen (Developer documentation)

RD: ''Again, not a package format, but this should certainly be published somewhere for each released version''

* Launchpad (https://launchpad.net/dolibarr)

RD: ''Ubuntu packages and build system?''

* Live CD

RD: ''Really? What for? Demos? Looks overkill''

* [https://build.opensuse.org/project/show/Application:ERP:Dolibarr OpenSuse build system]

RD: ''This one is pretty cool. Looks like we could leverage its capabilities to automate the builds of our Linux distribution packages.'' ''Credentials needed''

* Virtualmin installer
* Proxmox Appliance

== Tentative process ==

=== Early announcement ===

# Post to dolibarr-dev intention to package. Ask testers to test. Ask translators to update their translations. Fix release date allowing at least ''one'' week for people to do their tasks.

=== Building ===

# Update version numbers in source code, ChangeLog and PAD files
# Commit and Tag version

RD: ''Better be a [http://git-scm.com/book/en/Git-Basics-Tagging#Signed-Tags signed tag]''

<ol start="3" style="list-style-type: decimal;">
<li>Checkout tag to a test directory</li>
<li>Play unit tests</li>
<li>Play UI tests</li></ol>

If all is OK

<ol start="6" style="list-style-type: decimal;">
<li>Checkout tag to a build directory</li>
<li>Clean build directory (i.e. remove stuff that won't go into release. Includes devolopment tools, samples, test results, git repo itself, etc.)</li>
<li>Fix rights</li>
<li>TAR reference release</li></ol>

RD: ''We should also generate checksums''

RD: ''Add a GPG signature?''

<ol start="10" style="list-style-type: decimal;">
<li>ZIP release</li>
<li>RPM releases</li>
<li>DEB realease</li>
<li>Windows installer release</li></ol>

=== Testing ===

* ?

=== Pushing ===

# Tag to central repository

RD: ''Credentials needed. This won't get along with a pull request!''

<ol start="2" style="list-style-type: decimal;">
<li>Packages, Artifacts (Checksum(s), signature(s)…), ChangeLog and PAD files to dolibarr.org (/home/dolibarr/wwwroot/files)</li></ol>

RD: ''Credentials needed''

<ol start="3" style="list-style-type: decimal;">
<li>Packages to [http://sourceforge.net/projects/dolibarr/ Sourceforge.net]</li></ol>

RD: ''Credentials needed''

RD: ''Can be automated: [https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download doc]''

=== Verifiing ===

* ?

RD: ''This is where checksums comes in handy''

=== Releasing ===

# Craft announcement message

RD: ''The message template should be in the repo''

<ol start="2" style="list-style-type: decimal;">
<li>Post announcement as a news on dolibarr.org</li></ol>

RD: ''Credentials needed''

<ol start="2" style="list-style-type: decimal;">
<li>Send announcement on Social Networks</li></ol>

* [https://plus.google.com/+DolibarrOrg Google+]
* [http://www.twitter.com/dolibarr Twitter]
* [http://www.facebook.com/dolibarr Facebook]

RD: ''Credentials needed''

RD: ''Should all be automated through their respective APIs''

<ol start="3" style="list-style-type: decimal;">
<li>Send announcement on Mailing lists</li></ol>

dolibarr-user, dolibarr-dev, dolibarr-foundation

<ol start="4" style="list-style-type: decimal;">
<li>Send announcement on Forum</li></ol>

RD: ''This should be a sticky in the appropriate category (which?)''

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version on this wiki</li></ol>

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version in [http://doliforge.org Doliforge]</li></ol>

RD: ''Credentials needed''

== Misc. Questions ==

===RD===
* More projects are moving to tar.xz releases, shan't we join the boat?
* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.
LD: More then 80% of users prefer to use installer, and 60% of dowload are for wamp installer, so we must keep native distribution packages.
* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's
* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]
* Is there other announcements to be made?
* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?
LD: No, it would be better to have only php tools.

== Misc. Notes ==

* Directory structure for resulting binaries should be:
<pre>.
├── generic
├── package_aps
├── package_debian-ubuntu
├── package_mac
├── package_rpm_generic
├── package_rpm_mandriva
├── package_rpm_opensuse
├── package_rpm_redhat-fedora
└── package_windows
</pre>
* We need to define the versionning and naming conventions as well as the branching system

Dolibarr suppliers Brazil

2013-12-11T18:49:43Z

Saxa:

{{Dolibar_partners_list}}

{{TemplateCompany|
name=Sasa Ostrouska|
desc=Ajuda com Dolibarr na installacao e uso.|
web=|
email=casaxa@gmail.com|
zip=41230-080|
town=Salvador, Bahia|
country=Brasil|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

Module Brasil EN

2012-10-05T03:52:16Z

Saxa:

[[Category:Complementary modules]]
[[Category:Brasil]]
{{TemplateDocDev}}
{{TemplateDocUtil}}
= Informations =
{{TemplateModuleInfo
|editor=[[Sasa Ostrouska]]
|web=http://www.doliforge.org/projects/Brasil/
|status=dev
|prerequisites=
|minversion=3.3
|note=
}}

'''Module Brasil'''

This page should shortly become a description of what module Brasil should enable and do when installed in Dolibarr.

Few points which I have in mind:

1. Integrate all of the most important taxes used in Brasil with Dolibarr. Some of them are II, PIS, COFINS, ICMS, ICMS-II, ICMS-ST and other taxes.
Also be able to define the tax rates according to the NCM/SH code. The taxes should be linked in some way with the products table. I need to find out the
best possible way.

2. Possibility of export the invoice in a way understandable for the NF-e software. Maybe directly in xml or a TXT archive with pipe "|" as separator
so it can be imported in the government supplied free software.

Other stuff ?

Module Brasil EN

2012-10-05T03:50:46Z

Saxa:

[[Category:Complementary modules]]
[[Category:Brasil]]
{{TemplateDocDev}}
{{TemplateDocUtil}}
= Informations =
{{TemplateModuleInfo
|editor=[[Sasa Ostrouska]]
|web=http://www.doliforge.org
|status=dev
|prerequisites=
|minversion=3.3
|note=
}}

'''Module Brasil'''

This page should shortly become a description of what module Brasil should enable and do when installed in Dolibarr.

Few points which I have in mind:

1. Integrate all of the most important taxes used in Brasil with Dolibarr. Some of them are II, PIS, COFINS, ICMS, ICMS-II, ICMS-ST and other taxes.
Also be able to define the tax rates according to the NCM/SH code. The taxes should be linked in some way with the products table. I need to find out the
best possible way.

2. Possibility of export the invoice in a way understandable for the NF-e software. Maybe directly in xml or a TXT archive with pipe "|" as separator
so it can be imported in the government supplied free software.

Other stuff ?

More details here: https://doliforge.org/projects/Brasil/

Module Brasil EN

2012-10-05T03:44:41Z

Saxa:

'''Module Brasil'''

This page should shortly become a description of what module Brasil should enable and do when installed in Dolibarr.

Few points which I have in mind:

1. Integrate all of the most important taxes used in Brasil with Dolibarr. Some of them are II, PIS, COFINS, ICMS, ICMS-II, ICMS-ST and other taxes.
Also be able to define the tax rates according to the NCM/SH code. The taxes should be linked in some way with the products table. I need to find out the
best possible way.

2. Possibility of export the invoice in a way understandable for the NF-e software. Maybe directly in xml or a TXT archive with pipe "|" as separator
so it can be imported in the government supplied free software.

Other stuff ?

More details here: https://doliforge.org/projects/Brasil/

Module Brasil EN

2012-10-05T03:43:16Z

Saxa:

Module Brasil EN

2012-10-05T03:34:48Z

Saxa:

Module Brasil EN

2012-10-05T03:30:01Z

Saxa: Created page with "'''Module Brasil''' This page should shortly become a description of what module Brasil should enable and do when installed in Dolibarr."

'''Module Brasil'''

This page should shortly become a description of what module Brasil should enable and do when installed in Dolibarr.