Note: keep in mind ws/3 will prolly be json-based (and ws/2 supports json already), so mbxml will need work anyway
2017-05-16 13642, 2017
Sophist-UK
If we did that, we culd then centralise everything to do with that metadata into the one file - by creating apis to allow them to add metadata definitions and mappings for each format.
2017-05-16 13648, 2017
Sophist-UK
So, the release mbxml plugin would define the metadata tags it will populate, and tell each format what the mapping is from those into file tags.
2017-05-16 13651, 2017
adhawkins
bitmap: Ok. I'll hold off then, if it helps?
2017-05-16 13609, 2017
bitmap
sure
2017-05-16 13640, 2017
zas
Sophist-UK: picard plugins are python modules, so .. it is basically a code rework and clean up, i don't like the idea of making core functionnalities "plugins", but defining proper API and better use of modules is fine
2017-05-16 13642, 2017
Sophist-UK
Then if we want to add support for new metadata, we can make all the changes in the one .py file.
2017-05-16 13646, 2017
samj1912
Sophist-UK part of the reason I am waiting for the summit before starting to work on mbxml related refactoring
2017-05-16 13628, 2017
Sophist-UK
They would be plugins in the same way that CA is done using plugins i.e. internal.
2017-05-16 13630, 2017
samj1912
It might just be useless by the time 2.0 reaches its first stable version
2017-05-16 13646, 2017
samj1912
And we might have mbjson
2017-05-16 13651, 2017
Sophist-UK
But that would not stop someone writing a new plugin.
2017-05-16 13602, 2017
samj1912
Not sure what the plans are for a new WS
2017-05-16 13610, 2017
zas
samj1912: none for now ;)
2017-05-16 13639, 2017
zas
but preliminary discussions show we aren't fond of xml ;)
2017-05-16 13647, 2017
Sophist-UK
My thoughts at present are we should not rewrite the xml handling code - just break it up into pieces, and centralise. I think it will make a switch to json easier when it comes.
2017-05-16 13617, 2017
Sophist-UK
We could switch to ws2 json if we want to put the effort into it.
2017-05-16 13634, 2017
zas
Sophist-UK: +1 to split actual picard preprocessing of mb data from mb data, currently this is a bit mixed up
2017-05-16 13616, 2017
Sophist-UK
And my profiling of Picard shows that the heaviest CPU load is in reading XML into Picard. I am assuming that json will be less processor intensive (esp if we can use a C-based Python standard module to do it).
2017-05-16 13611, 2017
Freso
So I think the summary is that Sophist-UK can go ahead with their proposed changes? (And I guess we can discuss more specifically in the PR?)
2017-05-16 13649, 2017
zas
yes, if the goal is to split xml-related stuff from the rest
2017-05-16 13659, 2017
zas
we'll need it at some point anyway
2017-05-16 13619, 2017
zas
and in the process i guess a lot of code cleanup will happen
2017-05-16 13629, 2017
zas
so that's a go from me
2017-05-16 13635, 2017
Sophist-UK
I won't have the time to code a switch from xml to json. But I might have time to split mbxml and create the format apis.
2017-05-16 13655, 2017
Freso
I think that's fine.
2017-05-16 13612, 2017
samj1912
I will help, since this is pretty close to my Gsoc phase 2 part.
2017-05-16 13620, 2017
Sophist-UK
Great.
2017-05-16 13625, 2017
Freso
Alright.
2017-05-16 13645, 2017
samj1912
Wrap up and good night folks o/
2017-05-16 13647, 2017
Freso
So that's tonight meeting settled? Are we on again next Tuesday, or are you set to go for a while samj1912? :)
2017-05-16 13606, 2017
Sophist-UK
I still have my multi-level work paper that needs discussing.
2017-05-16 13609, 2017
samj1912
I think I have enough to code for a a couple of weeks
2017-05-16 13613, 2017
Freso
Oh, right.
2017-05-16 13625, 2017
Sophist-UK
If we can meet one Tuesday in the next couple of weeks that would be good.
2017-05-16 13632, 2017
Freso
samj1912: ^ ?
2017-05-16 13643, 2017
samj1912
Next Tuesday for works paper?
2017-05-16 13644, 2017
zas
I'm not against a Picard meeting on next tuesday, but we can make it shorter ?
2017-05-16 13653, 2017
Freso
We could potentially also do it at a "regular" Monday meeting (the last few Mondays have been rather short).
2017-05-16 13655, 2017
samj1912
Yes. I would also like that
2017-05-16 13656, 2017
zas
but i think we should keep one per week
2017-05-16 13656, 2017
CatQuest
+1
2017-05-16 13617, 2017
Freso
So next Tuesday, 18:00–18:30 UTC
2017-05-16 13624, 2017
zas
works for me
2017-05-16 13627, 2017
Sophist-UK
This one has been quite short.
2017-05-16 13628, 2017
CatQuest
yes please keep it as tuesday
2017-05-16 13630, 2017
Sophist-UK
Works for me.
2017-05-16 13630, 2017
samj1912
👍
2017-05-16 13637, 2017
CatQuest
:D
2017-05-16 13640, 2017
samj1912
Sophist-UK still an hour :p
2017-05-16 13642, 2017
Freso
Sophist-UK: It's been almost an hour, which is our regular meeting time limit. :)
2017-05-16 13611, 2017
Freso
Alright. Next Picard meeting will be next Tuesday, 18:00–18:30 UTC.
2017-05-16 13612, 2017
samj1912
And we had a clear agenda this time with almost 0 disagreements :p
2017-05-16 13612, 2017
Sophist-UK
Doesn't matter.
2017-05-16 13617, 2017
Freso
See you then!
2017-05-16 13623, 2017
samj1912
Yo o/
2017-05-16 13624, 2017
Sophist-UK
</bang>
2017-05-16 13627, 2017
CatQuest
\o/
2017-05-16 13628, 2017
Freso
Sophist-UK: ;)
2017-05-16 13646, 2017
CatQuest
natta samj1912 !
2017-05-16 13655, 2017
Sophist-UK
GN samj1912 - sleep well.
2017-05-16 13618, 2017
samj1912
Freso you can skip the picard meeting notes, I think Sophist-UK 's doc can be used to append meeting notes to it
2017-05-16 13640, 2017
Freso
samj1912: I think it's still nice to get them to the forums.
2017-05-16 13641, 2017
samj1912
He had already recorded the last week's I think
2017-05-16 13646, 2017
CatQuest agrees
2017-05-16 13649, 2017
samj1912
Okay :)
2017-05-16 13655, 2017
CatQuest
but we can also put it in the doc :D
2017-05-16 13603, 2017
Freso
(And I'm already half done with last week's.)
2017-05-16 13633, 2017
samj1912
Nn 😴
2017-05-16 13639, 2017
Freso
Natta :)
2017-05-16 13640, 2017
CatQuest
natta!
2017-05-16 13613, 2017
CatQuest off into the rain to picup lego bought from ebay to accent the lego pirate chess set
2017-05-16 13617, 2017
Sophist-UK
Last week's already in the doc - this weeks also.
2017-05-16 13627, 2017
CatQuest
wtg Sophist-UK
2017-05-16 13634, 2017
Sophist-UK
But could do with someone to check I got it all.
2017-05-16 13640, 2017
Sophist-UK
I will add a chatlog link too.
2017-05-16 13625, 2017
Freso
Sophist-UK: "Next meeting: Tuesday, starting 1hr earlier (to avoid v. late meeting for attendees in India) for 2hrs" - we specifically agreed on 1 hour, and a clearer agenda.
2017-05-16 13627, 2017
Sophist-UK
Ok. Clearer agenda I remember - but I was under the impression we had agree on an earlier start to allow for a longer meeting. But I am equally fine with 1hr.
2017-05-16 13657, 2017
madmouser1 has quit
2017-05-16 13639, 2017
Sophist-UK
Ok - write-up finished for people to review for accuracy.
