Members present: wastl, westei, Humbedooh, wikier ---------------- Meeting summary: ----------------
1. Preface 2. lmf 2.6 release a. http://lists.w3.org/Archives/Public/public-lod/2013Feb/0115.html (wikier, 2) 3. code importation a. document package structure (wikier, 3) 4. triple store backends 5. infra issues 6. aob -------- Actions: -------- - document package structure (wikier, 09:21:53) IRC log follows: # 1. Preface # 09:05:55 [wastl]: topics? 09:05:57 [wikier]: well, lmf 2.6 has been released last Friday 09:06:05 [wikier]: so that's one 09:06:10 [wikier]: code importation 09:06:19 [wikier]: infra issues (website mainly) 09:06:20 [wastl]: different triple store backends 09:06:33 [wikier]: 3.1? 09:06:40 [wastl]: (just a short notice, not a long discussion) 09:06:43 [wikier]: ok # 2. lmf 2.6 release # 09:07:33 [wikier]: ok 09:07:33 [wikier]: as you know 09:07:40 [wikier]: 2.6 has been released 09:07:55 [wikier]: which is the milestone we had for switching to marmotta 09:07:57 [wikier]: #link http://lists.w3.org/Archives/Public/public-lod/2013Feb/0115.html 09:08:25 [wastl]: [off[ can we pause for 5 minutes? 09:08:33 [wastl]: [off[ Red Bull workshop 09:08:40 [wikier]: we already have some downloads and a user requesting support about security 09:12:48 [wastl]: didn't see the user request but this is good 09:13:04 [wastl]: security is not so good, because this is currently not very strong in Marmotta 09:13:33 [wikier]: actually something to discuss for the future 09:13:35 [wastl]: maybe security should become a separate component so its awareness is raised 09:13:55 [wastl]: nb that there is a security layer based on rules and access control lists 09:14:40 [wastl]: more regarding LMF 2.6? 09:15:03 [wastl]: (thanks to all for making the release, it works great, giving a demo later) 09:15:06 [wikier]: basically I'll create a branch for back-porting potential bugfixes 09:15:19 [wikier]: wastl: hope the demo will work ;-) 09:15:33 [wastl]: it does, I already tried :) 09:15:33 [wikier]: super 09:15:48 [wastl]: I am just always shocked and think that things did not work because it is so fast :-) 09:15:55 [wikier]: xD 09:16:18 [wikier]: we'd have to get figures about performance 09:16:25 [wikier]: ok, next topic # 3. code importation # 09:16:48 [wikier]: as I wrote to dev@, later I'd like to start with this 09:16:56 [wastl]: ok, here I favour the solution with a tag, but first we should go through the modules and decide which are included in Marmotta and which only in the LMF 09:17:11 [wikier]: exactly 09:17:20 [wikier]: I'd like to wait for other opinions 09:17:26 [wastl]: I think for most parts this should be easy 09:17:49 [wikier]: so later both because that, but also because I have a lot of stuff waiting to be done 09:18:11 [wastl]: maybe we can go through the modules tomorrow 09:18:19 [wastl]: and then start the import 09:18:19 [wikier]: I plan to import the modules we discussed, and try to build it 09:18:26 [wikier]: also 09:18:28 [wastl]: ok, should not be so difficult 09:18:34 [wikier]: no 09:18:42 [wikier]: actually quite easy 09:19:10 [wastl]: there are some things though to consider during the code transition, e.g. the Apache parent POM 09:19:18 [wastl]: but this can be part of the further process 09:19:33 [wikier]: yes 09:19:34 [wastl]: first import as-is 09:19:40 [wikier]: exactly 09:19:48 [wastl]: then we all switch repositories 09:20:03 [wikier]: and then further steps: parent, groupId, packages and so on 09:20:23 [wastl]: yes, the package structure should also be documented 09:20:31 [wastl]: especially for the SOA architecture 09:20:46 [wastl]: currently I typically used 09:20:47 [wikier]: exactly 09:21:08 [wastl]: org.apache.marmotta.<component> and then .api, .services, .webservices .model 09:21:23 [wastl]: .exceptions 09:21:53 [wastl]: and depending whether there are more services or data models subpackages or not 09:21:53 [wikier]: #action document package structure 09:22:46 [wastl]: ok, more for the code importation? otherwise I suggest you prepare it if you find time and we discuss tomorrow 09:23:18 [wikier]: +1 09:23:31 [wikier]: next topic # 4. triple store backends # 09:24:01 [wastl]: I'd like to make it possible to switch between different triple store implementations 09:24:03 [wikier]: welcome dglachs 09:24:11 [wastl]: and I think since everything is already prepared in the current release 09:24:24 [wastl]: it is only a small change and can be done already for Marmotta 3.0 09:24:38 [wastl]: the change is mainly in more modular packaging of marmotta-core 09:24:41 [wikier]: I'd prefer to leave it for 3.1 09:25:09 [wikier]: imo 3.0-incubating would be just a formal release to get it into the process 09:25:16 [wastl]: the reason why I'd like to do it now is that it is basically a repackaging, and it makes sense to do it during the general process of repackaging 09:25:38 [wastl]: the repackaging would be 09:25:46 [wikier]: aja 09:26:01 [wastl]: to move the SesameServiceImpl to a separate package and rename it to KiWiSesameService 09:26:16 [wastl]: make lmf-versioning, lmf-reasoner depend on this new package 09:26:18 [wikier]: well, if it's not so big the task, maybe we can afford it for 3.0 09:26:18 [wastl]: and that's it 09:26:32 [wikier]: let's discuss it tomorrow 09:26:38 [wastl]: it is not, I already prepared it during 2.6 09:26:39 [wastl]: yes 09:27:01 [wastl]: IMO it is mainly repackaging and therefore should be part of 3.0 09:27:09 [wastl]: because for 3.0 we need to thing about the proper package structure 09:27:18 [westei]: renaming should be done in 3.0 because 3.1 needs to be compatible with 3.0 09:27:23 [wastl]: different backends can come later 09:27:46 [wikier]: good point, westei 09:28:08 [wastl]: (I was thinking about marmotta-backend-kiwi, marmotta-backend-sesame-native, marmotta-backend-sesame-memory, marmotta-backend-jena-tbd, ...) 09:28:08 [wikier]: ok 09:28:23 [wastl]: and in extras/ a marmotta-backend-bigdata 09:28:38 [wastl]: (license of BigData is GPL) 09:29:08 [wastl]: ok, let's discuss this later, just wanted to raise the topic 09:29:55 [wikier]: ok 09:30:19 [wastl]: next topic? 09:30:26 [wikier]: taking into account what westei pointed, now I'm more about introduce it directly to 3.0 # 5. infra issues # 09:30:40 [wikier]: basically awaiting for website and nexus 09:30:42 [wastl]: so I see website, ad Maven 09:30:43 [wastl]: yes 09:30:57 [wikier]: INFRA-5624 and INFRA-5612 09:31:04 [wastl]: any progress? 09:31:04 [wikier]: INFRA-5612 is important 09:31:13 [wikier]: for the release 09:31:19 [wikier]: no progress 09:31:27 [wastl]: maybe we need to insist again 09:31:29 [wikier]: I asked our mentors about advice on it 09:31:49 [wikier]: there the details 09:32:06 [wikier]: I'll try to push this week 09:32:14 [wikier]: and bascally that's it 09:32:19 [wikier]: basically 09:32:34 [wastl]: ok, thanks 09:32:49 [wastl]: regarding the Nexus we can also use the one of Sonatype 09:33:04 [Humbedooh]: Infra is understaffed at the moment with a few being on holiday, and with ApacheCon coming up in a weeks time, it's going to take a while to get your requests processed 09:33:34 [wikier]: I fear that 09:33:49 [wikier]: :-/ 09:34:04 [wastl]: OTOH the ticket is open since December 09:34:26 [Humbedooh]: yes, and you can blame the 28748748 projects that forgot to switch to svnpubsub for that :| 09:34:49 [wastl]: ok :) 09:35:04 [wastl]: nop, we waited so long we can also wait another two weeks 09:35:19 [wastl]: just would be good to know a time frame 09:35:49 [Humbedooh]: just ping joe and ask him for an estimate 09:36:04 [wastl]: ok, good 09:36:11 [wastl]: thanks ;) 09:36:14 [wikier]: I'll try to ping him tonight 09:36:19 [wikier]: thx Humbedooh 09:36:26 [Humbedooh]: yw 09:36:41 [wikier]: ok # 6. aob # 09:36:56 [wikier]: aob? 09:36:56 [wastl]: documentation 09:36:58 [wastl]: needs to be updated 09:37:19 [wastl]: I created some tickets to track the documentation of the triple store and the LDClient 09:37:26 [wastl]: but where should we do it? 09:37:49 [wastl]: I'd like to more easily give access to individual components that other projects can use 09:37:56 [wikier]: wiki? 09:38:04 [wastl]: shall we start this in the Marmotta wiki? 09:38:04 [wastl]: yes ok 09:38:14 [wastl]: but eventually it should move to the website 09:38:41 [wastl]: the components that can be used separately are: 09:38:49 [wastl]: - KiWI triple store (with submodules) 09:38:49 [wikier]: for the moment content is important 09:38:50 [wastl]: - LDClient 09:38:56 [wastl]: - LDCache 09:38:57 [wastl]: - LDPath 09:38:59 [wikier]: where it another business ;-) 09:39:34 [wastl]: ok, so I'll start somewhere if I find the time :) 09:39:41 [wastl]: even if it is just a README 09:40:19 [wikier]: so wiki is the quickest option imo 09:40:19 [wastl]: another topic 09:40:34 [wastl]: what do we do with bugs that are discovered in 2.6? 09:40:41 [wastl]: fix them for 3.0 or create a 2.6.1? 09:41:04 [wastl]: IMO 2.6 should somehow stabilize with small bugs fixed 09:41:21 [wastl]: but we could also wait for 3.0 and stabilize it instead 09:42:11 [wikier]: I created a branch for 2.6 maintenance 09:42:19 [wastl]: ok, good 09:42:26 [westei]: back porting fixes with a lot of changed package names seams a lot of extra effort. So stabilizing 3.0 seams more feasable 09:42:36 [wikier]: where to backport what with fix in 3.0 before the release 09:43:02 [wikier]: lot of effort, but... should be done 09:43:09 [wikier]: that's why I'l like to get 3.0 asap 09:43:09 [wastl]: many issues are actually UI issues or archetype issues 09:43:24 [wastl]: well, the ones I discovered so far 09:44:46 [wikier]: let's see.. 09:45:09 [wastl]: ok, but I agree that we should get 3.0 as quickly as possible 09:45:46 [wastl]: ok, off now 09:45:54 [wastl]: my presentation at Red Bull 09:46:01 [wastl]: cu 09:46:16 [wikier]: good luck! 09:46:18 [wikier]: ups, late 09:46:24 [wikier]: ok, thx everybody!
