Lecture 3: Tools, Resources & Rights

Lecture 3: Tools, Resources & Rights

Wolfgang Hürst

Mul$media group Interac$on Technology Division

Contact: [email protected], h>p://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 & tes$ng) intermediate report & presenta$on, revision of plans (if necessary)

Tussenproduct & voorloopige website, tussenpresenta$e

development (coding & tes$ng) final report, promo$on material eindverslag met handleiding, flyer, (website, video, flyer), CD/DVD-‐box, LECTURE 3: eindproduct, eindpresenta$e end TOOLS, presenta$on & demo for jury demonstra$e voor jury RESOURCES & demo (+ presenta$on?) demonstra$e (+ presenta$e?) op LEGAL ISSUES at the symposium symposium, CD/DVD-‐Box

20/11/13

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, communica$on, …

We only force you to use SVN for code management, and logbooks & mee9ngs for team management. But you are welcome to look around and use more. 20/11/13

3


Some pointers to related resources At UU (cf. links on course website):

•  Blackboard for project management (group rooms, wikis, …) h>ps://ict.science.uu.nl/index.php/Blackboard_%28NL%29

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

•  Projectspace voor studenten

h>ps://ict.science.uu.nl/index.php/Projectruimte

And more (see h>ps://ict.science.uu.nl/index.php/Help:Inhoud)

Other (again, cf. links on course website): •  Google Code & Google Docs

h>p://code.google.com & h>p://docs.google.com

20/11/13

4


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

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.

20/11/13

6


SVN (subversion)

Requires an SVN server h>ps://svn.science.uu.nl

And a client, such as h>p://tortoisesvn.net

Or a plugin, such as

h>p://ankhsvn.open.collab.net 20/11/13

7


SVN (subversion) To start, you have to create a repository on the server

•  Login (with SolisID) on h>ps://svn.science.uu.nl •  Select “create a new repository” •  Enter name and descrip$on, etc. Note for GT: the TA already created your repository! 20/11/13

8

2. Tool (SW Development)

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 documenta$on and further info 20/11/13

9


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

Access via Windows Explorer (right mouse bu>on)

•  First $me: 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 submiqng 20/11/13

10


SVN (subversion) Alterna$ve: use a Visual Studio Plugin, such as AnkhSVN

h>p://ankhsvn.open.collab.net

20/11/13

11


SVN (subversion) The best tool is only as good as the people using it.

Some SVN e9queHe:

•  •  • 

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, documenta8on, essen8al 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.

20/11/13

12


SVN (subversion) Usage for GT (mandatory): •  Your TA already created it •  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) 20/11/13

13

CODE RELATED DEADLINES

INFOB1PGT

INFOB1PICA

teambuilding & website, analysis & design document

teambuilding & website, project document

✓ development (coding & tes$ng)

intermediate report & presenta$on, revision of plans (if necessary)

SVN CODE (DEADLINE 16.12.)

tussenproduct, tussenpresenta$e

development (coding & tes$ng) final report, promo$on material (website, video, flyer), CD/DVD-‐box, presenta$on & demo for jury demo (& presenta$on?) at the symposium

20/11/13

SVN CODE met handleiding, flyer, eindverslag (DEADLINE 27.1.), eindpresenta$e end einproduct, CD/DVD WITH Ademonstra$e LL voor jury MATERIAL demonstra$e (+ presenta$e?) op symposium, CD/DVD-‐Box

14

2. Tools (AddiTonal Material)

Overview addiTonal material In addi$on to crea$ng the code & executable & docs, your final product/game also has to be … •  Promoted, e.g. via •  •  •  • 

a website (GT: via blogger) a video (only GT) a flyer a nice CD/DVD-‐box

•  Presented, e.g. to •  •  • 

20/11/13

the jury (ra$ng & nomina$ons) the public (hands on session at symposium) the award commi>ee (if you are one of the chosen ones) 15


Website Rule of thumb: •  One page for product / game •  One page for team presenta$on Or more, but be careful (good design takes $me) Some general $ps: •  Find balance between “marke$ng” & informa$on •  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 20/11/13

16


Website & Blog (only GT) For GT: The website should be a blog (using Blogger.com) •  The TA already created your blog •  You have to add “pages” to … •  … introduce your team and its members (Friday!) •  … show and promote your final game (in the end) •  You have to add “posts” to show your progress •  And of course: improve the overall design 20/11/13

17


Website & Blog (only GT) Your blog (created by TA): h>p://pgt13-‐.blogspot.nl/ •  is your team number (e.g. 1a, 1b, …) •  Refer to the website (under “teams”) to get it •  Don’t change this URL

20/11/13

18


Website & Blog (only GT) How to change your blog? •  Go to h>p://blogger.com •  Log in with your Google account •  This will bring you to Blogger’s Dashboard, where your blog should be listed •  Click on the menu icon to change “Seqngs”

20/11/13

19


Website & Blog (only GT) There, you can do all kinds of things, such as … •  Add a descrip$on •  Change it’s $tle •  Change the layout •  Chose a nice template And …

20/11/13

20


Website & Blog (only GT) Progress updates: what to post? From the course website (750 words as a rule of thumb): You can think of these topics (but not restricted to): Fun stuff to read Team building events Late night deadlines (with pizza and beer) Behind the scenes of a game developer Funny bugs Story behind the team name etc....etc.... Serious stuff to read a descrip$on of the class structure a descrip$on of how certain libraries or external sovware is used a descrip$on of an algorithm used in the game a descrip$on of the technology used etc....etc.... 20/11/13

21


Website & Blog (only GT) … add pages!

20/11/13

You have to … •  Create a page represen$ng your team and its members Deadline: this Friday, 22.11.13! •  Create a page (or more) represen$ng your final game by the end of the project Deadline: 27.1.14! •  Improve the layout (no deadline but be sure to start in $me) •  Regularly post progress updates and “interes$ng stuff” Deadlines: 22.11.13, 6.12.13, 20.12.13, 10.1.14, 24.1.14 (addi$onal posts are welcome!)

22


Website & Blog (only GT) Some $ps & recommenda$ons: •  Use the deadlines as milestones to show some project progress (e.g. first designs, screenshots, dravs, …) •  Mo$vate yourself by pos$ng addi$onal “fun stuff” in between •  Search the web for cool Blogger templates & styles •  Look for inspira$on at exis$ng blogs of real game companies, e.g. …

20/11/13

23


Website & Blog (only GT) Abbey games: h>p://abbeygames.com/ (there whole website is actually more of a blog)

20/11/13

24


Video (only GT) A nice trailer for your game •  For adver$sing, i.e. it should be fun •  For informa$on, i.e. it should reflect what you did and what’s special about it; make sure to highlight your extension(s)

Some general hints: •  Check examples of commercial games for inspira$on (but again, make sure to target it right) •  Look at last year’s videos for good & bad examples •  You also find tutorials and how-‐to infos online 20/11/13

25


Flyer Should give informa$on 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 adver$sement •  No scien$fic paper

Some general hints: •  Use website as template (save $me as much as possible) •  MS Office tools work surprisingly well for this 20/11/13

26


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 $me on it (e.g. use website & flyer as basis) 20/11/13

27


PromoTon material – general hints •  Save $me (and create corporate iden$ty) by using one design for all 3 (or 4) •  Check related how-‐to links and $ps on course website •  Check (& cri$cally evaluate) examples from last year •  Design for target audience and intended purpose!

20/11/13

28


PresentaTons To jury (3 tutors & 2 general members): •  Ra$ng of your game/product; basis for your grading •  Nomina$ons for best game/product award •  Make it informa$ve •  Make it “enjoyable”/entertaining To public (friends, families, colleagues): •  Others play your game / try out your product •  Vo$ng for audience award To award commiHee & press: •  Short demo in lecture hall (5 min) •  Entertain & impress ;) 20/11/13

29


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 sovware (e.g. Gimp, …) Videos: •  Screen capturing sovware, e.g. Camtasia Studio (30 days) •  Video edi$ng sovware, e.g. VirtualDub (free) •  Audio processing sovware, e.g. Audacity (free) •  Tools on your Macs & PCs (iMovie, MicrosoP Movie Maker)

You find some links on the course website. Note: these are also helpful to create content for your product. 20/11/13

30

3. Legal Issues

Disclaimer The following slides are a slight modifica$on 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!

20/11/13

31

3. Legal Issues

Most important warning Last year one team from the sovware 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. 20/11/13

32

3. Legal Issues

Rechten •  online materiaal is niet rechtsvrij •  belangrijk bij gebruik materiaal in professionele situa$e •  terrein is sterk in beweging •  nieuwe technische ontwikkelingen •  pressie vanuit content-‐ en sovware-‐industrie •  eindgebruikers hechten aan informa8evrijheid •  diverse rechten van intellectueel eigendom •  auteursrecht •  naburige rechten •  databaserecht •  zie ook vak Recht en Informa$ca •  h>p://www.cs.uu.nl/docs/vakken/ri/ •  verschillende ar$kelen (legale online toegang via UBU) 20/11/13

33

3. Legal Issues

Auteursrecht •  geev auteur recht van exploita$e •  geldt voor werken van ‘le>erkunde, wetenschap of kunst’ •  daaronder ook computerprogramma’s •  wordt automa$sch verkregen, geldt wereldwijd •  doel: s$muleren van culturele produc$e •  bevorderen van verspreiding kennis en cultuur •  middel: geev auteur economische prikkel tot produc$e •  recht geldt tot 70 jaar na dood auteur •  rechten gebruiker •  kennisname •  kopiëren voor eigen gebruik •  citaatrecht en andere vormen van informa$evrijheid

20/11/13

34

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’ •  sovware die ‘technisch effect’ heev kan ook onder octrooi vallen •  Amerika: patentrecht ruim toegepast op sovware •  veel triviale patenten 20/11/13

35

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 onrechtma$g (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 exploita$e •  stellen werk onder voorwaarden gra$s beschikbaar •  doen meestal geen afstand van rechten 20/11/13

36

3. Legal Issues

CreaTve Commons (CC)

biedt auteurs, kunstenaars, wetenschappers, docenten en alle andere crea$eve makers de vrijheid om op een flexibele manier met hun auteursrechten om te gaan

licen$emodellen voor kosteloos gebruik van digitale content •  juridisch goed beschermd •  jurispruden$e: Adam Curry vs. Weekend (2006) meer info op 20/11/13

h>p://crea$vecommons.nl/ & h>p://crea$vecommons.org/

37

3. Legal Issues

CreaTve Commons (CC) 4 licen$evoorwaarden mogelijk a>ribu$on share alike non-‐commercial no deriva$ve work

6 combina$es hiervan h>p://crea$vecommons.org/about/licenses/

20/11/13

38

3. Legal Issues

CreaTve Commons (CC) 4 licen$evoorwaarden mogelijk a_ribuTon share alike non-‐commercial no deriva$ve work


20/11/13

39

3. Legal Issues



20/11/13

40

3. Legal Issues



20/11/13

41

3. Legal Issues

CreaTve Commons (CC) 4 licen$evoorwaarden mogelijk a>ribu$on share alike non-‐commercial no derivaTve work


20/11/13

42

3. Legal Issues



20/11/13

43

3. Legal Issues

h>p://soundcloud.com/crea$vecommons

Voorbeeld CC SoundCloud A “social sound pla{orm” for crea$ng and sharing sounds (including music) Contains lots of sounds under the Crea$ve Commons licenses

20/11/13

44

3. Legal Issues

Voorbeeld CC

h>p://soundcloud.com/ h>ps://soundcloud.com/search/sounds?filter.license=to_use_commercially

3. Legal Issues

Voorbeeld CC

h>p://soundcloud.com/ h>ps://soundcloud.com/search/sounds?filter.license=to_use_commercially

3. Legal Issues

Open Source •  essen$e: gra$s programmacode •  en ook gecompileerde versies •  business model: sovware gra$s, services kosten geld •  geen afstand van auteursrecht! •  belangrijke grote toepassingen •  Linux, Mozilla (Firefox, Thunderbird), Open Office •  van alles op h>p://sourceforge.net/ •  verschillende licen$evormen •  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 licen$evormen •  schending voorwaarden is inbreuk op auteursrecht 20/11/13

47

3. Legal Issues

Wetenschappelijke kennis •  literatuur •  publica$es vallen onder auteursrecht •  vaak overgedragen aan uitgevers •  vragen veel geld voor online toegang •  veel discussie over juistheid hiervan •  open access $jdschriven •  pre-‐prints op web •  citaatrecht •  kennis kan vrijelijk worden toegepast •  morele verplich$ng tot citeren •  algoritmen •  vallen niet onder auteursrecht (beschermt de vorm) •  kunnen wel onder octrooi vallen (beschermt het idee) 20/11/13

48

3. Legal Issues

Welk recht heb je op je eigen werk? •  eigen bedrijf •  is van jou •  vrije $jd •  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: h>p://www.surffounda$on.nl/Auteursrechten/nl/Pages/ Default.aspx 20/11/13

49

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, a}eeldingen en documenten over de game is toegestaan •  conclusie: neem geen risico’s

20/11/13

50

3. Legal issues: (recommendaTon)

Use a disclaimer Put a disclaimer on your website/blog sta$ng that: •  This is an educa$onal 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 There are many examples and samples online. Search for them and make one that is suitable for your site.

20/11/13

51


Disclaimer example Here’s what I would probably write: “This site and its content are part of an educa$onal project done during a course in the computer science curriculum at Utrecht University. Its sole purpose is educa$onal 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. ”

20/11/13

52


Disclaimer example You also could consider adding a note about Fair use policy: h>p://en.wikipedia.org/wiki/Fair_use But note that this only covers United States copyright law. Further note that you are encouraged to be crea$ve and make your own graphics, sounds, etc.

20/11/13

53

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

20/11/13

54

4. Further Resources

CreaTve Commons examples •  Soundcloud (music, sounds) h>p://soundcloud.com •  Jamendo (music, paid licenses for commercial usage) h>p://www.jamendo.com •  Freesound (sounds, no music) h>p://www.freesound.org/ •  Wikimedia commons (photos, videos) h>p://commons.wikimedia.org/ •  Social media sharing pla{orms, such as h>p://flickr.com (photos) Bo>om line: there’s lots of stuff out there that you can legally use, but make sure to always check the license informa$on! 20/11/13

55

LECTURE 1: INTRO & ORGANISATION

INFOB1PGT teambuilding & website, analysis & design document

LECTURE 2: SW ENGINEERING & TEAMWORK

✓

INFOB1PICA teambuilding & website, project document

development (coding & tes$ng) intermediate report & presenta$on, LECTURE 5: revision of plans (if necessary) YOU!

tussenproduct, tussenpresenta$e

development (coding & tes$ng) final report, promo$on material eindverslag met handleiding, flyer, (website, video, flyer), CD/DVD-‐box, LECTURE 3: einproduct, eindpresenta$e end TOOLS, presenta$on & demo for jury demonstra$e voor jury RESOURCES & demo (& presenta$on?) demonstra$e (+ presenta$e?) op LEGAL ISSUES at the symposium symposium, CD/DVD-‐Box

20/11/13

LECTURE 4: GUESTS SPEAKER

56

5. Conclusion

Next step: guest lecture Fri, Nov 29, 11:00-‐12:45, guest lecture by Manuel Kerssemakers (Abbey Games)

IN PARALLEL: HARD WORK ON YOUR PROJECTS

J

Don’t forget that a>endance in the lectures is mandatory. For other deadlines, refer to the schedule on the website. 20/11/13

57

5. Conclusion

Final comments Any ques$ons? No? Then …

20/11/13

58

Lecture 3: Tools, Resources & Rights

Recommend Documents