#fedora-meeting-4: BrickHack 2016 - FOSS Contributions and Licensing

Meeting started by jflory7 at 22:00:33 UTC (full logs).

Meeting summary

  1. Pre-talk information (jflory7, 22:02:32)
    1. There is an Etherpad Q&A pad that will be used for questions. (jflory7, 22:02:45)
    2. https://etherpad.gnome.org/p/brickhack-2016-foss-qa (jflory7, 22:02:47)
    3. Remy DeCausemaker (decause) is presenting the talk at BrickHack 2016. (jflory7, 22:03:01)

  2. Getting started (jflory7, 22:08:16)
    1. The four basics of FOSS are: (jflory7, 22:08:25)
    2. 0) Communication (jflory7, 22:08:50)
    3. 1) Infrastructure (jflory7, 22:08:55)
    4. 2) On-boarding (jflory7, 22:08:59)
    5. 3) Licensing (jflory7, 22:09:09)

  3. Communication (jflory7, 22:09:13)
    1. IRC is the most popular communication method for many FOSS projects on the web (jflory7, 22:09:32)
    2. On the Freenode IRC network, you can join any channel for your favorite FOSS project, and you are likely to find the project (jflory7, 22:10:06)
    3. If you join an IRC channel asking for help, stick around and wait for help! IRC is a global community; there are people all over the world (jflory7, 22:10:28)
    4. Be patient when asking for help or trying to get help; people want to help but you need to be there to receive help :) (jflory7, 22:11:16)
    5. OpenHatch: "The Open Source Community's Welcoming Committee" (jflory7, 22:11:36)
    6. See #openhatch on irc.freenode.net (jflory7, 22:12:08)
    7. https://openhatch.org/ (jflory7, 22:12:21)

  4. Introduction (jflory7, 22:15:07)
    1. Remy DeCausemaker is presenting, employee of Red Hat working as the Fedora Community Action Lead. Many years of open source contributing, using Linux, lots of experience working in the area and happy to help. (jflory7, 22:15:54)
    2. "I use open source because it's free as in gratis, which is exciting" (jflory7, 22:16:11)
    3. "It's also free in freedom, or libre, which means anyone can do anything they want after I release it" (jflory7, 22:16:28)
    4. A public mailing list is publicly recorded. Thanks to it, when someone asks a question, it can be answered by linking to a prior conversation. (mikedep333, 22:17:49)
    5. People can also use mailing lists to keep track of activity in a project. They can subscribe to git changes on GitHub or other code forges too. (Or any other Version Control system.) (mikedep333, 22:19:09)
    6. The git commits include commit messages. These are very informative, and are much like inline comments. (mikedep333, 22:19:53)
    7. Docker (containers) is an example of an exciting open source technology where the industry is headed. (mikedep333, 22:20:55)
    8. Nobody wants to dive into a project with no documentation and where people aren't (instantly) answering your questions. Knowing how to dive into an open source project successfully is important. (mikedep333, 22:22:21)
    9. People are providing examples of open source projects that they contribute to. Some are using GitLab rather than GitHub. (mikedep333, 22:23:06)
    10. One nice thing about GitHub is that it lets you create README.md markdown files for documentation in your source tree. (jflory7, 22:24:10)
    11. Another nice thing is that they combine code hosting, mailing lists, and issue tracking. (mikedep333, 22:24:43)
    12. #ReadTheDocs lets you generate documentation for your project. (mikedep333, 22:25:20)
    13. The audience is providing examples of how they host web apps. Some people self-host on their own hardware, others use AWS (which is cheap but not free), one person uses Azure, and yet another uses DigitalOcean. (mikedep333, 22:27:03)
    14. It's time to talk about Cloud! (mikedep333, 22:27:53)
    15. There is IaaS (Infrastructure as a service), SaaS (Software as a Service), and PaaS (Platform as a Service). (mikedep333, 22:28:37)
    16. Many cloud providers like AWS and Azure provide 2 or 3 of them. (mikedep333, 22:29:14)
    17. When using a PaaS, PaaS makes it so you don't have to handle things like configuring and deploying virtual servers, configuring firewalls, etc. It let's you just deploy your code and run it. (mikedep333, 22:30:05)
    18. Red Hat lets you use OpenShift PaaS with 3 "gears" for free. (mikedep333, 22:30:31)

  5. On-boarding (jflory7, 22:31:26)
    1. Industry has a problem... lack of qualified applicants. All the time. (jflory7, 22:31:46)
    2. Federal government needs many, for example. They're underhiring for 2016. Plenty of engineers being hired all the time. Still not enough. (jflory7, 22:32:08)
    3. Many formal and informal channels to gain experience in open source without enrolling full time as a matriculated student (jflory7, 22:32:53)
    4. === Google Summer of Code === (jflory7, 22:34:11)
    5. Internship program for open source-related internships where students can get paid to hack on open source projects over the summer (jflory7, 22:34:31)
    6. Google pays students to work on FOSS projects (jflory7, 22:34:40)
    7. https://summerofcode.withgoogle.com/ (jflory7, 22:34:49)
    8. https://fedoraproject.org/wiki/GSOC_2016 (jflory7, 22:34:57)
    9. === GNOME Outreachy === (jflory7, 22:35:17)
    10. Outreachy is open to underrepresented communities with the purpose of getting them involved with open source. Get paid full time to work on FOSS projects! (jflory7, 22:35:49)
    11. https://gnome.org/outreachy/ (jflory7, 22:35:59)

  6. Licensing (jflory7, 22:39:19)
    1. #I (Remi and mikedep333) am not a lawyer and this does not constitute legal advice. (mikedep333, 22:40:36)
    2. When you write some thing, you hold copyright over it by default. (mikedep333, 22:41:21)
    3. There are multiple rights by default: 1. Modify 2. Distribute. 3 Redistribute. 4. Perform (publicly, for music) (mikedep333, 22:42:09)
    4. For software, there is the Exclusive view on the left, and the Inclusive view on the right. (mikedep333, 22:42:29)
    5. Within the Free and Open Source software community, there is a hacker named Richard Stallman. he is famous within the community. (mikedep333, 22:43:01)
    6. Stallman wrote a printer driver, a time when printers were new. He gave the printer driver to the printer manufacturer, but the manufacturer refused to release their improvements to the driver back to him or the community. (mikedep333, 22:44:11)
    7. This view by the printer manufacturer was an Exclusive view of Copyright. (mikedep333, 22:44:38)
    8. It depends on copyright, just as free and open source software licenses do. (mikedep333, 22:45:08)
    9. Free and open source software licenses are on a spectrum. There is permissive on one side, and copyleft on the other side. (mikedep333, 22:46:33)
    10. Permissive includes the MIT and BSD licenses. (mikedep333, 22:46:48)
    11. Copyleft includes the GPL. (mikedep333, 22:46:56)
    12. MIT and BSD permit people to do whatever they please with the software, including redistributing it under a license that is different, and not open source. (mikedep333, 22:47:31)
    13. Permissive that is. (mikedep333, 22:47:45)
    14. COpyleft is like the golden rule. When redistributing it, it must continue to be free & open source under the same license. (mikedep333, 22:48:21)
    15. There are lists of licenses, such as those by the OSI: http://opensource.org/licenses (mikedep333, 22:49:21)
    16. People write contracts all the time. Like free beer licenses, or contracts that depend on the color of M&M's. People can come up with ridiculous licenses. Why? Because they wrote the software. (mikedep333, 22:50:37)
    17. I (Remi) tends towards the copyleft side. However, I (Remi) has released some things under the Permissive Apache license. (mikedep333, 22:51:19)
    18. It usually depends on what type of open source community or language you are going into. If a project is using one license, you should probably contribute back under the same license. You may want to use the preferred license of a language too. Otherwise, you will turn people off and they won't use your code. (mikedep333, 22:52:39)
    19. Beware of "Over-Differentiation" (mikedep333, 22:53:14)

  7. Questions & Answers (jflory7, 22:54:42)
    1. Many pieces of software are stacks. Many companies take the bottom layers from open source, and try to differentiate at the top. (mikedep333, 22:54:43)
    2. You want to build this thing you think is a good idea, and in a business, you attract people salaries and money (jflory7, 22:55:35)
    3. In open source, you don't have that (jflory7, 22:55:40)
    4. It's all about "scratching the itch" (jflory7, 22:55:48)
    5. In FOSS, if you scratch an "itch" for something that someone has, there's a good chance someone will find you (jflory7, 22:56:07)
    6. After that, it comes down to culture (jflory7, 22:56:12)
    7. Many different reasons people contribute to open source (jflory7, 22:56:21)
    8. To get contributors: Have clear on-boarding paths, have good docs, have good communication (not "RTFM or get out") (jflory7, 22:57:00)
    9. Licensing: Difficult to go from copyleft to permissive, easier the other way around (jflory7, 22:57:44)
    10. Imagine a timeline -- there's different milestones that can factor into when or how the code licensing can be changed (jflory7, 22:58:19)
    11. Often you sign a Contributor Licensing Agreement that defines the terms (jflory7, 22:58:34)
    12. In Fedora, you can use any list of approved licenses, if you don't specify, it defaults to MIT (permissive) license (jflory7, 22:58:58)
    13. Changing a license is a very permanent thing -- you need 100% agreement by all contributors ever to change the license (jflory7, 22:59:22)
    15. There are many layers to this in a legal aspect and technological literacy to the nth degree is important (jflory7, 23:00:54)
    16. Questions about FOSS legal?? Not sure who to ask?? (jflory7, 23:01:45)
    17. https://sfconservancy.org/ (jflory7, 23:02:05)
    18. Email licensing@fsf.org for 1x1 advice or help (jflory7, 23:02:35)
    19. Q: "Fedora looks cool but how can I contribute?" (jflory7, 23:04:01)
    20. http://whatcanidoforfedora.org/ (jflory7, 23:04:05)
    21. Choose your own adventure! The above site is a sorting hat that can help you choose a place to contribute (jflory7, 23:04:44)
    22. Remy works on the Community Operations (CommOps) team and is *super* glad to help anyone get started (jflory7, 23:05:05)
    23. Check out the #fedora-commops IRC channel on Freenode! (jflory7, 23:05:27)
    24. https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/ (jflory7, 23:06:08)

Meeting ended at 23:13:02 UTC (full logs).

Action items

  1. (none)

People present (lines said)

  1. jflory7 (69)
  2. mikedep333 (35)
  3. zodbot (8)
  4. decause (3)

Generated by MeetBot 0.1.4.