| |
Fungus
Registered: Sep 2002
Posts: 741 |
Link tools used to production
I would love to see this option, which would be just like the ones for intros/sids used in this production.
It's nice to give credits to the authors of the tools we use to make things yes? :) |
|
| |
Raistlin
Registered: Mar 2007
Posts: 745 |
There’s a lot of data that my OCD wants from CSDb .. but it’s about time I think.
Does nobody else feel like we’re filling these databases with information that only we, ourselves, will ever care about - and that we’re dwindling, not being replenished by new generations?
Maybe the day that the database will be complete, it will be done by the last of us to survive :’-) |
| |
Fungus
Registered: Sep 2002
Posts: 741 |
I think it's valuable to let people know what is being used for things, and points them at stuff they might not otherwise be aware of. I think it might be encouraging for the authors to see their tools are appreciated and being used as well.
I'm all for creating a more positive feedback loop.
Yes, I see what mean too. Someday we will all be gone, but our legacy should live on, there are young people becoming interested in our beloved little machine still. |
| |
oziphantom
Registered: Oct 2014
Posts: 502 |
okay but can the server handle building this page if everybody documented their use of it Krill |
| |
WVL
Registered: Mar 2002
Posts: 924 |
Please don't. Do we really need to credit each and every tool in a production? It would become a total mess with what cruncher was used, what assembler to make the intro, what graphics editor to make the font, what pizza delivery to get the linking done in time, etc..
The example with the loaders by Krill or LFT is a good example of things going crazy. Not that I don't want to credit them, but their personal pages are becoming a total mess. |
| |
Jetboy
Registered: Jul 2006
Posts: 354 |
Quoting FungusI'm all for creating a more positive feedback loop.
Have you ever noticed how good intentions tend to backfire and cause something totally different than intended? I smell this would be the case. |
| |
Krill
Registered: Apr 2002
Posts: 3077 |
Quoting WVLThe example with the loaders by Krill or LFT is a good example of things going crazy. Not that I don't want to credit them, but their personal pages are becoming a total mess. That's a CSDb problem, though, and not an attribution problem. =)
(I'd like some kind of filter there, for "lesser" vs. "notable" credits.)
Recognition is THE scene currency, thus, it's part of my loader's license agreement to give credit (apart from that, it's plain 3-clause BSD style).
If not explicitly demanded, it's of course up to the user to give credit or not. |
| |
mankeli
Registered: Oct 2010
Posts: 152 |
FWIW I think it would make sense to separate credits into people that were actively involved in making the production, and those whose previous work was used. (passive involvement) I don't think the data itself is bad, quite the contrary, it's quite remarkable that we have reached a database of this level!
I'm kind of thinking aloud here, so please bear with me.
Examples of active involvement:
- programmer who wrote some routines
- framework programmer that provided technical support
- loader programmer that provided technical support
- graphician who drew a logo, fullscreen gfx, charset
- graphician told the coder what looks nice
- musician who composed song for the demo
- musician who took their old song and edited it to fit the demo flow better
Examples of passive involvement:
- programmer who created a loader middleware product that was used
- graphician who originally draw the charset in 1988, that was picked by the programmer
- musician who composed a song that was then picked by the programmer
- programmer that did the playroutine? (may also be obvious if the tool is mentioned?)
- programmer who wrote the original version of routine on Codebase64 (if used very directly)
And then there's maybe a third category for tools themselves:
- assembler used
- music editor
- photoshop :)
Pizza driver is probably not worth mentioning, since they are very commoditized? :) They can be mentioned in the scroll text!
And maybe the tools authors can be listed in passive authors, if the tools themselves are scene-related? I definitely think that Krill, LFT, Cadaver, Slammer, etc. should be mentioned by name. But maybe it's enough if the production links to the tool (if it's a scene product and has a csdb page), and then the tool itself would just credit the author?
So: Active authors, passive authors, and authors of the means of production? :-D |
| |
WVL
Registered: Mar 2002
Posts: 924 |
Quote: Quoting WVLThe example with the loaders by Krill or LFT is a good example of things going crazy. Not that I don't want to credit them, but their personal pages are becoming a total mess. That's a CSDb problem, though, and not an attribution problem. =)
(I'd like some kind of filter there, for "lesser" vs. "notable" credits.)
Recognition is THE scene currency, thus, it's part of my loader's license agreement to give credit (apart from that, it's plain 3-clause BSD style).
If not explicitly demanded, it's of course up to the user to give credit or not.
I agree, but still your personal page is a mess :-) It's no fun finding a production by Krill or LFT and needing to sift through all the loader credits.
I had the same issue crediting Soya for the eyes I stole from 'Eyes' and used in Halloweed 4. I didn't want to mess up his page and added the credit in the production notes. This sounds like a good compromise between crediting and not messing things up to me, but who am I? |
| |
mankeli
Registered: Oct 2010
Posts: 152 |
Oops, I forgot to remove the loader and music replayer authors of the passive list and can't edit the post anymore. :) They shouldn't be on the "passive authors" if the tools themselves are mentioned. |
| |
Jetboy
Registered: Jul 2006
Posts: 354 |
Good that person who uploads prods to csdb is credited, with all that nonsense you want to add it will be more effort than making actual demo... |
... 19 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 - Next |
