Wednesday, April 16, 2008

Openbravo Manifesto

Last weekend during the Openbravo Get Together in Barcelona we presented the Openbravo Manifesto (which was published both in English and Spanish). For a long time, many of us at Openbravo S.L wanted to clarify the extent of our commitment to Openbravo ERP and POS projects, and open source in general; we also wanted to share our values and belief with our Community. Openbravo was born as an open source project and some of its values are deeply rooted in the company.

The manifesto highlights Openbravo's company values: transparency, openness, collaboration, meritocracy, leadership, excellence and gratitude. We strive to live and keep these values in mind in everything that we do.

Most importantly, the Manifesto also highlights Openbravo company's commitments towards our Community: open source availability, open access to the code under development, open documentation and effective project infrastructure. We are also committed to honor other people's rights by providing proper attribution to any contribution and respecting other people's intellectual property; at the same time, we are ready to defend our Community's investment into the project through legal means if necessary.

We believe that publishing this Manisfesto is very important step ahead, since Openbravo S.L is currently the main sponsor of Openbravo projects. Additionally, we are proud of being the first company of our category that makes a public statement about its commitments to his Community. This underscores our belief that, from the very first day, our Community has been and will continue to be the key to success for the Openbravo projects.

4 comments:

Eduardo said...

"In its Subversion repository, Openbravo keeps a maintenance branch for each supported Community Edition that allows to isolate maintenance work from on going development. This maintenance branch, however, is intended for future usage as a commercial offer and it is therefore kept private and it is not visible to the community."

Liberar la rama estable para la Comunidad que os ayuda a crearla sí es compromiso con la Comunidad.

Lo demás son milongas.

Jordi Mas said...

Hello Eduardo,

You can apply the bugs that are critical for you or your customers on the latest community edition using Subversion[1]. All the bug fixes are in trunk, you only have to leverage the patches that you are interested into. In all the Subversion commits you have in the comment the bug fix that revision fixes. We do so to help people to identify them.

For the time being, this is the commitment we can sustain for free with our available resources. We don't want to undertake any commitment we can not maintain indefinitely, and maintaining a public stable branch for every community edition is something we cannot commit at the moment.

I agree the wording of the wiki article you are referring to is a little bit confusing, and we will improve it asap.

Jordi,

[1] http://wiki.openbravo.com/wiki/Subversion#Applying_revisions_to_your_copy

Ville Lindfors said...


For the time being, this is the commitment we can sustain for free with our available resources. We don't want to undertake any commitment we can not maintain indefinitely, and maintaining a public stable branch for every community edition is something we cannot commit at the moment.


I agree that it is too much to maintain a public stable branch, but how about public maintenance branch without any commitment?

This would benefit Openbravo to get larger developer community as currently some developers just try and abandon the Openbravo as there is just ridiculous bugs in stable version. Also developers would find new bugs instead of many developers finding the same issues all over again.

When Openbravo as a company has enough trust for the fixes it can release those to the customers that have purchased support contract.

It is bit ironical, that the one who is suffering the most about status quo is Openbravo as a company.

If there would be a vibrant community this would change by the community. With the current release quality it is difficult to attract developers. And open source project without developers is ...

I think that one of these will happen:
* Openbravo will make the maintenance branch public
* There will be community version that is buil on top of releases
* Openbravo will fade away

Let's see what happens.

be EMI said...

mengenai openbravo, kebetulan saya mengambil tugas akhir dengan tema ERP dengan obyek usaha mikro yaitu bidang furniture>\
Saya menginginkan opensource Openbravo ERP ini menggunakan bahasa Indonesia untuk tampilannya, karena selama ini saya menggunakan bahasa inggris, saya bermaksud untuk mengimplementasikan software ini untuk para UKM karena keterbatasan mereka menggunakan bahasa inggris