Lecture 3: Tools, Resources & Rights

Lecture 3: Tools, Resources & Rights Wolfgang Hürst Multimedia group Interaction Technology Division

Contact: [email protected], http://people.cs.uu.nl/huerst

LECTURE 1: INTRO & ORGANISATION

INFOB1PGT teambuilding & website, analysis & design document

LECTURE 2: SW ENGINEERING & TEAMWORK

INFOB1PICA teambuilding & website, project document

development (coding & testing) intermediate report & presentation, revision of plans (if necessary)

Tussenproduct & voorloopige website, tussenpresentatie

development (coding & testing) eindverslag met handleiding, flyer, final report, promotion material (website, video, flyer), CD/DVD‐box, LECTURE 3: eindproduct, eindpresentatie end TOOLS, demonstratie voor jury presentation & demo for jury RESOURCES & demo (+ presentation?) demonstratie (+ presentatie?) op LEGAL ISSUES at the symposium symposium, CD/DVD‐Box

11/19/2014

2

1. Tools (SW Development)

Tools for managing large projects Doing large projects requires lots of planning, organizing, managing, … Various tools exist to assist you with • Managing your product and organizing your data, code, … • Managing your team and organizing your workflow, communication, … We only force you to use SVN for code management, and logbooks & meetings for team management. But you are welcome to look around and use more. 11/19/2014

3


Some pointers to related resources At UU (cf. links on course website): • Blackboard for project management (group rooms, wikis, …) https://ict.science.uu.nl/index.php/Blackboard_%28NL%29

• UniTeams for project space, wikis, etc. https://ict.science.uu.nl/index.php/UniTeams

• Projectspace voor studenten https://ict.science.uu.nl/index.php/Projectruimte And more (see https://ict.science.uu.nl/index.php/Help:Inhoud)

Other (again, cf. links on course website): • Google Code & Google Docs http://code.google.com & http://docs.google.com 11/19/2014

4


Code management – revision control Various tools exist to support the actual implementation & testing. We only force you to use one for revision control. Revision control (or version control) = the management of changes to documents, programs, and other information stored as computer files (from Wikipedia) ICA is very highly encouraged to use SVN (subversion), for GT, the usage of SVN is mandatory! 11/19/2014

5


SVN (subversion) Keeps all code in a repository. Allows you to checkout code to work on it. Enables you to commit and merge code.

11/19/2014

6


SVN (subversion)

Requires an SVN server https://svn.science.uu.nl

And a client, such as http://tortoisesvn.net

Or a plugin, such as http://ankhsvn.open.collab.net 11/19/2014

7


SVN (subversion) To start, you have to create a repository on the server • Login (with SolisID) on https://svn.science.uu.nl

• Select “create a new repository” • Enter name and description, etc. Note for GT: the TA already created your repository! 11/19/2014

8


SVN (subversion) Once created, you can … • Add users (with different rights) • Get links to material (e.g. browse/checkout)

See course site for links to online documentation and further info! 11/19/2014

9


SVN (subversion) Local access (Windows), e.g. using Tortoise SVN http://tortoisesvn.net

Access via Windows Explorer (right mouse button) • First time: select “commit to SVN” and enter data

Terminology: • “update”: from SVN to own machine • “commit”: from own machine to Submit • “add”: enters data to version control without submitting 11/19/2014

10


SVN (subversion) Alternative: use a Visual Studio Plugin, such as AnkhSVN http://ankhsvn.open.collab.net

11/19/2014

11


SVN (subversion) The best tool is only as good as the people using it. Some SVN etiquette: • Only commit code that compiles! You are part of a team. Don’t let others debug your code. • Commit only material that you created yourself E.g. source code, documentation, essential content, … • Commit no material that gets generated E.g. no executable, no PDF, … Why? • SVN keeps everything! • Executable can be too big (storage & server overload) • There’s no need. Everyone can create it themselves. 11/19/2014

12


SVN (subversion) Usage for GT (mandatory): • Your TA already created your repository • Two dates when you have to submit your code Midterm: check by TA Final: grading by TA • Everything else is up to your tutor Usage for ICA (strongly recommended): • TA can help you with setup, etc. • TA also checks code (but not necessarily on SVN) 11/19/2014

13

CODE RELATED DEADLINES

INFOB1PGT

INFOB1PICA ✓

teambuilding & website, analysis & design document

teambuilding & website, project document

development (coding & testing) intermediate report & presentation, revision of plans (if necessary)

SVN CODE (DEADLINE 15.12.)

tussenproduct, tussenpresentatie

development (coding & testing) final report, promotion material (website, video, flyer), CD/DVD‐box, presentation & demo for jury demo (& presentation?) at the symposium

11/19/2014

SVN CODE eindverslag met handleiding, flyer, (DEADLINE 26.1.), einproduct, eindpresentatie end CD/DVD WITH ALL MATERIAL demonstratie voor jury (DEADLINE 28.1.) demonstratie (+ presentatie?) op symposium, CD/DVD‐Box

14

CODE RELATED DEADLINES (ICA)


INFOB1PICA ✓

teambuilding & website, project document

development (coding & testing) intermediate report & presentation, tussenproduct: week 50 revision of plans (if necessary)


development (coding & testing) eindproduct: : vrijdag 23 jan, final report, promotion material uiterlijk 16:00, bij de begeleider (website, video, flyer), CD/DVD‐box, (spreek samen af hoe je inlevert) presentation & demo for jury demo (& presentation?) CD/DVD: vrijdag 30 jan at the symposium tijdens het symposium

11/19/2014

eindverslag met handleiding, flyer, einproduct, eindpresentatie end demonstratie voor jury demonstratie (+ presentatie?) op symposium, CD/DVD‐Box

15

2. Tools (Additional Material)

Overview additional material In addition to creating the code & executable & docs, your final product/game also has to be … • Promoted, e.g. via • • • •

a website a video (only GT) a flyer a nice CD/DVD‐box

• Presented, e.g. to • the jury (rating & nominations) • the public (hands on session at symposium) • the award committee (if you are one of the chosen ones) 11/19/2014

16


Website Rule of thumb: • One page for product / game • One page for team presentation Or more, but be careful (good design takes time) Some general tips: • Find balance between “marketing” & information • Make sure “people get it” (e.g. what is special about your game/product) • Include screenshots (GT can also include video) • Check (and evaluate) pages from last year 11/19/2014

17


Website (& Blog for GT) For GT: Teams create their web page through their UU drive (cf. https://ict.science.uu.nl/index.php/Persoonlijke_website).

There will be a link from the course’s home page to it. Questions? Contact TA. Note: Blogger was used last year (website not completely updated yet) For ICA: Teams should also use their web space. Ask TA or tutor about details. 11/19/2014

18


Website (& Blog for GT) Game tech: • Create a page representing your team and its members Deadline: this Friday, 21.11.13! • Create a page (or more) representing your final game at the end Deadline: 26.1.14!

Informatica: • Voorlopige website Deadline: week 50 • Definitieve website Deadline: vrijdag 24 januari, 16:00 (op de projectspace ‐> studentenassistent)

• Improve the layout (no deadline but be sure to start in time) • Regularly post progress updates and “interesting stuff” Deadlines: 21.11.13, 5.12.13, 19.12.13, 9.1.14, 23.1.14 (additional posts are welcome!) 11/19/2014

GT: Website should include a blog!

19


Website (& Blog for GT) Abbey games (note: this is from their old site, i.e., how they started; see the new one here http://abbeygames.com/blog/ )

11/19/2014

20


Video (only GT) A nice video (“trailer & gameplay combo”) of your game • For advertising, i.e. it should be fun • For information, i.e. it should reflect what you did and what’s special about it; make sure to highlight your extension(s) Some general hints: • Look at last year’s videos for good & bad examples • You also find tutorials and how‐to infos online Note for ICA: videos are becoming more popular as appendix to papers as well (cf. SIGGRAPH, ACM CHI conferences, etc.) 11/19/2014

21


Flyer Should give information about your product/game • Use one side of an A4 paper (it will also be used as sign for the demos) Again, find the right balance • No pure advertisement • No scientific paper Some general hints: • Use website as template (save time as much as possible) • MS Office tools work surprisingly well for this 11/19/2014

22


CD/DVD‐box A “nice” box with • CD/DVD with all material • A nice, appealing cover Some general hints: • This is your final product: make it look nice! • But don’t spend too much time on it (e.g. use website & flyer as basis) 11/19/2014

23


Promotion material – general hints • Save time (and create corporate identity) by using one design for all 3 (or 4) • Check related how‐to links and tips on course website • Check (& critically evaluate) examples from last year • Design for target audience and intended purpose!

11/19/2014

24


Presentations

Note: final changes may apply due to number of teams, etc. Always check the website for final, up‐to‐date information!

To jury (3 tutors & 2 general members): • Rating of your game/product; basis for your grading • Nominations for best game/product award • Make it informative • Make it “enjoyable”/entertaining To public (friends, families, colleagues): • Others play your game / try out your product • Voting for audience award To award committee: • Short demo in lecture hall (5 min) • Entertain & impress ;) 11/19/2014

25


Actual tools to create these Website: • ICA: any HTML editor should do it, GT: use Blogger.com Flyer & box cover: • MS Office tools (works quite well & easy to learn) • Adobe tools (if you have experience with that) • Free software (e.g. Gimp, …) Videos: • Screen capturing software, e.g. Camtasia Studio (30 days trial) • Video editing software, e.g. VirtualDub (free) • Audio processing software, e.g. Audacity (free) • Tools on your Macs & PCs (iMovie, Microsoft Movie Maker) You find some links on the course website. Note: these are also helpful to create content for your product. 11/19/2014

26

3. Legal Issues

Disclaimer The following slides are a slight modification of content prepared and presented by Frans Wiering in 2010/2011. To avoid confusion of legal terms, they are in Dutch and have not been translated to English. Dit is geen juridisch advies!

11/19/2014

27

3. Legal Issues

Most important warning In a previous year one team from the software project got in trouble using an apparently copyrighted image on their website. To avoid any trouble: • Only use legal material that you are allowed to use! • If you are in doubt, don’t use it. • Put a disclaimer on all public material (e.g. your blog/website)! • Think twice before making your game/product downloadable. 11/19/2014

28

3. Legal Issues

Rechten • online materiaal is niet rechtsvrij • belangrijk bij gebruik materiaal in professionele situatie • terrein is sterk in beweging • nieuwe technische ontwikkelingen • pressie vanuit content‐ en software‐industrie • eindgebruikers hechten aan informatievrijheid • diverse rechten van intellectueel eigendom • auteursrecht • naburige rechten • databaserecht • zie ook vak Recht en Informatica • http://www.cs.uu.nl/docs/vakken/ri/ • verschillende artikelen (legale online toegang via UBU) 11/19/2014

29

3. Legal Issues

Auteursrecht • geeft auteur recht van exploitatie • geldt voor werken van ‘letterkunde, wetenschap of kunst’ • daaronder ook computerprogramma’s • wordt automatisch verkregen, geldt wereldwijd • doel: stimuleren van culturele productie • bevorderen van verspreiding kennis en cultuur • middel: geeft auteur economische prikkel tot productie • recht geldt tot 70 jaar na dood auteur Rechten gebruiker • kennisname • kopiëren voor eigen gebruik • citaatrecht en andere vormen van informatievrijheid

11/19/2014

30

3. Legal Issues

Overige rechten • naburige rechten • rechten uitvoerende kunstenaars • 50 jaar na uitvoering • databaserecht • bescherming content databases • 15 jaar na update • octrooi • per land aanvragen, 20 jaar bescherming, kost geld • beschermt uitvindingen van ‘technisch karakter’ • software die ‘technisch effect’ heeft kan ook onder octrooi vallen • Amerika: patentrecht ruim toegepast op software • veel triviale patenten 11/19/2014

31

3. Legal Issues

Rechten op digitaal materiaal • online content valt onder auteursrecht • kennisneming is nauwelijks beperkt • lokale kopie (bv. in cache) is toegestaan • delen is onrechtmatig (dus ook torrent‐protocol) • downloaden van illegale sites is tegenwoordig punt discussie • openbaarmaking is aan regels gebonden • regel rechten goed in professionele producten • je kunt natuurlijk de auteur betalen • veel auteurs vinden verspreiding belangrijker dan exploitatie • stellen werk onder voorwaarden gratis beschikbaar • doen meestal geen afstand van rechten 11/19/2014

32

3. Legal Issues

Creative Commons (CC) biedt auteurs, kunstenaars, wetenschappers, docenten en alle andere creatieve makers de vrijheid om op een flexibele manier met hun auteursrechten om te gaan licentiemodellen voor kosteloos gebruik van digitale content • juridisch goed beschermd • jurisprudentie: Adam Curry vs. Weekend (2006) meer info op 11/19/2014

http://creativecommons.nl/ & http://creativecommons.org/ 33

3. Legal Issues

Creative Commons (CC) 4 licentievoorwaarden mogelijk attribution share alike non‐commercial no derivative work 6 combinaties hiervan http://creativecommons.org/about/licenses/

11/19/2014

34

3. Legal Issues


11/19/2014

35

3. Legal Issues


11/19/2014

36

3. Legal Issues


11/19/2014

37

3. Legal Issues


11/19/2014

38

3. Legal Issues


11/19/2014

39

3. Legal Issues

http://soundcloud.com/creativecommons

Voorbeeld CC SoundCloud A “social sound platform” for creating and sharing sounds (including music) Contains lots of sounds under the Creative Commons licenses

11/19/2014

40

3. Legal Issues

Voorbeeld CC

http://soundcloud.com/ https://soundcloud.com/search/sounds?filter.license=to_use_commercially

3. Legal Issues

Voorbeeld CC

http://soundcloud.com/ https://soundcloud.com/search/sounds?filter.license=to_use_commercially

3. Legal Issues

Open Source • essentie: gratis programmacode • en ook gecompileerde versies • business model: software gratis, services kosten geld • geen afstand van auteursrecht! • belangrijke grote toepassingen • Linux, Mozilla (Firefox, Thunderbird), Open Office • van alles op http://sourceforge.net/ • verschillende licentievormen • regelen zaken als kopiëren, bewerken en toepassing • GNU General Public License • streng, toepassing maakt hele product Open Source • GNU Lesser Public License • staat ook commerciële toepassing toe • en nog vele andere licentievormen • schending voorwaarden is inbreuk op auteursrecht 11/19/2014

43

3. Legal Issues

Wetenschappelijke kennis • literatuur • publicaties vallen onder auteursrecht • vaak overgedragen aan uitgevers • vragen veel geld voor online toegang • veel discussie over juistheid hiervan • open access tijdschriften • pre‐prints op web • citaatrecht • kennis kan vrijelijk worden toegepast • morele verplichting tot citeren • algoritmen • vallen niet onder auteursrecht (beschermt de vorm) • kunnen wel onder octrooi vallen (beschermt het idee) 11/19/2014

44

A related side note

Scientific integrity / eerlijke wetenschap

11/19/2014

45

3. Legal Issues

Welk recht heb je op je eigen werk? • eigen bedrijf • is van jou • vrije tijd • is van jou • vervaardigd in opdracht • recht bij werk‐ of opdrachtgever • overeenkomst vereist • vervaardigd voor opleiding • je eigen inbreng is van jou • i.h.a. ook grote inbreng opleiding • meer info: http://www.surffoundation.nl/Auteursrechten/nl/Pages/Defa ult.aspx 11/19/2014

46

3. Legal Issues

Mag je een retrogame nabouwen? • het oorspronkelijke spel is beschermd • auteursrecht • wellicht octrooirecht • voor onderwijs en eigen gebruik is OK • distribueren is een schending van rechten! • maken van een film, afbeeldingen en documenten over de game is toegestaan • conclusie: neem geen risico’s

11/19/2014

47

3. Legal Issues: (recommendation)

Use a disclaimer Put a disclaimer on your website/blog stating that: • This is an educational project • There is no commercial interest behind it • You are only using copyright free and legal data • Ask people to contact you if you accidentally used inappropriate material There are many examples and samples online. Search for them and make one that is suitable for your site.

11/19/2014

48

3. Legal issues: (recommendation)

Disclaimer example Here’s what I would probably write: “This site and its content are part of an educational project done during a course in the computer science curriculum at Utrecht University. Its sole purpose is educational and there are no commercial interests involved. We carefully checked all material to make sure not to violate any copyrights or other legal rights. If inappropriate content is used accidentally, please inform us and we will be happy to remove it promptly. ”

11/19/2014

49

3. Legal issues: (recommendation)

Disclaimer example You also could consider adding a note about Fair use policy: http://en.wikipedia.org/wiki/Fair_use But note that this only covers United States copyright law.

Further note that you are encouraged to be creative and make your own graphics, sounds, etc.

11/19/2014

50

Disclaimer I’m not a lawyer. This was no legal advice. I take no responsibility for the correctness of the information that I just provided to you.

11/19/2014

51

4. Further Resources

Creative Commons examples • Soundcloud (music, sounds) http://soundcloud.com • Jamendo (music, paid licenses for commercial usage) http://www.jamendo.com • Freesound (sounds, no music) http://www.freesound.org/ • Wikimedia commons (photos, videos) http://commons.wikimedia.org/ • Social media sharing platforms, such as http://flickr.com (photos) Bottom line: there’s lots of stuff out there that you can legally use, but make sure to always check the license information! 11/19/2014

52

LECTURE 1: INTRO & ORGANISATION


LECTURE 2: SW ENGINEERING & TEAMWORK

✓

INFOB1PICA teambuilding & website, project document

development (coding & testing) intermediate report & presentation, LECTURE 5: revision of plans (if necessary) YOU!


development (coding & testing) eindverslag met handleiding, flyer, final report, promotion material einproduct, eindpresentatie end (website, video, flyer), CD/DVD‐box, LECTURE 3: TOOLS, demonstratie voor jury presentation & demo for jury RESOURCES & demo (& presentation?) demonstratie (+ presentatie?) op LEGAL ISSUES symposium, CD/DVD‐Box at the symposium GT LECTURE 4: game company pitches are cancelled  11/19/2014 more time to create your own games 

ICA LECTURE 4: Paul is still looking for guest speakers; check website for infos/updates 53

5. Conclusion

Final comments Any questions? No? Then …

11/19/2014

54

Lecture 3: Tools, Resources & Rights

Recommend Documents