13:32:44 #startmeeting move of Plasma Active to build.merproject.org 13:32:44 Meeting started Tue Mar 19 13:32:44 2013 UTC. The chair is notmart. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 13:32:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:33:12 Hi 13:33:28 * notmart is here 13:34:36 others? aseigo, Beineri, Sage? 13:34:44 * Beineri is present 13:35:40 I think Sage may be unwell today 13:36:03 ok 13:36:08 * notmart wishes him well 13:38:10 so, mainly two things, procedure to actually do the move and status of the new workers for the servers 13:39:08 one thing that was said was that is probably wise to follow the same naming scheme of nemo 13:39:31 so btw, what is the satatus of the migration of nemo to the new obs? is complete? still in progress? 13:39:50 #topic Move PA projects from MeeGo COBS to Mer COBS 13:39:58 (just fwiw) 13:42:37 So who was doing the migration? 13:43:22 for pa we still didn't do anythin (apart a copy of the current packages in my home project) 13:44:13 was pretty much waiting nemo definitely up and running, then starting to give to it the same structure 13:44:22 fair enough 13:44:43 will be done probably by me, Beineri, mdfe (that couldn't be present today) 13:44:45 worth identifying someone with the task though - so they can plan+report 13:44:49 :) 13:44:51 lbt: can you op merbot? 13:48:41 lbt: i can be on it 13:49:09 So Nemo migration is well under way 13:49:18 but particular things/ workflows that should be used? 13:50:01 we used in the past a certain workflow, is an occasion to change it a bit, always depends how much.. 13:50:01 in terms of devel/testing ? 13:50:16 OK 13:51:04 if you like how Nemo operates with boss doing some validation and trial builds then it would make it easier to use if you have the same project layout/naming 13:51:07 in part, in part i just have some doubts on how to both create and maintain the repos in the various "stages" 13:51:18 additionally it would help when sharing code 13:51:31 Sage has scripts that do that 13:51:39 is, for instance nemo done with some ci per se, just osc copypac of packages from one to another when stable, or..? 13:52:26 as just general structure i would do: 13:52:32 so nemo is going to move towards the model we've evolved in jolla (which is based on Nemo/Mer in the first place) 13:52:42 currently Nemo is not perfect 13:52:52 the new structure is much better 13:53:00 it is still SR based 13:53:01 using all nemo:hw:foo when possible 13:53:11 ideally havng just kde:mw and kde:ux 13:53:19 yep, OK 13:53:47 Nemo will also move to more ci/automation too 13:53:54 kde:mw is pretty much what's in kde:mer_extras in meego cobs (ideally with less packages, but removing eventual duplications after) 13:53:55 as well as being git-based 13:54:09 right 13:54:12 then kde:ux, basically what's now in kde:devel 13:54:45 to be git based, should it use a particular server? 13:55:15 I suggest writing this out as per https://wiki.merproject.org/wiki/Nemo/OBS 13:55:18 right now we just use osc and a jenkins that uploads tarballs for ci (on devel) 13:55:38 right - I have a tool called gitpkg which we use in Mer:Tools 13:55:53 it pulls a git repo in and runs git archive locally 13:56:00 makes uploads easy 13:56:08 I have whitelist of git services 13:56:25 github, gitorious, mer (not online yet) 13:56:45 mer will be using gitlab soon 13:57:01 * notmart not really convinced yet on using git for packages 13:57:27 you will be when your users get bored uploading tarballs :) 13:57:43 but that's not a dependency 13:57:51 just an FYI on how nemo works 13:59:00 yeah, and may get to it (personally would like to do one thing at a time) 13:59:49 but please tell if there is something that you would really prefer not happening in the new server.. 14:00:19 our main concern is likely to be load-based rather than storage 14:01:04 so things like only building on minimal # arches in the early phases 14:01:14 (if possible) 14:01:23 sure 14:01:46 also trying to coordinate on big updates which cause load spikes 14:02:12 and as i said i would also create only the deel stage at first, so testing and stable would be bult for the first time only when actually needed 14:03:11 sure 14:03:57 so is there an action to duplicate the Nemo/OBS page for PA ? 14:05:06 i can do it 14:05:59 provided it will be at first very draft and will evolve with time on an agreed form 14:06:09 wiki :) 14:06:22 you can #action yourself 14:07:39 #action notmart create a page like https://wiki.merproject.org/wiki/Nemo/OBS for Plasma Active 14:09:53 so, from my part i'll do, 1) wiki page 2) kde:devel:mw and kde:devel:ux repos on the repo with packages coming from meego cobs 14:10:13 (building only against i586 at first for testing) 14:11:01 i586 = atom - i486 = generic x86 14:12:19 so far our x86 images were just atom since targeted pretty much wetab,exopc 14:12:36 fine - just clarifying 14:12:51 Sounds like we have some tasks for the week then 14:13:01 s/we/you/ :) 14:13:01 sure 14:13:23 next topic? New servers? 14:13:54 #action notmart create kde:devel:mw and kde:devel:ux from meego cobs packages 14:15:39 lbt: we covered that last week? 14:15:46 yep 14:15:47 or is there new news on new servers? :) 14:15:49 nope 14:16:00 you got my email, yes? 14:16:07 yes 14:16:09 which is all I was really going to say :) 14:16:10 yay! 14:16:20 * aseigo is pleased at the internets, then. 14:16:32 ok, so this is pretty much covered as well i gather? 14:16:37 essentially I'm sorting out the finances - servers take an hour or so to come online 14:17:02 at this point, if nobody has anything to add i would say that's pretty much it 14:17:03 #info servers not ordered yet but only take an hour or so to come online so no problems there 14:17:17 then next week we can see how will be working so far.. 14:17:43 yes - and you can bug Sage and I for scripts when we have a spare few mins 14:18:31 ok 14:18:51 so btw at this point i would aim pa4 release from the new server already 14:19:03 that would be best it hink 14:19:20 otherwise we need to handle the case where people install with repos on the old systems .. and then have to change to the new ones 14:19:42 will already be frustrating for people running PA3, i imagine 14:19:56 FYI - I got an email from intel about shutdowns starting today with some VMs 14:20:01 that also means we are pretty much frozen, so after the initial huge spike for building everything there shouldn't be much rebuilding work for a while 14:20:03 * aseigo wishes the relevant meego.com domain names would forward to the new community obs 14:20:25 aseigo: meego.com is owned by linux foundation ... a nice public request? 14:20:50 oh, and this is a topic we'll need to hammer down in future, not necessarly now .. -> the mer-project.org domains and ones relevant to the OBS 14:21:07 yep ... http://releases.nemomobile.org/ 14:21:19 proxied to mer repo server 14:21:32 we need to lay out formally a disaster plan for these resources (so the rest of the world may sleep easily at our feet ;) 14:21:41 feel free :) 14:21:52 those are repositories from obs or a copy? 14:21:58 my plan is "keep lbt alive" 14:22:03 from the business, not the technical, perspective. in particular -> what should happen to the domains if the people currently running them lose interest 14:22:04 notmart: a copy 14:22:06 haha 14:22:14 lbt: i support that initiative whole-heartedly 14:22:24 eheh :) 14:22:40 * aseigo is reminded of that character in snow crash who has a nuclear device wired to his vital signs 14:23:02 (and therefore gets free protective custody / body guards in every city he passes through) 14:23:16 a cunning plan there, mr. lbt ;) 14:23:27 * lbt bows 14:23:44 anyways .. yeah .. we'll require a protocol that can be followed in case of future business / personal failure 14:24:00 i can spearhead that if needed, though i can't do it until probably may/june 14:24:26 I think our initial mer steering group may now be more relevant 14:24:32 "never forget the alamo! er .. meego.com!" 14:24:39 yes, rather relevant i'd think 14:25:02 but I think a public approach to LF about meego.com would make sense 14:25:10 that would be the body that should be empowered and given a clear set of protocols vis-a-vis these resources and the community dependent on them 14:25:11 specifically the community side 14:26:28 yes, that would be a reasonable thing to do .. an open letter sent to His Executiveness Mr. Zemlin perhaps 14:26:53 what about the MeeGo forums and mailing list, would they be transferred over to Mer / archived? 14:27:06 signed by mer,nemo,kde etc.. 14:27:36 eek - no forums 14:28:02 I'd say we need things which are likely to be embedded and need to be redirected 14:28:17 primarily repos 14:29:57 purely technical question... i probably need an admin to create the kde project? 14:30:57 err, yes, good point 14:31:12 we can take this to #mer 14:31:18 ok 14:31:33 other things to say in topic of the meeting? 14:31:54 #action asiego to prepare draft to LF about handling meego.com domain 14:35:02 sounds like we're done 14:35:07 yep 14:35:10 #endmeeting