Am Mittwoch, 23. Oktober 2013, 00:55:07 schrieb Cédric Krier: > On 22/10/13 10:27 -0700, [email protected] wrote: > > > None. > > > I propose that you test Tryton to understand how it works. > > > > > > > > > PS: Could you follow the netiquette and not write lines longer than 72 > > > to 78 characters. It is really painful to read such email. > > > > Céd: > > > > There are a lot of people who are attempting to contribute to the > > development of Tryton, some with the developer's perspective, some with > > the > > commercial perspective, and some manage to merge on both. By drawing on > > netiquette to limit a highly important and decisive discussion about the > > issues surrounding Tryton's abilities and competitiveness, instead of > > showing the tolerance to be open minded and respect the hours of work that > > others are putting into these issues, you show a very bad trait of > > character that I feel is absolutely inappropriate. > > Sorry but you are inverting the roles here. People not respecting the > netiquette are those who are showing a lack of tolerance and doesn't > respect the hours of work others.
I explained this in my other mail, there is mo point in shouting on the netiquette in that case. > > Instead of limiting these issues in the way you do here and have done in > > other cases, I really would welcome a much more open-minded approach, also > > with regard to people from the commercial side. > > Sorry again but I don't see any limiting behavior from me in this > thread. But I would expect from people starting discussion to do their > homework first. Here clearly there is a lack of knowledge on how Tryton > works on basis bricks as the supply management. So, what did you make believe that others did not do their homework before starting a thread? This disrespects the work of others as well. > > It is of no use to anybody here to limit discussions on issues where you - > > with all due respect and recognition - do not possess the know-how and > > in-depth knowledge to design things they may be needed. You should bring > > people together on this, instead of leaving an impression to decide that > > it's all dependent on your wisdom. > > I don't know how to take this. > But I really think the lack of knowledge is not on my side, especially > when we talk about the design of the application. No doubt that you are the master of the application. But my impression is, that functional input is only welcome if it is in line with the application design. > And just to resume, the thread is about something already done (that > happens 6 months ago) that someone doesn't understand and which is > indeed very small and with a limited impact of the system because it is > just a warning. So we are not talking about something new or something > that should be changed. May be, but to give it a proper translation, you need to understand whats behind. And it looks to me that industry best-practice is different from what was implemented. Thats what I try to understand. And to be very honest, I can easily spend my time going sailing than spending work on Tryton, if it is not appreciated. > And by the way, it is not "all dependent on my wisdom" but you have to > bring good solid arguments if you don't want to be dismissed. I'm happy to discuss SCM processes with you. I can not offer python programming experience, but some 20 years Supply Chain experience in different industries and with different applications (SAP R/3, SAP APO, i2, Manugistics, Promax) +1 for the beer in BCN Ax
signature.asc
Description: This is a digitally signed message part.
