14:04:38 #startmeeting famsco 14:04:38 Meeting started Wed Aug 17 14:04:38 2016 UTC. The chair is potty. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:04:38 The meeting name has been set to 'famsco' 14:04:45 #topic Roll Call 14:04:49 .hello potty 14:04:50 potty: potty 'Abdel G. Martínez L.' 14:06:28 .fas cwickert 14:06:28 cwickert: cwickert 'Christoph Wickert' 14:06:35 .fas tuanta 14:06:39 tuanta: tuanta 'Truong Anh Tuan' 14:06:49 .fas gnokii 14:06:50 gnokii: gnokii 'Sirko Kemter' 14:07:52 Right now we are 4/7 14:08:54 gnokii, tuanta, cwickert: I see 2 topics to discuss today: FOSCo transition (#373) and Mentoring improvement (#359). 14:09:05 Do you have another topic to include on the agenda? 14:09:45 potty: 398 14:10:20 cwickert: right :) thank you! 14:10:25 let's start then 14:10:34 #topic About the ambassador status of amsharma 14:10:39 .famsco 398 14:10:41 https://fedorahosted.org/famsco/ticket/398 14:11:08 Latest update on this ticket was from tatica: 14:11:12 "She already apologize herself, twice on this ticket. Her FAMA ticket was closed and she will keep working with us at Diversity until she decides if she wants to re-aply for ambassador once she feels she wants to. Please, lets all move on." 14:12:00 ok, let's close this and tell kushal to reopen if he is not satisfied 14:12:22 he is not satisfied 14:12:47 gnokii: oh, how do you know that? 14:12:56 because I spoke with him 14:13:48 gnokii: did he told you does he need to be satisfied? 14:14:44 yes I would like to quote it but my net is to bad cant open pages, the comment to that was it was in a public channel so it should be also an excuse in that 14:15:24 gnokii: :( ok... 14:15:45 sorry gnokii i don't get it 14:16:15 potty: kushal wanted a public apology, but I'm not sure if he will and can get it 14:16:28 frankly speaking I think it will just make things worse 14:16:32 cwickert: got it 14:16:36 cwickert: +1 14:16:40 the channel is not logged and there were not that many people present 14:16:55 I think that to, I suggest we close it and invite both in a closed channel to have a talk 14:16:58 the more we talk about it, the more people will get to know about the accoustations 14:17:25 even though the accusations were wrong, it will do damage to both of them if we have a public fight 14:19:31 So, what will be our action on this? 14:19:43 1. Close the ticket and invite them to a closed channel. 14:20:05 2. Close the ticket appealing that amsharma made her apologies on the ticket. 14:21:19 ? 14:22:11 This case may be more complicated. But yes, it's best to close it and discuss with them privately. 14:22:31 cwickert, gnokii ? 14:22:54 potty: we need somebody to talk to kushal. not sure if tatica is to do it or somebody else 14:23:01 potty look, I suggested 1. so I made my position clear 14:23:09 gnokii: understood 14:23:37 i can do it again 14:23:40 cwickert: tatica said she will finish the mediation on this issue 14:23:49 not sure if she made it through this week 14:23:50 gnokii, potty: what do we consider a 'closed channel' in this context? Is mail ok? 14:24:04 cwickert: i think mail is the best option 14:24:35 cwickert: I think both have to talk about what they expect from each other, so mail would be endless long then and for my side sorry tatica isnt objective 14:25:21 gnokii: you mean balanced, not objective 14:25:26 moin 14:25:30 hi tatica, thanks for coming 14:25:39 np, thx for the heads up 14:25:53 we are just discussing #389 14:26:11 hi tatica :) 14:26:16 oi potty :) 14:26:25 please continue, don't let me interrupt 14:26:36 tatica: we'd like to close the ticket because we feel the more we talk about it, the more damage will be done. 14:27:07 you say Amita apologized, but it seems kushal wants a public apology 14:27:09 cwickert, I thought the ticket was already closed 14:27:13 .fas giannisk 14:27:13 giannisk: giannisk 'Giannis Konstantinidis' 14:27:18 ,hello tatica 14:27:43 .hello tatica 14:27:43 * giannisk waves at everyone 14:27:44 tatica: tatica 'Maria Gracia Leandro Lombardo' 14:28:29 welcome giannisk 14:28:42 cwickert, I saw Amita apologize twice on the ticket, isn't that a public ticket? 14:29:35 tatica: I think kushal expects something like a 'mea culpa' mail to ambassadors list or so. I think this would make things worse 14:29:50 ping kushal 14:30:14 kushal: let's keep thing simple. What is your expectation with "public apologize"? 14:30:39 Seriously, are we still talking about this? :) 14:30:42 well the problem might be that an excuse with words like ïf i have insulted somebody....¨"is for some ppl meaningless 14:30:54 Let's move on, please 14:31:19 She apologized, case resolved. 14:31:45 giannisk: the case is only resolved if both sides agree 14:32:02 and I don't think kushal is really happy, is he? 14:32:05 giannisk: i agree with cwickert. One sided agreement is not an agreement. 14:32:22 potty, pong 14:32:24 +1 cwickert 14:32:27 cwickert: So, what else does the other party expect from amsharma? 14:32:47 none of the sides are happy, and none of the sides will be, this is about closing an uncomfortable moment 14:33:11 Hi kushal. When you mean "public apologize", which specific channel you are talking about? 14:33:26 potty, just saying sorry for saying wrong things (which are not true) about kushal should be enough. 14:33:29 giannisk: As I said, I think kushal wants a public apology. Either way, it's on us to find out, so we need to talk to him 14:33:38 potty, in that same ticket will do. 14:33:45 ok, cool 14:33:47 cwickert: He had his public apology, twice :) 14:33:47 thanks kushal 14:33:50 case closed 14:33:52 Good. Thank you very much kushal 14:34:12 #chair cwickert giannisk tuanta gnokii 14:34:12 Current chairs: cwickert giannisk gnokii potty tuanta 14:34:25 giannisk, there was nothing about trying to destroy my name. 14:34:43 kushal: can we close the ticket or not? 14:34:54 if not, what else do you want us to do? 14:34:55 cwickert, I need that statement on the ticket. 14:35:04 kushal: honestly, I doubt anyone tried to destroy your name :) it depends on how you perceive things 14:35:25 cwickert: ticket has already been closed, for the record 14:35:37 giannisk, every one on that channel thought I said those things, that is same of destroying my name. 14:35:40 I never lied. 14:36:23 kushal, would be enough a sorry for missunderstand thing? 14:36:32 amsharma on comment #40: "I did not mean to rude or hurt anyone. Please excuse me if that is the case here or on IRC or anywhere else." 14:36:46 tatica, there was no misunderstanding. 14:36:48 for me, that's an apology to he honest... 14:37:06 If FAmSCo says so. 14:37:08 tatica: would be an issue if amsharma write down the specific words: "I am sorry for saying wrong things (which are not true) about kushal" 14:37:08 Close the ticket. 14:37:23 I think I got in the middle of a personal rivalry 14:37:38 tatica, now that is not what I expect from you. 14:37:41 Amita, you're reading, is that something you're comfortable with or not? 14:37:41 tatica: that's the job of the mediator ;) 14:38:00 For record I have already nominated sankarshan_away for Fedora Ambassador mentor. 14:38:03 I will be honest with you and say that this is becoming a drama. :) She apologized, let's move on. 14:38:14 giannisk, yup, as I said. 14:38:22 cwickert, close the ticket. 14:38:25 kushal, be in my shoes, I try to solve things but nothing seems enough. I have a bit of frustration as well, even if I try to be as calm as possible 14:38:26 tatica, kushal, Amita: I think the three of you should work this out in private and not in public 14:38:33 cwickert, same 14:38:50 tatica, cwickert just move on. 14:38:52 is that ok with kushal and Amita ? 14:38:52 * cwickert feels sorry for bringing this up again 14:39:39 cwickert: It was necessary. We are humans at the very end and we have to be able to solve this kind of issues. 14:40:25 potty: yes, but I doubt this meeting is the right place to discuss this. I just wanted to make sure both sides are fine. Everything else should be handled in private communication. 14:40:36 kushal: I'll get back to you by mail later, ok? 14:40:42 cwickert, okay, thanks. 14:40:45 cwickert++ 14:40:47 let's move on the meeting 14:41:59 famsco: Let's move te topic to FOSCo transition. 14:42:09 #topic Proposal: consider tranforming FAmSCo into "FOSCo" — Fedora Outreach Steering Committee 14:42:17 .famsco 373 14:42:17 https://fedorahosted.org/famsco/ticket/373 14:42:33 Do we have any updates here? 14:43:02 So basically, during the "Meet your FAmSCo!" session at Flock, we considered starting with a minimum FOSCo 14:43:14 Which would be consisted of ambassadors + marketing + design + commops 14:44:18 giannisk: I am just writing a mail to FAMSCo list 14:44:22 and calling for a vote 14:44:28 cwickert: awesome 14:44:29 on this particular question 14:45:30 ok 14:46:47 Anything else here? 14:47:12 https://fedorahosted.org/famsco/ticket/373#comment:35 14:47:32 Nothing specific, apart those things that I have written on the ticket. 14:48:12 I just believe that we have to be agile, if we really want FOSCo to happen anytime soon. 14:48:15 I just sent the mail 14:48:21 and will update the ticket now 14:48:24 That is, start with a bare minimum and expand later on. 14:48:24 giannisk: totally agree 14:48:34 giannisk: like an os? 14:48:53 more agile in thinking on consequences 14:49:21 potty: haha, like software development, sure 14:49:30 giannisk: ;) 14:49:48 gnokii: I don't see any severe consequences; and if any "issues" occur, we can fix them quite easily 14:50:17 I can give you an answer to it, but you would cry then 14:50:54 gnokii: Go on :) 14:52:05 all: please cast your votes in the ticket now 14:52:31 s/all/giannisk, tuanta, potty, gnokii 14:52:42 I'm on it right now 14:53:03 potty: you might want to reload, I just posted. just simple +1, 0 or -1 14:53:43 yup 14:53:45 thanks 14:53:48 * potty voted 14:53:53 I am trying to open the ticket. My internet connectivity is not good now. 14:54:00 * giannisk as well 14:54:34 cwickert++ 14:54:34 potty: Karma for cwickert changed to 8 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:54:38 giannisk++ 14:54:43 yeah, we might have the same problemm 14:55:14 cwickert: remember to vote (: 14:55:59 gnokii, tuanta: you still have a week. I think it should be possible to find a place with working internet connection within this period. If not, there is not much FAmSCo can do for you, we cannot wait forever, otherwise we don't get anything done. 14:56:29 A week is ok for me :) 14:57:54 Ok. Let's move on. 14:58:07 Do anyone got extra opinions on this topic? 14:58:17 If not I will change to the final topic 14:58:53 let's move on 14:59:16 #topic Reorganizing Ambassador Mentoring 14:59:21 .famsco 359 14:59:21 https://fedorahosted.org/famsco/ticket/359 14:59:48 tatica: you still around? 14:59:54 yup 15:00:06 may you explain a bit what you posted on the ticket? 15:00:15 sure 15:01:03 so jflory7 had a great idea with the badges missions (which were already at a proposal mizmo had earlier). It won't be about the full mentoring process, but there are some basic things everyone need to do prior being awarded as a mentor 15:01:45 I have been in talks with mizmo a lot about this general idea, and right now as we speak I'm building a larger proposal for the "team badges missions" she was already working on, using the existing badges platform 15:02:26 I just want to be clear that this is merely for the basic mentoring tasks, not removing the human component. It's important to have the mentoring persona there to advice when things are in the good or bad way 15:02:50 but with a mission complexion (which can be several missions depending on the mentee skills) will be easier to follow progress 15:03:15 I'm up for any question/discussion 15:03:33 again, it's a merely proposal. may go or not 15:03:46 thank you, tatica 15:03:53 np 15:03:55 * giannisk will be away from keyboard for a while 15:04:02 toughts on this, cwickert gnokii tuanta giannisk ? 15:04:27 couldnt follow what it is about 15:04:36 gnokii: mentoring process 15:04:47 tatica: badges for which steps exactly? 15:04:50 ^^ 15:05:05 here's what mizmo had drawn previously https://pagure.io/fedora-hubs/issue/17#comment-2500 15:05:39 * mailga is in his vacation period..... 15:05:59 cwickert, it'd be flexible depending on each teams needs, but we can create badges based on an individual teams needs. 15:06:13 mizmo, thx :) 15:06:22 eg for design team we might require they create a badge design and fill a design ticket, create a wiki profile, submit their portfolio, create a fas acct, etc 15:06:29 so we'd set up a 'join the design team mission' 15:06:33 with badges for each of those tasks 15:06:40 some can be automated - you create a fas acct, you get that badge 15:06:51 tatica, mizmo: so the idea is to create a flow of steps for the mentors and create badges for each step completed? 15:06:57 cwickert, for ambasadors we could use the classroom badges, so they interact with ther region or city 15:06:58 some should be more human eg, your mentor needs to award you the badge 15:07:17 potty, yes 15:07:54 we ask ambassadors to spread fedora, but besides the posts, there are few ways to record the data 15:08:04 their posts are already loged into the planet, and that can be count 15:08:29 technically, a badge for everything can be created 15:08:45 mizmo, tatica: I don't think the mentors will like this idea. The main purpose of the mentoring is to find out if people are really *convinced* of Fedora and are willing to put in efford into the ambassadors. With gamification, I'm afraid they will collect badges like Pokemons. 15:09:17 cwickert, the point of the badges isnt to play a game though, it's to make the steps to get something accomplished clear 15:09:25 cwickert, as I said, it's merely an idea. 15:09:25 cwickert, and to track what's going on better 15:09:34 well to be honest 15:09:51 for the most of the things is a badge already 15:09:58 basically to make it easier to join fedora no matter the team - provide a consistent interface for understanding what you need to do to get started 15:10:09 cwickert: i don't see an issue to apply some gamification to Fedora 15:10:34 i clarify: i know this is no game, but having that kind motivation is good 15:10:48 mizmo: I fully agree we need to track progress better, that's exactly the purpose of the FAMA trac instance. But we don't want to give people false incentives, we want them to apply for ambassadorship because they *want* it 15:11:04 cwickert: it's a way for tracking the whole process, of course mentors have the final word and the *human* components still remain. 15:11:30 cwickert, oh of course. but thats why you need the human component of it. i would imagine for mentorship type roles like ambassadors, the mentor would be awarding many of the badges, so if the mentor feels the mentees heart is not in it, they have discretion not to award 15:11:52 its useless to talk about it anyway because, if I say i dont want a badges account you cant see it 15:12:13 mizmo: so it's just one badge once the mentoring is completed? 15:12:26 gnokii, even if someone didn't have / want a badges account, they could use the list of badges in the mission as a list of work items to work towards 15:12:27 I thought it was a series of badges throughout the mentoring process 15:12:43 cwickert, it can be as granular or as coarse as you guys want. 15:12:43 cwickert, either way you will gain those badges with the process as well 15:12:44 cwickert: no. I understood only one badge for the whole mentoring process. 15:12:50 is just organize the process 15:13:00 gnokii: following your way of thinking there are no way to change anything. IMO. 15:13:01 * tuanta has to leave now 15:13:02 cwickert: but to have the steps on a Hub page 15:13:05 cwickert, from the fedora hubs / badges side we can leave that up to individual teams, but i'd imagine it'd work better with a series of badges 15:13:09 to be an ambassador, you have to have a fas account, you need to update your info, you will have to attend events, etc etc 15:13:19 and give follow-up using automatic tools 15:13:37 * giannisk is back 15:13:37 this will be the ultimate goal https://badges.fedoraproject.org/badge/ambassador 15:13:37 If it is just a single badge, I don't see any benefit over trac 15:13:46 * giannisk is reading through the logs 15:13:47 cwickert, create a fas account, get assigned a mentor, have an initial interview / discussion with mentor, help mentor / some other ambassador hold an event, final approval from mentor <= these could all be separate badges 15:14:14 did you took a look to mizmo design? 15:14:30 tatica: share the link again please 15:14:45 tatica: I'm sorry, I didn't 15:14:50 check please the design team mission section https://pagure.io/fedora-hubs/issue/17#comment-2500 15:14:55 i think it might help if i make a blog post describing the design 15:15:00 By taking a very brief look, i think this is over-engineered 15:15:03 except fromo what I see in that pagure ticket 15:15:05 it's like a step by step guide, instead using words, you're using badges 15:15:09 giannisk++ 15:15:14 mizmo, yeah, I'm already working on it 15:15:37 giannisk, why do you think it's over-engineered? 15:15:45 at the moment we are using trac. Every step is a milestone in a ticket 15:15:53 as I said on the ticket, this requires mockups to make it more readable, it's a abstract idea that needs organization 15:15:57 i think it is a good idea. 15:16:01 if we were to replace milestones with badges, we have to write a whole lot of code 15:16:01 cwickert, trac is getting shut down over the next year 15:16:08 Because the current process works perfectly and this thing with the budges seems over complicated. 15:16:26 giannisk, how is it over complicated? 15:16:32 perfectly so why we discussing then? 15:16:32 trac is going out anyway 15:16:35 giannisk, are you going to be able to use the same process when you migrate to pagure? 15:16:55 mizmo: as long as pagure only has 10% of the features of trac and does not support any kind of ACLs, I don't see trac going away any time soon 15:17:05 giannisk, the thing is a lot of other fedora teams are going to move to this badges model for helping incoming newbies, so it would be nice for ambassadors to follow the same model so across teams we're consistent 15:17:17 may I ask something? 15:17:32 can I please have some more days to finish my mockups? and we can discuss this next week? 15:17:44 but it really helps because it can help make all the little steps obvious and help motivate newbies to keep going 15:17:45 the idea barely came out, I'm not even done with the mockups nor explaining 15:17:49 tatica ^^ ++++ 15:17:51 I don't think we need to delay the idea 15:17:57 erm, discussion 15:18:19 the big win you're going to get is that it's going to be a much nicer interface / easier to understand than trac could ever be 15:18:31 while I appreciate the input from the design team, I don't see any reason for us to not discuss improvements in the mentoring process 15:19:03 mizmo: cleaner interface with less features, as always ;) 15:19:13 cwickert, how would it have less features? 15:19:47 whatever you need can be plugged into it 15:19:54 eg badges can easily be driven by tickets 15:19:59 mizmo: did you look at trac and all it's plugins throughout what groups use on fedorahosted? I just named a killer feauture: ACLs 15:20:12 in design team we have it hooked up with our trac so that if you close a design team ticket it gives you a point, you collect so many and a badge is automatically awarded 15:20:38 ok, but to automatically award badges for the mentoring steps, we have to write a lot of code 15:20:43 so there isn't necessarily a reason you have to stop using trac, the badges could be another layer to make the various aspects you're using in trac more apparent to newcomers 15:20:47 and that's why giannisk called it over-engieered 15:20:55 cwickert, the badges team writes that 15:20:57 not you 15:20:57 cwickert for which one? 15:21:03 fas account exists 15:21:10 making wiki page exists 15:21:22 a lot of these badges exist already 15:21:25 mizmo: you write the code that looks up stuff in fedmsg? 15:21:34 i'm just going to say this and move on - giannisk, fedora hubs and this design has been something my team has been working on for months, it's really not fair to be so dismissive of all of the work of so many people by just calling it over engineered without fully understanding it 15:21:35 moving on 15:21:37 gnokii: mailing list does not 15:21:46 cwickert, yes there's a whole format for the badges to pick up the messages 15:21:55 cwickert: look at the badges trac, its already in work 15:21:55 cwickert, it's not really code iirc it's yaml 15:22:29 * mailga thinks that Ambassadors are not living in a world apart (even if mentors seem yes). An integration with the rest of Project is needed. 15:22:48 I feel that this is like saying a chicken isn't worthy before it has even hatch the egg 15:22:50 mizmo: I am not rejecting your idea, I do see the positive aspects. But I'm afraid it doesn't offer any benefit for the stakeholders, and that's the mentors first of all 15:23:13 mizmo: if mentors have to use another system in addition to trac to grant badges, it's more work for them 15:23:22 cwickert, i think it offers a lot of benefits for the mentors. let me explain how we anticipate it providing benefits to the folks on the design team who serve as (informal) mentors - 15:24:09 cwickert, it will help make the mentees better able to help themselves / self-service their path to becoming a member, because once a badge is earned, the system will suggest the next badge to them in the series so they know what they need to work on next 15:24:47 mizmo: at the moment we have a step by step wizard for this in the wiki 15:25:00 cwickert, it also creates a natural check in point with the mentor - we don't always like automated badge awarding either, because we like the designer to go through a critique with their mentor and have some back and forth. having the mentor award the badge when that is over with sort of helps as the impetus to set up that check point / critique / meeting 15:25:37 cwickert, a major complaint we get every time we interview new users or try to on board new users (i dont know if you guys find this too) is that the wiki is hard to use, it's hard to find information on it, it's hrd to understand how current / active the info is 15:25:43 somebody who is not willing/able to read 5 wiki pages with step-by-step instructions should IHMO not be an ambassador. Sorry if this sounds elitist, but that's the mentor's perception of the ambassadors group. 15:25:59 mizmo: I did not "dismiss" your work, nor did I say that I do not value what your efforts. However, I feel that we (the ambassadors) have other priorities for now. 15:26:07 part of the role of hubs is hopefully to replace the team join function of the wiki because from team to team its inconsistent - there are 'how to join ' pages with steps and pointers set up to teams that haven't existed in fedora for years or that never existed 15:26:17 well 15:26:21 giannisk, flatly stating 'overengineered' without understanding is a dismissal 15:26:32 mizmo: you say that 15:26:44 giannisk, this is not productive, we can take this out of channel if you want 15:26:44 let's not over-discuss this topic 15:27:12 cwickert, we dont want to lower the bar so much that folks who are lazy get in - not at all 15:27:14 mizmo: we have nothing to take out of this channel, i'm not up for a "fight" :) 15:27:24 I just ask time to develop my idea please 15:27:37 cwickert, but we do want a consistent experience across teams for joining, and newbies to have some assurance that the process they're following / the pages they are reading are actually still valid 15:27:51 I thought it was positive to bring the design input to merge it (if possible) with what we have to do (reorganize mentoring process) 15:28:02 potty, yeah 15:28:08 i'm sorry 15:29:11 mizmo: Please try to see it from the other perspective: I think the ambassadors have the best designed join process of all teams in Fedora: there is a step-by-step guide in the wiki, there is a mentoring process, there is FAMA, there are statistics. I'm not saying this is perfect, but I'm afraid the way you talk about it will be considered as dismissal by many mentors, too. 15:29:36 cwickert, absolutely, and we recognized that when we thought about designing this system which is why the ambassadors process inspired it a lot 15:30:30 ok, I think we should separate the process from the design questions 15:30:36 cwickert, what the hope is, is basically to make the process a standard across fedora teams, but not every team has as great documentation as your team and notevery team that has the documetnation keeps it updated 15:30:50 * giannisk believes we are already running late. 15:30:55 yes we are 15:31:13 i would say the #1 complaint from people we talked to who were newbies or gave up trying to become a contributor is that the info they found was out of date or wasn't clear if it was still current (or they thought it was and wasted time) 15:31:22 and thats the main problem relying on wiki for these kinds of processes 15:31:30 You have an idea, you have put effort on it, we appreciate that. Now, what I would like to say is, please come up with a concrete proposal and we would be more than happy to discuss about it. 15:31:39 * tatica just want to keep working in her idea, present it to all mentors and just see where it goes 15:31:40 But I don't think that now is the right time. 15:31:41 great, tatica will be working on that 15:31:49 and i will provide her support 15:32:07 * potty have to leave the meeting in 5 minutes... 15:32:12 giannisk, I said that 30min ago, when I asked for a week to present a formal idea 15:32:31 tatica: I might have missed that line, sorry. 15:32:34 mizmo: how is the wiki a problem? It allows all groups to adjust the process for their needs without having to talk to design, infra or commops first. I think this flexibility is a plus. 15:33:11 cwickert, it's a problem because while you guys keep yours updated id say at least 50% of other teams do not, so for newcomers, they can't trust ANY of the wiki pages 15:33:32 I will go back to my cave and work on my stuff 15:33:35 cwickert, which means more high touch interaction, asking around, trying to figure out if its valid or not - it's a lot of leg work and newbies already have a lot on their plate. a lot just opt out 15:33:40 mizmo: that is a social problem that cannot be addressed with a technical solution 15:33:44 this discussion is about something isn't even a full proposal 15:34:00 cwickert, it's not a social problem. people don't update the wiki because it's not a system that drives people to check up on it regularly 15:34:13 cwickert, its not a 'living' kind of document 15:34:32 mizmo: which again is a social problem, but let's not discuss this further 15:34:42 cwickert, we think that pairing the sign up process with something intended to be checked regularly like hubs wuld help solve it 15:34:43 cwickert: +1 15:34:53 all: let's use https://fedorahosted.org/famsco/ticket/359 for comments about the mentoring process itself, not about the design. tatica, mizmo, and gnokii will work on the badges/hubs approach and we will revisit their proposal once we have something look at. 15:34:56 cwickert, it is technical in that it's deeply mired in user interaction with different types of software 15:35:03 hu 15:35:06 thank you 15:35:25 cwickert, the proposal is already separated, I just linked the ticket in case someone wanted to follow up 15:35:35 I don't see any relation there 15:35:53 tatica: so where is that proposal? 15:36:29 cwickert, just a sec 15:36:45 feel free to post the link to the trac ticket 15:36:48 cwickert, http://imgur.com/a/6HhHH 15:36:49 here 15:36:58 because as I said... Nobody has let me finish it 15:37:17 so please... for the 100 time... let me at least finish my mockups instead arguing for something isn't even done yet 15:37:25 you're all arguing for an idea 15:37:30 this is not even about implementation yet 15:37:35 tatica: right 15:37:44 as a mentor, as an ambassador, as a fedora contributor 15:37:58 please stop arguing and making contributors lose the impulse and willingness to help 15:38:00 please 15:39:10 Alrighty. This needs time. You have it. Let's move on. :) 15:39:29 thank you 15:39:35 This was the latest topic. 15:39:41 Do anyone have extra topics? 15:39:45 #topic Open Floor 15:39:47 tatica: we are not arguing your mock-ups, we are just not sure it makes sense to implement it. for me, this would be the first step before I start working. I appreciate your work, but please don't be disappointed if (some of) the mentors don't like it. It's not that they don't like your work, they don't like the approach 15:40:09 cwickert, I have high tolerance to negatives already 15:40:20 what I have no tolerance is to arguing and not listening 15:40:53 cwickert, just imagine this wasn't me, but a candidate for a team 15:42:15 anyway, will continue working. tick tock, time is running 15:42:37 I will close the meeting in 3 minutes... 15:43:07 tatica: If your comment implies you think it is a personal problem, let me assure you it is not. I appreciate your work. But if I am to think of you as candidate for a team, I would expect this candidate to work with the team and do requirements gathering first. Makes sense? 15:43:26 cwickert, not at all 15:43:26 * mailga says that since the mentorship reorganisation is a FAmSCo task, we cannot ever be careful to hurt people's feelings. 15:43:37 cwickert, but a new contributor might get scared with a thread like this 15:44:41 you're making the assumption we didn't do requirements gathering 15:44:51 we've talked to representatives from all teams from the start including ambassadors 15:45:00 cwickert, and do not worry, at any point I thought this was personal :) 15:45:26 I just think everyone is hurry into something that is merely in my head (and now mizmo since I stalked her for 2 days with this) 15:45:28 mizmo: who did you talk to? 15:45:40 cwickert, im looking up the notes, i know tatica was there 15:45:46 yup 15:45:56 btw i did do a blog post about the idea a while back altho there are some updates - tatica needs to make some of the mockups for the mentor view 15:45:57 http://blog.linuxgrrl.com/2016/04/26/plan-to-level-up-contributors-with-fedora-hubs/ 15:46:04 cwickert, my goal was to first talk to hubs and badges to see if the idea was technically viable 15:46:41 cwickert, this was the initial meeting http://blog.linuxgrrl.com/2015/03/25/summary-of-enabling-new-contributors-brainstorm-session/ 15:46:56 if the idea was too crazy to develop, I would have drop out 15:47:24 i believe tatica was our ambassadors representative and she was chosen both for that and to represent LATAM 15:47:34 but we've had other discussions and meetings along the way 15:47:38 that one was last year 15:48:35 yeah, I couldn't follow up those meetings due... everyone knows why 15:48:53 I came back home I think in late april 15:48:57 mizmo: there is always the danger that the representative doesn't represent the group. I don't think there was any discussion within the mentors or FAMSCo groups. 15:49:10 anyway, this is no longer important for this meeting 15:49:12 cwickert, there was, and there was an open call for volunteers (linked to from that post) 15:49:17 #endmeeting