16:08:23 #startmeeting Fedora CommOps (2018-10-03) 16:08:23 Meeting started Wed Oct 3 16:08:23 2018 UTC. 16:08:23 This meeting is logged and archived in a public location. 16:08:23 The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:08:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:08:23 The meeting name has been set to 'fedora_commops_(2018-10-03)' 16:08:27 #meetingname commops 16:08:27 The meeting name has been set to 'commops' 16:08:29 #nick commops 16:08:33 #topic Agenda 16:08:39 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 16:08:42 #info (1) Roll call / Q&A 16:08:44 #info (2) Announcements 16:08:46 #info (3) Action items from last meeting 16:08:48 #info (4) Tickets 16:08:50 #info (5) Open floor 16:08:52 #topic Roll call / Q&A 16:08:56 #info Name; Timezone; Sub-projects/Interest Areas 16:08:58 #action commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] 16:09:01 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. 16:09:12 .hi 16:09:13 nb: nb 'Nick Bebout' 16:09:14 #info Justin W. Flory; UTC-5; CommOps, D&I, Mindshare, and more 16:09:20 * jwf waves to nb 16:09:26 * jwf will be back in a few minutes! 16:09:51 Sorry I'm late, got confused by the changed date/time 16:10:22 #info John M. Harris, Jr.; UTC-5; CommOps, Games SIG, Millennium Remix 16:10:28 #info Alberto Rodríguez; UTC-5; CommOps and more 16:10:34 .hello 16:10:34 jonatoni: (hello ) -- Alias for "hellomynameis $1". 16:10:56 .hello jonatoni 16:10:57 jonatoni: jonatoni 'Jona Azizaj' 16:11:42 #info jonatoni; UTC+2; CommOps, D&I, Ambassadors etc 16:11:57 Hi o/ 16:12:03 #info Alberto Rodríguez; UTC-5; CommOps and more 16:12:06 hi :) 16:12:16 #chair nb JohnMH bt0 jonatoni 16:12:16 Current chairs: JohnMH bt0 jonatoni jwf nb 16:12:19 * jwf waves 16:12:21 Hi all! 16:12:47 Let's go ahead and get started since we're running a little late. We'll improvise as we go with tickets. 16:12:52 #topic Action items from last meeting 16:12:57 #link https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-09-26-16.08.html 16:12:58 #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 if needed. If no status, we'll try to get a quick update and move forward. 16:13:25 #info === [INCOMPLETE] "jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3" === 16:13:31 #action jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 10 16:13:50 This week and the last was the start of our midterm period, so I haven't had a chance to really work on this 16:13:55 But hoping for another shot this weekend 16:14:08 @bt0dotninja: Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) 16:14:14 @bt0dotninja: Any updates here? 16:14:56 I update the ticket a little list of the current official tags supported by easyfix 16:15:10 And some others than I see in the wild 16:15:33 * jwf nods 16:16:31 #info === [COMPLETE] "bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)" === 16:16:31 #link https://pagure.io/fedora-commops/issue/168#comment-534169 16:16:31 #info Need to follow up on next steps on what to do with the gathered info. 16:16:42 Thanks 16:16:47 Yup! 16:16:58 This week was not a productive Fedora week for me: 16:17:00 #info === [INCOMPLETE] "jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26" === 16:17:00 #info === [INCOMPLETE] "jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30" === 16:17:00 #action jwf Set up Discourse and announce migration from mailing list before Monday, Oct. 8 16:17:12 I totally slipped on the Discourse action items but will make another attempt this week too 16:17:37 #info === [COMPLETE] "bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3" === 16:17:37 #link https://pagure.io/fedora-commops/issue/168#comment-534169 16:17:37 #info Need to follow up on next steps on what to do with the gathered info. 16:17:39 bt0++ 16:17:53 Okay, cool. That's all of the past action items from last time. 16:18:29 Let's jump to tickets. I didn't have time to prep anything, so I will be a minute to see what is highlighted for the meeting 16:18:38 #topic Tickets 16:18:41 #link https://pagure.io/fedora-commops/issues?status=Open&priority=20 16:18:58 #topic Ticket #110: "Fedora Appreciation Week 2018" 16:18:58 #link https://pagure.io/fedora-commops/issue/110 16:18:58 #link https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org 16:20:16 mizmo left a lot of helpful feedback in the Design Team ticket about Nuancier / collecting photos: 16:20:18 #link https://pagure.io/design/issue/619 16:20:44 Yeah 16:20:51 I only had a chance to skim this morning before my commute this morning, but her point on release forms for people included in photos needs consideration 16:21:35 Ideally I'd like to avoid complicating the process if there is any workaround since we are not using the photos for anything more than a blog post (and we probably have not collected consent for every published photo of every event report we've published), but I'm not sure how to proceed 16:21:39 I want to read Mo 16:22:02 * Mo's full comment before I make a decision, but not sure if any of you had a chance to read through it yet 16:22:14 (Oh, and we are one month away from FAW!!!) 16:23:28 I did read it, maybe we can use the photos in the user wiki 16:23:54 @bt0dotninja: Not a bad idea. All of those fall under a Creative Commons license too. 16:24:01 As a short process, basically the license allow us to use it 16:24:14 #idea Using user-uploaded photos on the wiki as an alternate since the Creative Commons license allows this type of use with attribution 16:24:24 And in that photo I don't look fat :) 16:24:29 bt0++ nice idea actually! That would be a really good workaround if we can't use Nuancier. 16:24:31 lolol! 16:24:41 I'll bet you like fine in any photo ;) 16:24:45 s/like/look 16:24:55 well, there *are* exceptions to needing a model release 16:25:08 IIRC it depends on if the person is in a location with an expectation of privacy 16:25:14 and if the person is the main focus of the photo 16:25:34 nb: Yeah… that's what we need to consider, but I don't know if we will be able to figure it out in this meeting. 16:25:48 I wish we had thought of this idea over the summer instead of the month before :D 16:25:58 But perhaps an idea for next time if it doesn't pan out in time for FAW 16:26:20 #info nb: May be some exceptions to needing a model release, e.g. if the person is in a place with expectation of privacy and if the person is main focus of photo 16:26:56 #help Need to more closely consider implications of using Nuancier for our purpose of using photos on CommBlog posts 16:26:56 meetbot.meeting.item.help -- jflory7 called for help in the "Fedora CommOps (2018-10-03)" meeting in #fedora-commops: "Need to more closely consider implications of using Nuancier for our purpose of using photos on CommBlog posts" 16:27:08 Yeah, we can take a look of the contributor stories and find in the wiki to know if has a photo and if is suitable for faw 16:27:10 The general answer is no you don’t need a release when photographing a public location, however, it is always best to error on side of caution and obtain a model release. This may not always be feasible and is appropriate to photograph even without a release in the case of street photography. An individual who is knowingly exposing themselves to the public does not have what is called a “reasonable expectation of privacy”. In 16:27:10 this situation, for their face and body. The no-model-release-situation only covers photographing a public location, not standing in a public location and photographing into someone’s home. There is no reasonable expectation of privacy for individuals walking down the street, but there is for individuals in their own homes – even if they leave their curtains open for the world to see. Not only is it unlawful, it is creepy to 16:27:10 be photographing into private homes. 16:27:26 #link https://scottwyden.com/street-photography-the-dos-and-do-nots/ 16:27:53 #idea If we use the wiki photos as an alternate, we can look at who submitted a contributor story and check if they uploaded any photos we could use for their contributor story 16:28:24 nb: It would be really helpful if you could check out the comment in this ticket and take the feedback there: https://pagure.io/design/issue/619 16:28:34 nb: I need to get back to mizmo but I don't think I can do it today :( 16:28:53 nb: It would be really helpful if you could help move that conversation forward with this info so we can unblock it if we can 16:29:50 Since it's now October, I think we can start thinking of a Fedora Magazine promo for the week before FAW 16:30:21 The Magazine team should be already aware of FAW (it came up on the mailing list), but it was a while ago and I would not be surprised if it was forgotten 16:30:44 We need a writer to help write a "pointer post" for the Fedora Magazine, intended to publish the week of Oct. 29 16:31:17 I'm heavily backlogged on writing already… so I don't think it's a good idea for me to take this one. 16:31:43 Right, another cool photography source is the magazine, if the people do a "how do you Fedora" interview 16:31:44 A pointer post is a quick summary of an event or upcoming $THING, and it references back to a longer CommBlog post for people to read more 16:31:57 @bt0dotninja: Yes, good idea again. Those are also CC BY. 16:32:11 #idea Another photo source: cprofitt's "How do you Fedora?" series on the Fedora Magazine 16:34:27 #help Need help writing a pointer post on the Fedora Magazine to announce FAW during the week of Oct. 29 16:34:27 meetbot.meeting.item.help -- jflory7 called for help in the "Fedora CommOps (2018-10-03)" meeting in #fedora-commops: "Need help writing a pointer post on the Fedora Magazine to announce FAW during the week of Oct. 29" 16:34:47 I don't have any problem with search and put together all the faw related links 16:34:49 I can throw this one out on the mailing list / Discourse 16:35:08 Action me for the article 16:35:19 Awesome. :+1: 16:35:20 #undo 16:35:20 Removing item from minutes: HELP by jwf at 16:34:27 : Need help writing a pointer post on the Fedora Magazine to announce FAW during the week of Oct. 29 16:35:37 @bt0dotninja: When do you want to set a deadline for a draft? 16:35:50 Does next meeting on Oct. 10 work? 16:36:25 Yes 16:36:32 Please 16:37:48 #action bt0 Create a draft of a FAW announcement for the Fedora Magazine to review at next meeting on Wednesday, Oct. 10 16:38:05 @bt0dotninja: Feel free to draft this wherever you prefer. Google Drive, in WordPress, etc. 16:38:14 Only please don't use Etherpad :D 16:38:38 Ok 16:39:09 Cool… so this is all I can think of for now on FAW 16:39:36 * jwf is really just looking at this: https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org 16:40:25 Anyone else have anything they want to bring up for FAW? 16:40:33 Questions, comments, concerns? 16:40:38 Going once… 16:40:48 Going twice… 16:40:57 Not from me 16:40:59 And thrice. 16:41:33 I'm going to skip #178 (Discourse / discussions.fp.o) because there's nothing new to talk about there since I slipped on all my action items this week. :( 16:41:53 * jwf forgot to put these things in my planner 16:42:10 #topic Ticket #168: "Propose a set of Pagure tags than help the onboarding process" 16:42:10 #link https://pagure.io/fedora-commops/issue/168 16:42:10 #info Next Steps: find the correct place for this docs (CommOps docs?? another repo, a brand new docs page?) 16:42:41 bt0++ thanks for checking this one out 16:43:03 It seems like the most valuable thing to document is probably the easyfix tag and how to get featured on the easyfix page 16:43:24 * jwf wishes we had a better interface for the easyfix page, but c'est la vie 16:43:30 Right 16:44:15 For other suggested tags, we can demonstrate the way we are using them in our Pagure repo… I'm never seen anyone else use tags like we do, with the teams: and type: tags 16:44:33 I always wonder if these are helpful to anyone other than me 😅 16:45:11 Off-topic for now, but anyways… let's brainstorm what we can do next and where we can start putting this stuff 16:45:30 I forgot, but last week, we actually agreed to host this all within our fedora-commops set of docs instead of its own repo, if I remember right? 16:45:39 So things would be kept together and not split across 16:46:06 I don't remember :( 16:46:25 But sounds great 16:46:32 I am fairly sure we did, or if we did talk about it, it was out of the meeting. I'll notate it this time :P 16:46:47 #agreed We will host the on-boarding guide / contributor guide resources in pagure.io/fedora-commops docs 16:47:06 Cool 16:47:21 I think the next step is to create a new submenu on our docs for "on-boarding tips and suggestions", or something similar to that. 16:47:33 Then, we can do small, short pages for things like the Pagure tags for example 16:47:47 So we create a new page, submit a PR, close ticket 16:48:01 Plus, it could be a good chance for others to play around with the docs toolchain we are using too. :) 16:48:10 Since it is somewhat undocumented on our end 16:48:42 #link https://pagure.io/fedora-commops/blob/master/f/.pagure/CONTRIBUTING.md 16:49:32 The next steps I suggest are: 16:49:49 (1) Find some other examples of common tags used, perhaps looking at ours or other repos 16:50:41 (2) Write a short page with helpful information about adding useful tags. Could contain three pieces of info: tag name, tag description, color code. Maybe a sentence why it is helpful or what it signals 16:50:56 We could definitely brainstorm together on #1 16:51:18 @bt0dotninja: Since you are the assignee, what do you think? 16:51:23 And anyone else is welcome to input too 16:52:11 Yeah, I can just do a summary of general tags 16:52:37 Cool. Do you have bandwidth to get this done before FAW? 16:52:48 Or do you want to hold it off / open it up for someone else to jump in if they have time? 16:52:55 * hold it off until after FAW 16:53:24 Yes 16:53:39 I can do it before the faw 16:54:14 Okay, sounds like a plan. And don't feel like it has to be perfect on first run. :D The whole point with these docs is so we can update them and change them over time. There is no such thing as "done" with these. They are a living document :) 16:54:18 bt0++ 16:54:45 @bt0dotninja: Do you want to set a deadline for a PR to the docs? 16:54:55 @bt0dotninja: I can make one to add a new section to our navigation 16:55:06 But I will leave the writing to you :) 16:55:07 Give me two weeks 16:55:28 Cool. I'll action it for Oct. 17. 16:55:46 Yes 16:55:55 #action bt0 Complete a first draft of new CommOps docs page on suggested Pagure tags by Wednesday, Oct. 17 16:55:57 .thank bt0 16:55:57 jwf thinks bt0 is awesome and is happy they are helping! (Please don't forget to bt0++ also) 16:56:23 Okey dokey… 16:56:30 I can't think of anything else to discuss on this one 16:56:39 Anyone else want to bring something up before we switch to open floor? 16:56:43 Going once… 16:56:53 Going twice… 16:57:03 And thrice. 16:57:11 #topic Open floor 16:57:20 Anyone have something they want to bring up before we close? 16:57:44 * jwf had one maybe crazy idea to pitch 16:58:36 Go ahead 16:59:22 The idea I had was thinking about the user experience of the Fedora Docs site. I also realized we have a brilliant Design Team that has done a lot of awesome UI/UX work for other projects like with Outreachy. I thought it would be cool if we could facilitate a conversation between Design Team and Docs team on running UI/UX interviews with community members 16:59:37 It would mostly depend if the Docs team finds this useful for their development 16:59:54 But if so, it would be cool to get some sub-project cross-pollination in this way 17:00:15 * jwf has a hard stop for another meeting right now, but should be back in 30 minutes 17:00:36 We're out of time, but since we're in channel, we can continue discussing 17:00:45 I'll close the meeting and check back in another 30 minutes :) 17:01:03 Thanks everyone for coming out today. 17:01:06 #endmeeting