19:30:06 #startmeeting translations 19:30:06 Meeting started Tue Nov 15 19:30:06 2016 UTC. The chair is pravins. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:30:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:30:06 The meeting name has been set to 'translations' 19:30:07 #meetingname translations 19:30:07 The meeting name has been set to 'translations' 19:30:07 #topic agenda and roll call 19:30:07 #info https://fedoraproject.org/wiki/G11N/Meetings/2016-11-15 19:30:22 hi all, who else available here today. 19:30:39 few members already said hi, before meeting. Adding them into chair 19:30:57 #chair jonatoni nolski jibec geohas 19:30:58 Current chairs: geohas jibec jonatoni nolski pravins 19:31:03 aeng: around ^^ 19:31:17 #chair noriko 19:31:17 Current chairs: geohas jibec jonatoni nolski noriko pravins 19:31:30 hi 19:31:34 hi 19:31:37 .fasinfo jibec 19:31:39 jibec: User: jibec, Name: Holcroft, email: jb.holcroft@gmail.com, Creation: 2012-11-09, IRC Nick: None, Timezone: UTC, Locale: C, GPG key ID: None, Status: active 19:31:42 jibec: Unapproved Groups: cla_fpca 19:31:45 jibec: Approved Groups: None 19:32:44 lets see upcoming schedule meanwhile 19:32:47 #topic Upcoming schedule 19:32:47 #link https://fedoraproject.org/wiki/Releases/25/Schedule 19:32:47 #info 2016-11-22 Fedora 25 Final Release (GA) 19:33:03 Still one week to go. Lets see if we can find some action item in todays meeting for F25. 19:33:31 o/ 19:33:46 sorry, wrong number nolski :( 19:33:50 .hello jonatoni 19:33:50 jonatoni_: jonatoni 'Jona Azizaj' 19:34:11 no worries :) 19:34:16 :) 19:34:23 We have many tickets today, lets start one by one. 19:34:29 #topic Badges for Trans team 19:34:30 #link https://pagure.io/g11n/issue/26 19:34:49 Basically for awarding badge we need some criteria. Most of the groups are using FAS groups. 19:35:06 We are using cvsl10n group from long time, this is mostly important to get Wiki and Voting access to trans team member as well. 19:35:16 I dont see any harm in using this group for awarding badges as well. 19:35:20 +1, cvsl10n FAS group is a good idea 19:36:05 he, I didn't get any badge for translating to german ... 19:36:11 Rather badge criteria will further push new members to join this group and it will solve other issues regarding Wiki and Voting auto. 19:36:22 .fas lailah 19:36:23 Kohane: lailah 'Sylvia Sánchez' 19:36:28 hi Kohane :) 19:36:32 #chair Kohane 19:36:32 Current chairs: Kohane geohas jibec jonatoni nolski noriko pravins 19:36:35 Hi 19:36:54 Haha, that was unexpected 19:36:54 Kohane, hi :-) 19:37:00 geohas: after this ticket gets fixed, you will definitely get one for Trans team member :) 19:37:13 Hi noriko 19:37:17 .fasinfo gmh 19:37:18 geohas: User: gmh, Name: Georg Hasibether, email: georg@hasibether.at, Creation: 2014-01-30, IRC Nick: geohas, Timezone: UTC, Locale: en, GPG key ID: 7F4CB4E8, Status: active 19:37:21 geohas: Approved Groups: magazine cvsl10n cla_fpca cla_done 19:37:23 +1 from me as well for using CVSl10n, i think no one opposed in mailing list as well. 19:38:14 So after this all members in cvs10n group will get trans team member badge, if anyone is not part of this group they can request membership. 19:38:26 piotr helped me quickly with approval :) 19:38:31 +1 19:38:56 if no one has objection, lets agree and move ahead. 19:39:03 yes, agree 19:39:22 #agreed To use cvsl10n for awarding badges to translation team members. 19:39:25 great, thanks. 19:40:02 #topic T-shirts for active contributor 19:40:03 #info https://pagure.io/g11n/issue/32 19:40:09 Thanks to council for approving budget for T-shirt. 19:40:24 and also thanks to aeng for providing list of users with 500+ commits. 19:40:44 Oh, it's on Pagure now! Nice. 19:40:50 Morning 19:40:59 aeng_: hi :) 19:41:13 aeng_: Morning 19:41:17 Kohane: yeah, we have migrated g11n trac already. Thanks to paragan. 19:41:33 As per stats, we have 78 members. 19:41:43 I think, we should make this 100 19:41:53 Yes, I agree. 19:42:03 Yup round the number 19:42:17 jibec suggested to award T-shirt to language team has only 1 members etc. It will help to promote our tras activity in particular region. 19:42:23 I agree with pravins 19:42:54 Sounds good. but how many extra? 19:43:13 78+22 19:43:53 +1 19:44:09 +1 19:44:14 Also for members like me, jonatoni who not translating much but helping with organization. If no objection from other. 19:44:14 +1 19:44:18 As long as it's in the budget 19:44:34 I have no objections from my side. 19:44:38 right. 100 number is good also in sense we can get good cost. 19:44:40 great. 19:44:46 #agreed for 100 T-shirts 19:45:00 pravins: nothing against jonatoni, but only if we have room for such exceptions ;) 19:45:01 +1 for me :) 19:45:26 jibec: exactly, so feel free to nominate such members. 19:45:38 We dont have much room. 19:45:58 i'll suggest from the two lists aeng extracted for council 19:46:11 #info Team members please nominate few person, who are not in criteria but actually helping lot to Translation group overall. 19:47:01 And where should we nominate these persons? 19:47:02 jibec: not understood suggestion. can you clarify more. 19:47:16 First thing that we need it's to have the design for the tshirts, after that we can see if we have enough budget for 100 tshirts or more 19:47:53 Kohane: we will plan for that, no idea as of now. 19:48:01 Okay, thanks 19:48:04 jonatoni: yeah and we need someone to lead that. 19:48:11 Also we need to plan for distribution strategy. 19:48:29 Yeah. Priority is still for the initial 78 members. 19:48:34 Also we need to think about the costs of distribution 19:48:41 aeng: definitely. 19:48:58 I can help with this 19:49:00 what if someone wants to ave that t-shirt but is not on the list? Can he/she get it if will donate some money to cover shipment or other costs? 19:49:11 Lol.. yup, that why the more regional to cover the higher the cost 19:49:32 zdenek: thats nice idea. 19:49:57 #idea if someone not on list but want T-shirt can he purchase with own money or some contribution. 19:50:11 jonatoni: great. 19:50:13 +1 19:50:20 +1 19:50:24 +1 19:50:30 +1 19:50:31 DeVconf is soon any many people travels their, it can help for distribution. 19:50:42 are you sure we get money by selling t-shirt? 19:50:47 Devconf or FOSDEM 19:50:58 also we should ask redhat for covering some costs 19:51:03 may we also reuse l10n badge logo and this tshirt? 19:51:22 Well keep in mind it's only for translators. Not just anyone who wants the tshirt 19:51:38 geohas: yes, i think we can get some help from Red Hat 19:52:19 aeng: yes, may be more specific from your second list which has 168 members ;) 19:52:40 aeng, donaters for translation 19:52:57 I hesitate to give +1 for purchase option of t-shirt. 19:53:14 Tbh i agree with noriko 19:54:04 what i think, if one want to purchase, they can directly contact the vendor, so no one will be involved other than vendor and person who wants T-shirt 19:54:15 but if it looks problematic lets drop the idea. 19:54:23 For the next fiscal year we can produce more tshirts for other contributors that will not have the chance to get one now 19:54:25 +0 for tshirt purchasing (not blocking no) 19:54:38 sure. 19:54:59 #agred Lets not make it more complicated by adding purchase option to it. 19:55:07 ok 19:55:08 Moving on 19:55:09 #agreed Lets not make it more complicated by adding purchase option to it. 19:55:32 #topic Fedora 25 Virtual translation sprint 19:55:33 #link https://fedorahosted.org/G11N/ticket/29 19:55:45 Kohane: only remaining task was to publish report. 19:55:51 Did you able to publish report? 19:55:59 not heard anything recently about it. 19:56:38 does anyone else has an update on communityblog report for Translation sprint? 19:57:07 We can ask jflory7 19:57:26 yes. 19:57:41 but does Kohane submitted it to commblog? 19:57:51 i remember i reviewed it once. 19:58:06 sure, lets ping jflory7 and Kohane later 19:58:22 #action pravins to ping jflory7 and Kohane later for translation sprint reprot. 19:58:32 next one 19:58:33 #topic No active coordinator for Malayalam 19:58:33 #link https://pagure.io/g11n/issue/31 19:58:41 This has been regular issue now. Few language group coordinator are not active and it actually hamper entry to new members. 19:58:49 What do you suggest for this? 19:59:05 Oh, I'm sorry, I momentarily got distracted 19:59:18 I'm helping a friend to open a ticket, I'm sorry 19:59:53 Kohane: no problem :) do update on Translation sprint report, you did nice by adding interviews to it. 20:00:00 First we need to talk with the coordinator 20:00:14 pravins: no, I didn't publish the report, I'm sorry. I'll do so these days. 20:00:21 Thanks! 20:00:27 Kohane: sure. 20:00:28 To see why he is not active 20:00:39 #action Kohane to publish Translation sprint report. 20:00:41 I heard similar situation for Hindi. 20:00:45 at fudcon. 20:00:50 Identify those peo0le and communicate with them. 20:00:53 Yes, I saw that... 20:01:11 We need some to follow steps for this issue. 20:01:16 If no response, nominate new coordinator 20:01:30 noriko: even i see coordinators for few languages are not at all active for year but still holding position. 20:01:32 Agree with aeng 20:01:48 yes, it should happen quickly otherwise new one who step in can give up and gone. 20:02:18 Me too feel same. 20:02:28 Yup. We just need to monitor the mailing list when new member request to join 20:02:47 for Malayalam case, its actually more than month now. 20:02:52 Person is still waiting. 20:02:52 It taken too long, someone need to step in and check 20:02:54 Pedro from the Portuguese Portugal team is still waiting for approval 20:03:26 Can we make some criteria here? 20:03:35 Yes, it would be good 20:03:38 can we nominate coordinator for empty translations teams? So in case there is new translator, this "universal" coordinator can quickly grant the rights 20:03:47 Like if no response in one week, escalate to trans list and then Admin can takeover it? 20:04:04 Good idea 20:04:11 one week.... 20:04:24 might be too short for community coordinator... am not sure. 20:04:57 One week personnel request, then 2nd week by cc'ing on trans list? So 2 weeks. 20:05:09 people can take holiday... 20:05:52 I think 2 weeks is a reasonable... 20:06:22 noriko +1, it can wait the release if slow answer 20:06:27 yes, but on the other hand there's someone who's waiting and maybe feel discouraged if nobody replies after so much... 20:06:40 only if there is no activities/posts in the mailing list for a couple of weeks? 20:07:01 This has been long standing issue. 20:07:13 jibec, good point. 20:07:46 hmm, but we are not still with clear criteria for escalate. 20:07:54 hmm, time is running. 20:08:09 Make it 2week before escalate to tranlist? 20:08:23 yes, 2 Weeks looks reasonable. 20:08:25 +1 20:08:31 +1 20:08:40 +1 20:08:47 Would someone like to takeover it and add criteria to Wiki, we can then further work on it. 20:08:50 escalate to trans list sounds good. 20:08:59 Section might be #Unresponsive coordinator 20:09:36 #agree Wait for 2 week for response from coordinator else escalate to Trans list and then admin can takeover. 20:09:39 but 2 weeks should not grant new coordinator automatically, right? 20:09:53 It will also add some responsibility on coordinator for replying in time. 20:10:11 noriko: no, after 2 weeks admin can think on it. 20:10:24 so more time for coordinator :) 20:10:33 i forgot to add action item for T-shirt 20:10:36 k : 20:10:43 :) 20:10:50 oh, what are we talking about? publishing of report or the process to handle coordinator desertion?? 20:10:50 #action jonatoni to help with Vendor stuff. 20:11:17 anyone else want to join jonatoni for T-shirts? i will help with identifying 78 members region. 20:11:23 jibec: yes 20:11:23 for report, 2 weeks is great, for coordinator, it's way more difficult 20:11:34 here to join 20:11:59 jibec: yeah, if coordinator is not responsive. 20:12:00 we should not write definitive rules, as every situation is different and need open discussionn 20:12:28 hmm, but at least we need something minimal 20:12:44 the process. 20:13:04 We need steps for the members if their coordinator is not responsive in the given timeframe 20:13:06 yep, but we do not decide that kind of things without planning, thinking and agreeing 20:13:14 I think there must be some kind of time limit 20:13:26 2 weeks 20:13:27 A person who wants to translate can't wait forever 20:13:34 yes, 2 weeks is fine 20:13:45 jibec: yes, lets start with draft, take opinion and then move ahead. 20:14:10 #action pravins to open ticket for unresponsive coordinator. 20:14:19 lets communicate on ticket further 20:14:24 two weeks to promote user to translator is no big deal, two weeks to propose a removal of coordinator is not good 20:14:38 We are talking about removal 20:14:41 Not 20:15:02 It's just ways to allow members to proceed 20:15:12 right. 20:15:27 not removal rather for approving new members. 20:15:32 ok, let's write it in the draft then, thanks for the details 20:15:40 next ticket 20:15:40 moving to next one. 20:15:46 #topic "L10N - New wiki structure proposal" 20:15:47 #link https://pagure.io/g11n/issue/34 20:16:04 where are we on new structure now. 20:16:33 * jonatoni_ needs to go home (sorry) 20:16:49 jonatoni: sure. happy journey :) 20:17:12 jibec: i think, proposal already in this stage from long time 20:17:13 nice ods 20:17:14 Gonna prepare me and my kids now. See yall 20:17:15 Here I have a question: Is https://pagure.io/g11n/ a replacement / successor of https://fedorahosted.org/G11N/ please? 20:17:20 if no any objection, i think we can move ahead. 20:17:45 so if I need to open ticket, should I go to pagure or to fedorahosted? 20:17:54 aeng: noriko does having meeting 30min earlier will help here? 20:18:09 zdenek: yes. we are using it now. 20:18:20 zdenek: perfect. 20:19:01 pravins: we should then move ahead 20:19:17 nobody said it was bad, so let's assume it's ok 20:19:36 zdenek: yes, trac was migrated to pagure 20:19:54 jibec: yes, actually having some restructure like this will be nice. 20:20:00 ok, thanks for confirmation. The new Wiki structure proposal if OK for me 20:20:10 for me too 20:20:11 +1 20:20:15 +1 20:20:16 +1 20:20:22 +1 ;) 20:20:24 +1 20:20:34 #agree To move ahead with new Wiki restructure proposal. 20:21:04 agree 20:21:05 jibec: do once say, you are starting for implementation on trans list. 20:21:07 sorry are we talking aobut https://pagure.io/g11n/? 20:21:25 noriko: nope, new Wiki restructure proposal. 20:21:31 about #link https://pagure.io/g11n/issue/34 20:21:36 https://pagure.io/g11n/issue/34 20:22:47 noriko: do reply on list, if you have any suggestion on proposal for restructure. 20:23:17 meanwhile moving to next ticket 20:23:30 .hello skamath 20:23:31 skamath: skamath 'Sachin S Kamath ' 20:23:35 sure, jibec pravins, is any possible impacts list? 20:23:36 Hi all :) 20:23:39 hi skamath :) 20:23:50 Hi 20:23:57 We just discussed your ticket regarding Non responsive coordinator. 20:24:12 My scrollback is too long :P 20:24:20 I am connecting to IRC after 5 days or so 20:24:21 noriko: can someone approve skamath, he is waiting for membership frm last one month. 20:24:36 That'd be great. 20:24:52 .fasinfo skamath 20:24:52 geohas: User: skamath, Name: Sachin S Kamath , email: sskamath96@gmail.com, Creation: 2014-11-12, IRC Nick: skamath, Timezone: Asia/Kolkata, Locale: en, GPG key ID: 10EDC863, Status: active 20:24:55 geohas: Approved Groups: cvsl10n freemedia fedora-join summer-coding fi-apprentice commops cla_fpca cla_done 20:24:55 Ani is not active from last couple of month. 20:25:36 moving to next ticket 20:25:42 #topic The Piwik usage in fedora.zanata.org 20:25:42 #link https://pagure.io/g11n/issue/30 20:25:43 Can we close this ticket, if no further issues? 20:26:02 give me a moment to read 20:26:29 sure. 20:26:34 Can I benefit from Piwik as a user? 20:26:57 remove piwik +1 20:27:15 Or this is something running on background and I cannot see its stats? 20:27:21 geohas: but its actually helping to get statistics and helping Zanata 20:27:28 I feel for this issue, we should have zanata member to represent and vote. 20:27:39 noriko: definitely. 20:27:55 I think we came to conclusion for this ticket. 20:28:00 noriko, you are right 20:28:23 well, the proposal was to remove Piwik, and it is now just to make data anonymous and let L10N admin access it 20:28:27 I think we should remove piwik 20:28:33 Since Paul frield confirmed on ticket, Piwik is not violating Fedora policy. 20:29:13 so, only use zanata with ghostery and ublock origin? 20:29:40 jibec: Data is already anonymous, since its only ip. 20:29:47 not username 20:29:55 pravins, my IP does not change, it's not anonymous 20:30:13 pravins, definitely a problem for static IP's 20:30:45 well, mine isn't static AFAIK but.... 20:30:56 same here, no static 20:31:02 But then, what bad can piwik on Zanata do if it is only tracking the IP's? 20:31:13 pravins: what is the vote ? should we decide on remove piwki or keeping it with a mecanism to make data anonymous and L10N admin access ? 20:32:23 Fedora is already using ip's for generating stats on our dnf update etc. (correct me if wrong) 20:32:29 and anyway, most companies are tracking their consumers, I think we should not accept this in an open-source community 20:32:58 does ip == users. Then its big problem. 20:33:07 If you're worry about IP, is all over fedora now. With your username too. 20:33:09 I dont know, how it will work for static ip. 20:33:23 Irc 20:33:34 Everything. 20:33:40 pravins: as we do not know the settings of piwiki, it can gather way more information, like where you click and many information about visitor 20:33:54 jibec, as far as I understand, piwik uses it only to maintain statistics of a user and not "activity" of the user 20:33:56 I think piwik should be removed 20:33:57 Jibec, it's only ip 20:34:19 again: should we decide on remove piwki or keeping it with a mecanism to make data anonymous and L10N admin access ? 20:34:25 Skamath, not exactly. It keeps track of page visits 20:34:50 aeng_: can Fedora infra access Piwik? 20:34:53 I doubt if even we can decide this in this meeting with limited people. 20:35:08 Nope. It's internal redhat 20:35:31 i strongly feel, Fedora infra is much proper team to investigate or have such access. 20:35:47 But as far as replied from Paul and infra fedora, it is not doing anything wrong 20:35:57 yes, I agree, infra is much proper team 20:36:06 but I think piwik should be removed 20:36:07 yeah. that is why i feel its fine. 20:36:19 aeng_: you said you wanted the point of view of community, you got it 20:36:40 jibec: this is more kind of issue we should discuss on council may be. not sure though 20:36:40 even if no vote is made to express it 20:36:46 Yeah. But I won't be down if it's a wrong decision 20:36:50 I don't agree with the page tracking, which piwik does 20:37:17 I'm happy to removed it tbh. But keep in mind the ikpact 20:37:51 Impact of we not knowing priority on each pages 20:37:54 how does removing piwik affect the translating process? 20:38:11 please again, I don't like to have a vote to decide on this issue in this meeting with limited people. 20:38:29 It will not impact the process. But we use when designing page and understand user behaviour 20:38:31 i feel, its definitely not user tracking or spying but moderately generating stats for process improvements. 20:38:35 aeng_: I offered an alternative with community control, I do not understand why RH want to block this 20:38:49 noriko: what do you mean by limited ? 20:39:01 RH is blocking what? 20:39:08 I second what pravins just said. 20:39:11 It's not about RH 20:39:11 noriko: yes, we will definitely not take vote here. 20:39:13 the votes we can gain in this meeting is not whole voice of entire translation team. 20:39:23 we can still vote for good, but not this issue. 20:39:28 noriko: +1 20:39:52 noriko: what is your suggestion to get the "entire translation team" approval? 20:39:57 noriko: that's true but what do you suggest for this particular issue? 20:40:06 jibec: it means more wider discussion :) 20:40:11 How about a ML thread? 20:40:14 as pravins mentioned, I support to escalte the issue to council? 20:40:36 yes, make sense. 20:40:38 that would be nice 20:40:56 Yeah 20:41:01 escalate what? 20:41:27 because there just seems to be a general statement which the council will probbaly send back 20:41:27 smooge: the issue we're discussing 20:42:01 #link https://pagure.io/g11n/issue/30 20:42:10 but anyway, i think lets move ahead 20:42:18 take this ticket either on mailing list or next time. 20:42:26 #topic Fedora 25 planning 20:42:27 #link https://pagure.io/g11n/issue/24 20:42:40 smooge: disagreement if we should keep piwiki as is (Zanata/RH controlled), remove it, or accepting to remove any personnal data and give community admin access 20:42:56 ip addresses are logged in many places by many different parties including many of the the isp's that your packets are crossing 20:43:03 Unfortunately we do not have talking points for Fedroa trans team 20:43:13 We need someone to take over this and create some talking points. 20:43:27 smooge, I feel that the issue beyonds the point we can say yes or no to remove. 20:43:34 It can be something like language with 100% or 80% + translations. 20:44:20 Anyone interested in writing Talking points from translation team for Fedora 25? 20:45:24 pravins, let this the meetbot do 20:45:33 I did it for french https://fedoraproject.org/wiki/User:Jibecfed/F25-pr%C3%A9sentation_communaut%C3%A9_francophone 20:45:45 wow, that nice. 20:45:47 but for global talking point, we need stats 20:45:53 wich I do not have 20:46:17 aeng_: as usual, can help with it. 20:46:40 jibec: page looks nice. 20:46:56 thank you, french marketing team asked for it 20:47:03 nice. 20:47:12 yes, very nice 20:47:25 pravins: ? 20:47:52 aeng_: some stats required for preparing Fedora 25 talking points for translations. 20:48:03 jibec: may be you can send email, with the requirement. 20:48:04 if aeng_ provides stats, it's not too difficult to produce for F25, but we need to iterate a lot to find and use usefull numbers, it depends on his availability 20:48:24 i said to the spanish team befor, i would like to translate F24 installation guide. but perhaps it would be better to do that with F25 IG 20:48:42 Protoanima: with F25 now :) 20:48:53 i means, with F26 ... 20:48:57 ok 20:49:02 26? 20:49:06 Protoanima, Pravins: there is nothing from docs team published for F25 in Zanata 20:49:15 i'll check if there are documents 20:49:20 F25 is about to be released 20:49:35 please see: https://pagure.io/docs-fp-o/issue/30 20:49:45 #info Docs team has not published Installation guide in Zanata 20:49:56 Kohane:yep, but even F24 translated content wasn't published 20:50:17 please see: https://pagure.io/docs-fp-o/issue/28 20:50:29 then how can i help? 20:50:35 i thought, F26 is fine, since we have good time for it now. F25 only 1 week. 20:50:41 you can't with docs, wait and see ;) 20:50:57 Protoanima: do comment on this ticket regarding, you want to translate but its now available, 20:51:26 We already have long meeting 20:51:34 from 1 hr to already almost 1.5 hr 20:51:37 can't find documents for f26 20:52:04 Protoanima: yeah, as said by jibec , it not available for f24 as well. So we need to ping. 20:52:10 Lets wrap up here. 20:52:18 #topic Open Floor 20:52:33 ok 20:52:45 any urgent points, if we missed. 20:53:02 noriko, can you approve my membership here : https://fedora.zanata.org/language/view/ml?dswid=3634 20:53:10 ahhahaa, funny enough we worry about ip and username, where our log already got it anyway 20:53:42 even IRC bot 20:54:13 aeng_: please keep your comments for the incomming council ticket, we'll have oppotunity to debate 20:54:23 im tired of all these 20:54:37 skamath, user name 'vaveej'? right? 20:54:38 done 20:54:40 aeng: jibec its not matter of only piwik and zanata 20:54:44 noriko, skamath 20:54:51 arg 20:54:52 its global issue and we need to find best practices around it. 20:55:00 skamath: done 20:55:10 In fedora we already have lot of site and we just need to see what are we doing already. 20:55:13 pravins: +1 20:55:19 Thanks! :) 20:55:20 Again i feel infra team can help here. 20:55:25 how? 20:55:36 thanks aeng 20:55:53 smooge: since Infra managing many Websites etc. 20:56:01 aeng_: and please note that you said Zanata is not Fedora related, so it's not like infrastructure-team managed 20:56:32 jibec: infra team already commented and mentioned they are doing the same thing 20:56:41 which means your ip, username is all over the place right now 20:57:23 the irc you;re in right now, its has your ip and username too 20:57:32 better use VPN and tunnel 20:57:34 in that case there is no point for zanata to stop... 20:57:57 noriko: yeah, as i said. Zanata is not only portal we are managing in Fedora. 20:58:09 see 20:58:24 This debate will not over here 20:58:26 even i can search for your ip region in irc 20:58:27 aeng: i'll take your word for that 20:58:30 at least in Open floor :) 20:58:41 so lets stop here 20:59:03 Thanks all for the meeting. Lets try to meet soon again, till that lets have discussion in mailing list. 20:59:11 #endmeeting