19:01:19 <ennael> #startmeeting
19:01:19 <Inigo_Montoya`> Meeting started Wed Apr 13 19:01:19 2011 UTC.  The chair is ennael. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:19 <Inigo_Montoya`> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:01:20 <erzulie> [ MeetBot - Debian Wiki ]
19:01:42 <ennael> #chair ennael boklm misc shikamaru
19:01:42 <Inigo_Montoya`> Current chairs: boklm ennael misc shikamaru
19:01:54 <ennael> hi all
19:02:45 <damsweb> hello all
19:02:59 <boklm> hello
19:03:02 <ennael> so let start
19:03:02 <stblack__> hello
19:03:14 <ennael> #topic version freeze coming: priorities, todo list
19:03:17 <mikala> hello,
19:03:24 <ennael> #topic version freeze coming: priorities, todo list
19:03:26 <ennael> grumpf
19:03:50 <ennael> ok we have less than 2 months until final release
19:03:59 <ennael> and version freeze coming soon
19:04:12 <ennael> so we need to fix some priorities
19:04:36 <ennael> missing packages, bug fixes, localization, packages requests
19:04:46 <mikala> and artwork?
19:04:57 <ennael> well not in todo list for us :)
19:05:04 <ennael> at least until we have it for integration
19:05:14 <mikala> yep that what i meaning by artwork
19:05:23 <mikala> integration on all desktop.
19:05:27 <ennael> ok
19:05:43 <ennael> so for those who do not know about it : http://check.mageia.org/
19:05:44 <erzulie> [ QA global report ]
19:05:49 <ennael> #url http://check.mageia.org/
19:05:49 <erzulie> [ QA global report ]
19:06:12 <ennael> pterjan installed it to follow interesting things about apckaging
19:06:33 <ennael> dependancies missing or wrong (2 first links)
19:06:48 <ennael> and version review compared to some other distributions
19:07:12 <ennael> any question on these pages ?
19:07:38 <Nanar> about pages itself no
19:07:46 <ennael> hi Nanar
19:07:57 <Nanar> ( hi ennael )
19:08:04 <ennael> first comment about 2 first links
19:08:15 <mikala> the packagers part is waiting for the maintainer database i guess ?
19:08:19 <Nanar> but is updating packages our priority ?
19:08:20 <ennael> yes
19:08:25 <ennael> Nanar: wait :)
19:08:36 * Nanar wait !
19:08:38 <ennael> so this is usefull information
19:08:47 <ennael> but we need priorities as said in topic
19:08:52 <mikala> regarding the « updating packages », we just need to mail pterjan to fix some « wrong » update ?
19:09:03 <brianb> hi
19:09:05 <ennael> I guess 2 first one should be our priorities
19:09:16 <ennael> fixing missing deps or packaging errors
19:09:21 <boklm> mikala: yes, or sysadmin list
19:09:27 <ennael> still lots of work on it to be done
19:09:28 <pterjan> mikala: config is in svn
19:10:10 <ahmad78> ennael: (don't forget the gnome-3-updates-that-show-in-updates.html)
19:10:20 <ennael> ahmad78: yep ;)
19:10:27 <pterjan> I was thinking of removing this list of updates for now and just comparing to mandriva, what do you think ?
19:10:37 <ennael> wait please :)
19:10:46 <mikala> pterjan: i would compare to fedora & mandriva
19:10:49 <ennael> I'd like us to fix the 2 first lists
19:10:57 <ennael> before beta2
19:10:59 <ennael> wdyt?
19:11:00 <pterjan> yes
19:11:07 <pterjan> seems doable, not many errors
19:11:16 <ennael> but still has to be done
19:11:36 <ennael> anybody ready to help on that ?
19:11:43 <Nanar> yup
19:11:46 <sebsebseb> hi
19:11:51 <ennael> ok
19:11:58 <ennael> I will mail on -dev about this point
19:12:16 <ennael> please mention the one you will work on so people avoid to twice the work
19:12:20 <ennael> is that ok ?
19:12:29 <Nanar> pterjan: update list is over mdv /cooker ?
19:12:39 <Nanar> for mandriva rpms
19:12:53 <ennael> #action fix missing deps before beta2
19:12:55 <philippeM> some are discussed on ml (python-xfce and apache-mod_python) solution is simple : drop them
19:12:58 <damsweb> FYI folks/empathy/telepathy are WIP :-)
19:13:00 <pterjan> Nanar: I have a file to do so but not used cirrently
19:13:08 <ennael> philippeM: well then just do it :)
19:13:20 <shikamaru> any help on ruby-selenium-webdriver would be welcome
19:13:28 <philippeM> ok I take them
19:13:30 <ennael> #action ennael will mail about this so that people can mention the one they are working on
19:13:48 <ennael> also please a reminder
19:14:00 <ennael> when you import package please take care of missing deps list
19:14:13 <ennael> we often see list growing up after some new one are imported
19:14:28 <mikala> ennael: can't rpmlint forbid submission on missing dependancy ?
19:14:33 <ennael> #info check missing deps when importing new packages
19:14:43 <Nanar> and btw: mageia packages must update mdv one
19:15:03 <ahmad78> Nanar: that's what upgrade tests should spot...
19:15:05 <pterjan> indeed we need to check that
19:15:16 <pterjan> maybe I can set an update test against 2010.1
19:15:18 <Nanar> ahmad78: I had to fix pingus
19:15:20 <pterjan> it should be empty
19:15:38 <ahmad78> (i.e. mga package will replace package from contrib/updates, but not contrib/backports in 2010.1, e.g. banshee)
19:15:39 <ennael> pterjan: can you have a look on a way to forbid packages import if missing deps ?
19:15:47 <ahmad78> ennael: that's bad
19:15:56 <ennael> ahmad78: ?
19:15:58 <pterjan> ennael: that will be annoying for some bootstrap
19:16:00 <ahmad78> a package can have missing deps that'll be imported
19:16:14 <ennael> but it's unusable
19:16:15 <Nanar> ennael: such check can be triggered by loop
19:16:16 <pterjan> sone subpackages can be temporarily not installab;e
19:16:22 <ennael> or at least be notfied
19:16:23 <ennael> i
19:16:36 <pterjan> well there is the rss of that page :)
19:16:48 <ennael> well looks like it's not that used :)
19:16:49 <ahmad78> yeah, we just need to look at it some more
19:16:50 <pterjan> I can also mail the list of broken dependencies daily to the ml
19:16:55 <ennael> yep
19:16:57 <Nanar> I still have to import ghc needing ghc to b built...
19:17:10 <ennael> that would be nice until stable release
19:17:20 <ennael> when people are tired of it it will be fixed :)
19:17:25 <ahmad78> :)
19:17:38 <shikamaru> Nanar: couldn’t we use the mdv rpm for the bootstrap ?
19:17:39 <ahmad78> fixed by annoying-the-hell-out-of-packagers
19:17:41 <ennael> wdyt ?
19:17:45 <andre999> an email to the submitter about missing dependancies would be useful as well
19:17:46 <ennael> ahmad78: sure :)
19:17:49 <shikamaru> that’s haskell compiler right ?
19:17:55 <Nanar> yes
19:17:56 <ahmad78> sure an email to -dev would be a good reminder
19:18:01 <ennael> ok
19:18:13 <ennael> #action send in a daily mail list of missing deps
19:18:16 <Nanar> shikamaru: yes, yes yes, just mentionning it, out of topic right now
19:18:33 <ennael> ok
19:18:36 <Dr_ST_home> hi
19:18:53 <ennael> is that all for missing deps ?
19:19:12 <shikamaru> about updates
19:19:24 <ennael> yep second point
19:19:30 <shikamaru> it could be nice to send to the list packages that should _not_ be updated :)
19:19:34 <ennael> and ahmad78 is very worried about it :)
19:19:36 <ennael> yep
19:19:51 <ennael> this is information but of course we need to be carefull with this
19:20:00 <Nanar> wikipage anyone can check ?
19:20:02 <ahmad78> it's just easy to update a GNOME package wrongly nowadays
19:20:08 <ennael> no question to update gcc or rpm or gnome3
19:20:09 <Nanar> or any lock on bsside ?
19:20:14 <shikamaru> a wiki page could do the job yes
19:20:18 <Nanar> ennael: :\
19:20:40 <ennael> link to this wiki page should be added written in red in web page
19:20:47 <Dr_ST_home> I missed it, in short, no gnome3?
19:20:53 <ennael> nope
19:20:58 <Dr_ST_home> ok
19:21:51 <ennael> having maintainers later amy help as people should ask them before updating sensitive packages
19:22:29 <ennael> pterjan: can you add this in page?
19:22:38 <ennael> ahmad78: does it look enough for you.
19:22:39 <ennael> ?
19:22:45 <pterjan> ok
19:22:59 <ahmad78> ennael: I hope so
19:23:00 <pterjan> not sure how but yes
19:23:13 * pterjan will probably need to make an ugly patch to the code
19:23:15 <ennael> Also mentors should be careful with this and inform trainees
19:23:29 <ennael> pterjan: that would be nice (not the ugly part)
19:24:32 <Dr_ST_home> ok, gtg but just to say I'm still interested, mail me if needed, I'll have more time in may
19:24:38 <Dr_ST_home> have a good meeting
19:24:45 <ennael> #action add link in page to inform about sensitive packages that should not be updated without asking
19:24:58 <Kharec> Can we update patchutils?
19:25:08 <ennael> wait please :)u27
19:25:10 <ennael> outch
19:25:12 <Kharec> oops.
19:25:12 <ennael> sorry
19:25:15 <Kharec> me too.
19:25:32 <Nanar> ennael: touchpad ? /o\
19:25:32 <andre999> it might be a good idea to put do-not-update and missing dependancies on the same wiki page ?
19:25:36 <ennael> Nanar: yep :)
19:25:54 <ennael> andre999: well missing deps are already listed in web page
19:26:05 <Nanar> andre999: missing deps is automatically generated pages
19:26:10 <andre999> ennael: ok i missed that
19:26:19 <ennael> in updates page you can find new version of gcc or rpm...
19:26:20 <andre999> ok
19:26:34 <ennael> so we just want to avoid some updates that we would not want
19:26:47 <ennael> especially as stable realease is coming
19:26:51 <Nanar> ennael: no rpm5 then ? /o\
19:26:56 * ennael slaps Nanar
19:26:56 <ennael> :)
19:27:04 <andre999> :)
19:27:05 <Nanar> :)
19:27:18 <ennael> ok anything else to add on that topic ?
19:27:42 <Nanar> maybe
19:27:44 <shikamaru> perhaps freeze some of them ?
19:27:57 <shikamaru> like what’s done for glibc afaik
19:28:03 <Nanar> should maintainer mention a list they don't want to see updated ?
19:28:33 <Nanar> I mean if I know package X must not be ve updated at time for any reason
19:28:39 <ennael> well I'd like to have it in this list together with a reason on this
19:28:55 <andre999> could be added to the do-not-update page ?
19:28:56 <Nanar> I can give the reason
19:29:18 <Nanar> but maybe nobody will think to this package as it is not os important
19:29:21 <Nanar> so
19:29:31 <ennael> Nanar: ok so add it in page
19:29:35 <Nanar> ok
19:29:37 <ennael> I will mail about that page ok ?
19:29:49 <Nanar> (yes indeed it's wiki page)
19:29:57 <ennael> #action ennael will mail about not-to-be-updated packages page on wiki
19:30:03 <ennael> ok
19:30:08 <ennael> anything else to add on this ?
19:30:38 <andre999> maybe all do-not-updates should have the reason ?
19:30:59 <ennael> 21:28 < ennael> well I'd like to have it in this list together with a reason on this
19:31:01 <pterjan> jq: if https://gist.github.com/918226 works (I did not even check the syntax) that should speed your uploads a lot :)
19:31:02 <ennael> that one ? :)
19:31:02 <erzulie> [ 's gist: 918226 -- Gist ]
19:31:31 <ennael> reminder: version freeze on 20th or april
19:31:39 <ennael> #info reminder: version freeze on 20th or april
19:33:08 <ennael> ok next topic then
19:33:16 <ennael> #topic secteam creation
19:33:25 <Nanar> hum
19:33:34 <ennael> we need to decide a date to have a meeting about this
19:34:09 <ennael> any proposal for those who are interested?
19:35:06 <Kharec> me, me!
19:35:11 <brianb> can you remind me what the role and function of the secteam will play?
19:35:37 <pterjan> brianb: managing security updates
19:35:40 <ennael> take care about all offcial updates for stable releases
19:35:46 <ennael> at least to manage it
19:36:10 <Kharec> And make fix for CVE issue?
19:36:17 <pterjan> yes
19:36:18 <Nanar> it's important task, needing time
19:36:32 <Nanar> and lot of management
19:36:38 <ennael> well we can have several part time guys
19:36:46 <ennael> and stew is proposing to help to manage it
19:37:04 <ennael> if no proposal I will discuss with myself and decide a date :)
19:37:05 <Kharec> I have to go, but i'm very interesting to be part of secteam
19:37:06 <pterjan> the main problem would be when we have everyone on vacation
19:37:25 <ennael> yep
19:37:28 <Nanar> ennael: so you need a date ?
19:37:34 <Kharec> I have to go, but i'm very interesting to be part of secteam
19:37:38 <ennael> yes what time you prefer
19:37:46 <Nanar> Kharec: ?
19:37:59 <Kharec> Nanar: yup?
19:38:00 <pterjan> he is very very interested :)
19:38:00 <anaselli> pterjan: just hope not to be all from the same country...
19:38:03 <shikamaru> I think he meant interested ? :)
19:38:08 <Kharec> pterjan: yep :)
19:38:14 <andre999> but distracted :)
19:38:33 <pterjan> anaselli: having people from south and north would help
19:38:35 <Nanar> Kharec: date and time for meeting about secteam
19:38:37 <Nanar> ?
19:38:44 <ennael> ok let say 19th of april, 21hUTC
19:38:47 <ennael> is that ok ?
19:38:51 <anaselli> and west and east too :)
19:39:07 <Kharec> ennael: ok for me, I will mail on -dev if you want
19:39:08 <Nanar> fine for me (even I am not the most intesrested)
19:39:17 <ennael> Kharec: I'm doing it now
19:39:21 <Kharec> ennael: no problem!
19:39:22 * pterjan will try to attend
19:39:32 <shikamaru> next tuesday so ?
19:39:39 <Kharec> yup!
19:39:43 <brianb> on -dev channel?
19:39:44 <Kharec> I will be there!
19:39:54 <Kharec> I think so.
19:39:57 <pterjan> someone from a country with no vacations ?
19:40:03 <ennael> :)
19:40:14 <anaselli> pterjan: do you?
19:40:16 <anaselli> :p
19:40:32 <ennael> #action secteam first meeting planned for 19th of april, 19h UTC
19:40:39 <Nanar> what is vacations ?
19:40:44 <Kharec> ennael: good!
19:40:45 <Nanar> :)
19:40:46 <shikamaru> Nanar: ^^
19:40:49 <ennael> Nanar: something for real human beings
19:40:54 <anaselli> pterjan: from the boss point of view... no one should go on vacation ;)
19:41:02 <Nanar> ennael: ah ok, not my concerned
19:41:04 <Kharec> good night all, see you tuesday (or tomorow)!
19:41:19 <ennael> I will check with stew and let you know on -dev
19:41:27 <Stormi> will the secteam manage all updates to stable releases ?
19:41:30 <Stormi> even bugfixes ?
19:41:46 <ennael> at least manage process
19:41:50 <mikala> Stormi: well at least contact the maintainer
19:41:59 <ennael> but this has to be decided
19:42:00 <ennael> later :)
19:42:03 <Stormi> ok
19:42:06 <ennael> #topic maintainers management
19:42:11 <ennael> ok
19:42:21 <ennael> boklm: can you make wuick review about maintainers app ?
19:42:31 <Stormi> yes, be very wuick
19:42:48 <ennael> hum
19:43:05 <boklm> so there is a test version of maintainers app on http://www.maintdb2.mageia.org.uk/maintainers
19:43:06 <erzulie> [ Mageia maintainers database ]
19:43:46 <Nanar> \o/
19:43:53 * Nanar maintains hot-babe
19:43:57 <boklm> linked to BS
19:43:59 <mikala> 70 packages
19:44:04 <mikala> ouch
19:44:11 <boklm> first time someone submit a package, he becomes the maintainer
19:44:19 <andre999> nice - but wouldn't it be better in alpha order ?
19:45:22 <anaselli> mikala: i believe it's because of the imported packages... :)
19:45:31 <andre999> it says "  " has 0 packages
19:45:32 <boklm> work is on maintdb is done by Kosmas
19:45:49 <ahmad78> boklm: that's not right... I submitted packages I don't want to be maintianer of (rda said it won't stick in that stage)
19:45:51 <ahmad78> :)
19:46:26 <ennael> as a comment on this we are looking for people to help on this app
19:46:36 <boklm> yes
19:46:37 <ennael> to finalize it in a faster way
19:46:39 <Nanar> language ?
19:46:47 <andre999> where are packages submitted by trainees - under mentor ?
19:46:49 <boklm> currently it's done in ruby I think
19:46:54 <ennael> #action find developpers to help on maintdb app
19:47:17 <Nanar> where is the code
19:47:19 <Nanar> ?
19:47:26 <Nanar> in our svn ?
19:47:40 <ennael> boklm: any information ?
19:47:44 <boklm> Nanar: url for the code is on http://mageia.org/wiki/doku.php?id=web:maintdb
19:47:45 <erzulie> [ web:maintdb [Mageia temporary wiki] ]
19:47:53 <boklm> http://gitorious.org/mageia-maintainers-database-r2
19:47:54 <erzulie> [ Mageia Maintainers Database r2 - Gitorious ]
19:48:09 <ennael> #url http://mageia.org/wiki/doku.php?id=web:maintdb
19:48:09 <erzulie> [ web:maintdb [Mageia temporary wiki] ]
19:49:09 <boklm> the wiki page has all the specs of the interface it should provide
19:49:13 <shikamaru> well, is the second url you gave uptodate ?
19:49:18 <Nanar> look like this project is outside mageia
19:49:36 <boklm> shikamaru: I don't know
19:49:42 <Nanar> their own VCS, own bug tracker, etc..
19:50:09 <boklm> developement does not seem very active at the moment
19:50:38 <ennael> Nanar: this is something we can change easily I guess
19:50:52 <ennael> big priority now is to finalize it quickly
19:52:01 <ennael> anybody interested ?
19:52:06 <shikamaru> I am
19:52:11 <ennael> great
19:52:17 <shikamaru> but I need to know what is needed
19:52:18 * Nanar don't know ruby
19:52:21 <ennael> 1 victim^w^contrib
19:52:25 <anaselli> ennael: which language?
19:52:29 <ennael> ruby
19:52:49 <boklm> current version is ruby, but could be redone in an other language if it can be faster to redo it
19:53:21 <Nanar> redo it in perl + catalyst is possible
19:53:32 <boklm> what it needs to do is descrideb in the API on the wiki page
19:53:37 <Nanar> but will need time
19:53:44 <Nanar> who did it first ?
19:53:57 <boklm> Nanar: first version is done by Kosmas
19:53:57 <anaselli> boklm: i'm a c/c++ programmer... ruby is not that different... i could gave a look, but don't so much spare time at the moment
19:54:02 <shikamaru> boklm: http://mageia.org/wiki/doku.php?id=web:maintdb#todo ?
19:54:02 <erzulie> [ web:maintdb [Mageia temporary wiki] ]
19:54:19 <anaselli> maybe in the week-end... but you can trust me so much :/
19:54:22 <shikamaru> these 6 items right ?
19:54:47 <boklm> shikamaru: ah, I don't know if TODO list is up to date
19:55:06 <boklm> shikamaru: but there is list of POST and GET urls that the app should have
19:55:20 <shikamaru> but these should be specified
19:55:42 <boklm> shikamaru: what is not specified ?
19:56:02 <shikamaru> these lists of POST and GET urls
19:56:41 <boklm> shikamaru: there is the list in the page, with arguments and what it should return
19:57:43 <shikamaru> mmh well, let me rephrase then :)
19:58:38 <shikamaru> in this list some routes might be implemented, some not, it’s hard to see in the wiki page which one are implemented, which are not
19:58:45 <boklm> ah yes
19:58:57 <shikamaru> maybe bugs should be opened about that
19:58:59 <boklm> I don't know exactly what is already implemented
19:59:35 <andre999> right - the status of each routine should be listed
20:00:33 <boklm> it seems txt format (the most important) is not implemented
20:00:36 <ennael> ok so looks like we need to take some time with current dev and precise all this
20:00:40 <shikamaru> ah ?
20:00:51 <andre999> (implemention status)
20:00:52 <ennael> shikamaru: can you do it on -dev ?
20:01:10 <shikamaru> well, yes, or else even a rewrite would be a waste of time IMHO
20:01:33 <boklm> ah, json is working
20:01:37 <shikamaru> yep
20:01:40 <ennael> ok let's try this for now
20:01:53 <shikamaru> ennael: do what on -dev ?
20:01:57 <ennael> #action shikamaru will contact current dev and check real status
20:02:02 <shikamaru> ah
20:02:08 <shikamaru> ok
20:02:14 <shikamaru> need to check with rda and kosmas
20:02:15 <ennael> on -dev would be nice so that other people can follow
20:02:18 <ennael> yep
20:02:41 <boklm> also, we need instructions to be able to install this on Mageia servers
20:02:56 <shikamaru> boklm: I can do that
20:03:13 <shikamaru> #action shikamaru write a procedure to install maintdb on Mageia servers
20:03:21 <boklm> thanks
20:03:43 <shikamaru> I think misc said fcgi would be prefered over other methods right ?
20:04:20 <boklm> hmm, I need to check
20:04:34 <ennael> together with this we will have to write down the way we want to manage maintainers rights : rest of the world
20:04:46 <ennael> meaning: who can do what and how ?
20:04:58 <ennael> do we use teams for maintainance on some packages...
20:05:28 <ennael> shall we use the way we had in mdv or change it
20:06:08 * ennael killed everybody...
20:06:13 <anaselli> well ennael team is good for me, i mean maintainer group
20:06:45 <anaselli> but maybe for some packages could be discussed case ba case
20:06:47 <shikamaru> no battery left, I follow on the phone but might take some time to answer :/ be right back
20:06:58 <anaselli> i mean some maintainers don't want to share...
20:07:05 <pterjan> I think allowing to co-maintain package is nice
20:07:10 <ennael> well having teams might need to have some kind of leaders to manage team
20:07:26 <pterjan> not really team in most cases
20:07:33 <andre999> teams make sense for big packages -- and critical packages
20:07:56 <ennael> pterjan: well at least to be sure tasks are done inside team for bug reports for example
20:07:58 <andre999> so being able to list multiple maintainers would be a good feature
20:08:04 <ennael> not waiting for the others to do it
20:08:45 <pterjan> well I think there is no real need for a team then if one person is more responsible
20:08:56 <pterjan> that person can be the maintainer
20:09:03 <Stormi> a games team could be could
20:09:07 <Stormi> good*
20:09:19 <pterjan> Stormi: why ?
20:09:30 <ennael> pterjan: I know for example we may have 3+ guys for KDE for example
20:09:33 <pterjan> it means I can not maintain a game if I don't want to maintain other games ?
20:09:36 <ennael> maybe for kernel
20:10:00 <andre999> ennael: similar for gnome
20:10:04 <Stormi> pterjan: I don't know
20:10:22 <ennael> so lots of question we need to answer before starting
20:10:25 <Stormi> maybe being in the team doesn't mean you have to maintain all packages the team can tuoch
20:10:31 <ennael> how would you like to proceed ?
20:10:32 <ennael> ML ?
20:10:46 <andre999> maybe a wiki page
20:10:49 <pterjan> I think ML is nice to collect all things people want
20:10:59 <shikamaru> that depends on the workload
20:11:02 <andre999> so we can see all the ideas/proposals together
20:11:03 <anaselli> ennael: i would consider three or four areas
20:11:08 <pterjan> then it can be summarized somewhere after like a week
20:11:18 <ennael> so collect during a week comments on ML
20:11:21 <ennael> summarize
20:11:22 <pterjan> and we can have a dedicated meeting based on the info
20:11:23 <Stormi> maybe someone could look at the state of the art and propose a first draft we could then discuss ?
20:11:29 <ennael> and decide during meeting ,
20:11:31 <ennael> ?
20:11:33 <mikala> hum need to move
20:11:34 <anaselli> and then assign one of them to who are present more
20:11:37 <ennael> then write policy
20:11:56 <ennael> Stormi: state of the art?
20:12:03 <ennael> what other distros are doing ?
20:12:06 <Stormi> yes
20:12:09 <ennael> I guess this will comme as comments
20:12:14 <Stormi> ok then :)
20:12:15 <ennael> explaining what is good or not
20:12:29 <ennael> ok
20:12:37 <pterjan> yes I am sure misc knows how it works in other distros :)
20:12:54 <ennael> #action start 1 week discussion on -dev ML about maintainers policy for Mageia
20:13:08 <ennael> #action plan a meeting dedicated to that subject to decide final policy
20:13:15 <ennael> what about using next meeting ?
20:13:22 <ennael> next wednesday
20:13:33 <anaselli> ennael: fine for me
20:13:35 <pterjan> maybe,
20:13:44 <ennael> ok
20:13:45 <pterjan> depends how many other things are to be discussed
20:13:56 <ennael> well we can focus meeting on that
20:14:01 <ennael> I guess it's important enough
20:14:05 <pterjan> ok
20:14:12 <ennael> #undo
20:14:12 <Inigo_Montoya`> Removing item from minutes: <MeetBot.items.Action object at 0xb73fbccc>
20:14:25 <pterjan> wow
20:14:28 <ennael> #action next meeting will be dedicated to that subject to decide final policy
20:14:29 <pterjan> nice feature :)
20:14:33 <ennael> :)
20:14:52 <ennael> ok anything else to add on maintainers topic ?
20:15:18 <anaselli> mini team should be the mentor-padawan team :)
20:15:24 <anaselli> could
20:15:39 <shikamaru> ?
20:16:04 <anaselli> i mean mentor and padawan work on the same packages at the moment
20:16:25 <anaselli> so they could be a maintanership team
20:16:25 <andre999> so automatically co-maintainers ?
20:16:38 <anaselli> at least in the very first time
20:16:39 <andre999> makes sense
20:16:49 <Stormi> let's see that on the ML
20:16:50 <ennael> should not be too long
20:16:55 <ennael> big work for mentors
20:17:02 <ennael> #topic action plan until stable1 release
20:17:17 <ennael> about that topic we spoke about missing deps, packaging errors
20:17:18 <shikamaru> mmh well, a team is especially useful for one thing : assigning bugs to a group of people
20:17:39 <ennael> we have one thing to be done which is translations updates for mageia specific softs
20:17:44 <ennael> like drakx*
20:18:03 <ennael> work is done by i18n team but we shoukd start to integrate it
20:18:10 <ennael> many bugs are opened on it
20:18:22 <ennael> so we need guys who would take care of it
20:18:52 <shikamaru> do teams commit their work in svn ?
20:19:14 <shikamaru> which would mean we just need to rebuild these tools right ?
20:19:20 <ennael> Transifex is linked to svn
20:19:23 <ennael> if I'm not wrong
20:19:28 <ennael> shikamaru: yes
20:19:36 <ennael> but we need to be sure it will be done
20:20:12 <anaselli> ennael: so what are you looking for exactly? one person per language?
20:20:15 <shikamaru> ok
20:20:20 <ennael> nope
20:20:27 <ennael> people in charge with some packages
20:20:46 <shikamaru> anaselli: not the translations themselves
20:21:02 <shikamaru> just ensure they are spread on the mirrors
20:21:22 <ennael> #action we need people to take care of releasing new versions integrating last localizations
20:21:23 <shikamaru> instead of just laying in svn
20:21:40 <andre999> we need to ensure the internationalisation of things we develop
20:22:11 <ennael> yep
20:22:12 <shikamaru> andre999: that's i18n job, not ours
20:22:32 <anaselli> which is the hard work there? making new tarball for rpm package?
20:22:33 <ennael> well ensure work on localization is integrated in final packages
20:22:41 <ennael> anaselli: no hard work
20:22:49 <ennael> but work that has to be done
20:23:12 <ennael> it's easier if 2 or 3 guys can manage it in a systematic way
20:23:22 <ennael> then we can slap them if work is not done ;)
20:23:38 <anaselli> i'm out then :p
20:23:56 <ennael> ok another mail I will send on ML
20:24:00 <ennael> be ready for spam
20:24:07 <andre999> :)
20:24:20 <ennael> anything else to add on things to be done before stable release?
20:25:36 <shikamaru> 5 spots to look at
20:25:47 <pterjan> decide on a place for a big party
20:25:54 <ennael> sure :)
20:27:03 <anaselli> ennael: either of secteam we should discuss also on how to manage stable release, and stable updates
20:27:18 <anaselli> the policy i mean
20:27:27 <ennael> anaselli: this is for next meeting
20:27:30 <ennael> ok
20:27:35 <ennael> last topic
20:27:41 <anaselli> ok
20:27:52 <ennael> #topic ARM review
20:27:57 <ennael> and here is rtp :)
20:28:18 <shikamaru> :)
20:28:47 <ennael> rtp: can you give us a quick view of current ARM port and what we could have for stable release ?
20:30:38 <rtp> as some may have noted, I've merged a bunch of patches to get some rpm build/work on arm
20:31:17 <rtp> that makes on my repo about 700-800 src.rpm so enough to get a system booting to a minimal system
20:32:26 <rtp> unfortunately, due to gcc miscompilation, I'm rebuilding all of them. I've done about 160 of them and found also some new build issues which were not arm (like some pkgfindeps stuff)
20:33:13 <rtp> so, if all goes well and enough packages are rebuild, I hope that we'll have a small rootfs working on qemu and some kirkwood systems
20:33:56 <rtp> no guarantee about GNOME/QT as there are still some rpms missing
20:34:06 <blino> rtp: how about integration in the BS? can we steal a pandaboard for that?
20:34:39 <rtp> blino: we need a working kernel for it and some storage on it too
20:35:07 <shikamaru> mmh could it act as a bottleneck if we do ?
20:35:32 <shikamaru> or could the scheduler cope with that ?
20:36:09 <blino> rtp: we could try ndb for storage, if we can connect the ARM board to an other system with a direct 1GBps ethernet connection
20:36:20 <rtp> shikamaru: the scheduler must probably be adapted
20:37:38 <brianb> are you refereing to the kernel scheduler?
20:37:38 <rtp> blino: yeah. I was thinking of something like openrd + panda so that we'll have 2 nodes and one with real storage. the 2 ethernets port will help for that too as there's no encryption on stuff like nbd
20:37:49 <rtp> brianb: build system scheduler
20:37:56 <brianb> ok
20:38:22 <rtp> brianb: packages will take more time to build so waiting for them to upload the rpm will slow down things
20:38:51 <shikamaru> exclude libreoffice ! :P
20:39:00 <pterjan> rtp: it may work fine if in arch and not in mandatory_arch
20:39:27 <rtp> pterjan: build system is out of my knowledge so every input is welcome :)
20:39:48 <pterjan> upload of packages from a node happens if all mandatory_arch are done
20:40:06 <pterjan> but I don't know if it works fine :)
20:40:23 <blino> I think it did work at some point
20:40:29 <blino> when x86_64 was not mandatory
20:41:18 <blino> but maybe we did not even use this "mandatory_arch" approach, at some point x86_64 rebuild was done using iurt directly on the src repo
20:42:06 <rtp> we could do that too but a choice has to be made
20:42:12 <rtp> :)
20:42:15 <ennael> ok
20:42:41 <ennael> #info decisions has to be taken on build system side to integrate ARM
20:43:07 <ennael> rtp: anything to add on that topic ?
20:43:30 <blino> we will let Anssi decide about this
20:43:30 <rtp> I don't think...
20:43:38 <rtp> blino: :)
20:43:59 <ennael> ok Anssi will manage ARM port :)
20:44:21 <ennael> hum
20:44:23 <shikamaru> :)
20:44:37 <ennael> ok 1h45 I guess we can close meeting for today
20:44:44 <ennael> thanks all for attending
20:44:51 <shikamaru> thanks
20:44:56 <ennael> #endmeeting