07:28:31 #startmeeting Lightning Talks - Flock 2016 07:28:31 Meeting started Thu Aug 4 07:28:31 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:28:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 07:28:31 The meeting name has been set to 'lightning_talks_-_flock_2016' 07:28:33 #meetingname flock2016 07:28:33 The meeting name has been set to 'flock2016' 07:28:35 #topic Intro 07:28:39 #info First three talks before the meeting started not logged 07:28:41 #topic Loopabull - Adam Miller 07:28:43 #link https://github.com/maxamillion/loopabull 07:28:45 #topic dgplug summer training - Kushal Das 07:28:53 #info dgplug = Durakpur Linux User Group 07:28:59 #undo 07:28:59 Removing item from minutes: INFO by jflory7 at 07:28:53 : dgplug = Durakpur Linux User Group 07:29:13 #info dgplug = Durgapur Linux User Group 07:29:15 #link https://dgplug.org/ 07:29:35 #info Since 2008, summer training for moving students from users to becoming leaders 07:29:45 Two people here in conference that were a part of the program 07:29:53 #info Around 10 people who become full-time contributors 07:30:13 #info Free and online training 07:30:19 Use IRC for communication 07:30:27 Teaching communication skills for open source communities 07:30:43 Lots of students from dgplug are coming to areas of Fedora for contributing, see #fedora-apps 07:32:20 #info Guest lectures: Contributors like pfrields/stickster talked about docs, lawyers about licensing, other Fedora contributors about developing in Fedora 07:32:31 #help We'd love to have some assistance, check out #dgplug on freenode 07:32:46 #topic Trends in Docs - Milan Navratil 07:32:59 #info Milan is a tech writer @ Red Hat for many years 07:34:07 #info Legos: Buying them you get many bricks. They provide guidance/instructions. "Follow these steps, this is what you will achieve." You can alter it on completion and make it different. Lego guide makers would be great technical writers. Instructions from somewhere like IKEA, a little more difficult 07:34:29 #info Traditional documentation focused on features and availability 07:34:40 Man page is difficult to discern which is most important 07:34:56 #info New documentation focuses on what the user is trying to do, what problem is the user trying to solve 07:35:25 #info Show what can be done by focusing on specific user cases 07:35:32 #info === Minimalism === 07:35:39 #info Limiting amount of text you need to read to solve problem 07:35:46 People not looking up docs for the kicks of it 07:35:49 Looking to solve a problem 07:36:04 Trying to think carefully about this by minimalizing amount of text 07:37:00 #topic Getting started in the kernel - Laura Abbott 07:37:28 Gave a kernel talk yesterday and lots of people interested in getting started - awesome! 07:37:33 Won't cover everything, but some pointers 07:37:52 #info kernelnewbies is a great site for getting started and is what the kernel Outreachy group uses for getting started 07:38:04 #link https://kernelnewbies.org 07:38:17 #info Think about what your purpose is when wanting to contribute - what do you want to focus on in the project? 07:38:42 Getting started with writing patches on some drivers is helpful for getting started 07:38:44 But then what??? 07:38:47 Where do you go? 07:39:07 #info Understanding error messages from the kernel is powerful and helps you deduce problems and figure out a problem 07:39:24 #info If you can patch it, try it; if you report it, read the fix for it later on and understand how it was fixed / changed 07:39:54 #info Learn how PCI interfaces work - on laptops, lots of quirks for variety of hardware and PCI is ever-present in PCI 07:40:14 #info Come contribute to the kernel! 07:40:51 #link http://eudyptula-challenge.org/ 07:41:23 #topic Translation pain - Jean-Baptiste Holcroft 07:42:09 #info "Battling" with Marketing for title of non-technical contributor - like to bring more exposure to translating 07:43:06 #info Goal of localization team is update the user experience for a local language 07:47:03 Oops, was distracted for a minute, didn't get to transcribe that one fully 07:47:16 #topic Two-sided platforms and Fedora - Pravin Satpute 07:48:18 #info Thinking of credit card companies: one side is merchants, another side is users 07:48:39 #info Thinking of online merchants, e.g. Amazon: one side is companies selling product, another side is users / customers 07:48:52 #info Many companies that have become successful by using the two-sided approach to targeting different audiences 07:50:02 #info Gaming: As a user, cannot buy games without a console; developers need to write games for platforms 07:50:39 Once the userbase is created, like with credit cards, is very stable and dependable 07:51:02 #info In two-sided platform, becomes difficult for others to join / compete 07:51:07 Taking it into Fedora: 07:51:17 #info Think of Fedora as a platform: one side are developers, another side are users 07:51:27 #info Different Fedora editions now: Workstation, Server, Cloud 07:51:45 #info More developers and communications results in benefits to the other side 07:52:03 Flock is a good opportunity for that 07:52:12 What else can we do to create that two-sided platform? 07:52:21 Has some articles on this idea / thought 07:52:43 #help Consider thinking of this two-sided approach when addressing marketing and other parts of Fedora 07:52:55 #topic Haskell SIG Update - Jens Petersen 07:53:09 First found out about Haskell doing mathematical physics research 07:53:43 #info Haskell is attractive for its mathematical applications and uses; more formal, but helpful for variety of projects / uses 07:53:51 Going to talk about what's good in the Haskell SIG 07:54:12 #info Fedora released 7.8 of Haskell recently (?) 07:54:17 What's coming for F25? 07:54:54 #info Very tight dependency-tracking, avoid updating too many libraries at once 07:56:49 #topic Conclusion 07:56:56 #link https://fedoraproject.org/wiki/Flock/Lightning_Talks_2016 07:56:59 #endmeeting