20:02:35 #startmeeting Fedora Join 20:02:35 Meeting started Fri Oct 16 20:02:35 2015 UTC. The chair is FranciscoD_. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:02:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:02:45 #chair jflory7 randomuser mailga 20:02:45 Current chairs: FranciscoD_ jflory7 mailga randomuser 20:02:51 #topic rollcall 20:02:53 .hello ankursinha 20:02:54 FranciscoD_: ankursinha 'Ankur Sinha' 20:03:01 .fas mailga 20:03:02 mailga: mailga 'Gabriele Trombini' 20:03:03 Hi, I'm here but kinda preoccupied at the moment 20:03:24 no worries randomuser :) 20:03:39 .hello jflory7 20:03:40 jflory7: jflory7 'Justin W. Flory' 20:03:57 hello jflory7 glad to see you here. 20:04:19 Glad to be here! 20:04:30 I don't think we're expecting any one else, but lets wait for a minute, just in case :) 20:04:39 hello FranciscoD_ (but we meet almost everyday).. 20:04:43 :D 20:05:34 Ok, lets begin with just a summary of what happened at flock 20:05:39 #topic flock summary 20:05:41 mailga: all yours :) 20:06:14 jflory7: at Flock you were seated near decause? 20:06:34 For the Join meeting, I was closer to the back, but on decause's side. 20:07:31 I haven't followed discussion between Pete and decause, do you remember anything? 20:08:22 we can always ask decause_airplane to weigh in later on the ML. He's travelling iirc. He sent out an e-mail about it 20:08:43 * FranciscoD_ expects commops will be involved in lots of join things too 20:08:59 * mailga nods 20:09:57 I think so too. I don't remember anything immediately from that conversation. 20:10:27 Ok, let's start with the recap, randomuser can join us later 20:10:32 sure thing 20:10:34 Sounds good. 20:11:39 Well, when I started the talk I thought I was able to follow the slides 20:12:07 the same FranciscoD_ checked before. 20:12:12 ++ 20:12:50 okay, I'm here, had a phone call 20:13:00 but, jflory7 can confirm that, soon the discussion started, before with Sirko then with decause 20:13:24 Pete followed discussion with decause and me the one with Sirko. 20:14:01 there was a good conversation but the presentation was irreperably disrupted :( 20:14:13 Well the first point was the merge between the join process of the groups... 20:14:35 mailga: randomuser: use the meetbot commands liberally so that the logs are nice and informative :) 20:14:41 randomuser: so true! I don't remember if I ended the slides. 20:14:57 FranciscoD_: ok. 20:15:26 So the first question is: do we start a project for the merge of the join processes? 20:15:38 in summary, we kinda decided to go forward with figuring out what we can do, and doing it 20:15:51 ok, so ideas then 20:16:04 #idea merge join processes of different Fedora teams 20:16:14 we'll discuss what implementing this would take in the next topic 20:16:24 ok. 20:16:30 what other ideas do we have to streamline the process? 20:16:36 #idea join.fp.o redo 20:16:54 join.fp.o is not newbie friendly :/ 20:17:17 no, of course, but we have whatcanidoforfedora.o 20:17:23 Well, from my perspective, I think the Join initiative is something that should be an interest of everyone in the project, which I think was kind of mentioned in the talk. 20:17:32 jflory7++ 20:17:34 It seems like that interest is a little bit absent in the general Join initiative 20:17:35 mailga++ 20:17:54 jflory7: I think that's also because we go quiet for longish periods of time 20:17:58 not enough traction 20:18:14 Is that because the interest is elsewhere or dispersed among other groups? I think the purpose of the Join initiative is a little bit fuzzy outside of making it easier to onboard new members. 20:18:15 whatcanidoforfedora is awesome 20:18:38 jflory7: that too, we haven't really worked on details - what we're going to do and how we're going to do it 20:18:51 as randomuser said 20:19:06 i'd like to have a task list that we can begin working on, basically 20:19:07 * randomuser thinks Fedora needs a planing / process tool that is not the wiki 20:19:14 +1 20:19:20 randomuser++ 20:19:20 jflory7: Karma for immanetize changed to 17 (for the f22 release cycle): https://badges.fedoraproject.org/tags/cookie/any 20:19:33 FranciscoD_: in one of MO talks, the one he made with robyduck, she mentioned the possibility to rewrite the join page, accordintd to the hubs. 20:19:46 mailga: yea, I read about that somewhere 20:20:02 the thing is, from what I understood, hubs is only for existing contributors 20:20:13 so we should also ask to MO or Robert about that. 20:20:15 so I'm not too clear on how the join page would be integrated into that system 20:20:16 I think it's intended to make things approachable 20:20:55 something like whatcanidoforfedora that takes the user to the hubs, which then walk through newbies will be nice 20:21:03 yes, good point FranciscoD_ 20:21:10 but the hubs mock ups dont' have anything for newbies 20:21:22 (from what I remember and understood) 20:21:55 theyre like a fedora intraweb - to make it easier to follow the happenings of all the teams and so on 20:21:57 Hub it's an integrated syste for fas members 20:22:02 yea 20:22:23 with lots of information coming from fedmsg/datagrepper 20:22:45 but we cannot have the wiki working syde by side with hubs, 20:23:02 I don't know what the plan for the wiki is 20:23:10 mee too. 20:23:13 I'm sure things like packaging guidelines will still stay on the wiki 20:23:38 this group might be more productive coming up with ideas for people, instead of technologies 20:24:25 randomuser: right, so my idea is take ownership of the future join.fp.o page. 20:24:48 I'm a bit slow today - friday night and all that. randomuser - would you have an example for "ideas for people"? 20:25:01 nevar! 20:25:31 but seriously, a little bit of personal interaction seems to help a lot of people get some initial momentum 20:25:37 yea 20:25:50 I was thinking of monthly "come talk to fedora" sessions 20:25:51 My question is how would the join.fp.o page be different than just the whatcanidoforfedora.org page? 20:26:37 ideally, whatcanidoforfedora should be the main landing page, i.e., join.fp.o 20:26:38 so I'm thinking about ways to approach people about contribution, or get approached, and best handle those initial interactions 20:27:10 randomuser: ++ 20:27:22 randomuser: without a merge of join pages this is difficult IMHO. 20:27:34 * randomuser nods 20:27:39 sort of why I thought making an official "join day" type of thing would be a start 20:28:01 FranciscoD_: in which way? 20:28:18 I'm all for better integration, but don't have time for the work so I'm trying to focus on other things; just tell me to be quiet :) 20:28:29 mailga: the join pages require quite a bit of coordination. I wouldn't want to begin working on them until we've decided on whether we're combining differnt teams processess and all that 20:29:32 FranciscoD_: right. The first step. 20:29:55 if we want better join pages, perhaps we could go through team/sig intro content on the wiki, one by one, and improve it for them? 20:30:01 we could start with docs! 20:30:31 randomuser: please explain it to me. 20:31:04 mailga: the "join day" is basically a day each month where we'll get as many contributors as possible to hang out in one place, wherever it is - hangouts or irc or wherever 20:31:26 and then we'll scream about it all over the place and try to get newbies to come in and speak to them 20:31:40 randomuser: ++ to improve join pages 20:31:40 FranciscoD_: how we could spread this event? 20:32:15 mailga: that's where we don't do very well - blogging, fedoramagazine, mailing lists, catch hold of community members that you know 20:32:45 if decause_airplane is working on a university outreach program already, get him to inform the uni about these slots and so on 20:32:46 I think it's important to have something to *do* on such days, even if no new folks show up 20:32:54 ++ 20:33:11 that way if they do show up, it's to a thing happening and not an awkward quiet room vibe 20:33:16 we could walk them through easy fix tasks? 20:33:17 randomuser: that's what I was guessing. 20:33:39 that way we incentivise the community too? 20:33:53 got simple stuff that everyone's too busy to do? 20:34:01 get newbies to do it for you once a month 20:34:06 sort of? 20:34:17 the easyfix part was a point of discussion at Flock. 20:34:31 if you're talking once a month, we could rotate through team features 20:34:38 yea 20:34:40 totally 20:34:52 its like the docs hours you do 20:34:54 or the test days 20:35:00 like around alpha, do QA, talk about what they do, how, what's going in in the release schedule, etc 20:35:01 just more tailored to newbies 20:35:05 ++ 20:35:06 sort of test-days? 20:35:12 #idea integrate with release tasks 20:35:16 #undo 20:35:16 Removing item from minutes: IDEA by FranciscoD_ at 20:35:12 : integrate with release tasks 20:35:24 #idea integrate "jon days" with release tasks 20:35:28 #undo 20:35:28 Removing item from minutes: IDEA by FranciscoD_ at 20:35:24 : integrate "jon days" with release tasks 20:35:32 *facepalm* 20:35:35 #idea integrate "join days" with release tasks 20:35:42 * mailga :-D 20:35:54 do you folks think this is worth working on? 20:36:02 I absolutely do 20:36:20 well, maybe not release tasks per se, at this point, but team tasks 20:36:22 yes it is, but we need to involve people from groups. 20:36:29 randomuser: ++ 20:36:33 I definitely agree with the team task join days. 20:36:36 being selective will allow us to work with them on planning 20:36:42 mailga: well, that's why we hang a carrot 20:36:53 carrot being "get some work done for the team" 20:37:17 ok, +1 20:38:11 * mailga asked to robyduck to join us, let's see 20:38:15 ok, I'll take up this task 20:38:24 #chair robyduck 20:38:24 Current chairs: FranciscoD_ jflory7 mailga randomuser robyduck 20:38:49 hi robyduck a question for you 20:38:58 hey all 20:38:59 if you can reply of course 20:39:34 with fedora-hubs wich kind of join page you have in mind? 20:40:23 oh, nice question, but we don't have a final answer yet 20:40:36 there are some ideas but... 20:40:38 rather, is anything planned for newbies? a newbie facing "view"? 20:41:23 well, hubs is mainly thought for contributors, a sort of Intranet 20:41:29 ++ 20:41:40 so I didnt mess that up then ^_^ 20:41:43 but yes, there will be of course pages for joining too 20:41:53 so no one aoutside fas account? 20:42:35 one of the ideas is to have a sort of landing page where people can get the most important links/apps 20:42:55 similar, bt not for the layout to apps.fpo 20:43:02 ++ 20:43:10 FranciscoD_: no you didn't :) 20:43:20 so is there a possibility that something like whatcanidoforfedora would link to these team join pages on the hubs? You know? 20:43:52 mailga: there will be probably a few pages without fas account, the rest is like facebook 20:44:17 yes I remember MO's mockups. 20:44:18 well, to contribute to almost any team in Fedora, a FAS account is required, right? 20:44:52 so if you click on something contributor tageted, you will be asked if you have an account. You will be able to create your account also diectly from there 20:45:04 so, we could have a first "view" that says "Looking to contribute to Fedora? Quickly set up an FAS account to get started!" and then that could give them access to the hubs, and the pages that walk them through the process 20:45:17 yeh 20:46:27 and you will also be able to have a look at whatcanidoforfedora.org 20:46:42 so just to get a first overview 20:46:56 that's the plan 20:47:18 sounds awesome 20:47:31 I think the new hubs will greatly improve the join process 20:47:38 awesome work too ;) 20:47:44 ++ 20:47:46 * FranciscoD_ is excited 20:47:46 yes hopefully 20:47:57 robyduck: and the wiki? I'll be alive? 20:48:06 robyduck: we'll wait for you folks to put this up and then bother you with modifications :P 20:48:30 s/I'll/it will 20:48:34 but they should mainly improve the comunication between contributors, the project itself and the groups they are contributing to 20:49:16 mailga: yes, sure, the wiki will be cleaned up a bit, but it will live for many other years 20:49:51 but no more handled, right? 20:50:29 can you rephrase? 20:50:54 I meant no more updated, sorry. 20:51:41 the wiki should be updated to a sort of rolling release (I guess that's the plan of mediawiki), dcs will all go to docs.fpo, and other stuff will go to hubs. But there is still much content in the wiki 20:51:58 and yes, userpages theoretically could also go to hubs 20:52:01 * FranciscoD_ thinks there's way too much info on the wiki to phase it out completely so soon 20:52:05 yea 20:52:24 that wuld make sense and would also be nicer 20:52:30 would* 20:52:31 robyduck: but stuff like packaging guidelines and info on updates-testing etc will stay on the wiki, right? 20:52:46 * robyduck nods 20:53:35 FranciscoD_: this is probably one of the best examples where the wiki is really useful 20:53:48 FranciscoD_: this means that the merge of the join pages is a nonsense job. 20:54:12 mailga: well, some stuff can be merged and improved 20:54:24 but *detailed* functioning of the groups may still require the wiki 20:54:27 hubs are the reason why we don't have any join page on the actual websites, just a redirect to the wiki 20:55:01 * robyduck means join.fpo is a redirect to the wiki now 20:55:39 mailga: as randomuser said earlier, we should leave the tech bits for the time being 20:55:44 quite a few changes coming 20:56:03 robyduck: do you think we can also edit the fp.o with a banner for any "join day"? 20:56:05 and until we see how they change things, us merging join pages and all doesn't make too much sense 20:56:23 FranciscoD_: we have also a developer protal now, should go live with F23 20:56:43 FranciscoD_: of course 20:56:50 robyduck: ++ 20:57:07 Ive been keeping an eye on the staging instance :) 20:57:40 ah ok, there is still some discussion of how to make this working best (infra side) 20:57:45 aye 20:57:53 and I'm waiting to see what content goes up on it 20:58:06 if its like fedoramagazine but with articles for contributors, it won't do much for newbies 20:58:23 * robyduck had the staging link somewhere...uff, but doesn't have it handy now 20:58:52 * mailga thinks robyduck needs a beer.... 20:59:02 FranciscoD_: no, it's for developers only. It's very specific 20:59:07 http://developer.fedorainfracloud.org/ 20:59:24 that's it 20:59:55 it will parse fedmag articles, yes 21:00:05 similar to start.fpo 21:00:47 not too helpful for newbies then 21:00:57 right 21:01:09 I think the "join day" idea seems to be the best thing to get started with at the moment 21:01:18 what do you think mailga randomuser jflory7 ? 21:01:28 * mailga nods 21:01:55 I think it's an achievable and productive thing 21:02:24 but before we have to find group users available (just like robyduck, so nice....) 21:02:24 what do you mean with "join day"? Sorry, I never heard about it 21:02:48 like a test day? 21:02:48 robyduck, we proposed doing something like qa's test days, only to educate people about specific groups in fedora 21:02:58 aha 21:03:11 a sort of classroom for newbies 21:03:12 get contributors from a team and interested newbies together 21:03:12 here is what websites does, here is their tools, here are their repos, here is how you annoy robyduck if there are problems 21:03:14 that kind of thing 21:03:20 :D 21:03:26 I also think the join-day is the best place to start. 21:03:35 randomuser: lol 21:03:48 a classroom, but we won't *teach* like a class - we'll have tasks (easyfix types) and they can work on them 21:03:56 do you also show how to get a beer? 21:03:59 :D 21:04:04 that way they join, do something that gives them confidence, and also get to meet some contributors 21:04:13 robyduck, that's part of the self-reward program! 21:04:16 robyduck: that's the first thing we'll show them - how to buy rounds of beer ;) 21:04:20 haha 21:04:39 Curious... not sure if this would be the time to consider it or maybe after doing a test run, but what do we think about targeting the join days to specific groups of people, e.g. a student day? 21:04:45 * robyduck likes this idea, sounds promising 21:05:02 we can do some preliminary planning with $group to get the required info, and if nobody shows up, we can go over that group's wiki content 21:05:11 ++ 21:05:12 jflory7: ++ 21:05:14 Might be a good way to get some university students to step in and start to get a little involved 21:05:31 jflory7: the problem is the same IMO, spreading the news. 21:05:32 thats where decause_airplane 's commops plans of university outreach could merge in 21:05:46 ^ 21:06:00 jflory7, do you get the sense your fellow students would feel engaged in a fedora-style online event, or would we need bookfaces and skypes or whatever you kids use these days? 21:06:38 thats why I would havve a banner on getfedora.o 21:06:51 Hmmm... 21:07:40 and that's the reason randomuser will send a lifetime supply of beer to robyduck 21:08:02 ha, you caught me not paying attention :P 21:08:43 * mailga thinks that randomuser and robyduck on the same sentence is something really dangerous. 21:08:56 It's hard to answer. I think an online event might work well for getting some kind of initial involvement, like I know here at RIT I see a lot of students who only will use IRC if they have to and there's no other choice, but at the same time, I think that in-person events is effective for getting them there and keeping them there. 21:08:57 well, if you want to do a classroom, then on IRC I guess. Not sure if a videoconference is useful here, but bluejeans can handle many users (needs to have a RH employee to use its account) 21:09:33 Not sure if events specifically is something relevant to this discussion, but I like the idea of considering a kind of "Join" event at hackathons / kind of things to get people interested and looking at the different sides of Fedora. 21:10:22 once we have hubs we'll be able to have a nicer UI for IRC (waartaa) 21:11:03 ++ 21:11:24 jflory7: join "booths" and so on at events is a great idea 21:11:57 we sorta do them informally already 21:12:10 but actually having a booth would be better, especially if the event is user facing 21:12:11 decause had his "Badge-athon" at Software Freedom Day @ the Rochester Inst. of Tech, which I think could be (more or less) a Join sort of event. 21:12:21 FranciscoD_: I think all our booths at events are kinda "join-booths" in the end, no? 21:12:41 robyduck ++ 21:12:44 robyduck: well, yea, but they don't actually ever say "I work for QA, come help me! I'll show you how to get started" 21:12:55 they're more like "here's a fedora booth, you can ask us whatever you want" 21:13:17 FranciscoD_: we should brief ambassadors for that. 21:13:57 probably something that'll be better done if we lead by example 21:13:59 as in, do it at an event or two 21:14:19 and then it should catch on if we get contributors that way 21:15:14 * mailga thinks about a "we want you"..... 21:15:21 yep 21:15:22 and so on 21:15:55 sounds very much like "yes we can"...:) 21:16:17 :D 21:16:38 ok, I think we're a bit over our time already 21:16:46 We do have a few ideas that we want to work on 21:17:00 How about I summarise and send a nice mail to the ML, and we'll begin working on details? 21:17:13 Sounds great to me. 21:17:29 great. 21:18:13 nice 21:18:21 should I end meeting for today then? 21:18:25 and ok, I'll give a beer to robyduck for the informations he gave. 21:18:42 \o/ 21:18:53 hahaha 21:19:01 well, flock will be in paris next year hopefully 21:19:10 we'll all get together and drink awesome french wine ;) 21:19:13 or Toulouse 21:19:17 * mailga will ask the payback to FranciscoD_ jflory7 and randomuser asap. 21:19:32 robyduck: as long as its in emea, I'll make it :P 21:19:39 I'll take a holiday if I have to ;) 21:19:50 FranciscoD_: I *will* be in EMEA 21:19:56 Maybe if I'm lucky I end up over there for next Flock... this year's was fantastic! 21:20:23 ++ 21:20:29 right, ending then 21:20:32 #endmeeting