*** DocScrutinizer05 has quit IRC | 00:00 | |
*** DocScrutinizer05 has joined #maemo-meeting | 00:00 | |
*** xes has joined #maemo-meeting | 00:55 | |
*** xes_ has joined #maemo-meeting | 01:08 | |
*** xes has quit IRC | 01:10 | |
*** xes_ is now known as xes | 01:13 | |
*** M4rtinK has quit IRC | 02:03 | |
*** xes has quit IRC | 03:15 | |
*** kolp has joined #maemo-meeting | 08:54 | |
*** DocScrutinizer05 has quit IRC | 09:14 | |
*** DocScrutinizer05 has joined #maemo-meeting | 09:14 | |
*** DocScrutinizer05 is now known as DocScrutinizer06 | 12:36 | |
*** DocScrutinizer06 is now known as DocScrutinizer05 | 12:37 | |
*** DocScrutinizer05 is now known as DocScrutinizer06 | 13:08 | |
*** DocScrutinizer06 is now known as DocScrutinizer05 | 13:08 | |
*** juiceme has quit IRC | 15:55 | |
*** RzR is now known as rZr | 20:31 | |
*** qwazix_ has quit IRC | 22:22 | |
*** xes has joined #maemo-meeting | 22:36 | |
*** peterleinchen_ has joined #maemo-meeting | 23:03 | |
* peterleinchen_ says hello | 23:05 | |
*** xes_ has joined #maemo-meeting | 23:12 | |
DocScrutinizer05 | hi! | 23:14 |
---|---|---|
*** xes has quit IRC | 23:14 | |
DocScrutinizer05 | sorry for being late | 23:14 |
peterleinchen_ | no prob, seems no one else is here | 23:16 |
DocScrutinizer05 | I'll not be here next week, and the two weeks after that | 23:16 |
DocScrutinizer05 | some off-time, finally | 23:17 |
DocScrutinizer05 | \o/ | 23:17 |
*** xes_ is now known as xes | 23:17 | |
DocScrutinizer05 | peterleinchen_: please highlight (or even better /query) me when sth pending. I'm 5m away from kbd, watching news | 23:19 |
peterleinchen_ | docscrutinizer05, okay will do so if some one appears ;) | 23:20 |
rZr | hi | 23:38 |
rZr | sorry i wont be able to attend this meeting | 23:38 |
rZr | i may connect later through my phone | 23:39 |
rZr | sorry | 23:39 |
rZr | anyway I confirm i got no answers from x-fade | 23:39 |
rZr | but I've got some feedbacks from his jolla workmate | 23:39 |
rZr | he is overloaded | 23:39 |
rZr | so may we got an answer later (or never) | 23:40 |
peterleinchen_ | okay, at least ... | 23:40 |
rZr | then for the future | 23:41 |
rZr | about coop w/ hifo and mc | 23:41 |
rZr | i will suggest to adopt a code of conduct | 23:41 |
rZr | http://www.kde.org/code-of-conduct/ | 23:42 |
rZr | https://github.com/Bantik/contributor_covenant | 23:42 |
DocScrutinizer05 | and how's that related to MC or HiFo? | 23:42 |
rZr | because there is electricity in the air | 23:43 |
rZr | now i am gone | 23:43 |
rZr | sorry i wish i could stay longer | 23:43 |
rZr | but i have to go | 23:43 |
* DocScrutinizer05 wonders what maemo council has in common with an open source project | 23:51 | |
DocScrutinizer05 | maemo council gets elected by community every 6 months, so community is king. council is both maemo council (which decides about maemo project related stuff like who gets permission to upload code to extras-devel etc) as well as HiFo's council which the HiFo board (community's cashier) supposed to execute what council asks for - unless it's a rogue or unlawful request. HiFo board is the entity that holds the financial and IP | 23:57 |
DocScrutinizer05 | assets and since it's bound to instructions from council, it makes sense that the board members are elected only once a year (or, for the e.V., maybe even less frequently, I haven't checked and actually don't care). I can't see where such code of conduct comes in on such scenario | 23:57 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!