Lecture 3: Tools, Resources & Rights Wolfgang Hürst

Lecture 3: Tools, Resources & Rights

Wolfgang Hürst

Contact: [email protected], h2p://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 & tesBng) intermediate report & presentaBon, revision of plans (if necessary)

Tussenproduct & voorloopige website, tussenpresentaBe

development (coding & tesBng) final report, promoBon material eindverslag met handleiding, flyer, (website, video, flyer), CD/DVD-‐box, LECTURE 3: eindproduct, eindpresentaBe end TOOLS, presentaBon & demo for jury demonstraBe voor jury RESOURCES & demo (+ presentaBon?) demonstraBe (+ presentaBe?) op LEGAL ISSUES at the symposium symposium, CD/DVD-‐Box

11/21/12

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, communicaBon, … 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. 11/21/12

3


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

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

•  Projectspace voor studenten

h2ps://ict.science.uu.nl/index.php/Projectruimte

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

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

h2p://code.google.com & h2p://docs.google.com

11/21/12

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! 11/21/12

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/21/12

6


SVN (subversion)

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

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

Or a plugin, such as

h2p://ankhsvn.open.collab.net 11/21/12

7


SVN (subversion) To start, you have to create a repository on the server • Login (with SolisID) on h2ps://svn.science.uu.nl • Select create a new repository • Enter name and descripBon, etc. Note for GT: the TA already created your repository! 11/21/12

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 documentaBon and further info 11/21/12

9


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

Access via Windows Explorer (right mouse bu2on)

•  First Bme: 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 11/21/12

10


SVN (subversion) AlternaBve: use a Visual Studio Plugin, such as AnkhSVN

h2p://ankhsvn.open.collab.net

11/21/12

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.

11/21/12

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) 11/21/12

13

CODE RELATED DEADLINES

INFOB1PGT

INFOB1PICA

teambuilding & website, analysis & design document

teambuilding & website, project document

✓ development (coding & tesBng)

intermediate report & presentaBon, TUSSENPRODUCT revision of plans (if necessary)

tussenproduct, tussenpresentaBe

development (coding & tesBng) final report, promoBon material EINDPRODUCT (website, video, flyer), CD/DVD-‐box, presentaBon & demo for jury demo (& presentaBon?) CD/DVD WITH ALL at the symposium MATERIAL 11/21/12

eindverslag met handleiding, flyer, eindproduct, eindpresentaBe end demonstraBe voor jury demonstraBe (+ presentaBe?) op symposium, CD/DVD-‐Box

14

2. Tools (AddiTonal Material)

Overview addiTonal material In addiBon to creaBng 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 •  •  •  11/21/12

the jury (raBng & nominaBons) the public (hands on session at symposium) the award commi2ee (if you are one of the chosen ones) 15


Website Rule of thumb: •  One page for product / game •  One page for team presentaBon Or more, but be careful (good design takes Bme) Some general Bps: •  Find balance between markeBng & informaBon •  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/21/12

16


Video (only GT) A nice trailer for your game •  For adverBsing, i.e. it should be fun •  For informaBon, 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 inspiraBon (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 11/21/12

17


Flyer Should give informaBon 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 adverBsement •  No scienBfic paper Some general hints: •  Use website as template (save Bme as much as possible) •  MS Office tools work surprisingly well for this 11/21/12

18


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 Bme on it (e.g. use website & flyer as basis) 11/21/12

19


PromoTon material – general hints •  Save Bme (and create corporate idenBty) by using one design for all 3 (or 4) •  Check related how-‐to links and Bps on course website •  Check (& criBcally evaluate) examples from last year •  Design for target audience and intended purpose!

11/21/12

20


PresentaTons To jury (3 tutors & 2 general members): •  RaBng of your game/product; basis for your grading •  NominaBons for best game/product award •  Make it informaBve •  Make it “enjoyable”/entertaining To public (friends, families, colleagues): •  Others play your game / try out your product •  VoBng for audience award To award commiHee & press: •  Short demo in lecture hall (5 min) •  Entertain & impress ;) 11/21/12

21


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 ediBng 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. 11/21/12

22

3. Legal Issues

Disclaimer The following slides are a slight modificaBon 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/21/12

23

3. Legal Issues

Rechten •  online materiaal is niet rechtsvrij •  belangrijk bij gebruik materiaal in professionele situaBe •  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 InformaBca •  h2p://www.cs.uu.nl/docs/vakken/ri/ •  verschillende arBkelen (legale online toegang via UBU) 11/21/12

24

3. Legal Issues

Auteursrecht •  geev auteur recht van exploitaBe •  geldt voor werken van ‘le2erkunde, wetenschap of kunst’ •  daaronder ook computerprogramma’s •  wordt automaBsch verkregen, geldt wereldwijd •  doel: sBmuleren van culturele producBe •  bevorderen van verspreiding kennis en cultuur •  middel: geev auteur economische prikkel tot producBe •  recht geldt tot 70 jaar na dood auteur •  rechten gebruiker •  kennisname •  kopiëren voor eigen gebruik •  citaatrecht en andere vormen van informaBevrijheid

11/21/12

25

3. Legal Issues

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

26

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 onrechtmaBg (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 exploitaBe •  stellen werk onder voorwaarden graBs beschikbaar •  doen meestal geen afstand van rechten 11/21/12

27

3. Legal Issues

CreaTve Commons (CC)

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

licenBemodellen voor kosteloos gebruik van digitale content •  juridisch goed beschermd •  jurisprudenBe: Adam Curry vs. Weekend (2006) meer info op 11/21/12

h2p://creaBvecommons.nl/ & h2p://creaBvecommons.org/

28

3. Legal Issues

CreaTve Commons (CC) 4 licenBevoorwaarden mogelijk a2ribuBon share alike non-‐commercial no derivaBve work 6 combinaBes hiervan h2p://creaBvecommons.org/about/licenses/

11/21/12

29

3. Legal Issues

CreaTve Commons (CC) 4 licenBevoorwaarden mogelijk aZribuTon share alike non-‐commercial no derivaBve work 6 combinaBes hiervan h2p://creaBvecommons.org/about/licenses/

11/21/12

30

3. Legal Issues


11/21/12

31

3. Legal Issues


11/21/12

32

3. Legal Issues

CreaTve Commons (CC) 4 licenBevoorwaarden mogelijk a2ribuBon share alike non-‐commercial no derivaTve work 6 combinaBes hiervan h2p://creaBvecommons.org/about/licenses/

11/21/12

33

3. Legal Issues


11/21/12

34

3. Legal Issues

h2p://soundcloud.com/creaBvecommons

Voorbeeld CC SoundCloud A social sound playorm for creaBng and sharing sounds (including music) Contains lots of sounds under the CreaBve Commons licenses

11/21/12

35

3. Legal Issues

h2p://soundcloud.com/creaBvecommons

Voorbeeld CC

11/21/12

36

3. Legal Issues

Open Source •  essenBe: graBs programmacode •  en ook gecompileerde versies •  business model: sovware graBs, services kosten geld •  geen afstand van auteursrecht! •  belangrijke grote toepassingen •  Linux, Mozilla (Firefox, Thunderbird), Open Office •  van alles op h2p://sourceforge.net/ •  verschillende licenBevormen •  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 licenBevormen •  schending voorwaarden is inbreuk op auteursrecht 11/21/12

37

3. Legal Issues

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

38

3. Legal Issues

Welk recht heb je op je eigen werk? •  eigen bedrijf •  is van jou •  vrije Bjd •  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: h2p://www.surffoundaBon.nl/Auteursrechten/nl/Pages/ Default.aspx 11/21/12

39

4. Further Resources

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

40

LECTURE 1: INTRO & ORGANISATION

INFOB1PGT teambuilding & website, analysis & design document

LECTURE 2: SW ENGINEERING & TEAMWORK

✓

INFOB1PICA teambuilding & website, project document

development (coding & tesBng) intermediate report & presentaBon, LECTURE 6: revision of plans (if necessary) YOU!

tussenproduct, tussenpresentaBe

development (coding & tesBng) final report, promoBon material eindverslag met handleiding, flyer, (website, video, flyer), CD/DVD-‐box, LECTURE 3: einproduct, eindpresentaBe end TOOLS, presentaBon & demo for jury demonstraBe voor jury RESOURCES & demo (& presentaBon?) demonstraBe (+ presentaBe?) op LEGAL ISSUES at the symposium symposium, CD/DVD-‐Box

11/21/12

LECTURES 4 & 5: GUESTS SPEAKERS

41

5. Conclusion

Next steps: guest lectures Lecture 4, 28.11., 13:15-‐15:00, WENT-‐BLAUW Egbert Bouman, Valori, for both ICA & GT Lecture 5, 30.11., 09:00-‐10:45, MIN 211 Servaas Goossens, Ortec

IN PARALLEL: HARD WORK ON YOUR PROJECTS



Don’t forget that a2endance in the lectures is mandatory. For other deadlines, refer to the schedule on the website. 11/21/12

42

11/21/12

43

5. Conclusion

Final comments Any quesBons? No? Then …

11/21/12

44

Lecture 3: Tools, Resources & Rights Wolfgang Hürst

Recommend Documents