22:00:33 <jflory7> #startmeeting BrickHack 2016 - FOSS Contributions and Licensing
22:00:33 <zodbot> Meeting started Sat Mar  5 22:00:33 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
22:00:33 <zodbot> The meeting name has been set to 'brickhack_2016_-_foss_contributions_and_licensing'
22:00:38 <jflory7> #meetingname brickhack
22:00:38 <zodbot> The meeting name has been set to 'brickhack'
22:00:41 <jflory7> #chair decause
22:00:41 <zodbot> Current chairs: decause jflory7
22:02:19 <jflory7> #chair mikedep333
22:02:19 <zodbot> Current chairs: decause jflory7 mikedep333
22:02:32 <jflory7> #topic Pre-talk information
22:02:45 <jflory7> #info There is an Etherpad Q&A pad that will be used for questions.
22:02:47 <jflory7> #link https://etherpad.gnome.org/p/brickhack-2016-foss-qa
22:03:01 <jflory7> #info Remy DeCausemaker (decause) is presenting the talk at BrickHack 2016.
22:04:34 <decause> jflory7: http://etherpad.osuosl.org/brickhack-foss-seminar
22:04:38 <decause> ooop, lol
22:04:43 <decause> you already got one
22:08:16 <jflory7> #topic Getting started
22:08:25 <jflory7> #info The four basics of FOSS are:
22:08:30 <jflory7> #info 1) Communication
22:08:37 <jflory7> #undo
22:08:37 <zodbot> Removing item from minutes: INFO by jflory7 at 22:08:30 : 1) Communication
22:08:50 <jflory7> #info 0) Communication
22:08:55 <jflory7> #info 1) Infrastructure
22:08:59 <jflory7> #info 2) On-boarding
22:09:09 <jflory7> #info 3) Licensing
22:09:13 <jflory7> #topic Communication
22:09:32 <jflory7> #info IRC is the most popular communication method for many FOSS projects on the web
22:10:06 <jflory7> #info On the Freenode IRC network, you can join any channel for your favorite FOSS project, and you are likely to find the project
22:10:28 <jflory7> #info 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
22:10:51 <jflory7> #meetingname famna
22:10:51 <zodbot> The meeting name has been set to 'famna'
22:11:16 <jflory7> #info Be patient when asking for help or trying to get help; people want to help but you need to be there to receive help :)
22:11:36 <jflory7> #info OpenHatch: "The Open Source Community's Welcoming Committee"
22:12:08 <jflory7> #info See #openhatch on irc.freenode.net
22:12:21 <jflory7> #link https://openhatch.org/
22:15:07 <jflory7> #topic Introduction
22:15:54 <jflory7> #info 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.
22:16:11 <jflory7> #info "I use open source because it's free as in gratis, which is exciting"
22:16:28 <jflory7> #info "It's also free in freedom, or libre, which means anyone can do anything they want after I release it"
22:17:49 <mikedep333> #info 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.
22:17:59 <jflory7> mikedep333++
22:19:09 <mikedep333> #info 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.)
22:19:53 <mikedep333> #info The git commits include commit messages. These are very informative, and are much like inline comments.
22:20:55 <mikedep333> #info Docker (containers) is an example of an exciting open source technology where the industry is headed.
22:22:21 <mikedep333> #info 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.
22:23:06 <mikedep333> #info People are providing examples of open source projects that they contribute to. Some are using GitLab rather than GitHub.
22:23:57 <mikedep333> # One nice thing about GitHub is that it lets you create README.md markdown files for documentation in your source tree.
22:24:10 <jflory7> #info One nice thing about GitHub is that it lets you create README.md markdown files for documentation in your source tree.
22:24:43 <mikedep333> #info Another nice thing is that they combine code hosting, mailing lists, and issue tracking.
22:25:20 <mikedep333> #info #ReadTheDocs lets you generate documentation for your project.
22:27:03 <mikedep333> #info 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.
22:27:53 <mikedep333> #info It's time to talk about Cloud!
22:28:37 <mikedep333> #info There is IaaS (Infrastructure as a service), SaaS (Software as a Service), and PaaS (Platform as a Service).
22:29:14 <mikedep333> #info Many cloud providers like AWS and Azure provide 2 or 3 of them.
22:30:05 <mikedep333> #info 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.
22:30:31 <mikedep333> #info Red Hat lets you use OpenShift PaaS with 3 "gears" for free.
22:31:26 <jflory7> #topic On-boarding
22:31:46 <jflory7> #info Industry has a problem... lack of qualified applicants. All the time.
22:32:08 <jflory7> #info Federal government needs many, for example. They're underhiring for 2016. Plenty of engineers being hired all the time. Still not enough.
22:32:53 <jflory7> #info Many formal and informal channels to gain experience in open source without enrolling full time as a matriculated student
22:34:11 <jflory7> #info === Google Summer of Code ===
22:34:31 <jflory7> #info Internship program for open source-related internships where students can get paid to hack on open source projects over the summer
22:34:40 <jflory7> #info Google pays students to work on FOSS projects
22:34:49 <jflory7> #link https://summerofcode.withgoogle.com/
22:34:57 <jflory7> #link https://fedoraproject.org/wiki/GSOC_2016
22:35:17 <jflory7> #info === GNOME Outreachy ===
22:35:49 <jflory7> #info 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!
22:35:59 <jflory7> #link https://gnome.org/outreachy/
22:39:19 <jflory7> #topic Licensing
22:40:36 <mikedep333> #info #I (Remi and mikedep333) am not a lawyer and this does not constitute legal advice.
22:41:21 <mikedep333> #info When you write some thing, you hold copyright over it by default.
22:42:09 <mikedep333> #info There are multiple rights by default: 1. Modify 2. Distribute. 3 Redistribute. 4. Perform (publicly, for music)
22:42:29 <mikedep333> #info For software, there is the Exclusive view on the left, and the Inclusive view on the right.
22:43:01 <mikedep333> #info Within the Free and Open Source software community, there is a hacker named Richard Stallman. he is famous within the community.
22:44:11 <mikedep333> #info 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.
22:44:38 <mikedep333> #info This view by the printer manufacturer was an Exclusive view of Copyright.
22:45:08 <mikedep333> #info It depends on copyright, just as free and open source software licenses do.
22:46:33 <mikedep333> #info Free and open source software licenses are on a spectrum. There is permissive on one side, and copyleft on the other side.
22:46:48 <mikedep333> #info Permissive includes the MIT and BSD licenses.
22:46:56 <mikedep333> #info Copyleft includes the GPL.
22:47:31 <mikedep333> #info 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.
22:47:45 <mikedep333> #info Permissive that is.
22:48:21 <mikedep333> #info COpyleft is like the golden rule. When redistributing it, it must continue to be free & open source under the same license.
22:49:21 <mikedep333> #info There are lists of licenses, such as those by the OSI: http://opensource.org/licenses
22:50:37 <mikedep333> #info 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.
22:51:19 <mikedep333> #info I (Remi) tends towards the copyleft side. However, I (Remi) has released some things under the Permissive Apache license.
22:52:39 <mikedep333> #info 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.
22:53:14 <mikedep333> #info Beware of "Over-Differentiation"
22:54:42 <jflory7> #topic Questions & Answers
22:54:43 <mikedep333> #info Many pieces of software are stacks. Many companies take the bottom layers from open source, and try to differentiate at the top.
22:55:35 <jflory7> #info You want to build this thing you think is a good idea, and in a business, you attract people salaries and money
22:55:40 <jflory7> #info In open source, you don't have that
22:55:48 <jflory7> #info It's all about "scratching the itch"
22:56:07 <jflory7> #info In FOSS, if you scratch an "itch" for something that someone has, there's a good chance someone will find you
22:56:12 <jflory7> #info After that, it comes down to culture
22:56:21 <jflory7> #info Many different reasons people contribute to open source
22:57:00 <jflory7> #info To get contributors: Have clear on-boarding paths, have good docs, have good communication (not "RTFM or get out")
22:57:44 <jflory7> #info Licensing: Difficult to go from copyleft to permissive, easier the other way around
22:58:19 <jflory7> #info Imagine a timeline -- there's different milestones that can factor into when or how the code licensing can be changed
22:58:34 <jflory7> #info Often you sign a Contributor Licensing Agreement that defines the terms
22:58:58 <jflory7> #info In Fedora, you can use any list of approved licenses, if you don't specify, it defaults to MIT (permissive) license
22:59:22 <jflory7> #info Changing a license is a very permanent thing -- you need 100% agreement by all contributors ever to change the license
22:59:39 <jflory7> #info NOTE REMY IS NOT A LAWYER AND THIS DOES NOT CONSTITUTE LEGAL ADVICE
23:00:54 <jflory7> #info There are many layers to this in a legal aspect and technological literacy to the nth degree is important
23:01:45 <jflory7> #info Questions about FOSS legal?? Not sure who to ask??
23:02:05 <jflory7> #link https://sfconservancy.org/
23:02:35 <jflory7> #info Email licensing@fsf.org for 1x1 advice or help
23:04:01 <jflory7> #info Q: "Fedora looks cool but how can I contribute?"
23:04:05 <jflory7> #link http://whatcanidoforfedora.org/
23:04:44 <jflory7> #info Choose your own adventure! The above site is a sorting hat that can help you choose a place to contribute
23:05:05 <jflory7> #info Remy works on the Community Operations (CommOps) team and is *super* glad to help anyone get started
23:05:27 <jflory7> #info Check out the #fedora-commops IRC channel on Freenode!
23:06:08 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/
23:13:02 <jflory7> #endmeeting