Difference between revisions of "FreeArtSearch"

From Ghoulwiki
Jump to: navigation, search
(→‎database design)
(→‎notes)
Line 95: Line 95:
 
== notes ==
 
== notes ==
 
* [[BlenderNotes]] for embedding license-notes and similar in a .blend file
 
* [[BlenderNotes]] for embedding license-notes and similar in a .blend file
 +
 +
 +
== discussion 19.10.2007 ==
 +
 +
* freeartsearch code "gpl3 or later" ?
 +
* ghoulsblade task : svn list , image search and  thumbnail generation 
 +
 +
=== db layout ===
 +
 +
db layout :
 +
* art items
 +
** unique id ,
 +
** filename (not neccessarily unique)
 +
** download url for the full version (might be http or svn )
 +
** suspected author / svn username is just a hint, usecase : only lead artist has commit access
 +
** suspected license (we need a big fat disclaimer about that part)
 +
** a few other infos like
 +
 +
* tag search :
 +
** tagnames (id,name)
 +
** tag assignments (tagid,artid)
 +
 +
* assign projects to art items, can be multiple , e.g. just an informative list like "used in x,y,z" , hint from download url
 +
 +
* usersystem
 +
* artists
 +
 +
 +
(note to self : link to ugd thread is dead, i should dig that one out of the dump)
 +
 +
* association svn-username with nick : like in ohloh it should be possible to use different commit names that all refer to one person
 +
 +
 +
* usecase :  only lead artist has commit access : some of the artfiles are in fact made by him, but others are not and he just committed them
 +
 +
* loose link between art, project, commiter and artist/author, ie the project link could be used to guess the license of a file
 +
 +
 +
=== ideas for later ===
 +
* later : art request, concept sketches and notes, roles,subtasks : spec(polycount...),concept,model,unwrap,texture,anim...
 +
* many beginning game artists struggle with lack of direction
 +
* good : as many directions as possible, spiced with the "about" word like "about 1000 polys"
 +
* many specs are good, in  the sense of  "guidelines" , not as "limitations", they are not binding, and give a good starting point
 +
* artrequest tagging, e.g. hill-ogre for project xrpg would have the tags "monster","humanoid","fantasy"
 +
* or like model/prop, model/character, model/creature, model/vehicle, model/1stpersonweapon
 +
* real world objects, don't require much concept art, rather reference photos or blueprints
 +
 +
<tmass> if such uber task list existed, i could probably lure some concepts artists there
 +
<tmass> who spend time on training/personal projects
 +
<tmass> and wouldn't mind doing something required by others
 +
<tmass> many people are afraid of obligations connected with participation in projects
 +
<tmass> but one-time well defined tasks are different deal
 +
<tmass> people may occasionally have free time or creative mood
 +
<tmass> and check out such task list
 +
<tmass> it would also provide help in building artist's portfolios
 +
 +
* rss support, watchlist/subscribe : email notifications on add ...
 +
 +
* encourage free licenses for art request
 +
** options for "accepted" or "desired" licenses when making the request
 +
* gently encourage it without forcing it : also per-project can-we-use-this requests
 +
* some artists will want to grant permission to use "per project"
 +
** if they get to work with a few os project they might become more open-minded
 +
* not permitting to use the animated model of a game's main character in other projects is understandable
 +
* make it easy for people to ask the artist like "hey, cool thing, can we use it for our project as well ?"
 +
 +
 +
* user ratings for art  (registered and anonymous seperately displayed) e.g. with 1-5 stars or so like ohloh
 +
** hmm many people searching might not register
 +
* cudo system from ohloh ?  (social networking idea)
 +
 +
* some sort of commit monitoring would be cool, to see what's recently submitted
 +
** rss,  list of newest additions... and watchlist config stuff when registered (mail on new)
 +
 +
 +
=== first steps for core ===
 +
*  indexing svns (like openarena) , generating previews, and making a search for filename would be the first steps i think
 +
* next would be tagging
 +
* and  indexing freegamearts and virtual worlds wiki
 +
* (maybe later  worldforge and a few of the texture-repositories from my linklist, but those two above should be enough for getting started)

Revision as of 15:13, 20 October 2007

about

the main aim is to bring artists and developers closer together and encourage contact and dialog

  • a good search for existing free art
    • focused on searching/linking rather than hosting
      • index stuff from existing content repositories, project svn/cvs repositories and forums
    • possible to manually add single/multiple links to media data
    • preview images / thumbnails of textures,models,etc
    • tagging
    • licensing infos
    • technical infos (texture resolution, mesh poly count, mesh anims...)
    • contact info to reach the authors... (e.g. username + link to project forums or similar if no public email)
  • a database for projects and people
    • list/search artists and interests (concept drawing, model, anim, texture, 2d-art, texture, sound, music..)
    • list/search developers and interests (programming languages, experience with frameworks,)
    • list/search for projects using free art
    • cross referencing / associations
      • which people are involved in which project
      • assets used in multiple projects (textures, models, sound, music,...)

organization

  • people possibly interested in participating :
    • LeChuck from unixgamedev.org
    • ghoulsblade
    • hagish (if we use phpcake?)
    • more to come hopefully =)

database design

graphviz: http://www.linuxjournal.com/article/7275

at the moment this is just a sketch not a design 

digraph G {

person;
media;
project;
repository;

repository -> project [label="belongs to"];
media -> repository [label="contained in"];
media -> project [label="contained in"];

person -> repository [label="commit name"];
person -> media [label="can upload"];

}

technology ideas worth investigating

  • we'll probably use http://www.cakephp.org/ rapid development webframework similar to ruby-on-rails
  • svn list : search for (textures, models, audio, ...) in opensource project repositories svn/cvs
  • blender batch mode / importers : automatically generate mesh previews

existing websites to consider

free content repositories

projects and forum threads with free art

notes

  • BlenderNotes for embedding license-notes and similar in a .blend file


discussion 19.10.2007

  • freeartsearch code "gpl3 or later" ?
  • ghoulsblade task : svn list , image search and thumbnail generation

db layout

db layout :

  • art items
    • unique id ,
    • filename (not neccessarily unique)
    • download url for the full version (might be http or svn )
    • suspected author / svn username is just a hint, usecase : only lead artist has commit access
    • suspected license (we need a big fat disclaimer about that part)
    • a few other infos like
  • tag search :
    • tagnames (id,name)
    • tag assignments (tagid,artid)
  • assign projects to art items, can be multiple , e.g. just an informative list like "used in x,y,z" , hint from download url
  • usersystem
  • artists


(note to self : link to ugd thread is dead, i should dig that one out of the dump)

  • association svn-username with nick : like in ohloh it should be possible to use different commit names that all refer to one person


  • usecase : only lead artist has commit access : some of the artfiles are in fact made by him, but others are not and he just committed them
  • loose link between art, project, commiter and artist/author, ie the project link could be used to guess the license of a file


ideas for later

  • later : art request, concept sketches and notes, roles,subtasks : spec(polycount...),concept,model,unwrap,texture,anim...
  • many beginning game artists struggle with lack of direction
  • good : as many directions as possible, spiced with the "about" word like "about 1000 polys"
  • many specs are good, in the sense of "guidelines" , not as "limitations", they are not binding, and give a good starting point
  • artrequest tagging, e.g. hill-ogre for project xrpg would have the tags "monster","humanoid","fantasy"
  • or like model/prop, model/character, model/creature, model/vehicle, model/1stpersonweapon
  • real world objects, don't require much concept art, rather reference photos or blueprints

<tmass> if such uber task list existed, i could probably lure some concepts artists there <tmass> who spend time on training/personal projects <tmass> and wouldn't mind doing something required by others <tmass> many people are afraid of obligations connected with participation in projects <tmass> but one-time well defined tasks are different deal <tmass> people may occasionally have free time or creative mood <tmass> and check out such task list <tmass> it would also provide help in building artist's portfolios

  • rss support, watchlist/subscribe : email notifications on add ...
  • encourage free licenses for art request
    • options for "accepted" or "desired" licenses when making the request
  • gently encourage it without forcing it : also per-project can-we-use-this requests
  • some artists will want to grant permission to use "per project"
    • if they get to work with a few os project they might become more open-minded
  • not permitting to use the animated model of a game's main character in other projects is understandable
  • make it easy for people to ask the artist like "hey, cool thing, can we use it for our project as well ?"


  • user ratings for art (registered and anonymous seperately displayed) e.g. with 1-5 stars or so like ohloh
    • hmm many people searching might not register
  • cudo system from ohloh ? (social networking idea)
  • some sort of commit monitoring would be cool, to see what's recently submitted
    • rss, list of newest additions... and watchlist config stuff when registered (mail on new)


first steps for core

  • indexing svns (like openarena) , generating previews, and making a search for filename would be the first steps i think
  • next would be tagging
  • and indexing freegamearts and virtual worlds wiki
  • (maybe later worldforge and a few of the texture-repositories from my linklist, but those two above should be enough for getting started)
Retrieved from "https://ghoulsblade.schattenkind.net/wiki/index.php?title=FreeArtSearch&oldid=2100"