-
Notifications
You must be signed in to change notification settings - Fork 15
/
01-legal.html
542 lines (454 loc) · 28.9 KB
/
01-legal.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>CS 4970: 01-legal slide set</title>
<meta name="description" content="A set of slides for UVa's Service Learning Practicum course">
<meta name="author" content="Aaron Bloomfield">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="../slides/reveal.js/css/reveal.css">
<link rel="stylesheet" href="../slides/reveal.js/css/theme/black.css" id="theme">
<link rel="stylesheet" href="../slides/css/slp.css">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="../slides/reveal.js/lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? '../slides/reveal.js/css/print/pdf.css' : '../slides/reveal.js/css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="../slides/reveal.js/lib/js/html5shiv.js"></script>
<![endif]-->
<script type="text/javascript" src="../slides/js/dhtmlwindow.js"></script>
<script type="text/javascript" src="../slides/js/canvas.js"></script>
<link rel="stylesheet" href="../slides/css/dhtmlwindow.css" type="text/css">
<style>
/* This is for the license comparison table, which is the only such table in this slide set */
.reveal table td {
font-size:70%;
}
</style>
</head>
<body>
<div id="dhtmlwindowholder"><span style="display:none"></span></div>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section data-markdown><script type="text/template">
# CS 4970
### Capstone Practicum I
<center><small>[Aaron Bloomfield](http://www.cs.virginia.edu/~asb) / [[email protected]](mailto:[email protected]) / [@bloomfieldaaron](http://twitter.com/bloomfieldaaron)</small></center>
<center><small>Repository: [github.com/aaronbloomfield/slp](http://github.com/aaronbloomfield/slp) / [↑](index.html) / <a href="01-legal.html?print-pdf"><img class="print" width="20" src="images/print-icon.png"></a></small></center>
## Legal Issues
</script></section>
<section data-markdown><script type="text/template">
# Contents
[Introduction](#/intro)
[History](#/history)
[Common "Free" Licenses](#/common)
[Licenses and You](#/you)
[UVa & Student Software](#/uva)
[Customer meetings](#/customers)
</script></section>
<section>
<section data-markdown id="intro"><script type="text/template">
# Introduction
</script></section>
<section data-markdown><script type="text/template">
## Where does copyright come from?
- Article I, Section 8, Clause 8 of the US Constitution, (the "Copyright Clause"), empowers Congress:
> To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.
- "Limited times" can [redefined with lots of lobbying](https://en.wikipedia.org/wiki/Copyright_Term_Extension_Act)
</script></section>
<section data-markdown><script type="text/template">
## If I buy software, it’s mine, right?
- The software publisher grants the use of one or more copies of the software
- But the company still owns the software
- Thus, to use it, you have to agree to the terms, via an End User License Agreement (EULA)
- These terms prevent things like reverse engineering, etc.
- And, lately, to prevent class action lawsuits ([Paypal did this](http://yro.slashdot.org/story/12/10/18/1637216/paypal-slips-no-class-action-clause-into-policy-update) on Oct 18, 2012; many others have since followed)
</script></section>
<section data-markdown><script type="text/template">
## Reverse engineering
- If a piece of hardware is legally obtained, then reverse engineering is lawful
- But not for software, as EULAs generally forbid it
- And federal courts have [found that EULAs override copyright law](http://en.wikipedia.org/wiki/Bowers_v._Baystate_Technologies)
- However, the DMCA allows for reverse engineering of software if and only if:
- You have legally obtained it
- It is specifically to achieve interoperability between computer programs
</script></section>
<section data-markdown><script type="text/template">
## Reverse engineering
- Legally being able to reverse engineering something doesn't prevent you from being sued, though
- Anybody can file a lawsuit for anything
- It just means the suit is not likely to be successful
- If you can pay the legal fees to get that far into the suit
</script></section>
</section>
<section>
<section data-markdown id="history"><script type="text/template">
# History
</script></section>
<section data-markdown><script type="text/template">
## rms: Richard Stallman
<img style="float:right;margin-left:1em" width="350" alt="Richard Stallman - Fête de l'Humanité 2014 - 010" src="https://upload.wikimedia.org/wikipedia/commons/thumb/7/7b/Richard_Stallman_-_F%C3%AAte_de_l%27Humanit%C3%A9_2014_-_010.jpg/256px-Richard_Stallman_-_F%C3%AAte_de_l%27Humanit%C3%A9_2014_-_010.jpg">
- Launched the GNU project in<br>1983 to create a free Unix-like<br>operating system
- Can you name the kernel?
- Pioneered the [GPL (the GNU<br>copyleft)](https://en.wikipedia.org/wiki/GNU_General_Public_License)
- He wrote (or heavily <br>contributed to): emacs, gcc,<br>gdb, etc.
- Image from <a title="By Thesupermat (Own work) [CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons" href="https://commons.wikimedia.org/wiki/File%3ARichard_Stallman_-_F%C3%AAte_de_l'Humanit%C3%A9_2014_-_010.jpg">Wikipedia</a>
</script></section>
<section>
<h2><a href="http://xkcd.com/743/">xkcd # 743</a></h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/infrastructures.png" title="The heartfelt tune it plays is CC licensed, and you can get it from my seed on JoinDiaspora.com whenever that project gets going." alt="Infrastructures">
</section>
<section data-markdown><script type="text/template">
## GNU Project
<img style="float:left;margin-left:1em;background-color:white" width="310" src="http://upload.wikimedia.org/wikipedia/en/2/22/Heckert_GNU_white.svg" alt="gnu project logo" title=""Heckert GNU white". Via Wikipedia - http://en.wikipedia.org/wiki/File:Heckert_GNU_white.svg#mediaviewer/File:Heckert_GNU_white.svg">
- Also called the free software<br>movement
- A free software mass<br>collaboration project started in<br>January 1984
- The tools that make Linux<br>possible are GNU tools
- Image from <a href="http://en.wikipedia.org/wiki/GNU#mediaviewer/File:Heckert_GNU_white.svg">Wikipedia</a>
</script></section>
<section data-markdown><script type="text/template">
## Free Software Foundation
- Created by Stallman on Oct 4, 1985 to support and promote the free software movement
- Employees and volunteers mostly work on legal and structural issues regarding free software
<a href="http://en.wikipedia.org/wiki/Free_Software_Foundation#mediaviewer/File:Free_Software_Foundation_logo_and_wordmark.svg"><img src="http://upload.wikimedia.org/wikipedia/commons/4/4a/Free_Software_Foundation_logo_and_wordmark.svg" alt="fsf logo" style="background-color:white" title=""Free Software Foundation logo and wordmark" by uploaded by User:SvenThis file was made by User:SvenTranslationIf this image contains text, it can be translated easily into your language. If you need help, contact meFlexible licensesIf you want to use this picture with another license than stated below, contact meContact the authorIf you need a really fast answer, mail me. If you need only a fast answer, write me here. - http://www.gnu.org/graphics/fsf-logo.html. Licensed under Public domain via Wikimedia Commons - http://commons.wikimedia.org/wiki/File:Free_Software_Foundation_logo_and_wordmark.svg#mediaviewer/File:Free_Software_Foundation_logo_and_wordmark.svg"></a>
</script></section>
<section data-markdown><script type="text/template">
## "Free software" became a bad term...
- Stallman’s unyielding stance and personality turned some people off to using the GPL
- And the GPL is very restrictive (see later), which also prevented some companies from releasing their code under it
- So that led to...
</script></section>
<section data-markdown><script type="text/template">
## "Open Source"
- Term created in 1998 by a group of leading free software individuals in reaction to Netscape’s January 1998 announcement of a [source code release](http://en.wikipedia.org/wiki/Netscape#Open_sourcing) to Netscape
</script></section>
<section data-markdown><script type="text/template">
## "Open Source"
- There are two broad categories:
- "Free open-source software": all parts of the software are free
- "Commercial open-source software": some parts are open source, but key parts are kept closed; used by companies who want to claim "open source"
</script></section>
<section data-markdown><script type="text/template">
## So what is "free software"?
- It could be anything from the FSF / GNU
- Or anything under a "free" license
- Typically it is called "FOSS" for "free and open source software"
- This can include many licenses, including the GPL
- This term is different than "free open source software" from the previous slide
- Licenses are approved as "open source licenses" by the [Open Source Initiative (OSI)](http://opensource.org/) based on their [Open Source Definition (OSD)](http://opensource.org/osd)
</script></section>
</section>
<section>
<section data-markdown id="common"><script type="text/template">
# Common "Free"<br>Licenses
</script></section>
<section data-markdown><script type="text/template">
## [GNU General Public License](http://en.wikipedia.org/wiki/GNU_General_Public_License)
- Called the ‘copyleft’
- All derivative works ***<font color="red">MUST</font>*** be released under the SAME license – even if it is only a small part that uses the GPL
- This causes it to be very restrictive
- Thus, it is is called a "viral" license
- GNU software: Linux kernel, gcc/g++, emacs, etc.
</script></section>
<section>
<h2><a href="http://xkcd.com/225/">xkcd # 225</a></h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/open_source.png" title="Later we'll dress up like Big Oil thugs and jump Ralph Nader." alt="Open Source">
</section>
<section>
<h2><a href="http://www.valeriovalerio.org/?p=11">Stallman attacked by Ninjas...</a></h2>
<img class="stretch" src="http://www.valeriovalerio.org/images/Stallman_ninja.JPG">
</section>
<section data-markdown><script type="text/template">
## Let's use GPL code but not tell!
- A Linksys (then Cisco) network storage device (product [NAS200](http://en.wikipedia.org/wiki/NAS200)) ran a customized version of Linux
- As did other products that Linksys developed
- And Linux is released under the GPL
- Linksys did not release the code, even when requested, and they were taken to court
- They were ordered to release their source code because of the GPL viral clause
</script></section>
<section data-markdown><script type="text/template">
## Let's use GPL code but not tell!
- The case is [*Free Software Foundation v. Cisco Systems*](http://en.wikipedia.org/wiki/Free_Software_Foundation_v._Cisco_Systems) (2008)
- This was the first (real) court-backed enforcement of the GPL, and set a legal precedent
</script></section>
<section data-markdown><script type="text/template">
## [MIT License](http://en.wikipedia.org/wiki/MIT_License)
- One of the simplest non-restrictive open source licenses
- Three parts:
- Anybody can use the software for free for any use
- The license must be included in the software
- There is no warranty
- Ruby on Rails and CakePHP are released under this license
</script></section>
<section data-markdown><script type="text/template">
## MIT License, part 1
- Copyright (C) <year> <copyright holders>
- Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
</script></section>
<section data-markdown><script type="text/template">
## MIT License, part 2
- The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
</script></section>
<section data-markdown><script type="text/template">
## MIT License, part 3
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
</script></section>
<section data-markdown><script type="text/template">
## [BSD License](http://en.wikipedia.org/wiki/BSD_licenses)
- A set of permissive licenses
- Two variants are GPL-compatible
- Meaning they can be combined with GPL code, but the result must be released under the GPL
- Thus, they are considered "free software licenses" by the FSF and "open source licenses" by the [OSI](http://opensource.org/)
- The 4-clause variant is not (nor is it widely accepted), due to the advertising clause (item 3 shown [here](https://en.wikipedia.org/wiki/BSD_licenses#4-clause_license_.28original_.22BSD_License.22.29))
- This clause (and variant) has fallen out of favor
- Django is released under the BSD license
</script></section>
<section data-markdown><script type="text/template">
## [Lesser GPL](http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License)
- Designed as a compromise between the restrictive GPL and the permissive MIT/BSD licenses
- Differences between LGPL and GPL
- LGPL does not place restrictions on software that *links* with LPGL code
- Thus, you can integrate proprietary software with LGPL code
- Thus, it is primarily used for software libraries, so there is a clear separation between the LGPL code and the proprietary code
- Software using this license: LibreOffice
</script></section>
<section data-markdown><script type="text/template">
## Other licenses
- [Mozilla Public License (MPL)](http://en.wikipedia.org/wiki/Mozilla_Public_License) is a hybrid of the BSD and GPL licenses (Firefox, Thunderbird)
- [Common Development and Distribution License (CDDL)](http://en.wikipedia.org/wiki/Common_Development_and_Distribution_License) is similar to, and based off of, the MPL (bash, NetBeans)
- [Apache License](http://en.wikipedia.org/wiki/Apache_License) requires any *change* in the software to be released in source form (Apache, Android)
- [Microsoft Public License (MS-PL)](http://en.wikipedia.org/wiki/Shared_source#Microsoft_Public_License_.28Ms-PL.29): unrestrictive, and similar to MIT and BSD
- [Microsoft Reciprocal License (MS-RL)](http://en.wikipedia.org/wiki/Shared_source#Microsoft_Reciprocal_License_.28Ms-RL.29): like MS-PL, but you must release changes in source form
</script></section>
<section data-markdown><script type="text/template">
## License comparison 1
| License name | Derived works must remain open? | Can changed derived license? |
|-|-|-|
| [Apache](http://en.wikipedia.org/wiki/Apache_License), v 2.0 | no | yes |
| [CDDL](http://en.wikipedia.org/wiki/Common_Development_and_Distribution_License) | no | yes, if compatible |
| [GPL](http://en.wikipedia.org/wiki/GNU_General_Public_License), v 2.0 | If published | yes, if compatible or owner agrees |
| [Lesser GPL](http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License) | similar to GPL | yes, if compatible |
| [Microsoft: MS‑PL](http://en.wikipedia.org/wiki/Shared_source#Microsoft_Public_License_.28Ms-PL.29) | no | no |
| [Microsoft: MS‑RL](http://en.wikipedia.org/wiki/Shared_source#Microsoft_Reciprocal_License_.28Ms-RL.29) | yes | no |
| [Mozilla (MPL)](http://en.wikipedia.org/wiki/Mozilla_Public_License) | no | no |
| [BSD License](http://en.wikipedia.org/wiki/BSD_licenses) | no | yes |
| [MIT License](http://en.wikipedia.org/wiki/MIT_License) | no | yes |
Table content derived from [this page](http://khason.net/blog/open-source-licenses-comparison-table/) (or [here](http://web.archive.org/web/20140110134826/http://khason.net/blog/open-source-licenses-comparison-table/))
</script></section>
<section>
<h2>License comparison 2 (from <a href="http://www.shafqatahmed.com/2008/10/comparison-of-d.html">here</a>)</h2>
<img class="stretch" src="http://www.shafqatahmed.com/WindowsLiveWriter/OpenSourceLicenseComparison_thumb.png" alt="license comparison table"></a>
</section>
<section data-markdown><script type="text/template">
## [Creative Commons License](http://en.wikipedia.org/wiki/Creative_Commons_license)
- A means by which authors of works can specify the terms under which people can share said works
- Typically (but not always) used for non-software
- There are four condition modules:
- Attribution (BY): requires attribution to original author
- Share alike (SA): derivative works allowed, but under the same license
- Non-commercial (NC): prevents commercial use
- No derivative works (ND): prevents derivative works
</script></section>
<section data-markdown><script type="text/template">
## [Creative Commons License](http://en.wikipedia.org/wiki/Creative_Commons_license)
- A license is specified by the terms:
- "CC BY-SA", which is what Wikipedia and the github SLP, PDR, and DADA repositories are released under
- "CC BY-NC", which is what xkcd is released under
</script></section>
</section>
<section>
<section data-markdown id="you"><script type="text/template">
# Licenses and You
</script></section>
<section data-markdown><script type="text/template">
## What this means for this course
- Ruby on Rails and CakePHP are both released under the MIT license
- Django is released under the BSD license
- But if we include any GPL code, we have to release the *entire* system under the GPL
- We can link to LGPL libraries just fine...
- Because we are developing real software for real customers, we have to pay attention to this
</script></section>
<section data-markdown><script type="text/template">
## But if you want to use GPL code
- Here is one alternative:
- Consider a single sub-system that is based of GPL code
- You can rewrite that sub-system, and release just that sub-system under the GPL (or LGPL)
- Then use the *binary* from that sub-system in your non-GPL system
- This allows you to use a GPL component, but not release your entire system under the GPL
- Your installation instructions will have to detail how to download and install the sub-system
</script></section>
<section data-markdown><script type="text/template">
## If you ever set software free...
- ... it will come back to you if it loves you...
- If you release it under the GPL, you can never "un-do" that decision!
</script></section>
</section>
<section>
<section data-markdown id="uva"><script type="text/template">
# UVa & Student<br>Software
</script></section>
<section data-markdown><script type="text/template">
## Who owns your code?
- If you were paid by the university...
- ... as a graduate student, paid RA, etc...
- ... then the university would own your code
- But since you are not paid by the university, you own your code
- And you can release it, GPL it, sell it, do nothing with it, etc.
</script></section>
<section data-markdown><script type="text/template">
## Who owns your code?
- Since it is a group project, the system is considered to be jointly-owned, and it’s up to the group to hash out any details
- All this is a university policy, and it follows federal copyright law
</script></section>
<section data-markdown><script type="text/template">
## SLP student agreement
- As mentioned earlier, there is an agreement ([pdf](../uva/student-participation-form.pdf), [word](../uva/student-participation-form.docx)) developed in conjunction with UVa's provost’s office and general counsel that does the following:
- The non-profit obtains the right to use your system forever (including the source code), but they can never release it, sell it, or claim that it was written by them
- They could hire a developer to enhance it, but the enhanced version would have the same restrictions (can not be released or sold)
- They can install it on any of their machines
</script></section>
<section data-markdown><script type="text/template">
## SLP student agreement
- Your rights are not restricted in any way
- You are just giving some (limited) rights to the nonprofit
- Basically, your right to charge them for it in the future or to revoke their usage of the system
- It also releases UVa from any responsibility if your software fails
</script></section>
<section data-markdown id="mustisign"><script type="text/template">
## Must you sign it?
- Can I force you to sign it?
- No! Nobody can force you to give up your rights
- Even though what you are giving up is really just the ability to charge this *one* nonprofit for your project in the future
- But if you do not sign it, then you can not work on a project with an external entity (i.e., a nonprofit)
- This means you will have to take the independent project capstone track
- This agreement has gotten approval from the provost's office at UVa
</script></section>
<section data-markdown id="nda"><script type="text/template">
## Non-disclosure agreement
- There is a non-disclosure agreement (NDA) that has also been created for you by UVa ([pdf](../uva/capstone-nda-for-students.pdf), [word](../uva/capstone-nda-for-students.docx))
- The nonprofits will have information that they do not want to have released, and thus will likely ask you to sign the NDA
- This form was created to prevent nonprofits from having you sign a less favorable NDA
- This form ONLY deals with the nonprofit's information and data; you still own the code
- There is no IP transfer, releasing of other rights, etc., in this form
</script></section>
<section data-markdown><script type="text/template">
## Must you sign it?
- Like the capstone agreement, I cannot force you to sign it
- But you can't work on a project for a nonprofit without signing it
- And thus you will likely have take the independent capstone track
</script></section>
<section data-markdown><script type="text/template">
## Warning
- All the nonprofits were told that, if they wanted an NDA signed, then they had to either:
1. Use the one we provide ([pdf](../uva/capstone-nda-for-students.pdf), [word](../uva/capstone-nda-for-students.docx))
2. Get theirs approved by UVa *prior* to any signings
- Under **NO CIRCUMSTANCES** are you to sign any form provided by the nonprofit that is not this NDA until you ***FIRST*** speak to me (and/or the legal powers at UVa)
- I don't expect this to ever happen, by the way...
- The capstone agreement is given to you by me, not by the nonprofit
</script></section>
<section data-markdown><script type="text/template">
## UVa Legal Agreements
- There is a [UVa Legal Forms](../uva/legal.html) page in the repo with 3 forms:
- "Student Participation and Release Form" ([pdf](../uva/student-participation-form.pdf), [word](../uva/student-participation-form.docx)), which is the SLP Student Agreement just mentioned
- I will have you sign this form when projects are assigned
- "Capstone NDA" ([pdf](../uva/capstone-nda-for-students.pdf), [word](../uva/capstone-nda-for-students.docx)), which is the non-disclosure agreement form
- The nonprofits will (likely) have you sign this form
</script></section>
<section data-markdown><script type="text/template">
## UVa Legal Agreements
- The third form is the "Customer Information Agreement" ([pdf](../uva/customer-project-agreement.pdf), [word](../uva/customer-project-agreement.docx)), which is a form that only the nonprofits sign
- It indicates that they are aware of a bunch of disclaimers and their licensing agreements
- Please read these forms through!!!
</script></section>
<section data-markdown><script type="text/template">
## Open Source Agreement
- Some projects may be required to be open source
- Any student working on this will have to agree, via another form, that the software is to be released under a given license upon completion
- The default is the GPL, unless the entire group -- and the instructor! -- come to an agreement for a different license
</script></section>
<section data-markdown><script type="text/template">
## Open Source Agreement
- If you are unsure if you are okay with this, then that's fine!
- Just don't choose that as one of your desired projects
- I will not put anybody on a required open source project that is not comfortable with their code being open sourced
</script></section>
</section>
<section>
<section data-markdown id="customers"><script type="text/template">
# Customer meetings
</script></section>
<section data-markdown><script type="text/template">
## Customer legal rules, part 1
- The following rules are in addition to the NDAs and overall legal agreement (found [here](../uva/legal.html)), which have been discussed previously
- The three rules that follow have been created in conjunction with Rick Schupp, the director of [UVa's office of Risk Management](http://www.virginia.edu/riskmanagement/)
- They are not a judgment of your capabilities as an adult
- Nor is it a judgment of the customer
- It is simply a set of guidelines to keep you safe
- And to address a UVa liability issue
</script></section>
<section data-markdown><script type="text/template">
## Customer legal rules, part 2
- Because you are being 'assigned' to a customer, UVa (and me!) wants to make sure that you are not forced into a uncomfortable situation as a result of this assignment
</script></section>
<section data-markdown><script type="text/template">
## Customer legal rule # 1
- You are NEVER to be in a meeting with a customer just by yourself -- you must be in a group of at least 2 student group members
- Preferably more, if possible
- Likewise, if you go to the customer's site, you MUST have another group member along with you
- No exceptions!
</script></section>
<section data-markdown><script type="text/template">
## Customer legal rule # 2
- You are NEVER to be in a situation where the customer gives you a ride home (or anywhere else)
- If you do not have transportation, then either make them come to you, or don't have the meeting that week
- If you are stranded, hire a cab and I will personally pay you back
- But only do this if you are really stranded; I'm not paying all the groups' transportations costs here...
</script></section>
<section data-markdown><script type="text/template">
## Customer legal rule # 3
- If anything in a meeting feels wrong, or makes you feel uncomfortable, you should leave immediately and let me know ASAP
</script></section>
<section data-markdown><script type="text/template">
## Notification
- The customers will all be made aware of these rules
- If it ever comes up, please let them know that I have insisted on this
- You ***SHOULD*** defer the blame to me -- that's my job
- And I did, in fact, tell you to follow them
- Feel free to chat with me about any of these issues (or any of your customer interactions)
</script></section>
<section data-markdown><script type="text/template">
## A note about travel
- It is between you and the customer whether you travel to him/her, or s/he comes to you
- You can reserve a room in Rice
- However, you are not to travel to a non-Charlottesville
- The UVa office of Risk Management has deemed any address outside of Charlottesville as being "too far" to be safe
- Any non-Charlottesville customers have been made aware of this
</script></section>
<section data-markdown><script type="text/template">
## A note about travel
- Note that "Charlottesville" includes the City of Charlottesville, as well as any location in Albemarle County that lists "Charlottesville" as the town on their address
- Like the other restrictions, this is not a judgement on you (or your driving skills!)
</script></section>
</section>
</div>
</div>
<script src="../slides/reveal.js/lib/js/head.min.js"></script>
<script src="../slides/reveal.js/js/reveal.js"></script>
<script src="../slides/js/settings.js"></script>
</body>
</html>