[14:31] == tfr42 [574f5926@gateway/web/freenode/ip.87.79.89.38] has joined #deegree [14:32] Hi [14:32] Hi [14:33] hu [14:33] hi [14:33] i believe, jens originally wanted the psc members to join this time to find a date for the joint meeting... [14:33] hi [14:33] Yes [14:34] But PSC has not be informed about our decision to meet now [14:34] yes, this was a bit on short notice [14:35] did know about that either [14:35] yes, sorry about the miscommunication. [14:35] Yes, is going to join the chat [14:35] jens asked me and i told him i was waiting for reijers' doodle pick [14:36] so we wait for jens? [14:36] yes, please [14:36] ok [14:36] herman is on the phone at the moment, cannot ask him if he's going to join [14:36] he is entering the chat now [14:38] While we are waiting, what is on the agenda for today? [14:38] 3.3 pull requests [14:38] http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20140509 [14:38] == jens [574f5926@gateway/web/freenode/ip.87.79.89.38] has joined #deegree [14:38] thnaks [14:38] == jens has changed nick to Guest38956 [14:39] Let's go [14:39] hi jens, welcome to the meeting [14:39] hi Guest38956! [14:39] hi, just joined in case you have questions regarding the server stuff [14:39] Hello [14:39] first, sorry for the miscommunication on psc participation [14:39] jens asked me and i told him i was waiting for reijers' doodle pick [14:39] but i didn't tell reijer that i was waiting [14:40] Again link to agenda: [14:40] http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20140509 [14:40] anything you would like to add? [14:40] would you like to add the topic I sent to all of you this morning? [14:40] Can we add the topic regarding deegree's infrastructur? [14:40] ok [14:41] moment [14:41] http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20140509 [14:41] anything else? [14:42] ok [14:43] i would suggest to start then [14:43] ok [14:43] Yes please [14:43] Can we do anything about the date for TMC/PSC joint meeting? [14:43] klaus and herman are missing [14:43] Sorry for the confusion here [14:44] personally, i suggest to go for yet another doodle [14:44] on the joint meeting [14:44] directly [14:44] for dates in a more distant future [14:44] As per the last doodle we have a meeting date and time Friday at 11... [14:44] tomorrow? [14:44] There we'll meet on skype to find a date and time for an in-person meeting... [14:45] day after tomorrow i mean [14:45] so would be good to have everybody on skype Friday, 11 a.m. [14:45] was there an email already on that? [14:45] me and herman are available at friday 11 am [14:46] fine with me [14:46] Good [14:46] Markus, you participated in the doodle. [14:46] i was the last who entered the friday 11am a few minutes ago [14:46] The mail was 02.05.2014 11:50 [14:46] the doodle is http://doodle.com/rvv98peuqwtyq4gq [14:46] i know that i participated, but was there a confirmation on the picked date? [14:47] that i missed [14:47] not yet, as Stephan just entered his options [14:47] but now we're fine. I'll send another mail to all of us [14:47] Great, then we will talk on Friday! [14:47] Let's move on to the next topic [14:47] "Consolidation of deegree infrastructure" [14:48] Yes [14:48] did everybody read jens email from today [14:48] ? [14:48] i did [14:48] Me too! [14:48] me too [14:48] me too [14:48] first, let me say thanks for contributing this in the past and the offer to continue [14:49] reijer pointed an alternative to a rented server [14:49] i would like to suggest to take one step back: do we need our own services [14:49] we could use hosted solutions instead [14:50] like we do already for git [14:50] That's for the long term [14:50] probably cheaper [14:50] i believe that this will cut administration and work [14:50] But since there are SMART errors we have to move NOW [14:51] sure, but moving to a hosted environment is not different than creating a new setup ourselfs [14:51] not that different [14:51] Is that possible for all infrastructure components? [14:51] Well, then we need an evaluation of the services provided, costs and so on [14:51] what are we actually going to loose if the disk fails? [14:52] - artifacts [14:52] - build jobs [14:52] we can rebuild those [14:52] anything else? [14:52] no! [14:52] The artifacts stored in Nexus [14:52] not again [14:52] how about making a backup of the artifacts first [14:53] this seems to be the most important thing to me [14:53] is there anything else hosted on the failing machine? [14:53] no nothing more [14:53] I guess we have backups of all servers. But have to ask to be sure [14:54] well, how about making a back up and someone evaluates hosted solutions for Nexus and Jenkins? [14:54] in the next days [14:54] any opinions? [14:55] do we prefer hosted? [14:55] i do [14:55] me too [14:55] nexus is just a glorified file server [14:55] no point in hosting + maintaining one ourselfs [14:56] could we please vote if the tmc prefers a hosted solution for nexus? [14:56] not yet [14:56] why not? [14:56] we need to find out where we want to go [14:57] even if it is not now [14:57] Well, the question is how do we deal with the failing HW [14:57] asap because of hd errors [14:57] make a backup! [14:57] now we discuss where to host the services [14:57] so far we don't know what we need, is there a SaaS for OSS available and so on [14:58] I would prefer to have this as two distinct tasks [14:58] We'll make a backup. But that's only half of the story [14:58] First decide how to deal with the current infrastructure [14:58] The server also has www.deegree.org... [14:58] that's important to know [14:58] hosted dupal is not going to be a problem [14:59] then how we would like move onwards wrt a prefered hosted solution [14:59] drupal [14:59] to me, the primary question is: who is going to do the migration work to a new hetzner server. [14:59] Sure but we have to move soon [15:00] how soon: what smart error do you have [15:00] the migration work has to be done by all of us, I guess [15:00] lat/lon will assist you. [15:00] so you'll know what you get [15:01] in that case i would (personally) prefer to invest that work into moving to a hosted solution [15:01] and not into an interim solution [15:01] but that's just me [15:01] that's probably also going to be the fastest way [15:01] Well, even if you don't know if there is an SaaS for Nexus? [15:02] there are many of those services [15:02] well, of course there is [15:02] Then tell me now, please [15:02] Can we agree that control over the initative's infrastructure is a highly strategic aspect which should be at least discussed or decided about together with the PSC? [15:03] And what about the 3rd party libs and the licences they come with? [15:03] Things we have to evaluate too [15:03] fine [15:04] still, jens: you came asking for help with this "highly strategic aspect" because it fails technically at the moment [15:05] I did not want to make it a strategic thing. That was you [15:05] I just want to change hardware [15:05] this seems to be a misunderstanding [15:06] anyhow my quick research on SaaS for nexus was disappointing [15:06] I couldn't find one [15:06] i am just pointing out how i prefer to invest my work resources [15:06] are you using a raid array at the moment? [15:06] Only cloudbees is offering JFrog Artifactory [15:06] if so: just replace the disk [15:07] thank you [15:07] after you properly removed the disk from the array of course [15:07] hetzner replaces broken disks for free [15:07] they don't [15:08] they do [15:08] we've been doing that for years [15:08] not for free [15:08] yes they do [15:08] == Guest38956 [574f5926@gateway/web/freenode/ip.87.79.89.38] has quit [Quit: Page closed] [15:08] i just asked them to replace one a few hours ago [15:08] Sorry, that's not coming to a point [15:09] agreed [15:09] Well, then let's wait for the disk to fail [15:09] The risk we take here is that we will lose some data = artifacts [15:09] I am willing to take that risk [15:09] since there is a backup [15:10] I never tested myself if the backup is easy to use [15:10] still, we need to find some consensus on how to deal with this [15:10] but then lets make a decision now that all of you agree [15:10] not to take action right now [15:10] My proposal [15:10] : [15:11] i am sorry, what would it cost to replace the disk then [15:11] as an interim solution [15:11] TMC decides to keep the current HW and is preparing a proposal to move ALL services to a hostes (SaaS) solution. [15:12] can I have your votes on that please? [15:12] that is: evaluate hosted solutions [15:12] if it's not possible, we don't have any other chance but host some services [15:13] other than that: +1 [15:13] +1 [15:13] +1 [15:13] stephan? [15:13] (still don't understand why you cannot replace the disk..._ [15:13] +1 [15:13] thank you [15:13] OK [15:13] thanks [15:13] but i also think that the broken raid disk has to be changed [15:14] I will prepare the answer to Jens email [15:14] thanks [15:14] Next item: [15:14] http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20140509#deegree_at_Bolsena_Code_Sprint_2014 [15:14] This is a good idea [15:14] VERY good idea, indeed! [15:15] not sure if i'm available [15:15] thanks [15:15] could you check back? [15:15] shall i write this as an email again? [15:15] to tmc and psc? [15:15] I would send this to the ml [15:15] ok [15:16] let's have that one public [15:16] stephan, you see any chance to join? [15:16] you or someone else you know? [15:16] the week is the week before my holiday so i have to check here first if i am available [15:17] ok [15:17] i will write an email to deegree-users, then [15:18] Next item: http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20140509#Status_of_automated_pull_request_testing [15:19] Well, it's not perfect, but at least it works for now... [15:19] which is great! [15:19] any questions or comments? [15:19] thx [15:19] do you have any idea how much effort this caching thing to going to be [15:20] no, not really [15:20] i found some scripts on the net [15:20] seems like something that's nice to have [15:20] right [15:20] not urgent imho [15:20] ok [15:20] shall we move on, then? [15:20] fine [15:21] Just for my understanding, the travis bot can check all pull request for the branch for 3.3 to now? [15:21] i read thru the travis docs and found that cacheing is only available for the paid ones (when researching for private lib problems) [15:21] one thing: sphinx [15:21] @stephanr: yes, but there are other options than the built-in caching [15:21] we had an issue in that area... [15:22] people have been using caching with the free travis as well [15:22] @copierj: yes, we could extend that [15:22] we would need to install a few packages via apt-get, but that's absolutely doable [15:23] would also be nice to have [15:23] more urgent that caching imho [15:23] as it breaks the build [15:23] Well, again my question: Can we go with that current solution on travis-ci, yes or NO? [15:23] sorry, torsten: i didn't fully understand the initial question [15:23] "for the branch for 3.3 to now" [15:24] we have a travis.yml (and hence automated testing) in master and 3.3-master [15:24] Good [15:25] ok, shall we pull? [15:25] Do we accept that workaround to manualy restart the build? [15:25] yes [15:25] yes, to my question? [15:25] torsten, you have any better idea? [15:25] no, previous one [15:25] No, I am fine [15:26] me toot [15:26] too [15:26] But I noticed that you created a lot of dummy pull requests to initiate the build again [15:27] i am pretty hopeful, that this was only necessary for branches that originated from a version without travis.yml [15:27] That workaround should be accepted by us and we should be aware that someone has to do this - manually [15:27] == segoer [574f5926@gateway/web/cgi-irc/kiwiirc.com/ip.87.79.89.38] has joined #deegree [15:27] i already restarted builds for 3.3 pull recently [15:27] worked [15:27] good point. [15:27] Good, [15:27] I am fine with that solution [15:27] hi there [15:27] you can see in travis that it timed out [15:27] hi [15:28] then we have to restart it. for now [15:29] ok. move on? [15:29] we already have 1 hour, btw [15:29] can you guys stay a bit longer [15:29] ? [15:29] I recognized that there is a tmc meeting today. is it taking place atm? [15:29] yes [15:29] ok :) [15:30] but it's official over right now [15:30] officially [15:30] we should extend the meeting to at least complete the pull requests [15:30] please [15:30] tmc members, shall we continue with the pull requests? [15:30] yes [15:30] hurry up ;-) [15:30] i am fine as well [15:30] may i ask a question then? [15:31] quick! [15:31] as nobody from the tmc replied to my email [15:31] please [15:31] is there any idea about a release date for 3.4? [15:31] well, there are blocker [15:31] blockers [15:31] this is no answer to my question ;) [15:31] i guess we need to talk about 3.4 on the joint meeting [15:31] ok [15:32] i cannot give you one, sorry [15:32] pull requests, then!? [15:32] https://github.com/deegree/deegree3/pull/189 [15:32] Please review and give your votes. [15:32] +1 [15:33] +0.5 (cannot tell the effect) [15:33] a unit test would have been nide [15:33] nice [15:33] I do miss the travis comment [15:34] why is it not shown? [15:34] anyhow [15:34] it is there, are you logged in? [15:34] uh, sorry [15:34] right [15:34] +0 [15:35] +1 [15:35] weird that ci result is not visible to everyone always [15:35] Result: +2.5. Merged [15:35] Next: https://github.com/deegree/deegree3/pull/198 [15:35] open for some time... [15:36] should we decline it? [15:36] we need a solution for the problem but -1 for this patch [15:36] -1 from me as well [15:37] postpone decline until we have more time to discuss? [15:37] 0 [15:38] 0, and discuss [15:38] Result: -2. Not merged. Need to discuss how to cope with it next time. [15:38] Skipping https://github.com/deegree/deegree3/pull/199 [15:38] perhaps we can go with the suggestion in my last comment [15:39] Next: https://github.com/deegree/deegree3/pull/209 [15:40] -1 (build fails) [15:40] 0, since travis warning and I can't say if this code is guilty or not [15:41] why can't we? [15:41] https://travis-ci.org/deegree/deegree3/jobs/24060894 [15:41] error: Could not find artifact jogl:jogl:jar:1.1.2 [15:41] seems to be a clear compilation error [15:41] Talking about myself, I can't since there is no test available which shows the resulting context [15:42] @copierrj: look at the end! [15:42] "Could not find artifact jogl:jogl:jar:1.1.2" is normal, sorry [15:42] ok [15:42] error is clear: -1 [15:43] -1 [15:43] Result: -3. Not merged [15:44] BTW, do we need to write feedback comments after TMC pull request decisions? [15:44] i guess, we do [15:44] yes, would be nice [15:45] can everyone that's logged in see the travis result? [15:45] or only us? [15:45] otherwise people have to recheck your chat log... [15:45] good question, i do not know [15:45] Good idead to give feedback [15:45] i can see the travis results [15:45] @torsten: would you be willing to help with comments after tmc sessions? [15:45] i am currently not logged in and the travis mark is there at the last commit [15:46] @segoer: great! [15:46] i am already busy with release email and stuff [15:46] @copierrj what do you mean? [15:46] i'm typing a comment atm [15:47] OK [15:47] @reijer: thanks, but isn't this a bit time consuming to do in the meeting? [15:47] yes, but otherwise it's probably not going to happen [15:47] i would prefer to do that afterwards. and ideally, in a standardized manner [15:47] torsten just signalled to help... [15:47] yes, that would be nice [15:48] so, torsten would you do that along with the release notes? [15:49] OK, afterwards and let's talk then [15:49] if everybody is ok with that [15:49] yes I do agree [15:49] fine with me [15:49] +1 [15:49] fine [15:49] thanks. just your votes then... [15:49] Next: https://github.com/deegree/deegree3/pull/211 [15:49] -1 (fails) [15:50] -1 [15:50] -1 [15:50] -1 (as it is failing) [15:51] Result: -4. Not merged. [15:51] Next: https://github.com/deegree/deegree3/pull/213 [15:51] do we have a 3.4 pull for this already? [15:52] good question. [15:52] -1 [15:52] -1 [15:52] -1 [15:52] -1 [15:52] Result: -4. Not merged. [15:53] Next: https://github.com/deegree/deegree3/pull/220 [15:53] oops. forgot to restart this one [15:53] not build yet by travis [15:54] as this branched before the travis.yml was added, we need to create a dummy pull request [15:54] this seems to be travis bug [15:54] i've rebased it [15:54] that's not the point [15:55] it's a travis bug [15:55] this is why i had to create all those dummy pull requests [15:55] but i obviously forgot this one [15:55] anyways: -1 [15:55] for now [15:55] skip it for now [15:55] -1 [15:55] 0 [15:56] quite sure it works.... [15:56] 0 [15:56] Result: -2. Not merged. Will be restarted and reconsidered next time [15:56] the other could say the same for their pull requests reijer ;) [15:56] sure [15:56] but we have also a 3.4 for this [15:56] https://github.com/deegree/deegree3/pull/229 [15:57] -1: needs to mention the corresponding 3.4 pull request [15:57] =1 [15:57] +1 [15:57] -1 [15:58] 0 [15:58] Result: -1. Not merged. [15:58] Next. https://github.com/deegree/deegree3/pull/234 [15:58] +1 [15:58] +1 [15:58] +1 [15:58] +1 [15:59] Result: 4. Merged. [15:59] == markusschneider [~schneider@p578bff50.dip0.t-ipconnect.de] has left #deegree [] [15:59] == markusschneider [~schneider@p578bff50.dip0.t-ipconnect.de] has joined #deegree [15:59] oops [15:59] welcome back! [15:59] sorry. closed my client accidentally [15:59] can anybody please provide the log afterwards? [15:59] yes [15:59] thx [16:00] Next: https://github.com/deegree/deegree3/pull/246 [16:00] +1 [16:00] +1 [16:00] +1 [16:00] +1 [16:00] Result: +4. Merged [16:01] Next: https://github.com/deegree/deegree3/pull/249 [16:01] -1 (discussion on ml still missing) [16:02] +1 (need it, like it) [16:02] also handbook is missing... [16:02] info in handbook would be nice [16:02] could you add that? [16:02] sure [16:03] do we have a feature ticket in trac? [16:03] not yet [16:03] sorry, but then [16:03] -1 [16:03] 0 [16:03] Result: -1. Not merged [16:04] Next: https://github.com/deegree/deegree3/pull/285 [16:04] -1 (waiting for more information) [16:04] -1 (more info requested) [16:05] -1 [16:05] -1 [16:05] Result: -4. Not merged. [16:06] Next: https://github.com/deegree/deegree3/pull/287 [16:06] +1 [16:06] +1 [16:06] +1 [16:06] we cannot trust travis for this one [16:07] 0 [16:07] Result: 3. Merged. [16:07] Final one: https://github.com/deegree/deegree3/pull/289 [16:08] +1 [16:09] +0.5: no tests, cannot tell. but looks good, trust reijer [16:09] there are tests [16:09] @copierrj as this changes some logic i would like to look deeper into it, would it be ok to put this for the next tmc meeting ? [16:09] sorry, missed the tests [16:10] @StephanR: do you have a database containing lots of complicated sdo's? [16:10] still, would it be ok to postpone it so stephan can investigate? [16:10] only if the next TMC is going to happen soon [16:10] really need this fix [16:10] i second a meeting date soon... [16:10] next week? [16:11] would be great [16:11] ok, skip that one [16:11] -1 [16:11] for now [16:11] 0, skip [16:11] waiting for your input [16:11] Result: Skipped [16:11] ok, this was long, gentleman [16:11] not exactly in one database, but i have some problemtic local data [16:11] puh! [16:11] thanks for your patience [16:11] btw [16:11] and stop [16:11] i need the log! [16:12] @StephanR: feel free to contact me if you have any questions [16:12] tfr42??? [16:12] I have got a ticket for topic "infrastructure" [16:12] https://wald.intevation.org/tracker/index.php?func=detail&aid=6530&group_id=27&atid=303 [16:12] thanks [16:12] assigned it to reijer [16:12] i will into it the next days (monday) and add my feedback [16:12] please start and move it around the tmc members [16:12] tfr42: OK [16:13] torsten, you send me the chat log, right? [16:13] yes [16:13] thx [16:13] bye [16:13] good bye then [16:13] bye [16:13] == copierrj [~chatzilla@83.247.8.136] has quit [Quit: ChatZilla 0.9.90.1 [Firefox 29.0/20140421221237]]