17:30:57 #startmeeting Fedora CommOps (2017-02-21) 17:30:57 Meeting started Tue Feb 21 17:30:57 2017 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:30:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:30:57 The meeting name has been set to 'fedora_commops_(2017-02-21)' 17:30:58 #meetingname commops 17:30:58 The meeting name has been set to 'commops' 17:31:02 #nick commops 17:31:03 .hello x3mboy 17:31:04 x3mboy: x3mboy 'Eduard Lucena' 17:31:07 #topic Agenda 17:31:11 #link https://fedoraproject.org/wiki/Meeting:CommOps_2017-02-21 17:31:16 #info (1) Roll Call / Q&A 17:31:20 #info (2) Announcements 17:31:25 #info (3) Action items from last meeting 17:31:30 #info (4) Tickets 17:31:40 #info (5) Community Blog 17:31:44 #info (6) Open Floor 17:31:53 #topic Roll Call / Q&A 17:31:53 #info Name; Timezone; Sub-projects/Interest Areas 17:31:59 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 17:32:02 If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask. 17:32:26 #info Dhanesh B. Sabane, UTC+5:30, CommOps, Marketing, Join, ML, Packaging, Python and more to come. :P 17:32:31 .hello bt0dotninja 17:32:32 bt0: bt0dotninja 'Alberto Rodriguez Sanchez' 17:32:33 #info Justin W. Flory; UTC+1; CommOps, Marketing, Magazine, Ambassadors, Diversity, sysadmin-badges, etc. 17:32:38 * jwf waves to all 17:32:42 #chair dhanesh95 bt0 x3mboy 17:32:42 Current chairs: bt0 dhanesh95 jwf x3mboy 17:32:49 * dhanesh95 waves back 17:33:00 * dhanesh95 is reading the Marketing meeting minutes 17:33:13 #info Alberto Rodriguez;UTC-6;Commops, Dotnet, Infra 17:34:33 dhanesh95: We didn't have time to look at many other tickets, but what we did cover was quality discussion. :) 17:34:46 We'll wait a few more minutes to see if any other folks arrive. 17:35:33 jwf: Yes.. I can see that from the logs. And I missed it. :( 17:35:59 dhanesh95: No worries, it happens. There will be some upcoming traffic on the mailing list where you can provide some input too, so keep an eye out there. :) 17:36:21 jwf: Roger that! 17:36:32 Alrighty, we can go ahead and get started, and anyone else who arrives can chime in as they get here. We have a pretty packed agenda today, but I think we can do it! 17:36:40 #topic Announcements 17:36:50 #info === "North America and Fedora: Year in Review" === 17:36:51 #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/ 17:36:56 #info A quick overview of the past year's events in North America by the Ambassadors. A good overview of the activities and what all is going on in the North American continent with Fedora! 17:37:01 #info === "[release] pagure: 2.13" === 17:37:07 #link https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/4KHO6XZCMU6NUB4OC5T6GDGHHKV6D72F/ 17:37:14 #info A new version of Pagure was released and pushed to the staging instance. It will likely make it ways over to production in the next few days. 17:37:20 #info === Marketing team: "Create Fedora 26 talking points" === 17:37:28 #link https://pagure.io/fedora-marketing/issue/245#comment-193454 17:37:34 #info Ongoing discussion in the Marketing Team to choose and narrow down target audiences for talking points. Knowing target audiences of Fedora 26 is also of interest to us too – feel free to follow along in the ticket! 17:37:46 17:37:52 That's all I have - anyone else want to add anything? 17:38:20 .hello bex 17:38:21 bexelbie: bex 'Brian (bex) Exelbierd' 17:38:23 Not for me 17:38:26 * jwf waves 17:38:28 #chair bexelbie 17:38:28 Current chairs: bexelbie bt0 dhanesh95 jwf x3mboy 17:38:52 Announcements, going once… 17:38:59 Nothing here 17:39:02 Going twice… 17:39:07 Thrice… 17:39:12 #topic Action items from last meeting 17:39:19 #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/commops.2017-02-14-17.31.html 17:39:26 #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward. 17:39:34 #info === [COMPLETE] bt0 Add bulletpoint list with a quick summary of each major area to the top of fp.o/wiki/Join page, close ticket #62 when completed === 17:39:38 :D 17:39:39 #link https://pagure.io/fedora-commops/issue/62#comment-193447 17:39:42 bt0++ 17:39:47 bt0++ 17:39:48 #info === [INCOMPLETE] jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts === 17:40:11 * jwf isn't sure if we will catch bexelbie in the meeting for this or not, but will go ahead and action himself anyways in case we don't 17:40:13 #action jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts 17:40:19 #info === [INCOMPLETE] jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed === 17:40:26 #action jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed 17:40:31 #info === [COMPLETE] jwf Add pictures sent from award3535 to post, create featured image, schedule ASAP === 17:40:37 #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/ 17:40:47 Okay, and that's all past action items… 17:40:49 #topic Tickets 17:40:54 #link https://pagure.io/fedora-commops/issues?tags=meeting 17:41:02 #info === Ticket #21: "Ambassadors - Event Report Template" === 17:41:06 #link https://pagure.io/fedora-commops/issue/21 17:41:12 #info This is an older ticket that we wanted to try to revisit this release cycle. To best approach this, it's worth discussing what type of content event reports should tell. What narrative are we looking for? What should Ambassadors focus on in their event reports? Does it differ from region to region? Let's focus on determining the goals and aims of what an Ambassador event report should have. 17:42:00 jwf, re: contrib directory there may be an RH project we can piggy bank on ... I'll look into it 17:42:15 I think this is definitely a timely topic in light of the upcoming changeover into the next fiscal year. It would be good if we could craft something earlier in the FY for Ambassadors to use. :) 17:42:43 bexelbie: Ah, okay, awesome! So maybe we can hash out the goals we want to look for in Ambassador reports, and we can action you for some follow-up later on in the ticket with this info? 17:43:37 These Ambassador reports are about the Ambassadors' activities, right? 17:44:08 dhanesh95: Correct. Ideally, there should be a tie-in to try to get an idea of the impact that an Ambassador or Ambassadors had at a given event. 17:44:12 For me, things I would want to know from an Ambassador event report might be… 17:44:25 So when does an Ambassador submit such a report? As soon as an activity is conducted or monthly? 17:45:06 dhanesh95: It depends on region, but usually it required after an event where Fedora budget was used to bring Ambassador(s) there. For North America, they're required within two weeks of the event conclusion to be reimbursed. 17:45:09 Not sure about other regions. 17:45:23 I suggest we keep the conversation focused on what as commops we'd like to get from Ambassadors and let the ambassadors group drive if they want to have our help in getting it to us 17:45:28 (1) What was the audience of the event? So we could make sure we know the type of people at the event and try to bring community members who are best able to reach out to that audience 17:46:09 bexelbie: Well, from my perspective, it would be trying to make a connection of event outcomes to long-term project objectives, goals, or the mission to the activity happening at an event. 17:47:19 I agree .. I'm just wondering if we will attract more flies with honey .... something like: We'd like to help you. If you get us X, Y, Z we can do pre-event publicity for you. If you get us P, Q, R, we can do post-event reporting for you. Here are some template ideas 17:47:25 what do you think amby people :) 17:47:45 Okay, I see what you're saying now. 17:48:24 So perhaps it being better for us to develop the criteria for what we want to pull there to guide their thinking when going into writing. 17:48:37 As compared to an exact "template" per say 17:48:59 yes 17:49:15 I like this.. 17:49:19 the one benefit of a template ... or even an interview set of questions if we want to commit to writing .. is that it makes it easier for ambassadors who aren't used to writing 17:49:45 sounds good 17:49:53 #idea Reaching out to Ambassadors / posting guidelines for event reports that encourage something like, "We'd like to help you, if you get us X,Y,Z, we can pre-event publicity; if you get us A,B,C, we can help with post-event reporting; here's some ideas for a post" 17:49:57 bexelbie++ 17:50:06 s/A,B,C/P,Q,R/ :P 17:50:32 :P 17:50:47 bexelbie: That was my original thinking with an explicit template, for Ambassadors who don't write often 17:51:05 More or less just headers they would use for developing their post 17:51:22 Pretty much guidelines like we just proposed, but laid out in a simple, editable format 17:51:34 we could even offer suggestions on what kind of photos work better than others 17:51:39 * jwf nods 17:51:41 like, please no more pictures of pins on tablecloths :) 17:51:49 no pictures of airplane wings 17:51:51 :) 17:51:54 #idea Offering suggestions of what types of photos are better for what kinds of content 17:51:58 * jwf nods 17:52:16 brb 17:52:32 So, I think we should figure out what the $LETTERS_OF_CHOICE are, and then we can see what Brian is able to dig up with the related effort in RH 17:53:03 So, maybe for pre-event reporting… 17:53:31 .hello bee2502 17:53:32 bee2502: bee2502 'Bhagyashree Padalkar' 17:53:56 * bt0 needs to see that photos 17:54:05 #proposed Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event (??????) 17:54:07 #chair bee2502 17:54:07 Current chairs: bee2502 bexelbie bt0 dhanesh95 jwf x3mboy 17:54:09 * jwf waves to bee2502 :) 17:54:14 o/ bee 17:54:15 dhanesh95 beat me to it ;) 17:54:16 bee2502: o/ 17:54:18 :P 17:54:34 jwf bt0 dhanesh95 o/ hello, missing commops badly 17:54:52 jwf: Proposed +1 17:55:02 ! 17:55:08 bee2502: You've been quite busy lately, but we're happy to steal a little bit of your time every once and while. :) 17:55:14 x3mboy: Sure, go ahead. 17:56:02 AFAIK, latam ambassadors are required to create a wiki page about the to request funds, and it's required all the info above mentioned 17:56:28 x3mboy: Would it be flexible if a LATAM Ambassador wrote a CommBlog article instead of a wiki page? 17:56:43 * jwf feels like it's different targets, though 17:57:02 * jwf sees the wiki as more "internal / planning" and the CommBlog as more "external / sharing" 17:57:11 Not sure, I can ask this saturday on meetings 17:57:19 s/meetings/meetings/g 17:57:25 x3mboy: This would be a helpful clarification. Can I action you to follow up on that? 17:57:31 Yeap 17:57:45 back 17:57:46 jwf, RH initiative would be regarding a contributor/speaker bureau not this 17:58:04 x3mboy, if we don't publish it .. possibly even widely in magazine then we aren't getting a multiplier effect from the effort 17:58:14 #action x3mboy Follow up with LATAM Ambassadors about if a CommBlog article suffices for reimbursement, update ticket #21 with feedback 17:58:34 bexelbie: Not sure I follow what you mean? 17:58:43 bexelbie: Also, what do you feel about the above #proposed? 17:58:53 x3mboy / bt0 ^^^ too 17:59:45 jfw, For me is absolutely ok, Wiki pages are little complicated and I think not too much people goes there to check info 18:00:32 x3mboy: Agreed 18:00:32 * bexelbie rereads 18:00:34 For convenience: [18:54:05] #proposed Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event (??????) 18:00:35 * bexelbie has a meeting starting at the same time 18:00:43 +1 from me ^^ 18:00:44 +1 to proposed 18:00:49 +1 18:00:56 +! 18:00:57 +1 18:00:59 *+1 18:01:05 #agreed Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event (??????) 18:01:13 Okay, and another one for post-event reporting… 18:01:29 jwf, x3mboy if we spend peoples time and effort and Fedora resources at an event we should publicize that so that people get excited about going to see us before the event and want to talk to the people we met or suggest equivalent events in other areas for follow up 18:02:06 bexelbie, agreed! 18:02:11 * bexelbie hopes that is clearer 18:02:32 #proposed Post-event reporting goals: Info about how *and* why Fedora participated, forming a conclusion about why Fedora's presence mattered at the event, showing our role in the event with visual aids (?????) 18:02:55 bexelbie: Makes perfect sense to me. :) 18:03:15 +1, sort of, to the above… could maybe use expanding, but can also add to it later 18:03:29 Maybe the critical point with ambassador could be: https://fedoraproject.org/wiki/Event_Wiki_Template#Event_Budget 18:03:49 Oh, let me remove all of the annoying question marks at the end for the previous #agreed… 18:03:52 #undo 18:03:53 Removing item from minutes: AGREED by jwf at 18:01:05 : Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event (??????) 18:04:02 #agreed Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event 18:04:13 I'm agreed about publicize the events, but it will be ok to publicize the budget request? 18:04:17 I'm not sure 18:05:26 This is the template required to ask for funds: https://fedoraproject.org/wiki/Event_Wiki_Template 18:05:41 budget request should be on the wiki event report can be wiki, blogposts or magazine article 18:05:43 x3mboy: I don't see the value in putting a budget request into a CommBlog post. I see value in having a wiki page *and* an event report, but to me, they're two separate things completel. 18:06:15 * bt0 agree with jwf 18:06:47 x3mboy, I suggest we think about Pre-event (post commitment by the ambassador) publicity 18:06:47 then follow up afterward 18:06:48 Were there any 0s / -1s to the above #proposed? 18:06:50 the budget isn't key 18:07:06 we don't advertise that 18:07:11 Mmmm, ok probably this need to be discussed deeply with ambassadors 18:07:22 jwf: +1 18:07:33 0 18:07:46 x3mboy: Definitely discuss this with LATAM and let us know the outcome of the discussion in the ticket. 18:07:52 bexelbie, I'm agreed, but maybe, just maybe, there will be complaints about having more work to pre-event. 18:07:55 #proposed Post-event reporting goals: Info about how *and* why Fedora participated, forming a conclusion about why Fedora's presence mattered at the event, showing our role in the event with visual aids (?????) [<== for convenience] 18:08:00 +1 from me 18:08:08 jwf, of course. I will create a meeting ticket to discuss this 18:08:16 x3mboy++ 18:09:09 x3mboy, I think all of this optional we can't force the Ambassadors to do it .. now hte regions or FAmSCo could decide this important to increase the value of our efforts - but htat is on them 18:09:29 Agreed too 18:09:40 Personally, I hope our Ambassadors would want to get all the publicity they can to increase their value 18:10:07 Maybe it will even better if FAmSCO reach this point, and spread to all regional Ambassadors teams 18:10:35 But for now FAmSCO is a little stuck, so I consider it is ok to reach each team... 18:11:20 Hi guys could someone please tell me what's going on with one sentence? I'm not entirely sure anymore... 18:11:49 I got dropped from connection a few times... 18:12:16 Rhea: We're on ticket #21, with regards to Ambassador Event Reports. https://pagure.io/fedora-commops/issue/21 We were trying to establish some goals for pre- and post-event writing. 18:12:37 Rhea, we are asking if the proposal: Pre-event reporting goals: Critical event information (time, day, location), info about Fedora's location and participation in event, how to engage with Fedora at event 18:12:46 I see thank you x.x 18:13:13 x3mboy: Also, the post-event 18:13:25 #proposed Post-event reporting goals: Info about how *and* why Fedora participated, forming a conclusion about why Fedora's presence mattered at the event, showing our role in the event with visual aids (?????) 18:13:29 Yes, I miss that 18:13:29 x3mboy, I think we should engage via the ambassadors email list and the regions/famsco 18:13:43 once we have a proposal they can edit 18:13:55 If nobody has objections, I'll go ahead and #agreed it, so we can move on to our other tickets, we're about 1/3 of the way through our meeting time. 18:13:59 bexelbie, that sounds good 18:15:01 Afterwards, I will work on drafting a set of guidelines or the copy-text that would be used on the CommBlog for this based on what we agree on. 18:16:20 Okay, going to do said action. :) 18:16:21 #agreed Post-event reporting goals: Info about how *and* why Fedora participated, forming a conclusion about why Fedora's presence mattered at the event, showing our role in the event with visual aids 18:16:23 * dhanesh95 got caught up with some other work. He'll lurk here. 18:16:55 #action jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports 18:17:08 #info === Ticket #43: "EDU Roster" === 18:17:13 #link https://pagure.io/fedora-commops/issue/43 18:17:19 #info We also wanted to follow up on this ticket this release cycle. This one focuses on building an active list or directory of active Fedora contributors who are involved with universities or schools already. Ideally, this people would be "first adopters" of any efforts we aim for with education-related outreach, like in the Marketing team. But where is the best place to keep and maintain this data? 18:17:37 Let me find the link for where this data currently lives. 18:18:11 #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative#Campus_Ambassadors 18:18:40 This page is likely in need of some gardening, but you can get an idea of what is trying to be accomplished there. 18:19:40 * jwf thinks for a bit 18:21:47 Since we don't have any sort of existing contact book-like thing in our infrastructure (and it's harder to justify a need for one), I think a wiki page could still work for this data, but maybe abstracting it out of the University Initiative page into its own page would be helpful. After doing that, the link would need to be properly socialized and cross-linked in places that have high visibility, so it's always somewhere where it will be noticed 18:21:47 and seen by community members. 18:22:18 This could be on general Ambassador wiki pages, an announcement on the Ambassadors list… 18:23:04 * jwf tries to think of other places, but is coming up short 18:23:22 I really think the key issue with this is visibility and communication instead of location, maybe 18:23:53 Maybe a pagure wiki/documentation page with private permission (wondering is such thing exists) 18:24:23 x3mboy: Ahh, could be a good think to maybe mention or link somewhere in regional repo READMEs…? 18:24:32 That definitely is something frequently seen and easy to contribute to 18:25:18 Yeah, I think READMEs for ticketing instances would be helpful, e.g. "Helpful links" 18:26:25 * jwf is just kind of loosely spinning gears, but will try to turn this into ordered steps for how to accomplish 18:26:40 Ok 18:26:48 So, action for this ticket will be??? 18:27:07 I know i was interested in campusambassadors but i've no clue whats even going on at all... I'm currently a little off-guard 18:27:47 Rhea if someone who is interested in being a college ambassador could easily be an ambassador 18:28:17 we really need to rethink that program (make them ambassadors and somehow give them more support) 18:28:27 yup 18:28:44 Rhea: You're not the only one who is unsure either. It used to be more active / engaged in 2009, but even then, the program had difficulties getting started. In summer 2016, there was a lot of discussion happening to try rebuilding the program, but because of personnel change, it lost traction. 18:29:08 We miss decause 18:29:08 For the context of this ticket, we shouldn't use "Campus Ambassadors" because the vocabulary is confusing and means different things to different people. 18:29:09 Why are we driving the college ambassadors program through commops and not amby? 18:29:53 The list we are building now is simply an organized list of people involved or engaged with universities to be used for other initiatives in the project, such as the ongoing discussion in Marketing and possible future work to develop Campus Ambassadors by FAmSCo / Ambassadors. 18:29:58 bexelbie, my same question to your previous person 18:30:03 age 18:30:05 * jwf is still typing the #proposed action idea he had 18:30:41 I would say because someone needs to start it up... 18:30:46 (as to why commops) 18:30:54 And go to famsco with the topic 18:31:08 (and commops is awesome, thats why) 18:31:21 Rhea, then we should try to get it started in ambassadors if it fits there better ... driving it from here makes it look like mission creep that some will react negatively too 18:31:23 even if it isn't 18:31:35 #proposed To close ticket #43, we need to (1) pull out the current Campus Ambassadors section from University Involvement Initiative page and move it to its own dedicated page, (2) insert links to this page on frequented Ambassador wiki pages to encourage people to visit the page and add themselves, (3) post a notice to the Ambassadors mailing list publicizing the page, and (4) possibly encouraging regions to add a link to their READMEs to help 18:31:35 socialize the page 18:31:49 reference the earlier topic - we rephrased it as a partnership .. .not a directive 18:32:39 * bexelbie rereads ticket 43 18:34:24 Re - jwf: we shouldnt use campus ambassadors... 18:34:28 I think this is confusing because of the context of Campus Ambassadors… it's really just a list of contributors, not even exclusively Ambassadors, who are involved and engaged with universities or educational institutions. The purpose of this list isn't only for an Ambassador context because it has useful merit in other parts of the project outside of Ambassadors, so that people working on EDU initiatives or outreach would be able to seek feedbac 18:34:28 k of people who have experience or are in these environments and would be able to offer feedback or their perspective to an issue. I strongly see this as a CommOps activity as it is organizing information in a way that helps improve communication across different parts of the project so people can work on tasks and get feedback from other Fedora contributors who are in these environments, but maybe not in their sub-project. 18:34:29 What do you propose 18:35:26 Rhea: I had an idea about how to move forward on successfully closing the ticket in the above #proposed. Would be curious to know thoughts of other folks on that outline. 18:35:37 -1 18:35:51 Southern_Gentlem: Hmmm, how come? 18:36:05 if you want to call for people who work/have contacts at univeristies fine 18:36:08 jwf 18:36:17 I see. I actually thouhgt that we meant like ambassadors who are actively engaged in university with their "ambassador stuff" 18:36:26 jwf, I think your proposal closes the ticket but doesn't actually get to the goal of moving the EDU initiative forward ... I think we need to think about that. 18:36:30 Southern_Gentlem: Yes, that's the purpose. 18:36:36 we need to totally throw campus Ambassadors under the bus 18:37:01 start from square one and leave the wording Campus ambassador outof it 18:37:06 I would just throw away whatever chaos we have, and start over. 18:37:22 Starting over by going through FAmSCo and making it a thing with ambassadors 18:37:32 Southern_Gentlem: Yeah, for the context of this ticket, I would prefer to avoid any mention of Campus Ambassadors completely because it means different things to different people. 18:37:41 and campus amb. would be actual ambassadors working towards uni+fedora -> events etc... 18:37:46 CA has left a bad taste in the community 18:38:33 i came an Ambassador to help my uni luug 18:38:43 bexelbie: I agree with that, but I don't know if that's in the scope of something we are able to do. I would like to see input from the Council towards getting traction to the Objective again. It's a discussion worth having, but ideally, this ticket is a supportive action to help support getting this objective traction again. 18:38:52 * jwf goes to dig for laptop charger quickly 18:39:14 With the EDU initiative we need to define actionable goals and then work with the teams in Fedora who could make it happen, I think 18:39:21 I am not sure we have done that so far 18:39:53 * jwf nods 18:40:42 I think the scope if the te scope of the ticket is too wide, and should be splitted to be digested 18:40:43 bexelbie, no it has never happened 18:40:50 Rhea: Yeah, Campus Ambassadors is likely something best to be tasked to FAmSCo as it's something really in their domain. 18:41:22 Southern_Gentlem: I also agree that there is definitely a perception to Campus Ambassadors by different people because of the confusion with its origin and really how it fits into the project. 18:42:09 An EDU initiative doesn't necessarily include anything htat functions like anyone would consider a campus ambassadors program 18:42:14 jwf i can see campus Amabassadors as ambassadors who are going to shool, or work at schools 18:42:33 i can see this being a sig with a badge 18:42:46 x3mboy: I think the scope of #43 is valid, but I feel like it would be helpful to have the Council revisit this Objective to see where things left off, set some sort of goals, and then have sub-projects support the Objective. But it feels like a task that is very large even for us, and I feel like it would be best delivered by the Council instead of us. 18:43:06 this ==Campus Ambassadors 18:43:35 Southern_Gentlem: That is also how I see the Campus Ambassadors – mainly focused on either students, faculty, or staff who are actively involved with a university or school 18:44:14 so make it a sig give people a badge, that will create a db of whose out there 18:44:21 For context, this list is just a list to understand who we have in our community and what experience and insight they might be able to offer towards a particular discussion 18:44:47 make it a FAS group and advertise it 18:45:14 The intent for this wasn't to have an organized group or even a SIG, but really just a helpful list to say, "Hey, we want to talk about this topic that is relevant to universities in EMEA, but we don't know who to contact outside of three people who are very active and involved in many areas of the project." 18:45:28 jwf, if we are building a database of expertise should we separate that from the edu intiative? 18:45:38 we could use that in a lot of areas, like "people who can talk to js developers" 18:46:04 We could have a FAS group, but I also see the discussion on the Ambassadors list about closing out country groups, but I think we could justify such a thing 18:46:12 jwf, if your goal isn't to organize something but to have a conversation, then why not start with a general email/conversatoin and not a list building? 18:46:48 bexelbie: Errr, I'm not proposing to separate this from the Objective, but just pulling the existing list out to its own dedicated page, so it has a clear purpose and isn't buried in the middle section of a very long wiki page. 18:46:53 jwf, I think building SIGS and FAS groups before we know why they exist is backwards .. it seems we want to talk about ideas, we should form a group if that is what the action leads too 18:48:00 jwf my idea is that if people are interested in the fas group we have a base group to start having other conversations 18:48:39 The sig/fas would go with what i already expressed, again, i would first discuss this with famsco, if it makes sense move forward with establishing sig/fas/wiki/otherinfo..... notify community about start of the program (specifically notify existing amb.) and get something running 18:48:59 bexelbie: Most of my brainstorming towards this ticket was based around the context of when we originally wrote it up and discussed it a year ago when Remy was driving the Objective. This is part of why I think I might be confused, because I think you and him had a different vision for how to carry out accomplishing the Objective. I'm all for the best solution, but I think there's a disconnect in terms of what the Objective is trying to do and how 18:49:00 we are trying to get there. 18:49:09 It should also be headed by someone who is involved in being ambassador at uni, so the lead has an idea what are they actually trying to aciheve 18:49:10 I think both ideas are not mutually exclusive and the wiki needs love 18:49:28 wiki needs to die, and start over the right way (famsco etc) 18:49:38 jwf, to make sure we are on the same page, Remy and I have not had a conversatoin about this objective at all 18:49:48 he passed along no notes, plans or other such things 18:49:54 I think the question we might need to answer is if we want this roster then, and if we do, how it fits into the Objective. 18:50:10 And I don't think questions about the Objective are best answered by us, but rather the Council. 18:50:15 so I am very ok with resetting this to both determine what we want to do and then we can look at our resources and people to accomplish it with and the relative importance to the project and hte project members 18:51:49 bexelbie: Yes, then it might make more sense for this ticket to be closed in light of more directive on the Objective, but that is definitely something I would rather the Council drive than us, because as to your previous point for other topics, I think it is something that is strange for us to be creating and driving 18:52:22 * jwf notes we also have eight minutes left in the meeting agenda 18:52:52 jwf, I would be happy to help you bring this to council :) 18:53:02 * bt0 "wiki needs to die" made me laugh 18:53:07 I want to find a place to put a cap in this discussion, but I'm a bit confused on where to set an action here. 18:53:33 bexelbie: Okay, I can take responsibility for filing a ticket here with some specific feedback. So long as you are +1 to this approach, I think it makes sense. 18:53:45 So, just to be clear, I want to write a #proposed and make sure we are all on the same page: 18:54:17 my suggest #proposed Close ticket #43 and suggest that those interested in an EDU intiative work together with the council 18:55:08 #proposed To make sure this ticket fits into the overall Objective and working towards accomplishing its goals, this ticket will be closed and a new ticket will be filed in the Council Pagure instance to revisit the University Involvement Initiative, to help set guidelines or create the vision for how this Objective should be carried out and how sub-projects can support moving it forward 18:55:10 +1 18:56:17 I suggest that we have those intersted in the EDU initiative do some self organization and ten approach council 18:56:25 I don't think we should as commops be the ticket filing entity 18:56:28 * Rhea is reading - me is slow 18:56:54 bexelbie: I think I could file the ticket to add some context about some of the things that have made me confused 18:57:18 I didn't mean for that to be the interpretation as CommOps being the ticket-filing entity 18:57:22 jwf, only if you want to be a major part of the restart of trying to have an edu initiative 18:57:51 jwf, I think the #action here should reflect the action of commops 18:58:05 bexelbie: Well, I don't know, I'm a little confused now. Ideally, yes, I want to help, but it would help to know what the vision for this is. 18:59:02 * jwf is also confused because he knew there were some conversations from in-person events that never made it into a publicly facing place, which is why Council insight to creating this vision would be helpful, because I didn't really know everything happening around this even when it was in primary focus 18:59:08 jwf, it is what you make of it :) 18:59:24 so action trumps vision 18:59:28 if you are invested in having an EDU initiative lets start with your vision 18:59:31 everyone else can edit 19:00:33 * jwf is a little lost, but will try to organize thoughts into the ticket for open discussion 19:00:39 Justin lets close this as commops and you and i can discuss it privately 19:00:43 i've got some stuff to add 19:00:51 with private interest of mine 19:01:00 (to move on right now) 19:01:17 +1 to close in commops 19:01:29 -1 to new ticket as starting point - try starting with a ML thread :) 19:01:43 or, *ack* a wiki page :) 19:01:47 advertised via ML 19:01:54 tickets imply the need for action to most folks 19:01:58 we aren't at action yet 19:02:06 Well, I definitely want to get this into a public ticket because a lot of the confusion that I have now is because of private conversations. Right now, I'll just try to get something together 19:02:12 bexelbie: you mean this? https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative 19:02:13 :P 19:02:25 What bex said +1 19:02:32 jwf, it is a start - now clean it up outside of commops and get an ml thread going to drive interest 19:02:36 then go to council/form sig/make magic :) 19:03:13 Justin can we set up 1-1 meeting (or anyone else interested in the topic) for some other time this weekend or in near future? 19:04:05 I think there's probably something I'm not following well in the IRC context, but will just try to get something together. I'm not really sure I am in a place where I will be able to drive anything for this Objective and I don't want to set false expectations for folks on this either. I'll try to get my thoughts down somewhere for now 19:04:25 :) 19:04:36 Yeah just close it as commops and we can have a brief chat baout it later 19:04:42 #proposed To make sure this ticket fits into the overall Objective and working towards accomplishing its goals, this ticket will be closed and there will be additional conversation somewhere, soon, about moving forward with the Objective as a whole 19:05:01 that 19:05:13 Err, meant to make that #agreed 19:05:18 #agreed To make sure this ticket fits into the overall Objective and working towards accomplishing its goals, this ticket will be closed and there will be additional conversation somewhere, soon, about moving forward with the Objective as a whole 19:05:30 #action jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion 19:05:41 #info === Ticket #70: "FOSS Student Pack" === 19:05:46 #link https://pagure.io/fedora-commops/issue/70 19:05:51 #info Another older ticket to circle back to for this release cycle and possibly the next. This could have two different audiences. Do we want a student pack for new contributors to Fedora with resources for getting them started? Do we want to feature cool Fedora apps or general infrastructure a student could use for any open source project? What are the goals of a student pack and what do we want to get out of it? What should the student get out of 19:05:52 it? 19:06:00 #info SKIPPED - ran out of time in meeting, will revisit next week 19:06:05 #topic Community Blog 19:06:12 #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go! 19:06:19 #info === This Week in CommBlog === 19:06:25 #info (1) "North America and Fedora: Year in Review" - award3535++ 19:06:31 #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/ 19:06:37 #info Total Views (Feb. 17 - Feb. 21): 186 19:06:39 ticket 70 may not belong in Commops ... 19:06:43 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3412 19:06:51 #info === Coming Up in CommBlog === 19:07:33 bexelbie: We discussed that specific point last week and saw benefit of having it start here from a community organization perspective. 19:07:40 #info (1) "TAFFY – Tucson Arizona Fedora Fanatic Yeasayers" - schyken 19:07:45 #link https://communityblog.fedoraproject.org/?p=3390&preview=1&_ppp=58c9663ba4 19:07:48 jwf, /me will try to reread :) 19:07:51 #info (2) "Google Summer of Code (GSoC) 2017: Mentors and ideas needed!" - rhea 19:07:55 #link https://communityblog.fedoraproject.org/?p=3454&preview=1&_ppp=98546c028c 19:08:00 #info (3) "University Connect – PCCOE , Pune" - amsharma 19:08:05 #link https://communityblog.fedoraproject.org/?p=3448&preview=1&_ppp=956558f7e1 19:08:10 #info (4) "University Connect - D. Y. Patil College, Pune" 19:08:15 #link https://communityblog.fedoraproject.org/?p=3439&preview=1&_ppp=c0cada9663 19:08:21 #topic Open Floor 19:08:46 bexelbie: I was hoping to have time to cover that specifically in this meeting to really flesh it out more, but we're close to a two hour meeting now :P 19:09:29 yeah 19:09:33 Okay… anyone have any other comments, questions, concerns before we close out? 19:09:48 nop 19:10:01 Thanks for sticking with us here everyone :) 19:10:25 Please re-scheduled ticket #70 for next meeting 19:10:36 mm 19:10:37 I have an action pending about this one 19:11:02 we done? :p 19:11:04 x3mboy: We'll definitely get it into the next meeting. I'm about to close #43 after this, so we'll have a lighter load next week. 19:11:10 Open floor, going once… 19:11:20 Going twice… 19:11:30 Thrice… 19:11:37 Okay, thanks everyone :) 19:11:38 #endmeeting