Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Nicolas Malin]

We can see this on second time to improve the taher's suggest task 
pullPluginSource with list different repository on the build.gradle


But by default only the official repository source code can be listed.

Nicolas


Le 11/01/2017 à 18:54, Pierre Smits a écrit :

We could also consider to have for each component a separate ASF git repo
that replicates to external repo structures like GitHub. This would
increase exposure and potentially attract more contributors as subject
matter experts.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jan 11, 2017 at 4:54 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:


I agree with the svn layout that Taher is proposing which is also inline
with what other Apache projects are doing (see for example [*]).
The idea behind these layouts is that the top level folder is for the
"project" and its subfolders are for the project's products:
project/product1
project/product2
...
that for OFBiz would be (as already mentioned by Taher):
ofbiz/ofbiz
ofbiz/ofbiz-plugins
ofbiz/site
...
Each of the above folders may contain the "trunk", "tags" and "branches"
folders.
In fact it is worth to mention that each Apache project can publish more
than one product (and in fact several do); the OFBiz project doesn't
currently but it is better to have a layout that will allow us to produce
more than one product.

Thank you,

Jacopo

[*] http://svn.apache.org/repos/asf/lucene/


On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb <
slidingfilame...@gmail.com

wrote:
Hello Folks

This is a proposal to the community to restructure our SVN repository. We
do this by separating "official" plugins from the core OFBiz framework

and

to provide build script tasks to easily download and install these

plugins.

The details of this proposal are as follows:

1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches

and

tags underneath as is)
2- Create a new tree under http://svn.apache.org/repos/as
f/ofbiz/ofbiz-plugins to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will

load

automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a
plugin from subversion and places it in /plugins and runs any install

logic

that it may have
   Syntax: pullPluginSource -PpluginId=
   Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above

So for example, under this proposal, trunk is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk

And the birt component is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt

This would allow us to have in the future the ability to provide releases
not only for the framework but the plugins as well as two separate

products.

What do you think?

Cheers,

Taher Alkhateeb

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Taher Alkhateeb]

I like the idea of ofbiz-core Nicolas

On Jan 12, 2017 9:49 AM, "Nicolas Malin"  wrote:

> Hi Taher
>
>
> Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit :
>
>> Hello Folks
>>
>> This is a proposal to the community to restructure our SVN repository. We
>> do this by separating "official" plugins from the core OFBiz framework and
>> to provide build script tasks to easily download and install these plugins.
>> The details of this proposal are as follows:
>>
>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
>> and tags underneath as is)
>>
> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
> Like that we would have :
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>
>> 2- Create a new tree under ps to house all plugins
>> 3- Remove /plugins/component-load.xml (any component in /plugins will
>> load automatically if it is enabled in ofbiz-component.xml)
>> 4- Create a gradle task with the below syntax. This task downloads a
>> plugin from subversion and places it in /plugins and runs any install logic
>> that it may have
>>   Syntax: pullPluginSource -PpluginId=
>>   Example: pullPluginSource -PpluginId=birt
>> 5- Refactor the build scripts to cater for all the above
>> 6- Update README.md to reflect all the above
>>
> The rest sound good for me :)
>
>> [...]
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>>
>>
>

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Nicolas Malin]

Hi Taher


Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit :

Hello Folks

This is a proposal to the community to restructure our SVN repository. 
We do this by separating "official" plugins from the core OFBiz 
framework and to provide build script tasks to easily download and 
install these plugins. The details of this proposal are as follows:


1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to 
http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches 
and tags underneath as is)

Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
Like that we would have :
http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin

2- Create a new tree under ps to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will 
load automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a 
plugin from subversion and places it in /plugins and runs any install 
logic that it may have

  Syntax: pullPluginSource -PpluginId=
  Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above 

The rest sound good for me :)

[...]

Cheers,

Taher Alkhateeb

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Ashish Vijaywargiya]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997


On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb  wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Pranay Pandey]

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits 
wrote:

> We could also consider to have for each component a separate ASF git repo
> that replicates to external repo structures like GitHub.

+1

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Thu, Jan 12, 2017 at 11:58 AM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits 
> wrote:
>
> > We could also consider to have for each component a separate ASF git repo
> > that replicates to external repo structures like GitHub.
>
>
> Agreed. it would be a natural consequence of the new layout and we should
> definitely request this to the Infra.
>
> Jacopo
>

Re: What is the "Apache OFBiz" product?

[Rupert Howell]

+1 for "Apache OFBiz enterprise automation framework" also.

On 12 January 2017 at 02:06, Hans Bakker  wrote:

> +1 for "Apache OFBiz enterprise automation framework"
>
> and perhaps later create a new product "OFBiz Business suite" based on the
> framework which is ready for direct use.
>
> However currently leave the immediate consumption for the systems like
> Hotwax e-commerce, Ilscipio ERP and GrowERP and others
>
> Regards,
> Hans
>
> On 12/01/17 00:44, Nicolas Malin wrote:
>
>> I don't like the term ERP because is so reduced term for OFBiz dans all
>> product that can register a task for a party and a product is an ERP
>>
>> I prefer "Apache OFBiz enterprise automation framework"
>>
>> The term ERP or Business suite will come with the plugin addition to the
>> OFBiz core.
>>
>> Nicolas
>>
>> Le 11/01/2017 à 17:15, Taher Alkhateeb a écrit :
>>
>>> Agreed Jacopo,
>>>
>>> My preference would be The "Apache OFBiz" ERP suite. The reason is
>>> that the
>>> term ERP is very popular and understandable to business folks. It also
>>> conveys the heart of what this product is all about. Yes it is not yet
>>> refined for immediate consumption by end users, but that does not prevent
>>> usage of the term.
>>>
>>>
>>>
>>>
>>> On Jan 11, 2017 6:19 PM, "Jacopo Cappellato" >> hotwaxsystems.com> wrote:
>>>
>>> On Wed, Jan 11, 2017 at 3:51 PM, Julien NICOLAS
>>> 
>>> wrote:
>>>
>>> [...]
 This is why I prefer the actual sentence "Apache OFBiz® is an open
 source
 product for the automation of enterprise processes that includes
 framework
 components and business applications"

 >From a trademark best practice perspective the above is incorrect
>>> (yeah...
>>> it is in our website) and should be changed to its equivalent:
>>>
>>> "The Apache OFBiz® open source product for the automation of enterprise
>>> processes"
>>>
>>> and its longer (descriptive) version would be:
>>>
>>> "The Apache OFBiz® open source product for the automation of enterprise
>>> processes includes framework components and business applications"
>>>
>>> A bit ugly.
>>>
>>> Jacopo
>>>
>>>
>>
> --
>
> Regards,
>
> Hans Bakker
> CEO, http://antwebsystems.com
>



-- 
Rupert Howell

Provolve Ltd
Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK

t: 01730 267868 / m: 079 0968 5308
e:  ruperthow...@provolve.com
w: http://www.provolve.com

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Jacopo Cappellato]

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits 
wrote:

> We could also consider to have for each component a separate ASF git repo
> that replicates to external repo structures like GitHub.


Agreed. it would be a natural consequence of the new layout and we should
definitely request this to the Infra.

Jacopo

Re: What is the "Apache OFBiz" product?

[Jacopo Cappellato]

On Wed, Jan 11, 2017 at 6:44 PM, Nicolas Malin 
wrote:

> I don't like the term ERP because is so reduced term for OFBiz dans all
> product that can register a task for a party and a product is an ERP
>
> I prefer "Apache OFBiz enterprise automation framework"
>
> The term ERP or Business suite will come with the plugin addition to the
> OFBiz core.
>
> Nicolas


I also like the shorter ones:

The "Apache OFBiz" enterprise framework
The "Apache OFBiz" enterprise suite (which is similar to the one proposed
by Gavin, that I also like, that has the word "business" instead on
"enterprise")
My concern with the word ERP is that it is an acronym and ends up being too
close to the word OFBiz, which is also some sort of acronym, and the
concatenated string may look confusing: "Apache OFBiz ERP".
Another concern with the name "enterprise framework" is that, when/if we
will release a separate product containing only the OFBiz framework, this
name would be confusing: in fact my preference is to allocate "framework"
for that product (if we will ever release it).

Anyway, great proposals so far... I hope the brainstorming will continue!
Any volunteer to list *all* the ideas to a Confluence page (maybe even with
relevant comments from this thread behind each proposal)?

Jacopo

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Pranay Pandey]

+1 for the proposal from Taher.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb  wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Arun Patidar]

+1 for directory structure and OFBiz plugin management.

-- 
Thanks & Regards
---
Arun Patidar
Manager,Enterprise Software Development
HotWax Mediawww.hotwaxsystems.com


On Thu, Jan 12, 2017 at 10:34 AM, Gavin Mabie  wrote:

> +1 Like it
> Gavin
>
> On Thu, Jan 12, 2017 at 7:00 AM, Deepak Dixit <
> deepak.di...@hotwaxsystems.com> wrote:
>
> > +1 for the svn folder structure.
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> >
> > On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai 
> wrote:
> >
> > > +1 to the svn folder structure.
> > >
> > > On the plugin publish and install, could we consider publish a zip file
> > to
> > > maven repository as well as the jars? In production environment, unzip
> > the
> > > zip file under plugins and then it can work, or even better, don't
> unzip
> > > it, let it work similar to an android apk file.
> > >
> > >
> > > -邮件原件-
> > > 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com]
> > > 发送时间: 2017年1月11日 23:02
> > > 收件人: dev@ofbiz.apache.org
> > > 主题: Proposal to create a separate svn repository for the OFBiz official
> > > plugins
> > >
> > > Hello Folks
> > >
> > > This is a proposal to the community to restructure our SVN repository.
> > > We do this by separating "official" plugins from the core OFBiz
> framework
> > > and to provide build script tasks to easily download and install these
> > > plugins. The details of this proposal are as follows:
> > >
> > > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> > and
> > > tags underneath as is)
> > > 2- Create a new tree under
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all
> plugins
> > > 3- Remove /plugins/component-load.xml (any component in /plugins will
> > load
> > > automatically if it is enabled in ofbiz-component.xml)
> > > 4- Create a gradle task with the below syntax. This task downloads a
> > > plugin from subversion and places it in /plugins and runs any install
> > logic
> > > that it may have
> > >Syntax: pullPluginSource -PpluginId=
> > >Example: pullPluginSource -PpluginId=birt
> > > 5- Refactor the build scripts to cater for all the above
> > > 6- Update README.md to reflect all the above
> > >
> > > So for example, under this proposal, trunk is located in:
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> > >
> > > And the birt component is located in:
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> > >
> > > This would allow us to have in the future the ability to provide
> releases
> > > not only for the framework but the plugins as well as two separate
> > products.
> > >
> > > What do you think?
> > >
> > > Cheers,
> > >
> > > Taher Alkhateeb
> > >
> > >
> >
>

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Gavin Mabie]

+1 Like it
Gavin

On Thu, Jan 12, 2017 at 7:00 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> +1 for the svn folder structure.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai  wrote:
>
> > +1 to the svn folder structure.
> >
> > On the plugin publish and install, could we consider publish a zip file
> to
> > maven repository as well as the jars? In production environment, unzip
> the
> > zip file under plugins and then it can work, or even better, don't unzip
> > it, let it work similar to an android apk file.
> >
> >
> > -邮件原件-
> > 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com]
> > 发送时间: 2017年1月11日 23:02
> > 收件人: dev@ofbiz.apache.org
> > 主题: Proposal to create a separate svn repository for the OFBiz official
> > plugins
> >
> > Hello Folks
> >
> > This is a proposal to the community to restructure our SVN repository.
> > We do this by separating "official" plugins from the core OFBiz framework
> > and to provide build script tasks to easily download and install these
> > plugins. The details of this proposal are as follows:
> >
> > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> and
> > tags underneath as is)
> > 2- Create a new tree under
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
> > 3- Remove /plugins/component-load.xml (any component in /plugins will
> load
> > automatically if it is enabled in ofbiz-component.xml)
> > 4- Create a gradle task with the below syntax. This task downloads a
> > plugin from subversion and places it in /plugins and runs any install
> logic
> > that it may have
> >Syntax: pullPluginSource -PpluginId=
> >Example: pullPluginSource -PpluginId=birt
> > 5- Refactor the build scripts to cater for all the above
> > 6- Update README.md to reflect all the above
> >
> > So for example, under this proposal, trunk is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> >
> > And the birt component is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> >
> > This would allow us to have in the future the ability to provide releases
> > not only for the framework but the plugins as well as two separate
> products.
> >
> > What do you think?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> >
>

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Deepak Dixit]

+1 for the svn folder structure.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai  wrote:

> +1 to the svn folder structure.
>
> On the plugin publish and install, could we consider publish a zip file to
> maven repository as well as the jars? In production environment, unzip the
> zip file under plugins and then it can work, or even better, don't unzip
> it, let it work similar to an android apk file.
>
>
> -邮件原件-
> 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com]
> 发送时间: 2017年1月11日 23:02
> 收件人: dev@ofbiz.apache.org
> 主题: Proposal to create a separate svn repository for the OFBiz official
> plugins
>
> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository.
> We do this by separating "official" plugins from the core OFBiz framework
> and to provide build script tasks to easily download and install these
> plugins. The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>Syntax: pullPluginSource -PpluginId=
>Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

Re: What is the "Apache OFBiz" product?

[Hans Bakker]

+1 for "Apache OFBiz enterprise automation framework"

and perhaps later create a new product "OFBiz Business suite" based on 
the framework which is ready for direct use.


However currently leave the immediate consumption for the systems like 
Hotwax e-commerce, Ilscipio ERP and GrowERP and others


Regards,
Hans

On 12/01/17 00:44, Nicolas Malin wrote:

I don't like the term ERP because is so reduced term for OFBiz dans all
product that can register a task for a party and a product is an ERP

I prefer "Apache OFBiz enterprise automation framework"

The term ERP or Business suite will come with the plugin addition to the
OFBiz core.

Nicolas

Le 11/01/2017 à 17:15, Taher Alkhateeb a écrit :

Agreed Jacopo,

My preference would be The "Apache OFBiz" ERP suite. The reason is
that the
term ERP is very popular and understandable to business folks. It also
conveys the heart of what this product is all about. Yes it is not yet
refined for immediate consumption by end users, but that does not prevent
usage of the term.




On Jan 11, 2017 6:19 PM, "Jacopo Cappellato"  wrote:

On Wed, Jan 11, 2017 at 3:51 PM, Julien NICOLAS

wrote:


[...]
This is why I prefer the actual sentence "Apache OFBiz® is an open
source
product for the automation of enterprise processes that includes
framework
components and business applications"


>From a trademark best practice perspective the above is incorrect
(yeah...
it is in our website) and should be changed to its equivalent:

"The Apache OFBiz® open source product for the automation of enterprise
processes"

and its longer (descriptive) version would be:

"The Apache OFBiz® open source product for the automation of enterprise
processes includes framework components and business applications"

A bit ugly.

Jacopo





--

Regards,

Hans Bakker
CEO, http://antwebsystems.com

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Shi Jinghai]

+1 to the svn folder structure.

On the plugin publish and install, could we consider publish a zip file to 
maven repository as well as the jars? In production environment, unzip the zip 
file under plugins and then it can work, or even better, don't unzip it, let it 
work similar to an android apk file.


-邮件原件-
发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com] 
发送时间: 2017年1月11日 23:02
收件人: dev@ofbiz.apache.org
主题: Proposal to create a separate svn repository for the OFBiz official plugins

Hello Folks

This is a proposal to the community to restructure our SVN repository. 
We do this by separating "official" plugins from the core OFBiz framework and 
to provide build script tasks to easily download and install these plugins. The 
details of this proposal are as follows:

1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to 
http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and tags 
underneath as is)
2- Create a new tree under
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will load 
automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a plugin 
from subversion and places it in /plugins and runs any install logic that it 
may have
   Syntax: pullPluginSource -PpluginId=
   Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above

So for example, under this proposal, trunk is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk

And the birt component is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt

This would allow us to have in the future the ability to provide releases not 
only for the framework but the plugins as well as two separate products.

What do you think?

Cheers,

Taher Alkhateeb

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Pierre Smits]

We could also consider to have for each component a separate ASF git repo
that replicates to external repo structures like GitHub. This would
increase exposure and potentially attract more contributors as subject
matter experts.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jan 11, 2017 at 4:54 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> I agree with the svn layout that Taher is proposing which is also inline
> with what other Apache projects are doing (see for example [*]).
> The idea behind these layouts is that the top level folder is for the
> "project" and its subfolders are for the project's products:
> project/product1
> project/product2
> ...
> that for OFBiz would be (as already mentioned by Taher):
> ofbiz/ofbiz
> ofbiz/ofbiz-plugins
> ofbiz/site
> ...
> Each of the above folders may contain the "trunk", "tags" and "branches"
> folders.
> In fact it is worth to mention that each Apache project can publish more
> than one product (and in fact several do); the OFBiz project doesn't
> currently but it is better to have a layout that will allow us to produce
> more than one product.
>
> Thank you,
>
> Jacopo
>
> [*] http://svn.apache.org/repos/asf/lucene/
>
>
> On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb <
> slidingfilame...@gmail.com
> > wrote:
>
> > Hello Folks
> >
> > This is a proposal to the community to restructure our SVN repository. We
> > do this by separating "official" plugins from the core OFBiz framework
> and
> > to provide build script tasks to easily download and install these
> plugins.
> > The details of this proposal are as follows:
> >
> > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> and
> > tags underneath as is)
> > 2- Create a new tree under http://svn.apache.org/repos/as
> > f/ofbiz/ofbiz-plugins to house all plugins
> > 3- Remove /plugins/component-load.xml (any component in /plugins will
> load
> > automatically if it is enabled in ofbiz-component.xml)
> > 4- Create a gradle task with the below syntax. This task downloads a
> > plugin from subversion and places it in /plugins and runs any install
> logic
> > that it may have
> >   Syntax: pullPluginSource -PpluginId=
> >   Example: pullPluginSource -PpluginId=birt
> > 5- Refactor the build scripts to cater for all the above
> > 6- Update README.md to reflect all the above
> >
> > So for example, under this proposal, trunk is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> >
> > And the birt component is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> >
> > This would allow us to have in the future the ability to provide releases
> > not only for the framework but the plugins as well as two separate
> products.
> >
> > What do you think?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> >
>

Re: What is the "Apache OFBiz" product?

[Nicolas Malin]

I don't like the term ERP because is so reduced term for OFBiz dans all 
product that can register a task for a party and a product is an ERP


I prefer "Apache OFBiz enterprise automation framework"

The term ERP or Business suite will come with the plugin addition to the 
OFBiz core.


Nicolas

Le 11/01/2017 à 17:15, Taher Alkhateeb a écrit :

Agreed Jacopo,

My preference would be The "Apache OFBiz" ERP suite. The reason is that the
term ERP is very popular and understandable to business folks. It also
conveys the heart of what this product is all about. Yes it is not yet
refined for immediate consumption by end users, but that does not prevent
usage of the term.




On Jan 11, 2017 6:19 PM, "Jacopo Cappellato"  wrote:

On Wed, Jan 11, 2017 at 3:51 PM, Julien NICOLAS 
wrote:


[...]
This is why I prefer the actual sentence "Apache OFBiz® is an open source
product for the automation of enterprise processes that includes framework
components and business applications"


>From a trademark best practice perspective the above is incorrect (yeah...
it is in our website) and should be changed to its equivalent:

"The Apache OFBiz® open source product for the automation of enterprise
processes"

and its longer (descriptive) version would be:

"The Apache OFBiz® open source product for the automation of enterprise
processes includes framework components and business applications"

A bit ugly.

Jacopo

Re: What is the "Apache OFBiz" product?

[Taher Alkhateeb]

Agreed Jacopo,

My preference would be The "Apache OFBiz" ERP suite. The reason is that the
term ERP is very popular and understandable to business folks. It also
conveys the heart of what this product is all about. Yes it is not yet
refined for immediate consumption by end users, but that does not prevent
usage of the term.




On Jan 11, 2017 6:19 PM, "Jacopo Cappellato"  wrote:

On Wed, Jan 11, 2017 at 3:51 PM, Julien NICOLAS 
wrote:

> [...]
> This is why I prefer the actual sentence "Apache OFBiz® is an open source
> product for the automation of enterprise processes that includes framework
> components and business applications"
>

>From a trademark best practice perspective the above is incorrect (yeah...
it is in our website) and should be changed to its equivalent:

"The Apache OFBiz® open source product for the automation of enterprise
processes"

and its longer (descriptive) version would be:

"The Apache OFBiz® open source product for the automation of enterprise
processes includes framework components and business applications"

A bit ugly.

Jacopo

Re: Proposal to create a separate svn repository for the OFBiz official plugins

[Jacopo Cappellato]

I agree with the svn layout that Taher is proposing which is also inline
with what other Apache projects are doing (see for example [*]).
The idea behind these layouts is that the top level folder is for the
"project" and its subfolders are for the project's products:
project/product1
project/product2
...
that for OFBiz would be (as already mentioned by Taher):
ofbiz/ofbiz
ofbiz/ofbiz-plugins
ofbiz/site
...
Each of the above folders may contain the "trunk", "tags" and "branches"
folders.
In fact it is worth to mention that each Apache project can publish more
than one product (and in fact several do); the OFBiz project doesn't
currently but it is better to have a layout that will allow us to produce
more than one product.

Thank you,

Jacopo

[*] http://svn.apache.org/repos/asf/lucene/


On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb  wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

Re: What is the "Apache OFBiz" product?

[Jacopo Cappellato]

On Wed, Jan 11, 2017 at 3:51 PM, Julien NICOLAS 
wrote:

> [...]
> This is why I prefer the actual sentence "Apache OFBiz® is an open source
> product for the automation of enterprise processes that includes framework
> components and business applications"
>

>From a trademark best practice perspective the above is incorrect (yeah...
it is in our website) and should be changed to its equivalent:

"The Apache OFBiz® open source product for the automation of enterprise
processes"

and its longer (descriptive) version would be:

"The Apache OFBiz® open source product for the automation of enterprise
processes includes framework components and business applications"

A bit ugly.

Jacopo

Proposal to create a separate svn repository for the OFBiz official plugins

[Taher Alkhateeb]

Hello Folks

This is a proposal to the community to restructure our SVN repository. 
We do this by separating "official" plugins from the core OFBiz 
framework and to provide build script tasks to easily download and 
install these plugins. The details of this proposal are as follows:


1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to 
http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches 
and tags underneath as is)
2- Create a new tree under 
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will 
load automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a 
plugin from subversion and places it in /plugins and runs any install 
logic that it may have

  Syntax: pullPluginSource -PpluginId=
  Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above

So for example, under this proposal, trunk is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk

And the birt component is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt

This would allow us to have in the future the ability to provide 
releases not only for the framework but the plugins as well as two 
separate products.


What do you think?

Cheers,

Taher Alkhateeb

Re: What is the "Apache OFBiz" product?

[Julien NICOLAS]

Hi Jacopo,

I'm not sure that ofbiz is an ERP. I mean I'm not sure that ofbiz is a 
turnkey solution. You can't just install the software and say "Let use 
it, it's ready!". We get our hands dirty before the final customer can 
use it serenely.


This is why I prefer the actual sentence "Apache OFBiz® is an open 
source product for the automation of enterprise processes that includes 
framework components and business applications"


I understand that is too long, this is why I suggest :

The "Apache OFBiz" framework

The "Apache OFBiz" web based application framework

Julien.

On 11/01/2017 14:51, Jacopo Cappellato wrote:

Any ideas? Please try to fill the  placeholder below with the string
that you find more suited:

  The "Apache OFBiz" 

Re: What is the "Apache OFBiz" product?

[Gavin Mabie]

The Apache OFBiz "Business Suite"?

Similar software solutions use this terminology. eg ADempiere Business
Suite, OpenBravo Business Suite.

Gavin



On Wed, Jan 11, 2017 at 3:51 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> *Rationale*
>
> "Apache OFBiz" is one of our trademarks. And we apply it to our project and
> product; we say:
> 1) the "Apache OFBiz" project or the "Apache OFBiz" community
> 2) the "Apache OFBiz" product (i.e. the downloadable software package that
> we release)
>
> While #1 is pretty much a satisfactory definition, I find that "product" is
> a too generic term and that we could find and agree upon a more precise and
> "official" definition.
> It is worth noting that the trademark best practices says that you should
> never use the trademark on a product as a noun but rather as an adjective.
> So for example:
> - this is *not* correct (noun): "download Apache OFBiz from here"
> - this *is* correct (adjective): "download the Apache OFBiz product from
> here"
>
> *Discussion Item*
>
> Can we find a better definition for our product than... "product" or
> "software product"?
>
> For example we could consider (after reading this definition [*]):
> The "Apache OFBiz" software suite or
> The "Apache OFBiz" suite or
> The "Apache OFBiz" ERP software suite or
> The "Apache OFBiz" ERP suite
> etc...
>
> Any ideas? Please try to fill the  placeholder below with the string
> that you find more suited:
>
>  The "Apache OFBiz" 
>
> If we agree upon an "official" definition then we could use it consistently
> in our website, announcements, social media etc...
>
> Regards,
>
> Jacopo
>
> [*] https://en.wikipedia.org/wiki/Software_suite
>

What is the "Apache OFBiz" product?

[Jacopo Cappellato]

*Rationale*

"Apache OFBiz" is one of our trademarks. And we apply it to our project and
product; we say:
1) the "Apache OFBiz" project or the "Apache OFBiz" community
2) the "Apache OFBiz" product (i.e. the downloadable software package that
we release)

While #1 is pretty much a satisfactory definition, I find that "product" is
a too generic term and that we could find and agree upon a more precise and
"official" definition.
It is worth noting that the trademark best practices says that you should
never use the trademark on a product as a noun but rather as an adjective.
So for example:
- this is *not* correct (noun): "download Apache OFBiz from here"
- this *is* correct (adjective): "download the Apache OFBiz product from
here"

*Discussion Item*

Can we find a better definition for our product than... "product" or
"software product"?

For example we could consider (after reading this definition [*]):
The "Apache OFBiz" software suite or
The "Apache OFBiz" suite or
The "Apache OFBiz" ERP software suite or
The "Apache OFBiz" ERP suite
etc...

Any ideas? Please try to fill the  placeholder below with the string
that you find more suited:

 The "Apache OFBiz" 

If we agree upon an "official" definition then we could use it consistently
in our website, announcements, social media etc...

Regards,

Jacopo

[*] https://en.wikipedia.org/wiki/Software_suite

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Jacopo Cappellato]

On Wed, Jan 11, 2017 at 12:21 PM, Gavin Mabie  wrote:

> +1 and good luck.  It may proof easier to write it in a line of code than
> in plain English. LOL.
>

indeed!

Jacopo

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Gavin Mabie]

+1 and good luck.  It may proof easier to write it in a line of code than
in plain English. LOL.

On Wed, Jan 11, 2017 at 1:06 PM, Michael Brohl 
wrote:

> +1
>
> I have to postpone ideas, will provide them later...
>
> Regards,
>
> Michael
>
>
> Am 11.01.17 um 10:10 schrieb Jacopo Cappellato:
>
> Hi all,
>>
>> I think it would be great if we could write a short, simple, clear,
>> realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
>> project.
>> The mission statement, that summarizes in 1 line what we are all here for,
>> could be published as the first paragraph of the OFBiz landing page [**]
>> and then also used in our announcements and wherever we need to provide a
>> one line summary of what we do and aim to do.
>>
>> Ideas?
>>
>> Jacopo
>>
>> [*] https://en.wikipedia.org/wiki/Mission_statement
>> [**] http://ofbiz.apache.org/
>>
>>
>
>

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Michael Brohl]

+1

I have to postpone ideas, will provide them later...

Regards,

Michael


Am 11.01.17 um 10:10 schrieb Jacopo Cappellato:

Hi all,

I think it would be great if we could write a short, simple, clear,
realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
project.
The mission statement, that summarizes in 1 line what we are all here for,
could be published as the first paragraph of the OFBiz landing page [**]
and then also used in our announcements and wherever we need to provide a
one line summary of what we do and aim to do.

Ideas?

Jacopo

[*] https://en.wikipedia.org/wiki/Mission_statement
[**] http://ofbiz.apache.org/






smime.p7s
Description: S/MIME Cryptographic Signature

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Taher Alkhateeb]

+1


On 11/01/17 13:57, Pranay Pandey wrote:

+1

Sounds great.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Wed, Jan 11, 2017 at 2:40 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:


Hi all,

I think it would be great if we could write a short, simple, clear,
realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
project.
The mission statement, that summarizes in 1 line what we are all here for,
could be published as the first paragraph of the OFBiz landing page [**]
and then also used in our announcements and wherever we need to provide a
one line summary of what we do and aim to do.

Ideas?

Jacopo

[*] https://en.wikipedia.org/wiki/Mission_statement
[**] http://ofbiz.apache.org/

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Pierre Smits]

+1

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jan 11, 2017 at 11:57 AM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> +1
>
> Sounds great.
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>
> On Wed, Jan 11, 2017 at 2:40 PM, Jacopo Cappellato <
> jacopo.cappell...@hotwaxsystems.com> wrote:
>
> > Hi all,
> >
> > I think it would be great if we could write a short, simple, clear,
> > realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
> > project.
> > The mission statement, that summarizes in 1 line what we are all here
> for,
> > could be published as the first paragraph of the OFBiz landing page [**]
> > and then also used in our announcements and wherever we need to provide a
> > one line summary of what we do and aim to do.
> >
> > Ideas?
> >
> > Jacopo
> >
> > [*] https://en.wikipedia.org/wiki/Mission_statement
> > [**] http://ofbiz.apache.org/
> >
>

Re: Defining the "Mission Statement" of the Apache OFBiz project

[Pranay Pandey]

+1

Sounds great.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Wed, Jan 11, 2017 at 2:40 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> I think it would be great if we could write a short, simple, clear,
> realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
> project.
> The mission statement, that summarizes in 1 line what we are all here for,
> could be published as the first paragraph of the OFBiz landing page [**]
> and then also used in our announcements and wherever we need to provide a
> one line summary of what we do and aim to do.
>
> Ideas?
>
> Jacopo
>
> [*] https://en.wikipedia.org/wiki/Mission_statement
> [**] http://ofbiz.apache.org/
>

Re: Proposal to rename specialpurpose to plugins

[Taher Alkhateeb]

Okay Folks, Done in r1778271. Thank you all for your patience, and you 
can continue your work on /plugins (the new directory replacing 
/specialpurpose)


Cheers,

Taher Alkhateeb

On 11/01/17 10:48, Taher Alkhateeb wrote:

Hello everyone,

Minor correction, sorry for the miscount, the total number of binding 
+1 votes is 5 and total number of +1 non-binding votes is 4


Cheers,

Taher Alkhateeb

On Wed, Jan 11, 2017 at 10:28 AM, Taher Alkhateeb 
mailto:slidingfilame...@gmail.com>> wrote:


+1

Thank you everyone for your feedback. I count 9 binding +1 votes
(including me), one +0 binding vote, and and -1 non-binding vote.

I will proceed with the name change today and link it to
OFBIZ-7972. If you have any work on /specialpurpose, may I ask to
postpone it for a day or two until the rename is complete?

Cheers,

Taher Alkhateeb

On Mon, Jan 9, 2017 at 5:07 PM, Gavin Mabie mailto:kwikst...@gmail.com>> wrote:

+1 to rename as plugins

On Mon, Jan 9, 2017 at 12:23 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com
> wrote:

> Thanks for the update Nicolas
>
> Jacques
>
>
>
> Le 09/01/2017 à 11:04, Nicolas Malin a écrit :
>
>> +1 to change specialpurpose.
>>
>> For remove hot-deploy, I prefer wait to have a good
namespace management
>> to identify correctly the origin of each plugin.
>>
>> I work with Jacques on the https://issues.apache.org/jira
>> /browse/OFBIZ-6919 but I take to much time to finish this
task, so I
>> think you can realize the migration as you want ;)
>>
>> Nicolas
>>
>> Le 03/01/2017 à 10:37, Taher Alkhateeb a écrit :
>>
>>> Sure Jacques, I'll wait for you and this thread is under
discussion
>>> anyway
>>>
>>> On Tue, Jan 3, 2017 at 12:32 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com
> wrote:
>>>
>>> Taher,

 Could you please just wait 1 day or 2, maybe more?

 I'm currently working on https://issues.apache.org/jira
 /browse/OFBIZ-6919
 and its subtasks (a new one is ready but not created).
and would prefer
 to
 apply these patch before yours because it's a huge thing
and mixing both
 will not help.

 Thanks

 Jacques



 Le 02/01/2017 à 19:34, Jacques Le Roux a écrit :

 +1
>
> Jacques
>
>
> Le 02/01/2017 à 17:45, Taher Alkhateeb a écrit :
>
> Hello Everyone,
>>
>> In reference to earlier discussions and threads on the
above subject,
>> I
>> am
>> hereby proposing renaming the directory "specialpurpose" to
>> "plugins". I
>> have patch ready with all tests passing.
>>
>> Ref discussion:
>>
https://lists.apache.org/thread.html/9bb4fba6ec56bd52a5bc55e

>>
44ba1672f088ec33eeb8a1af4d16fd6d2@%3Cdev.ofbiz.apache.org
%3E
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>>
>>
>
>>
>>
>

Defining the "Mission Statement" of the Apache OFBiz project

[Jacopo Cappellato]

Hi all,

I think it would be great if we could write a short, simple, clear,
realistic but inspirational "Mission Statement" [*] of the Apache OFBiz
project.
The mission statement, that summarizes in 1 line what we are all here for,
could be published as the first paragraph of the OFBiz landing page [**]
and then also used in our announcements and wherever we need to provide a
one line summary of what we do and aim to do.

Ideas?

Jacopo

[*] https://en.wikipedia.org/wiki/Mission_statement
[**] http://ofbiz.apache.org/