HI Piere,
inline...
Am 21.01.20 um 15:56 schrieb Pierre Smits:
Hi all,
The mission of the project is, in line with the ASF, to provide software
for the greater good and offering (potential) adopters a choice. In the
projects case this is done through providing the OFBiz works (each and all
Thanks Pierre,
I second that, I would not write it better!
Jacques
Le 21/01/2020 à 15:56, Pierre Smits a écrit :
Hi all,
The mission of the project is, in line with the ASF, to provide software
for the greater good and offering (potential) adopters a choice. In the
projects case this is done
Hi all,
The mission of the project is, in line with the ASF, to provide software
for the greater good and offering (potential) adopters a choice. In the
projects case this is done through providing the OFBiz works (each and all
products, as well as the supporting tooling for enabling contributors
Le 21/01/2020 à 00:36, Mathieu Lirzin a écrit :
Hello,
Taher Alkhateeb writes:
While working on all the above, I never faced major obstacles. But the
reason that I did not is I always made a complete, well written
argument about what I'm trying to implement. I always ask for a pair
of eyes
Hello,
Taher Alkhateeb writes:
> While working on all the above, I never faced major obstacles. But the
> reason that I did not is I always made a complete, well written
> argument about what I'm trying to implement. I always ask for a pair
> of eyes to look at my code and give me feedback, and
Great Message Taher!
Jacques
Le 20/01/2020 à 11:50, Taher Alkhateeb a écrit :
Hello Mathieu and all,
Thank you for this interesting and engaging thread. Before I make my
input, I would like to note that Apache OFBiz and its community from
my experience is welcoming of change and improvements.
Hello Mathieu and all,
Thank you for this interesting and engaging thread. Before I make my
input, I would like to note that Apache OFBiz and its community from
my experience is welcoming of change and improvements. In my earlier
days in the project we went through massive changes to the system
Thanks Mathieu,
It's quite clear to me now
Jacques
Le 11/01/2020 à 21:52, Mathieu Lirzin a écrit :
Hello Jacques,
Jacques Le Roux writes:
Le 05/01/2020 à 18:32, Mathieu Lirzin a écrit :
Michael Brohl writes:
This project is not only about tech, it has a user base with serious
business
Hello Paul, Jacopo and Olivier,
Paul Foxworthy writes:
> Being clearer about it would be a good thing. There is still the
> potential that a change that seems simple and straightforward to one
> contributor is disruptive to others. And if it truly is disruptive, we
> should collaborate on what
Hello Jacques,
Jacques Le Roux writes:
> Le 05/01/2020 à 18:32, Mathieu Lirzin a écrit :
>>
>> Michael Brohl writes:
>>
>>> This project is not only about tech, it has a user base with serious
>>> business running on base of OFBiz. This has always to be considered as
>>> serious as good
Hello,
Here are two clarifications about removing the “component-load.xml”
feature.
Michael Brohl writes:
> Am 05.01.20 um 18:32 schrieb Mathieu Lirzin:
>
>> effectively optional (like the marketing example you brought) it should
>> eventually be moved in the official plugins if we actually
Hi, everybody,
It is not easy to add something in the discussion among the different
arguments! (and on the different topics)
I will, however, try to give some summary of my position on the various
subjects discussed.
1) As Jacques recall "Community over code" so :
1.1 : It is important to
Hi Michael,
I purposely created a new thread because then there were no answers and I
wanted to create a new thread not inserted in the initial thread.
But because I got issue with my temporary IP address (due to my Internet
provider) it was sent later.
OK, copying there...
Jacques
Le
ns" directories with the exception
of the “config” directories is considered part of OFBiz public API or
not? What do people think?
For the record, Without the ability to safely refactor a large subset of
the codebase that have the status of “implementation details”, I will
simply stop c
There will always be a tension between guaranteeing backward compatibility
for the existing user base and the efforts to maintain our codebase,
enhance/refactor/innovate it.
Considering the peculiar nature of OFBiz, I don't think that trying to
define the areas that are part of the "public API"
Hi Jacques,
you've created another mail thread with exactly the same title. The
first thread already has answers which would get lost if your new thread
would be answered.
I propose that you simply answer the first thread directly.
Thanks,
Michael
Am 08.01.20 um 05:38 schrieb Jacques Le
On Mon, 6 Jan 2020 at 20:29, Samuel Trégouët
wrote:
> what is OFBiz public API?
>
> In my opinion we need an answer for this question otherwise we need to
> discuss every single changement! which seems to be really cumbersome!
> And even if we discuss every single changemen
Le 07/01/2020 à 00:56, Mathieu Lirzin a écrit :
Hello,
Jacques Le Roux writes:
Le 06/01/2020 à 10:29, Samuel Trégouët a écrit :
what is OFBiz public API?
In my opinion we need an answer for this question otherwise we need to
discuss every single changement! which seems to be really
Hi All,
Following Mathieu's question about "OFBiz public API" and the points he already
mentioned I decided to create a new thread.
I don't know what will happen with the other tread (mostly about
removing/replacing component-load.xml). That's not the subject here.
Mathieu wrote:
<>
I
? In software library/framework it
is quite easy to answer: a big changement is a breaking in public api.
It's not about being a big change, it's about breaking existing
mechanisms/configurations on the user side.
So here is the question from Mathieu:
what is OFBiz public API?
In my opinion we
Hello,
Jacques Le Roux writes:
> Le 06/01/2020 à 10:29, Samuel Trégouët a écrit :
>>
>> what is OFBiz public API?
>>
>> In my opinion we need an answer for this question otherwise we need to
>> discuss every single changement! which seems to be really cumb
is the question from Mathieu:
what is OFBiz public API?
In my opinion we need an answer for this question otherwise we need to
discuss every single changement! which seems to be really cumbersome!
And even if we discuss every single changement how to decide it is good
for our community: *one
(re)Forwarded at Michael's request
Message transféré
Sujet : Re: What is OFBiz public API?
Date : Sun, 5 Jan 2020 20:33:03 +0100
De :Jacques Le Roux
Organisation : Les Arts Informatiques
Pour : dev@ofbiz.apache.org
Hi Mathieu,
Inline too...
Le 05/01/2020 à
software library/framework it
is quite easy to answer: a big changement is a breaking in public api.
So here is the question from Mathieu:
what is OFBiz public API?
In my opinion we need an answer for this question otherwise we need to
discuss every single changement! which seems to be really
wing if the internal organisation of the
files inside the "framework/applications" directories with the exception
of the “config” directories is considered part of OFBiz public API or
not? What do people think?
See my comments above. We cannot reduce the discussion to a public API
because of
files inside the "framework/applications" directories with the exception
of the “config” directories is considered part of OFBiz public API or
not? What do people think?
For the record, Without the ability to safely refactor a large subset of
the codebase that have the status of “implemen
26 matches
Mail list logo
