Red1关于ADempiere及iDempiere的声明-最终版本

peanut

2012年1月11日Red1在其个人网站上刊出一篇关于ADempiere及iDempiere的正式声明。

对于关心ADempiere的朋友，以及关注Compiere产品家族的朋友，透过这篇声明，可以了解到ADempiere未来动向，可以进一步认识开源社区内部的运动与发展。

我摘译了其中一些较为重要的内容，在此不作是非评价。标有注释的地方为本人所加，仅供参考。
原文为英文，全文链接为： http://red1.org/adempiere/viewtopic.php?f=33&t=1482

这是2012年1月11日Red1修改后的最终版本。——Peanut

THE BOGOTA ANNOUNCEMENT - FINAL EDITION - 11.1.2012
波哥大声明 - 最终版本 - 2012年1月11日

Red1

I been here in Bogota with Carlos Ruiz since 4th January, and had a series of meetings on many matters ranging from the war to the issues to the code release of iDempiere. I try to make some brief but important questions or points below which is now final and frozen. Any further updates will be at the bottom of this thread.

(2012年)1月4日以来，我一直在波哥大（注释：哥伦比亚首都）与Carlos Ruiz在一起，有一系列会议——关于从斗争问题到iDempiere代码发布等各个方面。我尽量列出一些简短而重要的问题或要点。本文内容是最终版本并冻结。将来任何修改将会在帖子后面补充。

BACKGROUND: Carlos has two repos and Heng Sin has one. Carlos repos are ADempiere361 which we refer to as CarlosRuiz361 and iDempiere at BitBucket, which is a clone of HengSin's repo. Most agreed that HengSin's iDempiere OSGi completion is the way to go so this is our utmost concern that the path from ADempiere to iDempiere remains intact.

背景：Carlos有两个代码库，Heng Sin有一个。Carlos的代码库，一个是ADempiere361，我们称之为CarlosRuiz361，另一个是在BitBucket的iDempiere ，这个是HengSin代码库的克隆。大多数人同意——完善HengSin的iDempiere OSGi是我们要走的路。所以这是我们最关心的问题，从ADempiere到iDempiere的过程保持平稳。

QUESTION: IS ADEMPIERE MIGRATION FROM 361 to IDEMPIERE CLOSED?
1.1 iDempiere bitbucket is public but the 361 is restricted. 361 has moved from Kenai to bitbucket as a private branch (restricted to contributors only).
1.2 Carlos continues to work on the iDempiere bitbucket by reviewing all patches acceptable from direct or indirect sources including ADempiere trackers.
1.3 HengSin has always been public. It is Carlos Ruiz's work that suffers erroneous QA and review of code and credit from the main ADempiere project that is in question. So this thread is to work towards a right solution that puts first things first - the code.

问：从ADempiere从361到IDEMPIERE的迁移是否关闭了？
答：1.1 iDempiere@bitbucket是公开的，但是限制361。361已经从Kenai开发平台迁移到bitbucket开发平台，作为私人分支（仅对贡献者开放）。
1.2 Carlos继续在iDempiere@bitbucket工作，审查所有的可用补丁，来自直接的和间接的来源，包括ADempiere追踪。
1.3 HengSin的工作总是公开的。Carlos Ruiz的工作则是对ADempiere主项目中的众多问题代码进行质量保证和审查。所以朝向正确解决方案的思路是——把最重要的事情放在第一位——代码。

QUESTION: WHAT ABOUT CARLOSRUIZ361?
2.1 CarlosRuiz361 will be deprecated to iDempiere. What is in 361 is the migration pack and path to the iDempiere 1.0 release later. Those who follow it will have no problem converting or migrating or upgrading their instances to iDempiere.
2.2 Thus 361 is the ADempiere361 'forking point' to iDempiere.
2.3 The official ADempiere370 release at SourceForge.net/ADempiere has no path to iDempiere. Because no one is working on that here.
2.4 CarlosRuiz361 is restricted to contributors only. Those who have contributed some feature, bug report or fix directly to Carlos Ruiz will be given read access. Carlos will work less on 361 but more on iDempiere as the big jump. 361 will end with the migration path and pack.

问：那么关于CarlosRuiz361呢？
答：2.1 CarlosRuiz361将会被废弃。在361里的是迁移包和通向将发布的iDempiere 1.0的路径。那些跟从361的朋友，将会没有问题地转换、迁移或升级他们的实例到iDempiere。
2.2 因为361是ADempiere361通向iDempiere的“分叉点”。
2.3 官方在SourceForge.net发布的ADempiere370将无从通向iDempiere，因为没有人在那儿工作。
2.4  CarlosRuiz361仅向贡献者开放。那些贡献了功能、错误报告或纠错的朋友，将会给以读取权限。Carlos将会减少在361的工作，更多地在iDempiere工作——因为这是一个大的飞跃。 361以会以迁移路径或迁移包告终。

QUESTION: WHAT ABOUT HENGSIN'S REPO?
3.1 HengSin's work is cloned by Carlos into his bitbucket repo of iDempiere.
3.2 HengSin wish to follow the GitHub policy of self management and allow his repo to be cloned freely by anyone.
3.3 Eventually Carlos iDempiere and HengSin's synch with each other but there maybe some minute lag or difference due to common peer review lag.

问：那么关于HengSin的代码库呢？
答：3.1 HengSin的工作已经由Carlos克隆到他的iDempiere@bitbucket代码库。
3.2 HengSin希望跟从GitHub的自主管理策略，并允许他的代码库被任何人自由地克隆。
3.3 最终Carlos的iDempiere与HengSin的彼此同步，但是会存在一些微小的滞后或差异——由于共同同行评审的滞后。


QUESTION: WHAT ABOUT ADEMPIERE?
13. Ask them, perhaps they have more right to speak on this and not us. We are most concerned about a single important future roadmap of iDempiere and cannot focus on conflicts which we did not start. If rights were not harmed for us to contribute this would not have happened.

问：那么关于ADempiere呢？
答：13. 问他们(注释：指ADeV)，也许他们对此有更多的话语权，而不是我们。我们最关心的是iDempiere未来蓝图，而不是去专注于冲突，而且我们并未引发冲突。如果权利(注释：指ADeV在ADempiere社区的管理权)未曾阻碍我们作出贡献，这（注释：指成立iDempiere项目）本该不曾发生。


QUESTION: WHY DON'T YOU RETURN TO ADEMPIERE?
18. There are long posts explaining all our positions on so many issues from code review, to trunk destabilization, to citizenship management that was never really addressed by those in charge. They refused to take popular opinion seriously. Nor want to hold official vote on the outstanding issues. Nor does the one in charge wants to meet me, even though i traveled thousands of miles to his place. The rest of the committees does not seem to care of the issues nor able to advice the head who can accuse me freely and yet seems too powerful - untouchable. So we vote with our feet.

问：你为何不回到ADEMPIERE中去？
答：18. 有很多帖子解释我们在众多问题上的立场，从代码审查，主干版本(trunk)不稳定，到公民管理，那些负责人(注释：指ADeV ) 从来没有真正解决。他们拒绝认真采纳民-意，也不希望就悬而未决的问题举行正式投票。负责人(注释：可能是指ADeV的主席Norbert Wessel )也不愿意和我见面，尽管我不远千里来到他的驻地。其余的委员对这些问题似乎并不关心，而且也未能劝说负责人(他可以自由地指责我，而且貌似非常强势) - 碰不到头。因此，我们用脚投票。

siantii

从目前情况来看，idempiere的架构模式中各个功能模块内聚更强，耦合更单纯，也便于外围开发者专注于自己感兴趣的部分，方便开发维护和销售自己的模块。

peanut

主帖翻译已经更新至2012年1月11日Red1修改后的最终版本。特此说明

jiuduren

新年快乐！我们可以开始工作了{:soso_e113:}