IRC logs of #tryton for Monday, 2021-03-01 #tryton log beginning Mon Mar 1 12:00:02 AM CET 2021
-!- mathesis_(~ja1000@ has joined #tryton00:03
-!- srgdts_(~srgdts@unaffiliated/srgdts) has joined #tryton03:03
-!- springwurm(~Springwur@ has joined #tryton06:03
-!- mrichez(~Maxime@2a02:a03f:c2e8:f900:ed77:85ea:af2b:ba6e) has joined #tryton07:03
-!- Timitos(~kpreisler@2001:a61:42d:c01:762b:62ff:fe84:ed7e) has joined #tryton07:03
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton08:03
-!- rpit( has joined #tryton09:03
-!- wifasoi(8c69cf0d@mittelab/sudo/wifasoi) has joined #tryton10:03
wifasoiHi, have a (a possible problem)... I try to read the account_receivable from a party, but without success (it return the account don't specified error). The problem is that i specify an acount payable receivable (but not a default one) for each party10:03
wifasoiI tried to get the payable/receyvable account directtly but not luck10:03
wifasoi(but form the interface i can see i defined them)10:03
wifasoi(and from the database table)10:03
wifasoiwhat, in your experience, can cause this?10:03
wifasoi(i'm using tryton 5.8)10:03
cedkwifasoi: wrong context, probably it is missing the company10:03
wifasoiok, makes sense.. becouse I'm using the tryton console, so I should perform the operation in a "with Context()" block10:03
-!- thaneor( has joined #tryton10:03
wifasoithank you very much, I totally forgot it :D10:03
-!- thaneor1( has joined #tryton10:03
-!- springwurm(~Springwur@ has joined #tryton10:03
-!- ludo2(~Thunderbi@2001:912:1480:380::1) has joined #tryton10:03
-!- nicoe(~nicoe@2a02:578:852a:c00:7e2a:31ff:fe5e:b25d) has joined #tryton10:03
LordVan_quick question as i could not find anything online .. i want to display a float number, but by default it uses en_US format ('.' instead of the ',' which i want for german)10:03
LordVan_*display on a report10:03
pokoliLordVan_: i was reading your comments and I think we are working also on a similar project than yours11:03
pokoliLordVan_: is your bussines cutting steel to produce pieces?11:03
pokoliLordVan_: the numeric format depens on the user language. You should switch your user interface to german to show the numbers in proper format11:03
LordVan_pokoli, yes11:03
LordVan_user interface is german11:03
LordVan_but the generation of the odt report is ran on the server so11:03
pokoliLordVan_: sale report is rendered on the party language11:03
pokoliLordVan_: so probably setting the party language to german should fix your issue11:03
LordVan_that could be it11:03
pokoliLordVan_: we use sale_supply_production module to automatically generate production orders when the sale is confirmed11:03
LordVan_i should set the default party language to german . .for new ones it might not be set11:03
pokoliI'm still missing the part to descrive the needed operations on the parts at sale_line level11:03
LordVan_pokoli, i mostly added some test fields11:03
pokoliWe find that entering the full product details (specially prodution route) is hard for the users. So we are looking for some idea to simplify it11:03
LordVan_use a wizard maybe11:03
LordVan_i just have extra fields and will add a "material" module11:03
pokoliLordVan_: material is just a table with a name, isn't it?11:03
pokoliLordVan_: my main worries is about the operations that should be applied to the product on the production11:03
pokoliBecause we want to use the production module to compute costs and allowing the office users to know in which status of prodution is any customer order11:03
LordVan_pokoli, well i will model it after country module (loosely) as i might need it later too and i don'T want it just text based11:03
LordVan_yes i do not use production11:03
LordVan_i just need to generate the report with correct material, thickness, painted or not,..11:03
LordVan_pokoli, i was gonna upload my code to my github repo again anyway11:03
LordVan_(nothing special about it)11:03
LordVan_so i can do that later and show you, but i doubt there's much you'd not already know11:03
LordVan_the whole production process here is documented first on paper (hence why i need to generate the reports when an order is placed)11:03
pokoliLordVan_: we started on a first step where we do not use production, and just sale orders and related invoices11:03
pokoliand now are on the second phase where we want to introduce productions11:03
LordVan_pokoli, same here - though i am not doing invoicing with tryton just yet11:03
LordVan_i have some things I need to still work out first before generating invoices11:03
pokoliLordVan_: for generaing a report of material is just about adding some properties to products (or sale lines) and then print this information from the sale order in a custom report11:03
LordVan_since I am doing most of this myself it is not an issue to split it into small stages11:03
LordVan_pokoli, yes but i also need to write my own report class soon for some .. a bit special cases (like where one sale_line needs to generate multiple pages, or multiple sale_lines need to be combined on one page)11:03
LordVan_for that report i can't (always) just take every sale_line and use that but am going to have to post-process first what can/should be merged or split11:03
LordVan_-- to explain .. a sale_line can contain an assembly .. but that then consists of parts of different materials, metal sheet thickness,.. and each of those needs a seperate printed out page for production)11:03
LordVan_and in other cases we want more sale_line rows to be on one page because the customer does not want individual prices and they are the same material + thickness11:03
pokoliLordVan_: I think I now your problems11:03
pokoliLordVan_: using production module will probably make it easier11:03
LordVan_we have too many prototypes or just simply one-off things to use production .. it would over-complicate it11:03
pokolibecause on production is where you declare what needs to be done on each material11:03
LordVan_i might start using production later on for some repeatedly ordered parts, but for now ..11:03
pokoliLordVan_: the production should be automaticall generated with sale_supply_production module11:03
LordVan_pokoli, that would be a huge task11:03
LordVan_with likely barely any gain11:03
LordVan_for 90% of the orders11:03
pokoliLordVan_: why you sai there will be no gain?11:03
pokoliLordVan_: production is what contains all the tasks to be done, material to be used and the planning11:03
pokoliLordVan_: indeed you will have an extra operation for cutting the main material into the pieces that can not be tracked at sale level11:03
pokoliBecause the cutting groups pieces of several orders11:03
LordVan_pokoli, in theory yes11:03
LordVan_but that would require ahead of time planning of all those things11:03
LordVan_we do most of our orders rather short notice11:03
LordVan_sometimes order like one day 13:00 and want to pick up next morning 7AM11:03
LordVan_there is no point trying to plan/schedule cutting11:03
LordVan_we'd throw/change the plans more often than not11:03
LordVan_we rarely have stuff that actually cuts for a long time on one material11:03
pokoliLordVan_: for that reason there is the shipping_date on the sale order11:03
pokoliLordVan_: if you do not have any shipping date the order is scheduled on a fixed period (i.e: 3 days)11:03
pokoliLordVan_: but once you have an order that should be picked up next morning you just set the shipping_date to tomorrow11:03
LordVan_pokoli, i completely agree with you that ideally that all would work out great .. but for a small company where a lot of the workers are pretty much computer illiterate11:03
pokoliTryton will create all the related documents with this dates in mind, so the production users know on which orders should work first (ordered by date) without needing to care on anything else11:03
LordVan_it might be something in the (further) future11:03
LordVan_but that'D require major organisational changes company wide11:03
LordVan_that simply are not going to happen now11:03
LordVan_if i may ask .. how large is the company you are doing this project for?11:03
pokoliLordVan_: not so much, 15 employees working11:03
pokoliLordVan_: indeed they are working with papers like you describe (but they generate them using an excel file)11:03
LordVan_our project sheets used to be manuall written (Every single sheet every time except for some copy paste) until a few years ago when I implemented it in dolibarr - which did not work out11:03
LordVan_now we generate a large part of the (not too complex) ones fully with tryton already11:03
LordVan_we got like 15 employees total .. (including part time office,..)11:03
LordVan_pokoli, do they have a lot of "plannable" orders? we just got lots and lots of small, low quantity orders11:03
LordVan_so the complexity of production module is .. well11:03
LordVan_would probably require me myself to deal with most of it tbh as our office staff wouldn'T be able to handle that (qualification/knowledge wise)11:03
pokoliACTION is on phone11:03
pokoliLordVan_: 150 orders per months moreless12:03
-!- mariomop(~quassel@ has joined #tryton12:03
pokoliLordVan_: there are ones which are just 1 o 2 quantities of an item12:03
Hirschbeutelwe all have very similar problems 😉12:03
Hirschbeutelthe coating as well very often a complete individual request.12:03
HirschbeutelI have processdefinition on sale line: like (sanding, priming, topcoat, polishing) - this ar lines with the name and a text description if sales person ask for them12:03
pokoliHirschbeutel: we have another project related to custom T-Shirts and they have similar needs12:03
pokoliand I also had been asked for some option to define the full production on sale quotation. SO you need to plan everything in advance and compute the costs (and prices)12:03
pokoliThen if the customer agrees, you should follow the plan if not it can be thrown away12:03
pokoliHirschbeutel: i think there is place for some standard modules there but I still do not have an idea on how to design it12:03
pokolifor now we are using custom code to make the projects work12:03
Hirschbeutelme to - we shoul work on some generic12:03
pokoliHirschbeutel: agree but generic requires time to think it carefully :)12:03
Hirschbeutelpokoli: I can abstract what I do for in our case12:03
pokoliHirschbeutel: it will be a starting point12:03
pokoliHirschbeutel: but probably I prefer to comment it here because for me there are like two funcionalities12:03
pokoli1. Specify some production details at sale level12:03
pokoli2. Create a planning to know the costs of a production and use it at quotation level12:03
pokolithe second can be used without sale module to create plan diferent versions of a production BOM/Routing configuration12:03
pokoliIIRC when I was at nantic we implemented a module for the second12:03
Hirschbeutelbecause in our case ist a fundamental part of all: most of clients do not know the process - sale man ask them to know as many as he can and than searches for the best production process12:03
Hirschbeutelnot searching - there could be a generic process that fits or we need a customized based on a generic or it is completly custom12:03
Hirschbeutelin our case we can calculate based on the steps needed in the process - so price differs from some variables but we can calculate based on process_step12:03
HirschbeutelI have a process_template - you can select it on sale, a copy of the process_lines is made - leave it as it or change them to your needs12:03
Hirschbeutelso we have the design :)12:03
pokoliHirschbeutel: our prices also depen on the processes12:03
pokoliHirschbeutel: indeed we added a product to the production_operation and we allow to add operations on sale line which are added latter to the production process12:03
pokoliHirschbeutel: unit_price is computed with the price of the product + the prices of the operations with product (extra services)12:03
HirschbeutelI don't have a product - I have process_steps with some variables (like squaremeters, material etc)12:03
Hirschbeutelmore like a fluid bom13:03
LordVan_for us most of the time the cost is only calculated after manufacturing13:03
LordVan_because there is no time to calculate beforehand or it is just not well enough defined13:03
HirschbeutelLordVan_: It is not unusual to charge according to the work done13:03
HirschbeutelLordVan_: project module can do that :D13:03
Hirschbeutelthats wy for me project is my prefered way and I will fight my whole live to convince cedrik13:03
Hirschbeutelfor some companies a sale creates a kind of project13:03
LordVan_Hirschbeutel, haha13:03
HirschbeutelI think the blueprint to invoice services is similar - but it depends of definintion of service13:03
LordVan_I do agree .. we consider nearly each sale a project13:03
LordVan_tbh i haven'T actually looked at the project module too much13:03
LordVan_what i need right now works well with just sale and sale_line adjustments13:03
LordVan_the special cases are a different story13:03
Hirschbeutelso you can be one of my knights in the everlasting fight to make the project module omnipotent13:03
Hirschbeutelit should manage my live as welll13:03
LordVan_i would install the project module to have a look at it now, but i only have the production instance running and i don'T know if i want it on there haha13:03
TimitosHirschbeutel: its not about fighting its about convincing13:03
Hirschbeutelno - cedrik  is right, I was joking13:03
Hirschbeutelits one of the features of tryton: you have possibilities but you have to choose13:03
Hirschbeutelbut convincing int this case means fighting, am I wrong? :)13:03
HirschbeutelI think what we know is: there is a need for some modules handling small to no series production13:03
Timitosyes. many of us do need modules for this. there are already some threads on discuss about that and maybe we only need to intensify the discussion about these needs to find the common patterns13:03
Hirschbeutelthe common pattern is that there is no pattern, because the USP in this case is to differentiate :)13:03
HirschbeutelI would like to work on this ....13:03
Timitosif there is no pattern then we all end with custom modules13:03
Hirschbeutelpossibly we can find a very reduced core concept13:03
Hirschbeutelfirst is to find the document where the coding of the request starts13:03
Hirschbeutelfor me this is sale:opportuity - but you know that I have implementet it on sale13:03
HirschbeutelLordVan_ statet that sale_opportunity in small companies is one step to much - and I think this was the reason why I did it on sale13:03
Hirschbeutelbut in review sale_oportunity seems better13:03
LordVan_Hirschbeutel, i have most things on sale that i need13:03
LordVan_starting with sale_opportunity would add complexity and me having to add a lot of stuff in 2 places13:03
Hirschbeutelyes - I know - for this reason I have my stuff on sale as well13:03
Hirschbeutelthis should be discussed13:03
Hirschbeutelwho starts the thread?13:03
LordVan_feel free i am quite busy right now ;)13:03
Hirschbeutelpass the baton to > ...13:03
HirschbeutelOk - will think about it - without thinking I will post only chaotic stuff :)13:03
LordVan_same here13:03
Hirschbeutelcedk: ping14:03
-!- springwurm(~Springwur@ has joined #tryton14:03
pokoliLordVan_: if you are manufacturing, the production modules takes care of automatically computing the costs for you15:03
LordVan_pokoli, they would .. if i knew beforehand - or it would be feasible to enter all that15:03
LordVan_as i said i will probably use it for repeatedly ordered parts later on15:03
pokoliHirschbeutel: about sales and projects link is already discussed here:
pokoliit still requires some love from my side15:03
LordVan_and then look into if i can simplify the process enough to use it for the simple orders too15:03
cedkHirschbeutel: pong15:03
pokoliLordVan_: for repetitive orders it works out of the box. As you will have the Bill of Materials and the route of Operations previously created15:03
Hirschbeutel@pokoli: I have similar on sale - linking it and an action: create project15:03
Hirschbeutelin this action I handle the conversion from the data encoded on sale to that ones needed for the project15:03
Hirschbeutelcedk: I startet to work on sale_point first to understand it right. the TODO create an invoice  - do you mean a normal invoice with the sequence of the standard invoices?15:03
Hirschbeutelcedk: I need to read the legal requirements - but I think this depends on country. will ask Timitos  - I guess in Germany it is a receipt and and the "invoice" is the same thing only with an Adress on it ....15:03
pokoliHirschbeutel: IIRC in spain it is possible to just create an account move which resumes all the tickets15:03
pokoliHirschbeutel: only requirement is that you do not identify the customer15:03
Hirschbeutelyes - thats the receipt15:03
-!- lucascastro( has joined #tryton15:03
pokoliHirschbeutel: not sure but probable we will need to create an invoice without identify the customer (no tax_identifier) because those records should be send to SII15:03
pokoliSII -> Send all invoices to tax authority using a webservices15:03
LordVan_same here15:03
Hirschbeutelpokoli: if I understood right the use case is: customers pays and asks for an invoice - because he want to get back taxes or to feel more comfortabel or whatever15:03
pokoliHirschbeutel: then you should ask for the tax_identifier and identify the customer to create a normal invoice15:03
Hirschbeutelpokoli: one moment - will look at some in my office - but I feel that nobody asking me for that (cause I don't know without going back to my office ;)15:03
Hirschbeutelpokoli: no - only a minimal address and a line telling: paid in cash on date15:03
LordVan_about my numeric formant question earlier @pokoli15:03
LordVan_the sale party has german set as language15:03
LordVan_so is tryton UI15:03
LordVan_so it must be the server side15:03
LordVan_not respecting that15:03
-!- htgoebel( has joined #tryton15:03
pokoliLordVan_: but where are the wrong format shown? On the user interface or on the report?15:03
LordVan_odt report15:03
LordVan_it shows 2.0 instead of 2,015:03
pokoliLordVan_: custom report?15:03
LordVan_not yet no just the normal sale report15:03
LordVan_with custom odt ofc15:03
pokoliLordVan_: then probably you are missing the set_lang call in the odt template15:03
LordVan_that could be15:03
LordVan_i shall check out the original template again.15:03
htgoebeldoes Tryton already provided some means of a "waiting list" for a service?15:03
htgoebelLike when you need a place in the hospital: You put your name on the list and if a bed is available you are asked whether you want to take it. You can jump of the list anytime and there is no contract until you actually agree on taking the bed.15:03
pokoliACTION is happy to have an active chat today with the community :)15:03
-!- mniip(~mniip@freenode/staff/mniip) has joined #tryton15:03
pokolihtgoebel: we usally manage that with states15:03
pokolihtgoebel: for example, on outgoing list there is a "waiting" state which is all the shipments that should be picked15:03
pokolihtgoebel: and the shipment is not picked/packed/sent until it goes forward in the workflow15:03
htgoebelpokoli: This would be far to late in the process.15:03
htgoebelpokoli: Wait - need to rephrase15:03
pokolihtgoebel: to be honest I do not know your process because you did not explain it to us :)15:03
pokolijust giving some ideas15:03
htgoebelpokoli: When using a state for some picking, the process has advanced quite far already.15:03
htgoebelThe waiting is at the very beginning, the is not even a contract, not even a binding sale offer.15:03
htgoebelLike when you are waiting to get a place on the next ship, a room in a seniors residence, a kidney transplantation: Your name and contact is put on a list and if everybody in front of you has been served, it's your turn to decide whether you still want to agree on some contract15:03
htgoebelpokoli: Implementing this from scratch is easy: Just an ordered lists of parties.15:03
htgoebelpkoli: I just wonder if Tryton already implements such means.15:03
pokolihtgoebel: if you have some asset to be rent, there is the sale_subscription_asset module15:03
pokolihtgoebel: otherwise it's just o quotation that need to be accepted15:03
htgoebelpokoli: Thx.15:03
pokolihtgoebel: once you have a table with a many2one to party, there is a list of parties which you can order on any field (for example creation data)15:03
pokolihtgoebel: not sure if that helped so much, but your concept is very abstract15:03
htgoebelpokoli: Well, a waiting list is quite abstract ;-)15:03
pokolihtgoebel: what I mean is that the implementation can be very diferent depending on the problem to solve16:03
pokolihtgoebel: following on your examples, on the ship you should agree on the days before confirming the place and make it not available for others16:03
pokolihtgoebel: a room in seniors residence can be managed out of the with sale_subscrition_asset module:
pokolihtgoebel: and a kidney translplantion probably you start looking at the kidney once you have the need of it (a kind of sale_supply)16:03
pokoliso for me there should be a diferent implementation for each of your examples16:03
htgoebelpokoli: Thanks. I actually missed that I need to wait for an answer (or timeout) before offering to the next one on the list.16:03
htgoebelpokoli: For now - i still need to convince my CIO ;-) I'll go with a very simply many2one table.16:03
htgoebelEverything else needs to be defined later.16:03
pokolihtgoebel: if your CIO needs a videoconference to resolve doubts I will be happy to help on that16:03
pokolihtgoebel: but please have a concrete list of questions so we can answer them16:03
pokolihtgoebel: and if you do not mind we can make it like an interview and share it on tryton's youtube chanels for others16:03
Hirschbeutelhtgoebel: I have a waiting list for books16:03
Hirschbeutelhtgoebel: (party, book, date of request) more or less - if book returns, next user gets a message - after a defined delay the next - first comes first serve16:03
htgoebelpokoli: Thanks for the offer - the "CIO" actually is not the CIO but the (main and single) developer of the current solution.16:03
htgoebelpokoli: This is why I asked for technical features.16:03
htgoebelpokoli: Anyhow, my presentation is tomorrow and I'm about to structure what I have up to now.16:03
htgoebelHirschbeutel: Sounds very much like what I meant :-)16:03
pokoliHirschbeutel: did you have a waiting list for webshop?16:03
htgoebelhirschbeutel: If this is publicly available, I'd like to present it tomorrow. Otherwise I'd just tell there already is such an solution.16:03
pokoliHirschbeutel: we have one where all the users are noticed when a product is received on the warehouse16:03
Hirschbeutelhtgoebel: you can tell him there is a solution for everything, the only problem is to know where16:03
Hirschbeutelpokoli: not yet - but this is a rquirement16:03
Hirschbeutelpokoli: not having this is lame :)16:03
Hirschbeutelpokoli: we should start a repo with shop plugins16:03
pokoliHirschbeutel: did you think there is some usage without webshop?16:03
Hirschbeutelpokoli: yes - possibly if you think like: a sales person can encode such a line and forget about this - so system will do the marketing16:03
Hirschbeutelpokoli: so the answer is YES!16:03
Hirschbeutel(mechanism, email*, date, product)16:03
pokoliHirschbeutel: indeed we just store the party and the product16:03
Hirschbeutelemail* for rpc from outside16:03
pokoliHirschbeutel: and we have a state field to see if the request has been received or not16:03
pokoliHirschbeutel: and when the state is updated to received we trigger a notification using notification_email module16:03
Hirschbeutelwhich request?16:03
Hirschbeutelmail state?16:03
pokoliHirschbeutel: request -> the record of the waiting list (product and party)16:03
Hirschbeutelpokoli: do not understand - if there is a line, a request happend, or not?16:03
pokoliHirschbeutel: there is a line with two states: Waiting and Received16:03
pokoliHirschbeutel: once the party adds the product to the waiting list, a line with party and the product is created16:03
pokoliat this stage the line is in waiting state16:03
Hirschbeutelah - know I got it16:03
pokoliHirschbeutel: and when the product is recieved the state of the line is updated to received16:03
pokoliFrom there you can use the marketing_automation module or the notification_email16:03
pokolior nothing :)16:03
HirschbeutelI delete the line - because there are to many requests and nobody needs this information historical16:03
Hirschbeutelbut with state is good as well -depends off the number of requests and if the company sees this a a GDPO issue16:03
Hirschbeuteldon't know - for legal stuff deleting is always the best solution :)16:03
Hirschbeutelburn it ....16:03
Hirschbeutelpokoli: send me a offer :)16:03
pokoliHirschbeutel: we prefer to save the line to see if the customer purchased the product at the end or not16:03
pokoliHirschbeutel: for example if we send a notification and the party does not buy the product in 7 days we can send another mail, or call him16:03
pokoliYou know, marketing is evil at some points. They now more from us than ourselves16:03
Hirschbeutelpokoli: I would hate you for that :)16:03
Hirschbeutelpokoli: but possibly buy to get rid of your calls16:03
-!- rpit1( has joined #tryton16:03
Hirschbeutelpokoli: in our case, the products are in short supply - if you don't get back to us, you're out of luck.16:03
Hirschbeutelpokoli: but this all is the same module16:03
Hirschbeutelpokoli: I'll take yours16:03
pokoliHirschbeutel: you can always read the customer to waiting list automitcally if there is not stock and they did not have luck to buy16:03
Hirschbeutelpokoli: gimme offer - i will sell it16:03
Hirschbeutelpokoli: need to migrate all that stuff, no time to write new features16:03
pokoliHirschbeutel: indeed to make it generic we should probably need a draft state, and a test to ensure that when adding to the waiting list there is not stock16:03
Hirschbeuteli could contribute as well :)16:03
pokoliHirschbeutel: and a warehouse where the customer want's the product16:03
Hirschbeutelpokoli: why?16:03
pokoliHirschbeutel: because in our case we have a single warehouse but I it should be possible to have and order between warehouses16:03
pokoliHirschbeutel: because we may have a warehouse on germany and another in Barcelona16:03
pokoliHirschbeutel: if there are a lots of demand of products in Germany and we have stock on Barcelona, we may delivery directly16:03
Hirschbeutelpokoli: yes - in this case it would be cool16:03
pokoliHirschbeutel: that the work of going from a custom solution to a generic one that can be reused16:03
pokoliHirschbeutel: i let you open a feature request on the forum :)16:03
Hirschbeutelsecond task I put on my list ...16:03
pokoliHirschbeutel: i throw the entire list away because it was to large xD16:03
Hirschbeutelpokoli: I was ask to help out in a project and now fixing the whole day16:03
pokoliHirschbeutel: it seems clear that they need help on fixing a lot of issues.16:03
pokoliHirschbeutel: You should ask them to provide you a complete test suite to avoid the errors16:03
Hirschbeutelpokoli: the fixes have changed to new features ;)16:03
Hirschbeutelpokoli: they own me16:03
pokoliHirschbeutel: this also happen on tryton bug tracker, bugs are converted to new features some times :P16:03
-!- springwurm( has joined #tryton18:03
-!- jani-matti( has joined #tryton18:03
-!- lucascastro( has joined #tryton18:03
-!- lucascastro(~lucascast@ has joined #tryton18:03
-!- lucascastro( has joined #tryton18:03
-!- htgoebel( has left #tryton19:03
-!- nicoe(~nicoe@2a02:578:852a:c00:7e2a:31ff:fe5e:b25d) has joined #tryton19:03
-!- ludo2(~Thunderbi@2001:912:1480:380::1) has joined #tryton19:03
-!- ludo2(~Thunderbi@2001:912:1480:380::1) has joined #tryton21:03
-!- nicoe(~nicoe@2a02:578:852a:c00:7e2a:31ff:fe5e:b25d) has joined #tryton21:03
-!- thaneor( has joined #tryton22:03
-!- thaneor1( has joined #tryton22:03
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton23:03

Generated by 2.16.0 by Marius Gedminas - find it at!