# Friday, April 21, 2017¶

## Fictive team meeting¶

Here is what I would say in a team meeting if we had one now.

Yesterday I said to Tonis that our #1320 (named “releases@jane”) should be reserved for actual work on the Jane site and not e.g. for general discussion. That was a mistake by distraction. This ticket is for everything about Jane which “does not deserve a ticket on its own”. We should rename it to “misc@jane”.

We have site-specific named tickets:

Some other named tickets:

• #268 Triage (write tickets, teamwork planning, accept pull requests, …)
• #269 Travis (Getting Lino to pass on Travis CI)

I now see that Tonis started to use #1672 (Stable branches for git) when working on what I would assign to #269. This shows that it was time to start having named tickets.

I named the following tickets about “Investing into a given team member”:

Yes, there is no named ticket for “Luc” yet. That does not mean that I am perfect. It is rather because nobody ever explicitly invested time into teaching me something (at least not since our ticketing system exists). Im am looking forward to the day when this ticket will be created.

Tonis, why did you choose “Reference tickets” as the label and RefTickets as internal name for that table which shows our named tickets. I would have choosen “Named tickets” and NamedTickets respectively. Yes, it is possible that my usage of the words “name” and “reference” in Lino is a bit chaotic. Observations:

• The words “name” and “reference” are almost synonym, they both are a convention of a group of people who agree to use it when referring to something.
• A “reference” is usually an abbreviated or codified “name”, and the uniqueness is considered more important.
• We have the BabelNamed mixin which defines a field “name” whose verbose_name (label) is “Description”. That field is not required to be unique, and it is not even a name (according to above definitions).

Tonis wrote: “One strange thing is I have to manually import my workflows.py file, it looks as if it’s done automatically in courses and other plugins, however not with meetings… If you have some insider knowledge about this please fill me in.”

I guess that this insider knowledge is workflows_module site attribute. You can define one “workflows module” per application which “collects” predefined workflow definitions by importing them.

Yes, Lino does not automatically import any workflows.py file. Actually the only hard-coded magic names which Lino adds to Django’s models.py file are desktop.py and mobile.py (according to your design_name attribute).

Note that this design_name attribute is a deprecation candidate because we will probably decide to rather implement mobile layouts using mobile_view.

## Why Tx25 is failing¶

GitKraken helped me to find the probable reason for #1706. In file RetrieveTIGroups.wsdl the soap address has changed. Before commit 0782decb in Welfare (commit message “#739 (r:CourtName) tested and fixed”) we had:

<soap:address location="https://bcssksz-services-%(cbss_environment)s.smals.be:443/SOA4520/RetrieveTIGroupsService/retrieveTI"/>


and since then we have:

<soap:address location="https://b2b-%(cbss_environment)s.ksz-bcss.fgov.be:4520/RetrieveTIGroupsService/retrieveTI"/>


Note that in both cases, Lino will replace %(cbss_environment)s by “prod” or “accpt” or “test”.

I could find the responsible commit using the CLI:

$git log lino_welfare/modlib/cbss/WSDL/RetrieveTIGroups.wsdl  But how can I show the changes in a given file for a known commit? I tried the following: $ git diff abd8fb76eeea0cd7de46849c498252010782decb lino_welfare/modlib/cbss/WSDL/RetrieveTIGroups.wsdl


But this didn’t show anything. This is of course an old problem. Explanation and answer as usual on stackoverflow.

## Meeting with Tonis¶

meetings.MembersByMeeting(lists.MembersByList):
master = 'lists.List'
master_key = None

@classmethod
def get_filter_kw(self, ar, **kw):
if ar.master_instance is None:
return
kw.update(list=ar.master_instance.partner_list)
return kw


## Meeting with Tanel¶

We decided that the Vilma project no longer uses Lino Noi but gets its own application. So I created a new project Lino Vilma and renamed the existing demo project in book to lino_book.projects.liina. We removed most functionality from Vilma, it is currently just a shared contacts and skills management.

Side effects:

TODO:

• Add a new plugin “resources” : a resource is an object of public interest, more or less available for “renting”, usually having a responsible organisation and a contact person
• Add filter parameters to partners : who offers a given skill? who has a (given) role in a (given) organization?
• Continue translation to Estonian.

These tasks are not urgent because the Vilma project is going to sleep now until we find money for it.